A good tip during a UCS upgrade is to count the total number of flogi’s per FI before rebooting each FI. Good to make sure after reboot the same number are present.
Run the below command and get the vif names, and total. After reboot ensure same exists.
BigUCS-B(nxos)# show npv flogi-table
——————————————————————————–
SERVER EXTERNAL
INTERFACE VSAN FCID PORT NAME NODE NAME INTERFACE
——————————————————————————–
vfc764 250 0xe501a0 20:00:00:zz:zz:zz:b0:1f 20:00:00:zz:zz:zz:00:cf fc2/5
vfc774 250 0xe501c0 20:00:00:zz:zz:zz:b0:3f 20:00:00:zz:zz:zz:00:ef fc2/5
vfc784 250 0xe501a1 20:00:00:zz:zz:zz:b0:7f 20:00:00:zz:zz:zz:01:0f fc2/5
vfc794 250 0xe501c1 20:00:00:zz:zz:zz:b0:5f 20:00:00:zz:zz:zz:00:ff fc2/5
vfc826 250 0xe501a3 20:00:00:zz:zz:zz:b0:9f 20:00:00:zz:zz:zz:01:2f fc2/5
vfc836 250 0xe501a2 20:00:00:zz:zz:zz:b1:af 20:00:00:zz:zz:zz:01:4f fc2/5
vfc846 250 0xe501a4 20:00:00:zz:zz:zz:b1:bf 20:00:00:zz:zz:zz:01:6f fc2/5
vfc856 250 0xe501a6 20:00:00:zz:zz:zz:b1:ef 20:00:00:zz:zz:zz:01:9f fc2/5
vfc866 250 0xe501a5 20:00:00:zz:zz:zz:b1:df 20:00:00:zz:zz:zz:01:8f fc2/5
vfc876 250 0xe501a7 20:00:00:zz:zz:zz:b0:ff 20:00:00:zz:zz:zz:00:af fc2/5
Total number of flogi = 10.
To find the server belonging to a FC vif
BigUCS-B(nxos)# sho int fc vfc764
^
Invalid command (unexpected token) at ‘^’ marker.
BigUCS-B(nxos)# sho int vfc764
vfc764 is trunking
Bound interface is Vethernet8956
Port description is server 2/2, VHBA hba1
Hardware is Virtual Fibre Channel
Port WWN is 22:fb:54:7f:ee:12:0f:7f
Admin port mode is F, trunk mode is on
snmp link state traps are enabled
Port mode is TF
Port vsan is 250
Trunk vsans (admin allowed and active) (250)
Trunk vsans (up) (250)
Trunk vsans (isolated) ()
Trunk vsans (initializing) ()
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
65429679 frames input, 112652461052 bytes
0 discards, 0 errors
55603618 frames output, 72831100160 bytes
0 discards, 0 errors
last clearing of “show interface” counters never
Interface last changed at Tue Sep 16 15:31:55 2014
From knowing the Blade the corresponding Service Profile can be found with:
BigUCS-B(nxos)# show server assoc 2/2
With the blade known, the service profile can be found with (credit goes to John Kennedy for this command):
BigUCS-B# sho server assoc 2/2
Server Association Service Profile
——- ———— —————
2/2 Associated esx01
Hmm, wonder how a blade or service profile could be found with a WWPN? If anyone knows comment and will credit and add to post.
Be First to Comment