UCS FCoE VSAN 1 down

Any way to clear these faults?
F1081 2013-02-21T15:04:24.658 157614 san Member 1/31 of Port-Channel 8 on fabric interconnect A is down, membership: down
F1081 2013-02-21T15:04:24.658 157613 san Member 1/32 of Port-Channel 8 on fabric interconnect A is down, membership: down
Have FCoE setup between 6248s and Nexus 5548s. Using VSAN 20 on Fabric A and VSAN 40 on Fabric B.
Why is VSAN 1 trying to initialize when I have the FCoE port-channel mapped to VSAN 20 in UCSM? Any way to set the allowed trunk vsan list?
Everything is working just would like the anoying faults to go away

Hi,
This sounds like:
FCoE Uplink vsan membership fault for any vsan not configured upstream
Symptom:
Fabric Vsan Membership Down fault message on FCoE uplink portsSeverity: Major
Code: F1083
Name: Fabric Vsan Membership Down
Conditions:
Observed with UCSM 2.1 and when FCoE uplink port is configured on the Fabric Interconnect
Workaround:
None.Error message is cosmetic.
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCud81857
I'd open a case on it and have them link it to the bug if it is indeed the case

Similar Messages

FCoE uplink is down on vsan

Hello, I have a problem connecting nexus switches to fabric interconnects.
I have created vsan's, unified uplinks, vfc interfaces on nexus, vlan to vsan mappings but still I see this fault in the event log.
HBA templates and HBA's are also created.
I have 2 nexus 5548up switches connected to UCS 6324 FI's.

Walter, I believe this is correct article in my case: http://www.cisco.com/c/en/us/support/docs/switches/nexus-5000-series-switches/116248-configure-fcoe-00.html
So I've done everything as described, including port-channel, but still have the same issue, do I miss something?
I've performed a migration from IBM Servers and FC-switches to UCS and now myb storage is connected via iSCSI, my goal is to make it FcOE connected so I'd have all the benefits of FC in unified fabric. This is my first experience with UCS and FcOE.
Here is what I have on Nexus side for now:
vfc50 is trunking
    Bound interface is port-channel4
    Hardware is Ethernet
    Port WWN is 20:31:8c:60:4f:1f:bd:ff
    Admin port mode is F, trunk mode is on
    snmp link state traps are enabled
    Port mode is TF
    Port vsan is 500
    Trunk vsans (admin allowed and active) (500)
    Trunk vsans (up)                       ()
    Trunk vsans (isolated)                 ()
    Trunk vsans (initializing)             (500)
    1 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
    1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
      0 frames input, 0 bytes
        0 discards, 0 errors
      0 frames output, 0 bytes
        0 discards, 0 errors
And UCS:
Interface Vsan Admin Admin Status Bind Oper Oper
Mode Trunk Info Mode Speed
Mode (Gbps)
vfc765 500 F on trunking Veth8957 TF auto
vfc767 500 F on trunking Veth8959 TF auto
vfc776 1 E on trunking Po4 TE 20
FI-A-A(nxos)# sh flogi data
INTERFACE VSAN FCID PORT NAME NODE NAME
vfc765 500 0x5f0000 20:00:00:25:b5:00:0a:1f 20:00:00:25:b5:00:00:0f
vfc767 500 0x5f0020 20:00:00:25:b5:00:0a:0f 20:00:00:25:b5:00:00:1f
I don't understand why vfc's 765,767 are not binded to Po4.

Vsan membership down on mapped FC uplink port

Hi,
since I updated Cisco UCS Manager, all Chassis and Fabric Interconnects to version 2.2(1), I get some minor faults.
I configure ports 31 and 32 as FC uplink ports and mapped each port to a vsan:
Port 31 = VSAN "blue"
Port 32 = VSAN "red"
(I know, this is not common to map two diffrent VSANs to the same fabric, but I have to )
Since the update, I get minor faults:
Port 31 --> FCoE or FC uplink is down on VSAN "red" / membership-down
Port 32 --> FCoE or FC uplink is down on VSAN "blue" / membership-down
I have no FC port channels or FC trunking mode activated. Fabric Interconnect is in EHM.
Same in the other fabric.
Can someone help me or is this the same cosmetic issue as discussed in the quote?
FCoE Uplink vsan membership fault for any vsan not configured upstream Symptom:Fabric Vsan Membership Down fault message on FCoE uplink portsSeverity: MajorCode: F1083Name: Fabric Vsan Membership DownConditions:Observed with UCSM 2.1 and when FCoE uplink port is configured on the Fabric InterconnectWorkaround:None.Error message is cosmetic.
Thanks in advance
/Danny

