Cisco MDS-9124 Troubleshooting Guide - Page 191
shutdown, no shutdown, debug fcns events register vsan
View all Cisco MDS-9124 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 191 highlights
Chapter 8 Troubleshooting Ports Common Problems with Port Interfaces Send documentation comments to [email protected] 7) FSM: Transition at 331187 usecs after Sun Feb 1 04:18:15 1980 Previous state: [FLOGI_ST_PERFORM_CONFIG] Triggered event: [FLOGI_EV_RIB_RESPOSE] Next state: [FLOGI_ST_PERFORM_CONFIG] /* Response from RIB */ 8) FSM: Transition at 331768 usecs after Sun Feb 1 04:18:15 1980 Previous state: [FLOGI_ST_PERFORM_CONFIG] Triggered event: [FLOGI_EV_ACL_CFG_RESPONSE] Next state: [FLOGI_ST_PERFORM_CONFIG] /* Response from RIB */ 9) FSM: Transition at 331772 usecs after Sun Feb 1 04:18:15 1980 Previous state: [FLOGI_ST_PERFORM_CONFIG] Triggered event: [FLOGI_EV_CONFIG_DONE_COMPLETE] Next state: [FLOGI_ST_FLOGI_DONE] /* Programming done */ Curr state: [FLOGI_ST_FLOGI_DONE] /* Flogi was successful */ Step 5 If the device logs in successfully, proceed to the next step. Otherwise, you may have a problem with the device or its associated software. Use the shutdown command in interface mode to shut down the Fibre Channel interface Then use the no shutdown command after turning on the debug described in Step 6 and Step 7. Note We recommend that you do not disable and then enable a T or TE port. This would affect all the VSANs crossing the EISL instead of just the VSAN experiencing the problem. Step 6 Use the debug fcns events register vsan command to watch the FLOGI process take place. switch# debug fcns events register vsan 99 This command enables debug mode for name server registration. It generates messages on the switch console related to FCNS events. The system output may look something like this: switch# config t Enter configuration commands, one per line. End with CNTL/Z. switch(config)# interface fc3/14 switch(config-if)# no shutdown /* enable the port */ switch(config-if)# Feb 17 04:42:54 fcns: vsan 99: Created entry for port-id 27800 Feb 17 04:42:54 fcns: vsan 99: Got Entry for port-id 27800 Feb 17 04:42:54 fcns: vsan 99: Registered port-name 36a4078be0000021 for port-id 780200 Feb 17 04:42:54 fcns: vsan 99: Registered node-name 36a4078be0000020 for port-id 780200 /* The wwpn and FCID for the port, note that the bytes in the world wide name are reversed */ Feb 17 04:42:54 fcns: vsan 99: Registered cos 8 for port-id 780200 /* Class of Service */ Feb 17 04:42:54 fcns: vsan 99: Registered port-type 1 for port-id 780200 /* Port Type */ Feb 17 04:42:54 fcns: vsan 99: Reading configuration for entry with port-name 36a4078be0000021, node-name 36a4078be0000020 Feb 17 04:42:54 fcns: vsan 99: No configuration present for this portname Feb 17 04:42:54 fcns: vsan 99: No configuration present for this nodename /* Port is now registered in nameserver, will send out RSCN to it */ OL-9285-05 Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x 8-19