Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

UCS 5108 Fiber Interconnect

Dear Mike,

I unable to detect my chassis in the UCS manager. The 4 server ports tell me that "ether port 1 on fabric interconnect A oper state: link-up, reason: FEX not configured".

Actually I decomissioned my chassis while this problem was present. I thought that by recomissioning the chassis will solve the problem. But now I can see my chassis in the UCS.

Can you please help me?

Regards,

Sameer

5 REPLIES
Cisco Employee

UCS 5108 Fiber Interconnect

Hi Sameer,

Please refer to the following link which details the error:

http://www.cisco.com/en/US/docs/unified_computing/ucs/ts/faults/reference/FaultsTransient.html#wp1058312

"The Cisco UCS Manager discovered the chassis with  only one link in the first attempt although the chassis discovery policy  is configured for four links. Until the discovery is successful with  that link, the remaining links cannot be marked as active."

Check what your chassis discovery policy is set to, seems like it is set to 4 links. You need to change it to meet the amount of links that you have connected, which seems like 1 link. Make the change in the discovery policy and then re-acknowledge the chassis.

Let me know how you go.

Thanks,

Michael

New Member

UCS 5108 Fiber Interconnect

Dear Michael,

I have four links connected on each blade ( I have 2 blades) and all the four ports are in the same state. Also, I cannot see the chassis in UCS manager so how can I re-acknowledge it?

Regards,

Sameer

Cisco Employee

UCS 5108 Fiber Interconnect

Hi Sameer,

To recommission the chassis, please have a look at the following:

Recommissioning a Single Chassis

Please also confirm that these 4 links are connected to only a single fabric interconnect? That is, IOM 1 has 4 links connected to Fabric A and IOM 2 has 4 links connected to Fabric B?

After confirming the cabling and you recommission your chassis, if you continue to have issues, please provide the following:

1. UCS firmware version in use

2. Screenshot of the error from UCSM

3. Output of following commands:

      UCS-A# connect nxos A/B (collect these outputs from both A and B)

      UCS-A(nxos)# show fex

      UCS-A(nxos)# show fex detail

      UCS-A(nxos)# show interface fex-fabric

      UCS-A# scope org /

      UCS-A /org # scope chassis-disc-policy

      UCS-A /org/chassis-disc-policy # show detail

You can send this output to me in a private message if you prefer.

Thanks,

Michael

New Member

Re: UCS 5108 Fiber Interconnect

Dear Michael,

First of all I would thank you for your responce.

Ok, I cannot see anything in the Decommisioned tab, so there is nothing to Recomission.

Following is the output of the commands:

UCS firmware version is 2.0(1s)

MMR-A(nxos)# show fex

  FEX            FEX             FEX                  FEX

Number       Description         State      Model            Serial

------------------------------------------------------------------------

---       --------    Discovered           N20-C6508   QCI1507A3YX

MMR-A(nxos)#

MMR-A(nxos)#

MMR-A(nxos)#

MMR-A(nxos)# show fex detail

MMR-A(nxos)#

MMR-A(nxos)#

MMR-A(nxos)#

MMR-A(nxos)# show interface fex-fabric

     Fabric      Fabric       Fex                FEX

Fex  Port      Port State    Uplink    Model         Serial

---------------------------------------------------------------

---    Eth1/1    Discovered     1         N20-C6508  QCI1507A3YX

---    Eth1/2    Discovered     3         N20-C6508  QCI1507A3YX

---    Eth1/3    Discovered     2         N20-C6508  QCI1507A3YX

---    Eth1/4    Discovered     4         N20-C6508  QCI1507A3YX

MMR-A(nxos)#

MMR-A# scope org /
MMR-A /org # scope chassis-disc-policy
MMR-A /org/chassis-disc-policy # show detail

Chassis Discovery Policy:
    Description:
    Qualifier: none
    Action: 4 Link
    Rebalance: User Acknowledged
    Link Aggregation Pref: None
MMR-A /org/chassis-disc-policy #

MMR-B(nxos)# show fex

  FEX            FEX             FEX                  FEX

Number       Description         State      Model            Serial

------------------------------------------------------------------------

---       --------    Discovered           N20-C6508   QCI1511A2OI

MMR-B(nxos)#

MMR-B(nxos)#

MMR-B(nxos)#

MMR-B(nxos)#

MMR-B(nxos)# show fex detail

MMR-B(nxos)#

MMR-B(nxos)#

MMR-B(nxos)#

MMR-B(nxos)# show interface fex-fabric

     Fabric      Fabric       Fex                FEX

Fex  Port      Port State    Uplink    Model         Serial

---------------------------------------------------------------

---    Eth1/1    Discovered     1         N20-C6508  QCI1511A2OI

---    Eth1/2    Discovered     2         N20-C6508  QCI1511A2OI

---    Eth1/3    Discovered     4         N20-C6508  QCI1511A2OI

---    Eth1/4    Discovered     3         N20-C6508  QCI1511A2OI

MMR-B(nxos)#

MMR-B# scope org /
MMR-B /org # scope chassis-disc-policy
MMR-B /org/chassis-disc-policy # show detail

Chassis Discovery Policy:
    Description:
    Qualifier: none
    Action: 4 Link
    Rebalance: User Acknowledged
    Link Aggregation Pref: None
MMR-B /org/chassis-disc-policy #

Very strange for me, I have checked the physical connectivity as well, all the 8 cables are properly connected and there are green lights showing at the place where the cables are connected.

Thankyou for your help again.

Regards,

Sameer Ahmed Khan

Cisco Employee

Re: UCS 5108 Fiber Interconnect

Hi Sameer,

Thanks for getting me those outputs.

Since the chassis has been decommissioned, the UCS is ignoring the chassis at the end of the server ports - hence why we are seeing the "Fex not configured" on the 8 links (4 to each IOM).

As to why the chassis is not appearing in the "decommissioned" tab:

1) To verify if this is a mis-reporting in the GUI, try checking the following output:

      UCS-A# show chassis

      UCS-A# show chassis decommissioned

      If you see the decommissioned chassis, then attempt to recommission the chassis via the CLI. Commands documented via:

       Recommissioning a Chassis

2) Otherwise, can you try to unconfigure your 8 server ports and then re-configure them as server ports. What is the outcome?

3) If no improvement, can you power down the chassis, re-seat the IOMs, and then power the chassis back up. What is the outcome?

4) If all of this doesn't work, I suggest that you open a TAC case, reference this forum thread and the engineer can have a live troubleshooting session with you. Also let me know the TAC case number and i'll work with the engineer behind the scenes.

Let me know what happens.

Thanks,

Michael

1842
Views
0
Helpful
5
Replies
CreatePlease to create content