Hi HugoStiglitz
I saw this message , after upgradet to 2.2(1d)
but In several times , Cleared this message .
Fist of all ,
I Removed All FCoE Uplink Cable whose FabricInterconnect-A
and then
I saw FCoE or FC uplink is down on VSAN Red and blue
but, FabricInterconnect-A has no VSAN blue in this port-Channel
In several times ,
FCoE or FC uplink is down on VSAN blue is clear.
I have no idea , when clear this messages .

N5K running 5.0(2)N2(1) support for FCOE VSAN-trunking

Hi, from 5.0(2)N2(1) on , on the N5K on a FCoE Port VSAN-trunking should be supported on VE-Port and VF-Port.
But I could not find a doc how to configure
classical configuration where I assign one VSAN to every FCoE-Port
vlan 111
name ETH_111
vlan 112
name ETH_112
vlan 113
name ETH_113
vlan 1011
name VSAN_1
fcoe vsan 1
vlan 1012
name VSAN_2
fcoe vsan 2
vlan 1013
name VSAN_3
fcoe vsan 3
vsan database
vsan 1 interface vfc 1
vsan 2 interface vfc 2
vsan 3 interface vfc 3
int vfc 1
bind interface eth 1/1
int vfc 2
bind interface eth 1/2
int vfc 3
bind interface eth 1/3
interface eth 1/1
switchport mode trunk
switchport trunk allowed vlan 111,1011
spanning-tree port type edge trunk
spanning-tree bpduguard enable
interface eth 1/2
switchport mode trunk
switchport trunk allowed vlan 112,1012
spanning-tree port type edge trunk
spanning-tree bpduguard enable
interface eth 1/3
switchport mode trunk
switchport trunk allowed vlan 113,1013
spanning-tree port type edge trunk
spanning-tree bpduguard enable
no I want to configure FCoE trunk transporting all 3 VSANs on Eth 1/4
interface vfc 4
description FCoE Uplink
bind interface eth 1/4
switchport trunk allowed vsan 1-3
interface eth 1/4
description FCoE Uplink
switchport mode trunk
switchport trunk allowed vlan 1011,1012,1013
spanning-tree port type edge trunk
spanning-tree bpduguard enable
so I assume I do not have to configure anything additional in the VSAN-database, I saw it s only possible to assign a VFC-Interface to only one VSAN.
Does anybody have more infos about configuring VSAN-trunking on FCoE Ports ?
Thx in Advance
Hubert

Unless you need to keep the data separate, there is not a requirement to place each VFC interface in a different VSAN. They can all exist in the same VSAN, and you can isolate them from each other using zoning with in the VSAN.
What are you looking to trunk the FCoE connections to? At this point the only option is another N5K. Eventually, there will be FCoE trunk support between the N5K, the Cisco N7K, and the MDS.
You are correct that for the trunk port, you do not need to ad any VSAN database entry. It will reside in the default VSAN which is normally VSAN 1.
It this not working for you, or is this a planned configuration that you want to verify.
You do need to make the VFC 4 interface in your post an E port. 'switchport mode e' is the command.
Here is a snip from a working FCoE trunk port on a 5K. It happens to use an Ethernet port channel bound to the VFC.
pod2-N5010-82# sh run interface port-channel 402
version 5.0(2)N1(1)
interface port-channel402
switchport mode trunk
switchport trunk allowed vlan 122,222
speed 10000
pod2-N5010-82# sh run interface vfc 402
version 5.0(2)N1(1)
interface vfc402
bind interface port-channel402
switchport mode E
switchport trunk allowed vsan 122
switchport trunk allowed vsan add 222
no shutdown
pod2-N5010-82# sh int vfc 402
vfc402 is trunking
    Bound interface is port-channel402
    Hardware is Virtual Fibre Channel
    Port WWN is 21:91:00:05:9b:20:a9:7f
    Peer port WWN is 00:00:00:00:00:00:00:00
    Admin port mode is E, trunk mode is on
    snmp link state traps are enabled
    Port mode is TE
    Port vsan is 1 <====
    Trunk vsans (admin allowed and active) (122,222)
    Trunk vsans (up)                       (122,222)
    Trunk vsans (isolated)                 ()
    Trunk vsans (initializing)             ()
