vsan membership down on mapped FC uplink port

[Danny Sandner]

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 ports
Severity: 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. 

Thanks in advance

/Danny

[Walter Dey]

In FC NPV mode, each VSAN defined in UCS, is by default trunked in all uplinks, and this cannot be changed (similar to vlans, which are also included in all uplink trunks);  in your case, you have one link per vsan, no vsan trunk, therefore its really a cosmetic issue.

[padramas · Accepted solution]

Hello Danny,

Yes it is cosmetic issue in UCSM 2.2.1

the issue is tracked under

https://tools.cisco.com/bugsearch/bug/CSCum89468

The one you quoted (  CSCud81857 ) is specifically for FCoE uplinks from FI in UCSM 2.1 version.

HTH

Padma

[Danny Sandner]

Hey thanks.

Hope they will fix it soon. Now I have 24 warnings because I deleted some VLANs and create new ones. The old VLANs stuck in the warnings, too, either they do not exists anymore.

/Danny

[Larry Hedrick]

I have upgraded to 2.2(1c) and still have the problem... maybe the next version... 

[Larry Hedrick]

After I upgraded to 2.2(1d) the fault was still present until I disabled and enabled the FC interface, then the fault cleared... 

[kashima yoshihito]

I have upgrated to 2.2(2d) , but the problem has still going on . 

if we want to solve the issue ,

as we use anathor vsan which use uplink port .

shuld we make VSAN "blue"  on FabricInterconnectA , and VSAN "red" on FaricInterconnectB ?

For example

FabricInterconnectA has just VSAN  "blue"

FabricInterconnectB has just VSAN 　"red"

[Danny Sandner]

Hi kashimayoshihito,

you mean version 2.2(1d), right? They fixed similar problems. In 2.2(1c), all FC Uplinks (shut and no shut uplinks) failed. Now, only no shut uplinks fails.

If you use only one vsan per ucs fabric, you get no failure. This is the normal scenario for ucs, because normally you install the ucs in one rack / datacenter.

Release Notes of version 2.2(1d):

Erroneous minor faults “FCoE” or “FC uplink is down” are no longer displayed in Cisco UCS Manager when FC uplink interfaces are admin shut.

/Hugo

[kashima yoshihito]

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 .