Virtual Ethernet Interface identification in UCS

[leivaae]

I would appreciate pointers or information that will help me identify UCS-5108 blade server and physical ethernet interfaces based upon a Veth#### value I get via CLI or SNMP from a UCS FI 6248. For example, using the command 'show mac address-table dynamic' on a 6248 CLI, I get the following information:

* 903      0025.b500.000e    dynamic   0          F    F  Veth1892

* 903      0025.b500.003f    dynamic   0          F    F  Veth1676

* 903      0025.b500.004f    dynamic   0          F    F  Veth1668

* 903      0025.b500.005e    dynamic   0          F    F  Veth1884

* 903      0025.b500.006e    dynamic   0          F    F  Veth1876

* 903      0025.b500.009f    dynamic   10         F    F  Veth1660

* 903      0025.b500.00af    dynamic   0          F    F  Veth1868

* 200      0050.5686.5d0d    dynamic   0          F    F  Veth1876

* 200      0050.5686.5d0e    dynamic   0          F    F  Veth1852

* 200      0050.5686.5d10    dynamic   0          F    F  Veth1876

* 200      0050.5686.5d13    dynamic   0          F    F  Veth1852

* 200      0050.5686.5d17    dynamic   0          F    F  Veth1916

* 200      0050.5686.5d1c    dynamic   0          F    F  Veth1892

How do I know what 5108 chassis, FEX uplink, physical ethernet port each of those Veth### ports are?

TIA,

Angel

[padramas · Accepted solution]

Hello Angel,

The following SAM CLI command provides complete path info for server NIC / vHBA 

              show service-profile circuit server X/Y

There are other commands which does not completely trace the path.

connect nxos

show pinning border-interfaces

show pinning server-interfaces

HTH

Padma

[leivaae]

Padma,

Thank you for the reply. It helps. I also contacted a Cisco TAC engineer, and got a reply with valuable information. It turns out that the Cisco UCS FI 6248 is quite similar to a Cisco Nexus 5500. I can use similar CLI commands and verify Virtual and physical interfaces. The following comamnds are quite useful to get what I was looking for:

- connect nxos

- sh run int veth####
- sh int veth####

Or

Under the SAM CLI:
- sh service-profile circuit detail
- sh service-profile circuit server x/y

Cheers,

Angel