HTH,
Mike

UCS FCoE Native VLAN

Cisco doc (http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/white_paper_c11-560403.html) about FIP advises the following:
"The FIP VLAN discovery protocol is the only FIP protocol running on the native VLAN; all other FIP protocols run on the discovered FCoE VLANs."
As for FCoE in UCS, Is the native vlan mentioned above FCoE native VLAN (by default is vlan 4049 in UCS 2.0) ?

Hi,
Usually when you add it to the trunk as native, you don't to add again. So, option-2
HTH

Cisco UCS-E vsan HCL

Can anyone verify if the Cisco UCS -E Series has a raid controller supported by vmware vsan?

Hi Wilson,
Cisco Have recently submitted an Expert Webcast: Cisco Unified Computing System (UCS) B series Upgrade & Troubleshooting
https://supportforums.cisco.com/event/12289671/expert-webcast-cisco-unified-computing-system-ucs-b-series-upgrade-troubleshooting
Let me know for any questions / concerns, much appreciated.
Thanks!
Tara

UCS F port trunking and reserved VSAN confusion

We have an existing UCS infrastructre where all the FI's FC ports are connected to the MDS9513 as one to one connection ( no port channel or trunking) and the FI is working as "end host mode" . We are planning to move some crtical production application to the UCS infrastrcture and becuse of that we would like to use the FC port chanelling and F-port trunking. While reading some documents I found that there are some restriction on UCS for VSAN numbering while using the FI for F-port trunking . As per the following doc http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/cli/config/guide/2.0/b_UCSM_CLI_Configuration_Guide_2_0_chapter_010101.html#concept_5223F7F368524A39AB1A47B9F8BFEC8A
it says donot configure VSAN ID range from 3840 to 4079 . The MDS 9513 is running NX-OS 4.2(3) . Our existing MDS SAN infrstructure already have 2 VSANs with ID number 4000 and 4001 ( Both of these VSANS are usied for some storage replication unrelated to UCS). In the UCS we alreay have 2 VSANS' ( 200 and 201) and are planning to create 2 more ( 300 and 301). My question is if I configure the FI's for F-port truncking/FC port channeling then what will happen to my existing VSAN 4000 and 4001 on the MDS9513 SAN
Thanks
RK

If you are asking how long it will take to enable f-port trunk and how disruptive it will be? It's not lengthy, but, it will cause the link to stop passing traffic and cause SCSI retrys. Your server will know it happened. If your fc multipathing is operating properly there will be no outage.If there are any configuration issues, the link may be down for an extended period, further compounding this disruption in traffic.
You initially asked about two features, f-port trunk and f-port channel. These are seperate features and require different configuration changes. It's best to add one feature at a time, not both in the same configuration change. Each change will be disruptive.
Do one fabric at a time. Ensure the f-port trunk is fully functional before doing the f-port channel, making sure it is functional before starting work on the second fabric.If your multipathing is operating as it should, there will be no outage. If there is any doubt schedule an outage window.
Dave

Nexus 5548UP FCoE to C series UCS

Ok here is the scenario
nexus 5548 switch ---- fex 2232 --- UCS C series (C220)
snippets of the configuration:
vlan 1100
fcoe vsan 1100
vlan database
vsan 1100
fex 100
description 2232-A
fcoe
int ethernet100/1/1
switchport
switchport mode trunk
switchport trunk allowed vlan 10,1100
interface vfc100
bind interface ethernet100/1/1
switchport trunk allowed vsan 1100
no shut
so it is configured above, the vfc interface won't trunk unless I do the following:
vsan database
vsan 1100 interface vfc100
I found this document that describes mapping VSANs to VLANs example configuration (page 8)

Each fc and/or vfc interface must be member of a VSAN; by default, they belong all initially to VSAN 1.

FCoE Nexus 5000

