cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
411
Views
0
Helpful
1
Replies
Highlighted
Beginner

Identify Eye Height Port connectivity

Ran a command to measure Eye Height on Cisco UCS.  Got output similar to the one pasted below :

 

NXOS A (Fabric interconnect A)

+-------+------------+-------------+------------+----------------------------+--+--+--+--+--+--+--+--+--+--+
| Port | Eye Height | Eye Width | Raw values | Time measured |St|20|21|22|23|24|25|26|2E|2F|
+-------+------------+-------------+------------+----------------------------+--+--+--+--+--+--+--+--+--+--+
Eth 1/1 | 0 mv | 0 mUI | 0/ 0 | 04/24/2018 00:07:05.589517 |00|00|00|00|00|00|00|00|00|00|
fi0 | 200 mv | 859 mUI | 40/ 37 | 04/24/2018 00:06:28.910173 |00|00|00|00|00|00|00|00|00|00|
fi1 | 200 mv | 890 mUI | 40/ 39 | 04/24/2018 00:06:28.915304 |00|00|00|00|00|00|00|00|00|00|
Eth 1/2 | 0 mv | 0 mUI | 0/ 0 | 04/24/2018 00:10:41.693907 |00|00|00|00|00|00|00|00|00|00|
fi0 | 200 mv | 765 mUI | 40/ 31 | 04/24/2018 00:09:50.362649 |00|00|00|00|00|00|00|00|00|00|
fi1 | 200 mv | 843 mUI | 40/ 36 | 04/24/2018 00:09:50.367773 |00|00|00|00|00|00|00|00|00|00|
Eth 1/3 | 100 mv | 703 mUI | 20/ 2d | 08/02/2018 03:51:52.505439 |a9|e0|46|42|b2|60|46|42|88|00|
fi0 | 200 mv | 890 mUI | 40/ 39 | 08/02/2018 03:51:52.510551 |00|00|00|00|00|00|00|00|00|00|
fi1 | 200 mv | 875 mUI | 40/ 38 | 08/02/2018 03:51:52.515664 |00|00|00|00|00|00|00|00|00|00|
Eth 1/4 | 93 mv | 640 mUI | 1e/ 29 | 08/02/2018 03:51:58.612929 |a9|e0|4e|0e|f0|60|4e|0e|88|00|
fi0 | 200 mv | 859 mUI | 40/ 37 | 08/02/2018 03:51:58.618056 |00|00|00|00|00|00|00|00|00|00|
fi1 | 200 mv | 875 mUI | 40/ 38 | 08/02/2018 03:51:58.623198 |00|00|00|00|00|00|00|00|00|00|
Eth 1/5 | 100 mv | 671 mUI | 20/ 2b | 08/02/2018 03:52:04.712955 |a9|de|40|00|f0|5e|40|00|88|00|
fi0 | 200 mv | 875 mUI | 40/ 38 | 08/02/2018 03:52:04.718069 |00|00|00|00|00|00|00|00|00|00|

 

If you see "Eth 1/4" is having height value of 93. Trying to find out the blade server which is connected to this Port. Any idea how to get that information?

1 REPLY 1
Highlighted
Cisco Employee

Greetings.

It would be helpful to know the port role (i.e. Uplink, server).

If it's an uplink, then from the nxos, you can  check the pinned veths via:

(nxos)# show pinning interface port-channel xx

(nxos)# show pinning interface eth x/y

 

If you are looking at a server port that is connected to IOM/chassis, then take a look at https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ts/guide/UCSTroubleshooting/UCSTroubleshooting_chapter_01001.html  for the server (HIF) port pinning to NIF (IOM to FI link).

Excerpt below:

Link Pinning and Failover Behavior

Failures seen when a link between IOM and fabric interconnect (an IOM HIF port) goes down are more easily understood when the static route pinning applied to the servers in the chassis is understood. The quickest solution may be simply to reacknowledge the chassis, but understanding this topic will provide insight into when to apply that solution.

Table 2 Link Pinning on an IOM

Number of Active Fabric Links

Blade slot pinned to fabric link

1-Link

All the HIF ports are pinned to the active link

2-Link

1,3,5,7 to link-1

2,4,6,8 to link-2

4-Link

1,5 to link-1

2,6 to link-2

3,7 to link-3

4,8 to link-4

8-Link (Applies only to 2208XP )

1 to link-1

2 to link-2

3 to link-3

4 to link-4

5 to link-5

6 to link-6

7 to link-7

8 to link-8

Only 1,2,4 and 8 links are supported. 3,5,6, and 7 links are not valid configurations.

Here is an example of an expected behavior:

  1. There are four active links on each IOM to their respective fabric interconnects.

     

  2. Link 4 between IOM-1 and its fabric interconnect (currently Active) is accidentally unplugged by a datacenter worker.

     

  3. Connectivity through IOM-1 from blade slots 3,4,7, and 8 fails over to IOM-2 and the standby fabric interconnect. While you might think that only slots 4 and 8 would be affected, link 3 fails administratively because 3 link configurations are not supported. Data throughput is not lost, but the failure is noted in Cisco UCS Manager.

     

  4. At this point you can either:

     

    • Resolve the connectivity issue by plugging link 4 back in. Normal configured operation will resume.

       

    • Re-acknowledge the chassis, and the configuration will re-establish pinning to work over 2 fabric links. If at a later time the links are replaced or repaired, a second re-acknowledgement will be needed.

 

Thanks,

Kirk...

 

Content for Community-Ad