Instruction/ maintenance manual of the product 6624 Alcatel
Go to page of 614
OmniSwitc h Troubles hooting Guide September 2005 i Part No. 031496-00, Rev. C September 2005 OmniSwitch 6624/6648/ 6800/7700/7800/8800 T r oubleshooting Guide www.
ii OmniSwitch Troubleshooting Guide September 2005 This troubleshoo ting guide documen ts OmniSwitch 6624/6 648/770/78 00/8800 hardware, including ch assis and associat ed compone nts, and Rel ease 5.1 softwa re. The specifications described in this guid e are subject to change without notice.
OmniSwitc h Troubles hooting Guide September 2005 iii Contents About This Guide ...................... ................ ................ ................... ................ ............... . xv Supported Platforms ...................... .............
iv OmniSwitch Troubleshooting Guide September 2005 Verify Source Learning ................. .................... ................ ................... ................ ........... 2-6 Verify Switch Health ................................. .............
OmniSwitc h Troubles hooting Guide September 2005 v GMIGBPDU ................. ............... .................... ............... .................... ............. 4-16 GM2FIXED .................. ............... .................... ..............
vi OmniSwitch Troubleshooting Guide September 2005 Troubleshooting a DNS Failure ............................ ................ ............... .................... ....... 6-2 Starting the Troubleshooting Procedure ......................... ..........
OmniSwitc h Troubles hooting Guide September 2005 vii Dshell ............. ................ ............... .................... ................ ............... .................... ..... ...... 9-6 NI Debug Dshell ......................... .........
viii OmniSwitch Troubleshooting Guide September 2005 Dshell Troubleshooting .......... ............... .................... ............... .................... ................ . 11-8 Viewing the ARP Table on Om niSwitch 6624 /6648 Switches .........
OmniSwitc h Troubles hooting Guide September 2005 ix Dshell Troubleshooting .......... ............... .................... ............... .................... ................ . 14-9 Chapter 15 Troubleshooting DVMRP ............ ....................
x Omni Switch Troubleshooting Guide September 2005 Multicast Group Status is Shown as Disabled ... ................... .................... ........... 16-27 PIM-SM Limitations ...................... .................... ............... ..............
OmniSwitc h Troubles hooting Guide September 2005 xi Chapter 19 Troubleshooting 802.1X ......................... .................... ............... ................ ............. 1 9-1 In This Chapter ........... ................ ...................
xii OmniSwitch Troubleshooting Guide September 2005 Calendar Manager Module ............................. ................... ................ .................... A-19 Data Port Output Module ................... ........ ................ ............
OmniSwitc h Troubles hooting Guide September 2005 xiii Bus Mapping on OmniSwitch 7700/7800/8800 Switches ............... .................... ........ A-42 Xybus Mapping ...................... .................... .................... ............... .
xiv OmniSwi tch Troubleshooting Guide September 2005.
OmniSwitc h Troubles hooting Guide September 2005 page -xv About This Guide This OmniSwitch Trou bleshooting G uide describes how to use Command Line Interface (CLI) an d Dshell commands availabl e on the OmniSwitch 66 00 Family, OmniSwitch 6800 Series, OmniSwitch 7700/7800, and the OmniSwitch 880 0 to troublesho ot switch and network problems.
page -xvi OmniSwitch Troubleshooting Guide September 2005 Note. Troubleshooting documen tation for le gacy produc ts (e.g., Omni Switc h/Router) can be download ed at http://sup port.
OmniSwitc h Troubles hooting Guide September 2005 page -xvii • Related commands. • Release history, which indicate s the re lease when the comma nd was in troduced. Appendix D provides a li st of useful VI editor commands and a sample VI session t hat modifies the boot.
page -xviii OmniSwitch Troubleshooting Guide September 2005 • OmniSwitch 6800 Series Hardwar e Users Guide Complete technical spe cifications and procedures for all OmniSwit ch 6800 chassis, power sup plies, fans, uplink mo dules, and st acking modu les.
OmniSwitc h Troubles hooting Guide September 2005 page -xix • OmniSwitch 7700 /7800/8800 Network Configura tion Guide Includes network configuration p rocedures and descri ptive informati on on all the majo r software features and pr otocols included in the base soft ware pack age.
page -xx OmniSwitch Troubleshooting Guide September 2005 Before Calling Alcatel’ s T echnical Assistance Center Before calling Alc atel’s Technical Assistanc e Center (TAC), make sure that yo u have read thro ugh the appropriate section (or sect ions) and have complete d the actions suggested for your system’s problem.
OmniSwitc h Troubles hooting Guide September 2005 page 1-1 1 T r oubleshooting the Switch System In order to troubleshoot th e system, a basic understanding of the oper ation of Chassis Management Modules (CMMs) and their in teraction with Netwo rk Interface (NI) modul es is required.
Introduction Troubleshooting the Switch System page 1-2 OmniSwitch Troubleshooting Guide September 2005 Intr oduction The CMM is the Ma nagement Modul e of the switch. All of the critical operations of the switch includi ng the monito ring is the resp onsibility of th e CMM.
Troubleshooting the Switch System Troubleshooting System for OS-6624/664 8 and OS-7/8XXX OmniSwitc h Troubles hooting Guide September 2005 page 1-3 T roubleshooting System for OS-6624/6648 and OS-7/8XXX If the switch is having any problems the first pl ace to look for is the CMM.
Troubleshooting System for OS-6624/6648 and OS-7/8XXX Troubleshooting the Switc h System page 1-4 OmniSwitch Troubleshooting Guide September 2005 NI-2 UP POWER ON N/A 00:d0:95:84:3d:26 NI-3 UP POWER O.
Troubleshooting the Switch System Troubleshooting System for OS-6624/664 8 and OS-7/8XXX OmniSwitc h Troubles hooting Guide September 2005 page 1-5 Hardware Revision: , Serial Number: B42N101P2 , Manu.
Troubleshooting System for OS-6624/6648 and OS-7/8XXX Troubleshooting the Switc h System page 1-6 OmniSwitch Troubleshooting Guide September 2005 Power Supplies in chassis 8 PS Operational Status -----+------------------- PS-1 UP PS-2 NOT PRESENT Make sure that all the known go od power supplies are operatio nal.
Troubleshooting the Switch System Troubleshooting System for OS-6624/664 8 and OS-7/8XXX OmniSwitc h Troubles hooting Guide September 2005 page 1-7 The average on one minute is calculated from t he average of 12 sample s. Each sample is an average of the CPU utilization during 5 second s.
Troubleshooting System for OS-6624/6648 and OS-7/8XXX Troubleshooting the Switc h System page 1-8 OmniSwitch Troubleshooting Guide September 2005 d on NI slot 1, GBIC port 2 MON AUG 21 23:28:39 2023 H.
Troublesho oting the Switch Sy stem Advanced Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 1-9 Advanced T roubleshooting One level of switch loggin g is stored in the two log files located in the /flash directory. There is another low level debu g that can be enabled and used for diagnosin g the problems.
Advanced Troubleshooting Troubleshooting the Switch System page 1-10 OmniSwitch Troubleshooting Guide September 2005 _SM_IPCUP_TIMEOUT 3349118948 CSM-CH info tCsCSMtas k csCsmHelloReceptio - -> CS_.
Troubleshooting the Switch System Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 1-11 Dshell T roubleshooting To further diagnose the t ask consuming the CPU o n the CMM one needs to use the fo llowing Dshell commands: Note.
Dshell Troubleshooting Troubleshooting the Switch System page 1-12 OmniSwitch Troubleshooting Guide September 2005 GrpMob gmcControl 5793320 100 0% ( 80) 0% ( 0) Stp stpCMM_mai 56b3eb0 100 0% ( 82) 0%.
Troubleshooting the Switch System Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 1-13 2 tasks were created. 2 tasks were deleted. spyStop value = 0 = 0x0 It seems that the CPU task is high because of tNetTask , Ipedr , and tOSPF .
Dshell Troubleshooting Troubleshooting the Switch System page 1-14 OmniSwitch Troubleshooting Guide September 2005 %o0 = 490f9e0 %o1 = 0 %o2 = 0 %o3 = 0 %o4 = 0 %o5 = 0 %sp = 490f920 %o7 = 0 value = 76612560 = 0x49103d0 Certified: [Kernel]-> To troubleshoot a CPU or mem ory spike with 5.
Troubleshooting the Switch System Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 1-15 tAioIoTask0 Asynchro nous I/O Supp ort tNetTask Routing Task tIpedrMsg IP Ethernet .
Dshell Troubleshooting Troubleshooting the Switch System page 1-16 OmniSwitch Troubleshooting Guide September 2005 Health Health Task L3Hre Layer 3 HRE Task DbgNiGw NI Debug supp ort SrcLrn Source Learning Task GrpMob Group Mobility Task Stp Spanning Tree Task 8021q 802.
Troubleshooting the Switch System Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 1-17 DrcTm Dynamic Routing Control Timer Task tDrcIprm Dynamic Routing Contro l Ta sk fo.
Dshell Troubleshooting Troubleshooting the Switch System page 1-18 OmniSwitch Troubleshooting Guide September 2005 tIpedrMsg IP Ethernet Driver Task Me ssage handler tahw_sch Spanning Tree Supp ort qd.
Troubleshooting the Switch System Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 1-19 taNiEsmDrv NI Ethernet switc hing drive r task tsLnkState Link State monitor task P.
Dshell Troubleshooting Troubleshooting the Switch System page 1-20 OmniSwitch Troubleshooting Guide September 2005 onex 802.1X Vrrp VRRP task UdpRly UDP Relay task Qos CMM QOS PolMgr Policy Manage r t.
Troubleshooting the Switch System Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 1-21 tCS_CVM Chassis Version Manager SesMon_12 Session Monitor tTelnetOut0e4208c Telnet .
Dshell Troubleshooting Troubleshooting the Switch System page 1-22 OmniSwitch Troubleshooting Guide September 2005 1:0 0160cef8 t_ipc_cmm_p 1% 1% 1:0 015f61d0 taL3Hre 0% 1% 1:0 015ee670 taXMAP_ni 0% 1.
Troubleshooting the Switch System Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 1-23 OmniSwitch 6624/6648 Dshell T roubleshooting One of the important things in OS-660 0 is to confirm the stack topo logy.
Dshell Troubleshooting Troubleshooting the Switch System page 1-24 OmniSwitch Troubleshooting Guide September 2005 To view the stack to pology in de tail, use the follo wing command: Working: [Kernel].
Troubleshooting the Switch System Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 1-25 NI=4 CMM=0 role=3 * state_linkA=1 remote_slotA=5 remote_li nkA=51 * state_linkB=1 r.
Using AlcatelDebug.cfg Troubleshooting the Switch System page 1-26 OmniSwitch Troubleshooting Guide September 2005 In stacking environment, only th e primary and secondary switches h ave console enabled whereas consol e is disabled for th e idle switches.
Troubleshooting the Switch System Troubleshoot ing IPC on OS-6/7/8XXX Series of Switches OmniSwitc h Troubles hooting Guide September 2005 page 1-27 T roubleshooting IPC on OS-6/7/8XXX Series of Switches IPC (Inter Process Communication) is should by the system to communi cate between different software modules.
Troubleshooting IPC on OS-6/7/8XXX Seri es of Switches Troubleshooting the Switch System page 1-28 OmniSwitch Troubleshooting Guide September 2005 LocalPool: Full size is 64, remain ing: 64 In socket .
Troubleshooting the Switch System Troubleshoot ing IPC on OS-6/7/8XXX Series of Switches OmniSwitc h Troubles hooting Guide September 2005 page 1-29 LocalPool: Full size is 64, remain ing: 64 In socket queues: 0 Not queued: 0: DMA queues: 0 In the above two outputs it seems th at the cont rol pool is stuck and th e socket queues are i ncrementing.
Troubleshooting IPC on OS-6/7/8XXX Seri es of Switches Troubleshooting the Switch System page 1-30 OmniSwitch Troubleshooting Guide September 2005 value = 10 = 0xa Working: [Kernel]-> The above command displays a lot of information bu t we are intere sted in the most repeatin g socket ID.
Troubleshooting the Switch System Troubleshoot ing IPC on OS-6/7/8XXX Series of Switches OmniSwitc h Troubles hooting Guide September 2005 page 1-31 Now doing a task trac e on this task can be helpfu .
Troubleshooting IPC on OS-6/7/8XXX Seri es of Switches Troubleshooting the Switch System page 1-32 OmniSwitch Troubleshooting Guide September 2005 LocalPool: Full size is 0, remaini ng: 1024 In socket queues: 0 Not queued: 0: In DMA queues: 0 value = 6 = 0x6 The above displa y of the command do es not show the Fu ll size of an y of the pool s.
Troubleshooting the Switch System Troubleshoot ing IPC on OS-6/7/8XXX Series of Switches OmniSwitc h Troubles hooting Guide September 2005 page 1-33 631908 next = 0x17c8c44, pFreeQ = 0x2fc7a8, data_of.
Troubleshooting IPC on OS-6/7/8XXX Seri es of Switches Troubleshooting the Switch System page 1-34 OmniSwitch Troubleshooting Guide September 2005 nidbg> tt 0x15f7768 1e6ce0 vxTaskEntry +c : stp_ta.
Troubleshooting the Switch System Troubleshoot ing IPC on OS-6/7/8XXX Series of Switches OmniSwitc h Troubles hooting Guide September 2005 page 1-35 Socket ID = 0x100, dest slot = 5, re mote addr = 0x.
Port Numbering Conversion Overvi ew Troubleshooting the Switch System page 1-36 OmniSwitch Troubleshooting Guide September 2005 Por t Numbering Conversion Over view The sections below docu ment how to convert port number parameters. Note. Dshell co mmands should only be used by Alcat el personnel or under th e direction of Alcatel.
Troubleshooting the Switch System Po rt Numbering Conversion Overview OmniSwitc h Troubles hooting Guide September 2005 page 1-37 Note that 1 is the uport number.
Port Numbering Conversion Overvi ew Troubleshooting the Switch System page 1-38 OmniSwitch Troubleshooting Guide September 2005.
OmniSwitc h Troubles hooting Guide September 2005 page 2-1 2 T r oubleshooting Switched Ethernet Connectivity This chapter assume s that it h as been verified tha t the connectivity problem is across Ethernet media and the connecti on between t he non-communica ting devices is switched/bridged not ro uted (i.
Overview of Troubleshooting Appro ach Troubl eshooting Switched Ethernet Connectiv ity page 2-2 OmniSwitch Troubleshooting Guide September 2005 Over view of T roubleshooting Appr oach • Verify physical layer conne ctivity. • Verify current running co nfiguration is accurate.
Troubleshooting Switched Ethernet Connect ivity Verify Physical Layer Connectivity OmniSwitc h Troubles hooting Guide September 2005 page 2-3 V erify Physical Layer Connectivity Verify that there is valid link light along the entire da ta path be tween the device s that can not switch to each other.
Verify Physical Layer Connectivity Trouble shooting Switched Ethernet Connectivity page 2-4 OmniSwitch Troubleshooting Guide September 2005 -> show ni 5 Module in slot 5 Model Name: OS7-E NI-C24 , .
Troubleshooting Switched Ethernet Connectivity Verify Current Running Configuratio n OmniSwitc h Troubles hooting Guide September 2005 page 2-5 V erify Current Running Configuration If the physical l ayer looks OK, then verify the configuration. Use the show config uration snapsho t all to display the curren t running config uration.
Verify Source Learning Troubleshoot ing Switched Eth ernet Connectivity page 2-6 OmniSwitch Troubleshooting Guide September 2005 To further verify the ports are in the correc t VLAN and that they are in spanning tree forwarding in stead of blocking use the show v lan port command.
Troubleshooting Switched Ethernet Connectivity Verify Switch Health OmniSwitc h Troubles hooting Guide September 2005 page 2-7 V erify Switch Health If source learnin g appears to be not working correctly, verify the health o f the switch wi th the show health , and show heal th slot comman ds.
Using the Log File Troubleshooting Switched Ethernet Connectiv ity page 2-8 OmniSwitch Troubleshooting Guide September 2005 Using the Log File If none of the ab ove suggest a rea son as to why E thern.
Troubleshooting Switched Ethernet Connectivity Using the Log File OmniSwitc h Troubles hooting Guide September 2005 page 2-9 Checking the 7700/7800 Nantucket Fabric for Interrupts, Data Counts and Err.
Using the Log File Troubleshooting Switched Ethernet Connectiv ity page 2-10 OmniSwitch Troubleshooting Guide September 2005 Check for Catalina (MAC) or Por t Lockup Lab-Span1 > dshell Working: [Ke.
OmniSwitc h Troubles hooting Guide September 2005 page 3-1 3 T r oubleshooting Source Learning In order to tro ubleshoot Source Learni ng problems, a basic understanding of the process is required. A review of the “Managing Source Lear ning” chapter from the appropriate OmniSwi tch Network Configu- ration Guide is required.
Introduction Troubleshooting Source Learning page 3-2 OmniSwitch Troubleshooting Guide September 2005 Intr oduction Source Learning Example When a packet first arrives on NI so urce learning exam ines the packet and tries to classify the packet t o join its correct VLAN.
Troubleshooting Source Learning Troubl eshooting a Source Learni ng Problem OmniSwitc h Troubles hooting Guide September 2005 page 3-3 T roubleshooting a Source Learning Pr oblem In order to trou bles.
Troubleshooting a Source Learning Problem Troubleshooting Source Learning page 3-4 OmniSwitch Troubleshooting Guide September 2005 In order to na rrow down to a specific N I the followin g command ca .
Troubleshooting Source Learning Advanced Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 3-5 Once, the MA C addresses are l earned on th e ports th en the devices should be able to communicate depending on the upper layers.
Advanced Troubleshooting Troubleshooting Source Learning page 3-6 OmniSwitch Troubleshooting Guide September 2005 format text Debugs the packet text. format all Debugs the entire packet. output screen Output will ap pear on screen. output swit chlog Output will be sav ed to a log file .
Troubleshooting Source Learning Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 3-7 Dshell T roubleshooting The OmniSwitch 6/7/8XXX has a distributed archite ctur e. Source Learning is spe c ific to a NI. Each NI has a layer 2 pseudo-cam w hich is which can hold 64K entries.
Dshell Troubleshooting Troubleshooting Source Learning page 3-8 OmniSwitch Troubleshooting Guide September 2005 000001f3 Total L2 SA entry amount = 1 Both of the M AC addresses are learne d in the corre ct VLANs on the right NI.
Troubleshooting Source Learning Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 3-9 Working: [Kernel]->Sl_no_systrace=1 Sl_no_systrace = 0x56402f4: value = 1 = 0x1 Wor.
Dshell Troubleshooting Troubleshooting Source Learning page 3-10 OmniSwitch Troubleshooting Guide September 2005 OS-6600 To look at the forwarding database on OS-6600 in Dshe ll use the slcDumpSlotSlice command.
Troubleshooting Source Learning Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 3-11 L2 Physical Pool Stats: Total Used Free DstSwp Tables 16384 0 16384 NetID Tables 1638.
Dshell Troubleshooting Troubleshooting Source Learning page 3-12 OmniSwitch Troubleshooting Guide September 2005.
OmniSwitc h Troubles hooting Guide September 2005 page 4-1 4 T r oubleshooting Spanning Tr e e In order to troubleshoot spanning tree rela ted problems an understanding of the protocol and i ts features are needed. The OmniSwitc h supports two Spanni ng Tree Algo rithms; 802.
Troubleshooting Spanning Tree Troubleshooting Spanning Tree page 4-2 OmniSwitch Troubleshooting Guide September 2005 T roubleshooting Spanning T ree A failure of the Sp anning Tree Prot ocol (STP) will usually cause either a bridge loo p on the LAN or constant reconvergence of STP.
Troubleshooting Spanning Tree Troubleshooting Spanning Tree OmniSwitc h Troubles hooting Guide September 2005 page 4-3 Use the show spantree ports command to de termine if the po rt is in forwarding or bl ocking and are i n the correct VLAN. Remember that in any LAN with physical redunda ncy there must be at least one port in blocking status.
Troubleshooting Spanning Tree Troubleshooting Spanning Tree page 4-4 OmniSwitch Troubleshooting Guide September 2005 Since STP is run in a distributed fa shion it is important to verify that eac h NI that is involved is not ha ving a resource proble m.
Troubleshooting Spanning Tree Dshell OmniSwitc h Troubles hooting Guide September 2005 page 4-5 Dshell As mentioned prev iously, it is imp ortant to verify the health o f the NI as well as th e CMM. Please refer to Chapter 1, “Troubleshooting the Switch System,” fo r directi ons.
Dshell Troubleshooting Spanning Tree page 4-6 OmniSwitch Troubleshooting Guide September 2005 Working: [Kernel]->esmDumpCoronado 1,0,0x6608000+140*4,32 6608230 : 1000 1000 0 0 0 0 0 0 6608250 : 0 0.
Troubleshooting Spanning Tree Dshell OmniSwitc h Troubles hooting Guide September 2005 page 4-7 0 0 660885c : 0 0 0 0 0 0 0 0 value = 1 = 0x1 Binary: 0000 0000 001 1 For VLAN 1 the bits set are 20 3 which are equivalent t o binary 0000 0000 0011. Bit s 1 and 2 are set indi- cating that ports 1 and 2 have the span ning tree vecto r set for VLAN 1 .
Dshell Troubleshooting Spanning Tree page 4-8 OmniSwitch Troubleshooting Guide September 2005 1:0 Message age of received BPDU : 0 1:0 PIM port c state 5 1024 0 1:0 recordProposed operPointToPoin tMAC.
Troubleshooting Spanning Tree Dshell OmniSwitc h Troubles hooting Guide September 2005 page 4-9 1:0 Designated bridge ID = 80000 0d0 957962aa 1:0 Designated portId = 29697 1:0 Bridge portId = 29697 1:.
Generic Troubleshooting in Dshell Troubleshooting Spanning Tree page 4-10 OmniSwitch Troubleshooting Guide September 2005 Generic T r oubleshooting in Dshell Note. Dshell co mmands should only be used by Alcat el personnel or under th e direction of Alcatel.
Troubleshooting Spanning Tree Generic Troubleshooting in Dshell OmniSwitc h Troubles hooting Guide September 2005 page 4-11 74 - PORTDELE (2,ffffffff,ffffffff ,ffffffff) 75 - PORTATCH (2,1,ffffffff,ff.
Generic Troubleshooting in Dshell Troubleshooting Spanning Tree page 4-12 OmniSwitch Troubleshooting Guide September 2005 MODVLADM This event is receiv ed is sent by th e Spanning Tree CMM to the NIs when the admi nistrative stat e of a VLAN is changed (event generated by the VLAN Manager to the Spanning Tree CMM).
Troubleshooting Spanning Tree Generic Troubleshooting in Dshell OmniSwitc h Troubles hooting Guide September 2005 page 4-13 MDEFVLAN This event is receiv ed is sent by th e Spanning Tree C MM to the NI when t he default VLAN o f a fixed or q-tagged port is ch ange (this also a pplies to logical port).
Generic Troubleshooting in Dshell Troubleshooting Spanning Tree page 4-14 OmniSwitch Troubleshooting Guide September 2005 PORTJOIN This event is sent by Link Aggreg atio n NI when a physical port is joinin g an aggregator; It could be either a static aggregator (OmniChannel) or a dynamic a ggregator (802.
Troubleshooting Spanning Tree Generic Troubleshooting in Dshell OmniSwitc h Troubles hooting Guide September 2005 page 4-15 PTSTPMOD The is event is generated by the Spanning Tree CMM when the Spanni ng Tree configuration parameter of a port is changed by the operator.
Generic Troubleshooting in Dshell Troubleshooting Spanning Tree page 4-16 OmniSwitch Troubleshooting Guide September 2005 The Port VLAN blocking message sent to the Source Learning N I has the foll owing struct ure: uint16 VlanId, u int32 PortVecto r This event has the following values for t he message ID: • appID : APPID_SP ANNING_TREE.
Troubleshooting Spanning Tree Generic Troubleshooting in Dshell OmniSwitc h Troubles hooting Guide September 2005 page 4-17 GM2FIXED This message is sent by Group Mobili ty NI in respo nse to a BPDU on mobil e port message sent by th e Spanning Tree.
Generic Troubleshooting in Dshell Troubleshooting Spanning Tree page 4-18 OmniSwitch Troubleshooting Guide September 2005 TOPOCHGT This event notifie s a change of Sp anning Tree to pology.
Troubleshooting Spanning Tree Generic Troubleshooting in Dshell OmniSwitc h Troubles hooting Guide September 2005 page 4-19 Physical and Logical Por t Dumps Logical Ports (stpni_debugLpor t) Here follows the display of the Logical port seen by the Spanning Tree.
Generic Troubleshooting in Dshell Troubleshooting Spanning Tree page 4-20 OmniSwitch Troubleshooting Guide September 2005 The fields displa yed by th e stpni_debugLport command are described below: Ph.
Troubleshooting Spanning Tree Generic Troubleshooting in Dshell OmniSwitc h Troubles hooting Guide September 2005 page 4-21 23 0000 01a6 00000051 0000 84 ff 00:d0:95:84:3c:e1 0064 01 05 0001 01aa 0000.
Generic Troubleshooting in Dshell Troubleshooting Spanning Tree page 4-22 OmniSwitch Troubleshooting Guide September 2005 Physical and Logical Port T rac e Display (stpni_debugpor t) This is a combina tion of the Lo gical and Ph ysical port display.
Troubleshooting Spanning Tree Generic Troubleshooting in Dshell OmniSwitc h Troubles hooting Guide September 2005 page 4-23 • sockGlobal_maxmsgevt : This counter is the maximu m number of message (counter) proc essed consecutively on the Message Event Ma nager channel (inter-NI STP channel).
Generic Troubleshooting in Dshell Troubleshooting Spanning Tree page 4-24 OmniSwitch Troubleshooting Guide September 2005 Inter-NI T race (stpNI Sock_intraceprint) This trace records all the inter-NI STP events rece ived by the Socket Hand ler and has the followi ng format: • An ASCII pattern reflect ing the event.
Troubleshooting Spanning Tree Generic Troubleshooting in Dshell OmniSwitc h Troubles hooting Guide September 2005 page 4-25 CMM Spanning T ree T races Tr a c e M e n u The stpCMMSock_help Dshell command di splays the Spanni ng Tree Manager men u as shown bel ow.
Writing a PR for Spanning Tree Troubleshooting Spanning Tree page 4-26 OmniSwitch Troubleshooting Guide September 2005 W riting a PR for Spanning T ree The following su bsections desc ribe some guid elines to follow whe n writing a PR that addresses Spannin g Tree.
Troubleshooting Spanning Tree Writing a PR for Spanning Tree OmniSwitc h Troubles hooting Guide September 2005 page 4-27 Spanning T ree Unchanged When Por t State Has Changed If the show spanning tree.
Writing a PR for Spanning Tree Troubleshooting Spanning Tree page 4-28 OmniSwitch Troubleshooting Guide September 2005.
OmniSwitc h Troubles hooting Guide September 2005 page 5-1 5 T r oubleshooting BOOTP/ DHCP/UDP Relay In order to troubleshoot a BOOTP/DHCP and UDP Re lay, a basic understand ing of the pr otocol is required. Some basic concepts are covered below. The OmniSwitch supports UDP Rel ay.
Starting the Troubleshooting Procedure Troubleshooting BOOTP/DHCP/UDP Relay page 5-2 OmniSwitch Troubleshooting Guide September 2005 Use a Network Diagram It is extremely important to know where the server is in relatio n to the client, which switch both the clie nt and the server is directly conn ected to and their po rt numbers.
Troubleshooting BOOTP/DHCP/UDP Relay Starting the Troubleshooting Procedure OmniSwitc h Troubles hooting Guide September 2005 page 5-3 Preliminary 6/5/06 For ward Delay Timer Forward delay is the amou nt of time in second s UDP relay will wait before forward ing a request to a DHCP server, or the same DHCP server .
Starting the Troubleshooting Procedure Troubleshooting BOOTP/DHCP/UDP Relay page 5-4 OmniSwitch Troubleshooting Guide September 2005 UDP Relay and Group Mobility If UDP Relay is being used with a Mobile DHCP Rule, de termine if the end station is simp ly getting th e wrong IP address scope.
Troubleshooting BOOTP/DHCP/UDP Relay A dvanced Troubleshooti ng for UDP Relay OmniSwitc h Troubles hooting Guide September 2005 page 5-5 Preliminary 6/5/06 Advanced T roubleshooting for UDP Relay To monitor the UDP traffic, the debug ip packet protocol udp CLI command can be used.
Dshell Troubleshooting BOOTP/DHCP/UDP Relay page 5-6 OmniSwitch Troubleshooting Guide September 2005 Dshell To send the UDP R elay debug to th e console, fo llow the followi ng commands: Note. Dshell co mmands should only be used by Alcat el personnel or under th e direction of Alcatel.
Troubleshooting BOOTP/DHCP/UDP Relay Dshell OmniSwitc h Troubles hooting Guide September 2005 page 5-7 Preliminary 6/5/06 00 00 00 00 00 00 00 00 -- 00 00 00 00 00 00 00 63 82 53 63 35 01 03 32 04 -- .
Dshell Troubleshooting BOOTP/DHCP/UDP Relay page 5-8 OmniSwitch Troubleshooting Guide September 2005.
OmniSwitc h Troubles hooting Guide September 2005 page 6-1 6 T r oubleshooting DNS In order to troubleshoot a DNS problem, a basic unde rstanding of the protocol/feature is required .
Troubleshooting a DNS Failure Troubleshooting DNS page 6-2 OmniSwitch Troubleshooting Guide September 2005 T roubleshooting a DNS Failure Star ting the T roubleshooting Pr ocedure If you try to use DNS resolution and it does not resolv e , or connect from the switch with error such as “unknown host” take the following step s.
Troubleshooting DNS DNS Configuration Considerations OmniSwitc h Troubles hooting Guide September 2005 page 6-3 • If you find conflictin g information, then see wh ich portion has the wrong information and focus on that layer again (layer 2, 3, or 7).
DNS Configuration Considerations Troubleshooting DNS page 6-4 OmniSwitch Troubleshooting Guide September 2005.
OmniSwitc h Troubles hooting Guide September 2005 page 7-1 7 T r oubleshooting Link Aggregation In order to troublesho ot a Link Aggregatio n issue a ba sic understanding of the prot ocol is required.
Link Aggregation Limits and Guidelines Troubleshooting Link Aggregation page 7-2 OmniSwitch Troubleshooting Guide September 2005 Link Aggregation Limits and Guidelines Consider the fo llowing when con.
Troubleshooting Link Aggregation Troubl eshooting a Link Aggregation Failure OmniSwitc h Troubles hooting Guide September 2005 page 7-3 T roubleshooting a Link Aggregation Failure Link Aggregation Setup The figure above has the followin g setup: • Switch A and Switch B connect ed back to back and Link Aggregation configured.
Troubleshooting a Link Aggregation Failure Troubleshooting Link Aggregation page 7-4 OmniSwitch Troubleshooting Guide September 2005 The show linkagg port CLI command followed by the slot an d port number will d isplay the port and link state as well as if it is the primary port.
Troubleshooting Link Aggregation Troubl eshooting a Link Aggregation Failure OmniSwitc h Troubles hooting Guide September 2005 page 7-5 Source Learning When one of th e primary links g o down, the filtering databa se is purged an d the process of learning the source addresses is started again.
Troubleshooting a Link Aggregation Failure Troubleshooting Link Aggregation page 7-6 OmniSwitch Troubleshooting Guide September 2005 LACP 802.3AD Most of the steps followed pr eviously in this ch apter apply to troubl eshooting LACP. To verify the con fig- uration use the show linkag g [agg.
Troubleshoot ing Link Aggrega tion Advanc ed Link Aggregation Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 7-7 Advanced Link Aggregation T roubleshooting To verify that the link aggregate so ftware recognize s all the ava ilable slices, pe rform the following steps: Note.
Advanced Link Aggregation Troubleshooting Troubleshooting Link Aggregation page 7-8 OmniSwitch Troubleshooting Guide September 2005 MAC=00:d0:95:6b:54:0c name= primary_port_index=0 admin_state=1 o per.
Troubleshoot ing Link Aggrega tion Advanc ed Link Aggregation Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 7-9 agg_multicast_frm_tx_ok = 0 agg_broadcast_frm_tx_ok = 0 agg_uni.
6800 Link Aggregation Debug Function s Troubleshooting Link Aggregation page 7-10 OmniSwitch Troubleshooting Guide September 2005 6800 Link Aggregation Debug Functions The following functions ar e available for Link Aggregation debu gging on the NI. A summary is sh own below.
Troubleshooting Link Aggregation 6800 Link Aggregation Debug Functi ons OmniSwitc h Troubles hooting Guide September 2005 page 7-11 la_ni_port_up_pr t Certified: [Kernel]->la_ni_port_up_prt 1:0: 0 .
6800 Link Aggregation Debug Function s Troubleshooting Link Aggregation page 7-12 OmniSwitch Troubleshooting Guide September 2005 la_ni_trace_freeze Certified: [Kernel]->la_ni_trace_freeze value = .
OmniSwitc h Troubles hooting Guide September 2005 page 8-1 8 T r oubleshooting 802.1Q In order to troubleshoot an 802.1Q problem on a por t, a basic understanding of the networ king OSI model is required to assist one with the trouble shooting ste ps to resolve a particular ne twork problem.
Troubleshooting 802.1Q Troubleshooting 802.1Q page 8-2 OmniSwitch Troubleshooting Guide September 2005 T roubleshooting 802.1Q When troublesho oting an 802 .1Q problem, it is impo rtant to not only investigate the 802.1Q feature and configuration, but also the basic Et hernet connectivi ty between the problematic switches.
Troubleshooting 802.1Q Troubleshooting 802.1Q OmniSwitc h Troubles hooting Guide September 2005 page 8-3 Default VLAN T raffic If traffic that sho uld be in the defau lt VLAN is not passin g properly, fir st verify that th e default VLAN is set correctly, as see above.
Troubleshooting 802.1Q Troubleshooting 802.1Q page 8-4 OmniSwitch Troubleshooting Guide September 2005 Question : What needs to be done if the native VLAN needs to be tagged when connected t o an Omni.
Troubleshooting 802.1Q Advanced Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 8-5 Advanced T roubleshooting To verify the 802. 1Q configura tion from the CM M perspective use the de bug 802.1q CLI command. If frame type is set to all , then the egress default VLAN will eq ual the ports default VLAN.
Advanced Troubleshooting Troubleshooting 802.1Q page 8-6 OmniSwitch Troubleshooting Guide September 2005 output definitions Aggregate/Slot Status Whether the slot or aggr egate link is activel y running. Port Status Whether the port is a ctively ru nning.
Troubleshooting 802.1Q Dshell Commands OmniSwitc h Troubles hooting Guide September 2005 page 8-7 Dshell Commands The first step in troubles hooting for an 802.1Q problem throu gh Dshell is to verify t he configurations. Validating th e configurations in Dshell remo ve the chances o f inconsisten cy between the C LI and Dshell.
Dshell Commands Troubleshooting 802.1Q page 8-8 OmniSwitch Troubleshooting Guide September 2005 ON 5:0 value = 23 = 0x17 5:0 nidbg> print_default_vlan_8021 q_ni 23 5:0 5:0 print_default_vlan_8021q_.
OmniSwitc h Troubles hooting Guide September 2005 page 9-1 9 T r oubleshooting Gr oup Mobility In order to trou bleshoot a VL AN Mobility proble m, a basic u nderstanding o f the techno logy is required.
Troubleshooting a VLAN Mobility Failure Troubleshooting Group Mobility page 9-2 OmniSwitch Troubleshooting Guide September 2005 T roubleshooting a VLAN Mobility Failure There is no systematic pr ocedure to trou bleshoot a VLA N mobility issue.
Troubleshooting Group Mobility Troubleshooti ng a VLAN Mobility Failure OmniSwitc h Troubles hooting Guide September 2005 page 9-3 With VLAN mobility, it i s critical that the n etwork ad ministrator have a good understanding of the traffi c on their network i n order to assign proper rules.
Troubleshooting a VLAN Mobility Failure Troubleshooting Group Mobility page 9-4 OmniSwitch Troubleshooting Guide September 2005 Precedence Due to the variety of rules that can be configured there c an be traffic that can match mult iple rules, i.e. a n IP frame could ma tch a netw ork address rule a s well as a protocol rule.
Troubleshooting Group Mobility Advanced Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 9-5 Advanced T roubleshooting To verify if a port is a candidate for mobility as wel l as if mobility a s been turn ed on for a give n port use the debug vlan rule po rts CLI command.
Dshell Troubleshooting Group Mobility page 9-6 OmniSwitch Troubleshooting Guide September 2005 Dshell Note . Dshell command s should only be used by Alcate l personnel or under th e direction of Alcatel.
Troubleshooting Group Mobility 6800 Group Mobility Troubleshooti ng OmniSwitc h Troubles hooting Guide September 2005 page 9-7 6800 Gr oup Mobility T roubleshooting The following co mmands and debu gging functions a re available for troubleshootin g Group Mobi lity on the NI.
6800 Group Mob ility Troubleshooting Troubleshooting Group Mobility page 9-8 OmniSwitch Troubleshooting Guide September 2005 ************************************ *************** Group Mobility Help fo.
Troubleshooting Group Mobility 6800 Group Mobility Troubleshooti ng OmniSwitc h Troubles hooting Guide September 2005 page 9-9 GMC_LOG: "gmcShowRule", ht=1 bht=0 c ol=R GMC_LOG: "gmcSho.
6800 Group Mob ility Troubleshooting Troubleshooting Group Mobility page 9-10 OmniSwitch Troubleshooting Guide September 2005.
OmniSwitc h Troubles hooting Guide September 2005 page 10-1 10 T r oubleshooting QoS In order to troubleshoot Qualit y of Service (QoS), a basic unde rstanding of the concep t is required.
QoS Behavior Troubleshooting QoS page 10-2 OmniSwitch Troubleshooting Guide September 2005 QoS Behavior It is important to k now how QoS behav es by defaul t in order to un derstand the w ay it works and to be able to troubleshoo t it. So first of all , a list of default behaviors.
Troubleshooting QoS Troubleshooting QoS OmniSwitc h Troubles hooting Guide September 2005 page 10-3 On the OmniSw itch 6624/6 648, flows al ways share queue s. On the OmniSw itch 7700/78 00/8800, flo ws may share queues if they match the same policy and th e policy a ction is configur ed for sharing throug h the policy action CLI command.
Troubleshooting QoS Troubleshooting QoS page 10-4 OmniSwitch Troubleshooting Guide September 2005 QoS Apply Another common mista ke for having a po licy not work is t o forget to ap ply the QoS config uration to the configuration . Most QoS commands require a qos apply CLI command before the configuration is active.
Troubleshooting QoS Troubleshooting QoS OmniSwitc h Troubles hooting Guide September 2005 page 10-5 V iewing QoS Settings When troublesho oting, it is esse ntial to keep track of al l your QoS settings that are effective; i.
Troubleshooting QoS Troubleshooting QoS page 10-6 OmniSwitch Troubleshooting Guide September 2005 V alidation In order to va lidate the policy which are not applie d yet (pendi ng policies) or you may.
Troubleshooting QoS Troubleshooting QoS OmniSwitc h Troubles hooting Guide September 2005 page 10-7 What happens when some traffic comes in for ip destinat ion port 80? Since it does not sati sfy cond.
Troubleshooting QoS Troubleshooting QoS page 10-8 OmniSwitch Troubleshooting Guide September 2005 *IP : 192 .168.10.0 -> 0.0.0.0 *UDP : 0 -> 69 *TOS/DSCP: 0/0 Using pending l3 policies Classify .
Troubleshooting QoS Troubleshooting QoS OmniSwitc h Troubles hooting Guide September 2005 page 10-9 For example, a TFTP session in one direction will prompt a reply b ack from the host.
Troubleshooting QoS Troubleshooting QoS page 10-10 OmniSwitch Troubleshooting Guide September 2005 To view the QoS log, use the show qos log command. The displa y is similar to the following: -> sh.
Troubleshooting QoS Troubleshooting QoS OmniSwitc h Troubles hooting Guide September 2005 page 10-11 QoS Statistics The show qos statistics CLI command displays statistics about t he global QoS config.
Troubleshooting QoS Troubleshooting QoS page 10-12 OmniSwitch Troubleshooting Guide September 2005 Debug QoS Internal The CLI command debug qos internal displays debugging i nformation for Qo S internal t o the switch.
Troubleshooting QoS Troubleshooting QoS OmniSwitc h Troubles hooting Guide September 2005 page 10-13 OmniSwitch 6624/6648 Dshell T roubleshooting Note .
Troubleshooting QoS Troubleshooting QoS page 10-14 OmniSwitch Troubleshooting Guide September 2005 QVID Egress VLAN ID. A value appears in th is field if the packet is being routed to the destin ation IP address, which is the address that appea rs in the IP field.
Troubleshooting QoS Example QoS Rules OmniSwitc h Troubles hooting Guide September 2005 page 10-15 Example QoS Rules See below for the steps to create a rule for blocki ng an of fending MAC address using the CLI on the OmniSwitch. Please note the rule do es not take effect until you use the qos apply CLI command.
Example QoS Rules Troubleshooting QoS page 10-16 OmniSwitch Troubleshooting Guide September 2005 Example of a traffic shaping rule: -> qos stats interval 30 log level 7 log console -> policy condition ip_traffic2 so urce ip 192.168.10.20 -> policy action BW maximum bandwi dth 40.
OmniSwitc h Troubles hooting Guide September 2005 page 11-1 11 T r oubleshooting ARP The OmniSwitch supports Address Re solution Protoco l (ARP). In order to troubleshoot issu es related to ARP, a basic un derstanding of the protocol i s requir e d. Some basic concepts are covered in the sections below.
ARP Protocol Failure Troubleshooting ARP page 11-2 OmniSwitch Troubleshooting Guide September 2005 ARP Pr otocol Failure If device A is no t able to commu nicate with d evice B, it cou ld be a result of ARP resoluti on failure.
Troublesho oting ARP ARP Protocol Failure OmniSwitc h Troubles hooting Guide September 2005 page 11-3 When device A ARPs for the gatewa y IP address exist on the switch, an associated ARP cache e ntry is created by the switch. Thi s entry can be viewed by u sing the show arp command.
ARP Protocol Failure Troubleshooting ARP page 11-4 OmniSwitch Troubleshooting Guide September 2005 To confirm the M AC address of th e rou ting instance, use th e following command: -> show ip inte.
Troubleshooting ARP Common Error Conditions OmniSwitc h Troubles hooting Guide September 2005 page 11-5 Common Err o r Conditions If the ARP is not get ting resolved in either of the two workstations, then the following conditions may exist: • General health of the switch or NI.
Advanced ARP Troubleshooting Troubleshooting ARP page 11-6 OmniSwitch Troubleshooting Guide September 2005 Advanced ARP T r oubleshooting If the MAC addresses is a lready learned on the port an d the .
Troubleshooting ARP Advanced ARP Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 11-7 Some devices may be silent like pri nters. They ARP at the time of the bootup but after t hat they do not ARP at all. In order to accommoda te those devices Omni Switch allows different choi ces: • To increase the ARP time out value.
Dshell Troubleshooting Troubleshooting ARP page 11-8 OmniSwitch Troubleshooting Guide September 2005 Dshell T roubleshooting In order to troubleshoot ARP cache make sure all th e steps mentioned in the earlier sections have been taken. Dshell should be use d when no more erro r collection ca n be done from the CLI and debug CLI.
Troublesho oting ARP Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 11-9 10.40.212.3 00:d0:95:6b:4c: e9 300 0x0 1948275 0 405 0 0 212 10.40.212.4 00:d0:95:7c:7d: 78 300 0x0 1946929 0 405 0 0 212 10.40.212.12 7 08:00:20:b0:ea: d1 300 0x0 1948092 0 405 0 0 212 10.
Dshell Troubleshooting Troubleshooting ARP page 11-10 OmniSwitch Troubleshooting Guide September 2005 V iewing the ARP T able on OmniSwitch 6624/6648 Switches To look at th e ARP tab le on OS-6600 u se the foll owing command in Dshell: Working: [Ke rnel]->ipn i_arpShow Slot 2.
OmniSwitc h Troubles hooting Guide September 2005 page 12-1 12 T r oubleshooting IP Routing In order to trou bleshoot an IP Rout ing problem, a basic un derstanding of t he IP protoco l/feature is required.
In This Chapter Troublesh ooting IP Rou ting page 12-2 OmniSwitch Troubleshooting Guide September 2005 In This Chapter “Introduction ” on page 12-3 “IP Routing Prot ocol Failure” on page 12 -3.
Troublesh ooting IP Rou ting Introduction OmniSwitc h Troubles hooting Guide September 2005 page 12-3 Intr oduction The primary func tion of IP Routing is processing Lay e r 3 IP packets and forwardi ng them in between two different networks or subnets .
Troubleshooting via the CLI Troubleshooting IP Routing page 12-4 OmniSwitch Troubleshooting Guide September 2005 ..... 4/19 default inactive 4/20 default inactive 4/21 default inactive 4/22 default forwarding 4/23 default inactive .
Troublesh ooting IP Rout ing Troublesh ooting via the CL I OmniSwitc h Troubles hooting Guide September 2005 page 12-5 domainName : nameServer(s): Verify that the switc h has a valid route to the dest.
Troubleshooting via the CLI Troubleshooting IP Routing page 12-6 OmniSwitch Troubleshooting Guide September 2005 Destination unreachable 201 15 Time exceeded 0 0 Parameter problem 0 0 Source quench 0 .
Troublesh ooting IP Rout ing Troublesh ooting via the CL I OmniSwitc h Troubles hooting Guide September 2005 page 12-7 Multicast packets sent = 0, Broadcast packets received = 51008 , Broadcast packet.
Troubleshooting via the CLI Troubleshooting IP Routing page 12-8 OmniSwitch Troubleshooting Guide September 2005 The show udp statistics command displays UDP errors and stat istics.
Troublesh ooting IP Rout ing Troublesh ooting via the CL I OmniSwitc h Troubles hooting Guide September 2005 page 12-9 The show ip config command displays IP configuratio n on the switch: -> show ip config IP directed-broadcast = ON, IP default TTL = 64 There are us er-config urable pa rameters that can be change d as per re quirement.
Troubleshooting via the CLI Troubleshooting IP Routing page 12-10 OmniSwitch Troubleshooting Guide September 2005 10.1.99.0/24 192.168.60.2 OSPF 1 60 10.1.99.0/24 192.168.61.2 OSPF 1 61 10.1.99.0/24 192.168.62.2 OSPF 1 62 10.11.5.0/24 10.11.5.2 LOCAL 1 511 10.
Troubleshooting IP Routing Troubleshooting with Debug CLI OmniSwitc h Troubles hooting Guide September 2005 page 12-11 T roubleshooting with Debug CLI As always, being able to obta in a tr ace of t he traffic via a Sn iffe r applicat ion will tell y ou the botto m line.
Troubleshooting with Debug CLI Troubleshooting IP Routing page 12-12 OmniSwitch Troubleshooting Guide September 2005 ip-addres s Specifies an IP address to debug. The debug o utput will only be for packets received from this IP a ddress. Enter ip-address, then enter the IP address that you want to debug.
Troublesh ooting IP Rou ting RIP Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 12-13 RIP T roubleshooting The following comman ds are used to trou bleshoot RIP failures: show .
RIP Trouble shooting Troubleshootin g IP Routin g page 12-14 OmniSwitch Troubleshooting Guide September 2005 11.40.150.1 6 enabled enabled 0/0(0) The interface is enabled.
Troublesh ooting IP Rou ting RIP Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 12-15 10.10.42.159 255.255.255.255 11.41.211.1 2 11.40.117.0 255.255.255.0 11.40.211.1 2 11.40.150.0 255.255.255.0 11.40.150.1 1 11.40.211.0 255.255.
RIP Trouble shooting Troubleshootin g IP Routin g page 12-16 OmniSwitch Troubleshooting Guide September 2005 error Includes error conditions, fail ure s, processing errors, etc. warning Includes general warnings , non-fatal condi tions. recv Enables debugging in the receive flow path of th e code.
Troublesh ooting IP Rou ting RIP Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 12-17 tRip-: Adding 11.40.1.0/24->11.40.211.1 to FIB tRip-: in ripRdbLookup for 11.40.117.0 (255.255.255.0) tRip-: Adding 11.40.117.0/24->11.
RIP Trouble shooting Troubleshootin g IP Routin g page 12-18 OmniSwitch Troubleshooting Guide September 2005 tRip-: in ripRdbLookup for 10.0.0.0 (25 5.0.0.0) tRip-: ripSupply: Adding tuple(4) dst=10.10.41.57 mask=0.0.0.0 gw=0.0.0.0 met=16 tRip-: ripSupply: Forcing metric for 10 .
Troubleshooting IP Routing OSPF Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 12-19 OSPF T roubleshooting The following comman ds are used to trouble shoot OSPF failures: show ip ospf interface x.
OSPF Troubleshooting Troubleshooting IP Routing page 12-20 OmniSwitch Troubleshooting Guide September 2005 # of Init State Neighbors = 0, # of Exchange State Neighbors = 0, # of Full State Neighbors = 0 This interface has bee n assigned to area 0.0.0.
Troubleshooting IP Routing OSPF Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 12-21 External LSDB Limit = 0, Exit Overflow Interval = 0, # of SPF calculations done = 0, # of I.
OSPF Troubleshooting Troubleshooting IP Routing page 12-22 OmniSwitch Troubleshooting Guide September 2005 0.0.0.0 sumnet 10.40.0.0 192.168.50.4 0x800000 02 5 0.0.0.5 rtr 11.40.211 .1 11.40.211.1 0x800000 41 6 0.0.0.5 rtr 11.41.211 .1 11.41.211.1 0x800000 33 6 0.
Troubleshooting IP Routing OSPF Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 12-23 192.168.54.0 10.26.0.1 0x80 000032 123 OSPF 192.168.55.0 10.26.0.1 0x80 000032 123 OSPF 192.168.56.0 10.26.0.1 0x80 000032 123 OSPF 192.168.57.
OSPF Troubleshooting Troubleshooting IP Routing page 12-24 OmniSwitch Troubleshooting Guide September 2005 If local, stat ic, or any other ex ternal protoc ol routes need to be redistributed into OSPF then the first step is to make that OSPF router to be a AS Border Router.
Troubleshooting IP Routing OSPF Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 12-25 send Administratively e nables/ disables debugging messa ges for packets sent by OSPF only. flood Administrati vely enables/disables debu gging messages for the fl ooding of Link State Advertisements (LSAs) in OSPF only.
OSPF Troubleshooting Troubleshooting IP Routing page 12-26 OmniSwitch Troubleshooting Guide September 2005 Let’s look at all t he messages that appear on the console during the setup of OSPF adjacency.
Troubleshooting IP Routing BGP Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 12-27 tOspf-: ospfNbrStateMachine: (10.40.110.3) Change! PREV LOADING; EVENT LOAD- DONE; NEXT FULL. (Loading of the LSAs done , spf calculations bein g done and the routes are gettin g loaded in the route table.
BGP Troubleshooting Troubleshooting IP Routing page 12-28 OmniSwitch Troubleshooting Guide September 2005 -> show ip bgp neighbors statistic s 152.23.
Troublesho oting IP Routin g Ds hell Tr oubleshooting Advanced IP Routing OmniSwitc h Troubles hooting Guide September 2005 page 12-29 Dshell T roubleshooting Advanced IP Routing The following Dshell command s are used to troubleshoot advanced IP routing.
Dshell Troubleshooting Advanced IP Routing Troubleshooting IP Routing page 12-30 OmniSwitch Troubleshooting Guide September 2005 Internet address: 127.
Troublesho oting IP Routin g Ds hell Tr oubleshooting Advanced IP Routing OmniSwitc h Troubles hooting Guide September 2005 page 12-31 1:0 1:0 fe7 vlan180.
Dshell Troubleshooting Advanced IP Routing Troubleshooting IP Routing page 12-32 OmniSwitch Troubleshooting Guide September 2005 sessionId = 0 spfCount = 97 incrSpfCount = 0 ageTimer = 180 ageTicks = 61 ***Dumping myConfig contents*** cfg.flags = 0x223 cfg.
Troublesho oting IP Routin g Ds hell Tr oubleshooting Advanced IP Routing OmniSwitc h Troubles hooting Guide September 2005 page 12-33 redistTable[5] = 0x0 redistTable[6] = 0x0 redistTable[7] = 0x0 *r.
Dshell Troubleshooting Advanced IP Routing Troubleshooting IP Routing page 12-34 OmniSwitch Troubleshooting Guide September 2005.
OmniSwitc h Troubles hooting Guide September 2005 page 13-1 13 T r oubleshooting V ir tual Router Redundancy Pr otocol (VRRP) In This Chapter “Protocol Information” on page 13-3 “OmniSwitch 7700.
Overview Troubleshooting Virtual Rou ter Redundancy Protocol (VRRP ) page 13-2 OmniSwitch Troubleshooting Guide September 2005 Over view VRRP specifies an elec tion protocol . All protocol me ssaging (not user data) is performed using IP multi- cast datagrams.
Troubleshooting Virtual Router Redundancy Protoc ol (VRRP) Protocol Information OmniSwitc h Troubles hooting Guide September 2005 page 13-3 Pr otocol Information This next section describes ho w VRRP routers exchange informat ion. IP Field Descriptions Source Address The primary address of the interfac e th e packet is bein g sent from.
OmniSwitch 7700/7800 /8800 Implementation Troubleshoot ing Virtua l Router Redundancy Protocol (VRRP ) page 13-4 OmniSwitch Troubleshooting Guide September 2005 OmniSwitch 7700/7800/8800 Implementation This section will cov er how and what th e OmniSwitch 7700 /7800/8800s wi ll support.
Troubleshooting Virtual Router Redund ancy P rotocol (VRRP) CMM Failover OmniSwitc h Troubles hooting Guide September 2005 page 13-5 CMM Failover When the CMM receives a Takeover message from the Ch assis Supervisor it will first inform ARP to purge all entries for the virt ual router IP/Mac addresses.
CMM Failover Troubleshooting Virtual Router Redundancy Pro tocol (VRRP) page 13-6 OmniSwitch Troubleshooting Guide September 2005 show vrrp statistics Displays statistics about VRRP pack ets for all virtual rout er s configured o n the switch or for a particular virtual router.
Troubleshooting Virtual Router Redund ancy P rotocol (VRRP) CMM Failover OmniSwitc h Troubles hooting Guide September 2005 page 13-7 -> show vrrp 1 statistics Virtual Router VRID = 1 on VLAN = 1 St.
CMM Failover Troubleshooting Virtual Router Redundancy Pro tocol (VRRP) page 13-8 OmniSwitch Troubleshooting Guide September 2005 Release History Release 5.1; command was introd uced. Authentication type errors The total number of VRRP packets receiv ed in which the Aut hT ype value was dif ferent than the one co nfigured for the virtual router .
Troubleshooting Virtual Router Redundancy Prot ocol (VRR P) OmniSwitch VRRP Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 13-9 OmniSwitch VRRP T roubleshooting The following c.
ARP Table Troubleshooting Virtual Rou ter Redundancy Protocol (VRRP) page 13-10 OmniSwitch Troubleshooting Guide September 2005 ARP T able The ARP Table of the OmniSwitch that is the Master Route r will have the Virtual MAC Learne d in the ARP Table. It wi ll not be learn ed on a port.
Troubleshooting Virtual Router Redundancy Protocol (VRR P) Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 13-11 Dshell T roubleshooting In a situation where VRRP is flapping, go into Dshell of the swi tch that is config ured as the back up virtual router that is flapping and enter vrrpTMon(1, vrid, vlanId ) .
Dshell Troubleshooting Troubleshooting Virt ual Router Redundancy Protocol (VRRP) page 13-12 OmniSwitch Troubleshooting Guide September 2005.
OmniSwitc h Troubles hooting Guide September 2005 page 14-1 14 T r oubleshooting IP Multicast Switching (IPMS) In order to trou bleshoot IP Multica st Switching, a ba sic understanding of its funct ion is required. Some basic concepts are covered below.
Troubleshooting IP Multicast Switching (IPMS) Troubleshoot ing a Device that Cannot Join an IP Multicast Stream OmniSwitc h Troubles hooting Guide September 2005 page 14-2 T roubleshooting a Device th.
Troubleshooting IP Multicast Switching (IPMS) Troubleshoot ing a Device that Drops Out of an IP Multicast Stream OmniSwitc h Troubles hooting Guide September 2005 page 14-3 T roubleshooting a Device t.
Troubleshooting IP Multicast Switching (IPMS) Troubleshoot ing a Device that Drops Out of an IP Multicast Stream OmniSwitc h Troubles hooting Guide September 2005 page 14-4 Is Multicast Switchi ng ena.
Troubleshooting IP Multicast Switching (IPMS) Troubleshoot ing a Device that Drops Out of an IP Multicast Stream OmniSwitc h Troubles hooting Guide September 2005 page 14-5 OmniSwitch Netwo rk Configuratio n Guide .
Troubleshooting IP Multicast Switching (IPMS) Troubleshoot ing a Device that Drops Out of an IP Multicast Stream OmniSwitc h Troubles hooting Guide September 2005 page 14-6 You may also have a misconfigured or malfunct ioning ip multic ast static-querier.
Troubleshooting IP Multicast Switching (I PMS) Troubleshooting IPMS in Debug CLI OmniSwitc h Troubles hooting Guide September 2005 page 14-7 T roubleshooting IPMS in Debug CLI The Debug CLI will all ow you to view traffic traver sing the switch in many ways.
Troubleshooting IP Multicast Switching (I PMS) Troubleshooting IPMS in Debug CLI OmniSwitc h Troubles hooting Guide September 2005 page 14-8 Note the output of the show ip multicas t queriers command during this test: -> show ip multicast queriers Source IP VLAN Slot/Port Expire Ty pe --------------------+----+-------- -+------+------- 10.
Troubleshooting IP Multicast Switching (IPMS) Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 14-9 Dshell T roubleshooting The IPMS application has its own shell to verify the spec ific data displayed on the CLI. Use a qu estion mark to display the lo cal list of commands for each level.
Troubleshooting IP Multicast Switching (IPMS) Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 14-10 grp - Group Membership nbr - Neighbors qry - Queriers src - Sources pr.
Troubleshooting IP Multicast Switching (IPMS) Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 14-11 IPMEM> src Hash Multicast Source IP/ Multicast Dest IP VLAN VPN TYP EXP RTY P kt Cnt INDX Unicast Source IP ==== ==================== ========== ========== ==== === === === === = ====== 0291 172.
Troubleshooting IP Multicast Switching (IPMS) Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 14-12 MAIN> ? Main Menu main - Main Menu clist - Display Sub-tasks restar.
Troubleshooting IP Multicast Switching (IPMS) Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 14-13 IPMFM> dst HASH Destination IP VLAN VPN VCI TYPE ID ==== ==================== ==== === = === ========== ==== 0000 0.0.
Troubleshooting IP Multicast Switching (IPMS) Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 14-14 1:0 menu route - 0x4 1:0 menu cmm - 0x8 1:0 1:0 alarm - 0x8 1:0 error .
Troubleshooting IP Multicast Switching (IPMS) Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 14-15 1:0 1:0 create - 0 1:0 enqueue - 0 1:0 global drop - 0 1:0 flow drop -.
Troubleshooting IP Multicast Switching (IPMS) Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 14-16.
Troubleshooting IP Multicast Switching (IPMS) Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 14-17.
Troubleshooting IP Multicast Switching (IPMS) Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 14-18.
Troubleshooting IP Multicast Switching (IPMS) Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 14-19.
Troubleshooting IP Multicast Switching (IPMS) Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 14-20.
OmniSwitc h Troubles hooting Guide September 2005 page 15-1 15 T r oubleshooting DVMRP In This Chapter “Introducti on” on page 15-2 “DVMRP Trou bleshootin g” on page 1 5-2 “DVMRP Global and .
Introduction Troublesh ooting DVM RP page 15-2 OmniSwitch Troubleshooting Guide September 2005 Intr oduction DVMRP is used t o route Multica st packets thro ugh di fferen t IP Networks. This is a Dense Mode Multi- cast Routing Pro tocol. Dense M ode refers to the network environment the protocol was desig ned to service.
Troubleshooting DVMRP DVMRP Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 15-3 Route Timeout = 140, Number of Routes = 6, Number of Reachable Routes = 6 -> show ip dvmrp interface Address Vlan Tunnel Metric Admin-Status Oper-Status -----------------+------+--------+ --------+---------------+-------- ----- 192.
DVMRP Troubleshooting Troubleshooting DVMRP page 15-4 OmniSwitch Troubleshooting Guide September 2005 192.168.10.1 1 No 1 Enabled Enabled 192.168.11.1 2 No 1 Enabled Enabled 192.168.12.1 3 No 1 Enabled Enabled Remote rout es will be see n if they ar e learned fro m another swit ch.
Troubleshooting DVMRP DVMRP Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 15-5 The third command turns on the debug l evel. The low is 0, which is no debugg ing at all, and the high is 110, which prints every thing to th e screen.
DVMRP Troubleshooting Troubleshooting DVMRP page 15-6 OmniSwitch Troubleshooting Guide September 2005 tDvmrp-: dvmrpRibRemoveHoldDown: 192.168.11.0-255.255. 255.0 tDvmrp-: dvmrpRibDelinkHoldDownQ: 192.168.11.0-255.255 .255.0 tDvmrp-: dvmrpInitChildAndSubs: All V1 nbrs dependent on us for rt 192.
Troubleshooting DVMRP DVMRP Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 15-7 tDvmrp-: #subords=0, pruncnt=0 tDvmrp-: Looking at V1... tDvmrp-: V1 not sub/nbr tDvmrp-: Looking at V2... tDvmrp-: V2 not sub/nbr tDvmrp-: V2 not rib->upstrVl=1, may need forwarding tDvmrp-: Group 224.
DVMRP Troubleshooting Troubleshooting DVMRP page 15-8 OmniSwitch Troubleshooting Guide September 2005 tDvmrp-: IGMP packet from 192.168.10.1 tDvmrp-: IGMP packet from 192.168.11.1 tDvmrp-: IGMP packet from 192.168.12.1 tDvmrp-: IGMP packet from 192.168.
Troubleshooting DVMRP DVMRP Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 15-9 tDvmrp-: IGMP packet from 192.168.10.1 tDvmrp-: IGMP packet from 192.168.10.1 tDvmrp-: IGMP packet from 192.168.10.1 tDvmrp-: IGMP packet from 192.
DVMRP Troubleshooting Troubleshooting DVMRP page 15-10 OmniSwitch Troubleshooting Guide September 2005 tDvmrp-: Found S,G matching source network 255.255.255 .0 tDvmrp-: Creating a new prune state S,G 192.168.10.25 224.2.142.227 tDvmrp-: V3 time:218 Nbr :192.
Troubleshooting DVMRP DVMRP Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 15-11 tDvmrp-: V3 is a sub/nbr, numFwdIfs=2 tDvmrp-: V3 not rib->upstrVl=1, may need forwarding tDvmrp-: Group 224.
DVMRP Troubleshooting Troubleshooting DVMRP page 15-12 OmniSwitch Troubleshooting Guide September 2005 tDvmrp-: Metric orig=32, adj=32 tDvmrp-: dvmrpUpdateUnreachable: tDvmrp-: Nbr[192.168.11.2] no longer a subordinate for rt 192.168.10.0 tDvmrp-: dvmrpUpdateUnreachable Nbr[192.
Troubleshooting DVMRP DVMRP Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 15-13 tDvmrp-: dvmrpUpdateRoute: V2 UPDATE route for 192.
DVMRP Troubleshooting Troubleshooting DVMRP page 15-14 OmniSwitch Troubleshooting Guide September 2005 tDvmrp-: #subords=0, pruncnt=0 tDvmrp-: Looking at V1... tDvmrp-: V1 not sub/nbr tDvmrp-: V1 not rib->upstrVl=2, may need forwarding tDvmrp-: Group 224.
Troubleshooting DVMRP DVMRP Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 15-15 tDvmrp-: dvmrpUpdatePoisoned: nbr 192.168.12 .3 is dependent on us for rt 192.168.13.0 tDvmrp-: dvmrpComputeForwardingVectorForRoute: call it ... tDvmrp-: dvmrpComputeForwardingVector : tDvmrp-: For rt 192.
DVMRP Troubleshooting Troubleshooting DVMRP page 15-16 OmniSwitch Troubleshooting Guide September 2005 tDvmrp-: Group 224.2.178.69 not learned on V1 tDvmrp-: Looking at V2... tDvmrp-: V2 not sub/nbr tDvmrp-: Looking at V3... tDvmrp-: V3 is a sub/nbr, numFwdIfs=1 tDvmrp-: V3 not rib->upstrVl=2, may need forwarding tDvmrp-: Group 224.
Troubleshooting DVMRP DVMRP Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 15-17 -> tDvmrp-: dvmrpRecvIpmrmDelEntry: V2 S,G 192.
DVMRP Troubleshooting Troubleshooting DVMRP page 15-18 OmniSwitch Troubleshooting Guide September 2005 tDvm-> rpshow -: Metric or ig=1, adj=2 tDvmrp-: dvmrpUpdateReachable: tDvmrp-: dvmrpRibResetAgeoutTimer: -> show ip dvmrp route tDvmrp-: dvmrpRecvReport: tDvmrp-: dvmrpUpdateRoute: V2 UPDATE route for 192.
Troubleshooting DVMRP DVMRP Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 15-19 tDvmrp-: V1, GW 0.0.0.0, PruneSent 0 tDvmrp-: V2 (forward on) tDvmrp-: Forward on 0 tunnels tDvmrp-: dvmrpUpdateRoute: V2 UPDATE route for 192.168 .
DVMRP Troubleshooting Troubleshooting DVMRP page 15-20 OmniSwitch Troubleshooting Guide September 2005 100| 172.100.1.25| 255.255.255. 0| 1| 0| 515| 172.
OmniSwitc h Troubles hooting Guide September 2005 page 16-1 16 T r oubleshooting PIM-SM In order to troubleshoot iss ues related to Protocol Independent Multicast-Sparse M ode (PIM-SM), a basic understanding of the protocol—as well as IP multic ast technology—are required .
Introduction Troubleshooting PIM-SM page 16-2 OmniSwitch Troubleshooting Guide September 2005 Intr oduction Traditional multicast routing prot ocols like DVMRP, MOSPF or PIM-DM were implemented to provide multicast routing in campus network .
Troublesh ooting PIM-SM Protocol Overview OmniSwitc h Troubles hooting Guide September 2005 page 16-3 Pr otocol Over view DR Election Hello messages are sent periodically bet ween PIM neighb ors. This informs routers wh ich interface has PIM neighbors.
Protocol Overview Tr oubleshooting PIM-SM page 16-4 OmniSwitch Troubleshooting Guide September 2005 PIM: ----- PIM Header ----- PIM: PIM: Version = 2 PIM: Message Type = 0 (Hel lo) PIM: Reserved = 0 P.
Troublesh ooting PIM-SM Protocol Overview OmniSwitc h Troubles hooting Guide September 2005 page 16-5 Related CLI Command To view if a PIM router interface is the DR for the LAN segment, enter the fol.
BSR Election Troubleshooting PIM-SM page 16-6 OmniSwitch Troubleshooting Guide September 2005 BSR Election Candidates-BSR sends Bootstrap me ssages within it s PIM-SM dom ain.
Troublesh ooting PIM-SM BSR Election OmniSwitc h Troubles hooting Guide September 2005 page 16-7 Simplified Packet Format IP: ----- IP Header ----- IP: Protocol = 103 (P IM) IP: Source address = [1 92.
BSR Election Troubleshooting PIM-SM page 16-8 OmniSwitch Troubleshooting Guide September 2005 The router selects itself as initial BSR . tPimsm-: Received bootstrap message from 192.168.11.1, bsr addr:192.168.11.1 on vlan 1 tPimsm-: Ignoring less pref erred bsr 192.
Troublesh ooting PIM-SM BSR Election OmniSwitc h Troubles hooting Guide September 2005 page 16-9 Related CLI Command To view which routers are assuming the ro le of the BSR, e xpiry ti me, C-BSR address, and C-BSR prior- ity, type : -> show ip pimsm Status = enabl ed, BSR Address = 192.
C-RP Advertis ements Troubleshooting PIM-SM page 16-10 OmniSwitch Troubleshooting Guide September 2005 C-RP Adver tisements Candidate-RPs advertisements are pe riodically unicast from the C -RP to the BSR.
Troublesh ooting PIM-SM C-RP Advertisements OmniSwitc h Troubles hooting Guide September 2005 page 16-11 PIM: ----- PIM H eader ----- PIM: Version = 2 PIM: Message Type = 8(Candida te-RP-Ad vertisemen.
C-RP Advertis ements Troubleshooting PIM-SM page 16-12 OmniSwitch Troubleshooting Guide September 2005 Another output from a C-RP advertis ement, advertises itself for all multicast groups. All group add resses are represented by the pair 224.0.0 .0 240.
Troublesh ooting PIM-SM RP-SET OmniSwitc h Troubles hooting Guide September 2005 page 16-13 RP-SET An RP-SET contain s a set of Candi d ates-RP IP addresses that want to participate as RP for mul ticast group. The RP-SET i s derived from the C RP-Adverti sements received by the BSR.
RP-SET Troubleshooting PIM-SM page 16-14 OmniSwitch Troubleshooting Guide September 2005 Simplified Bootstrap RP-SET Packet T aken on a 192.168.12/24 Network IP: ----- IP Header ----- IP: Version = 4, head er length = 20 by tes IP: Protocol = 103 (PIM) IP: Source address = [192.
Troublesh ooting PIM-SM RP-SET OmniSwitc h Troubles hooting Guide September 2005 page 16-15 PIM: RP1-Holdtime = 150 (in seconds) PIM: RP1-Priority = 0 PIM: Reserved = 0 PIM: PIM: *** Encoded-Group Add.
RP-SET Troubleshooting PIM-SM page 16-16 OmniSwitch Troubleshooting Guide September 2005 PIM: *** Encoded-Unicast RP Address # 1 *** PIM: Address fami ly = 1 (IP (IP version 4)) PIM: En codi ng type = 0 PIM: Unicast address = [192.
Troublesh ooting PIM-SM RP-SET OmniSwitc h Troubles hooting Guide September 2005 page 16-17 Related CLI Command To View RP-SET on a router, use the show ip pimsm rp-set command. For exampl e: -> show ip pimsm rp-set Group Address Address Holdtime Expires ------------------+--------------- +--------+----------- 225.
Join/Prune Troubleshooting PIM -SM page 16-18 OmniSwitch Troubleshooting Guide September 2005 Join/Prune Join/Prune messages a re sent by the DR to join or pru ne a branch off the multicast di stribution tree in order to receive multicas t group on a speci fic LAN segment that has active grou p members.
Troublesh ooting PIM-SM Join/Prune OmniSwitc h Troubles hooting Guide September 2005 page 16-19 PIM: ----- PIM H eader ----- PIM: PIM: Version = 2 PIM: Message Type = 3(Join/Prune ) PIM: Reserved = 0 .
Join/Prune Troubleshooting PIM -SM page 16-20 OmniSwitch Troubleshooting Guide September 2005 PIM: .... ..1. = WC bit - join / prune applies to the (*,G) or (*,*, RP) entry PIM: .... ...1 = RPT-bit - info rmation about (S, G) is sent towards the RP PIM: Mask length = 32 PIM: Source address = [192.
Troublesh ooting PIM-SM Register OmniSwitc h Troubles hooting Guide September 2005 page 16-21 Register When a source starts tr ansmitting to a multicast g roup, the DR on the segment encapsulates the data a nd sends it as unicast to the RP re presenting the g roup.
Register Troubleshooting PIM-SM page 16-22 OmniSwitch Troubleshooting Guide September 2005 Simplified REGISTER Packet Format IP: ----- IP Header ----- IP: Source address = [192.
Troublesh ooting PIM-SM Shared Tree OmniSwitc h Troubles hooting Guide September 2005 page 16-23 Shared T ree A shared distribu tion tree is formed a round the RP, fr om which a ll traffic is distribut ed regardless of the location of the traffic sour ces.
Shared Tr ee Troubleshooting PIM-SM page 16-24 OmniSwitch Troubleshooting Guide September 2005 Related CLI Command In order to view the IP multicast routing tab le as well as source and distribution t.
Troublesh ooting PIM-SM Source-Based Tree OmniSwitc h Troubles hooting Guide September 2005 page 16-25 Source-Based T ree PIM SM protocol allows a D R to build a Shortest Path Tree, which could provide a shortest pat h toward the source. It is being referenced as Source Based Tree because t he DR closest to t he receiver is initiating the process.
Source-Based Tree Troubleshooting PIM-SM page 16-26 OmniSwitch Troubleshooting Guide September 2005 Related CLI Command To view the distri bu tion tree issue: -> show ip pimsm mroute Group Address Src Address Assert Assert Assert Flags Metric expires Pref ---------------+------------------ +------+-----------+------+----- 225.
Troubleshooting PIM-SM Troubleshooting Examples: Limitations OmniSwitc h Troubles hooting Guide September 2005 page 16-27 T roubleshooting Examples: Limitations Incorrect BSR ID Turn on BSR debugg ing to view bootstrap messages: -> ip pimsm debug-type bootstrap -> ip pimsm debug-level 100 tPimsm-: Received bootstra p message from 192.
Troubleshooting Examples: Limita tions Troubleshooting PIM -SM page 16-28 OmniSwitch Troubleshooting Guide September 2005 -> show ip pimsm Status = enabl ed, BSR Address = 192.1 68.13.1, BSR Expiry Time = 00h:0 1m:43s, CBSR Address = 0.0.0 .0, CBSR Mask Length = 30, CBSR Priority = 0, CRP Address = 192.
Troubleshooting PIM-SM Troubleshooting Examples: Limitations OmniSwitc h Troubles hooting Guide September 2005 page 16-29 -> debug ip pimsm rp Group Address RP Address ------------------+--------------- --- 224.0.1.22 172.100.1.254 224.0.1.24 172.100.
Troubleshooting Examples: Limita tions Troubleshooting PIM -SM page 16-30 OmniSwitch Troubleshooting Guide September 2005.
OmniSwitc h Troubles hooting Guide September 2005 page 17-1 17 T r oubleshooting Ser ver Load Balancing In order to successfully troublesh o ot the Alcat el Server Load Balancin g feature, a brief underst anding of this services func tions are necessary.
Introduction Troubleshooting Server Load Balancing page 17-2 OmniSwitch Troubleshooting Guide September 2005 Intr oduction The primary func tion of a Se rver Load Balan ce cluster is to provide a metho d to logical ly treat a group of physical servers (known as a serv er farm) as one large v irtual se rver (known as an SLB cluster).
Troubleshooting Server Load Balancing Troubleshooting Commands OmniSwitc h Troubles hooting Guide September 2005 page 17-3 T roubleshooting Commands Below is a list o f commands, which will be used and discussed in this chapter.
Troubleshooting a Complete Failure Tro ubleshooting Server Load Balancing page 17-4 OmniSwitch Troubleshooting Guide September 2005 T roubleshooting a Complete Failure Gathering pert inent information is essential in order t o properly charact erize the prob lem.
Troubleshooting Server Load Balanc ing Troubleshooting a Partial Failure OmniSwitc h Troubles hooting Guide September 2005 page 17-5 T roubleshooting a Partial Failure The number one cause of a partial failure is miscon figuratio n. In the following area, we will sho w you how to determine the SLB configurati on.
The Troubleshooting Procedure Troub leshooting Server Load Balancing page 17-6 OmniSwitch Troubleshooting Guide September 2005.
OmniSwitc h Troubles hooting Guide September 2005 page 18-1 18 T r oubleshooting Authenticated VLANs In order to troublesho ot Authenticated VLAN (AV LAN), a basic understa nding of how authen tication works in the switch is requir ed. Understandin g of Radi us and DHCP server wil l be useful in trou bleshoot- ing Authenticate d VLAN.
Troubleshooting AVLAN Troubleshooting Authenticated VLANs page 18-2 OmniSwitch Troubleshooting Guide September 2005 T roubleshooting A VLAN DHCP Request Failure If the client (PC -1) is configur ed to.
Troubleshooting Authenticate d VLANs Troubleshooting AVLAN OmniSwitc h Troubles hooting Guide September 2005 page 18-3 192.168.10.100 00:c0:4f:0c:3a: e4 DYNAMIC 1/21 vlan 2 There are couple s of other things y ou can verify is on the DHCP server itself.
Troubleshooting AVLAN Troubleshooting Authenticated VLANs page 18-4 OmniSwitch Troubleshooting Guide September 2005 -> show mac-address-table Legend: Mac Address: * = address n ot valid Vlan Mac Ad.
Troubleshooting Authenticated VLANs T roubleshooting Using Debug Systrace OmniSwitc h Troubles hooting Guide September 2005 page 18-5 Useful Notes on Client Issues • If using telnet authentication manual IP release and renew required ge tting the n ew IP after authentic a- tion.
Troubleshooting Using Debug Systrace Troubleshooting Authenticated VLANs page 18-6 OmniSwitch Troubleshooting Guide September 2005 Initiate the T elnet Authentication -> 2394037098 AAA debug1 Send .
Troubleshooting Authenticated VLANs T roubleshooting Using Debug Systrace OmniSwitc h Troubles hooting Guide September 2005 page 18-7 Chal_Rsdebug3p link, set in No li nkEntering in aaaAvlanAuthRspOK2.
Troubleshooting Using Debug Systrace Troubleshooting Authenticated VLANs page 18-8 OmniSwitch Troubleshooting Guide September 2005 chaddr=00:90:27:75:dc:a2 2476995124 AAA debug2 sname=<>f ile=&l.
Troubleshooting Authenticated VLANs T roubleshooting Using Debug Systrace OmniSwitc h Troubles hooting Guide September 2005 page 18-9 name : admin, Rec(TRUNCATED) 2165965890 AAA debug3 Entering in aaa.
Troubleshooting Using Debug Systrace Troubleshooting Authenticated VLANs page 18-10 OmniSwitch Troubleshooting Guide September 2005 AV C l i e n t A VClient Authentication Start -> 1592327563 AAA debug3 XCAP r ec.
Troubleshooting Authenticated VLANs T roubleshooting Using Debug Systrace OmniSwitc h Troubles hooting Guide September 2005 page 18-11 1595408715 AAA info [RAD] rad _buildauth: port 1 added to acces s.
Dshell Troubleshooting Troubleshooting Authenticated VLANs page 18-12 OmniSwitch Troubleshooting Guide September 2005 1628234512 AAA debug3 aaaHdlUti lBufInNormalList, free Id 1088026 64, typ 8 162823.
Troubleshooting Authenticated VLANs Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 18-13 Bit 9: Configuration - adDebugSetFilterLevel 0xX : Se t trace level filter X = B.
Dshell Troubleshooting Troubleshooting Authenticated VLANs page 18-14 OmniSwitch Troubleshooting Guide September 2005 Authenticated MAC address = 00.20.DA.00.00.02 XCAP 802.3 SNAP header = AA.AA.03.00.20DA.0202 Authenticated DNS name = authent.com 802.
Troubleshooting Authenticated VLANs Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 18-15 XCAP: Unexpected message identifier rcv .= 0 value = 1866 = 0x74a To verify the Authen tication IP bound to each VLAN wi th subnet mask please run the adDebugShowAv- lanIp command.
Dshell Troubleshooting Troubleshooting Authenticated VLANs page 18-16 OmniSwitch Troubleshooting Guide September 2005.
OmniSwitc h Troubles hooting Guide September 2005 page 19-1 19 T r oubleshooting 802.1X The 802.1X standard defines port-based network access controls, and provides th e structure for authe nti- cating physi cal devices atta ched to a LAN. It uses the Extensib le Authentica tion Protocol (EAP).
Troubleshooting with the CL I Troubleshooting 802.1X page 19-2 OmniSwitch Troubleshooting Guide September 2005 T roubleshooting with the CLI 1 Make sure the Radius an d Accounting po rts are config ured the same on both switc h and Radius Server.
Troubleshooting 802.1X Trouble shooting with the CLI OmniSwitc h Troubles hooting Guide September 2005 page 19-3 Authentication : enabled, IP Router Port : none, IPX Router Port : none, 6 Verify the status of the 802.1 x port using the show 802.1x command.
Troubleshooting Using Debug CLI Troubleshooting 802.1X page 19-4 OmniSwitch Troubleshooting Guide September 2005 T roubleshooting Using Debug CLI Assuming Radius communication takes place on UDP port 1645: Layer-2: debug ip packet protocol udp port 1645 start C S 1/1 00d09579640e->00d0956af558 IP 10.
Troubleshooting 802.1X Troubleshooting Using Debug CLI OmniSwitc h Troubles hooting Guide September 2005 page 19-5 440814250 AAA info [RAD] rad BuildServeurAuth : id = 19 440874069 AAA info [RAD] rad .
Troubleshooting Using Debug CLI Troubleshooting 802.1X page 19-6 OmniSwitch Troubleshooting Guide September 2005 444336676 AAA info [RAD] rad AddAttr : adding attribute type 5 444417261 AAA info [RAD].
Troubleshooting 802.1X Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 19-7 Dshell T roubleshooting Note . Dshell command s should only be used by Alcate l personnel or under the dir ection of Alcatel.
Dshell Troubleshooting Troubleshooting 802.1X page 19-8 OmniSwitch Troubleshooting Guide September 2005 2:0 Direction = In-Out (0) 2:0 Source MAC addr. = 00.00.0 0.00.00.00 2:0 value = 0 = 0x0 To verify the sequence of the packe t flow, set the be low D shell flags to troubleshoot the issue.
Troubleshooting 802.1X Dshell Troubleshooting OmniSwitc h Troubles hooting Guide September 2005 page 19-9 2:0 2:0 AD INFO-> EAPol pkt.sent out: 2:0 Slot=2,Glb.port=0x22,User p ort=3,Frame=0x4479000 2:0 2:0 AD INFO-> EAPol pkt.from suppl icant, rcv.
Dshell Troubleshooting Troubleshooting 802.1X page 19-10 OmniSwitch Troubleshooting Guide September 2005.
OmniSwitc h Troubles hooting Guide September 2005 page -1 A OS6600/OS7700/OS8800 Architecture Over view The switch be nefits from an inte lligent, multi -layer switch ing, fully d istributed and passi.
The MAC ASIC page -2 OmniSwitch Troubleshooting Guide September 2005 The MAC ASIC There are two different types of MAC layer ASIC s: • Catalina • Firenze Catalina The Catalina b asically provid es three function s: Media Access Cont rol (MAC) Layer functions, d ata buff- ering, and statistics accumula tion and storage for each port.
The MAC ASIC OmniSwitc h Troubles hooting Guide September 2005 page -3 Coronado Catalina 0 Catalina 1 1 Gig P ort 1 Gig p ort XY-BUS F-BUS GNI-U-2 OS-7XXX Coronado 0 Catalina 0 Catalina 1 Gi ga bit po.
The MAC ASIC page -4 OmniSwitch Troubleshooting Guide September 2005 Firenze The Firenze basically prov ides three function s: Medi a Access Control (MAC) Laye r functions, D ata buff- ering, Flow Control and stati stics a ccumulation and storag e for each port.
The MAC ASIC OmniSwitc h Troubles hooting Guide September 2005 page -5 The Cor onado ASIC The Coronado ASIC is the cent erpiece of t his advanced architectural design. While each ASIC performs a vital function i n the overall a rchitecture, th e Coronado provid es most of the key features like wire-rate L2 and L3 switching an d routing.
The MAC ASIC page -6 OmniSwitch Troubleshooting Guide September 2005 The Coronado ASIC contains bo th Ingress and Egress functi ons. Ethernet frame s flow from the Catal ina through the Ingress Coron ado, through the Nant ucket switch fabric, then thro ugh the Coronado Egress logic and finally out t he Egress Catalina.
The MAC ASIC OmniSwitc h Troubles hooting Guide September 2005 page -7 Coronado: The “Bra in” of the System • Provides hardware performance for mo st features on the OmniSwitch. • Involved in both the ing ress and egress packet processing. • Provides a high spe ed connection to Catalina via the XYBUS.
Queue Driver Interaction page -8 OmniSwitch Troubleshooting Guide September 2005 • Queues are maintained by th e software module know n as the Queue Driver runs on each NI. It provid es the interactio n to other software modules in the Falcon/Eagl e product to crea te/modify/delete /manage all the queues in the system.
Queue Driver Interaction OmniSwitc h Troubles hooting Guide September 2005 page -9 NI Super vision Queue driver sends th e task initializati on and task ready messages to the NI Sup ervision task just before receiving any co nfiguration informat ion from the CM M Ethernet dri ver.
Queue Driver Interaction page -10 OmniSwitch Troubleshooting Guide September 2005 QoS Policy Deleted When a QoS Policy i s deleted, the QoS Manager is notifie d.
Link Aggregation OmniSwitc h Troubles hooting Guide September 2005 page -11 Link Aggregation Link Aggregation feature allows software to aggregate a set o f ports (not necessar ily contiguous or on the same Coronado ) into a group. Each port is referred to as a channel th at can carry some bandwidth.
Source Learning page -12 OmniSwitch Troubleshooting Guide September 2005 Source Learning Coronado ASIC is a ingres s classifier that performs Layer 2 hardwar e table lookups to the V LAN Id corre- sponds to the in coming packets.
Hardware Routing Engine (HRE) OmniSwitc h Troubles hooting Guide September 2005 page -13 Hardware Routing Engine (HRE) This feature is responsible for ma naging the Coro nado HRE resources that perform IP and IPX pack et classificat ion and forwar ding.
Hardware Routing Engine (HRE) page -14 OmniSwitch Troubleshooting Guide September 2005 Router MACs Helps identify candidate traffic for cl assification. The HRE only operates on traffic tha t is ident ified as requiring layers 3 and 4 classificat ion.
QoS/Policy Manager OmniSwitc h Troubles hooting Guide September 2005 page -15 QoS/Policy Manager Policies describe subsets of t raffic, and what to do with that traffic. The Pol icy Processor determines what policies are enforceable, an d organizes t he policies into list s used by the c lassifier.
The Fabric Architecture page -16 OmniSwitch Troubleshooting Guide September 2005 The Fabric Architecture ASIC provides the swit ching fabric functional ity for the OmniSwitch Seri es. The switching fabric does no frame processing and d oes not distinguish bet ween L2 switching and L3 routing.
Nantucket ASIC OmniSwitc h Troubles hooting Guide September 2005 page -17 Nantucket ASIC The Nantucket ASICs have the following: • Support for 8 an d 16 Coronados on ly. • No dynamic que ue numbering for e ach NI slot. • Fixed eight Nantuckets per Fabr ic board.
Nantucket ASIC page -18 OmniSwitch Troubleshooting Guide September 2005 Functional Description: The Nantucket software resides on Chassis Management Module (CMM) and run on the UltraSPARC IIe processor within th e CMM. The Nantucke t software communicates to the Nantucket ASIC via the PCI Bridge and Bbu s Bridges.
Nantucket ASIC OmniSwitc h Troubles hooting Guide September 2005 page -19 Calendar Manager Module • Generates dequeue requests to the Queue Manag er module with priori ties of uP packets high est, multi- cast packets se cond highest and unicast packets lowest.
Nantucket ASIC page -20 OmniSwitch Troubleshooting Guide September 2005 N antu cket 0 N antu cket 1 N antu cket 2 N antu cket 3 N antu cket 0 N antu cket 1 Coronado Coronado Coronado Coronado Coronado.
Nantucket ASIC OmniSwitc h Troubles hooting Guide September 2005 page -21 N antuck et 3 Seco n da r y C MM OS-7700 Backplane N antucket 2 N antucket 3 N antucket4 N antucket 5 N antucket 6 N antucket7.
Roma page -22 OmniSwitch Troubleshooting Guide September 2005 Roma Each Fabric Module is based on two Roma ASICs, whic h provide the store-and-f orward switching fabr ic function for the OS-8 800 product. Th e Roma ASIC is bit-sli ced; a group of eig ht Roma ASICs op erates together as a singl e synchronized fabric.
Roma OmniSwitc h Troubles hooting Guide September 2005 page -23 • Separate paychecks for multicast • Generates ingress coupons, receives egre ss coupon s for backpressure capabi lity • Ingress coupon generation period: ~2 microseconds • Paycheck gene ration period : 32.
Roma page -24 OmniSwitch Troubleshooting Guide September 2005 Flow Control Coupon and payc heck thresholds are set for unicast an d IPC queues (multicast is limited by Coronado for fabric ingre ss). These thre sholds are us ed to genera te ingress backpressure an d paycheck messages.
Roma OmniSwitc h Troubles hooting Guide September 2005 page -25 Fabric Slot Extraction This state assumes that there are five fabric sl ots occupied, w ith one fabri c card serv ing as the re dundant card. Roma Drive r will have al ready set up the op erational Ro ma chip set to use built-in hot swap handling.
Chassis Management Module (CMM) page -26 OmniSwitch Troubleshooting Guide September 2005 Framing Err or The Framing Error event represents an event where the Roma ASIC detects an error in a pa cket header on ingress. Since t his will pote ntially corrupt the buffer syste m, a free list rebui ld is required wh en this is detected.
Chassis Management Module (CMM) OmniSwitc h Troubles hooting Guide September 2005 page -27 OS7000 CMM The CMM for OS7000 contains the follow ing: • System Processor • Ultra Space 11e (400 MHz) •.
Chassis Management Module (CMM) page -28 OmniSwitch Troubleshooting Guide September 2005 Functional Description of CMM Software and Conf iguration management i s implemented in such a way to provid e the operator wit h: • Flexibility • Resiliency • And to mini mize the service interruption du ring the upda te of a networ k.
Chassis Management Module (CMM) OmniSwitc h Troubles hooting Guide September 2005 page -29 AOS Boot ROM • Sparc Processor executes the Spar c Boot ROM code from flash Memory in the protected mem ory.
Chassis Management Module (CMM) page -30 OmniSwitch Troubleshooting Guide September 2005 MiniBoot MiniBoot contai ns VX Works Operat ing system Performs the following tasks: • Post Mortem Dump (PMD) Pr ocessing to save as mu ch diagnostic as possible in the FFS after a system crash.
Chassis Management Module (CMM) OmniSwitc h Troubles hooting Guide September 2005 page -31 Miniboot Lo ad Mi n imu m V X W o rk s with File system with PMD process. Boot.cfg determ ination and Boot ROM (Hidden & Protected) MiniBoot 1-Default 2-Backup (W rite Protecte d) Boot.
Chassis Management Module (CMM) page -32 OmniSwitch Troubleshooting Guide September 2005 Overall System Architecture • Fabric resides on CMM • Number of Nantuckets can be 4 or 8 depending on the c.
Chassis Management Module (CMM) OmniSwitc h Troubles hooting Guide September 2005 page -33 • Fabric reside s independent of t he CMM. It resid es at the Bac k of the Chassis. CMM can fail over inde- pendent of Switching Fabric and vice versa. • Minimum of 4 Switchin g Fabric Modules (SFM) with 8 ROMS chips are required to operate.
Packet Wa lk page -34 OmniSwitch Troubleshooting Guide September 2005 Packet W alk Packet W alk Principles • All switching and routing is performed on the Ing ress side of the switc h. There are no ad dress lookups made on the Egress side. • The Coronado combines the L2 switching a nd L3 routing log ic into the sa me ASIC.
Specific Packet Flows OmniSwitc h Troubles hooting Guide September 2005 page -35 Specific Packet Flows Unknown L2 Source, Known L2 Destination The Catalina ASIC Packet arri ves at Catali na.
Unknown Destination page -36 OmniSwitch Troubleshooting Guide September 2005 Unknown Destination Known L2 Source, Unknown L2 Destination The Catalina ASIC Packet arri ves at Catali na.
Unknown Destination OmniSwitc h Troubles hooting Guide September 2005 page -37 The Coronado ASIC • The Coronado receives th e packet via the FBUS. • The Coronado then strips th e 802.1q header that was a dd ed on ingress, if needed. The Catalina ASIC • Packet is then put on to the Xybus to be re ceived by the Catalin a.
Unknown Destination page -38 OmniSwitch Troubleshooting Guide September 2005 Unknown L3 DA The Coronado ASIC • The FIFO logic maintain s queues of frames from bo th Xybus i nterfaces and selects an incoming frame for HRE processi ng. This FIFO is done on the on ch ip memory of the HRE.
Unknown Destination OmniSwitc h Troubles hooting Guide September 2005 page -39 Pac ket arrives from Catalina to Co ronado Source Address known ? Y 1 Pseudo-CAM (PCAM) Provides Group ID (GID) N 2 Assig.
Unknown Destination page -40 OmniSwitch Troubleshooting Guide September 2005 5 Classif y Special DA DA is router MAC DA is IGM P DA is IPMS DA is STP m ulticast (BPDU) 6 7 8 DA PCAM lookup, known ? S/.
Hardware Buses on OmniSwitch 7700/78 00/8800 Switches OmniSwitc h Troubles hooting Guide September 2005 page -41 Hardware Buses on OmniSwitch 7700/7800/ 8800 Switches Xybus The interface bet ween the MAC to Coronado, which is 0-1 Fbus The interfac e between t he Coronado to the Fabric AS IC (Nantucket or Roma).
Bus Mapping on OmniSwitch 77 00/7800/8800 Switches page -42 OmniSwitch Troubleshooting Guide September 2005 Bus Mapping on OmniSwitch 7700/7800/8800 Switches Xybus Mapping Each board typ e has own mapp ing, describe d for all ex isting board ty pe below.
OS6624/6648 Architecture OmniSwitc h Troubles hooting Guide September 2005 page -43 OS6624/6648 Architecture OmniSwitch 6XXX is a stac kable version of the OS7/ 8XXX Switches. It provides pure Ethernet switch- ing for 10/100 an d Gigabit ports, alon g with stackability.
OS6624/6648 Architecture page -44 OmniSwitch Troubleshooting Guide September 2005 Hardware Architectural Over view OS6600 uses off the shelf In tel ASIC. Int el IXE2424 Switching ASIC is u sed to implement the required functionality . The key features of Intel IXE2424 ar e: • Provides 24 10/100 FE ports and 4 GE ports.
OS6624/6648 Architecture OmniSwitc h Troubles hooting Guide September 2005 page -45 IXE 242 4 Pack e t M emo ry Address Memory 100MH 32 Bit PCI 66 MHz SMII 125 MHz MDIO Interface GM11/10 Bit Interface.
OS6624/6648 Architecture page -46 OmniSwitch Troubleshooting Guide September 2005 Layer 2 For warding • Packets enter the IXE2424 throug h the SMII & GMII/ TBI pins from external PHY devi ces. First, the MAC associated with the port th e packet was received from proce sses the packet.
OS6624/6648 Architecture OmniSwitc h Troubles hooting Guide September 2005 page -47 Address Learning Address Learning in the IXE2424 i s performed primarily in the software. The har dware provides a CAM interface to facilitate fa st learning o f addresses.
OS6624/6648 Architecture page -48 OmniSwitch Troubleshooting Guide September 2005 Address Look-up Methodology Source and Destination Addresses are searched in parall el and then a sync proce ss occurs to ensure both are completed.
OS6624/6648 Architecture OmniSwitc h Troubles hooting Guide September 2005 page -49 3-Protocol Entry • Used to allow di fferent rules to be applied for diff erent protocols associated with same address. Proto- col Offset Register is u sed to identify which protocols will be used in the system.
OS6624/6648 Architecture page -50 OmniSwitch Troubleshooting Guide September 2005 Layer 3 For warding Packets Arriv ed Header 64 B ytes Apply proto col based VLA N on Search the IP Source a nd Destina.
OS6624/6648 Architecture OmniSwitc h Troubles hooting Guide September 2005 page -51 VLANs The IXE2424 supp orts VLANs base d on: • Ports. This is accomplished usin g Port Net ID Entry described bel ow. • 802.1Q Tags. This tag is incl uded in the p acket.
OS6624/6648 Architecture page -52 OmniSwitch Troubleshooting Guide September 2005 T ag Net ID Entr y • Contains relate d information like tagged set and me mber set. A 4x32 bit entry is presen t for every possible VLAN (409 6 supported). • VLAN Tag Vali d.
OS6624/6648 Architecture OmniSwitc h Troubles hooting Guide September 2005 page -53 Rules-Based Priority • Several types of pr iority rules are supported. Each rule is associa ted with a specific device priori ty. If a packet satisfies a certain pr iority rule, i t is assigned the device prio rity correspon ding to that rule.
CMM Functionality for OS6600 page -54 OmniSwitch Troubleshooting Guide September 2005 CMM Functionality for OS6600 The overall software architecture of Fal con is retain ed for Hawk.
CMM Functionality for OS6600 OmniSwitc h Troubles hooting Guide September 2005 page -55 The chassis like, or V-Chassis, stra tegy allows the syst em to keep th e sa me management interface. Si nce on Falcon/Eagle, the management uses the notion of slot , this notio n of slot is retain ed for Hawk.
CMM Functionality for OS6600 page -56 OmniSwitch Troubleshooting Guide September 2005 • In idle mode the role of Chassis Su pervision is limited to monitoring the te mperature, power suppl y, fan(s), hand ling of flash sy nchronization and takeover.
CMM Functionality for OS6600 OmniSwitc h Troubles hooting Guide September 2005 page -57 The process of multi ple CMMs is compo sed of following ste ps: • Bootup • Role election • Lowest slot num.
OS6600 IPC Commun ication page -58 OmniSwitch Troubleshooting Guide September 2005 OS6600 IPC Communication IPC software in terface is un changed. IPC prov ides the followi ng services: • NI-NI comm.
OS6600 BOOT Sequence OmniSwitc h Troubles hooting Guide September 2005 page -59 OS6600 BOOT Sequence • Different from Falcon/Eagle • No NI cod e to downlo ad • Each element is independent from t.
OS6600 BOOT Sequence page -60 OmniSwitch Troubleshooting Guide September 2005 • Get the Role of the Stack- Primary, Secondary or Idle • Start NI supervisi on and Prober • Start Stack Manager •.
OS6600 BOOT Sequence OmniSwitc h Troubles hooting Guide September 2005 page -61 • NI supervision and Prober Task . NI Supervision task in turn starts the NI applica tions.
OS6600 BOOT Sequence page -62 OmniSwitch Troubleshooting Guide September 2005.
OmniSwitc h Troubles hooting Guide September 2005 page -1 B Debug Commands This chapter documents th e following Command Line Inte rface (CLI) debug comma nds. Blue text indi- cates that the text is hypertex t-linked to addi tional documen tation for th at command.
page -2 OmniSwitch Troubleshooting Guide September 2005 SNMP Debug Commands debug snmp trace debug snmp reset debug snmp interface debug snmp data Session Debug Commands debug session trace debug sess.
OmniSwitc h Troubles hooting Guide September 2005 page -3 Server Load Balancing (SLB) Debug Commands debug slb help debug slb debug slb adminstatus debug slb createcluster debug slb deletecluster debu.
page -4 OmniSwitch Troubleshooting Guide September 2005 HRE Debug Commands debug hre warn debug hre trace debug hre pcam debug hre pcam verbose debug hre pcam mode range debug hre ipx flow debug hre i.
OmniSwitc h Troubles hooting Guide September 2005 page -5 VLAN Debug Co mmands debug vlan vpas debug vlan rule protocol-m ap debug vlan rule ports debug vlan rule memory debug vlan rule database debug.
page -6 OmniSwitch Troubleshooting Guide September 2005 debug 802.1q Retrieves debuggi ng messages for the ta gged port selec ted. debug 802.1q { slot / po rt | aggregat e_id } Syntax Definitions slot The slot number to configure 802.1Q tagging. port The port number to confi gure 802.
OmniSwitc h Troubles hooting Guide September 2005 page -7 Release History Release 5.1; command was intr oduced. Related Commands N/A MIB Objects N/A output definitions Aggregate/Sl ot Status Wh ether the slot or aggreg ate link is actively runn ing. Port Status Whether the port is a ctively ru nning.
page -8 OmniSwitch Troubleshooting Guide September 2005 ip dvmrp debug-level Defines the level of debuggin g fo r DVMRP protocol on the switch. ip dvmrp debug-level level Syntax Definitions level Specifies the DVMRP debug level (0 –255). Higher debug-levels will include all message s that correspond to a lower value.
OmniSwitc h Troubles hooting Guide September 2005 page -9 ip dvmrp debug-type Enables or disables DVMRP debugging for a sp ec ified message type, or for all message typ es. Note. Debugging for a speci fied message type w ill only be enabled if its de bug level is a value greate r than zero (i.
page -10 OmniSwitch Troubleshooting Guide September 2005 Defaults Platforms Support ed OmniSwit ch 7700, 780 0, 8800 Usage Guidelines • Use the no form of the command to disable debuggin g for the specified item. • Reminder: Debu gging for a sp ecified message type w ill only be enabled if its de bug level is a value greater than zero (i.
OmniSwitc h Troubles hooting Guide September 2005 page -11 show ip dvmrp debug Displays the c urrent level of debugging fo r DVMRP prot ocol on the sw itch, as we ll as the current DVMRP debugging status for all messages ty pes.
page -12 OmniSwitch Troubleshooting Guide September 2005 Release History Release 5.1; command was intr oduced. Related Commands Grafts The current debugg ing status for DV MRP Graft processing. Options include on or off . IGMP The current debugging status fo r DVMRP Internet Group Management Protocol (IGMP) pa cket processin g.
OmniSwitc h Troubles hooting Guide September 2005 page -13 debug ip pack et Enables/disables/configures the IP packet debug feat ure. This command i s generally used only when working with a field engineer to debug a problem on the switch.
page -14 OmniSwitch Troubleshooting Guide September 2005 protocol Specifies a protocol type to debug. Specify tcp to debug TCP packets; specify udp to debug UPD packets; specify icmp to debug ICMP pack- ets; specify igmp to debug IGMP packets; specify num to numerically specify a protocol (e .
OmniSwitc h Troubles hooting Guide September 2005 page -15 Related Commands debug ip level Configures IP debug le vel. This command allo ws you to set the le vel (amount) of information d isplayed.
page -16 OmniSwitch Troubleshooting Guide September 2005 debug ip level Configures the IP d ebug level. Th is command allows you to set the le vel (amount) of i nformation displayed. The lower the level, the mor e significant the event. For example, a level of 1 will di splay only the most criti cal problems.
OmniSwitc h Troubles hooting Guide September 2005 page -17 debug ip pack et default Returns IP packet debug optio ns to default values. debug ip packet default Syntax Definitions N/A Defaults N/A Platforms Support ed OmniSwitch 6624, 6648, 7 700, 7800, 8800 Usage Guidelines See “Defaults” on page B-14 for default values.
page -18 OmniSwitch Troubleshooting Guide September 2005 debug ip pack et Displays IP debug co nfiguration par ameters. This command is ge nerally used only when working with a field enginee r to debug a pro blem on the swi tch.
OmniSwitc h Troubles hooting Guide September 2005 page -19 Release History Release 5.1; command was intr oduced. Related Commands debug ip packet Configures IP packet deb ug.
page -20 OmniSwitch Troubleshooting Guide September 2005 debug ip mroute debug-level Configures the Mu tlicast Routing d ebug level. debug ip mroute debug-level level Syntax Definitions level Specifies the M utlicast Routi ng debug lev el (0–255).
OmniSwitc h Troubles hooting Guide September 2005 page -21 ip mroute debug-type Displays the curren t multicast routing debug levels a nd types. ip mroute debug-type [tm | protos {on | off} | misc | m.
page -22 OmniSwitch Troubleshooting Guide September 2005 ip ospf debug-level Configures OSPF de bugging level. The level refers to the granularity o f the information p rovided. Gener- ally, the higher the number, th e more specific the information. ip ospf debug -level level Syntax Definitions level The debugging level.
OmniSwitc h Troubles hooting Guide September 2005 page -23 ip ospf debug-type Configures the type of O SPF functionality to debug. ip ospf debug-type [error] [warning] [state] [recv] [send] [flood] [s.
page -24 OmniSwitch Troubleshooting Guide September 2005 auth Administrat ively enables/d isables debugging messages for OSPF ’s authentication process. area Administratively e nables/ disables debugging messages for OSPF’s ar ea events. intf Administrat ively enables/d isables debugging messages for OSPF ’s interface ope rations.
OmniSwitc h Troubles hooting Guide September 2005 page -25 Related Commands MIB Objects ALAOSPFDEBUGCONFIG alaOspfDebugError alaOspfDebugWarning alaOspfDebugState alaOspfDebugRecv alaOspfDebugSend ala.
page -26 OmniSwitch Troubleshooting Guide September 2005 show ip ospf debug Displays current OSPF debug level and types. show ip ospf debug Syntax Definitions N/A Defaults N/A Platforms Support ed Omn.
OmniSwitc h Troubles hooting Guide September 2005 page -27 Release History Release 5.1; command was intr oduced. Related Commands output definitions Debug Level The granularity of the debug messa ges. This number wi ll be 10, 50, or 99, where the lower numb er is least specific.
page -28 OmniSwitch Troubleshooting Guide September 2005 MIB Objects alaOspfDebugLevel alaOspfDebugError alaOspfDebugWarning alaOspfDebugState alaOspfDebugRecv alaOspfDebugSend alaOspfDebugFlood alaOs.
OmniSwitc h Troubles hooting Guide September 2005 page -29 ip pimsm debug-level Defines the level of PIM-SM de bug messages th at are generated. ip pimsm debug-level level Syntax Definitions level Specifies the PIM-SM debug leve l (0–255). Higher debug-lev els will include all message s that correspond to a lower value.
page -30 OmniSwitch Troubleshooting Guide September 2005 ip pimsm debug-type Configures the type(s) of PIM-SM debug messages to display. ip pimsm debug-type message_list no ip pimsm debug-t ype message_list Syntax Definitions message_list Specifies the type(s) of PIM-SM messages to be de bugged.
OmniSwitc h Troubles hooting Guide September 2005 page -31 Platforms Support ed OmniSwit ch 7700, 780 0, 8800 Usage Guidelines • The message-types specified in the command line will only be displayed if the debug leve l has been set to a number grea ter than zero (i.
page -32 OmniSwitch Troubleshooting Guide September 2005 show ip pimsm debug Displays the current PIM-SM debug levels and types. show ip pimsm debug Syntax Definitions N/A Defaults N/A Platforms Suppo.
OmniSwitc h Troubles hooting Guide September 2005 page -33 Release History Release 5.1; command was intr oduced. Related Commands crp The current state of messages rel ated to Candidate R endezvous Point (C-RP). Options include on or off . erro r The current state of messages re lated to all error handling.
page -34 OmniSwitch Troubleshooting Guide September 2005 ip rip debug-type Configures the type of RIP messages to debug. The debu g feature on the switch is generally used only under the directio n of a field e ngineer. Use thi s command to c onfigure the typ e of RIP debug warn ings (e.
OmniSwitc h Troubles hooting Guide September 2005 page -35 Release History Release 5.1; command was intr oduced. Related Commands MIB Objects alaRipLogTable alaRipDebugType ip rip debug-level Configures RIP debugging l evel. show ip rip debug Displays the current RIP debug levels and types.
page -36 OmniSwitch Troubleshooting Guide September 2005 ip rip debug-level Configures RIP debug level . You can set th e level of information disp layed using the ip rip debug level command. The lo wer the leve l, the more si gnificant the e vent. For example, a level of 1 will display only the most criti cal problems.
OmniSwitc h Troubles hooting Guide September 2005 page -37 show ip rip debug Displays the current RIP debug l evels and types. show ip rip debug Syntax Definitions N/A Defaults N/A Platforms Support e.
page -38 OmniSwitch Troubleshooting Guide September 2005 Related Commands MIB Objects dispDrcRipDebug ip rip debug-level Configures RIP debugg ing level.
OmniSwitc h Troubles hooting Guide September 2005 page -39 debug slot information Displays all the information about a specific slot. It inclu des all the details about the ports, stat istics, MDIX, IPC pools, and othe r phy-related information.
page -40 OmniSwitch Troubleshooting Guide September 2005 InPauseFrames = 0, OutPauseFrames = 0 #################################### ##### debug interfaces 1 Led #################################### ##.
OmniSwitc h Troubles hooting Guide September 2005 page -41 #################################### ##### debug ipc pools slot 1 #################################### ##### IPC Pools slot 1, slice 0: Urgen.
page -42 OmniSwitch Troubleshooting Guide September 2005 slot/port( 1/5 ): Phy ID : 1e 0 : 3000 7809 13 78f7 de 1 0 4 2801 8 : 0 0 0 0 0 0 0 0 10 : 184 100 8000 54 de 2 0 0 202 18 : 0 0 40 100 c42 9 0.
OmniSwitc h Troubles hooting Guide September 2005 page -43 0 : 3000 7809 13 78f7 de 1 0 4 2801 8 : 0 0 0 0 0 0 0 0 10 : 184 100 8000 54 de 2 0 0 202 18 : 0 0 40 100 c42 3 0 0 210 slot/port( 1/14): Phy.
page -44 OmniSwitch Troubleshooting Guide September 2005 18 : 0 0 40 100 c41 9 0 0 210 slot/port( 1/22): Phy ID : 1e 0 : 3000 7809 13 78f7 de 1 0 4 2801 8 : 0 0 0 0 0 0 0 0 10 : 184 100 8000 54 de 2 0.
OmniSwitc h Troubles hooting Guide September 2005 page -45 runt = 0 runt sz = 0 flowstate = 0 flowmode = 0 flowwait = 0 slot/port = ( 1/3 ) slice = 0 mac_chip = 0 index = 0x 3eb gport = 0x 2 Mac = 0x0.
page -46 OmniSwitch Troubleshooting Guide September 2005 long = 1 long sz = 1553 runt = 0 runt sz = 0 flowstate = 0 flowmode = 0 flowwait = 0 slot/port = ( 1/7 ) slice = 0 mac_chip = 0 index = 0x 3ef .
OmniSwitc h Troubles hooting Guide September 2005 page -47 pause SA = 0x 0:d0:95:6a:5f:31 pause DA = 0x 1:80:c2: 0: 0: 1 long = 1 long sz = 1553 runt = 0 runt sz = 0 flowstate = 0 flowmode = 0 flowwai.
page -48 OmniSwitch Troubleshooting Guide September 2005 trap = 0 pause SA = 0x 0:d0:95:6a:5f:35 pause DA = 0x 1:80:c2: 0: 0: 1 long = 1 long sz = 1553 runt = 0 runt sz = 0 flowstate = 0 flowmode = 0 .
OmniSwitc h Troubles hooting Guide September 2005 page -49 ifg = 12 backoff = 0 trap = 0 pause SA = 0x 0:d0:95:6a:5f:39 pause DA = 0x 1:80:c2: 0: 0: 1 long = 1 long sz = 1553 runt = 0 runt sz = 0 flow.
page -50 OmniSwitch Troubleshooting Guide September 2005 mtu = 1553 flood = 1 flood lmt = 1 ifg = 12 backoff = 0 trap = 0 pause SA = 0x 0:d0:95:6a:5f:3d pause DA = 0x 1:80:c2: 0: 0: 1 long = 1 long sz.
OmniSwitc h Troubles hooting Guide September 2005 page -51 debug interfaces set backpressure Enables and disab les fabric back pressure on a Network Interface (NI) or an entire chassis. debug interfaces set [ slot ] backpressure {enable | disable} Syntax Definitions slot The slot number to enabl e or disa ble fabric back pressure.
page -52 OmniSwitch Troubleshooting Guide September 2005 debug interfaces backpressure Displays if fabric bac k pressure is enable d or disabl ed on a Network Interface (N I) or an entire chassis. debug interfaces [ slot ] backpressure Syntax Definitions slot The slot number t o display the fa bric back pressure state.
OmniSwitc h Troubles hooting Guide September 2005 page -53 Related Commands MIB Objects N/A debug interfaces set backpressure Enables and disab les fabric back pressure on an NI or an e ntire chassis.
page -54 OmniSwitch Troubleshooting Guide September 2005 debug interfaces led Displays LED information. debug interfaces slot led Syntax Definitions slot The slot number of the Ne twork Interface (NI) module.
OmniSwitc h Troubles hooting Guide September 2005 page -55 Release History Release 5.1; command was intr oduced. Related Commands N/A.
page -56 OmniSwitch Troubleshooting Guide September 2005 debug interfaces mdix Displays Media Dependent Interface with Crossover (MDIX) information. debug interfaces slot mdix Syntax Definitions slot The slot number of the Ne twork Interface (NI) module.
OmniSwitc h Troubles hooting Guide September 2005 page -57 Related Commands N/A.
page -58 OmniSwitch Troubleshooting Guide September 2005 debug interfaces phy Displays PHY information. debug interfaces slot phy Syntax Definitions slot The slot number of the Ne twork Interface (NI) module.
OmniSwitc h Troubles hooting Guide September 2005 page -59 0 : 3000 7809 13 78f7 de 1 0 4 2801 8 : 0 0 0 0 0 0 0 0 10 : 184 100 8000 0 de 2 0 0 202 18 : 0 0 40 e100 c42 9 0 0 210 slot/port( 1/6 ): Phy.
page -60 OmniSwitch Troubleshooting Guide September 2005 10 : 184 100 8000 0 de 2 0 0 202 18 : 0 0 40 100 c42 3 0 0 210 slot/port( 1/14): Phy ID : 1e 0 : 3000 7809 13 78f7 de 1 0 4 2801 8 : 0 0 0 0 0 .
OmniSwitc h Troubles hooting Guide September 2005 page -61 Phy ID : 1e 0 : 3000 7809 13 78f7 de 1 0 4 2801 8 : 0 0 0 0 0 0 0 0 10 : 184 100 8000 0 de 2 0 0 202 18 : 0 0 40 100 c41 d 0 0 210 slot/port(.
page -62 OmniSwitch Troubleshooting Guide September 2005 debug interfaces mac Displays MAC info rmation. debug interfaces slot mac Syntax Definitions slot The slot number of the Ne twork Interface (NI) module.
OmniSwitc h Troubles hooting Guide September 2005 page -63 debug interfaces port structure Displays port structure information. debug interfaces slot port structure Syntax Definitions slot The slot number of the Ne twork Interface (NI) module.
page -64 OmniSwitch Troubleshooting Guide September 2005 slot/port = ( 1/3 ) slice = 0 mac_chip = 0 index = 0x 3eb gport = 0x 2 Mac = 0x00:d0:95:6a:5f:2a prevLink = 0 cur_Link = 2 linkUptime= 0 admin .
OmniSwitc h Troubles hooting Guide September 2005 page -65 slot/port = ( 1/7 ) slice = 0 mac_chip = 0 index = 0x 3ef gport = 0x 6 Mac = 0x00:d0:95:6a:5f:2e prevLink = 0 cur_Link = 2 linkUptime= 0 admi.
page -66 OmniSwitch Troubleshooting Guide September 2005 flowstate = 0 flowmode = 0 flowwait = 0 slot/port = ( 1/11) slice = 0 mac_chip = 0 index = 0x 3f3 gport = 0x a Mac = 0x00:d0:95:6a:5f:32 prevLi.
OmniSwitc h Troubles hooting Guide September 2005 page -67 runt = 0 runt sz = 0 flowstate = 0 flowmode = 0 flowwait = 0 slot/port = ( 1/15) slice = 0 mac_chip = 1 index = 0x 3f7 gport = 0x 12 Mac = 0x.
page -68 OmniSwitch Troubleshooting Guide September 2005 long = 1 long sz = 1553 runt = 0 runt sz = 0 flowstate = 0 flowmode = 0 flowwait = 0 slot/port = ( 1/19) slice = 0 mac_chip = 1 index = 0x 3fb .
OmniSwitc h Troubles hooting Guide September 2005 page -69 pause SA = 0x 0:d0:95:6a:5f:3d pause DA = 0x 1:80:c2: 0: 0: 1 long = 1 long sz = 1553 runt = 0 runt sz = 0 flowstate = 0 flowmode = 0 flowwai.
page -70 OmniSwitch Troubleshooting Guide September 2005 debug interfaces mac stats Displays MAC stats for a slot or slot/port. debug interfaces { slot | slot / port } mac stats Syntax Definitions slot The slot number of the Ne twork Interface (NI) module.
OmniSwitc h Troubles hooting Guide September 2005 page -71 debug interfaces mac port Displays MAC level register information. debug interfaces { slot | slot / port } mac port Syntax Definitions slot The slot number of the Ne twork Interface (NI) module.
page -72 OmniSwitch Troubleshooting Guide September 2005 debug interfaces mac nonport Displays MAC level informatio n for nonport from t he register values. debug interfaces { slot | slot / port } mac nonport Syntax Definitions slot The slot number of the Ne twork Interface (NI) module.
OmniSwitc h Troubles hooting Guide September 2005 page -73 debug interfaces switching Displays the regist er value specifi ed in hexadec imal for all the slo ts or displays a spe cified number o f register valu es starting fro m the he xadecimal address for all the slo ts.
page -74 OmniSwitch Troubleshooting Guide September 2005 debug ipc pools slot Displays IPC po ols on a particu lar slot. debug ipc pools slot slot Syntax Definitions slot The slot number of the Ne twork Interface (NI) module.
OmniSwitc h Troubles hooting Guide September 2005 page -75 Related Commands debug ipc pools cmm Displays IPC Pools o n Chassis Ma nagement Modu les (CMMs). debug ipc bbus Display s IPC pools for the Burst Bus with transmit and received count, Direct Memory Access errors, and parity errors.
page -76 OmniSwitch Troubleshooting Guide September 2005 debug ipc pools cmm Displays IPC Pool s on Chassis Manageme nt Modules (CMMs). debug ipc pools CMM Syntax Definitions N/A Defaults N/A Platform.
OmniSwitc h Troubles hooting Guide September 2005 page -77 Related Commands debug ipc pools slot Displays IPC po ols on a part icular slot. debug ipc bbus Display s IPC pools for the Burst Bus with transmit and received count, Direct Memory Access errors, and parity errors.
page -78 OmniSwitch Troubleshooting Guide September 2005 debug ipc bbus Displays IPC pools for the Burst Bus with transmit an d received count, Dire ct Memory Access errors, and parity errors.
OmniSwitc h Troubles hooting Guide September 2005 page -79 13| 1| 5944| 106369| 0| 0| 14| 1| 5946| 108400| 0| 0| 15| 0| 0| 0| 0| 0| 16| 1| 5955| 107128| 0| 0| Release History Release 5.1; command was intr oduced. Related Commands debug ipc pools cmm Displays IPC Pools o n Chassis Ma nagement Modu les (CMMs).
page -80 OmniSwitch Troubleshooting Guide September 2005 debug ipc active sock ets Displays all the active sockets on Chassis Management Modu les (CMMs).
OmniSwitc h Troubles hooting Guide September 2005 page -81 Release History Release 5.1; command was intr oduced. Related Commands debug ipc pools cmm Displays IPC Pools o n Chassis Ma nagement Modu les (CMMs). debug ipc bbus Display s IPC pools for the Burst Bus with transmit and received count, Direct Memory Access errors, and parity errors.
page -82 OmniSwitch Troubleshooting Guide September 2005 debug ipc active sock ets slot Displays all the active sockets on a particular slot. debug ipc active sockets slot slot Syntax Definitions slot The slot number of the Ne twork Interface (NI) module.
OmniSwitc h Troubles hooting Guide September 2005 page -83 2A6578|2| 208000B| 0| NI Task 2A6640|3| A08000B| 5000B| NI Task 2A6708|3| 908000B|100B000B| NI Task 2A67D0|3| 308000B| 309000B| NI Task 2A6898|3| 708000B| 6000B| NI Task 2A6960|3| F08000B| 20A000B| NI Task Release History Release 5.
page -84 OmniSwitch Troubleshooting Guide September 2005 debug fabric threshold Displays the threshold number for e ach fabric ASIC. In addition, it al so displays the Unicast pay gener- ated internally using Pay a lgorithm and Coup ons generated.
OmniSwitc h Troubles hooting Guide September 2005 page -85 0 27 330 f0 90 6 0 2d0 0 28 330 f0 90 6 0 2d0 0 29 660 28a 180 c 0 5a0 0 30 330 f0 90 6 0 2d0 0 31 20 20 20 2 0 20 0 32 330 f0 90 6 0 2d0 0 3.
page -86 OmniSwitch Troubleshooting Guide September 2005 1 21 330 f0 90 6 0 2d0 1 22 330 f0 90 6 0 2d0 1 23 330 f0 90 6 0 2d0 1 24 330 f0 90 6 0 2d0 1 25 330 f0 90 6 0 2d0 1 26 330 f0 90 6 0 2d0 1 27 .
OmniSwitc h Troubles hooting Guide September 2005 page -87 2 15 330 f0 90 60 2d0 2 16 330 f0 90 60 2d0 2 17 330 f0 90 60 2d0 2 18 330 f0 90 60 2d0 2 19 330 f0 90 60 2d0 2 20 330 f0 90 60 2d0 2 21 330 .
page -88 OmniSwitch Troubleshooting Guide September 2005 3 9 330 f0 90 60 2d0 3 10 330 f0 90 60 2d0 3 11 330 f0 90 60 2d0 3 12 330 f0 90 60 2d0 3 13 660 28a 180 c0 5a0 3 14 330 f0 90 60 2d0 3 15 330 f.
OmniSwitc h Troubles hooting Guide September 2005 page -89 4 3 330 f0 90 60 2d0 4 4 330 f0 90 60 2d0 4 5 330 f0 90 60 2d0 4 6 330 f0 90 60 2d0 4 7 330 f0 90 60 2d0 4 8 330 f0 90 60 2d0 4 9 330 f0 90 6.
page -90 OmniSwitch Troubleshooting Guide September 2005 debug fabric status Displays the over all status of al l the fabric ASICs. It displays the c hip version and ne tlist version bei ng used. In additi on, it also displ ays if any intern al or external interrupts were received.
OmniSwitc h Troubles hooting Guide September 2005 page -91 debug fabric stats Displays the fabric ASIC st atistics. debug fabric stats Syntax Definitions N/A Defaults N/A Platforms Support ed OmniSwit ch 7700, 780 0, 8800 Usage Guidelines • This command is not va lid for OS-6600 series of switche s.
page -92 OmniSwitch Troubleshooting Guide September 2005 Release History Release 5.1; command was intr oduced. Related Commands debug fabric status Displays the overa ll status of all t he fabric ASICs.
OmniSwitc h Troubles hooting Guide September 2005 page -93 debug fabric output Displays the fabric ASIC port number and the frame count. debug fabric output Syntax Definitions N/A Defaults N/A Platforms Support ed OmniSwit ch 7700, 780 0, 8800 Usage Guidelines • This command is not va lid for OS-6600 series of switche s.
page -94 OmniSwitch Troubleshooting Guide September 2005 1 6 31451 1 7 45447 1 8 47328 1 9 47327 1 10 9006 1 11 59975 1 12 59988 1 13 45449 1 14 48030 1 15 62795 --------- ------ ------- 2 0 55509 2 1.
OmniSwitc h Troubles hooting Guide September 2005 page -95 4 14 48030 4 15 62795 --------- ------ ------- 5 0 55509 5 1 59202 5 2 55029 5 3 55110 5 4 45451 5 5 47993 5 6 31452 5 7 45449 5 8 47328 5 9 .
page -96 OmniSwitch Troubleshooting Guide September 2005 Related Commands debug fabric status Displays the overa ll status of all t he fabric ASICs. debug fabric stats Displays the fabric ASIC statistics.
OmniSwitc h Troubles hooting Guide September 2005 page -97 debug fabric mcvectors Displays the Fabric ASIC port number and the frame count for multi cast packets.
page -98 OmniSwitch Troubleshooting Guide September 2005 0 110 c 0 111 c 0 112 4004 0 114 1006 0 115 4 0 116 4 0 117 804 0 130 804 0 140 7 0 141 5 0 150 586d 0 211 4004 0 212 1004 0 311 4 0 411 4 0 51.
OmniSwitc h Troubles hooting Guide September 2005 page -99 1 711 4 --------- ------ --------- 2 1 de6d 2 50 404 2 51 404 2 52 404 2 53 404 2 54 404 2 55 404 2 56 404 2 57 404 2 58 404 2 59 404 2 60 40.
page -100 OmniSwitch Troubleshooting Guide September 2005 3 102 4 3 103 4 3 104 44 3 105 44 3 106 4 3 107 4 3 108 24 3 109 24 3 110 c 3 111 c 3 112 4004 3 114 1006 3 115 4 3 116 4 3 117 804 3 130 804 .
OmniSwitc h Troubles hooting Guide September 2005 page -101 4 141 5 4 150 586d 4 211 4004 4 212 1004 4 311 4 4 411 4 4 511 5 4 611 6 4 711 4 --------- ------ --------- 5 1 de6d 5 50 404 5 51 404 5 52 .
page -102 OmniSwitch Troubleshooting Guide September 2005 6 56 404 6 57 404 6 58 404 6 59 404 6 60 404 6 61 404 6 62 404 6 100 5 6 102 4 6 103 4 6 104 44 6 105 44 6 106 4 6 107 4 6 108 24 6 109 24 6 1.
OmniSwitc h Troubles hooting Guide September 2005 page -103 7 111 c 7 112 4004 7 114 1006 7 115 4 7 116 4 7 117 804 7 130 804 7 140 7 7 141 5 7 150 586d 7 211 4004 7 212 1004 7 311 4 7 411 4 7 511 5 7 611 6 7 711 4 Release History Release 5.1; command was intr oduced.
page -104 OmniSwitch Troubleshooting Guide September 2005 debug fabric input Displays the fabric ASIC p ort numb er, frame count, and e rror count. debug fabric input Syntax Definitions N/A Defaults N/A Platforms Support ed OmniSwit ch 7700, 780 0, 8800 Usage Guidelines • This command is not va lid for OS-6600 series of switche s.
OmniSwitc h Troubles hooting Guide September 2005 page -105 1 5 5157878 0 1 6 5170104 0 1 7 0 0 1 8 5125861 0 1 9 5134184 0 1 10 5281984 0 1 11 5134611 0 1 12 5135085 0 1 13 0 0 1 14 5157433 0 1 15 51.
page -106 OmniSwitch Troubleshooting Guide September 2005 4 13 0 0 4 14 5157433 0 4 15 5135398 0 --------- ------ ------- ------- 5 0 5405287 0 5 1 5129582 0 5 2 5135541 0 5 3 5149706 0 5 4 0 0 5 5 51.
OmniSwitc h Troubles hooting Guide September 2005 page -107 Related Commands debug fabric status Displays the overa ll status of all t he fabric ASICs.
page -108 OmniSwitch Troubleshooting Guide September 2005 debug fabric fbus Displays the fabric ASIC port number and th e synchronizati on status for all t he FBUSs.
OmniSwitc h Troubles hooting Guide September 2005 page -109 1 6 Yes Yes Yes 1 7 No No No 1 8 Yes Yes Yes 1 9 Yes Yes Yes 1 10 Yes Yes Yes 1 11 Yes Yes Yes 1 12 Yes Yes Yes 1 13 No No No 1 14 Yes Yes Y.
page -110 OmniSwitch Troubleshooting Guide September 2005 4 14 Yes Yes Yes 4 15 Yes Yes Yes --------- ------ ----------- ------ ------- 5 0 Yes Yes Yes 5 1 Yes Yes Yes 5 2 Yes Yes Yes 5 3 Yes Yes Yes .
OmniSwitc h Troubles hooting Guide September 2005 page -111 Related Commands debug fabric status Displays the overa ll status of all t he fabric ASICs.
page -112 OmniSwitch Troubleshooting Guide September 2005 debug fabric errors Displays the errors detected for all the fabric ASICs on a swit ch. debug fabric errors Syntax Definitions N/A Defaults N/A Platforms Support ed OmniSwit ch 7700, 780 0, 8800 Usage Guidelines This command is only not fo r OS-6600 series of swit ches.
OmniSwitc h Troubles hooting Guide September 2005 page -113 debug fabric calendars Displays the fabric ASIC p ort number, calendar number, a nd the calendar length.
page -114 OmniSwitch Troubleshooting Guide September 2005 1 7 2 1 8 24 1 9 2 1 10 24 1 11 2 1 12 2 1 13 2 1 14 24 1 15 2 1 16 24 --------- -------- -------- 2 1 2 2 2 24 2 3 1 2 4 2 2 5 24 2 6 2 2 7 2.
OmniSwitc h Troubles hooting Guide September 2005 page -115 4 15 2 4 16 24 --------- -------- -------- 5 1 2 5 2 24 5 3 1 5 4 2 5 5 24 5 6 2 5 7 2 5 8 24 5 9 2 5 10 24 5 11 2 5 12 2 5 13 2 5 14 24 5 1.
page -116 OmniSwitch Troubleshooting Guide September 2005 25-32 0 0 0 0 0 0 0 0 0 2 1- 8 20 21 22 23 24 25 26 27 9-16 28 29 2a 2b 30 31 32 33 17-24 34 35 36 37 38 39 3a 3b 25-32 20 20 20 20 20 20 20 2.
OmniSwitc h Troubles hooting Guide September 2005 page -117 17-24 1f4 1f5 1f6 1f7 1f8 1 f9 1fa 1fb 25-32 1e0 1e0 1e0 1e0 1e0 1 e0 1e0 1e0 --- --- ----- --- --- --- --- --- - -- --- --- 1 1 1- 8 c 1c 0.
page -118 OmniSwitch Troubleshooting Guide September 2005 25-32 40 40 40 40 40 40 40 40 2 4 1- 8 6c 7c 60 60 60 60 60 60 9-16 60 60 60 60 60 60 60 60 17-24 60 60 60 60 60 6 0 60 60 25-32 60 60 60 60 6.
OmniSwitc h Troubles hooting Guide September 2005 page -119 9-16 28 29 2a 2b 30 3 1 32 33 17-24 34 35 36 37 38 3 9 3a 3b 25-32 20 20 20 20 20 2 0 20 20 3 3 1- 8 57 41 42 43 44 4 5 50 51 9-16 52 53 54 .
page -120 OmniSwitch Troubleshooting Guide September 2005 debug slb help Prints a list of all debug Server Load Bal ancing (SLB) options. debug slb help Syntax Definitions N/A Defaults N/A Platforms Support ed OmniSwit ch 7700, 780 0, 8800 Usage Guidelines • Server Load Balancin g (SLB) is not supporte d on OS-6600 series o f switches.
OmniSwitc h Troubles hooting Guide September 2005 page -121 CMMTrace <level> NITrace <level> NIDebug <slot> <sli ce> Flags Traps <enable=0|1 > SimServers <enable=0|1 &.
page -122 OmniSwitch Troubleshooting Guide September 2005 debug http sessiondb Displays the HTTP session dat abase. debug http sessiondb Syntax Definitions N/A Defaults N/A Platforms Support ed OmniSw.
OmniSwitc h Troubles hooting Guide September 2005 page -123 debug hre warn Enables and disables the Hard ware Routing En gi ne (HRE) warning messages on a specific HRE. debug hre warn {enable | disable} slot / slice Syntax Definitions enable Enables warning messages.
page -124 OmniSwitch Troubleshooting Guide September 2005 debug hre trace Enables and disables Hardw are Routing Engi ne (HRE) trace messages on a specific HRE. debug hre trace {enable | disable} slot / slice Syntax Definitions enable Enables trace messages.
OmniSwitc h Troubles hooting Guide September 2005 page -125 debug hre pcam Displays all the PCAM entries kn own on a particular slot and slice. debug hre pcam slot / slice There are two possib le arguments to this command - <start> and <count> .
page -126 OmniSwitch Troubleshooting Guide September 2005 forward[hdr=fff5] 0c003: 003a0001 c0a83a02 fff2015c 1 c00c008 [ipms] src=192.168.58.2, dak ey=0001, sgid=03a, svpn=015c forward[hdr=fff2], next=0c00 8 0c004: 00390001 c0a83902 fff1015c 1 c00c000 [ipms] src=192.
OmniSwitc h Troubles hooting Guide September 2005 page -127 debug hre pcam verbose Displays all the PCAM entries kn own on a particular slot and slice. debug hre pcam verbose slot / slice [ start count ] Syntax Definitions slot Specifies an NI slot n umber.
page -128 OmniSwitch Troubleshooting Guide September 2005 [ipms] src=192.168.60.2, dak ey=0001, sgid=03c, svpn=015c forward[hdr=fff6] mode=5, alloc=collision, pre v=0c005 agetype=leaf, current=4, bas e=4, initial=2, parent=00012 siblingprev=0c000, siblingne xt=0c002 0c002: 003b0001 c0a83b02 fff5015c 0 c000000 [ipms] src=192.
OmniSwitc h Troubles hooting Guide September 2005 page -129 debug hre pcam mode range This command displays th e range of PCAM indices assigned to each mode. debug hre pcam mode range slot / slice Syntax Definitions slot Specifies an NI slot n umber. slice Specifies an NI slice (ASIC) n umber.
page -130 OmniSwitch Troubleshooting Guide September 2005 debug hre history Displays the h istory of the Ha rdware Routin g Engine (HR E). debug hre history slot / slice Syntax Definitions slot Specifies an NI slot n umber. slice Specifies an NI slice (ASIC) n umber.
OmniSwitc h Troubles hooting Guide September 2005 page -131 Related Commands N/A.
page -132 OmniSwitch Troubleshooting Guide September 2005 debug hre error Enables/Disables erro r messages from Hardware Routin g Engine (HRE) support software on a Chassis Manageme nt Module (CMM ) for a spec ific slot/slice. debug hre error {enable | disable} slot / slice Syntax Definitions enable Enables error messages.
OmniSwitc h Troubles hooting Guide September 2005 page -133 debug hre debug Enables/Disables debug messages fro m Hardware Rout ing Engine (HRE) su pport software on a Chassis Manageme nt Module (CMM ) for a spec ific slot/slice. debug hre debug {enable | disable} slot / slice Syntax Definitions enable Enables debug messages.
page -134 OmniSwitch Troubleshooting Guide September 2005 debug hre cmm warn Enables/Disables warning messages from Hardware Routing Engine (HRE ) support software on a Chassis Manageme nt Module (CMM). debug hre cmm warn {enable | disable} Syntax Definitions enable Enables warning messages.
OmniSwitc h Troubles hooting Guide September 2005 page -135 debug hre cmm trace Enables/Disables trace me ssages from Hardware Routing Engine (HRE) support software on a Chassis Manageme nt Module (CMM). debug hre cmm trace {enable | disable} Syntax Definitions enable Enables warning messages.
page -136 OmniSwitch Troubleshooting Guide September 2005 debug hre cmm error Enables/Disables erro r messages from Hardware Routin g Engine (HRE) support software on a Chassis Manageme nt Module (CMM). debug hre cmm error {enable | disable} Syntax Definitions enable Enables warning messages.
OmniSwitc h Troubles hooting Guide September 2005 page -137 debug hre cmm debug Enables/Disables debug messages fro m Hardware Rout ing Engine (HRE) su pport software on a Chassis Manageme nt Module (CMM). debug hre cmm debug {enable | disable} Syntax Definitions enable Enables warning messages.
page -138 OmniSwitch Troubleshooting Guide September 2005 debug health Enables and disables heal th debugging. debug health {enable | disable} Syntax Definitions enable Enables health debugging.
OmniSwitc h Troubles hooting Guide September 2005 page -139 debug health cpu Displays the h istory of CPU utiliza tion on a C hassis Manageme nt Module (CMM) if no p arameters are specified and displays the hi story of the CPU’s h ealth if parameters are specified.
page -140 OmniSwitch Troubleshooting Guide September 2005 Release History Release 5.1; command was intr oduced. Related Commands debug health Enabl es and disables health debugging .
OmniSwitc h Troubles hooting Guide September 2005 page -141 debug health rx Displays health of receive utiliz ation on a particu lar slot or slot/po rt. debug health rx [ slot [/ port ]] Syntax Definitions slot Specifies an inte rface slot numb er. port Specifies an interfac e port number.
page -142 OmniSwitch Troubleshooting Guide September 2005 Related Commands N/A.
OmniSwitc h Troubles hooting Guide September 2005 page -143 debug health memory Displays histor y of memory utilization on CMM wh en no slot number is specified and displays hist ory of memory utilizati on on a particu lar sl ot if a slot number is specified.
page -144 OmniSwitch Troubleshooting Guide September 2005 Release History Release 5.1; command was intr oduced. Related Commands N/A.
OmniSwitc h Troubles hooting Guide September 2005 page -145 debug gmap flags Displays the GMAP flags a nd information about GMAP en tries in GMAP database.
page -146 OmniSwitch Troubleshooting Guide September 2005 debug console flow control Enables and disables the fl ow control for the consol e. debug console flow cont rol {enable | disable} Syntax Definitions enable Enables flow control. disable Disables flow cont rol.
OmniSwitc h Troubles hooting Guide September 2005 page -147 debug console show flow control Displays the current flow control status. debug console show flow control Syntax Definitions N/A Defaults N/.
page -148 OmniSwitch Troubleshooting Guide September 2005 debug command-info Enables and disables the comman d-info mode. debug command-info {enable | disable} Syntax Definitions enable Enables command-info mode.
OmniSwitc h Troubles hooting Guide September 2005 page -149 debug clishell data Displays the current i nformation about the sessi on. debug clishell data Syntax Definitions N/A Defaults N/A Platforms .
page -150 OmniSwitch Troubleshooting Guide September 2005 debug amap database Verifies if the AMAP database is fin e or not. debug amap database Syntax Definitions N/A Defaults N/A Platforms Support e.
OmniSwitc h Troubles hooting Guide September 2005 page -151 debug chassis show Displays all the debug configurations. debug chassis show Syntax Definitions N/A Defaults N/A Platforms Support ed OmniSwitch 6624, 6648, 7 700, 7800, 8800 Usage Guidelines N/A Examples -> debug chassis show Release History Release 5.
page -152 OmniSwitch Troubleshooting Guide September 2005 debug chassis secondary emp Enables and disables the Ethernet Management Port (EMP) port on a secondary Chassi s Management Module (CMM) debug chassis secondary emp {enable | disable} Syntax Definitions enable Enables the secondary CMM’s EMP port.
OmniSwitc h Troubles hooting Guide September 2005 page -153 debug chassis hello Enables and disables hello messages fro m the seco ndary Chassis Management Mo dule (CMM) to th e primary CMM. debug chassis hello {enable | disable} Syntax Definitions enable Enables hello messages.
page -154 OmniSwitch Troubleshooting Guide September 2005 debug chassis hello timers Enables and disables hell o timers from the primary Chass is Management Modul e (CMM) to the second- ary. If the secondary CMM does not respon d back in the interval, it is rebooted.
OmniSwitc h Troubles hooting Guide September 2005 page -155 debug chassis auto-reboot Enables and disables chassis auto-reboots after a fatal error. debug chassis auto-reboot {enable | disable | on | off} Syntax Definitions enable Enables chassis auto-reboots af ter a fatal error.
page -156 OmniSwitch Troubleshooting Guide September 2005 debug chassis auto-reboot ni Enables and disables Network Interface (NI) module auto-reboots after a fatal error. debug chassis auto-reboot ni {enable | disable} Syntax Definitions enable Enables NI auto-rebo ots after a fatal error.
OmniSwitc h Troubles hooting Guide September 2005 page -157 debug vlan vpas Displays the info rmation about al l the ports with their IfIndex and the VLAN memb ership.
page -158 OmniSwitch Troubleshooting Guide September 2005 2006 105 qtagged inactive 2006 108 qtagged inactive 2006 110 qtagged inactive 2006 111 qtagged inactive 2006 112 qtagged inactive 2006 117 qta.
OmniSwitc h Troubles hooting Guide September 2005 page -159 4001 104 qtagged inactive 4001 150 qtagged inactive 4002 1 default forwarding 4002 105 qtagged forwarding 4002 150 qtagged forwarding 6001 1.
page -160 OmniSwitch Troubleshooting Guide September 2005 13003 1 default inactive 13004 1 default inactive 13005 1 default inactive 13006 1 default inactive 13007 1 default inactive 13008 1 default i.
OmniSwitc h Troubles hooting Guide September 2005 page -161 40000001 56 qtagged forward ing 40000001 57 qtagged forward ing 40000001 58 qtagged forward ing 40000001 59 qtagged forward ing 40000001 60 .
page -162 OmniSwitch Troubleshooting Guide September 2005 debug vlan rule protocol-map Displays the p rotocol ma p available. If a proprietary prot ocol type is co nfigured on the switch that w ill also display i n the output of this command .
OmniSwitc h Troubles hooting Guide September 2005 page -163 debug vlan rule ports Displays all the ports available and can be a c andidate for VLA N rules. debug vlan rule ports Syntax Definitions N/A Defaults N/A Platforms Support ed OmniSwitch 6624, 6648, 7 700, 7800, 8800 Usage Guidelines All the ports shown as “+” are in use.
page -164 OmniSwitch Troubleshooting Guide September 2005 8/8 + - 8/9 + - 8/10 + - 8/11 + - 8/12 + - 8/13 + - 8/14 + - 8/15 + - 8/16 + - 8/17 + - 8/18 + - 8/19 + - 8/20 + - 8/21 + - 8/22 + - 8/23 + - .
OmniSwitc h Troubles hooting Guide September 2005 page -165 16/9 + + 16/10 + + 16/11 + + 16/12 + + 16/13 + + 16/14 + + 16/15 + + 16/16 + + 16/17 + + 16/18 + + 16/19 + + 16/20 + + 16/21 + + 16/22 + + 16/23 + + 16/24 + + Release History Release 5.1; command was intr oduced.
page -166 OmniSwitch Troubleshooting Guide September 2005 debug vlan rule database Displays the rules configured on the switch for Group Mob ility. debug vlan rule database Syntax Definitions N/A Defa.
OmniSwitc h Troubles hooting Guide September 2005 page -167 debug vlan rule communication Displays the communic ation of the Chassis Management Module (CM M) with all the software mod ules and all Network Interface (NI) modules for synchronizing the ru les configured on the CMM.
page -168 OmniSwitch Troubleshooting Guide September 2005 GlobSlice: 5 skt=0x130 rslot=6 rslice=0 rapp=9 rsnp=2 CNXNLESS state:RX GlobSlice: 6 skt=0x130 rslot=7 rslice=0 rapp=9 rsnp=2 CNXNLESS state:R.
OmniSwitc h Troubles hooting Guide September 2005 page -169 debug vlan communication Displays the commu nication of the Chassis mana gement Module (CMM) with all the software modules and all Network Interf ace (NI) modules.
page -170 OmniSwitch Troubleshooting Guide September 2005 defaults assumed=0 txrty=0 txfail=0 bfrty=0 SNMP sid= 1d rap= 68 rsp = 4 CNXNLESS NO-RX notify=0 defaults assumed=0 txrty=0 txfail=0 bfrty=0 W.
OmniSwitc h Troubles hooting Guide September 2005 page -171 IPMS VL sid= 32 rap= 17 rsp = 34 CNXN-OR ESTABLISHED notify=80 defaults assumed=0 txrty=0 txfail=0 bfrty=0 QOS sid= 31 rap= 13 rsp = 2 CNXN-.
page -172 OmniSwitch Troubleshooting Guide September 2005 Related Commands N/A.
OmniSwitc h Troubles hooting Guide September 2005 page -173 debug port information Displays all the informa tion related to an i nterface. It includ es the counters, mobil e port configuration, ta g, aggregate, phy, LED, and MAC related informatio n debug port information slot / port Syntax Definitions slot Specifies an inte rface slot numb er.
page -174 OmniSwitch Troubleshooting Guide September 2005 debug qos Configures th e type of QoS ev ents that will be displayed in the QoS log. debug qos [info] [config] [rule] [main] [route] [hre] [po.
OmniSwitc h Troubles hooting Guide September 2005 page -175 egress Logs information about packets leavin g the switch. rsvp Logs information about RSVP flows. Current ly not supported. balance Logs information a bout flows tha t are part of a lo ad balancing cluster.
page -176 OmniSwitch Troubleshooting Guide September 2005 debug systrace Enables or disables sysTrace lo gging. The syst em trace, or sysTrace , facil ity provide s a consistent, high- level mechanism fo r capturing even t records in a hist ory buffer.
OmniSwitc h Troubles hooting Guide September 2005 page -177 Related Commands MIB Objects N/A debug ktrace Enables or disables kT race logging. debug ktrace appid level Adds or removes a kT race captur e level for a specified subsystem. debug ktrace show Displays current kT race parameters.
page -178 OmniSwitch Troubleshooting Guide September 2005 debug systrace watch Enables the sysTrace log on the console, or turns of f (disables) the console di splay.
OmniSwitc h Troubles hooting Guide September 2005 page -179 debug systrace show Displays sysTrace debug log informa tion (e.g., sysTrace status , Appl ication IDs with non-default Severity Level settings).
page -180 OmniSwitch Troubleshooting Guide September 2005 Related Commands MIB Objects N/A debug ktrace Enables or disables kT race logging. debug ktrace appid level Adds or removes a kT race captur e level for a specified subsystem. debug ktrace show Displays current kT race parameters.
OmniSwitc h Troubles hooting Guide September 2005 page -181 debug systrace appid level Adds or removes a sysTrace capture level for a specified appli cation ID (i.e., subsystem). debug systrace appid { app_id | integer } level { level | integer } debug systrace no appid app_id Syntax Definitions app_id An applicatio n ID keyword value.
page -182 OmniSwitch Troubleshooting Guide September 2005 Defaults Platforms Support ed OmniSwitch 6624, 6648, 7 700, 7800, 8800 Usage Guidelines • You may enter more t han one applica tion ID in the co mmand line. Sep arate each appli cation ID with a space.
OmniSwitc h Troubles hooting Guide September 2005 page -183 debug systrace show log Displays sysTrace log information. debug systrace show log [ file ] Syntax Definitions file Specifies a particular fi le from which sysTrace lo g information will be displayed.
page -184 OmniSwitch Troubleshooting Guide September 2005 Output fields are descr ibed here: Release History Release 5.1; command was intr oduced. Related Commands MIB Objects N/A output definitions Tim e s t a mp The timestamp indicating when the sy sT race log entry occ urred.
OmniSwitc h Troubles hooting Guide September 2005 page -185 show log pmd Displays the contents of a stored Post Mortem Dump (PMD) file. The PMD file is a diagnostic aid that stores system information fo llowing some p recipitating ev ent (e.g., a system error).
page -186 OmniSwitch Troubleshooting Guide September 2005 Record Type -> MemoryData Address - > 1b2b74 Size -> c4 0 0 0 7 0 6e 31 3d 3 3e df 5 0 0 37 54 0 0 18 b6 0 0 11 87 0 0 7a 88 0 0 2c 4.
OmniSwitc h Troubles hooting Guide September 2005 page -187 Registration Type ->Task Task No. ->3571290 Record Type -> UserDefined Task Id -> 3571290 Address -> 1adcc38 Size -> 10 46 69 72 73 74 20 69 74 65 72 61 74 69 6f 6e a ------------------------------------ ------------------------- Registration Type ->Task Task No.
page -188 OmniSwitch Troubleshooting Guide September 2005 Output fields are descr ibed here: Release History Release 5.1; command was intr oduced. Related Commands N/A MIB Objects N/A output definitions PMD V ersion The Post Mortem Dump (PMD) version ID.
OmniSwitc h Troubles hooting Guide September 2005 page -189 debug memory monitor Enables or disab les memory monito ring function s. debug memory monitor {enable | disable} Syntax Definitions enable Enables memory monitoring. disable Disables memory monitoring.
page -190 OmniSwitch Troubleshooting Guide September 2005 debug memory monitor show status The debug memory monitor sho w status command d isplays memory moni toring status inf ormation.
OmniSwitc h Troubles hooting Guide September 2005 page -191 debug memory monitor show log Displays memory moni toring log info rmation. debug memory monitor show log Syntax Definitions N/A Defaults N/.
page -192 OmniSwitch Troubleshooting Guide September 2005 CliShell0 02314da8 272 02b33a3c malloc SSYaccStac SS YaccInit CliShell0 023183d8 512 02b33a3c malloc CliParse cl ishell_m CliShell0 027b0100 5.
OmniSwitc h Troubles hooting Guide September 2005 page -193 Related Commands MIB Objects N/A debug memory monitor Enables or disab les memory monitori ng functions. debug memory monitor show log global Displays memory monito ring global stat istics. debug memory monitor show log task Displays memory monito ring task statistics.
page -194 OmniSwitch Troubleshooting Guide September 2005 debug memory monitor show log global Displays memory monito ring global stat istics. debug memory monitor show log glob al Syntax Definitions .
OmniSwitc h Troubles hooting Guide September 2005 page -195 Related Commands MIB Objects N/A debug memory monitor Enables or disab les memory monitori ng functions. debug memory monitor show log Displays memory moni toring log info rmation. debug memory monitor show log task Displays memory monito ring task statistics.
page -196 OmniSwitch Troubleshooting Guide September 2005 debug memory monitor show log task Displays memory monitorin g task statistics. debug memory monitor show log task Syntax Definitions N/A Defa.
OmniSwitc h Troubles hooting Guide September 2005 page -197 Health 249 127649 AAA 221312 222236 Ipedr 31500 105868 NanDrvr 56 74396 Ftpd 56 56 Telnetd 9552 9552 tCS_CVM 28 28 tssApp65535_3 228 228 SsA.
page -198 OmniSwitch Troubleshooting Guide September 2005 debug memory monitor show log size Displays memory monito ring size statistics. debug memory monitor show log size Syntax Definitions N/A Defa.
OmniSwitc h Troubles hooting Guide September 2005 page -199 Release History Release 5.1; command was intr oduced. Related Commands MIB Objects N/A debug memory monitor Enables or disab les memory monitori ng functions. debug memory monitor show log Displays memory moni toring log info rmation.
page -200 OmniSwitch Troubleshooting Guide September 2005 debug ktrace Enables or disables kTrace lo gg ing. The kernel trace, or kTrac e , facility p rovides a c onsistent, lo w-level mechanism for captu ring integer-ba sed event records i n a history buffer.
OmniSwitc h Troubles hooting Guide September 2005 page -201 Related Commands MIB Objects N/A debug ktrace appid level Adds or removes a kT race captur e level for a specified subsystem. debug ktrace show Displays current kT race parameters. debug ktrace show log Displays kT race log information.
page -202 OmniSwitch Troubleshooting Guide September 2005 debug ktrace show Displays current kTrace pa rameters (e.g., kTrace stat us, Applicatio n IDs with non-default Severi ty Level settings).
OmniSwitc h Troubles hooting Guide September 2005 page -203 Related Commands MIB Objects N/A debug ktrace Enables or disables kT race logging. debug ktrace appid level Adds or removes a kT race captur e level for a specified subsystem. debug ktrace show log Displays kT race log information.
page -204 OmniSwitch Troubleshooting Guide September 2005 debug ktrace appid level Adds or removes a kTrace capture level for a specified application ID (i.e., subsystem). debug ktrace appid { app_id | integer } level { lev el | integer } debug ktrace no appid app_id Syntax Definitions app_id An applicatio n ID keyword value.
OmniSwitc h Troubles hooting Guide September 2005 page -205 Defaults Platforms Support ed OmniSwitch 6624, 6648, 7 700, 7800, 8800 Usage Guidelines • You may enter more t han one applica tion ID in the co mmand line. Sep arate each appli cation ID with a space.
page -206 OmniSwitch Troubleshooting Guide September 2005 debug ktrace show log Displays kTrace log informati on. debug ktrace show log [ file ] Syntax Definitions file Specifies a particular file from which k Trace log information will be displayed.
OmniSwitc h Troubles hooting Guide September 2005 page -207 Output fields are descr ibed here: Release History Release 5.1; command was intr oduced. Related Commands MIB Objects N/A output definitions Event The event for whic h kT race log information is displayed.
page -208 OmniSwitch Troubleshooting Guide September 2005.
OmniSwitc h Troubles hooting Guide September 2005 page -1 C T echnical Suppor t Commands This chapter describes Techn ical Support Comman d Line Interface (CLI) show commands that cr eate log files of the output fro m multiple standard CLI show commands.
page -2 OmniSwitch Troubleshooting Guide September 2005 show tech- s upport Creates a log file of the output of several sy stem-wide C ommand Line Interface (CLI) commands.
OmniSwitc h Troubles hooting Guide September 2005 page -3 show tech- support layer2 Creates a log file of the output of several Layer 2 Command Line Interfac e (CLI) commands.
page -4 OmniSwitch Troubleshooting Guide September 2005 show tech- support layer3 Creates a log file of the output of several Layer 3 Command Line Interfac e (CLI) commands.
OmniSwitc h Troubles hooting Guide September 2005 page -5 show tech- support layer3 rip Creates a log file of the outp ut of several Rout in g Information Protocol (RIP ) Command Line Interface (CLI) commands.
page -6 OmniSwitch Troubleshooting Guide September 2005 show tech- support layer3 pimsm Creates a log file of the output of several Prot ocol-Independent Multicast Sparse Mode (PIM-SM) Command Line Interface (CLI) commands.
OmniSwitc h Troubles hooting Guide September 2005 page -7 show tech- support layer3 ospf Creates a log file of the output of several Open Sh ortest Path First ro uting (OSPF) Command Line Inter- face (CLI) commands.
page -8 OmniSwitch Troubleshooting Guide September 2005 show tech- support layer3 mroute Creates a log file of t he output of several mult icast routing Command Line Interface (CLI) commands.
OmniSwitc h Troubles hooting Guide September 2005 page -9 show tech- support layer3 ipx Creates a log file of the output of several Internet Pack et Exchange (IPX) protocol Command Line Inter- face (CLI) commands.
page -10 OmniSwitch Troubleshooting Guide September 2005 show tech- support layer3 dvmrp Creates a log file of the output of several Dist ance Vector Multicast Routing Protoco l (DVMRP) Command Line Interface (CLI) commands.
OmniSwitc h Troubles hooting Guide September 2005 page -11 show tech- support layer3 bgp Creates a log file of the output of several Border Gateway Protocol (BGP) Comma nd Line Interface ( CLI) commands.
page -12 OmniSwitch Troubleshooting Guide September 2005.
OmniSwitc h Troubles hooting Guide September 2005 page -1 D Modifying Files with VI Editor The switch has a b uilt in Unix te xt editor calle d VI. This section covers some basic VI commands and ho w to use VI to modify th e IP address of the EMP (Ethernet Management Port), which is stored in the boot.
Useful VI Commands page -2 OmniSwitch Troubleshooting Guide September 2005 Useful VI Commands The following are some useful VI comma nds: u - undo the last command. CTL/L -reprint current screen. CTL/F -pages forwar d one scre en. CTL/B -pages ba ck one sc reen.
Sample VI Session OmniSwitc h Troubles hooting Guide September 2005 page -3 Dew - Deletes the curre nt word. P - Puts back text from previo us delete. yy -Puts the current line in buffe r; leaves th e current line in tact. p -Places the line in the buffer afte r the current posi tion of the cursor.
Sample VI Session page -4 OmniSwitch Troubleshooting Guide September 2005.
OmniSwitc h Troubles hooting Guide September 2005 Index-1 Index Numerics 802.1Q Debug commands B-6 A AMAP Debug commands B-150 ASICs Catalina A-2 Coronado A-5, A-7 fabric ASICs A-16 Firenze A-4 Layer .
page -2 OmniSwitch Troubleshooting Guide September 2005 show show ip rip redis t command 12-14 show spantr ee c ommand 4-2, 7-4 show spantree ports command 4-3 show stack topology command 1-4 show swl.
OmniSwitc h Troubles hooting Guide September 2005 page -3 la_ni_lacp_stats_prt command 7-9 la_pm_port_prt command 7-7 lagg_Sock_cmm_boardupprint command 7-7 nanListMapping command A-42 pmdi_generate c.
page -4 OmniSwitch Troubleshooting Guide September 2005 V VI editor D-1 VLANs Debug commands B-157.
An important point after buying a device Alcatel 6624 (or even before the purchase) is to read its user manual. We should do this for several simple reasons:
If you have not bought Alcatel 6624 yet, this is a good time to familiarize yourself with the basic data on the product. First of all view first pages of the manual, you can find above. You should find there the most important technical data Alcatel 6624 - thus you can check whether the hardware meets your expectations. When delving into next pages of the user manual, Alcatel 6624 you will learn all the available features of the product, as well as information on its operation. The information that you get Alcatel 6624 will certainly help you make a decision on the purchase.
If you already are a holder of Alcatel 6624, but have not read the manual yet, you should do it for the reasons described above. You will learn then if you properly used the available features, and whether you have not made any mistakes, which can shorten the lifetime Alcatel 6624.
However, one of the most important roles played by the user manual is to help in solving problems with Alcatel 6624. Almost always you will find there Troubleshooting, which are the most frequently occurring failures and malfunctions of the device Alcatel 6624 along with tips on how to solve them. Even if you fail to solve the problem, the manual will show you a further procedure – contact to the customer service center or the nearest service center