Hi,
I have a Nexus 5000 conected with a UCS C-200 with qlogic CNA in FCoE. The ethernet traffic is ok, but FC dont work fine, i thinks that i have configured all ok, by the show int vfc show the trunk vsan in initializating mode and i dont find what is the problem
switch(config-if)# sh int vfc 1
vfc1 is trunking
    Bound interface is Ethernet1/9
    Port description is Conexion FC con UCS1
    Hardware is Virtual Fibre Channel
    Port WWN is 20:00:00:0d:ec:e8:2c:7f
    Admin port mode is F, trunk mode is on
    snmp link state traps are enabled
    Port mode is TF
    Port vsan is 1
    Trunk vsans (admin allowed and active) (1)
    Trunk vsans (up)                       ()
    Trunk vsans (isolated)                 ()
    Trunk vsans (initializing)             (1)
    1 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
    1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
      0 frames input, 0 bytes
        0 discards, 0 errors
      0 frames output, 0 bytes
        0 discards, 0 errors
    last clearing of "show interface" counters never
    Interface last changed at Mon Dec 20 19:59:31 2010
switch(config-if)# show port internal info interface vfc 1
vfc1 - if_index: 0x1E000000, phy_port_index: 0x1000
     local_index: 0xffff
Admin Config - state(up), mode(F), speed(auto), trunk(on)
    beacon(off), snmp trap(on), tem(false)
    description(Conexion FC con UCS1)
    port owner()
Operational Info - state(trunking), mode(TF), speed(auto), trunk(on)
    state reason(None)
    phy port enable (1), phy layer (FC), port_osm_mode(OSM)
    participating(1), fcid(0x000000), bb_scn(0)
    config port vsan (1), oper port vsan (1)
    rx bb_credit(0), rx bb_credit multiplier(0)
    rx bb_credit performance buffers(0), tx bb_credit(0)
    not first time port bringup is 0
    Port WWN is 20:00:00:0d:ec:e8:2c:7f
    current state [PI_FSM_ST_TXPORT_INIT_TRUNKING_ENABLED]
    port_init_eval_flag(0x00000401), cfg wait for none
        FC_PORT_INIT_DATA_VALID (0)
        FC_PORT_INIT_ADMIN_ST_DOWN_TO_UP (10)
        FC_PORT_INIT_PHY_PORT_UP (49)
    Mts node id 0x0
    Lock Info: resource [vfc1]
      type[0] p_gwrap[(nil)]
          FREE @ 259535 usecs after Mon Dec 20 19:59:31 2010
      type[1] p_gwrap[(nil)]
          FREE @ 260559 usecs after Mon Dec 20 19:59:31 2010
      type[2] p_gwrap[(nil)]
          FREE @ 266012 usecs after Mon Dec 20 19:59:31 2010
    0x10000001e000000
    eport_init_flag(0x00000000), elp_chk_flag(0x00000000)
    elp_rcvd_fc2_handle(0x00000000), elp_sent_fc2_handle(0x00000000)
    esc_chk_flag(0x00000000), esc_fc2_handle(0x00000000)
    elp_flags(0x0000), classes_supported(F), tx bb_credit(0)
    Peer ELP Revision: 0
    Timer active for PI_FSM_EV_TE_2_E_TIMER_EXPIRED
    cnt_link_failure(0), cnt_link_success(0), cnt_port_up(0)
    cnt_cfg_wait_timeout(2), cnt_port_cfg_failure(2), cnt_init_retry(0)
    nos link failures (0), debounce window (300 ms), elp wait tout (750 ms)
    link fail reason (0x0)    num_elps_before_up (0)
    internal_reinit_counter (0) external_reinit_counter (0)
Trunk Info -
    trunk vsans (allowed active) (1)
    trunk vsans (operational allowed) (1)
    trunk vsans (up) ()
    trunk vsans (isolated) ()
TE port per vsan information
vfc1, Vsan 1 - state(down), state reason(waiting for flogi), fcid(0x000000)
    port init flag(0x0),
    Lock Info: resource [vfc1, vsan 1]
      type[0] p_gwrap[(nil)]
          FREE @ 270103 usecs after Mon Dec 20 19:59:31 2010
      type[1] p_gwrap[(nil)]
          FREE @ 270104 usecs after Mon Dec 20 19:59:31 2010
      type[2] p_gwrap[(nil)]
          FREE @ 270105 usecs after Mon Dec 20 19:59:31 2010
    0x40000011e000000
