OmniSwitch OS6860/OS6900/OS10K Troubleshooting Guide Part No.032996-00 Rev.A
AOS Release 7.X and 8.X January 2015
Alcatel-Lucent Page 79 of 148
arp( 76) 0 3 - 396 - - 460 115[115 ] 0[0 ]
0[0 ] 0[0
ripng( 77) 0 3 397 - - - 461 0[0 ] 0[0 ]
0[0 ] 0[0
pim( 78) 0 3 - 398 - - 462 0[0 ] 0[0 ]
0[0 ] 0[0
mcipc( 82) 0 3 399 - - - 463 183182[183182 ] 0[0 ]
0[0 ] 0[0
10.4. Troubleshooting in the Maintenance Shell
Maintenance Shell commands should only be used by Alcatel-Lucent personnel or under the
direction of Alcatel-Lucent. Misuse or failure to follow procedures that use Maintenance Shell
commands in this guide correctly can cause lengthy network down time and/or permanent damage to
hardware.
VFC Troubleshooting
Swlog is extremely important to trace any VFC-related issues. All VFC-related swlog is stored in the /var/log
directory called "vfc1.log". Note that the swlog is cleared every time the OmniSwitch OS6900 or 10K is
rebooted.
For example if VFC error messages appeared on the console and you want to see more details as to what
happened during that time, login as super user "su", cd to the /var/log directory, open the vfc.log file, and
search for that particular timestamp when the error event happened. To troubleshoot VFC in real-time while
having the console connection active, open a telnet session and do the following as indicated below:
#-> cd /var/log
#-> ls
fd1.log ipms.log lag.log mcm.log vfc1.log vm.log vstk.log wtmp
#-> tail -f vfc1.log
19 16:49:04 - dbg: [vfcInitSlotProfile:249] Create Transaction buffer vfcTxBuf[0
19 16:49:04 - dbg: [vfcInitSlotProfile:254] zNI 0, profiling done
19 16:49:04 - dbg: [vfcInitSlotProfile:249] Create Transaction buffer vfcTxBuf[1
19 16:49:04 - dbg: [vfcInitSlotProfile:254] zNI 1, profiling done
19 16:49:04 - dbg: [vfcConnectToCS:52] VFC Connect to CS
19 16:49:04 - dbg: [vfcConnectToPM:602] VFC Connected to PM
19 16:49:04 - dbg: [main:407] ==generated MIB database==
19 16:49:04 - dbg: [main:410] VFC cslib_unblock
19 16:49:04 - dbg: [vfcMainLoop:301] vfcMainLoop
19 16:49:04 - dbg: [vfcHandleMipMsg:380] Queuing the MIP message
19 16:49:04 - dbg: [getQsapRangeFromIfIndex:1920] Before EOIC: received PORT qsa
19 16:49:04 - dbg: [getQsapRangeFromIfIndex:1920] Before EOIC: received PORT qsa
19 16:49:04 - dbg: [vfc_qsap_control_prop:2185] Invalid QSI 719 16:49:04 - dbg:
19 16:49:04 - dbg: [vfcHandleMipMsg:380] Queuing the MIP message
19 16:49:04 - dbg: [getQsapRangeFromIfIndex:1907] Before EOIC: received LAG qsap
19 16:49:04 - dbg: [vfcHandleMipMsg:380] Queuing the MIP message
19 16:49:04 - dbg: [vfcMipEoicFunction:268] EOIC received
19 16:50:15 - dbg: [vfcAddNewConnection:256] New connection: 127.2.65.1:37985, S
19 16:50:15 - dbg: [vfcHandleIncomingMsg:140] NI 0 connected after NI DOWN, sock
19 16:50:15 - dbg: [vfcHandleIncomingMsg:147] RX VFC_MSG_HELLO zNi 0 BOOTUP
19 16:50:15 - dbg: [vfcPMEventsRegister:575] Port Manager Registrations Done
10.5. Troubleshooting in bShell
Display Field Processing Selector configuration (in AOS the configuration is always the same for all ports):
BCM.0> d chg fp_port_field_sel
FP_PORT_FIELD_SEL.ipipe0[0]:
<SLICE9_S_TYPE_SEL=2,SLICE9_F3=6,SLICE9_8_PAIRING=1,SLICE8_S_TYPE_SEL=2,SLICE8_F3=3,SLICE8_F2=5,
SLICE8_F1=1,SLICE7_S_TYPE_SEL=1,SLICE7_F2=5,SLICE7_F1=5,SLICE6_S_TYPE_SEL=1,SLICE5_S_TYPE_SEL=1,S
LICE4_S_TYPE_SEL=1,
SLICE3_S_TYPE_SEL=2,SLICE3_F3=5,SLICE3_F1=1,SLICE2_S_TYPE_SEL=1,SLICE2_F3=6,SLICE2_F2=4,SLICE2_F1
=6,SLICE1_S_TYPE_SEL=1,
To Next Page
Loading...