current state [TE_FSM_ST_WAIT_FOR_FLOGI]
    RNID info not found.
    first time elp: 1
    Peer ELP Revision: 0
Pacer Info -
    Pacer state: released credits due to timer expiry
PQP: not in progress
My configuration
vlan 701
fcoe vsan 1
name FCoE-Vsan1
interface vfc1
bind interface Ethernet1/9
switchport description Conexion FC con UCS1
no shutdown
interface Ethernet1/9
description Conexion FCoE con UCS1
switchport mode trunk
spanning-tree port type edge trunk
I need configure anything in UCS?.
Regards.

Under your ethernet 1/9 try adding:
switchport trunk allowed vlan 1, 701
Assuming vlan 1 as your native default vlan and 701 is FCoE vlan, this should bring up vlan 701 to your CNA.

FCoE in Nexus 5000

Hi,
I have a Nexus 5000 conected with a UCS C-200 with qlogic CNA in FCoE. The ethernet traffic is ok, but FC dont work fine, i thinks that i have configured all ok, by the show int vfc show the trunk vsan in initializating mode and i dont find what is the problem
switch(config-if)# sh int vfc 1
vfc1 is trunking
    Bound interface is Ethernet1/9
    Port description is Conexion FC con UCS1
    Hardware is Virtual Fibre Channel
    Port WWN is 20:00:00:0d:ec:e8:2c:7f
    Admin port mode is F, trunk mode is on
    snmp link state traps are enabled
    Port mode is TF
    Port vsan is 1
    Trunk vsans (admin allowed and active) (1)
    Trunk vsans (up)                       ()
    Trunk vsans (isolated)                 ()
    Trunk vsans (initializing)             (1)
    1 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
    1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
      0 frames input, 0 bytes
        0 discards, 0 errors
      0 frames output, 0 bytes
        0 discards, 0 errors
    last clearing of "show interface" counters never
    Interface last changed at Mon Dec 20 19:59:31 2010
switch(config-if)# show port internal info interface vfc 1
vfc1 - if_index: 0x1E000000, phy_port_index: 0x1000
     local_index: 0xffff
Admin Config - state(up), mode(F), speed(auto), trunk(on)
    beacon(off), snmp trap(on), tem(false)
    description(Conexion FC con UCS1)
    port owner()
Operational Info - state(trunking), mode(TF), speed(auto), trunk(on)
    state reason(None)
    phy port enable (1), phy layer (FC), port_osm_mode(OSM)
    participating(1), fcid(0x000000), bb_scn(0)
    config port vsan (1), oper port vsan (1)
    rx bb_credit(0), rx bb_credit multiplier(0)
    rx bb_credit performance buffers(0), tx bb_credit(0)
    not first time port bringup is 0
    Port WWN is 20:00:00:0d:ec:e8:2c:7f
    current state [PI_FSM_ST_TXPORT_INIT_TRUNKING_ENABLED]
    port_init_eval_flag(0x00000401), cfg wait for none
        FC_PORT_INIT_DATA_VALID (0)
        FC_PORT_INIT_ADMIN_ST_DOWN_TO_UP (10)
        FC_PORT_INIT_PHY_PORT_UP (49)
    Mts node id 0x0
    Lock Info: resource [vfc1]
      type[0] p_gwrap[(nil)]
          FREE @ 259535 usecs after Mon Dec 20 19:59:31 2010
      type[1] p_gwrap[(nil)]
          FREE @ 260559 usecs after Mon Dec 20 19:59:31 2010
      type[2] p_gwrap[(nil)]
          FREE @ 266012 usecs after Mon Dec 20 19:59:31 2010
    0x10000001e000000
    eport_init_flag(0x00000000), elp_chk_flag(0x00000000)
    elp_rcvd_fc2_handle(0x00000000), elp_sent_fc2_handle(0x00000000)
    esc_chk_flag(0x00000000), esc_fc2_handle(0x00000000)
    elp_flags(0x0000), classes_supported(F), tx bb_credit(0)
    Peer ELP Revision: 0
    Timer active for PI_FSM_EV_TE_2_E_TIMER_EXPIRED
    cnt_link_failure(0), cnt_link_success(0), cnt_port_up(0)
    cnt_cfg_wait_timeout(2), cnt_port_cfg_failure(2), cnt_init_retry(0)
    nos link failures (0), debounce window (300 ms), elp wait tout (750 ms)
    link fail reason (0x0)    num_elps_before_up (0)
    internal_reinit_counter (0) external_reinit_counter (0)
Trunk Info -
    trunk vsans (allowed active) (1)
    trunk vsans (operational allowed) (1)
    trunk vsans (up) ()
    trunk vsans (isolated) ()
TE port per vsan information
vfc1, Vsan 1 - state(down), state reason(waiting for flogi), fcid(0x000000)
    port init flag(0x0),
    Lock Info: resource [vfc1, vsan 1]
      type[0] p_gwrap[(nil)]
          FREE @ 270103 usecs after Mon Dec 20 19:59:31 2010
      type[1] p_gwrap[(nil)]
          FREE @ 270104 usecs after Mon Dec 20 19:59:31 2010
      type[2] p_gwrap[(nil)]
          FREE @ 270105 usecs after Mon Dec 20 19:59:31 2010
    0x40000011e000000
current state [TE_FSM_ST_WAIT_FOR_FLOGI]
    RNID info not found.
    first time elp: 1
    Peer ELP Revision: 0
Pacer Info -
    Pacer state: released credits due to timer expiry
PQP: not in progress
My configuration
vlan 701
fcoe vsan 1
name FCoE-Vsan1
interface vfc1
bind interface Ethernet1/9
switchport description Conexion FC con UCS1
no shutdown
interface Ethernet1/9
description Conexion FCoE con UCS1
switchport mode trunk
spanning-tree port type edge trunk
I need configure anything in UCS?.
Regards.

A network diagram would be quite useful ? is it multihop FCoE, Storage connectivity with FCoE,......

Vfc error disabled because of Ethernet port down?

We are building a new datacenter and is starting to set up the SAN.
This small DC consist of 2 Nexus 5596UP, a Compellent SAN and 2 Dell M1000e cassis with blade servers.
naive FC part in Nexus has been easy to set up but we have problems with the FCOE setup.
Since the blades are not installed yet none of the Ethernet ports are up. As soon as we bind an ethernet port to a vfc the vfc goes to error disable with this message:
%PORT-2-IF_DOWN_ERROR_DISABLED: %$VSAN 1900%$ Interface vfc101 is down (Error disabled)
Config snippets:
vlan 1900
fcoe vsan 1900
name VSAN-A-FCOE
vlan 1901
name VSAN-B-FCOE
vsan database
vsan 1900 name "VSAN-A"
vsan 1901 name "VSAN-B"
interface vfc101
bind interface Ethernet1/1
no shutdown
vsan database
vsan 1900 interface vfc101
vsan 1900 interface fc2/13
vsan 1900 interface fc2/14
vsan 1900 interface fc2/15
vsan 1900 interface fc2/16
interface Ethernet1/1
switchport mode trunk
spanning-tree port type edge trunk
vlan 1900
fcoe vsan 1900
name VSAN-A-FCOE
vlan 1901
name VSAN-B-FCOE
vsan database
vsan 1900 name "VSAN-A"
vsan 1901 name "VSAN-B"
vsan database
vsan 1900 interface vfc101
vsan 1900 interface fc2/13
vsan 1900 interface fc2/14
vsan 1900 interface fc2/15
vsan 1900 interface fc2/16
interface vfc101
bind interface Ethernet1/1
no shutdown
interface Ethernet1/1
switchport mode trunk
spanning-tree port type edge trunk
Do the vfc go error disable because the ethernet interface being down? I was under the impression it should just go "down"

What you are seeing is normal.. Here are outputs from my lab switch where I shut Eth1/20 which is tied to vFC 20
24.10.5020A.1(config)# int ethernet 1/20
24.10.5020A.1(config-if)# shut
2011 Oct 21 10:16:01 24 %ETHPORT-5-IF_DOWN_CFG_CHANGE: Interface Ethernet1/20 is down(Config change)
2011 Oct 21 10:16:01 24 %FLOGI-5-MSG_PORT_LOGGED_OUT: %$VSAN 100%$ [VSAN 100, Interface vfc20: mode[TF]] Nx Port 21:00:00:c0:dd:12:0e:35 logged OUT.
2011 Oct 21 10:16:01 24 %PORT-5-IF_PORT_QUIESCE_FAILED: Interface vfc20 port quiesce failed due to failure reason: Epp Not Supported by Peer (0x19d)
2011 Oct 21 10:16:01 24 %PORT-5-IF_DOWN_NONE: %$VSAN 100%$ Interface vfc20 is down (None)
2011 Oct 21 10:16:01 24 %PORT-2-IF_DOWN_ERROR_DISABLED: %$VSAN 100%$ Interface vfc20 is down (Error disabled)
2011 Oct 21 10:16:02 24 %ETHPORT-5-IF_DOWN_ADMIN_DOWN: Interface Ethernet1/20 is down (Administratively down)
24.10.5020A.1(config-if)#

Nexus 5548UP FCoE

Hi,
I'm trying to setup an connection from Netapp to n5k using CNA card on Netapp.
I've configured n5k as it should, but it seems that it always fails with:
2011 Jun 27 11:45:19 site1-n5k-sw1 %PORT-5-IF_TRUNK_DOWN: %$VSAN 50%$ Interface vfc31, vsan 50 is down (waiting for flogi)
Any ideas if it's configured wrongly on nexus side ... (?) Thanks.
feature fcoe
interface Ethernet1/23
switchport mode trunk
spanning-tree port type edge trunk
vlan 50
fcoe vsan 50
vsan database
vsan 50 interface vfc31
interface vfc31
bind interface Ethernet1/23
switchport trunk allowed vsan 50
no shutdown
# sh vsan membership
vsan 50 interfaces:
    fc1/29            vfc31
n5k-sw1(config-if)# sh int vfc31
vfc31 is trunking
    Bound interface is Ethernet1/23
    Hardware is Virtual Fibre Channel
    Port WWN is 20:1e:00:05:73:f2:b0:bf
    Admin port mode is F, trunk mode is on
    snmp link state traps are enabled
    Port mode is TF
    Port vsan is 50
    Trunk vsans (admin allowed and active) (50)
    Trunk vsans (up)                       ()
    Trunk vsans (isolated)                 ()
    Trunk vsans (initializing)             (50)
    1 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
    1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
      0 frames input, 0 bytes
        0 discards, 0 errors
      0 frames output, 0 bytes
        0 discards, 0 errors
    last clearing of "show interface" counters never
    Interface last changed at Mon Jun 27 11:43:17 2011
-n5k-sw1(config-if)# sh flogi database
INTERFACE        VSAN    FCID           PORT NAME               NODE NAME
fc1/29           50    0xb80000 20:41:00:05:73:e3:59:80 20:32:00:05:73:e3:59:81
Total number of flogi = 1.

Documentation says so
The Ethernet interface that you bind the virtual Fibre Channel interface to must be configured as follows:
•It must be a trunk port (use the switchport mode trunk command).
•The FCoE VLAN that corresponds to virtual Fibre Channel's VSAN must be in the allowed VLAN list.

Nexus 5548 UP and FCoE an brocade

Hi,
I need help.
Architecture :
I have got two Nexus 5548UP .
The nexus are linked to 2 brocade 200e.
Esxi are conrected to Nexus 2248PP, Fcoe and Data >>> interface 101/1/9
Problem:
I try configured Fcoe to Esxi 5.0 but the interface vfc 1 still down.
My configuration :
fex 101
pinning max-links 1
description "FEX101-N2232PP-S12"
fcoe
fex 102
pinning max-links 1
description "FEX102-N2232PP-Sxx"
fcoe
slot 1
port 31-32 type fc
vlan 2900
fcoe vsan 2900
vsan database
vsan 2900
feature npv
interface fc1/31
no shutdown
interface fc1/32
interface Ethernet101/1/9
descri TO-ESXI
switchport mode trunk
vfc1 is down (Error disabled)
    Bound interface is Ethernet101/1/9
    Hardware is Ethernet
    Port WWN is 20:00:54:7f:ee:b6:4b:bf
    Admin port mode is F, trunk mode is on
    snmp link state traps are enabled
    Port vsan is 2900
    1 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
    1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
      0 frames input, 0 bytes
        0 discards, 0 errors
      0 frames output, 0 bytes
        0 discards, 0 errors
    last clearing of "show interface" counters never
Help me,
Cdlt,

Hi,
I had same configuration on both N5K.
I have removed the configuration Fcoe on second N5k.
Interface vfc1 seems to be Ok.
But i have another problem, On esxi the Emulex One command plug-in says ethernet's interfaces is up.
But Vcenter sees them down !!
Emulex One command :
In the distibuted Vswitch :
But LLDP seems Ok :

Single Nexus 5548UP- FCoE configuration with multiple server ports

Hello Everyone,
I am new to Networking so please bear with me.
Here is some background information. We have a SINGLE Nexus 5548 UP switch to which we are connecting both the storage and the UCS C240 M3 servers (with CNA). Both the storage and server has 2 ports each going to this nexus switch.
We want to implement FCoE with this solution.
Below are the steps (for server ports) that I have followed to configure the nexus. But the port not logging into the SAN (no flogi) with the config.
Enable Features
config t
feature lacp
feature dot1x
feature interface-vlan
feature sshServer
feature npiv
end
Confgure Ethernet Ports - Server
configure
interface ethernet 1/17
description To_UCS_rack_server_1_FCoE_port_1
switchport mode trunk
switchport trunk native vlan 6
switchport trunk allowed vlan 1,6
spanning-tree port type edge trunk
priority-flow-control mode on
no shutdown
end
configure
interface ethernet 1/18
description To_UCS_rack_server_1_FCoE_port_2
switchport mode trunk
switchport trunk native vlan 6
switchport trunk allowed vlan 1,6
spanning-tree port type edge trunk
priority-flow-control mode on
no shutdown
end
Create VLAN
configure
vlan 6
name FCOE_VLAN
fcoe vsan 6
end
Setup FCoE QOS
configure terminal
system qos
service-policy type qos input fcoe-default-in-policy
service-policy type queuing input fcoe-default-in-policy
service-policy type queuing output fcoe-default-out-policy
service-policy type network-qos fcoe-default-nq-policy
end
Create vfc for Initiators (UCS Servers)
configure
interface vfc 17
bind interface ethernet 1/17
switchport description virtual_fiber_channel_Server1_Port1
end
configure
interface vfc 18
bind interface ethernet 1/18
switchport description virtual_fiber_channel_Server1_Port2
end
Adding vFC’s to VSAN
configure
vsan database
vsan 6 interface vfc 17
vsan 6 interface vfc 18
Create Zonesets and Zones
configure
show flogi database vsan 6 ----> Do not see any pwwn here???
show fcns database vsan 6
Any help in the regard would be highly appreciated.
Cheers,
KS

Fixed the issue. "switchport trunk native vlan 6" was causing the issue. Maybe the storage and Servers were not configured with proper VLAN's. I removed the native vlan and everything logged in fine.
Any how I have configured a single zone with all 3 servers pWWN's. I know single initiator zoning is the way to go.
Can you please guide me if I can move these servers in their separate zones without any outages? If it helps, all severs have 2 pWWN's. The current zoneset is active with that single zone.
Please let me know if you need any additional details.
Cheers,
KS

UCS HA test

Hi,
I am building UCS system UC applications. I have two 5108 chassis with 3 B200 M2 blade in each Chassis. I completed configuration and want to do 'Production Readiness Test’ on UCS. When power down Fabric Interconnect-A (Primary), all my ESX hosts does not respond for the ping, more 5 mins, which is unexpected behavior. Secondly all my VMs on the ESX hosts lose disk connection and VMs get disk errors.
If anybody have seen this behavior and know the fix, please let me know.
Thanks in advance...
Cheers
CG

Can you plz explain litle more about your UCS setup
like
1. vNIC configuration in UCS
2. configuration of vNICs in ESX ,
3.UCSM version
4. CNA type and
5. no of uplink sounthbound connectivity.
Regards
Manick

UCS FCoE VSAN 1 down

Similar Messages

Maybe you are looking for