Part No. 031496-00, Rev. C September 2005 OmniSwitch 6624/6648/ 6800/7700/7800/8800 Troubleshooting Guide www.alcatel.
This troubleshooting guide documents OmniSwitch 6624/6648/770/7800/8800 hardware, including chassis and associated components, and Release 5.1 software. The specifications described in this guide are subject to change without notice. Copyright © 2006 by Alcatel Internetworking, Inc. All rights reserved. This document may not be reproduced in whole or in part without the express written permission of Alcatel Internetworking, Inc. Alcatel® and the Alcatel logo are registered trademarks of Alcatel.
Contents About This Guide .........................................................................................................xv Supported Platforms ......................................................................................................... xv Who Should Read this Manual? ...................................................................................... xvi When Should I Read this Manual? ..................................................................................
Verify Source Learning ...................................................................................................2-6 Verify Switch Health .......................................................................................................2-7 Verify ARP ......................................................................................................................2-7 Using the Log File ..........................................................................................................
GMIGBPDU ....................................................................................................4-16 GM2FIXED .....................................................................................................4-17 VMADDVPA ..................................................................................................4-17 VMDELVPA ...................................................................................................4-17 VMDEFVPA .................................................
Troubleshooting a DNS Failure ......................................................................................6-2 Starting the Troubleshooting Procedure ...................................................................6-2 Layer 7 DNS or Name Resolution Issue ..................................................................6-2 DNS Configuration Considerations ................................................................................6-3 Chapter 7 Troubleshooting Link Aggregation ..............
Dshell ..............................................................................................................................9-6 NI Debug Dshell .......................................................................................................9-6 6800 Group Mobility Troubleshooting ...........................................................................9-7 show vlan rules .........................................................................................................9-7 gmHelp .....
Dshell Troubleshooting .................................................................................................11-8 Viewing the ARP Table on OmniSwitch 6624/6648 Switches ............................11-10 Chapter 12 Troubleshooting IP Routing ................................................................................... 12-1 In This Chapter ..............................................................................................................12-2 Introduction .........................
Dshell Troubleshooting .................................................................................................14-9 Chapter 15 Troubleshooting DVMRP ........................................................................................ 15-1 In This Chapter ..............................................................................................................15-1 Introduction ..................................................................................................................
Multicast Group Status is Shown as Disabled .....................................................16-27 PIM-SM Limitations ............................................................................................16-28 Upstream Neighbor/Next Hop Debug Commands ...............................................16-28 Chapter 17 Troubleshooting Server Load Balancing ........................................................... 17-1 In This Chapter .................................................................
Chapter 19 Troubleshooting 802.1X ......................................................................................... 19-1 In This Chapter ..............................................................................................................19-1 Troubleshooting with the CLI .......................................................................................19-2 Troubleshooting Using Debug CLI ...............................................................................
Calendar Manager Module .................................................................................... A-19 Data Port Output Module ...................................................................................... A-19 Nantucket Redundancy ......................................................................................... A-19 Roma ............................................................................................................................ A-22 Functional Description ........
Bus Mapping on OmniSwitch 7700/7800/8800 Switches ........................................... A-42 Xybus Mapping ..................................................................................................... A-42 Fbus Mapping ........................................................................................................ A-42 Falcon (OmniSwitch 7700/7800) Fbus Mapping ........................................... A-42 Eagle (OmniSwitch 8800) Fbus Mapping ........................................
xiv OmniSwitch Troubleshooting Guide September 2005
About This Guide This OmniSwitch Troubleshooting Guide describes how to use Command Line Interface (CLI) and Dshell commands available on the OmniSwitch 6600 Family, OmniSwitch 6800 Series, OmniSwitch 7700/7800, and the OmniSwitch 8800 to troubleshoot switch and network problems.
Note. Troubleshooting documentation for legacy products (e.g., Omni Switch/Router) can be downloaded at http://support.ind.alcatel.com/releasefiles/indexpage.cfm. Who Should Read this Manual? The principal audience for this user guide is Service and Support personnel who need to troubleshoot switch problems in a live network.
• Related commands. • Release history, which indicates the release when the command was introduced. Appendix D provides a list of useful VI editor commands and a sample VI session that modifies the boot.params file. What is Not in this Manual? This guide is intended for troubleshooting switches in live networks. It does not provide step-by-step instructions on how to set up particular features on the switch or a comprehensive reference to all CLI commands available in the OmniSwitch.
• OmniSwitch 6800 Series Hardware Users Guide Complete technical specifications and procedures for all OmniSwitch 6800 chassis, power supplies, fans, uplink modules, and stacking modules. • OmniSwitch 7700/7800 Hardware Users Guide Complete technical specifications and procedures for all OmniSwitch 7700 and 7800 chassis, power supplies, fans, and Network Interface (NI) modules.
• OmniSwitch 7700/7800/8800 Network Configuration Guide Includes network configuration procedures and descriptive information on all the major software features and protocols included in the base software package. Chapters cover Layer 2 information (Ethernet and VLAN configuration), Layer 3 information (routing protocols, such as RIP and IPX), security options (authenticated VLANs), Quality of Service (QoS), link aggregation, and server load balancing.
Before Calling Alcatel’s Technical Assistance Center Before calling Alcatel’s Technical Assistance Center (TAC), make sure that you have read through the appropriate section (or sections) and have completed the actions suggested for your system’s problem. Additionally, do the following and document the results so that the Alcatel TAC can better assist you: • Have a network diagram ready. Make sure that relevant information is listed, such as all IP addresses and their associated network masks.
1 Troubleshooting the Switch System In order to troubleshoot the system, a basic understanding of the operation of Chassis Management Modules (CMMs) and their interaction with Network Interface (NI) modules is required. Some concepts are covered in this chapter: • Understanding of the “Diagnosing Switch Problems” chapter in the appropriate OmniSwitch Switch Management Guide. • Understanding of the “Using Switch Logging” from the appropriate OmniSwitch Network Configura- tion Guide is highly recommended.
Introduction Troubleshooting the Switch System Introduction The CMM is the Management Module of the switch. All of the critical operations of the switch including the monitoring is the responsibility of the CMM. CMM not only provides monitoring but also synchronizes all of the NI for different operations. The operation of the CMM is the same in OS-6/7/8XXX switches. The only difference is that OS-6/7XXX has the switching fabric inherent to the module whereas OS-8800 has fabric at the back of the chassis.
Troubleshooting the Switch System Troubleshooting System for OS-6624/6648 and OS-7/8XXX Troubleshooting System for OS-6624/6648 and OS-7/8XXX If the switch is having any problems the first place to look for is the CMM. All the task are supervised by CMM. Any in coherency between CMM and the NI can cause problems to appear. 1 The first step for troubleshooting problems with the switch is to look at the overall general health of the switch.
Troubleshooting System for OS-6624/6648 and OS-7/8XXX Troubleshooting the Switch System NI-2 UP POWER ON N/A 00:d0:95:84:3d:26 NI-3 UP POWER ON N/A 00:d0:95:86:50:f4 NI-4 UP POWER ON N/A 00:d0:95:84:49:be NI-5 UP POWER ON N/A 00:d0:95:84:39:be NI-6 UP POWER ON N/A 00:d0:95:84:4a:90 NI-7 UP POWER ON N/A 00:d0:95:84:39:f4 NI-8 UP POWER ON N/A 00:d0:95:84:3c:44 OmniSwitch 6600 with 8 stackable switches show up.
Troubleshooting the Switch System Troubleshooting System for OS-6624/6648 and OS-7/8XXX Hardware Revision: Serial Number: Manufacture Date: Firmware Version: Admin Status: Operational Status: , B42N101P2, OCT 18 2001, , POWER ON, UP Make sure that all the known good power supplies are operational.
Troubleshooting System for OS-6624/6648 and OS-7/8XXX Troubleshooting the Switch System Power Supplies in chassis 8 PS Operational Status -----+------------------PS-1 UP PS-2 NOT PRESENT Make sure that all the known good power supplies are operational. 3 Verify the CPU utilization.
Troubleshooting the Switch System Troubleshooting System for OS-6624/6648 and OS-7/8XXX The average on one minute is calculated from the average of 12 samples. Each sample is an average of the CPU utilization during 5 seconds. Those values are stored in a table. The current minute (1 Min Avg or “min”) displays the average of the last 12 samples. Every 60 seconds the average of the 12 samples is recorded into the average value for this minute.
Troubleshooting System for OS-6624/6648 and OS-7/8XXX d on NI slot 1, GBIC port 2 MON AUG 21 23:28:39 2023 HSM-CHASSIS ed on NI slot 5, GBIC port 2 MON AUG 21 23:30:39 2023 HSM-CHASSIS d on NI slot 5, GBIC port 2 MON AUG 21 23:30:41 2023 HSM-CHASSIS ed on NI slot 1, GBIC port 1 MON AUG 21 23:30:45 2023 HSM-CHASSIS ed on NI slot 1, GBIC port 2 TUE AUG 22 00:05:45 2023 CSM-CHASSIS TUE AUG 22 00:05:45 2023 CSM-CHASSIS TUE AUG 22 00:05:53 2023 SYSTEM restart type=0x2 (COLD) Troubleshooting the Switch System
Troubleshooting the Switch System Advanced Troubleshooting Advanced Troubleshooting One level of switch logging is stored in the two log files located in the /flash directory. There is another low level debug that can be enabled and used for diagnosing the problems. This debug is known as “systrace”, meaning system trace. The information in this trace is stored in NVRAM on the CMM, so it is valid until powered off.
Advanced Troubleshooting _SM_IPCUP_TIMEOUT 3349118948 CSM-CH 3345200526 CSM-CH 3342928783 CSM-CH 3342928661 CSM-CH _SM_IPCUP_TIMEOUT 3342928628 CSM-CH 3336738410 CSM-CH 3336738287 CSM-CH _SM_IPCUP_TIMEOUT 3336738256 CSM-CH 3334849145 CSM-CH 3330548020 CSM-CH 3330547902 CSM-CH _SM_IPCUP_TIMEOUT 3330547869 CSM-CH 3324495309 CSM-CH 3324357940 CSM-CH 3324357816 CSM-CH _SM_IPCUP_TIMEOUT 3324357782 CSM-CH 3318167293 CSM-CH 3318167171 CSM-CH _SM_IPCUP_TIMEOUT 3318167139 CSM-CH Troubleshooting the Switch System
Troubleshooting the Switch System Dshell Troubleshooting Dshell Troubleshooting To further diagnose the task consuming the CPU on the CMM one needs to use the following Dshell commands: Note. Dshell commands should only be used by Alcatel personnel or under the direction of Alcatel. Misuse or failure to follow procedures that use Dshell commands in this guide correctly can cause lengthy network down time and/or permanent damage to hardware.
Dshell Troubleshooting GrpMob Stp 8021q LnkAgg tSlcMsgHdl AmapMgr GmapMgr PMirMon Ipedr AAA stpTick tIpedrPkt AVLAN onex Ipmem la_cmm_tick ipmfm ipmpm Ipx Vrrp UdpRly Qos PolMgr SlbCtrl WebView SNMP GTW SNMP TIMER GmapTimer DrcTm tDrcIprm tOspf tPimsm tDrcIpmrm cliConsole tWebTimer tssApp_SNMP_ tssApp_3_4 CfgMgr tCS_CCM2 Sshd Telnetd Rmon tCS_CVM SmNiMgr tIpxTimer tIpxGapper SesMon_3 tTelnetOut0 tTelnetIn0 CliShell0 tPolMonSvr tDcacheUpd KERNEL INTERRUPT IDLE TOTAL page 1-12 Troubleshooting the Switch Sy
Troubleshooting the Switch System Dshell Troubleshooting 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. Check to see if any of the task is suspended on the CMM.
Dshell Troubleshooting Troubleshooting the Switch System %o0 = 490f9e0 %o1 %o3 = 0 %o4 %sp = 490f920 %o7 value = 76612560 = 0x49103d0 Certified: [Kernel]-> = = = 0 0 0 %o2 %o5 = = 0 0 To troubleshoot a CPU or memory spike with 5.1.5.X, you can start a software routine in dshell and it will log the task name to the swlog whenever there is a spike in CPU or memory usage.
Troubleshooting the Switch System Dshell Troubleshooting tAioIoTask0 Asynchronous I/O Support tNetTask Routing Task tIpedrMsg IP Ethernet Driver Message Handle Task tAioWait Asynchronous I/O Support bbussIntMoni BBUS monitor Task ipc_monitor IPC monitor Task tL2Stat L2 statistics gathering task Gateway Management Information Protocol Gateway EIpc Extended IPC task EsmDrv Ethernet switching manager Driver Task tMemMon Memory Monitor Task tCS_PTB Chassis Supervision Pass-through Suppo
Dshell Troubleshooting Troubleshooting the Switch System Health Health Task L3Hre Layer 3 HRE Task DbgNiGw NI Debug support SrcLrn Source Learning Task GrpMob Group Mobility Task Stp Spanning Tree Task 8021q 802.
Troubleshooting the Switch System Dshell Troubleshooting DrcTm Dynamic Routing Control Timer Task tDrcIprm Dynamic Routing Control Task for IP Route Manager tOspf OSPF Task tPimsm PIM SIM Task tDrcIprm Dynamic Routing Control IP Route Manager task cliConsole CLI Console Task tWebTimer Web Session Timer tssApp_SNMP Temporary System Services task to support SNMP tssApp_3_4 Temporary System Services task to support CLI CfgMgr Configuration Manager Task tCS_CCM2 Chassis Configuration Mana
Dshell Troubleshooting Troubleshooting the Switch System tIpedrMsg IP Ethernet Driver Task Message handler tahw_sch Spanning Tree Support qdsUnr Queue Dispatcher of unresolved queues taSM_DVR NI Stack Manager ipcReceive IPC Receive Task taSM_NI NI Stack Manager la_ni_tick_ NI Link Aggregation Timer tahw_stp Spanning Tree Support IPCHAWKTIME IPC Timer ipc_monitor IPC monitor task tNiSup&Prb NI supervision and Prober task tL2Stat L2 statistics gathering task taEipc Extended IPC task
Troubleshooting the Switch System Dshell Troubleshooting taNiEsmDrv NI Ethernet switching driver task tsLnkState Link State monitor task PortMgr Port manager task PsMgr Power supply Manager task VlanMgr VLAN Manager task TrapMgr Trap manager task SM_CMM CMM Stack Manager PartMgr Partition Manager task SNMPagt SNMP agent SNMP GTW SNMP Gateway SNMP TIMER SNMP Agent Timer SesMgr Session Manager Task SsApp Session Application Task Ntpd NTP Daemon Task Health Health Monitor task E
Dshell Troubleshooting Troubleshooting the Switch System onex 802.1X Vrrp VRRP task UdpRly UDP Relay task Qos CMM QOS PolMgr Policy Manager task Ipmem IP Multicast Task ipmfm IP Multicast Forwarding ipmpm IP Multicast Management DrcTm Dynamic Routing Control Timer task TDrcIprm Dynamic Routing Control IP Route Manager task taDot1q_ 802.
Troubleshooting the Switch System Dshell Troubleshooting tCS_CVM Chassis Version Manager SesMon_12 Session Monitor tTelnetOut0e4208c Telnet Outgoing tTelnetIn0 Telnet Incoming CliShell0 CLI session 0 shell Task tPolMonSvr Policy Manager Monitor LDAP Servers tDcacheUpd FPGA Support To further qualify the source of the problem we need to look at each and every NI.
Dshell Troubleshooting 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 0160cef8 015f61d0 015ee670 015f7768 015f4080 015ed4c0 017fb470 017f8fb8 017f6290 01602bf8 01601e30 01601450 015fed08 015fbc18 015fa088 015f0f90 015eb370 015e70d0 015e47b0 015e2e30 015e1030 015c09e0 015a2b28 015a16d0 015a0ca0 01593e98 01590da8 014f5e80 014f4cd0 t_ipc_cmm_p taL3Hre taXMAP_ni taStp taQoS taIpms tExcTask tDBG_sp_tk tNiSup&Prb taHw_qdrv taI
Troubleshooting the Switch System Dshell Troubleshooting OmniSwitch 6624/6648 Dshell Troubleshooting One of the important things in OS-6600 is to confirm the stack topology.
Dshell Troubleshooting Troubleshooting the Switch System output definitions (continued) Local Mac Local Mac address used for IPC communication across the stacking cables. Role Primary or Secondary. Nb Neighbor ID (1-Based). In_loop 1 if the stacks are connected in a loop for redundant path. Neighbor1 Shows the connections to other stacks through the port number. Topology Role 1=Primary, 2= Secondary, 3=Idle. Topology Outport Displays the port used to access the other stacks.
Troubleshooting the Switch System Dshell Troubleshooting NI=4 CMM=0 role=3 * state_linkA=1 remote_slotA=5 remote_linkA=51 * state_linkB=1 remote_slotB=3 remote_linkB=28 NI=5 CMM=0 role=3 * state_linkA=1 remote_slotA=4 remote_linkA=51 * state_linkB=1 remote_slotB=6 remote_linkB=52 NI=6 CMM=0 role=3 * state_linkA=1 remote_slotA=7 remote_linkA=51 * state_linkB=1 remote_slotB=5 remote_linkB=52 NI=7 CMM=0 role=3 * state_linkA=1 remote_slotA=6 remote_linkA=51 * state_linkB=1 remote_slotB=8 remote_linkB=52 NI=8
Using AlcatelDebug.cfg Troubleshooting the Switch System In stacking environment, only the primary and secondary switches have console enabled whereas console is disabled for the idle switches. To enable the Dshell access to the idle switches use the following command on primary stack: Nisup_control_WW_on slot You must execute this command on each idle switch in the stack. Please note that these switches will not allow to exit with the exit command.
Troubleshooting the Switch System Troubleshooting IPC on OS-6/7/8XXX Series of Switches Troubleshooting IPC on OS-6/7/8XXX Series of Switches IPC (Inter Process Communication) is should by the system to communicate between different software modules. This communication can be between different processes in the same software module or between two entirely separate modules. This process can be between NI and CMM or between CMM to CMM.
Troubleshooting IPC on OS-6/7/8XXX Series of Switches Troubleshooting the Switch System LocalPool: Full size is 64, remaining: 64 In socket queues: 0 Not queued: 0: In DMA queues: 0 Each type of pool has the following listed in the command output: • Maximum size of buffers available • Currently available buffers • Socket Queues being used • Not Queued in pool • Direct Memory Access Queues Currently available buffers should always be around the maximum available in normal operation.
Troubleshooting the Switch System Troubleshooting IPC on OS-6/7/8XXX Series of Switches LocalPool: Full size is 64, remaining: 64 In socket queues: 0 Not queued: 0: DMA queues: 0 In the above two outputs it seems that the control pool is stuck and the socket queues are incrementing. In order to find out which task is using these queues we need to look at the socket information.
Troubleshooting IPC on OS-6/7/8XXX Series of Switches Troubleshooting the Switch System value = 10 = 0xa Working: [Kernel]-> The above command displays a lot of information but we are interested in the most repeating socket ID. In the above example it is 0x8.
Troubleshooting the Switch System Troubleshooting IPC on OS-6/7/8XXX Series of Switches Now doing a task trace on this task can be helpful to see if the task is moving: Working: [Kernel]->tt 0x67f3c10 108e9c vxTaskEntry +c : Letext (&dataInfo, 67f3920, 67f3a20, 34000000, 66ff8 00, 6a69800) 66b69b4 Letext +2d4: zcSelect (5, 67f3a20, 0, 0, 6a6c800, 247) 6ff56f8 zcSelect +458: semTake (67eedc0, ffffffff, a, 28, a, 0) 158b4c semTake +2c : semBTake (67eedc0, ffffffff, &semTakeTbl, 0, &semBTa ke, 264c00) value
Troubleshooting IPC on OS-6/7/8XXX Series of Switches Troubleshooting the Switch System LocalPool: Full size is 0, remaining: 1024 In socket queues: 0 Not queued: 0: In DMA queues: 0 value = 6 = 0x6 The above display of the command does not show the Full size of any of the pools. This indicates that CMM is unable to view the IPC pools of the NI. In this scenario, one needs to load the NI Debugger and go to the NI and look at the IPC Pools.
Troubleshooting the Switch System Troubleshooting IPC on OS-6/7/8XXX Series of Switches 631908 next = 0x17c8c44, pFreeQ = 0x2fc7a8, data_offset = 0, free_list_num = 6 Socket ID = 0x19, dest slot = 2, remote addr = 0x3030002, ipc status = S Task ID = 0x17fd170, PayLoad Len= 128, ipc priority = 0x1, data ptr = 0x1 632108 next = 0x17caab0, pFreeQ = 0x2fc7a8, data_offset = 0, free_list_num = 6 Socket ID = 0x19, dest slot = 2, remote addr = 0x3030002, ipc status = S Task ID = 0x17fd170, PayLoad Len= 128, ipc p
Troubleshooting IPC on OS-6/7/8XXX Series of Switches Troubleshooting the Switch System nidbg> tt 0x15f7768 1e6ce0 vxTaskEntry +c : stp_task_entry (0, 0, 0, 0, 0, 0) f22e8 stp_task_entry +80 : stpNISock_start (22bc00, 22bea0, 22bdc4, 3, 22bd f4, 3) Multiple task trace of the task with IPC Pools should be taken. This process might have to be repeated on multiple NI in order to find out the cause of the problem and identify the NI causing the problem to happen.
Troubleshooting the Switch System Troubleshooting IPC on OS-6/7/8XXX Series of Switches Socket ID = 0x100, dest slot = 5, remote addr = 0x5400042, ipc status = S Task ID = 0x7571700, PayLoad Len= 812, ipc priority = 0x1, data ptr = 0x6cfe3 a0 next = 0x739b810, pFreeQ = 0x74fb4e0, data_offset = 0, free_list_num = 6 Socket ID = 0x100, dest slot = 65, remote addr = 0x8440041, ipc status = S Task ID = 0x7571700, PayLoad Len= 812, ipc priority = 0x1, data ptr = 0x6cfeb a0 next = 0x7396da4, pFreeQ = 0x74fb4e0,
Port Numbering Conversion Overview Troubleshooting the Switch System Port Numbering Conversion Overview The sections below document how to convert port number parameters. Note. Dshell commands should only be used by Alcatel personnel or under the direction of Alcatel. Misuse or failure to follow procedures that use Dshell commands in this guide correctly can cause lengthy network down time and/or permanent damage to hardware.
Troubleshooting the Switch System Port Numbering Conversion Overview Note that 1 is the uport number. Output similar to the following will be displayed: 8:0 8:0 Valid 8:0 in LSM 8:0 ---------- Port Numbers 8:0 Slot 8:0 Slice 8:0 Mac 8:0 Bus 8:0 phy 8:0 gport 8:0 lport 8:0 iport 8:0 pport 8:0 uport 1 0 -----------------8 0 0 0 0 224 0 0 0 1 OmniSwitch 6624/6648 (Hawk) Example Find all valid lports values with the dmpValidPorts command from Dshell on each element (i.e., each slot in a stack).
Port Numbering Conversion Overview page 1-38 Troubleshooting the Switch System OmniSwitch Troubleshooting Guide September 2005
2 Troubleshooting Switched Ethernet Connectivity This chapter assumes that it has been verified that the connectivity problem is across Ethernet media and the connection between the non-communicating devices is switched/bridged not routed (i.e., Devices are in the same IP Subnet). For configuration assistance in designing and configuring switched Ethernet connectivity, please refer to the “Configuring Ethernet Ports” chapter in the appropriate OmniSwitch Network Configuration Guide.
Overview of Troubleshooting Approach Troubleshooting Switched Ethernet Connectivity Overview of Troubleshooting Approach • Verify physical layer connectivity. • Verify current running configuration is accurate. • Verify source learning. • Investigate any error conditions. • Verify health of NIs involved. • Verify health of CMM. Client A Client B 5/1 5/2 OmniSwitch 7800 IP = 192.168.10.2 IP = 192.168.
Troubleshooting Switched Ethernet Connectivity Verify Physical Layer Connectivity Verify Physical Layer Connectivity Verify that there is valid link light along the entire data path between the devices that can not switch to each other. Make sure to include all interswitch links. Verify LED’s on all involved CMMs and NIs are Solid OK1, Blinking OK2. If this is not the case, contact technical support.
Verify Physical Layer Connectivity -> show ni 5 Module in slot 5 Model Name: Description: Part Number: Hardware Revision: Serial Number: Manufacture Date: Firmware Version: Admin Status: Operational Status: Power Consumption: Power Control Checksum: MAC Address: ASIC - Physical: -> show cmm Module in slot CMM-A-1 Model Name: Description: Part Number: Hardware Revision: Serial Number: Manufacture Date: Firmware Version: Admin Status: Operational Status: Power Consumption: Power Control Checksum: MAC Address
Troubleshooting Switched Ethernet Connectivity Verify Current Running Configuration Verify Current Running Configuration If the physical layer looks OK, then verify the configuration. Use the show configuration snapshot all to display the current running configuration. Use this command to verify the ports that are involved are in the correct VLAN.
Verify Source Learning Troubleshooting Switched Ethernet Connectivity To further verify the ports are in the correct VLAN and that they are in spanning tree forwarding instead of blocking use the show vlan port command. Also note that the port type must match what it is connecting to. If the port is 802.1Q tagged enabled for the required vlan, then the device it attaches to must also be Q tagged enabled for that vlan. Remember to run this command on all ports in the data path.
Troubleshooting Switched Ethernet Connectivity Verify Switch Health Verify Switch Health If source learning appears to be not working correctly, verify the health of the switch with the show health, and show health slot commands. Be sure to run the latter command on all necessary NIs. Any variables that have reached or exceeded their limit value could cause forwarding problems on the switch. In this case please contact Technical Support.
Using the Log File Troubleshooting Switched Ethernet Connectivity Using the Log File If none of the above suggest a reason as to why Ethernet switching is not properly working, look into the log file and see if there are any messages that may suggest why switching is not working properly. Use the show log swlog command to view the system log file. Look for evidence of a system or interface problem around the time the problem began. -> show log swlog Displaying file contents for ’swlog2.
Troubleshooting Switched Ethernet Connectivity Using the Log File Checking the 7700/7800 Nantucket Fabric for Interrupts, Data Counts and Error Counts Working: [Kernel]->nanListB02 HB Out of Sync Interrupts: 0 Error Count Exceeded Interrupts: 0 Framing Error Interrupts: 0 Parity Error Interrupts: 0 B02 Data Port 0 Frame Count = 690dbd37 B02 Data Port 1 Frame Count = 0 B02 Data Port 2 Frame Count = 542e70d9 B02 Data Port 3 Frame Count = 0 B02 Data Port 4 Frame Count = 0 B02 Data Port 5 Frame Count = 0 B02
Using the Log File Troubleshooting Switched Ethernet Connectivity Check for Catalina (MAC) or Port Lockup Lab-Span1 > dshell Working: [Kernel]->getNiResetCount Slot Slot 1, ASICResetCnt_p addr 0x2c3ee0 2, ASICResetCnt_p addr 0x2c3ee0 ENI HALF Duplex Reset count addr 0x2c3f60 phy 0: 0 0 0 0 phy 1: 0 0 0 0 PHY FIFO LOCKUP Reset count addr 0x2c3fc0 phy 0: 0 0 0 0 phy 1: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 value = 0 = 0x0 Working: [Kernel]-> page 2-10 OmniSwitch Troubleshooting Guide
3 Troubleshooting Source Learning In order to troubleshoot Source Learning problems, a basic understanding of the process is required. A review of the “Managing Source Learning” chapter from the appropriate OmniSwitch Network Configuration Guide is required. The following RFC and IEEE standards are supported: RFCs supported 2674 - Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN Extensions IEEE Standards supported 802.
Introduction Troubleshooting Source Learning Introduction VLAN 114 Port: 8/23 IP: 10.40.114.50 MAC:00-C0-4f-12-F7-1B OmniSwitch 7800 VLAN 114 Port: 16/16 IP: 10.40.114.100 MAC: 00-10-A4-B5-B5-38 Source Learning Example When a packet first arrives on NI source learning examines the packet and tries to classify the packet to join its correct VLAN. If a port is statically defined in a VLAN, the MAC address is classified in the default VLAN.
Troubleshooting Source Learning Troubleshooting a Source Learning Problem Troubleshooting a Source Learning Problem In order to troubleshoot a source learning problem the first step is to verify that the physical link is up and the port has correctly auto-negotiated with the end-station. The next thing is to verify that the port is a member of the right VLAN, if a port is statically configured for a VLAN, or the Group Mobility policies are correctly defined.
Troubleshooting a Source Learning Problem Troubleshooting Source Learning In order to narrow down to a specific NI the following command can be used (any valid slot number can be specified): -> show mac-address-table slot 8 Legend: Mac Address: * = address not valid Vlan Mac Address Type Protocol Operation Interface ------+-------------------+--------------+-----------+------------+----------114 00:c0:4f:12:f7:1b learned 10800 bridging 8/23 Total number of Valid MAC addresses above = 1 This does show tha
Troubleshooting Source Learning Advanced Troubleshooting Once, the MAC addresses are learned on the ports then the devices should be able to communicate depending on the upper layers. Variations of MAC-related commands can be viewed in the “Managing Source Learning” chapter from the appropriate OmniSwitch Network Configuration Guide.
Advanced Troubleshooting Troubleshooting Source Learning format text Debugs the packet text. format all Debugs the entire packet. output screen Output will appear on screen. output switchlog Output will be saved to a log file. board cmm Debugs CMM packets. board ni Debugs packets for a Network Interface (NI). To debug a specific interface, enter ni, then enter the slot number of the NI.
Troubleshooting Source Learning Dshell Troubleshooting Dshell Troubleshooting The OmniSwitch 6/7/8XXX has a distributed architecture. Source Learning is specific to a NI. Each NI has a layer 2 pseudo-cam which is which can hold 64K entries. 32K entries are reserved for L2 Source Addresses which are local to that NI in L2SA table and the rest of 32K entries are reserved for L2 Destination Addresses which can be from local or remote NI in L2DA table. Note.
Dshell Troubleshooting Troubleshooting Source Learning 000001f3 Total L2 SA entry amount = 1 Both of the MAC addresses are learned in the correct VLANs on the right NI. Now, if device A is trying to communicate to device B then the next thing to look for is the destination MAC address table. This is to verify that the destination MAC address table has the information about the device B.
Troubleshooting Source Learning Dshell Troubleshooting Working: [Kernel]->Sl_no_systrace=1 Sl_no_systrace = 0x56402f4: value = 1 = 0x1 Working: [Kernel]->nidbg 3:0 nidbg> Sl_NiDebug=4 3:0 Sl_NiDebug = 0x2d1fc4: value = 4 = 0x4 3:0 nidbg> 3:0 3:0 ----------------------------- HRE PACKET HRADER ----------------------3:0 isIPMS = 0, isSAMatched = 0, isDAMatched = 0, isMcst = 1, qId = 49, isRouted = 0, isTagged = 0, isFlood = 1, protoco l = 0, sPort = 64 3:0 payLoadLength = 66, isLocked = 0, lockId = 0 3:0 is
Dshell Troubleshooting Troubleshooting Source Learning OS-6600 To look at the forwarding database on OS-6600 in Dshell use the slcDumpSlotSlice command.
Troubleshooting Source Learning Dshell Troubleshooting L2 Physical Pool Stats: DstSwp Tables NetID Tables Protocol Tables ASIC Rsrc Wraps Total 16384 16384 2046 2048 Used 0 0 1 26 Free 16384 16384 2045 2022 value = 294 = 0x126 Output of many fields are described below: output definitions Addr The index. VID The VLAN ID. Addr The MAC address learned. DN The device number (stack number). PN The port number. Age The MAC address type, which can be Dynamic or Static.
Dshell Troubleshooting page 3-12 Troubleshooting Source Learning OmniSwitch Troubleshooting Guide September 2005
4 Troubleshooting Spanning Tree In order to troubleshoot spanning tree related problems an understanding of the protocol and its features are needed. The OmniSwitch supports two Spanning Tree Algorithms; 802.1D (standard) and 802.1w (rapid reconfiguration). In addition, the Omniswitch supports two Spanning Tree operating modes: flat (single STP instance per switch) and 1x1 (single STP instance per VLAN). Spanning Tree Protocol is defined in the IEEE 802.1D standard. The 802.
Troubleshooting Spanning Tree Troubleshooting Spanning Tree Troubleshooting Spanning Tree A failure of the Spanning Tree Protocol (STP) will usually cause either a bridge loop on the LAN or constant reconvergence of STP. This in turn can cause several resultant problems. • If there is a bridge loop on the LAN, there can appear to be a broadcast storm since broadcast packets will continuously loop the network.
Troubleshooting Spanning Tree Troubleshooting Spanning Tree Use the show spantree ports command to determine if the port is in forwarding or blocking and are in the correct VLAN. Remember that in any LAN with physical redundancy there must be at least one port in blocking status. If it is known which ports are usually in blocking, those ports can be a good place to start to verify they are still in blocking status.
Troubleshooting Spanning Tree Troubleshooting Spanning Tree Since STP is run in a distributed fashion it is important to verify that each NI that is involved is not having a resource problem. Use the show health command to verify the resources available on an NI.
Troubleshooting Spanning Tree Dshell Dshell As mentioned previously, it is important to verify the health of the NI as well as the CMM. Please refer to Chapter 1, “Troubleshooting the Switch System,” for directions. Note. Dshell commands should only be used by Alcatel personnel or under the direction of Alcatel. Misuse or failure to follow procedures that use Dshell commands in this guide correctly can cause lengthy network down time and/or permanent damage to hardware.
Dshell Troubleshooting Spanning Tree Working: [Kernel]->esmDumpCoronado 1,0,0x6608000+140*4,32 6608230 0 6608250 0 6608270 0 6608290 0 : 1000 0 0 0 0 0 0 0 : : : 1000 0 0 0 0 0 1000 0 0 0 0 0 0 0 0 0 0 0 0 0 value = 1 = 0x1 Working: [Kernel]->esmDumpCoronado 1,0,0x6608000+511*4,32 66087fc 0 660881c 0 660883c 0 660885c 0 : 1000 0 0 0 0 0 0 0 : : : 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 value = 1 = 0x1 The above commands that the spanning tree vector is set
Troubleshooting Spanning Tree 0 660885c : 0 Dshell 0 0 0 0 0 0 0 0 value = 1 = 0x1 Binary: 0000 0000 0011 For VLAN 1 the bits set are 203 which are equivalent to binary 0000 0000 0011. Bits 1 and 2 are set indicating that ports 1 and 2 have the spanning tree vector set for VLAN 1. The next register value is for VLAN 2, hex value is 8000000. Binary: 1000 0000 0000 0000 0000 0000 0000 Binary value indicates that bit 28 is set which means that port 24 is set for VLAN 2.
Dshell Troubleshooting Spanning Tree 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 1:0 page 4-8 Message age of received BPDU : 0 PIM port c state 5 1024 0 recordProposed operPointToPointMAC=1 PIM port c state 7 1536 0 PIM port c state 4 1536 0 port 12 is forward (5) tick (tack) time is now 701603 RSTBPDU transmitted on po
Troubleshooting Spanning Tree Dshell 1:0 Designated bridge ID = 800000d0 957962aa 1:0 Designated portId = 29697 1:0 Bridge portId = 29697 1:0 Message age : 256 1:0 Proposing 1:0 tick (tack) time is now 701647 1:0 tick (tack) time is now 701648 1:0 1:0 RSTBPDU transmitted on port 33 on STP 53 1:0 Root bridge ID = 3200d0 95820514 1:0 Path to Root cost = 3 1:0 Designated bridge ID = 800000d0 957962aa 1:0 Designated portId = 29697 1:0 Bridge portId = 29697 1:0 Message age : 256 1:0 Proposing OmniSwitch Troub
Generic Troubleshooting in Dshell Troubleshooting Spanning Tree Generic Troubleshooting in Dshell Note. Dshell commands should only be used by Alcatel personnel or under the direction of Alcatel. Misuse or failure to follow procedures that use Dshell commands in this guide correctly can cause lengthy network down time and/or permanent damage to hardware. The stp_help command (executed from the NiDebug Dshell command prompt) displays the trace menu for the Spanning Tree algorithm on NIs.
Troubleshooting Spanning Tree 74 75 76 77 78 79 80 81 82 83 84 85 - Generic Troubleshooting in Dshell PORTDELE (2,ffffffff,ffffffff,ffffffff) PORTATCH (2,1,ffffffff,ffffffff) LINK_UP (1,64,1,ffffffff) LINK_UP (2,64,1,ffffffff) LINK_UP (14,64,1,ffffffff) LINKDOWN (1,ffffffff,ffffffff,ffffffff) LINKDOWN (2,ffffffff,ffffffff,ffffffff LINK_UP (1,64,1,ffffffff) LINK_UP (2,64,1,ffffffff) AGGR_UP (1,120,2e,ffffffff) Warning File:stpni_bpduEvt.
Generic Troubleshooting in Dshell Troubleshooting Spanning Tree MODVLADM This event is received is sent by the Spanning Tree CMM to the NIs when the administrative state of a VLAN is changed (event generated by the VLAN Manager to the Spanning Tree CMM). The parameters are: • First parameter: The VLAN identifier. • Second parameter: The VLAN administrative state. A 1 indicates Enable while a 2 indicates Disable.
Troubleshooting Spanning Tree Generic Troubleshooting in Dshell MDEFVLAN This event is received is sent by the Spanning Tree CMM to the NI when the default VLAN of a fixed or q-tagged port is change (this also applies to logical port). This event is generated on the CMM by VLAN Manager application. The parameters are: • First parameter: Global port identifier. • Second parameter: new default VLAN. PORTAGGR This event is currently unused. PORTDISG This event is currently unused.
Generic Troubleshooting in Dshell Troubleshooting Spanning Tree PORTJOIN This event is sent by Link Aggregation NI when a physical port is joining an aggregator; It could be either a static aggregator (OmniChannel) or a dynamic aggregator (802.3ad). This message is generated after the first port has joined the aggregator (see “AGGR_UP” on page 4-13). The parameters are: • First parameter: The aggregator identifier (logical port ID value between 0 and 31).
Troubleshooting Spanning Tree Generic Troubleshooting in Dshell PTSTPMOD The is event is generated by the Spanning Tree CMM when the Spanning Tree configuration parameter of a port is changed by the operator. The parameters are: • First parameter: The spanning identifier (i.e., VLAN identifier). • Second parameter: The global port identifier. • Third and fourth parameters: The type of the parameter/value.
Generic Troubleshooting in Dshell Troubleshooting Spanning Tree The Port VLAN blocking message sent to the Source Learning NI has the following structure: uint16 VlanId, uint32 PortVector This event has the following values for the message ID: • appID: APPID_SPANNING_TREE. • subMsgNum: STP_PortVlanBlocking. These event fields are defined below: • VlanId: A value 1 to 4095 identifies a VLAN (0 means that the message is applied to ports defined by the PortVector on all VLANs).
Troubleshooting Spanning Tree Generic Troubleshooting in Dshell GM2FIXED This message is sent by Group Mobility NI in response to a BPDU on mobile port message sent by the Spanning Tree. By sending this message group mobility tells to Spanning Tree that the mobile port must be reverted to the fixed state. The parameters are: • First parameter: The global port identifier. • Second parameter: The default VLAN.
Generic Troubleshooting in Dshell Troubleshooting Spanning Tree TOPOCHGT This event notifies a change of Spanning Tree topology. The format of the message is: uint16 VlanId, uint16 aging_timer This event has the following values for the message ID: • appID: APPID_SPANNING_TREE • subMsgNum: STP_TopologyChange These event fields are defined below: • VlanId: A value of 1 to 4095 identifies a VLAN and 0 means that the message is applied to all the VLANs (single Spanning Tree per switch).
Troubleshooting Spanning Tree Generic Troubleshooting in Dshell Physical and Logical Port Dumps Logical Ports (stpni_debugLport) Here follows the display of the Logical port seen by the Spanning Tree. Each line corresponds to the local port identifier index.
Generic Troubleshooting in Dshell Troubleshooting Spanning Tree The fields displayed by the stpni_debugLport command are described below: output definitions dGid The field contains the value of the default VLAN associated to the port. When the default GID is 0, it indicates that the port is in the IDLE state (field sta=00). Qid Default QID (not used). Portid Global port identifier (0x0190xxxx indicates that it is a logical port, and 0x0001 indicates that it is logical port 1).
Troubleshooting Spanning Tree 23 0000 01a6 00000051 05 0001 01aa 00000052 05 0001 01ae 00000053 05 0001 01b2 00000054 05 0001 01b6 00000055 05 0001 01ba 00000056 0b 0001 01be 00000057 00 0000 0000 00000000 00 0000 0000 00000000 23 0000 01ca 0000005a 23 0000 01ce 0000005b 00 0000 0000 00000000 00 0000 0000 00000000 00 0000 0000 00000000 00 0000 0000 00000000 07 0001 01d2 00000060 05 0001 01d6 00000061 05 0001 01da 00000062 05 0001 01de 00000063 05 0001 01e2 00000064 05 0001 01e6 00000065 05 0001 01ea 000000
Generic Troubleshooting in Dshell Troubleshooting Spanning Tree output definitions (continued) Portid Global port identifier (0x0190xxxx indicates that it is a logical port, and 0x0001 indicates that it is logical port 1). NTag Number of tags (802.1q) attached to that port. This field should always be 0 when the port is FIXED or MOBILE. Vector Bitmap of the local ports that belong to the aggregator (logical port).
Troubleshooting Spanning Tree Generic Troubleshooting in Dshell • sockGlobal_maxmsgevt: This counter is the maximum number of message (counter) processed consecutively on the Message Event Manager channel (inter-NI STP channel). • sockGlobal_looptick: This flag is set to 1 indicates that we loop until the maximum number of message processed (Threshold) is overtaken. • sockGlobal_maxtick: This counter is the maximum number of ticks processed consecutively.
Generic Troubleshooting in Dshell Troubleshooting Spanning Tree Inter-NI Trace (stpNISock_intraceprint) This trace records all the inter-NI STP events received by the Socket Handler and has the following format: • An ASCII pattern reflecting the event. • Up to 4 parameters (a -1 (or 0xffffffff) indicates that the parameter is not significant).
Troubleshooting Spanning Tree Generic Troubleshooting in Dshell CMM Spanning Tree Traces Trace Menu The stpCMMSock_help Dshell command displays the Spanning Tree Manager menu as shown below.
Writing a PR for Spanning Tree Troubleshooting Spanning Tree Writing a PR for Spanning Tree The following subsections describe some guidelines to follow when writing a PR that addresses Spanning Tree. Please note that the following subsections use Dshell commands, not CLI commands. Note. Dshell commands should only be used by Alcatel personnel or under the direction of Alcatel.
Troubleshooting Spanning Tree Writing a PR for Spanning Tree Spanning Tree Unchanged When Port State Has Changed If the show spanning tree CLI command still displays the same information while a port state has changed then the problem could be due to a broken communication path between the CMM and NI. In this case do the following (for both the CMM and NI): • Time-out trace of the socket handler (stpNISock_totraceprint or stpCMMSock_totraceprint).
Writing a PR for Spanning Tree page 4-28 Troubleshooting Spanning Tree OmniSwitch Troubleshooting Guide September 2005
5 Troubleshooting BOOTP/ DHCP/UDP Relay In order to troubleshoot a BOOTP/DHCP and UDP Relay, a basic understanding of the protocol is required. Some basic concepts are covered below. The OmniSwitch supports UDP Relay. Reading the “DHCP Relay” chapter from the appropriate OmniSwitch Network Configuration Guide is also highly recommended.
Starting the Troubleshooting Procedure Troubleshooting BOOTP/DHCP/UDP Relay Use a Network Diagram It is extremely important to know where the server is in relation to the client, which switch both the client and the server is directly connected to and their port numbers. A network diagram presents this kind of information, for example, in an easily understood matter. VLAN 10 DHCP Server IP Address: 10.10.10.58 OmniSwitch 7800 Switch VLAN IP Addresses: 10.10.10.200 20.20.20.
Troubleshooting BOOTP/DHCP/UDP Relay Preliminary 6/5/06 Starting the Troubleshooting Procedure Forward Delay Timer Forward delay is the amount of time in seconds UDP relay will wait before forwarding a request to a DHCP server, or the same DHCP server. (If only one is configured on the switch.) This allows the DHCP server who initially got the DHCP request packet from the client to respond before the request is forwarded to another DHCP server.
Starting the Troubleshooting Procedure Troubleshooting BOOTP/DHCP/UDP Relay UDP Relay and Group Mobility If UDP Relay is being used with a Mobile DHCP Rule, determine if the end station is simply getting the wrong IP address scope. If this is the case, verify group mobility, as the source VLAN of the UDP request could be wrong when it reaches the UDP Relay function.
Troubleshooting BOOTP/DHCP/UDP Relay Preliminary 6/5/06 Advanced Troubleshooting for UDP Relay Advanced Troubleshooting for UDP Relay To monitor the UDP traffic, the debug ip packet protocol udp CLI command can be used. Note. See the “IP Commands” chapter in the OmniSwitch CLI Reference Guide for more information. The output below shows the entire conversation of a DHCP client with MAC address 000039:73130 in VLAN 20 to a DHCP server in VLAN 10 with a IP address of 10.10.10.58.
Dshell Troubleshooting BOOTP/DHCP/UDP Relay Dshell To send the UDP Relay debug to the console, follow the following commands: Note. Dshell commands should only be used by Alcatel personnel or under the direction of Alcatel. Misuse or failure to follow procedures that use Dshell commands in this guide correctly can cause lengthy network down time and/or permanent damage to hardware. • Use the command udprelay_do_systrace = 0 to disable systrace and enable console output.
Preliminary 6/5/06 Troubleshooting BOOTP/DHCP/UDP Relay 00 82 1e 72 00 53 05 65 00 63 39 73 00 35 02 70 00 01 02 61 00 03 4e 63 00 32 37 65 00 04 04 2e ----- 00 c0 01 41 00 a8 1c 50 00 14 03 31 Dshell 00 9a 2b 32 00 36 3c 30 00 04 10 30 00 c0 41 ff 63 a8 69 In the example above, the BOOTP request was dropped because the number of seconds elapsed since the start of the process was not incremented (secs=0), and the forward delay was set to 3 seconds.
Dshell page 5-8 Troubleshooting BOOTP/DHCP/UDP Relay OmniSwitch Troubleshooting Guide September 2005
6 Troubleshooting DNS In order to troubleshoot a DNS problem, a basic understanding of the protocol/feature is required. Some basic concepts are covered below. Reading the “Enabling the DNS Resolver” section in the “Logging Into the Switch” chapter in the appropriate OmniSwitch Switch Management Guide is highly recommended.
Troubleshooting a DNS Failure Troubleshooting DNS Troubleshooting a DNS Failure Starting the Troubleshooting Procedure If you try to use DNS resolution and it does not resolve, or connect from the switch with error such as “unknown host” take the following steps. Verify IP connectivity from the switch in question to the DNS server by pinging the server (destination) in question from the switch (source) by its IP address. If successful, move on to layer 7 DNS or Name resolution issue.
Troubleshooting DNS DNS Configuration Considerations • If you find conflicting information, then see which portion has the wrong information and focus on that layer again (layer 2, 3, or 7). • The response packet should contain the following fields: DLC with the source Mac address of the DNS server, and the destination MAC address of the switch. The IP header will contain the source IP address of the DNS server, and the destination IP address of the switch.
DNS Configuration Considerations page 6-4 Troubleshooting DNS OmniSwitch Troubleshooting Guide September 2005
7 Troubleshooting Link Aggregation In order to troubleshoot a Link Aggregation issue a basic understanding of the protocol is required. Reading the “Configuring Static Link Aggregation” and “Configuring Dynamic Link Aggregation” chapters in the appropriate OmniSwitch Network Configuration Guide is also highly recommended.
Link Aggregation Limits and Guidelines Troubleshooting Link Aggregation Link Aggregation Limits and Guidelines Consider the following when configuring Static Link Aggregation groups: • Maximum number of link aggregation groups: 30 (OmniSwitch 6624/6648), 32 (OmniSwitch 7700/ 7800), or 16 (OmniSwitch 8800). • Number of links per group supported: 2, 4, 8, or 16 • Link aggregation groups are identified by unique MAC addresses, which are created by the switch.
Troubleshooting Link Aggregation Troubleshooting a Link Aggregation Failure Troubleshooting a Link Aggregation Failure Switch A Switch B OmniSwitch 7800 OmniSwitch 7800 Link Aggregation Setup The figure above has the following setup: • Switch A and Switch B connected back to back and Link Aggregation configured. • Port 7/1 of Switch A is connected to port 7/1 of Switch B. • Port 7/2 of Switch A is connected to port 7/2 of Switch B. • VLAN 10 is assigned to this aggregate.
Troubleshooting a Link Aggregation Failure Troubleshooting Link Aggregation The show linkagg port CLI command followed by the slot and port number will display the port and link state as well as if it is the primary port. (See the samples below.) If the operational or administrative state is down and the port is primary, this indicates a software problem.
Troubleshooting Link Aggregation Troubleshooting a Link Aggregation Failure Source Learning When one of the primary links go down, the filtering database is purged and the process of learning the source addresses is started again. The next available port is chosen to be the primary port. If the port that goes down happens to be a secondary port, the MAC addresses learned on that particular port are reassigned to other ports evenly.
Troubleshooting a Link Aggregation Failure Troubleshooting Link Aggregation LACP 802.3AD Most of the steps followed previously in this chapter apply to troubleshooting LACP. To verify the configuration use the show linkagg [agg. Number]. Again, verify the aggregate is enabled and up. The most important aspect in troubleshooting LACP is to verify the transmission of valid LACPDUs. For this you can go to the Dshell section as well as use a sniffer tool.
Troubleshooting Link Aggregation Advanced Link Aggregation Troubleshooting Advanced Link Aggregation Troubleshooting To verify that the link aggregate software recognizes all the available slices, perform the following steps: Note. Dshell commands should only be used by Alcatel personnel or under the direction of Alcatel. Misuse or failure to follow procedures that use Dshell commands in this guide correctly can cause lengthy network down time and/or permanent damage to hardware.
Advanced Link Aggregation Troubleshooting Troubleshooting Link Aggregation MAC=00:d0:95:6b:54:0c name= primary_port_index=0 admin_state=1 oper_state=2 Individual=0 Actor : ID=00:00:00:00:00:00 Prio=0 Admin Key=0 Oper Key=2 Partner : ID=00:00:00:00:00:00 Prio=0 Admin Key=0 Oper Key=2 0x04442ea8 status=6 ifindex=8001 port_id=224 port_type=1 port_index=0 adminstate=1 operstate=1 link_up_down=1 activation_order=1 bandwidth=100 agg_ctx_p=0x0443a958 agg_port_ctx_p=0x04442ea8 obj_port_ctx_p=0x04442d30 0x04442c20
Troubleshooting Link Aggregation Advanced Link Aggregation Troubleshooting agg_multicast_frm_tx_ok agg_broadcast_frm_tx_ok agg_unicast_frm_tx_ok agg_frm_discard_tx agg_frm_with_tx_errors = = = = = 0 0 0 0 0 value = 40000003 = 0x2625a03 Since LACP is run on the NI it is important to verify the NI has the proper information. Many of the same commands run above are available in the NI debugger. (See the table below.) The syntax and output are the same. la_ni_agg_prt Displays aggregates.
6800 Link Aggregation Debug Functions Troubleshooting Link Aggregation 6800 Link Aggregation Debug Functions The following functions are available for Link Aggregation debugging on the NI. A summary is shown below.
Troubleshooting Link Aggregation 6800 Link Aggregation Debug Functions la_ni_port_up_prt Certified: [Kernel]->la_ni_port_up_prt 1:0: 0 -> 0x0ce87d28 agg_ctx=0x00000000 1:0: 2 -> 0x0ce93e98 agg_ctx=0x00000000 1:0: 4 -> 0x0ce92f90 agg_ctx=0x00000000 1:0: 5 -> 0x0f75fe30 agg_ctx=0x00000000 1:0: 6 -> 0x0ce736e0 agg_ctx=0x00000000 1:0: 7 -> 0x0ce93050 agg_ctx=0x00000000 1:0:48 -> 0x0ce92bd0 agg_ctx=0x00000000 value = 91 = 0x5b = '[' status=0 port_id=0 adminstate=1 link_up_down=1 status=0 port_id=2 adminstate=
6800 Link Aggregation Debug Functions Troubleshooting Link Aggregation la_ni_trace_freeze Certified: [Kernel]->la_ni_trace_freeze value = 244315184 = 0xe8ff430 la_ni_trace_unfreeze Certified: [Kernel]->la_ni_trace_unfreeze #_LA_SRV_TRACE_NI_LINKAGG_TRAC_UNFROZEN value = 40 = 0x28 = '(' la_ni_kite_help The la_ni_kite_help function may be accessed from the D-shell and will display the following output: Working: [Kernel]->la_ni_kite_help la_ni_kite_get_bcm_trunk_info(unit,agg_id) value = 83 = 0x53 = 'S' p
8 Troubleshooting 802.1Q In order to troubleshoot an 802.1Q problem on a port, a basic understanding of the networking OSI model is required to assist one with the troubleshooting steps to resolve a particular network problem. Alcatel’s OmniSwitch supports 802.1Q specifications as defined by RFC 2674/IEEE 802.1Q/D11. Reading the “Configuring 802.1Q” in the appropriate OmniSwitch Network Configuration Guide is also highly recommended. In This Chapter “Troubleshooting 802.
Troubleshooting 802.1Q Troubleshooting 802.1Q Troubleshooting 802.1Q When troubleshooting an 802.1Q problem, it is important to not only investigate the 802.1Q feature and configuration, but also the basic Ethernet connectivity between the problematic switches. Please refer to Chapter 2, “Troubleshooting Switched Ethernet Connectivity,” of this document. Switch A Switch B OmniSwitch 7800 OmniSwitch 7800 802.1Q Example If there is no traffic passing at all across an 802.
Troubleshooting 802.1Q Troubleshooting 802.1Q Default VLAN Traffic If traffic that should be in the default VLAN is not passing properly, first verify that the default VLAN is set correctly, as see above. Also note the switch can be configured to either accept or deny untagged packets. When enabling a port on the OmniSwitch 7700/7800/8800 to accept tagged traffic, you can specify whether only 802.
Troubleshooting 802.1Q Troubleshooting 802.1Q Question: What needs to be done if the native VLAN needs to be tagged when connected to an OmniSwitch 7700/7800/8800? Answer: The Gigabit/Ethernet port can be moved into a different dummy VLAN, and then the tagged service can be created for the previous native VLAN. CLI Commands are as follows: 1 Dummy VLAN 99 created: >vlan 99 2 A tag service is to be created on port 99 in VLAN 1. ->vlan 99 port default 1/1 3 Tag service created on VLAN 1. ->vlan 1 802.
Troubleshooting 802.1Q Advanced Troubleshooting Advanced Troubleshooting To verify the 802.1Q configuration from the CMM perspective use the debug 802.1q CLI command. If frame type is set to all, then the egress default VLAN will equal the ports default VLAN. If force tag internal is set to off, e.g. force tag internal will equal 0, otherwise it will be ffffffff. The following shows the debug 802.1q CLI command used to verify that the slot and port are up. -> debug 802.
Advanced Troubleshooting Troubleshooting 802.1Q output definitions Aggregate/Slot Status Whether the slot or aggregate link is actively running. Port Status Whether the port is actively running. General Info Provides general information on the modules in the chassis, including module type, number of ports, and ASIC. Hardware Info Lists the various debug messages for the selected slot and port.
Troubleshooting 802.1Q Dshell Commands Dshell Commands The first step in troubleshooting for an 802.1Q problem through Dshell is to verify the configurations. Validating the configurations in Dshell remove the chances of inconsistency between the CLI and Dshell. Following is the list of commands to verify the configuration of the 802.1Q ports in Dshell. These commands will verify that there is no inconsistency between the CLI and Dshell. Note.
Dshell Commands Troubleshooting 802.
9 Troubleshooting Group Mobility In order to troubleshoot a VLAN Mobility problem, a basic understanding of the technology is required. Reviewing the “Assigning Ports to VLANs” and “Defining VLAN Rules” chapters in the appropriate OmniSwitch Network Configuration Guide is highly recommended.
Troubleshooting a VLAN Mobility Failure Troubleshooting Group Mobility Troubleshooting a VLAN Mobility Failure There is no systematic procedure to troubleshoot a VLAN mobility issue. This section will give you a checklist, with a generally best course of action to take to determine the source of the VLAN mobility failure. 1 Verify that port mobility has been turned on for a given port and is still active. 2 Determine VLAN rules. 3 Determine mobile port membership. 4 Verify Traffic on a mobile port.
Troubleshooting Group Mobility Troubleshooting a VLAN Mobility Failure With VLAN mobility, it is critical that the network administrator have a good understanding of the traffic on their network in order to assign proper rules. It is not only important to verify the required rules have been configured, but it is also important to understand the concept of precedence for rules that may overlap. In addition, it is important not to design beyond the limitations of the software.
Troubleshooting a VLAN Mobility Failure Troubleshooting Group Mobility Precedence Due to the variety of rules that can be configured there can be traffic that can match multiple rules, i.e. an IP frame could match a network address rule as well as a protocol rule. For this reason, all rules are arranged in a precedence.
Troubleshooting Group Mobility Advanced Troubleshooting Advanced Troubleshooting To verify if a port is a candidate for mobility as well as if mobility as been turned on for a given port use the debug vlan rule ports CLI command. Note that ports 6/1-2 are mobile ports. Ports 7/1-2 and 8/1-2 are not a candidate for mobility because they are either 802.1Q ports or part of a link aggregate.
Dshell Troubleshooting Group Mobility Dshell Note. Dshell commands should only be used by Alcatel personnel or under the direction of Alcatel. Misuse or failure to follow procedures that use Dshell commands in this guide correctly can cause lengthy network down time and/or permanent damage to hardware. NI Debug Dshell Use the gmnSetPrintDestination command from the NiDebug Dshell command to redirect the output of the group mobility commands to the current session.
Troubleshooting Group Mobility 6800 Group Mobility Troubleshooting 6800 Group Mobility Troubleshooting The following commands and debugging functions are available for troubleshooting Group Mobility on the NI. A summary is shown below.
6800 Group Mobility Troubleshooting Troubleshooting Group Mobility *************************************************** Group Mobility Help for NI *************************************************** gmnKiteDebug = 1 ------- Enable real time debugging gmnKiteDebug = 0 ------- Disable real time debugging gmnKiteShowEframe = 1 -- Display E_FRAME_PARAM when gmnKiteDebug is enabled gmnKiteShowEframe = 0 -- Do not display E_FRAME_PARAM when gmnKiteDebug is enabled gmnKiteShowDefVlan gmnKiteShowPiMap gmnKiteDebug
Troubleshooting Group Mobility 6800 Group Mobility Troubleshooting GMC_LOG: "gmcShowRule", ht=1 bht=0 col=R GMC_LOG: "gmcShowRule", GMC_LOG: "gmcSh owRule", vid = 112 value = 12 = 0xc gmnKiteDebug Certified: [Kernel]->gmnKiteDebug = 1 Certified: [Kernel]->gmnKiteShowPortSet port mobile enabled restore ignoreBPDU auth ifilter ----+------+-------+-------+----------+----+------0 1 1 1 0 0 0 1 1 1 1 0 0 0 2 1 1 1 0 0 0 3 1 1 1 0 0 0 4 1 1 1 0 0 0 5 1 1 1 0 0 0 6 1 1 1 0 0 0 7 1 1 1 0 0 0 gmnKiteShowRules Ce
6800 Group Mobility Troubleshooting page 9-10 Troubleshooting Group Mobility OmniSwitch Troubleshooting Guide September 2005
10 Troubleshooting QoS In order to troubleshoot Quality of Service (QoS), a basic understanding of the concept is required. Some basic concepts are covered below. Reading the “Configuring QoS” and “Configuring ACLs” chapters in the appropriate OmniSwitch Network Configuration Guide is also highly recommended.
QoS Behavior Troubleshooting QoS QoS Behavior It is important to know how QoS behaves by default in order to understand the way it works and to be able to troubleshoot it. So first of all, a list of default behaviors. Default By default, flows that do not match any policies are accepted on the switch. This applies to bridged, routed, and multicast flows.
Troubleshooting QoS Troubleshooting QoS On the OmniSwitch 6624/6648, flows always share queues. On the OmniSwitch 7700/7800/8800, flows may share queues if they match the same policy and the policy action is configured for sharing through the policy action CLI command. In order to be shared, the flows must arrive on the same slice and be destined for the same egress port.
Troubleshooting QoS Troubleshooting QoS QoS Apply Another common mistake for having a policy not work is to forget to apply the QoS configuration to the configuration. Most QoS commands require a qos apply CLI command before the configuration is active. This is valid for QoS configuration on the CLI. Loading a QoS ASCII configuration file does not require a qos apply command. Note. Use the qos apply CLI command to activate your QoS settings. (You still need to save on exit.
Troubleshooting QoS Troubleshooting QoS Viewing QoS Settings When troubleshooting, it is essential to keep track of all your QoS settings that are effective; i.e. that have been applied. A good way to display all the QoS settings is to use the show configuration snapshot qos CLI command, which generates a snapshot file of the switch’s QoS current running configuration.
Troubleshooting QoS Troubleshooting QoS Validation In order to validate the policy which are not applied yet (pending policies) or you may want to see how theoretical traffic would be classified by policies that are already applied on the switch, the show policy classify CLI command can be used. -> show policy classified L3 applied The switch will display information about the potential L3 traffic and attempt to match it to a policy (applied policies only).
Troubleshooting QoS Troubleshooting QoS What happens when some traffic comes in for ip destination port 80? Since it does not satisfy condition “oktftp”, it depends on the global disposition for router and bridged traffic (qos default routed disposition and qos default bridged disposition). In our case, the global disposition is default; i.e. accept. We will receive the result below to accept the traffic when no rules are matched.
Troubleshooting QoS *IP : *UDP : *TOS/DSCP: 0/0 Troubleshooting QoS 192.168.10.0 -> 0.0.0.0 0 -> 69 Using pending l3 policies Classify L3: *Matches rule 'oktftp': action oktftp (accept) In this example, the display indicates that the switch found a rule, “oktftp”, to classify destination traffic with the specified Layer 3 information. Correction If the policy is found invalid, you can use the qos revert CLI command.
Troubleshooting QoS Troubleshooting QoS For example, a TFTP session in one direction will prompt a reply back from the host. If a policy is created to deny traffic from that host to the switch, the replies from the host will still be accepted on the switch if the TFTP session policy is configured as a reflexive policy. If we do not define the rule “oktftp” below, no TFTP session would take place between TFTP client 192.168.10.4 and TFTP server 192.168.20.10. -> policy condition noip destination ip 192.
Troubleshooting QoS Troubleshooting QoS To view the QoS log, use the show qos log command.
Troubleshooting QoS Troubleshooting QoS QoS Statistics The show qos statistics CLI command displays statistics about the global QoS configuration as shown below: -> show qos statistics QoS stats Events L2: 21 L3 Ingress: 0 L3 Egress: 0 IGMP Join: 0 Fragments: 0 Bad Fragments: 0 Unknown Fragments: 0 Sent NI messages: 9 Received NI messages: 4322 Failed NI messages: 0 Load balanced flows: 0 Reflexive flows: 0 Reflexive correction: 0 Flow lookups: 0 Flow hits: 0 Max PTree nodes: 0 Max PTree depth: 0 Flow hit
Troubleshooting QoS Troubleshooting QoS Debug QoS Internal The CLI command debug qos internal displays debugging information for QoS internal to the switch. This command has the following syntax: debug qos internal “[slice slot/slice] [flow] [queue] [port] [l2tree] [vector] [pending] [verbose] [mapper] [pool] [log]” One of the most useful commands to debug all your QoS policy rules is debug qos internal slice/slot flow where slot is the slot number and slice is the slice (ASIC) number.
Troubleshooting QoS Troubleshooting QoS OmniSwitch 6624/6648 Dshell Troubleshooting Note. Dshell commands should only be used by Alcatel personnel or under the direction of Alcatel. Misuse or failure to follow procedures that use Dshell commands in this guide correctly can cause lengthy network down time and/or permanent damage to hardware. qosIxHelp dshell->qosIxeHelp ???? Example output of qosIxHelp needed ???? qosDBState Shows the IP and CAM usage and Semaphore.
Troubleshooting QoS Troubleshooting QoS output definitions (continued) QVID Egress VLAN ID. A value appears in this field if the packet is being routed to the destination IP address, which is the address that appears in the IP field. EGR0 The egress slot/port on ASIC 0. The port that will forward a routed packet to the destination IP address, which is the address that appears in the IP field. EGR0 must be equal to EGR1. A -1 in this field indicates that packets cannot be routed to the IP on this slot.
Troubleshooting QoS Example QoS Rules Example QoS Rules See below for the steps to create a rule for blocking an offending MAC address using the CLI on the OmniSwitch. Please note the rule does not take effect until you use the qos apply CLI command. Any time you make a change you need to reissue the qos apply command for it to take.
Example QoS Rules Troubleshooting QoS Example of a traffic shaping rule: -> -> -> -> -> qos stats interval 30 log level 7 log console policy condition ip_traffic2 source ip 192.168.10.20 policy action BW maximum bandwidth 40.
11 Troubleshooting ARP The OmniSwitch supports Address Resolution Protocol (ARP). In order to troubleshoot issues related to ARP, a basic understanding of the protocol is required. Some basic concepts are covered in the sections below. RFCs supported IETF RFC 826 Reading the IETF RFC 826 specification is highly recommended to anyone implementing or troubleshooting an ARP issue on their network.
ARP Protocol Failure Troubleshooting ARP ARP Protocol Failure Gateway 00:d0:95:79:62:d1 Gateway 00:d0:95:79:62:8b Segment: A Segment: B Workstation: A Workstation: B 08:00:20:a8:f0:8a 00:C0:4F:04:6C:2A If device A is not able to communicate with device B, it could be a result of ARP resolution failure. To troubleshoot ARP the first reference point is to make sure that the MAC address of device A and device B are learned on the right port and in correct VLAN.
Troubleshooting ARP ARP Protocol Failure When device A ARPs for the gateway IP address exist on the switch, an associated ARP cache entry is created by the switch. This entry can be viewed by using the show arp command. To search for a specific ARP entry, use the following command syntax: show arp ip-address For example: -> show arp 10.255.11.
ARP Protocol Failure Troubleshooting ARP To confirm the MAC address of the routing instance, use the following command: -> show ip interface vlan 10 vlan 10 Link type Link status SNMP interface index Interface index Enable IP forwarding Administrative status Operational status Enable trap Internet address Broadcast address Subnet mask Hardware address Vrrp MAC Auth MAC Maximum Transfer Unit (MTU) Packets received Packets sent Bytes received Bytes sent Multicast packets received Multicast packets sent Broa
Troubleshooting ARP Common Error Conditions Common Error Conditions If the ARP is not getting 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 Advanced ARP Troubleshooting If the MAC addresses is already learned on the port and the ARP is not getting resolved then we can further troubleshoot on the switch to see if the ARP request is reaching the switch and switch is responding back. To troubleshoot the ARP packets we need to use the diagnostic CLI commands. Precaution must be taken when using these commands as it might dump a lot of information on the screen.
Troubleshooting ARP Advanced ARP Troubleshooting Some devices may be silent like printers. They ARP at the time of the bootup but after that they do not ARP at all. In order to accommodate those devices OmniSwitch allows different choices: • To increase the ARP time out value. By default the ARP timeout value is set for 300 seconds.
Dshell Troubleshooting Troubleshooting ARP Dshell Troubleshooting In order to troubleshoot ARP cache make sure all the steps mentioned in the earlier sections have been taken. Dshell should be used when no more error collection can be done from the CLI and debug CLI. Note. Dshell commands should only be used by Alcatel personnel or under the direction of Alcatel.
Troubleshooting ARP 10.40.212.3 10.40.212.4 10.40.212.127 10.40.212.238 192.168.50.1 192.168.50.2 192.168.50.5 192.168.51.5 192.168.52.5 192.168.53.5 192.168.54.5 192.168.56.2 192.168.57.1 192.168.57.2 192.168.57.5 192.168.58.
Dshell Troubleshooting Troubleshooting ARP Viewing the ARP Table on OmniSwitch 6624/6648 Switches To look at the ARP table on OS-6600 use the following command in Dshell: Working: [Kernel]->ipni_arpShow Slot 2. NI Arp Table destination gateway 2.2.2.100 00:00:5e:00:01:02 4.4.4.1 00:d0:95:84:07:1e 4.4.4.100 00:00:5e:00:01:04 10.255.13.2 00:20:da:0a:54:10 10.255.13.90 00:d0:95:6a:84:51 131.118.33.
12 Troubleshooting IP Routing In order to troubleshoot an IP Routing problem, a basic understanding of the IP protocol/feature is required. Some basic concepts are covered below. Reading RFCs 791, 1812 and 1716 are highly recommended to anyone implementing or troubleshooting IP Routing on their switch/network. IP Routing is a process by which layer 3 packets are forwarded between two different subnets or networks.
In This Chapter Troubleshooting IP Routing In This Chapter “Introduction” on page 12-3 “IP Routing Protocol Failure” on page 12-3 “Troubleshooting via the CLI” on page 12-3 “Troubleshooting with Debug CLI” on page 12-11 “RIP Troubleshooting” on page 12-13 “OSPF Troubleshooting” on page 12-19 “BGP Troubleshooting” on page 12-27 page 12-2 OmniSwitch Troubleshooting Guide September 2005
Troubleshooting IP Routing Introduction Introduction The primary function of IP Routing is processing Layer 3 IP packets and forwarding them in between two different networks or subnets. This is broken down into two functions. First is determining the best path to get from one network or subnet to the next and second is to forwarding the packet into that destination network. With that being said you need to figure out what type of routing the client is doing.
Troubleshooting via the CLI ..... 4/19 4/20 4/21 4/22 4/23 ..... default default default default default Troubleshooting IP Routing inactive inactive inactive forwarding inactive If the destination VLAN gateway address does respond to a ping, there should be no issue with routing, and the cause is likely to be with Source Learning assuming all other items check out properly (i.e. PC IP setup, link status, etc.) (see Chapter 2: Managing Source Learning).
Troubleshooting IP Routing Troubleshooting via the CLI domainName : nameServer(s): Verify that the switch has a valid route to the destination subnet via the show ip route command: -> show ip route Dest Address Subnet Mask Gateway Addr Age Protocol ------------------+-----------------+-----------------+---------+----------127.0.0.1 255.255.255.255 127.0.0.1 00:14:39 LOCAL 192.168.1.0 255.255.255.0 192.168.1.1 00:13:08 LOCAL 192.168.10.0 255.255.255.0 192.168.10.50 00:14:35 LOCAL 192.168.10.1 255.255.255.
Troubleshooting via the CLI Destination unreachable Time exceeded Parameter problem Source quench Redirect Echo request Echo reply Address mask request Address mask reply Troubleshooting IP Routing 201 0 0 0 0 9377 1 0 0 15 0 0 0 0 0 9377 0 0 The show ip router database command may yield a clue, possibly telling you that an interface that is designated as a router interface is down or disabled for some reason.
Troubleshooting IP Routing Troubleshooting via the CLI Multicast packets sent Broadcast packets received Broadcast packets sent Input errors Output errors Collisions Dropped = = = = = = = 0, 51008, 155, 0 1 0 0 The show ip traffic command gives switch-wide statistics for traffic, and the “No Route Discards” statistic should somewhat resemble the “icmp stats destination unreachable” number, in that both numbers should be increasing at a similar rate.
Troubleshooting via the CLI Troubleshooting IP Routing output definitions Local Address Local IP address for this TCP connection. If a connection is in the LISTEN state and will accept connections for any IP interface associated with the node, IP address 0.0.0.0 is used. Local Port Local port for this TCP connection. Remote Address Remote IP address for this TCP connection. Remote Port Remote port number for this TCP connection.
Troubleshooting IP Routing Troubleshooting via the CLI The show ip config command displays IP configuration on the switch: -> show ip config IP directed-broadcast = ON, IP default TTL = 64 There are user-configurable parameters that can be changed as per requirement. The vlan mtu-ip command sets the MTU (Maximum Transmission Unit) size for a VLAN. -> vlan 110 mtu-ip 1500 The show ip interface command displays statistics of a particular IP interface.
Troubleshooting via the CLI 10.1.99.0/24 10.1.99.0/24 10.1.99.0/24 10.11.5.0/24 10.40.100.0/24 10.40.105.0/24 10.40.108.0/24 10.40.110.0/24 page 12-10 Troubleshooting IP Routing 192.168.60.2 192.168.61.2 192.168.62.2 10.11.5.2 10.40.100.2 10.40.105.2 10.40.108.2 10.40.110.
Troubleshooting IP Routing Troubleshooting with Debug CLI Troubleshooting with Debug CLI As always, being able to obtain a trace of the traffic via a Sniffer application will tell you the bottom line. If the packets leave the source and arrive at the destination segment properly, the issue does not lie with routing, the switch, or any intermediate device. In debug you can look at certain types of traffic crossing through the switch.
Troubleshooting with Debug CLI Troubleshooting IP Routing ip-address Specifies an IP address to debug. The debug output will only be for packets received from this IP address. Enter ip-address, then enter the IP address that you want to debug. ip-pair Use this option to match packets exchanged between two network addresses. Enter ip-pair, then enter each IP address. protocol Specifies a protocol type to debug.
Troubleshooting IP Routing RIP Troubleshooting RIP Troubleshooting The following commands are used to troubleshoot RIP failures: show show show show show show ip ip ip ip ip ip rip rip rip rip rip rip interface //check for status enable and version Rip V1 or V2 redis-filter peer routes debug //level 0 is disabled 7700-> ip rip debug-type ? ^ WARNING TIME SETUP SEND REDIST RECV RDB INFO ERROR CONFIG ALL AGE (IP Routing & Multicast Command Set) To debug RIP: 1) 2) 3) 4) ip ip ip ip rip rip rip rip
RIP Troubleshooting 11.40.150.1 Troubleshooting IP Routing 6 enabled enabled 0/0(0) The interface is enabled.
Troubleshooting IP Routing 10.10.42.159 11.40.117.0 11.40.150.0 11.40.211.0 11.41.117.0 11.41.211.0 192.168.10.0 RIP Troubleshooting 255.255.255.255 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 11.41.211.1 11.40.211.1 11.40.150.1 11.40.211.4 11.41.211.1 11.41.211.4 11.40.150.100 2 2 1 1 2 1 2 Notice, that route 6.0.0.0 and 8.0.0.0 appears with the natural subnet mask, even though it is configured to be class C mask.
RIP Troubleshooting Troubleshooting IP Routing error Includes error conditions, failures, processing errors, etc. warning Includes general warnings, non-fatal conditions. recv Enables debugging in the receive flow path of the code. send Enables debugging in the send flow path of the code. rdb Debugs RIP database handling. age Debugs code handling database entry aging/timeouts. redist Debugs redistribution code. info Provides general information.
Troubleshooting IP Routing tRip-: tRip-: tRip-: tRip-: tRip-: tRip-: tRip-: tRip-: tRip-: tRip-: tRip-: RIP Troubleshooting Adding 11.40.1.0/24->11.40.211.1 to FIB in ripRdbLookup for 11.40.117.0 (255.255.255.0) Adding 11.40.117.0/24->11.40.211.1 to FIB in ripRdbLookup for 11.40.150.0 (255.255.255.0) Adding 11.40.150.0/24->11.40.211.1 to FIB in ripRdbLookup for 11.41.117.0 (255.255.255.0) Adding 11.41.117.0/24->11.40.211.1 to FIB in ripRdbLookup for 11.41.211.0 (255.255.255.0) Adding 11.41.211.0/24->11.
RIP Troubleshooting Troubleshooting IP Routing tRip-: in ripRdbLookup for 10.0.0.0 (255.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.10.42.57 to INFINITY (split horizon) tRip-: in ripRdbLookup for 10.0.0.0 (255.0.0.0) tRip-: ripSupply: Adding tuple(5) dst=10.10.42.57 mask=0.0.0.0 gw=0.0.0.0 met=16 tRip-: ripSupply: Forcing metric for 10.10.42.159 to INFINITY (split horizon) tRip-: in ripRdbLookup for 10.0.0.0 (255.0.0.
Troubleshooting IP Routing OSPF Troubleshooting OSPF Troubleshooting The following commands are used to troubleshoot OSPF failures: show ip show ip show ip show ip //state show ip show ip ospf interface x.y.z. ospf area 2.2.2.2 ospf ospf neighbor is FULL (connect to DR or BDR) or 2 Ways (router to router) ospf interface //DR or BDR ospf lsdb //within area A debug-level of 50 for detail and 75 for more detail.
OSPF Troubleshooting Troubleshooting IP Routing # of Init State Neighbors # of Exchange State Neighbors # of Full State Neighbors = 0, = 0, = 0 This interface has been assigned to area 0.0.0.5. OSPF interface status is down because the administrative status of the OSPF interface is down. If the priority of the interface is set to 0 then this interface will not participate in the elections for DR and BDR. Check to verify that the area 0.0.0.5 was created on the switch and is operational.
Troubleshooting IP Routing OSPF Troubleshooting External LSDB Limit Exit Overflow Interval # of SPF calculations done # of Incr SPF calculations done # of Init State Nbrs # of Exchange State Nbrs # of Full State Nbrs # of attached areas # of Active areas # of Transit areas # of attached NSSAs = = = = = = = = = = = 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 Since, OSPF is enabled globally so enable OSPF on the interface. -> ip ospf interface 10.40.110.
OSPF Troubleshooting 0.0.0.0 0.0.0.5 0.0.0.5 0.0.0.5 0.0.0.5 0.0.0.5 0.0.0.5 0.0.0.5 0.0.0.5 0.0.0.5 0.0.0.5 0.0.0.5 0.0.0.5 0.0.0.5 0.0.0.5 0.0.0.5 0.0.0.5 0.0.0.5 0.0.0.5 0.0.0.5 0.0.0.5 0.0.0.5 0.0.0.5 0.0.0.5 Troubleshooting IP Routing sumnet rtr rtr rtr rtr net net net sumnet sumnet sumnet sumnet sumnet sumnet sumnet sumnet sumnet sumnet sumasbr sumasbr sumasbr sumasbr sumasbr sumasbr 10.40.0.0 11.40.211.1 11.41.211.1 192.168.50.3 192.168.50.4 10.40.110.3 10.40.111.3 10.40.212.3 10.0.128.0 10.10.
Troubleshooting IP Routing 192.168.54.0 192.168.55.0 192.168.56.0 192.168.57.0 192.168.58.0 192.168.59.0 192.168.60.0 192.168.61.0 192.168.62.0 OSPF Troubleshooting 10.26.0.1 10.26.0.1 10.26.0.1 10.26.0.1 10.26.0.1 10.26.0.1 10.26.0.1 10.26.0.1 10.26.0.
OSPF Troubleshooting Troubleshooting IP Routing If local, static, or any other external protocol routes need to be redistributed into OSPF then the first step is to make that OSPF router to be a AS Border Router. This need OSPF status to be disabled. -> ip ospf status disable -> ip ospf asbr -> ip ospf redist local -> ip ospf redist-filter 0.0.0.0 0.0.0.0 ->ip ospf redist status enable -> ip ospf status enable For any redistribution into OSPF, OSPF status needs to be disabled and then re-enabled.
Troubleshooting IP Routing OSPF Troubleshooting send Administratively enables/disables debugging messages for packets sent by OSPF only. flood Administratively enables/disables debugging messages for the flooding of Link State Advertisements (LSAs) in OSPF only. spf Administratively enables/disables debugging messages for OSPF’s Shortest Path First (SPF) calculations only. lsdb Administratively enables/disables debugging messages for OSPF’s Link State Database (LSDB) related operations only.
OSPF Troubleshooting Troubleshooting IP Routing Let’s look at all the messages that appear on the console during the setup of OSPF adjacency. The enabled debug types are state, hello and area using the command: This command is too verbose so special care should be taken when using this command. -> ip ospf debug-type warning -> ip ospf debug-type error -> ip ospf debug-type state -> ip ospf debug-level 255 (Building Router LSA to advertise on the interface.
Troubleshooting IP Routing BGP Troubleshooting tOspf-: ospfNbrStateMachine: (10.40.110.3) Change! PREV LOADING; EVENT LOADDONE; NEXT FULL. (Loading of the LSAs done, spf calculations being done and the routes are getting loaded in the route table. The state moves to Full with the neighbor.) tOspf-: [curTime tOspf-: Age 0 tOspf-: tOspf-: tOspf-: ospfAreaTimer:3356 ospfBuildRouterLsa(area 0.0.0.5, flags 0x5).
BGP Troubleshooting Troubleshooting IP Routing -> show ip bgp neighbors statistics Neighbor address = # of UP transitions = Time of last UP transition = # of DOWN transitions = Time of last DOWN transition = Last DOWN reason = # of msgs rcvd = # of Update msgs rcvd = # of prefixes rcvd = # of Route Refresh msgs rcvd = # of Notification msgs rcvd = Last rcvd Notification reason = Time last msg was rcvd = # of msgs sent = # of Update msgs sent = # of Route Refresh msgs sent = # of Notification msgs sent = L
Troubleshooting IP Routing Dshell Troubleshooting Advanced IP Routing Dshell Troubleshooting Advanced IP Routing The following Dshell commands are used to troubleshoot advanced IP routing. ipdbg=x This command runs on the NI of the 7700/8800. Value can be 'OR'ed (for example, 0x20001000 is 'OR'ed with IPDBG_DBG and IPDBG_WARN). The most common value is 0x20000000. The default value is 0x10000000. Please run this command with a taskDelay . A value of 300 ticks equals 5 seconds.
Dshell Troubleshooting Advanced IP Routing Troubleshooting IP Routing Internet address: 127.0.0.1 Netmask 0xff000000 Subnetmask 0xff000000 Metric is 0 Maximum Transfer Unit size is 32768 46 packets received; 46 packets sent 0 multicast packets received 0 multicast packets sent 0 input errors; 0 output errors 0 collisions; 0 dropped iprmShowRoutes Shows the types of routes on the CMM. ->dshell Working: [Kernel]->iprmShowRoutes tShell-: TOS Destination Gateway Protocol Metric tShell-: 0 0.0.0.0/0 172.50.1.
Troubleshooting IP Routing Dshell Troubleshooting Advanced IP Routing 1:0 1:0 fe7 vlan180. [@0x01488690] 1:0 Flags 0x1041 State 0x1 1:0 Internet address: 169.10.208.3 1:0 Netmask 0xfffff000 Subnetmask 0xfffff000 1:0 Ethernet Address: 00:d0:95:86:88:68 1:0 VRRP Ethernet Address: 00:00:00:00:00:00 1:0 Maximum Transfer Unit size is 1500 1:0 Arp timeout is 300. 1:0 If address list pointer 1488600 1:0 Iprm_routeShow Shows the type of routes per NI.
Dshell Troubleshooting Advanced IP Routing Troubleshooting IP Routing sessionId = 0 spfCount = 97 incrSpfCount = 0 ageTimer = 180 ageTicks = 61 ***Dumping myConfig contents*** cfg.flags = 0x223 cfg.mcastExtensions = 0x0 cfg.spfHold = 10 cfg.spfDelay = 5 cfg.routeTag = 0 cfg.redistHostRoutes = 0 routerId = 0xa111b67 version = 2 areaBdrRtrStatus = 0 spfStatus = 1 ***Dumping Global spfInfo contents*** incrSpfCount = 0x0 spfLast = 0x18fadb spfSignature = 0x0 spfMaxNodes = 0x1388 incrSpfMaxNodes = 0x1388 .....
Troubleshooting IP Routing Dshell Troubleshooting Advanced IP Routing redistTable[5] = 0x0 redistTable[6] = 0x0 redistTable[7] = 0x0 *rdbRtr = 0x47a5640 *rdbNet = 0x48ed4a8 *rdbAsbr = 0x47cb6a0 *extRdb = 0x47adbd4 *** ipConfig contents *** defaultEncap = 0 defaultTTL = 0 primaryAddr = 0 defaultGwAddr = 0 ifCfgList = 0x0 rdbSyncCount = 0 rdbSyncTimer = -1 *** Fast Memory Pool Ids *** NbrPoolId = 0x48edbd8 RoutePoolId = 0x48ed858 LsaQueuePoolId = 0x48ed818 RdbSyncMsgPoolId = 0x48ed7d8 AreaAggrNodePool = 0x4
Dshell Troubleshooting Advanced IP Routing page 12-34 Troubleshooting IP Routing OmniSwitch Troubleshooting Guide September 2005
13 Troubleshooting Virtual Router Redundancy Protocol (VRRP) In This Chapter “Protocol Information” on page 13-3 “OmniSwitch 7700/7800/8800 Implementation” on page 13-4 “CMM Failover” on page 13-5 “OmniSwitch VRRP Troubleshooting” on page 13-9 “ARP Table” on page 13-10 “Dshell Troubleshooting” on page 13-11 OmniSwitch Troubleshooting Guide September 2005 page 13-1
Overview Troubleshooting Virtual Router Redundancy Protocol (VRRP) Overview VRRP specifies an election protocol. All protocol messaging (not user data) is performed using IP multicast datagrams. The Multicast IP address is 224.0.0.18. This allows VRRP to operate over a variety of LAN technologies supporting IP. There source MAC address for these datagrams is also specified in the RFC. That is 00-00-5E-00-01-(VRID). The last pair in the Mac address is the Virtual Router ID (VRID).
Troubleshooting Virtual Router Redundancy Protocol (VRRP) Protocol Information Protocol Information This next section describes how VRRP routers exchange information. IP Field Descriptions Source Address The primary address of the interface the packet is being sent from. Destination Address The IP Multicast address 224.0.0.18 TTL Must be 255 or packet is dropped. Protocol 112 decimal. VRRP Field Descriptions Version Specifies the VRRP version of the packet. Currently this is version 2.
OmniSwitch 7700/7800/8800 Implementation Troubleshooting Virtual Router Redundancy Protocol (VRRP) OmniSwitch 7700/7800/8800 Implementation This section will cover how and what the OmniSwitch 7700/7800/8800s will support. VRRP Security The OmniSwitch7700/7800/8800 will support no authentication and simple text password. However the third method mentioned in the RFC, IP Authentication with HD5 HMAC is not supported in this the current release of VRRP software.
Troubleshooting Virtual Router Redundancy Protocol (VRRP) CMM Failover CMM Failover When the CMM receives a Takeover message from the Chassis Supervisor it will first inform ARP to purge all entries for the virtual router IP/Mac addresses. VRRP will then continue with a normal start-up procedure, even though interfaces are already enabled upon bootup of secondary.
CMM Failover Troubleshooting Virtual Router Redundancy Protocol (VRRP) show vrrp statistics Displays statistics about VRRP packets for all virtual routers configured on the switch or for a particular virtual router. show vrrp [vrid] statistics Syntax Definitions vrid The virtual router ID, in the range from 1–255 (OmniSwitch 7700, 7800, or 8800) or 1–7 (OmniSwitch 6624 or 6648).
Troubleshooting Virtual Router Redundancy Protocol (VRRP) CMM Failover output definitions (continued) State The administrative state of the VRRP instance; initialize means that this VRRP instance is waiting for a startup event, such as a reboot or when the virtual router is disabled; backup means that this instance is monitoring the availability and the state of the master router; master means that this instance is functioning as the master router.
CMM Failover Troubleshooting Virtual Router Redundancy Protocol (VRRP) output definitions (continued) Authentication type errors The total number of VRRP packets received in which the AuthType value was different than the one configured for the virtual router. IP TTL errors The total number of VRRP packets received in which the IP address list does not match the configured list for the virtual router.
Troubleshooting Virtual Router Redundancy Protocol (VRRP) OmniSwitch VRRP Troubleshooting OmniSwitch VRRP Troubleshooting The following commands can be used to troubleshoot VRRP: swlog appid vrrp level debug3 Example output: sw-2> swlog appid vrrp level debug3 +++ vrrpAdverTimer +++ vrrpSendAdvPkt: vrid=1 pri0=0 +++ vrrpSendAdvPkt: VRID 10 (0xa) sent 20 bytes +++ vrrpAdverTimer +++ vrrpSendAdvPkt: vrid=1 pri0=0 +++ vrrpSendAdvPkt: VRID 10 (0xa) sent 20 bytes +++ vrrpAdverTimer +++ vrrpSendAdvPkt: vrid=1
ARP Table Troubleshooting Virtual Router Redundancy Protocol (VRRP) ARP Table The ARP Table of the OmniSwitch that is the Master Router will have the Virtual MAC Learned in the ARP Table. It will not be learned on a port. In the example below I use the show arp command to illustrate before and after a switch the VRRP master.
Troubleshooting Virtual Router Redundancy Protocol (VRRP) Dshell Troubleshooting Dshell Troubleshooting In a situation where VRRP is flapping, go into Dshell of the switch that is configured as the backup virtual router that is flapping and enter vrrpTMon(1, vrid, vlanId). For example, for virtual router 200 on VLAN 200 the command will be: vrrpTMon(1,200,200). You should then see the advertisements arriving once per second on your console.
Dshell Troubleshooting page 13-12 Troubleshooting Virtual Router Redundancy Protocol (VRRP) OmniSwitch Troubleshooting Guide September 2005
14 Troubleshooting IP Multicast Switching (IPMS) In order to troubleshoot IP Multicast Switching, a basic understanding of its function is required. Some basic concepts are covered below. OmniSwitch 7700/7800/8800 supports IP Multicast Switching and Routing. Reading the “Configuring IP Multicast Switching” chapter in the appropriate OmniSwitch Network Configuration Guide is also highly recommended.
Troubleshooting IP Multicast Switching (IPMS) Troubleshooting a Device that Cannot Join an IP Multicast Stream Troubleshooting a Device that Cannot Join an IP Multicast Stream If a device cannot join a stream, the first thing to do is to verify Layer 2/Layer 3 connectivity and that no physical errors exist. The next step is to look at the switch the device is attache to, see if the device is a member of the multicast group.
Troubleshooting IP Multicast Switching (IPMS) Troubleshooting a Device that Drops Out of an IP Multicast Stream Troubleshooting a Device that Drops Out of an IP Multicast Stream If the issue is a device can actually join a multicast stream, but loses it after a period of time, there are a few items to check.
Troubleshooting IP Multicast Switching (IPMS) Troubleshooting a Device that Drops Out of an IP Multicast Stream Is Multicast Switching enabled on your switch? If it is not enabled, you will likely notice high utilization for the switch, and devices in the VLANs where multicast traffic is flowing will be being flooded with the stream(s). As Multicast Switching comes standard with this release, it should be enabled.
Troubleshooting IP Multicast Switching (IPMS) Troubleshooting a Device that Drops Out of an IP Multicast Stream OmniSwitch Network Configuration Guide. Also, see the “IPMS Application Example” section as it gives a good example of how and when to use several of the IPMS commands. To find where a multicast stream begins in your network, you can use the show ip multicast forwarding command.
Troubleshooting IP Multicast Switching (IPMS) Troubleshooting a Device that Drops Out of an IP Multicast Stream You may also have a misconfigured or malfunctioning ip multicast static-querier. In the show ip multicast queriers command, look for Type of “Static” and check to see if the IP addresses configured exist and are functioning properly. Also mentioned was that if a group membership expires it may be because it isn’t on an IP VLAN. This is probably due to a querying problem.
Troubleshooting IP Multicast Switching (IPMS) Troubleshooting IPMS in Debug CLI Troubleshooting IPMS in Debug CLI The Debug CLI will allow you to view traffic traversing the switch in many ways. The most useful command for troubleshooting IP Multicast is: -> debug ip packet show-multicast on board ni 1 output console This command turns on debug for IP packets, turns on the ability to show multicast packets, looks only on blade #1, and outputs to console.
Troubleshooting IP Multicast Switching (IPMS) Troubleshooting IPMS in Debug CLI Note the output of the show ip multicast queriers command during this test: -> show ip multicast queriers Source IP VLAN Slot/Port Expire Type --------------------+----+---------+------+------10.10.10.190 1 1/22 146 Dynamic The .190 address is that of the uplinked OSR9 in the test.
Troubleshooting IP Multicast Switching (IPMS) Dshell Troubleshooting Dshell Troubleshooting The IPMS application has its own shell to verify the specific data displayed on the CLI. Use a question mark to display the local list of commands for each level. Every CLI commend has a corresponding output on this shell with extended information on each entry. See examples below: Note. Dshell commands should only be used by Alcatel personnel or under the direction of Alcatel.
Troubleshooting IP Multicast Switching (IPMS) grp nbr qry src prx vprx v3prx qint qtmr hwrt enbl - Dshell Troubleshooting Group Membership Neighbors Queriers Sources Proxy Proxy by Vlan IGMPv3 Proxies Querier interface list Querier timer list Toggle hardware flag Toggle enable flag IPMEM> grp Hash IDX ==== 0001 0014 0022 0001 0024 0001 0090 0001 0101 0014 0254 0001 Destination IP Client IP VLAN VPN EXP TYP Mode Version Flags Source MAC =================== =================== ==== === ===== === ==== ==
Troubleshooting IP Multicast Switching (IPMS) Dshell Troubleshooting IPMEM> src Hash Multicast Source IP/ Multicast Dest IP VLAN VPN TYP EXP RTY Pkt Cnt INDX Unicast Source IP ==== ==================== ==================== ==== === === === === ======= 0291 172.99.255.153 239.1.1.101 549 12 NAT -63009 0 0001 0.0.0.0 0 IPMEM> qint VLAN Intf Addr/ MAC ACT State Version Nbr V1 Port Timeout Querier Addr -------- -------------------- ------------- --- ----- ------- --- ------- ------0100 172.100.1.
Troubleshooting IP Multicast Switching (IPMS) Dshell Troubleshooting MAIN> ? Main Menu main - Main Menu clist - Display Sub-tasks restart - Restart IPMS MAIN> clist Connected Tasks ipmem ipmfm ipmni1 ipmni2 ipmni3 ipmni4 ipmni5 ipmni6 ipmni7 ipmni8 ipmni9 ipmni10 ipmni11 ipmni12 ipmni13 ipmni14 ipmni15 ipmni16 [slot/slice 1/0] [chipset C1] [ONLINE] [] [slot/slice 8/0] [chipset C1] [ONLINE] [] [slot/slice 9/0] [chipset C2] [ONLINE] [] [slot/slice 16/0] [chipset C1] [ONLINE] [] [slot/slice 2/0] [chipset C1
Troubleshooting IP Multicast Switching (IPMS) Dshell Troubleshooting IPMFM> dst HASH Destination IP VLAN VPN VCI TYPE ID ==== ==================== ==== === ==== ========== ==== 0000 0.0.0.0 0526 128 0000 NATV 0014 0001 0534 128 0000 NATV 0014 0001 0535 128 0000 NATV 0014 0001 ….[ Deleted lines to reduce size].... 0532 128 0000 NATV 0014 0001 0508 128 0000 NATV 0014 0001 0527 128 0000 NATV 0014 0001 0090 239.0.0.90 0549 012 0000 NATV 0001 0001 0257 239.1.1.1 0500 128 0000 NATV 0014 0001 0278 224.0.1.
Troubleshooting IP Multicast Switching (IPMS) 1:0 menu route 1:0 menu cmm 1:0 1:0 alarm 1:0 error 1:0 alert 1:0 config 1:0 table 1:0 egress 1:0 hardware 1:0 ingress igmp 1:0 message 1:0 ingress native 1:0 port updates 1:0 ingress tunnel 1:0 value = 0 = 0x0 Dshell Troubleshooting - 0x4 - 0x8 - 0x8 0x80 0x800 0x8000 0x80000 0x800000 0x8000000 0x80000000 0x4000 0x40000 0x400000 0x40000000 1:0 nidbg> ipms_dbg|=0x40000; taskDelay 120; ipms_dbg 1:0 value = 262396 = 0x400fc THU JUN 09 11:50:49 : IPMS (17) inf
Troubleshooting IP Multicast Switching (IPMS) 1:0 1:0 create 1:0 enqueue 1:0 global drop 1:0 flow drop 1:0 buffer 1:0 lock 1:0 queue 1:0 no frame 1:0 drops 1:0 lookup 1:0 fragment 1:0 frame 1:0 ip cksum 1:0 igmp cksum 1:0 grp 1:0 alloc 1:0 modify 1:0 free 1:0 send 1:0 recv 1:0 flow 1:0 duplicate 1:0 recovery 1:0 value = 0 = 0x0 OmniSwitch Troubleshooting Guide - Dshell Troubleshooting 0 0 0 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 September 2005 page 14-15
Troubleshooting IP Multicast Switching (IPMS) OmniSwitch Troubleshooting Guide September 2005 Dshell Troubleshooting page 14-16
Troubleshooting IP Multicast Switching (IPMS) OmniSwitch Troubleshooting Guide September 2005 Dshell Troubleshooting page 14-17
Troubleshooting IP Multicast Switching (IPMS) OmniSwitch Troubleshooting Guide September 2005 Dshell Troubleshooting page 14-18
Troubleshooting IP Multicast Switching (IPMS) OmniSwitch Troubleshooting Guide September 2005 Dshell Troubleshooting page 14-19
Troubleshooting IP Multicast Switching (IPMS) OmniSwitch Troubleshooting Guide September 2005 Dshell Troubleshooting page 14-20
15 Troubleshooting DVMRP In This Chapter “Introduction” on page 15-2 “DVMRP Troubleshooting” on page 15-2 “DVMRP Global and Interface Commands” on page 15-2 “DVMRP Debug Commands” on page 15-4 OmniSwitch Troubleshooting Guide September 2005 page 15-1
Introduction Troubleshooting DVMRP Introduction DVMRP is used to route Multicast packets through different IP Networks. This is a Dense Mode Multicast Routing Protocol. Dense Mode refers to the network environment the protocol was designed to service. Dense Mode protocols are designed for LAN environments where there are a lot of users and bandwidth is plentiful.
Troubleshooting DVMRP Route Timeout DVMRP Troubleshooting = 140, Number of Routes = 6, Number of Reachable Routes = 6 -> show ip dvmrp interface Address Vlan Tunnel Metric Admin-Status Oper-Status -----------------+------+--------+--------+---------------+------------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 If an interface is not enabled then no multicast traffic will be routed to that VLAN the Interface represents.
DVMRP Troubleshooting 192.168.10.1 192.168.11.1 192.168.12.1 Troubleshooting DVMRP 1 2 3 No No No 1 1 1 Enabled Enabled Enabled Enabled Enabled Enabled Remote routes will be seen if they are learned from another switch. Again be sure that the interfaces are enabled. If that is the case it possible that the other switch is not configured correctly. If the above commands look good in your switch and in the other switches you can use the following command to see if the switch has a next hop.
Troubleshooting DVMRP DVMRP Troubleshooting The third command turns on the debug level. The low is 0, which is no debugging at all, and the high is 110, which prints everything to the screen. There is so much going on in the switch and so much put to the screen that an explanation of what level would bring what output. Instead we are recommending that a setting of 95 is the most useful setting.
DVMRP Troubleshooting tDvmrp-: tDvmrp-: tDvmrp-: 192.168.11.0 tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 192.168.12.0 tDvmrp-: 192.168.12.0 tDvmrp-: tDvmrp-> -: 255.255.255.255 tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 224.2.178.69 tDvmrp-: tDvmrp-: tDvmrp-: 255.255.255.
Troubleshooting DVMRP tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 224.2.142.227 tDvmrp-: tDvmrp-: tDvmrp-: 255.255.255.255 tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 224.2.142.227 tDvmrp-: 255.255.255.255 tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 224.2.178.69 tDvmrp-: 255.255.255.
DVMRP Troubleshooting tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 192.168.10.
Troubleshooting DVMRP tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 255.255.255.0 tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 255.255.255.0 tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 255.255.255.0 tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 255.255.255.0 tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 255.255.255.0 tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 255.255.255.
DVMRP Troubleshooting tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 192.168.10.
Troubleshooting DVMRP tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 192.168.12.0 tDvmrp-: 192.168.14.0 tDvmrp-: 192.168.15.0 tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 255.255.255.
DVMRP Troubleshooting Troubleshooting DVMRP 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.168.11.2] no longer a subordinate for rt 192.168.10.0 tDvmrp-: dvmrpComputeForwardingVectorForRoute: call it... tDvmrp-: dvmrpComputeForwardingVector: tDvmrp-: For rt 192.168.10.0 - grp 224.2.142.227 tDvmrp-: #subords=1, pruncnt=1 tDvmrp-: Looking at V1... tDvmrp-: Looking at V2...
Troubleshooting DVMRP tDvmrp-: 255.255.255.0 tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 192.168.11.
DVMRP Troubleshooting Troubleshooting DVMRP 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.2.178.69 not learned on V1 tDvmrp-: Looking at V2... tDvmrp-: V2 not sub/nbr tDvmrp-: Looking at V3... tDvmrp-: V3 not sub/nbr tDvmrp-: V3 not rib->upstrVl=2, may need forwarding tDvmrp-: Group 224.2.178.
Troubleshooting DVMRP tDvmrp-: 192.168.13.0 tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 192.168.11.2 tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 192.168.11.
DVMRP Troubleshooting tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 192.168.11.2 tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 192.168.11.2 tDvmrp-: 192.168.11.2 tDvmrp-: 224.0.1.24 tDvmrp-: 192.168.11.2 tDvmrp-: 224.2.142.
Troubleshooting DVMRP -> tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 255.255.255.0 tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 255.255.255.0 tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 255.255.255.0 tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 255.255.255.0 tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 255.255.255.
DVMRP Troubleshooting Troubleshooting DVMRP tDvm-> rpshow -: Metric orig=1, adj=2 tDvmrp-: dvmrpUpdateReachable: tDvmrp-: dvmrpRibResetAgeoutTimer: -> show ip dvmrp route tDvmrp-: tDvmrp-: 255.255.255.0 tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 255.255.255.0] tDvmrp-: 192.168.10.
Troubleshooting DVMRP tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 255.255.255.0 tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 255.255.255.0 tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 255.255.255.0] tDvmrp-: 192.168.12.0 tDvmrp-: 255.255.255.0 tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 255.255.255.0 tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 255.255.255.0] tDvmrp-: 192.168.14.0 tDvmrp-: 255.255.255.0 tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: tDvmrp-: 255.255.255.0] tDvmrp-: 192.168.15.
DVMRP Troubleshooting 100| 515| 172.100.1.25| 172.65.1.25| Troubleshooting DVMRP 255.255.255.0| 255.255.0.
16 Troubleshooting PIM-SM In order to troubleshoot issues related to Protocol Independent Multicast-Sparse Mode (PIM-SM), a basic understanding of the protocol—as well as IP multicast technology—are required. Basic PIM-SM concepts are explained below; for detailed protocol specifications please refer to RFC 2362 (PIM-SM) as well as the OmniSwitch 7700/7800/8800 Advanced Routing Configuration Guide, which contains a protocol overview and PIM-SM configuration information.
Introduction Troubleshooting PIM-SM Introduction Traditional multicast routing protocols like DVMRP, MOSPF or PIM-DM were implemented to provide multicast routing in campus network. These traditional dense mode multicast protocol were intended for use within regions where a group is widely represented or bandwidth is not an issue.
Troubleshooting PIM-SM Protocol Overview Protocol Overview DR Election Hello messages are sent periodically between PIM neighbors. This informs routers which interface has PIM neighbors. Hello messages are multicast packets using address 224.0.0.13, which corresponds to ALL-PIM-ROUTERS group. When a router receives a Hello message, it stores the IP address for that neighbor and determines the Designated Router (DR) for that specific interface. The highest IP address system is elected DR.
Protocol Overview Troubleshooting PIM-SM PIM: ----- PIM Header ----PIM: PIM: Version = 2 PIM: Message Type = 0 (Hello) PIM: Reserved = 0 PIM: Checksum = 4017 (correct) PIM: Option Type = 1 (PIM-SM) PIM: Option Length = 2 PIM: Option Value = 0x0069 (Hold time in seconds) Debugging Hello Messages To debug DR election and view Hello messages sent and received on PIM router interface, use the following commands: -> ip pimsm debug-type hello -> ip pimsm debug-level 100 Debug output: tPimsm-: Se
Troubleshooting PIM-SM Protocol Overview Related CLI Command To view if a PIM router interface is the DR for the LAN segment, enter the following command: -> show ip pimsm neighbor Neighbor Address Vlan Uptime Expires Mode -----------------+--------+-----------+-----------+--------192.168.11.2 2 17h:49m:48s 00h:01m:28s Sparse (DR) 192.168.12.2 2 17h:19m:34s 00h:01m:15s Sparse (DR) If (DR) is not present it means the interface has not DR role on the segment.
BSR Election Troubleshooting PIM-SM BSR Election Candidates-BSR sends Bootstrap messages within its PIM-SM domain. Bootstrap messages are multicast to the ALL-PIM-ROUTERS group. Bootstrap message parameters C-BSR ID, which are equal to the BSR IP address, and the C-BSR priority, are used for the BSR election. The BSR will be the router with the highest priority; in case the routers have the same priority, the highest IP address will become the BSR.
Troubleshooting PIM-SM BSR Election Simplified Packet Format IP: ----- IP Header ----IP: Protocol = 103 (PIM) IP: Source address = [192.168.11.2] IP: Destination address = [224.0.0.
BSR Election Troubleshooting PIM-SM 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 preferred bsr 192.168.11.1, Pri 0. Bsr 192.168.11.2, Pri 0 Bootstrap message received and action taken, notice BSR ID and BSR priority. tPimsm-: Received bootstrap message from 192.168.11.1, bsr addr:192.168.11.1 on vlan 1 tPimsm-: Ignoring less preferred bsr 192.168.11.1, Pri 0. Bsr 192.168.11.
Troubleshooting PIM-SM BSR Election Related CLI Command To view which routers are assuming the role of the BSR, expiry time, C-BSR address, and C-BSR priority, type: -> show ip pimsm Status BSR Address BSR Expiry Time CBSR Address CBSR Mask Length CBSR Priority ....... = = = = = = enabled, 192.168.13.1, 00h:02m:01s, 0.0.0.0, 30, 0, IF you don’t want a PIM router to assume BSR role, enter the following syntax: -> no ip pimsm cbsr-address This command will result in a C-BSR address of 0.0.0.
C-RP Advertisements Troubleshooting PIM-SM C-RP Advertisements Candidate-RPs advertisements are periodically unicast from the C-RP to the BSR. These advertisements contain group multicast address the router can be responsible for and the priority for the corresponding group address. C-RP could be configured to participate as RP for specific multicast groups or for all multicast groups. Highest priority will be 0.
Troubleshooting PIM-SM C-RP Advertisements PIM: ----- PIM Header ----PIM: Version =2 PIM: Message Type = 8(Candidate-RP-Advertisement) PIM: Reserved =0 PIM: Checksum = 269d (correct) PIM: Prefix count PIM: Priority =1 =0 PIM: Holdtime = 150 (in seconds) PIM: *** Encoded-Unicast-RP-Address *** PIM: Address family = 1 (IP (IP version 4)) PIM: Encoding type = 0 PIM: Unicast address = [192.168.11.
C-RP Advertisements Troubleshooting PIM-SM Another output from a C-RP advertisement, advertises itself for all multicast groups. All group addresses are represented by the pair 224.0.0.0 240.0.0.0, which covers 224.0.0.0 up to 239.255.255.255. tPimsm-: Recv. CRP-Adv (RP:192.168.10.3,Prefix Cnt:1, Pri:0) from 192.168.10.3:192.168.11.1 on vlan 2 tPimsm-: RP : 192.168.10.3 : Prefix: 224.0.0.0 Mask : 240.0.0.
Troubleshooting PIM-SM RP-SET RP-SET An RP-SET contains a set of Candidates-RP IP addresses that want to participate as RP for multicast group. The RP-SET is derived from the C RP-Advertisements received by the BSR. RP-SETs are advertised by the BSR in a bootstrap message to all PIM SM routers by using the ALL-PIM-ROUTER address 224.0.0.13. It contains details on the each C-RP IP address, the multicast group routers want to participate and the corresponding priority.
RP-SET Troubleshooting PIM-SM Simplified Bootstrap RP-SET Packet Taken on a 192.168.12/24 Network IP: ----- IP Header ----IP: Version = 4, header length = 20 bytes IP: Protocol = 103 (PIM) IP: Source address = [192.168.12.1] IP: Destination address = [224.0.0.
Troubleshooting PIM-SM RP-SET PIM: RP1-Holdtime = 150 (in seconds) PIM: RP1-Priority =0 PIM: Reserved =0 PIM: PIM: *** Encoded-Group Address # 2 *** PIM: Address family = 1 (IP (IP version 4)) PIM: Encoding type =0 PIM: Reserved PIM: Mask length =0 = 32 PIM: Group multicast address = [226.1.1.
RP-SET Troubleshooting PIM-SM PIM: *** Encoded-Unicast RP Address # 1 *** PIM: Address family = 1 (IP (IP version 4)) PIM: Encoding type = 0 PIM: Unicast address = [192.168.12.2] PIM: RP1-Holdtime = 150 (in seconds) PIM: RP1-Priority =0 PIM: Reserved =0 The RP-Holdtime parameters is the corresponding time the BSR will hold related RP multicast group information in its table as valid. This parameter is reset to 150 s when a C-RP Advertisement is received at BSR and originated by the RP in question.
Troubleshooting PIM-SM RP-SET Related CLI Command To View RP-SET on a router, use the show ip pimsm rp-set command. For example: -> show ip pimsm rp-set Group Address Address Holdtime Expires ------------------+---------------+--------+----------225.1.1.1/32 192.168.11.2 150 00h:00m:00s 226.1.1.1/32 192.168.12.2 150 00h:00m:00s 227.1.1.1/32 192.168.12.
Join/Prune Troubleshooting PIM-SM Join/Prune Join/Prune messages are sent by the DR to join or prune a branch off the multicast distribution tree in order to receive multicast group on a specific LAN segment that has active group members. Registration of the members is achieved with IGMP host membership report.
Troubleshooting PIM-SM Join/Prune PIM: ----- PIM Header ----PIM: PIM: Version =2 PIM: Message Type = 3(Join/Prune) PIM: Reserved =0 PIM: Checksum = 5794 (correct) PIM: PIM: *** Encoded-Unicast-Upstream Neighbor Address *** PIM: Address family = 1 (IP (IP version 4)) PIM: Encoding type = 0 PIM: Unicast address = [192.168.12.
Join/Prune Troubleshooting PIM-SM PIM: .... ..1. = WC bit - join / prune applies to the (*,G) or (*,*,RP) entry PIM: .... ...1 = RPT-bit - information about (S,G) is sent towards the RP PIM: Mask length = 32 PIM: Source address = [192.168.11.
Troubleshooting PIM-SM Register Register When a source starts transmitting to a multicast group, the DR on the segment encapsulates the data and sends it as unicast to the RP representing the group. The source IP address will be the DR and the destination IP address will be the RP. Two behaviors are possible: 1-The RP joins the source tree by sending a PIM join to the DR. Packets will then flow from the source to the RP unencapsulated. 2-The RP does not join the source tree.
Register Troubleshooting PIM-SM Simplified REGISTER Packet Format IP: ----- IP Header ----IP: Source address = [192.168.13.1] IP: Destination address = [192.168.11.2] PIM: ----- PIM Header ----PIM: Version =2 PIM: Message Type = 1(Register) PIM: Reserved PIM: Checksum PIM: Reserved PIM: Flags =0 = deff (should be 45b5) =0 = 00 PIM: 0... .... = Border bit - router is a DR for a source that i PIM: .0.. ....
Troubleshooting PIM-SM Shared Tree Shared Tree A shared distribution tree is formed around the RP, from which all traffic is distributed regardless of the location of the traffic sources. The advantage of shared distribution trees is simple topology on PIM SM routers. The DR is sending a JOIN message to the RP, and a graft to the SPT. The disadvantage is that the path between the source and receivers might not be the shortest one, which could introduce delay.
Shared Tree Troubleshooting PIM-SM Related CLI Command In order to view the IP multicast routing table as well as source and distribution tree type: -> show ip pimsm mroute Group Address Assert Assert Assert Flags Metric expires Pref ---------------+------------------+------+-----------+------+----225.1.1.1 192.168.14.
Troubleshooting PIM-SM Source-Based Tree Source-Based Tree PIM SM protocol allows a DR to build a Shortest Path Tree, which could provide a shortest path toward the source. It is being referenced as Source Based Tree because the DR closest to the receiver is initiating the process. When a PIM SM graft the shared path tree, a counter is initiated for this specific group on the last DR closest to the receiver that will be incremented every data packet received.
Source-Based Tree Troubleshooting PIM-SM Related CLI Command To view the distribution tree issue: -> show ip pimsm mroute Group Address Assert Assert Assert Flags Metric expires Pref ---------------+------------------+------+-----------+------+----225.1.1.1 192.168.14.
Troubleshooting PIM-SM Troubleshooting Examples: Limitations Troubleshooting Examples: Limitations Incorrect BSR ID Turn on BSR debugging to view bootstrap messages: -> ip pimsm debug-type bootstrap -> ip pimsm debug-level 100 tPimsm-: Received bootstrap message from 192.168.11.1, bsr addr:192.168.13.1 on vlan 2 tPimsm-: RPF check failed for bootstrap msg. SA: 192.168.11.1,BSR :192.168.13.
Troubleshooting Examples: Limitations -> show ip pimsm Status BSR Address BSR Expiry Time CBSR Address CBSR Mask Length CBSR Priority CRP Address CRP Hold Time CRP Expiry Time CRP Interval CRP Priority Data Timeout Join/Prune Interval Max RPs Probe Time Register Checksum Register Suppress Timeout Troubleshooting PIM-SM = = = = = = = = = = = = = = = = = enabled, 192.168.13.1, 00h:01m:43s, 0.0.0.0, 30, 0, 192.168.12.
Troubleshooting PIM-SM Troubleshooting Examples: Limitations -> debug ip pimsm rp Group Address RP Address ------------------+-----------------224.0.1.22 172.100.1.254 224.0.1.24 172.100.1.254 239.0.0.90 172.100.1.254 239.1.1.200 172.100.1.254 239.1.1.201 172.100.1.254 239.1.1.202 172.100.1.254 239.255.255.254 172.100.1.
Troubleshooting Examples: Limitations page 16-30 Troubleshooting PIM-SM OmniSwitch Troubleshooting Guide September 2005
17 Troubleshooting Server Load Balancing In order to successfully troubleshoot the Alcatel Server Load Balancing feature, a brief understanding of this services functions are necessary. Our Basic Definition The “Server Load Balancing” (SLB) term used in this document refers to the functionality of distributing client requests across servers logically grouped in “clusters.” A “cluster” logically aggregates a set of servers that run identical applications with access to the same content (e.g.
Introduction Troubleshooting Server Load Balancing Introduction The primary function of a Server Load Balance cluster is to provide a method to logically treat a group of physical servers (known as a server farm) as one large virtual server (known as an SLB cluster). Note. This document does not discuss the basic operation of Server Load Balancing. To learn about how SLB works, refer to “Configuring Server Load Balancing” in the OmniSwitch 7700/7800/8800 Network Configuration Guide.
Troubleshooting Server Load Balancing Troubleshooting Commands Troubleshooting Commands Below is a list of commands, which will be used and discussed in this chapter. show ip slb (Displays SLB information) show ip slb cluster-name For example: -> show ip slb cluster Intranet Cluster Intranet VIP : 128.241.130.
Troubleshooting a Complete Failure Troubleshooting Server Load Balancing Troubleshooting a Complete Failure Gathering pertinent information is essential in order to properly characterize the problem. Obtain symptom facts, review all recent network or architecture changes, localize the problem, e.g. does it affect only certain floors, or departments? Devise an action plan. The first step in any troubleshooting process is to gather information.
Troubleshooting Server Load Balancing Troubleshooting a Partial Failure Troubleshooting a Partial Failure The number one cause of a partial failure is misconfiguration. In the following area, we will show you how to determine the SLB configuration. The Troubleshooting Procedure If you have reason to believe that the SLB cluster is operational, however inaccessible, Alcatel’s 7700/ 7800/8800 provides useful commands for narrowing down the problem.
The Troubleshooting Procedure page 17-6 Troubleshooting Server Load Balancing OmniSwitch Troubleshooting Guide September 2005
18 Troubleshooting Authenticated VLANs In order to troubleshoot Authenticated VLAN (AVLAN), a basic understanding of how authentication works in the switch is required. Understanding of Radius and DHCP server will be useful in troubleshooting Authenticated VLAN. Note. Reading the “Managing Authentication Servers” and the “Configuring Authenticated VLANs” chapters in the appropriate OmniSwitch Network Configuration Guide is highly recommended.
Troubleshooting AVLAN Troubleshooting Authenticated VLANs Troubleshooting AVLAN DHCP Request Failure If the client (PC-1) is configured to get the DHCP IP address and can not get DHCP address during the first phase of authentication process, it could be because of wrong configuration in the switch, communication failure or miss configured DHCP server.
Troubleshooting Authenticated VLANs 192.168.10.100 Troubleshooting AVLAN 00:c0:4f:0c:3a:e4 DYNAMIC 1/21 vlan 2 There are couples of other things you can verify is on the DHCP server itself. • Router IP address is set to the IP address of one of the authenticated VLANs in the switch. • Address pool must be created in order to assign the DHCP IP address.
Troubleshooting AVLAN Troubleshooting Authenticated VLANs -> show mac-address-table Legend: Mac Address: * = address not valid Vlan Mac Address Type Protocol Operation Interface ------+-------------------+--------------+-----------+------------+----------2 00:c0:4f:0c:3a:e4 learned Total number of Valid MAC addresses above = 1 0 bridging 1/21 Now verify that the Gateway defined in RADIUS server point towards the right IP address.
Troubleshooting Authenticated VLANs Troubleshooting Using Debug Systrace Useful Notes on Client Issues • If using telnet authentication manual IP release and renew required getting the new IP after authentica- tion. Troubleshooting Using Debug Systrace Telnet Authentication and De-authentication Do not change the aaaDebugFunction flag under Dshell, keep it the default setting.
Troubleshooting Using Debug Systrace Troubleshooting Authenticated VLANs Initiate the Telnet Authentication -> 2394037098 AAA debug1 Send AAA_HDL_MGT_USER_REQ 2394037225 AAA debug1 Message succefully sent 2394037384 AAA debug3 Entering in aaa_ProcessHdlMsg 2394037565 AAA debug1 AVLAN begin Evt : Req,St : IDLE, name : Avlan ses 0x60008 00.00.00.00.00.
Troubleshooting Authenticated VLANs Troubleshooting Using Debug Systrace Chal_Rsdebug3p link, set in No linkEntering in aaaAvlanAuthRspOK2 3971075352397129005 AAAAAA debudebug3g1 AAA_Serv>>End Authent Evt St :entering in aaaAvla IDLE, name : , ses nSendOneCtxToSeconda: 0/ 0, Ret = OryCmm K 2397304273 AAA debug2 SL 0xa0070 00.90.27.75.dc.a2, VL 103, proto 1 p 1 2397391330 AAA debug3 Entering in aaaAvlanReplyHdlMgt 2397455810 AAA debug1 Send Authent.
Troubleshooting Using Debug Systrace Troubleshooting Authenticated VLANs chaddr=00:90:27:75:dc:a2 2476995124 AAA debug2 sname=<>file=<> 2476995365 AAA debug1 DHCP Release sent successfully 2477000684 AAA debug3 AAA_Serv>> sort aaaSortUserCtx HTTP/S Authentication Start of Authentication using https://x.x.x.253 -> 2163508216 AAA debug3 Entering in aaa_ProcessHdlMsg 2163508471 AAA debug1 AVLAN begin Evt : Req,St : IDLE, name : Avlan ses 0x9000b 00.00.00.00.00.
Troubleshooting Authenticated VLANs Troubleshooting Using Debug Systrace name : admin, Rec(TRUNCATED) 2165965890 AAA debug3 Entering in aaa_AuthRspOK 2166030420 AAA debug3 Entering in aaa_ReplyHdlMgt 2166095975 AAA debug1 Send auth Success, session 9000b 2166161550 AAA debug32166161654 EntAAAering in aaa_user ReturnST_IDLEde2166227153bug1 AAAA VLAN begin Evt : Auth Reply Ok,St : debug1WAIT RESP, nam e : admin Avlan se(AAA_Serv>> Ctx adminTRUNCATED) removed from Chal_Rsp link, 2166400173set in No linkAAA 2
Troubleshooting Using Debug Systrace Troubleshooting Authenticated VLANs AVClient AVClient Authentication Start -> 1592327563 AAA debug3 XCAP rec. from Auth Dispat 00.90.27.75.dc.
Troubleshooting Authenticated VLANs Troubleshooting Using Debug Systrace 1595408715 AAA info [RAD] rad_buildauth: port 1 added to access-request 1595473430 AAA info [RAD] radDoSend OK : id=9, addr=0x8502fd01 port=1645 try=1 1595582865 AAA info [RAD] radDoSend OK : id=9, addr=0x8502fd01 port=1645 try=1 1595670050 AAA debug3 [RAD] radProcPkt: Got a reply from Radius server , id = 9, code 2, length 59 1595778543 AAA info [RAD] radProcPkt: Attribute type 25, length 27 1595865571 AAA info [RAD] radProcPkt: cla
Dshell Troubleshooting Troubleshooting Authenticated VLANs 1628234512 AAA debug3 aaaHdlUtilBufInNormalList, free Id 108802664, typ 8 1628234571 AAA debug1 Send AAA_HDL_MGT_LOGOUT_REQ 1628234637 AAA debug1 Message succefully sent 1628234753 AAA debug3 Entering in aaa_ProcessHdlMsg 1628234810 AAA debug3 Entering in aaaAvlanReplyHdlFailNoCtx 1628298934 AAA debug1 Send authent.
Troubleshooting Authenticated VLANs Dshell Troubleshooting - adDebugSetFilterLevel 0xX - adDebugSetFilterPort X Bit 9: Configuration : Set trace level filter X = Bit field Bit 1: ERROR Bit 2: WARNING Bit 3: INFO : Set user port number filter Available only for INFO's trace X = 0 = No filter : Display Authentication IP addresses configured : Display AD's context : Display debug counters : Display 802.
Dshell Troubleshooting Authenticated MAC address XCAP 802.3 SNAP header Authenticated DNS name 802.1x EAPol SNAP header 802.1x Authentication control 802.1x Authentication share 802.1x PAE group MAC address 802.1x node MAC address Debug level Debug frame type filtered Debug user port filtered Debug dump value = 1031 = 0x407 Troubleshooting Authenticated VLANs = = = = = = = = = = = = 00.20.DA.00.00.02 AA.AA.03.00.20DA.0202 authent.com AA.AA.03.00.0000.888E Disable (2) Unic (2) 01.80.C2.00.00.03 00.D0.95.
Troubleshooting Authenticated VLANs Dshell Troubleshooting XCAP: Unexpected message identifier rcv.= 0 value = 1866 = 0x74a To verify the Authentication IP bound to each VLAN with subnet mask please run the adDebugShowAvlanIp command. Working: [Kernel]->adDebugShowAvlanIp AD show AVLAN IP addresses VLAN number IP address Mask Authentication IP address = = = = 1 10.0.0.92 255.255.0.0 10.0.0.253 VLAN number IP address Mask Authentication IP address = = = = 13 10.4.2.18 255.255.0.0 10.4.0.
Dshell Troubleshooting page 18-16 Troubleshooting Authenticated VLANs OmniSwitch Troubleshooting Guide September 2005
19 Troubleshooting 802.1X The 802.1X standard defines port-based network access controls, and provides the structure for authenticating physical devices attached to a LAN. It uses the Extensible Authentication Protocol (EAP). Note. See the “Configuring 802.1X” chapter in the appropriate OmniSwitch Network Configuration Guide for a detailed explanation about different 802.1X components. Understanding and troubleshooting of Radius Server in conjunction with switch level troubleshooting is very helpful.
Troubleshooting with the CLI Troubleshooting 802.1X Troubleshooting with the CLI 1 Make sure the Radius and Accounting ports are configured the same on both switch and Radius Server. The default on the Radius Server can be either 1645/1812 for Radius and 1646/1813 for the Accounting. Layer-2: show aaa server Server name = rad1 Server type = RADIUS, IP Address 1 = 133.2.253.1, Retry number = 3, Time out (sec) = 2, Authentication port = 1645, Accounting port = 1646 2 Verify the port is configured for 802.
Troubleshooting 802.1X Authentication IP Router Port IPX Router Port Troubleshooting with the CLI : enabled, : none, : none, 6 Verify the status of the 802.1x port using the show 802.1x command. Read the OmniSwitch CLI Refer- ence Guide to understand the explanation for each field. Layer-2: show 802.1x 2/3 802.
Troubleshooting Using Debug CLI Troubleshooting 802.1X Troubleshooting Using Debug CLI Assuming Radius communication takes place on UDP port 1645: Layer-2: debug ip packet protocol udp port 1645 start C C C C 1 1 1 1 1 1 1 1 2 2 2 S R S R R S R S R S R S R R R 1/1 1/1 1/1 1/1 CMM 1/1 1/1 CMM CMM 1/1 1/1 CMM 2/3 2/3 2/3 00d09579640e->00d0956af558 IP 10.1.1.1->133.2.253.1 UDP 1025,1645 00d0956af558->00d09579640e IP 133.2.253.1->10.1.1.1 UDP 1645,1025 00d09579640e->00d0956af558 IP 10.1.1.1->133.2.253.
Troubleshooting 802.
Troubleshooting Using Debug CLI Troubleshooting 802.
Troubleshooting 802.1X Dshell Troubleshooting Dshell Troubleshooting Note. Dshell commands should only be used by Alcatel personnel or under the direction of Alcatel. Misuse or failure to follow procedures that use Dshell commands in this guide correctly can cause lengthy network down time and/or permanent damage to hardware. Launch the NiDebugger. Go to the NI where user is connected.
Dshell Troubleshooting Troubleshooting 802.1X 2:0 Direction = In-Out (0) 2:0 Source MAC addr. = 00.00.00.00.00.00 2:0 value = 0 = 0x0 To verify the sequence of the packet flow, set the below Dshell flags to troubleshoot the issue. The best way to troubleshoot is to compare the failed case with good case. 2:0 nidbg> adDebugSetFilterFrame 0xffff 2:0 nidbg> adDebugSetFilterLevel 0xff 2:0 AD INFO-> 802.1x port config.rcv.: Msg.=0x4370000 2:0 2:0 AD INFO-> 802.1x port config.rcv.: 2:0 Slot=2,Msg.
Troubleshooting 802.1X Dshell Troubleshooting 2:0 2:0 AD INFO-> EAPol pkt.sent out: 2:0 Slot=2,Glb.port=0x22,User port=3,Frame=0x4479000 2:0 2:0 AD INFO-> EAPol pkt.from supplicant, rcv.on 802.1x glb.port=0x22,user port=3: sent to 802.1x CMM: 2:0 Slot=2,802.1x port's state=6,Auth.Ctrl=1,Auth.Share=2, 2:0 Src.MAC addr.=00.0F.1F.D5.54.95,Cond.codes=0x8080,Frame=0x447c800 2:0 2:0 AD INFO-> EAPol pkt.sent to AAA's 802.1x: 2:0 Slot=2,Glb.port=0x22,User port=3,Msg.=0x15cfe90 2:0 2:0 AD INFO-> 802.
Dshell Troubleshooting page 19-10 Troubleshooting 802.
A OS6600/OS7700/OS8800 Architecture Overview The switch benefits from an intelligent, multi-layer switching, fully distributed and passive backplane architectural design that provides redundancy of critical hardware and software elements for a continuous (non-stop) traffic processing in any network conditions without a single point of failure. Switch processing scheme includes a non-blocking store-and-forward crossbar design switching fabric with a distributed processing.
The MAC ASIC The MAC ASIC There are two different types of MAC layer ASICs: • Catalina • Firenze Catalina The Catalina basically provides three functions: Media Access Control (MAC) Layer functions, data buffering, and statistics accumulation and storage for each port. The Catalina provides the interface between Ethernet analog devices (10/100 Mbps and 1000 Mbps) and the Coronado.
The MAC ASIC F-BUS Coronado GNI-U-2 OS-7XXX XY-BUS Catalina 0 Catalina 1 1 Gig Port 1 Gig port F-BUS F-BUS Coronado 0 … XY-BUS Catalina 0 Gigabit port 1 Coronado 3 XY-BUS Catalina 1 Gigabit port 2 Catalina 6 Gigabit port 7 Catalina 7 Gigabit port 8 GNI-U/C-8 OS-8800 OmniSwitch Troubleshooting Guide September 2005 page -3
The MAC ASIC Firenze The Firenze basically provides three functions: Media Access Control (MAC) Layer functions, Data buffering, Flow Control and statistics accumulation and storage for each port. Firenze handles up to six Ethernet interfaces that can support independently either 10 or 100 or 1000 Mbit/ s throughput using independently either TBI or GMII interfaces. The Firenze Based GNI is a 1Gbps Ethernet Switching Module for the Falcon system.
The MAC ASIC F-BUS F-BUS Coronado 0 Coronado 3 … XY-BUS XY-BUS Firenze 1 Firenze 0 6 Gigabit ports 6 Gigabit ports Firenze 6 6 Gigabit ports Firenze 7 6 Gigabit ports GNI-U/C-24 OS-8800 The Coronado ASIC The Coronado ASIC is the centerpiece of this advanced architectural design. While each ASIC performs a vital function in the overall architecture, the Coronado provides most of the key features like wire-rate L2 and L3 switching and routing.
The MAC ASIC The Coronado ASIC contains both Ingress and Egress functions. Ethernet frames flow from the Catalina through the Ingress Coronado, through the Nantucket switch fabric, then through the Coronado Egress logic and finally out the Egress Catalina. Note: Frames always flow through the Nantucket, even if the input and output ports are on the same Coronado ASIC. One or more Coronado ASIC are located on the network interface cards.
The MAC ASIC Coronado: The “Brain” of the System • Provides hardware performance for most features on the OmniSwitch. • Involved in both the ingress and egress packet processing. • Provides a high speed connection to Catalina via the XYBUS. XYBUS is two unidirectional busses between Catalina and Coronado. XYBUS is 1.24 Gbps. • Provides 2 high speed connections to the fabric via the FBUS. An FBUS is two unidirectional busses. • Provides connections to all the ASICs via the management BUS known as BBUS.
Queue Driver Interaction • Queues are maintained by the software module known as the Queue Driver runs on each NI. It provides the interaction to other software modules in the Falcon/Eagle product to create/modify/delete/manage all the queues in the system. This module provides debugging information required for the queues and maintains the statistics. This module maintains all the information required about all the queues on the Coronado.
Queue Driver Interaction NI Supervision Queue driver sends the task initialization and task ready messages to the NI Supervision task just before receiving any configuration information from the CMM Ethernet driver. This indicates to the NI supervision task that the queue driver task is ready. Source Learning L2 Destination Address Manager is a software block of Source Learning. It is responsible for destination MAC address learning and programming the L2 destination address pseudo cam on the Coronado.
Queue Driver Interaction QoS Policy Deleted When a QoS Policy is deleted, the QoS Manager is notified. It checks to see if there are any flows associated with the QoS Policy. The queue id for all the pseudo cam entries associated with the policy should be reprogrammed with a default queue and the existing queue has to be freed. The QoS Manager requests the Queue Driver to free the queue.
Link Aggregation Link Aggregation Link Aggregation feature allows software to aggregate a set of ports (not necessarily contiguous or on the same Coronado) into a group. Each port is referred to as a channel that can carry some bandwidth. This feature requires that all the queues associated with all the ports in the group to be contiguous. Events resulting in Link Aggregation and Q driver interaction may be for the creation and deletion of link aggregation group.
Source Learning Source Learning Coronado ASIC is a ingress classifier that performs Layer 2 hardware table lookups to the VLAN Id corresponds to the incoming packets. In principle, Coronado will perform a Layer 2 Source Address (L2 SA) lookup based on whether the incoming port is a tagging or non-tagging port, a copy of the packet is re-queued to the Source Learning queue for processing if the lookup fails.
Hardware Routing Engine (HRE) Hardware Routing Engine (HRE) This feature is responsible for managing the Coronado HRE resources that perform IP and IPX packet classification and forwarding. This functionality employees five principal Coronado resources—header cache entries, pseudo-CAM entries, hash function registers, modes, and router MACs.
Hardware Routing Engine (HRE) Router MACs Helps identify candidate traffic for classification. The HRE only operates on traffic that is identified as requiring layers 3 and 4 classification. Candidate traffic for such classification must be of the type IP or IPX and must have its layer 2 destination MAC be a router MAC for this switch or be a bridged MAC that has been marked for layer 3 and 4 classification or be an IP multicast MAC. This feature only manages router MACs.
QoS/Policy Manager QoS/Policy Manager Policies describe subsets of traffic, and what to do with that traffic. The Policy Processor determines what policies are enforceable, and organizes the policies into lists used by the classifier. QoS uses the same policies for Prioritization/Shaping, IP Filtering (ACLs), NAT, and IPMS Filtering.
The Fabric Architecture The Fabric Architecture ASIC provides the switching fabric functionality for the OmniSwitch Series. The switching fabric does no frame processing and does not distinguish between L2 switching and L3 routing. The fabric provides only a limited amount of FIFO buffering for each port, flood and the multicast queue. Most of the system buffering is in the Ingress Coronado’s Queue Manager. The backplane fabric is a bit-sliced ASIC.
Nantucket ASIC Nantucket ASIC The Nantucket ASICs have the following: • Support for 8 and 16 Coronados only. • No dynamic queue numbering for each NI slot. • Fixed eight Nantuckets per Fabric board. • Maximum of one redundant Fabric board. The Nantucket software is arranged as: • Nantucket operational software resides on the CMM. • Nantucket operational software runs on the UltraSPARC IIe on the CMM. • All accesses to Nantucket registers is through the PCI bridge and over the Bbus bridges.
Nantucket ASIC Functional Description: The Nantucket software resides on Chassis Management Module (CMM) and run on the UltraSPARC IIe processor within the CMM. The Nantucket software communicates to the Nantucket ASIC via the PCI Bridge and Bbus Bridges.
Nantucket ASIC Calendar Manager Module • Generates dequeue requests to the Queue Manager module with priorities of uP packets highest, multi- cast packets second highest and unicast packets lowest. • Request dequeues from 512 unicast queues by sending a QID. • Request dequeues from uP queue by sending FIFO ID. • Calendar for a Coronado with 24 10/100 ports would be: 0,1,2,3,4,5,6,7,8,9,...,23. • Calendar for a Coronado with 12 10/100 ports and 1 Gigabit port would be:0,1,0,2,...9,0,10,11,12.
Nantucket ASIC Nantucket 0 Coronado Coronado Coronado Coronado Nantucket 1 Nantucket 2 Nantucket 3 Nantucket 0 Primary CMM Coronado Coronado Coronado Coronado Nantucket 1 page -20 OmniSwitch Troubleshooting Guide September 2005
Nantucket ASIC OS-7700 Backplane Coronado Nantucket 0 Nantucket 0 Coronado Nantucket 3 Nantucket 1 Nantucket 1 Coronado Secondary CMM Coronado Nantucket 2 Nantucket 2 Coronado Coronado Nantucket 3 Nantucket 3 Coronado Nantucket4 Nantucket 4 Coronado Nantucket 5 Nantucket 5 Coronado Coronado Coronado Coronado Coronado Nantucket 6 Nantucket 6 Coronado Nantucket7 Nantucket 7 Coronado Coronado Every Coronado is connected to Primary CMM and secondary CMM with all the Nantuckets.
Roma Roma Each Fabric Module is based on two Roma ASICs, which provide the store-and-forward switching fabric function for the OS-8800 product. The Roma ASIC is bit-sliced; a group of eight Roma ASICs operates together as a single synchronized fabric. A total of four Fabric modules are required to build a complete Fabric in the OS-8800 system. An optional fifth Fabric Module may be used for fabric redundancy. In a group of eight Roma ASICs, there is always one master and seven slaves.
Roma • Separate paychecks for multicast • Generates ingress coupons, receives egress coupons for backpressure capability • Ingress coupon generation period: ~2 microseconds • Paycheck generation period: 32.
Roma Flow Control Coupon and paycheck thresholds are set for unicast and IPC queues (multicast is limited by Coronado for fabric ingress). These thresholds are used to generate ingress backpressure and paycheck messages. Each Roma ASIC participating as an operational bit slice is responsible for 2 NIs according to the scheme: bit slice n is responsible for NI slots 2(n+1) and 2(n+1)-1. Bit slices are zero-based (0 - 7); NI slots are onebased (1 - 16).
Roma Fabric Slot Extraction This state assumes that there are five fabric slots occupied, with one fabric card serving as the redundant card. Roma Driver will have already set up the operational Roma chip set to use built-in hot swap handling. Upon extraction of fabric card, most of the hot swap handling is done by Roma ASIC logic. The performs the following tasks when a fabric card is removed: • Recover the new fabric slot set state since the operational fabric may change.
Chassis Management Module (CMM) Framing Error The Framing Error event represents an event where the Roma ASIC detects an error in a packet header on ingress. Since this will potentially corrupt the buffer system, a free list rebuild is required when this is detected. Coronado ROMA 0 ROMA 1 . . . .
Chassis Management Module (CMM) OS7000 CMM The CMM for OS7000 contains the following: • System Processor • Ultra Space 11e (400MHz) • 64MB SDRAM Memory • Switching Fabrics • 4 Switching fabrics, Nantucket, in OS-7700 • 8 Switching fabrics, Nantucket, in OS-7800 • Management • DB-9 console/modem Port • RJ45-Out of Band 10/100 LAN Port • Reset Switch • Hot Swappable • Up to 2 CMMs per chassis • Management redundancy • Switching Fabric Redundancy OS8800 CMM The CMM for OS8800 contains the following: • System
Chassis Management Module (CMM) Functional Description of CMM Software and Configuration management is implemented in such a way to provide the operator with: • Flexibility • Resiliency • And to minimize the service interruption during the update of a network. • 2 Software versions are stored into flash: • 1 working version: operational release, used for upgrades. • 1 certified version: operator validated trusted release.
Chassis Management Module (CMM) AOS Boot ROM • Sparc Processor executes the Sparc Boot ROM code from flash Memory in the protected memory. • Performs minimum diagnostic tests of the Sparc Processor • Verifies memory used by Sparc Processor is fine • If the diagnostic tests find an error, the CMM/Fabric LED will flash to indicate the error and the processor will retry to boot.
Chassis Management Module (CMM) MiniBoot MiniBoot contains VX Works Operating system Performs the following tasks: • Post Mortem Dump (PMD) Processing to save as much diagnostic as possible in the FFS after a system crash. • Hardware diagnostics to determine if all the boards are operational at boot time. • Image Rollback to select either the current uncommitted (working) software release or the previously- committed (certified) release.
Chassis Management Module (CMM) Running Version Flash Files /flash/boot Boot ROM (Hidden & Protected) MiniBoot 1-Default 2-Backup (Write Protected) Boot.cfg ……… Contains boot Execute Read/Write Miniboot Load Minimum VX Works with File system with PMD process. Boot.
Chassis Management Module (CMM) Software Management Command Fos Configuration Save Version Activate Version Restore Version Certify Version Query BBUS • Falcon Overall Block Diagram NI NI ……… NI NI FBUS Nantuck .. Nantucket Nantucket .. Nantucket Secondary CMM Board Primary CMM Board …. Secondary ….
Chassis Management Module (CMM) • Eagle Overall Block Diagram Fabric Boards R R R R R R R R R R Redundant Fabric Module FBUS NI NI NI CMM NI …. NI CMM BBUS …. Secondary …. Primary • Fabric resides independent of the CMM. It resides at the Back of the Chassis. CMM can fail over inde- pendent of Switching Fabric and vice versa. • Minimum of 4 Switching Fabric Modules (SFM) with 8 ROMS chips are required to operate. The additional SFM provides (4+1) redundancy.
Packet Walk Packet Walk Packet Walk Principles • All switching and routing is performed on the Ingress side of the switch. There are no address lookups made on the Egress side. • The Coronado combines the L2 switching and L3 routing logic into the same ASIC. • Data always flows through the Nantucket even if the source and destination ports are on the same Coronado. • As indicated the “switching fabric” functionality is provided by Nantucket ASICs.
Specific Packet Flows Specific Packet Flows Unknown L2 Source, Known L2 Destination The Catalina ASIC Packet arrives at Catalina. CRC check done. If valid CRC it is put on XYBUS to Coronado The Coronado ASIC • The FIFO logic maintains queues of frames from both Xybus interfaces and selects an incoming frame for HRE processing. This FIFO is done on the on chip memory of the HRE.
Unknown Destination Unknown Destination Known L2 Source, Unknown L2 Destination The Catalina ASIC Packet arrives at Catalina. CRC check done. If valid CRC it is put on XYBUS to Coronado The Coronado ASIC • The FIFO logic maintains queues of frames from both Xybus interfaces and selects an incoming frame for HRE processing. This FIFO is done on the on chip memory of the HRE.
Unknown Destination The Coronado ASIC • The Coronado receives the packet via the FBUS. • The Coronado then strips the 802.1q header that was added on ingress, if needed. The Catalina ASIC • Packet is then put on to the Xybus to be received by the Catalina. • Catalina Egress will generate the CRC and regulate the packet framing including the interpacket gap. • The above delivers the first few packets of a flow that has an unknown destination via the flood queue.
Unknown Destination Unknown L3 DA The Coronado ASIC • The FIFO logic maintains queues of frames from both Xybus interfaces and selects an incoming frame for HRE processing. This FIFO is done on the on chip memory of the HRE. • The parser logic selects fields from the frame to identify the protocol and find key values that are used by the HRE for lookups (DA, SA) • Coronado does a L2 SA pCAM lookup. • Coronado determines this is a known source and retrieves Group ID.
Unknown Destination Packet arrives from Catalina to Coronado Y Pseudo-CAM (PCAM) Provides Group ID (GID) Assign Default GID and sends to S/W N 1 Source Address known ? 2 De Queue packet and perform PCAM update Y Is DA Router MAC, IGMP, STP, Multicast Switching Is DA Special ? 5 N Y Lookup provides QID & Priority Description Index (PDI) Is DA Known? 4 Access PDI to assign internal priority (0…3) & final QID En Queue data to final QID, QID determines destination port, priority & bandwidth N
Unknown Destination 5 Classify Special DA DA is router MAC DA is IGMP DA is IPMS 7 6 DA PCAM lookup, known ? DA is STP multicast (BPDU) S/W 8 L3 FDB? Slow Path Routing N N Y Y Send to Destination Send to Default Gateway Provides a Next_Hop_Header_Cache index NHHC index provides QID, ReQID & PDI 4 Performs NAT, MAC-DA, TTL, SLB and Fragment modifications L3 Packet Walk 7 6 DA is IGMP N L3 DA lookup Pass? S/W QID set to either multicast within the vlan or drop DA is IPMS ReQID Sent
Hardware Buses on OmniSwitch 7700/7800/8800 Switches 8 DA is STP multicast (BPDU) S/W QID for flood or drop ReQID for S/W processing BPDU Hardware Buses on OmniSwitch 7700/7800/ 8800 Switches Xybus The interface between the MAC to Coronado, which is 0-1 Fbus The interface between the Coronado to the Fabric ASIC (Nantucket or Roma). For the OmniSwitch 7700 (Falcon half chassis) it is 0-7. For the OmniSwitch 7800 (Falcon full chassis) it is 0-15. For the OmniSwitch 8800 (Eagle) it is 0-63.
Bus Mapping on OmniSwitch 7700/7800/8800 Switches Bus Mapping on OmniSwitch 7700/7800/8800 Switches Xybus Mapping Each board type has own mapping, described for all existing board type below. • OS7-ENI-C24 and OS8-ENI-C24: Single slice board, connects two Catalina MAC ASICs through xybus0 and xybus1. • OS7-ENI-FM12: Single slice board, connects one Catalina MAC ASICs through xybus0, • OS7-GNI-U2: Single slice board, connects two Catalina MAC ASICs through xybus0 and xybus1.
OS6624/6648 Architecture OS6624/6648 Architecture OmniSwitch 6XXX is a stackable version of the OS7/8XXX Switches. It provides pure Ethernet switching for 10/100 and Gigabit ports, along with stackability.
OS6624/6648 Architecture Hardware Architectural Overview OS6600 uses off the shelf Intel ASIC. Intel IXE2424 Switching ASIC is used to implement the required functionality. The key features of Intel IXE2424 are: • Provides 24 10/100 FE ports and 4 GE ports. • L2 and L3 switching • Integrated FE and GE Macs • L2/L3/L4 Prioritization16K MAC, 16K IP, 8K IPX, 4K VLAN Tables, IEEE 802.1s • Multiple Spanning Tree IEEE 802.
OS6624/6648 Architecture Packet Memory Address Memory 100MH 32 Bit PCI 66 MHz SMII 125 MHz IXE 2424 MDIO Interface GM11/10 Bit Interface 125MHz External Interfaces to IXE 2424 OmniSwitch Troubleshooting Guide September 2005 page -45
OS6624/6648 Architecture Layer 2 Forwarding • Packets enter the IXE2424 through the SMII & GMII/TBI pins from external PHY devices. First, the MAC associated with the port the packet was received from processes the packet. The MAC checks the CRC to see if the packet is valid and also updates appropriate receive packet port statistics. • In parallel, two things happen next.
OS6624/6648 Architecture Address Learning Address Learning in the IXE2424 is performed primarily in the software. The hardware provides a CAM interface to facilitate fast learning of addresses. On power-up, the switch does not know which addresses are associated with which ports. So, when the switch receives the first packet, the source address lookup fails. This packet is considered source and destination address unresolved and is sent to the CPU for address learning.
OS6624/6648 Architecture Address Look-up Methodology Source and Destination Addresses are searched in parallel and then a sync process occurs to ensure both are completed. The IXE2424 uses a fast method of organizing and searching the address records to meet wire speed performance requirements. Record Entries (see Layer 2 Data Structures section below) contain the addresses. A proprietary binary search algorithm is employed to look for these addresses; no hashing algorithm is used.
OS6624/6648 Architecture 3-Protocol Entry • Used to allow different rules to be applied for different protocols associated with same address. Proto- col Offset Register is used to identify which protocols will be used in the system. Up to 18 Layer 2 protocols are supported. There is a separate protocol entry for each protocol defined in the Protocol Offset Register • Priority level of the packet for queuing • Filter (6 bits), Mirror (5 bits), Priority (5 bits), TOS (6 bits) indices for flow-based rules.
OS6624/6648 Architecture Layer 3 Forwarding Packets Arrived Header 64 Bytes Apply protocol based VLAN on Search the IP Source and Destination addresses in the Yes Does the address exist i d t b ? No Apply address VLAN for Untagged packet Yes L3 No L3- Send the packet to CPU for address Learning Broadcast the packet to all the ports in the VLAN Is Routed P k t? Is the dest and receive port in the Apply Filter, Mirror, Priority, QOS and WRED Yes N Find Outgoing Tag and Port’s 802.
OS6624/6648 Architecture VLANs The IXE2424 supports VLANs based on: • Ports. This is accomplished using Port Net ID Entry described below. • 802.1Q Tags. This tag is included in the packet. • Protocols. This is accomplished using the Protocol to VID Lookup Table described below. • Addresses. This is accomplished by using the AVID field in NetId (L2, IP or IPX), if Address-based VLAN feature is enabled.
OS6624/6648 Architecture Tag Net ID Entry • Contains related information like tagged set and member set. A 4x32 bit entry is present for every possible VLAN (4096 supported). • VLAN Tag Valid. Indicates if this VLAN tag has been configured by the CPU. If not, all packets with this tag are dropped. • Ports on which a packet with this Tag can go out on. • VLAN Statistics Index. IXE2424 can collect statistics on up to 15 VLANs, identified by this index. • IP Statistics Index.
OS6624/6648 Architecture Rules-Based Priority • Several types of priority rules are supported. Each rule is associated with a specific device priority. If a packet satisfies a certain priority rule, it is assigned the device priority corresponding to that rule. • Global Priority Rules enable assignment of specific device priority to all packets from a specific source address (global source priority) or all packets meant for a specific destination address (global destination priority).
CMM Functionality for OS6600 CMM Functionality for OS6600 The overall software architecture of Falcon is retained for Hawk. The user will perceive the system as a virtual chassis; where one element is elected as the primary CMM, another as the secondary CMM and the rest of the elements as NI. The two elements that are elected primary CMM and secondary CMM are also NI. This choice was directed by finding a solution to manage the entire stack with a single IP address.
CMM Functionality for OS6600 The chassis like, or V-Chassis, strategy allows the system to keep the same management interface. Since on Falcon/Eagle, the management uses the notion of slot, this notion of slot is retained for Hawk. Since there is no chassis, we need to provide a means by which a slot number is assigned to an element. The current strategy is to have the user assigning a slot number, via a push button on the front panel, located below the LCD display. The default slot number is one.
CMM Functionality for OS6600 • In idle mode the role of Chassis Supervision is limited to monitoring the temperature, power supply, fan(s), handling of flash synchronization and takeover. The following services are provided when running in idle mode: • Prober needs to monitor the temperature and report a temperature rising over a defined warning thresh- old to HSM.
CMM Functionality for OS6600 The process of multiple CMMs is composed of following steps: • Bootup • Role election • Lowest slot number is elected as Primary • Following number is elected as secondary • Redundancy • Failure of primary • Secondary takeover • Lowest idle number become secondary • Failure of secondary • Lowest idle number become new secondary • Failure of both • Election of a new primary and secondary OmniSwitch Troubleshooting Guide September 2005 page -57
OS6600 IPC Communication OS6600 IPC Communication IPC software interface is unchanged. IPC provides the following services: • NI-NI communication • CMM-NI communication • CMM is the primary or active • CMM-CMM communication • Each element in a stack is addressable from its CMM perspective.
OS6600 BOOT Sequence OS6600 BOOT Sequence • Different from Falcon/Eagle • No NI code to download • Each element is independent from the other • For instance it is possible to have a primary which has not the lowest slot number The following figures illustrate the bootup process: Load Base Stack Manage r IPC Librarie Librari Librari Wait for Stack Manager Topology/role Chassis Supervisio NI Supervisio ’ Stack Manager Wait for stack port Configuration From ESM Driver • Load the Base Code • Load t
OS6600 BOOT Sequence • Get the Role of the Stack-Primary, Secondary or Idle • Start NI supervision and Prober • Start Stack Manager • Get the stack port Configuration from the ESM Driver NI Supervisio ’ IXE 2424 driver Chassis Supervisio Queue Dispatche Chassis supervision Role + Stack Manager Compute stack ESM Driver Stack port configuration • NI Supervision performs the following Tasks: • Load and Start the IXE2424 driver • Start the Queue Dispatcher • Start Stack Manager to compute the stack t
OS6600 BOOT Sequence Chassis Supervisio Daughter Tasks NI powered on CMM applicatio CMM applicatio ESM Driver Start message NI Supervisio ’ NI applicatio NI applicatio NI applicatio NI applicatio • NI supervision and Prober Task. NI Supervision task in turn starts the NI applications.
OS6600 BOOT Sequence page -62 OmniSwitch Troubleshooting Guide September 2005
B Debug Commands This chapter documents the following Command Line Interface (CLI) debug commands. Blue text indicates that the text is hypertext-linked to additional documentation for that command. 802.1Q Debug Commands debug 802.
SNMP Debug Commands debug snmp trace debug snmp reset debug snmp interface debug snmp data Session Debug Commands debug session trace debug session reset debug session interface debug session data Hardware Slot Debug Commands debug slot information Interfaces Debug Commands debug interfaces set backpressure debug interfaces backpressure debug interfaces led debug interfaces mdix debug interfaces phy debug interfaces mac debug interfaces port structure debug interfaces mac stats debug interfaces mac p
Server Load Balancing (SLB) Debug Commands debug slb help debug slb debug slb adminstatus debug slb createcluster debug slb deletecluster debug slb clusteradminstatus debug slb clusterdistribution debug slb clusterpingperiod debug slb clusterpingtimeout debug slb clusterpingretries debug slb clusterstickytime debug slb server debug slb removeserver debug slb dumpcluster debug slb dumpclusters debug slb dumpserver debug slb dumpservers debug slb dumpni debug slb dumpvlan debug slb dumpmisc debug slb discove
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 ipms flow debug hre ip flow debug hre history debug hre error debug hre debug debug hre cmm warn debug hre cmm trace debug hre cmm error debug hre cmm debug debug hre clear ipx debug hre clear ip debug hre cache verbose debug hre cache Health Debug Commands debug health debug health cpu debug health temperature cpu debug health temperature cmm debug health status
VLAN Debug Commands debug vlan vpas debug vlan rule protocol-map debug vlan rule ports debug vlan rule memory debug vlan rule database debug vlan rule communication debug vlan communication debug vlan database debug vlan communication Port Manager (PM) Debug Commands debug pm object debug pm mibs debug pm eventlist debug pm bindings debug pm index AAA Debug Commands debug aaa Port Debug Commands debug port information QoS Debug Commands debug qos IPX Debug Commands debug ipx info debug ipx info r
debug 802.1q Retrieves debugging messages for the tagged port selected. debug 802.1q {slot/port | aggregate_id} Syntax Definitions slot The slot number to configure 802.1Q tagging. port The port number to configure 802.1Q tagging. aggregate_id The aggregate link number to configure 802.1Q tagging. Defaults N/A Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines Retrieves debugging messages for the tagged port selected. Examples -> debug 802.
output definitions Aggregate/Slot Status Whether the slot or aggregate link is actively running. Port Status Whether the port is actively running. General Info Provides general information on the modules in the chassis, including module type, number of ports, and ASIC. Hardware Info Lists the various debug messages for the selected slot and port. Release History Release 5.1; command was introduced.
ip dvmrp debug-level Defines the level of debugging for 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 messages that correspond to a lower value. For example, a debug level of 2 will display all messages for level 1 and level 2. As a rule of thumb, higher levels will display more detailed messages; lower levels will display more basic messages.
ip dvmrp debug-type Enables or disables DVMRP debugging for a specified message type, or for all message types. Note. Debugging for a specified message type will only be enabled if its debug level is a value greater than zero (i.e., 1–255). For information on specifying the debug level, refer to the ip dvmrp debug-level command. ip dvmrp debug-type message_type no ip dvmrp debug-type message_type Syntax Definitions message_type Enables or disables DVMRP debugging for the specified item.
Defaults parameter default message_type error Platforms Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines • Use the no form of the command to disable debugging for the specified item. • Reminder: Debugging for a specified message type will only be enabled if its debug level is a value greater than zero (i.e., 1–255). For information on specifying the debug level, refer to the ip dvmrp debug-level command. • The syntax all can be used to easily turn debugging for all message types on or off (e.g.
show ip dvmrp debug Displays the current level of debugging for DVMRP protocol on the switch, as well as the current DVMRP debugging status for all messages types. show ip dvmrp debug Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines • The administrative debugging status for message types displayed in the table are determined by the ip dvmrp debug-type command. • To configure debug levels, refer to the ip dvmrp debug-level command.
output definitions (continued) Grafts The current debugging status for DVMRP Graft processing. Options include on or off. IGMP The current debugging status for DVMRP Internet Group Management Protocol (IGMP) packet processing. Options include on or off. IPMRM The current debugging status for DVMRP IP Multicast Routing Manager (IPMRM) interaction. Options include on or off. Init The current debugging status for DVMRP Initialization. Options include on or off.
debug ip packet Enables/disables/configures the IP packet debug feature. This command is generally used only when working with a field engineer to debug a problem on the switch.
protocol Specifies a protocol type to debug. Specify tcp to debug TCP packets; specify udp to debug UPD packets; specify icmp to debug ICMP packets; specify igmp to debug IGMP packets; specify num to numerically specify a protocol (e.g., 89); specify all to debug all protocol types. show-broadcast Specifies whether or not to display broadcast packets. Specify on to display broadcast packets on the screen or in the log; specify off if you do not want to display broadcast packets.
Related Commands debug ip level OmniSwitch Troubleshooting Guide Configures IP debug level. This command allows you to set the level (amount) of information displayed.
debug ip level Configures the IP debug level. This command allows you to set the level (amount) of information displayed. The lower the level, the more significant the event. For example, a level of 1 will display only the most critical problems. A level of 99 would display all of the available information for the specified debug type. It is best to use the default level of 1 unless instructed to increase the level by a field engineer.
debug ip packet default Returns IP packet debug options to default values. debug ip packet default Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines See “Defaults” on page B-14 for default values. Examples -> debug ip packet default Release History Release 5.1; command was introduced. Related Commands debug ip packet OmniSwitch Troubleshooting Guide Configures IP packet debug.
debug ip packet Displays IP debug configuration parameters. This command is generally used only when working with a field engineer to debug a problem on the switch. debug ip packet Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines This command is used to display IP debug configuration parameters. To start IP debugging you must enter the start keyword.
Release History Release 5.1; command was introduced. Related Commands debug ip packet OmniSwitch Troubleshooting Guide Configures IP packet debug.
debug ip mroute debug-level Configures the Mutlicast Routing debug level. debug ip mroute debug-level level Syntax Definitions level Specifies the Mutlicast Routing debug level (0–255). Defaults parameter default level Platforms Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines Higher debug-levels will include all messages that correspond to a lower value. For example, a debug level of 2 will display all messages for level 1 and level 2.
ip mroute debug-type Displays the current multicast routing debug levels and types. ip mroute debug-type [tm | protos {on | off} | misc | mip {on | off} | ipms {on | off} | init | fib {on | off} | error {on | off} | all | aging {on | off}] no ip mroute debug-type [tm | protos {on | off} | misc | mip {on | off} | ipms {on | off} | init | fib {on | off} | error {on | off} | all | aging {on | off}] Syntax Definitions debug level The current debug level value.
ip ospf debug-level Configures OSPF debugging level. The level refers to the granularity of the information provided. Generally, the higher the number, the more specific the information. ip ospf debug-level level Syntax Definitions level The debugging level. The valid range 0–255. Defaults parameter default level 0 Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines This command allows you to select the granularity at which you wish to view debugging information.
ip ospf debug-type Configures the type of OSPF functionality to debug.
auth Administratively enables/disables debugging messages for OSPF’s authentication process. area Administratively enables/disables debugging messages for OSPF’s area events. intf Administratively enables/disables debugging messages for OSPF’s interface operations. mip Administratively enables/disables debugging messages for MIP processing of OSPF specific commands. info Administratively enables/disables debugging messages for purpose to provide OSPF information.
Related Commands ip ospf debug-level Configures OSPF debugging level. show ip ospf debug Displays current OSPF debug level and types.
show ip ospf debug Displays current OSPF debug level and types. show ip ospf debug Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines • This command is used to display the debugging information currently enabled for the OSPF router. • See the related commands sections below to modify the list.
output definitions Debug Level The granularity of the debug messages. This number will be 10, 50, or 99, where the lower number is least specific. error The error debug messages status. Error messages provide information of program faults. warning The warning debug messages status. Debugging messages show router operation calls. state The state debug messages status. State messages show the router state in relation to its neighbors. recv The received OSPF packet debug messages status.
MIB Objects alaOspfDebugLevel alaOspfDebugError alaOspfDebugWarning alaOspfDebugState alaOspfDebugRecv alaOspfDebugSend alaOspfDebugFlood alaOspfDebugSPF alaOspfDebugLsdb alaOspfDebugRdb alaOspfDebugAge alaOspfDebugVlink alaOspfDebugRedist alaOspfDebugSummary alaOspfDebugDbexch alaOspfDebugHello alaOspfDebugAuth alaOspfDebugArea alaOspfDebugIntf alaOspfDebugMip alaOspfDebugInfo alaOspfDebugSetup alaOspfDebugTime alaOspfDebugTm alaOspfDebugAll page -28 OmniSwitch Troubleshooting Guide September 2005
ip pimsm debug-level Defines the level of PIM-SM debug messages that are generated. ip pimsm debug-level level Syntax Definitions level Specifies the PIM-SM debug level (0–255). Higher debug-levels will include all messages that correspond to a lower value. For example, a debug-level of 1 will display only those messages that are defined with a level of 1; however, a debug level of 2 will display all messages of level 1 and level 2, etc.
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-type message_list Syntax Definitions message_list Specifies the type(s) of PIM-SM messages to be debugged. Select supported PIM-SM message types from the list below. You may enter multiple message types in any order. For example, ip pimsm debugtype time flash init. supported message types descriptions all Enables or disables PIM-SM debugging for all items listed below.
Platforms Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines • The message-types specified in the command line will only be displayed if the debug level has been set to a number greater than zero (i.e., 1–255). For information on specifying the debug level, refer to the ip pimsm debug-level command on page B-29. • The syntax all can be used to easily turn on/off all message types (e.g., ip pimsm debug-type all or no ip pimsm debug-type all).
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 Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines The debug types displayed in the table are determined by the ip pimsm debug-type command on page B-30. To configure debug levels, refer to the ip pimsm debug-level command on page B-29.
output definitions (continued) crp The current state of messages related to Candidate Rendezvous Point (C-RP). Options include on or off. error The current state of messages related to all error handling. Options include on or off. hello The current state of messages related to hello messages. Options include on or off. igmp The current state of messages related to Internet Group Management Protocol (IGMP) packet processing. Options include on or off.
ip rip debug-type Configures the type of RIP messages to debug. The debug feature on the switch is generally used only under the direction of a field engineer. Use this command to configure the type of RIP debug warnings (e.g., errors, warning) that will be logged.
Release History Release 5.1; command was introduced. Related Commands ip rip debug-level Configures RIP debugging level. show ip rip debug Displays the current RIP debug levels and types.
ip rip debug-level Configures RIP debug level. You can set the level of information displayed using the ip rip debug level command. The lower the level, the more significant the event. For example, a level of 1 will display only the most critical problems. A level of 99 would display all of the available information for the specified debug type. It is best to use the default level of 1 unless instructed to increase the level by a field engineer.
show ip rip debug Displays the current RIP debug levels and types. show ip rip debug Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines N/A Examples -> show ip rip debug Debug Level Types/Sections error warning recv send rdb age config redist info setup time = 3 = = = = = = = = = = = on on on on on on on on on on on output definitions Debug Level Debug level. The valid range 0–255. The default level is 0.
Related Commands ip rip debug-level Configures RIP debugging level. ip rip debug-type Configures the type of RIP messages to debug.
debug slot information Displays all the information about a specific slot. It includes all the details about the ports, statistics, MDIX, IPC pools, and other phy-related information. debug slot information slot Syntax Definitions slot The slot number of the Network Interface (NI) module.
InPauseFrames = 0, OutPauseFrames = 0 ######################################### debug interfaces 1 Led ######################################### Slot/Port Activity LNK -----------+----------+-------1/1 normal OFF 1/2 normal OFF 1/3 normal OFF 1/4 normal OFF 1/5 normal OFF 1/6 normal OFF 1/7 normal OFF 1/8 normal OFF 1/9 normal OFF 1/10 normal OFF 1/11 normal OFF 1/12 normal OFF 1/13 normal OFF 1/14 normal OFF 1/15 normal OFF 1/16 normal ON 1/17 normal OFF 1/18 normal ON 1/19 normal OFF 1/20 normal ON 1/
######################################### debug ipc pools slot 1 ######################################### IPC Pools slot 1, slice 0: UrgentPool: Full size is 256, remaining: 256 In socket queues: 0 Not queued: 0: In DMA queues: 0 ControlPool: Full size is 1024, remaining: 1023 In socket queues: 0 Not queued: 1: In DMA queues: 0 NormalPool: Full size is 256, remaining: 255 In socket queues: 0 Not queued: 1: In DMA queues: 0 JumboPool: Full size is 64, remaining: 64 In socket queues: 0 Not queued: 0: In DMA
slot/port( 1/5 ): Phy ID : 1e 0 : 3000 7809 8 : 0 0 10 : 184 100 18 : 0 0 slot/port( 1/6 ): Phy ID : 1e 13 0 8000 40 78f7 0 54 100 de1 0 de2 c429 0 0 0 0 4 0 0 0 2801 0 202 210 0 : 3000 7809 8 : 0 0 10 : 184 100 18 : 0 0 slot/port( 1/7 ): Phy ID : 1e 13 0 8000 40 78f7 0 54 100 de1 0 de2 c42b 0 0 0 0 4 0 0 0 2801 0 202 210 0 : 3000 7809 8 : 0 0 10 : 184 100 18 : 0 0 slot/port( 1/8 ): Phy ID : 1e 13 0 8000 40 78f7 0 54 e100 de1 0 de2 c42b 0 0 0 0 4 0 0 0 2801 0 202 210 0 : 3000 7809 8 : 0
0 : 3000 7809 8 : 0 0 10 : 184 100 18 : 0 0 slot/port( 1/14): Phy ID : 1e 13 0 8000 40 78f7 0 54 100 de1 0 de2 c423 0 0 0 0 4 0 0 0 2801 0 202 210 0 : 3000 7809 8 : 0 0 10 : 184 100 18 : 0 0 slot/port( 1/15): Phy ID : 1e 13 0 8000 40 78f7 0 54 100 de1 0 de2 c423 0 0 0 0 4 0 0 0 2801 0 202 210 0 : 3000 7809 8 : 0 0 10 : 184 100 18 : 0 0 slot/port( 1/16): Phy ID : 1e 13 0 8000 40 78f7 0 54 e100 de1 0 de2 c423 0 0 0 0 4 0 0 0 2801 0 202 210 0 : 3000 782d 8 : 0 0 10 : 184 7780 18 : 2 0 slot
18 : 0 0 slot/port( 1/22): Phy ID : 1e 40 100 c419 0 0 210 0 : 3000 7809 8 : 0 0 10 : 184 100 18 : 0 0 slot/port( 1/23): Phy ID : 1e 13 0 8000 40 78f7 0 54 100 de1 0 de2 c41d 0 0 0 0 4 0 0 0 2801 0 202 210 0 : 3000 7809 8 : 0 0 10 : 184 100 18 : 0 0 slot/port( 1/24): Phy ID : 1e 13 0 8000 40 78f7 0 54 100 de1 0 de2 c41b 0 0 0 0 4 0 0 0 2801 0 202 210 0 : 3000 7809 13 78f7 de1 0 8 : 0 0 0 0 0 0 10 : 184 100 8000 d4 de2 31 18 : 0 0 1c8 100 c41d 0 #########################################
runt = flowstate = 0 runt sz = 0 flowmode = 0 0 slot/port slice index Mac prevLink admin d_bw mtu ifg trap pause SA long runt flowstate = = = = = = = = = = = = = = ( 1/3 ) 0 mac_chip = 0 0x 3eb gport = 0x 0x00:d0:95:6a:5f:2a 0 cur_Link = 2 1 auto = 1 3 d_duplex = 3 1553 flood = 12 backoff = 0 0x 0:d0:95:6a:5f:2a 1 long sz = 1553 0 runt sz = 0 0 flowmode = 0 slot/port slice index Mac prevLink admin d_bw mtu ifg trap pause SA long runt flowstate = = = = = = = = = = = = = = ( 1/4 ) 0 mac_chip = 0 0x 3e
long = runt = flowstate = 1 long sz = 0 runt sz = 0 flowmode = 1553 0 0 slot/port slice index Mac prevLink admin d_bw mtu ifg trap pause SA long runt flowstate = = = = = = = = = = = = = = ( 1/7 ) 0 mac_chip = 0 0x 3ef gport = 0x 0x00:d0:95:6a:5f:2e 0 cur_Link = 2 1 auto = 1 3 d_duplex = 3 1553 flood = 12 backoff = 0 0x 0:d0:95:6a:5f:2e 1 long sz = 1553 0 runt sz = 0 0 flowmode = 0 slot/port slice index Mac prevLink admin d_bw mtu ifg trap pause SA long runt flowstate = = = = = = = = = = = = = = ( 1/
pause SA long runt flowstate = 0x 0:d0:95:6a:5f:31 = 1 long sz = 1553 = 0 runt sz = 0 = 0 flowmode = 0 slot/port slice index Mac prevLink admin d_bw mtu ifg trap pause SA long runt flowstate = = = = = = = = = = = = = = ( 1/11) 0 mac_chip = 0 0x 3f3 gport = 0x 0x00:d0:95:6a:5f:32 0 cur_Link = 2 1 auto = 1 3 d_duplex = 3 1553 flood = 12 backoff = 0 0x 0:d0:95:6a:5f:32 1 long sz = 1553 0 runt sz = 0 0 flowmode = 0 slot/port slice index Mac prevLink admin d_bw mtu ifg trap pause SA long runt flowstate = =
trap pause SA long runt flowstate = 0 = 0x 0:d0:95:6a:5f:35 = 1 long sz = 1553 = 0 runt sz = 0 = 0 flowmode = 0 slot/port slice index Mac prevLink admin d_bw mtu ifg trap pause SA long runt flowstate = = = = = = = = = = = = = = ( 1/15) 0 mac_chip = 1 0x 3f7 gport = 0x 0x00:d0:95:6a:5f:36 0 cur_Link = 2 1 auto = 1 3 d_duplex = 3 1553 flood = 12 backoff = 0 0x 0:d0:95:6a:5f:36 1 long sz = 1553 0 runt sz = 0 0 flowmode = 0 slot/port slice index Mac prevLink admin d_bw mtu ifg trap pause SA long runt flows
ifg trap pause SA long runt flowstate = 12 backoff = = 0 = 0x 0:d0:95:6a:5f:39 = 1 long sz = 1553 = 0 runt sz = 0 = 0 flowmode = 0 slot/port slice index Mac prevLink admin d_bw mtu ifg trap pause SA long runt flowstate = = = = = = = = = = = = = = ( 1/19) 0 mac_chip = 1 0x 3fb gport = 0x 0x00:d0:95:6a:5f:3a 0 cur_Link = 2 1 auto = 1 3 d_duplex = 3 1553 flood = 12 backoff = 0 0x 0:d0:95:6a:5f:3a 1 long sz = 1553 0 runt sz = 0 0 flowmode = 0 slot/port slice index Mac prevLink admin d_bw mtu ifg trap pause
mtu ifg trap pause SA long runt flowstate = 1553 flood = = 12 backoff = = 0 = 0x 0:d0:95:6a:5f:3d = 1 long sz = 1553 = 0 runt sz = 0 = 0 flowmode = 0 slot/port slice index Mac prevLink admin d_bw mtu ifg trap pause SA long runt flowstate = = = = = = = = = = = = = = ( 1/23) 0 mac_chip = 1 0x 3ff gport = 0x 0x00:d0:95:6a:5f:3e 0 cur_Link = 2 1 auto = 1 3 d_duplex = 3 1553 flood = 12 backoff = 0 0x 0:d0:95:6a:5f:3e 1 long sz = 1553 0 runt sz = 0 0 flowmode = 0 slot/port slice index Mac prevLink admin d_bw
debug interfaces set backpressure Enables and disables 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 enable or disable fabric back pressure. The valid range is 1–8 on an OmniSwitch 7700, 1–16 on an OmniSwitch 7800, and 1–16 on an OmniSwitch 8800. enable Enables fabric backpressure. disable Disables fabric backpressure.
debug interfaces backpressure Displays if fabric back pressure is enabled or disabled on a Network Interface (NI) or an entire chassis. debug interfaces [slot] backpressure Syntax Definitions slot The slot number to display the fabric back pressure state. The valid range is 1–8 on an OmniSwitch 7700 and 1–16 on an OmniSwitch 7800, and 1–16 on an OmniSwitch 8800.
Related Commands debug interfaces set backpressure Enables and disables fabric back pressure on an NI or an entire chassis.
debug interfaces led Displays LED information. debug interfaces slot led Syntax Definitions slot The slot number of the Network Interface (NI) module.
Release History Release 5.1; command was introduced.
debug interfaces mdix Displays Media Dependent Interface with Crossover (MDIX) information. debug interfaces slot mdix Syntax Definitions slot The slot number of the Network Interface (NI) module.
Related Commands N/A OmniSwitch Troubleshooting Guide September 2005 page -57
debug interfaces phy Displays PHY information. debug interfaces slot phy Syntax Definitions slot The slot number of the Network Interface (NI) module.
0 : 3000 7809 8 : 0 0 10 : 184 100 18 : 0 0 slot/port( 1/6 ): Phy ID : 1e 13 0 8000 40 78f7 0 0 e100 de1 0 de2 c429 0 0 0 0 4 0 0 0 2801 0 202 210 0 : 3000 7809 8 : 0 0 10 : 184 100 18 : 0 0 slot/port( 1/7 ): Phy ID : 1e 13 0 8000 40 78f7 0 0 100 de1 0 de2 c42b 0 0 0 0 4 0 0 0 2801 0 202 210 0 : 3000 7809 8 : 0 0 10 : 184 100 18 : 0 0 slot/port( 1/8 ): Phy ID : 1e 13 0 8000 40 78f7 0 0 100 de1 0 de2 c42b 0 0 0 0 4 0 0 0 2801 0 202 210 0 : 3000 7809 8 : 0 0 10 : 184 100 18 : 0 0 slot/por
10 : 184 100 18 : 0 0 slot/port( 1/14): Phy ID : 1e 8000 40 0 100 de2 c423 0 0 0 0 202 210 0 : 3000 7809 8 : 0 0 10 : 184 100 18 : 0 0 slot/port( 1/15): Phy ID : 1e 13 0 8000 40 78f7 0 0 100 de1 0 de2 c423 0 0 0 0 4 0 0 0 2801 0 202 210 0 : 3000 7809 8 : 0 0 10 : 184 100 18 : 0 0 slot/port( 1/16): Phy ID : 1e 13 0 8000 40 78f7 0 0 100 de1 0 de2 c423 0 0 0 0 4 0 0 0 2801 0 202 210 0 : 3000 782d 8 : 0 0 10 : 184 7780 18 : 2 0 slot/port( 1/17): Phy ID : 1e 13 0 8000 88 78f7 0 0 100 de1
Phy ID : 1e 0 : 3000 7809 8 : 0 0 10 : 184 100 18 : 0 0 slot/port( 1/23): Phy ID : 1e 13 0 8000 40 78f7 0 0 100 de1 0 de2 c41d 0 0 0 0 4 0 0 0 2801 0 202 210 0 : 3000 7809 8 : 0 0 10 : 184 100 18 : 0 0 slot/port( 1/24): Phy ID : 1e 13 0 8000 40 78f7 0 0 100 de1 0 de2 c41b 0 0 0 0 4 0 0 0 2801 0 202 210 13 0 8000 40 78f7 0 0 100 de1 0 de2 c41d 0 0 0 0 4 0 0 0 2801 0 202 210 0 8 10 18 : : : : 3000 0 184 0 7809 0 100 0 Release History Release 5.1; command was introduced.
debug interfaces mac Displays MAC information. debug interfaces slot mac Syntax Definitions slot The slot number of the Network Interface (NI) module. Defaults N/A Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines N/A Examples -> debug interfaces 1 mac ERROR: Type <0> for Debug_mac is unknown Release History Release 5.1; command was introduced.
debug interfaces port structure Displays port structure information. debug interfaces slot port structure Syntax Definitions slot The slot number of the Network Interface (NI) module.
slot/port slice index Mac prevLink admin d_bw mtu ifg trap pause SA long runt flowstate = = = = = = = = = = = = = = ( 1/3 ) 0 mac_chip = 0 0x 3eb gport = 0x 0x00:d0:95:6a:5f:2a 0 cur_Link = 2 1 auto = 1 3 d_duplex = 3 1553 flood = 12 backoff = 0 0x 0:d0:95:6a:5f:2a 1 long sz = 1553 0 runt sz = 0 0 flowmode = 0 slot/port slice index Mac prevLink admin d_bw mtu ifg trap pause SA long runt flowstate = = = = = = = = = = = = = = ( 1/4 ) 0 mac_chip = 0 0x 3ec gport = 0x 0x00:d0:95:6a:5f:2b 0 cur_Link = 2 1 a
slot/port slice index Mac prevLink admin d_bw mtu ifg trap pause SA long runt flowstate = = = = = = = = = = = = = = ( 1/7 ) 0 mac_chip = 0 0x 3ef gport = 0x 0x00:d0:95:6a:5f:2e 0 cur_Link = 2 1 auto = 1 3 d_duplex = 3 1553 flood = 12 backoff = 0 0x 0:d0:95:6a:5f:2e 1 long sz = 1553 0 runt sz = 0 0 flowmode = 0 slot/port slice index Mac prevLink admin d_bw mtu ifg trap pause SA long runt flowstate = = = = = = = = = = = = = = ( 1/8 ) 0 mac_chip = 0 0x 3f0 gport = 0x 0x00:d0:95:6a:5f:2f 0 cur_Link = 2 1 a
flowstate = 0 flowmode = 0 slot/port slice index Mac prevLink admin d_bw mtu ifg trap pause SA long runt flowstate = = = = = = = = = = = = = = ( 1/11) 0 mac_chip = 0 0x 3f3 gport = 0x 0x00:d0:95:6a:5f:32 0 cur_Link = 2 1 auto = 1 3 d_duplex = 3 1553 flood = 12 backoff = 0 0x 0:d0:95:6a:5f:32 1 long sz = 1553 0 runt sz = 0 0 flowmode = 0 slot/port slice index Mac prevLink admin d_bw mtu ifg trap pause SA long runt flowstate = = = = = = = = = = = = = = ( 1/12) 0 mac_chip = 0 0x 3f4 gport = 0x 0x00:d0
runt = flowstate = 0 runt sz = 0 flowmode = 0 0 slot/port slice index Mac prevLink admin d_bw mtu ifg trap pause SA long runt flowstate = = = = = = = = = = = = = = ( 1/15) 0 mac_chip = 1 0x 3f7 gport = 0x 0x00:d0:95:6a:5f:36 0 cur_Link = 2 1 auto = 1 3 d_duplex = 3 1553 flood = 12 backoff = 0 0x 0:d0:95:6a:5f:36 1 long sz = 1553 0 runt sz = 0 0 flowmode = 0 slot/port slice index Mac prevLink admin d_bw mtu ifg trap pause SA long runt flowstate = = = = = = = = = = = = = = ( 1/16) 0 mac_chip = 1 0x 3f
long = runt = flowstate = 1 long sz = 0 runt sz = 0 flowmode = 1553 0 0 slot/port slice index Mac prevLink admin d_bw mtu ifg trap pause SA long runt flowstate = = = = = = = = = = = = = = ( 1/19) 0 mac_chip = 1 0x 3fb gport = 0x 0x00:d0:95:6a:5f:3a 0 cur_Link = 2 1 auto = 1 3 d_duplex = 3 1553 flood = 12 backoff = 0 0x 0:d0:95:6a:5f:3a 1 long sz = 1553 0 runt sz = 0 0 flowmode = 0 slot/port slice index Mac prevLink admin d_bw mtu ifg trap pause SA long runt flowstate = = = = = = = = = = = = = = ( 1/
pause SA long runt flowstate = 0x 0:d0:95:6a:5f:3d = 1 long sz = 1553 = 0 runt sz = 0 = 0 flowmode = 0 slot/port slice index Mac prevLink admin d_bw mtu ifg trap pause SA long runt flowstate = = = = = = = = = = = = = = ( 1/23) 0 mac_chip = 1 0x 3ff gport = 0x 0x00:d0:95:6a:5f:3e 0 cur_Link = 2 1 auto = 1 3 d_duplex = 3 1553 flood = 12 backoff = 0 0x 0:d0:95:6a:5f:3e 1 long sz = 1553 0 runt sz = 0 0 flowmode = 0 slot/port slice index Mac prevLink admin d_bw mtu ifg trap pause SA long runt flowstate = =
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 Network Interface (NI) module. port The port number of the interface. Defaults N/A Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines N/A Examples -> debug interfaces 1 mac stats ERROR: Type <3> for Debug_mac is unknown Release History Release 5.1; command was introduced.
debug interfaces mac port Displays MAC level register information. debug interfaces {slot | slot/port} mac port Syntax Definitions slot The slot number of the Network Interface (NI) module. port The port number of the interface.
debug interfaces mac nonport Displays MAC level information for nonport from the register values. debug interfaces {slot | slot/port} mac nonport Syntax Definitions slot The slot number of the Network Interface (NI) module. port The port number of the interface.
debug interfaces switching Displays the register value specified in hexadecimal for all the slots or displays a specified number of register values starting from the hexadecimal address for all the slots. debug interfaces [slot | slot/port] switching 0xhex [num] Syntax Definitions slot The slot number of the Network Interface (NI) module. port The port number of the interface. 0Xhex The register value in hexadecimal (e.g., 0xffff). num The number of register values to be displayed.
debug ipc pools slot Displays IPC pools on a particular slot. debug ipc pools slot slot Syntax Definitions slot The slot number of the Network Interface (NI) module.
Related Commands debug ipc pools cmm Displays IPC Pools on Chassis Management Modules (CMMs). debug ipc bbus Displays IPC pools for the Burst Bus with transmit and received count, Direct Memory Access errors, and parity errors. debug ipc active sockets Displays all the active sockets on Chassis Management Modules (CMMs). debug ipc active sockets slot Displays all the active sockets on a particular slot.
debug ipc pools cmm Displays IPC Pools on Chassis Management Modules (CMMs).
Related Commands debug ipc pools slot Displays IPC pools on a particular slot. debug ipc bbus Displays IPC pools for the Burst Bus with transmit and received count, Direct Memory Access errors, and parity errors. debug ipc active sockets Displays all the active sockets on Chassis Management Modules (CMMs). debug ipc active sockets slot Displays all the active sockets on a particular slot.
debug ipc bbus Displays IPC pools for the Burst Bus with transmit and received count, Direct Memory Access errors, and parity errors.
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 introduced. Related Commands debug ipc pools cmm Displays IPC Pools on Chassis Management Modules (CMMs). debug ipc pools slot Displays IPC pools on a particular slot. debug ipc active sockets Displays all the active sockets on Chassis Management Modules (CMMs).
debug ipc active sockets Displays all the active sockets on Chassis Management Modules (CMMs).
Release History Release 5.1; command was introduced. Related Commands debug ipc pools cmm Displays IPC Pools on Chassis Management Modules (CMMs). debug ipc bbus Displays IPC pools for the Burst Bus with transmit and received count, Direct Memory Access errors, and parity errors. debug ipc pools slot Displays IPC pools on a particular slot. debug ipc active sockets slot Displays all the active sockets on a particular slot.
debug ipc active sockets slot Displays all the active sockets on a particular slot. debug ipc active sockets slot slot Syntax Definitions slot The slot number of the Network Interface (NI) module.
2A6578|2| Task 2A6640|3| Task 2A6708|3| Task 2A67D0|3| Task 2A6898|3| Task 2A6960|3| Task 208000B| 0| NI A08000B| 5000B| NI 908000B|100B000B| NI 308000B| 309000B| NI 708000B| 6000B| NI F08000B| 20A000B| NI Release History Release 5.1; command was introduced. Related Commands debug ipc pools cmm Displays IPC Pools on Chassis Management Modules (CMMs). debug ipc bbus Displays IPC pools for the Burst Bus with transmit and received count, Direct Memory Access errors, and parity errors.
debug fabric threshold Displays the threshold number for each fabric ASIC. In addition, it also displays the Unicast pay generated internally using Pay algorithm and Coupons generated. debug fabric threshold Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines This command is not valid for OS-6600 series of switches.
0 27 330 f0 90 60 2d0 0 28 330 f0 90 60 2d0 0 29 660 28a 180 c0 5a0 0 30 330 f0 90 60 2d0 0 31 20 20 20 20 20 0 32 330 f0 90 60 2d0 0 33 330 f0 90 60 2d0 0 34 330 f0 90 60 2d0 0 35 330 f0 90 60 2d0 0 36 330 f0 90 60 2d0 0 37 330 f0 90 60 2d0 0 38 330 f0 90 60 2d0 0 39 330 f0 90 60 2d0 0 40 330 f0 90 60 2d0 0 41 330 f0 90 60 2d0 0 42 330 f0 90 60 2d0 0 43 330 f0 90 60 2d0 0 44 330 f0 90 60 2d0 0 45 660 28a 180 c0 5a0 0 46 330 f0 90 60 2d0 0 47 330 f0 90 60 2d0 0 48 330 f0 90 60 2d0 0 49 330 f0 90 60 2d0 0 50
1 21 330 f0 90 60 2d0 1 22 330 f0 90 60 2d0 1 23 330 f0 90 60 2d0 1 24 330 f0 90 60 2d0 1 25 330 f0 90 60 2d0 1 26 330 f0 90 60 2d0 1 27 330 f0 90 60 2d0 1 28 330 f0 90 60 2d0 1 29 660 28a 180 c0 5a0 1 30 330 f0 90 60 2d0 1 31 20 20 20 20 20 1 32 330 f0 90 60 2d0 1 33 330 f0 90 60 2d0 1 34 330 f0 90 60 2d0 1 35 330 f0 90 60 2d0 1 36 330 f0 90 60 2d0 1 37 330 f0 90 60 2d0 1 38 330 f0 90 60 2d0 1 39 330 f0 90 60 2d0 1 40 330 f0 90 60 2d0 1 41 330 f0 90 60 2d0 1 42 330 f0 90 60 2d0 1 43 330 f0 90 60 2d0 1 44 3
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 f0 90 60 2d0 2 22 330 f0 90 60 2d0 2 23 330 f0 90 60 2d0 2 24 330 f0 90 60 2d0 2 25 330 f0 90 60 2d0 2 26 330 f0 90 60 2d0 2 27 330 f0 90 60 2d0 2 28 330 f0 90 60 2d0 2 29 660 28a 180 c0 5a0 2 30 330 f0 90 60 2d0 2 31 20 20 20 20 20 2 32 330 f0 90 60 2d0 2 33 330 f0 90 60 2d0 2 34 330 f0 90 60 2d0 2 35 330 f0 90 60 2d0 2 36 330 f0 90 60 2d0 2 37 330 f0 90 60 2d0 2 38 3
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 f0 90 60 2d0 3 16 330 f0 90 60 2d0 3 17 330 f0 90 60 2d0 3 18 330 f0 90 60 2d0 3 19 330 f0 90 60 2d0 3 20 330 f0 90 60 2d0 3 21 330 f0 90 60 2d0 3 22 330 f0 90 60 2d0 3 23 330 f0 90 60 2d0 3 24 330 f0 90 60 2d0 3 25 330 f0 90 60 2d0 3 26 330 f0 90 60 2d0 3 27 330 f0 90 60 2d0 3 28 330 f0 90 60 2d0 3 29 660 28a 180 c0 5a0 3 30 330 f0 90 60 2d0 3 31 20 20 20 20 20 3 32
4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 330 330 330 330 330 330 330 330 330 330 660 330 330 330 330 330 330 330 330 330 330 330 330 330 330 330 660 330 20 330 330 330 330 330 330 330 330 330 330 330 330 330 f0 f0 f0 f0 f0 f0 f0 f0 f0 f0 28a f0 f0 f0 f0 f0 f0 f0 f0 f0 f0 f0 f0 f0 f0 f0 28a f0 20 f0 f0 f0 f0 f0 f0 f0 f0 f0 f0 f0 f0 f0 90 90 90 9
debug fabric status Displays the overall status of all the fabric ASICs. It displays the chip version and netlist version being used. In addition, it also displays if any internal or external interrupts were received. debug fabric status Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines This command is not valid for OS-6600 series of switches.
debug fabric stats Displays the fabric ASIC statistics. debug fabric stats Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines • This command is not valid for OS-6600 series of switches. • “Unicast In” should be equal to the “Unicast Out”. • For Multicast, multicast in will be different from multicast out. Iteration of this command should show the queues moving.
Release History Release 5.1; command was introduced. Related Commands debug fabric status page -92 Displays the overall status of all the fabric ASICs.
debug fabric output Displays the fabric ASIC port number and the frame count. debug fabric output Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines • This command is not valid for OS-6600 series of switches. • Each fabric ASIC has 16 ports in case of 7800 and 8 port in case of 7700. • The frame count on the similar ports for all the fabric ASICs should be same.
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 59200 2 2 55029 2 3 55110 2 4 45451 2 5 47993 2 6 31452 2 7 45447 2 8 47328 2 9 47327 2 10 9006 2 11 59975 2 12 59988 2 13 45449 2 14 48030 2 15 62795 --------- ------ ------3 0 55509 3 1 59202 3 2 55029 3 3 55110 3 4 45451 3 5 47993 3 6 31452 3 7 45447 3 8 47328 3 9 47327 3 10 9006 3 11 59975 3 12 59988 3 13 45449 3 14 48030 3 15 62795 --------- ------ ------4 0 5550
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 47327 5 10 9008 5 11 59975 5 12 59988 5 13 45449 5 14 48031 5 15 62795 --------- ------ ------6 0 55509 6 1 59202 6 2 55029 6 3 55110 6 4 45451 6 5 47993 6 6 31452 6 7 45450 6 8 47328 6 9 47327 6 10 9008 6 11 59975 6 12 59988 6 13 45449 6 14 48032 6 15 62795 --------- ------ ------7 0 55509 7 1 59202 7 2 55029 7 3 55110 7 4 45452 7 5 47993 7 6 31452 7 7 45450 7 8 47328 7
Related Commands debug fabric status Displays the overall status of all the fabric ASICs. debug fabric stats Displays the fabric ASIC statistics.
debug fabric mcvectors Displays the Fabric ASIC port number and the frame count for multicast packets. debug fabric mcvectors Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines • This command is not valid for OS-6600 series of switches. • Each fabric ASIC has 16 ports in case of 7800 and 8 port in case of 7700. • The frame count on the similar ports for all the fabric ASICs should be same.
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 511 5 0 611 6 0 711 4 --------- ------ --------1 1 de6d 1 50 404 1 51 404 1 52 404 1 53 404 1 54 404 1 55 404 1 56 404 1 57 404 1 58 404 1 59 404 1 60 404 1 61 404 1 62 404 1 100 5 1 102 4 1 103 4 1 104 44 1 105 44 1 106 4 1 107 4 1 108 24 1 109 24 1 110 c 1 111 c 1 112 4004 1 114 1006 1 115 4 1 116 4 1 117 804 1 130 804 1 140 7 1 141 5 1 150 586d 1 211 4004 1 212 1004
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 404 2 61 404 2 62 404 2 100 5 2 102 4 2 103 4 2 104 44 2 105 44 2 106 4 2 107 4 2 108 24 2 109 24 2 110 c 2 111 c 2 112 4004 2 114 1006 2 115 4 2 116 4 2 117 804 2 130 804 2 140 7 2 141 5 2 150 586d 2 211 4004 2 212 1004 2 311 4 2 411 4 2 511 5 2 611 6 2 711 4 --------- ------ --------3 1 de6d 3 50 404 3 51 404 3 52 404 3 53 404 3 54 404 3 55 404 3 56 404 3 57 404 3 58 404
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 3 140 7 3 141 5 3 150 586d 3 211 4004 3 212 1004 3 311 4 3 411 4 3 511 5 3 611 6 3 711 4 --------- ------ --------4 1 de6d 4 50 404 4 51 404 4 52 404 4 53 404 4 54 404 4 55 404 4 56 404 4 57 404 4 58 404 4 59 404 4 60 404 4 61 404 4 62 404 4 100 5 4 102 4 4 103 4 4 104 44 4 105 44 4 106 4 4 107 4 4 108 24 4 109 24 4 110 c 4 111 c 4 112 4004 4 114 1006 4 115 4 4 116 4
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 404 5 53 404 5 54 404 5 55 404 5 56 404 5 57 404 5 58 404 5 59 404 5 60 404 5 61 404 5 62 404 5 100 5 5 102 4 5 103 4 5 104 44 5 105 44 5 106 4 5 107 4 5 108 24 5 109 24 5 110 c 5 111 c 5 112 4004 5 114 1006 5 115 4 5 116 4 5 117 804 5 130 804 5 140 7 5 141 5 5 150 586d 5 211 4004 5 212 1004 5 311 4 5 411 4 5 511 5 5 611 6 5 711 4 --------- ------ --------6 1 de6d 6 50 40
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 110 c 6 111 c 6 112 4004 6 114 1006 6 115 4 6 116 4 6 117 804 6 130 804 6 140 7 6 141 5 6 150 586d 6 211 4004 6 212 1004 6 311 4 6 411 4 6 511 5 6 611 6 6 711 4 --------- ------ --------7 1 de6d 7 50 404 7 51 404 7 52 404 7 53 404 7 54 404 7 55 404 7 56 404 7 57 404 7 58 404 7 59 404 7 60 404 7 61 404 7 62 404 7 100 5 7 102 4 7 103 4 7 104 44 7 105 44 7 106 4 7 107 4 7
7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 111 112 114 115 116 117 130 140 141 150 211 212 311 411 511 611 711 c 4004 1006 4 4 804 804 7 5 586d 4004 1004 4 4 5 6 4 Release History Release 5.1; command was introduced. Related Commands debug fabric status Displays the overall status of all the fabric ASICs. debug fabric stats Displays the fabric ASIC statistics.
debug fabric input Displays the fabric ASIC port number, frame count, and error count. debug fabric input Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines • This command is not valid for OS-6600 series of switches. • Each fabric ASIC has 16 ports in case of 7800 and 8 port in case of 7700. • The frame count on the similar ports for all the fabric ASICs should be same. • There should be no errors on any fabric.
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 5135397 0 --------- ------ ------- ------2 0 5405287 0 2 1 5129581 0 2 2 5135540 0 2 3 5149706 0 2 4 0 0 2 5 5157878 0 2 6 5170105 0 2 7 0 0 2 8 5125862 0 2 9 5134184 0 2 10 5281985 0 2 11 5134612 0 2 12 5135085 0 2 13 0 0 2 14 5157433 0 2 15 5135397 0 --------- ------ ------- ------3 0 5405287 0 3 1 5129582 0 3 2 5135540 0 3 3 5149706 0 3 4 0 0 3 5 5157878 0 3 6 5170105
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 5157879 0 5 6 5170105 0 5 7 0 0 5 8 5125862 0 5 9 5134185 0 5 10 5281985 0 5 11 5134612 0 5 12 5135086 0 5 13 0 0 5 14 5157434 0 5 15 5135398 0 --------- ------ ------- ------6 0 5405287 0 6 1 5129582 0 6 2 5135541 0 6 3 5149706 0 6 4 0 0 6 5 5157879 0 6 6 5170105 0 6 7 0 0 6 8 5125862 0 6 9 5134185 0 6 10 5281985 0 6 11 5134612 0 6 12 5135086 0 6 13 0 0 6 14 5157434 0 6
Related Commands debug fabric status Displays the overall status of all the fabric ASICs. debug fabric stats Displays the fabric ASIC statistics.
debug fabric fbus Displays the fabric ASIC port number and the synchronization status for all the FBUSs. debug fabric fbus Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines • This command is not valid for OS-6600 series of switches. • Each fabric ASIC has 16 ports in case of 7800 and 8 port in case of 7700. • The synchronization status on the similar ports for all the fabric ASICs should be same.
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 Yes 1 15 Yes Yes Yes --------- ------ ----------- ------ ------2 0 Yes Yes Yes 2 1 Yes Yes Yes 2 2 Yes Yes Yes 2 3 Yes Yes Yes 2 4 No No No 2 5 Yes Yes Yes 2 6 Yes Yes Yes 2 7 No No No 2 8 Yes Yes Yes 2 9 Yes Yes Yes 2 10 Yes Yes Yes 2 11 Yes Yes Yes 2 12 Yes Yes Yes 2 13 No No No 2 14 Yes Yes Yes 2 15 Yes Yes Yes --------- ------ ----------- ------ ------3 0 Yes Yes Yes
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 5 4 No No No 5 5 Yes Yes Yes 5 6 Yes Yes Yes 5 7 No No No 5 8 Yes Yes Yes 5 9 Yes Yes Yes 5 10 Yes Yes Yes 5 11 Yes Yes Yes 5 12 Yes Yes Yes 5 13 No No No 5 14 Yes Yes Yes 5 15 Yes Yes Yes --------- ------ ----------- ------ ------6 0 Yes Yes Yes 6 1 Yes Yes Yes 6 2 Yes Yes Yes 6 3 Yes Yes Yes 6 4 No No No 6 5 Yes Yes Yes 6 6 Yes Yes Yes 6 7 No No No 6 8 Yes Yes Yes 6 9
Related Commands debug fabric status Displays the overall status of all the fabric ASICs. debug fabric stats Displays the fabric ASIC statistics.
debug fabric errors Displays the errors detected for all the fabric ASICs on a switch. debug fabric errors Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines This command is only not for OS-6600 series of switches.
debug fabric calendars Displays the fabric ASIC port number, calendar number, and the calendar length. debug fabric calendars Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines • This command is not valid for OS-6600 series of switches. • Each fabric ASIC has 16 ports in case of 7800 and 8 port in case of 7700. • The calendar number and length should be the same for all the similar ports on all the fabric ASICs.
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 2 8 24 2 9 2 2 10 24 2 11 2 2 12 2 2 13 2 2 14 24 2 15 2 2 16 24 --------- -------- -------3 1 2 3 2 24 3 3 1 3 4 2 3 5 24 3 6 2 3 7 2 3 8 24 3 9 2 3 10 24 3 11 2 3 12 2 3 13 2 3 14 24 3 15 2 3 16 24 --------- -------- -------4 1 2 4 2 24 4 3 1 4 4 2 4 5 24 4 6 2 4 7 2 4 8 24 4 9 2 4 10 24 4 11 2 4 12 2 4 13 2 4 14 24 page -114 OmniSwitch Troubleshooting Guide Septem
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 15 2 5 16 24 --------- -------- -------6 1 2 6 2 24 6 3 1 6 4 2 6 5 24 6 6 2 6 7 2 6 8 24 6 9 2 6 10 24 6 11 2 6 12 2 6 13 2 6 14 24 6 15 2 6 16 24 --------- -------- -------7 1 2 7 2 24 7 3 1 7 4 2 7 5 24 7 6 2 7 7 2 7 8 24 7 9 2 7 10 24 7 11 2 7 12 2 7 13 2 7 14 24 7 15 2 7 16 24 Nan Cal Cal Num Num Entry --- --- ----- --- --- --- --- --- --- --- --0 1 1- 8 c 1c 0 0 0 0
0 2 0 3 0 4 0 5 0 6 0 7 0 8 0 9 0 10 0 11 0 12 0 13 0 14 0 15 0 16 page -116 25-32 1- 8 9-16 17-24 25-32 1- 8 9-16 17-24 25-32 1- 8 9-16 17-24 25-32 1- 8 9-16 17-24 25-32 1- 8 9-16 17-24 25-32 1- 8 9-16 17-24 25-32 1- 8 9-16 17-24 25-32 1- 8 9-16 17-24 25-32 1- 8 9-16 17-24 25-32 1- 8 9-16 17-24 25-32 1- 8 9-16 17-24 25-32 1- 8 9-16 17-24 25-32 1- 8 9-16 17-24 25-32 1- 8 9-16 17-24 25-32 1- 8 9-16 0 20 28 34 20 57 52 40 40 6c 60 60 60 80 88 94 80 ac a0 a0 a0 cc c0 c0 c0 e0 e8
--- --1 1 1 2 17-24 34 1 2 1 3 1 4 1 5 1 6 1 7 1 8 17-24 f4 1 15 1 16 --- --2 1 2 2 2 3 17-24 1f4 1f5 1f6 1f7 1f8 1f9 25-32 1e0 1e0 1e0 1e0 1e0 1e0 ----- --- --- --- --- --- --1- 8 c 1c 0 0 0 0 9-16 0 0 0 0 0 0 17-24 0 0 0 0 0 0 25-32 0 0 0 0 0 0 1- 8 20 21 22 23 24 25 9-16 28 29 2a 2b 30 31 35 36 37 38 39 3a 3b 25-32 0 0 0 0 0 0 1- 8 20 21 22 23 24 25 9-16 28 29 2a 2b 30 31 17-24 34 35 36 37 38 39 25-32 20 20 20 20 20 20 1- 8 57 41 42 43 44 45 9-16 52 53 54 55 40 40 17-24 40 40 40
2 4 9-16 60 2 5 2 6 2 7 2 8 2 9 2 10 2 11 2 12 2 13 2 14 2 15 2 16 --- --3 1 3 page -118 2 25-32 40 40 40 40 40 40 40 40 1- 8 6c 7c 60 60 60 60 60 60 60 60 60 60 60 60 60 17-24 60 60 60 60 60 60 60 60 25-32 60 60 60 60 60 60 60 60 1- 8 80 81 82 83 84 85 86 87 9-16 88 89 8a 8b 90 91 92 93 17-24 94 95 96 97 98 99 9a 9b 25-32 80 80 80 80 80 80 80 80 1- 8 ac bc a0 a0 a0 a0 a0 a0 9-16 a0 a0 a0 a0 a0 a0 a0 a0 17-24 a0 a0 a0 a0 a0 a0 a0 a0 25-32 a0 a0 a0 a0 a0 a0 a0 a0 1- 8 cc dc c0 c0
3 3 3 4 3 5 3 6 3 7 9-16 17-24 25-32 1- 8 9-16 17-24 25-32 1- 8 9-16 17-24 25-32 1- 8 9-16 17-24 25-32 1- 8 9-16 17-24 25-32 1- 8 9-16 17-24 28 34 20 57 52 40 40 6c 60 60 60 80 88 94 80 ac a0 a0 a0 cc c0 c0 29 35 20 41 53 40 40 7c 60 60 60 81 89 95 80 bc a0 a0 a0 dc c0 c0 2a 36 20 42 54 40 40 60 60 60 60 82 8a 96 80 a0 a0 a0 a0 c0 c0 c0 2b 37 20 43 55 40 40 60 60 60 60 83 8b 97 80 a0 a0 a0 a0 c0 c0 c0 30 38 20 44 40 40 40 60 60 60 60 84 90 98 80 a0 a0 a0 a0 c0 c0 c0 31 39 20 45 40 40 40 60 6
debug slb help Prints a list of all debug Server Load Balancing (SLB) options. debug slb help Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines • Server Load Balancing (SLB) is not supported on OS-6600 series of switches. • Not all the commands by the help option are implemented right now.
CMMTrace NITrace NIDebug Flags Traps SimServers ServerArp PacketLoss Kill NI Snapshot Certify Takeover Help Release History Release 5.1; command was introduced.
debug http sessiondb Displays the HTTP session database. debug http sessiondb Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines N/A Examples -> debug http sessiondb Sess SessName Name TimeOut Status URL Name--&--StatMsg ---+----+-------------+---------+-------+---------------+-------------------------------Current Active WebView Session: 0 Release History Release 5.1; command was introduced.
debug hre warn Enables and disables the Hardware Routing Engine (HRE) warning messages on a specific HRE. debug hre warn {enable | disable} slot/slice Syntax Definitions enable Enables warning messages. disable Disables warning messages. slot Specifies an NI slot number. slice Specifies an NI slice (ASIC) number. Platforms Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines OS-66000 series does not have a HRE so this commands is not supported on these switches.
debug hre trace Enables and disables Hardware Routing Engine (HRE) trace messages on a specific HRE. debug hre trace {enable | disable} slot/slice Syntax Definitions enable Enables trace messages. disable Disables trace messages. slot Specifies an NI slot number. slice Specifies an NI slice (ASIC) number. Platforms Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines OS-66000 series does not have a HRE so this commands is not supported on these switches.
debug hre pcam Displays all the PCAM entries known on a particular slot and slice. debug hre pcam slot/slice There are two possible arguments to this command - and . is the PCAM index to start with; default is 0. is the number of entries to display; max is 24, default is 12. Syntax Definitions slot Specifies an NI slot number. slice Specifies an NI slice (ASIC) number. start The PCAM index to start with. count The number of entries to display. The range is 0–24.
forward[hdr=fff5] 0c003: 003a0001 c0a83a02 fff2015c 1c00c008 [ipms] src=192.168.58.2, dakey=0001, sgid=03a, svpn=015c forward[hdr=fff2], next=0c008 0c004: 00390001 c0a83902 fff1015c 1c00c000 [ipms] src=192.168.57.2, dakey=0001, sgid=039, svpn=015c forward[hdr=fff1], next=0c000 0c005: 00380001 c0a83802 fff0015c 1c00c001 [ipms] src=192.168.56.2, dakey=0001, sgid=038, svpn=015c forward[hdr=fff0], next=0c001 0c006: 003e0000 c0a83e02 ffef015c 0c000000 [ipms] src=192.168.62.
debug hre pcam verbose Displays all the PCAM entries known on a particular slot and slice. debug hre pcam verbose slot/slice [start count] Syntax Definitions slot Specifies an NI slot number. slice Specifies an NI slice (ASIC) number. start The PCAM index to start with. count The number of entries to display. The range is 0–24.
[ipms] src=192.168.60.2, dakey=0001, sgid=03c, svpn=015c forward[hdr=fff6] mode=5, alloc=collision, prev=0c005 agetype=leaf, current=4, base=4, initial=2, parent=00012 siblingprev=0c000, siblingnext=0c002 0c002: 003b0001 c0a83b02 fff5015c 0c000000 [ipms] src=192.168.59.2, dakey=0001, sgid=03b, svpn=015c forward[hdr=fff5] mode=5, alloc=collision, prev=0c00d agetype=leaf, current=4, base=4, initial=2, parent=00012 siblingprev=0c001, siblingnext=0c003 0c003: 003a0001 c0a83a02 fff2015c 1c00c008 [ipms] src=192.
debug hre pcam mode range This command displays the range of PCAM indices assigned to each mode. debug hre pcam mode range slot/slice Syntax Definitions slot Specifies an NI slot number. slice Specifies an NI slice (ASIC) number. Defaults N/A Platforms Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines OS-66000 series does not have a HRE so this commands is not supported on these switches.
debug hre history Displays the history of the Hardware Routing Engine (HRE). debug hre history slot/slice Syntax Definitions slot Specifies an NI slot number. slice Specifies an NI slice (ASIC) number. Defaults N/A Platforms Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines OS-66000 series does not have a HRE so this commands is not supported on these switches.
Related Commands N/A OmniSwitch Troubleshooting Guide September 2005 page -131
debug hre error Enables/Disables error messages from Hardware Routing Engine (HRE) support software on a Chassis Management Module (CMM) for a specific slot/slice. debug hre error {enable | disable} slot/slice Syntax Definitions enable Enables error messages. disable Disables error messages. slot Specifies an NI slot number. slice Specifies an NI slice (ASIC) number.
debug hre debug Enables/Disables debug messages from Hardware Routing Engine (HRE) support software on a Chassis Management Module (CMM) for a specific slot/slice. debug hre debug {enable | disable} slot/slice Syntax Definitions enable Enables debug messages. disable Disables debug messages. slot Specifies an NI slot number. slice Specifies an NI slice (ASIC) number.
debug hre cmm warn Enables/Disables warning messages from Hardware Routing Engine (HRE) support software on a Chassis Management Module (CMM). debug hre cmm warn {enable | disable} Syntax Definitions enable Enables warning messages. disable Disables warning messages. Platforms Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines OS-66000 series does not have a HRE so this commands is not supported on these switches. Examples -> debug hre cmm warn enable 3/0 Release History Release 5.
debug hre cmm trace Enables/Disables trace messages from Hardware Routing Engine (HRE) support software on a Chassis Management Module (CMM). debug hre cmm trace {enable | disable} Syntax Definitions enable Enables warning messages. disable Disables warning messages. Platforms Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines OS-66000 series does not have a HRE so this commands is not supported on these switches. Examples -> debug hre cmm trace enable 3/0 Release History Release 5.
debug hre cmm error Enables/Disables error messages from Hardware Routing Engine (HRE) support software on a Chassis Management Module (CMM). debug hre cmm error {enable | disable} Syntax Definitions enable Enables warning messages. disable Disables warning messages. Platforms Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines OS-66000 series does not have a HRE so this commands is not supported on these switches. Examples -> debug hre cmm error enable 3/0 Release History Release 5.
debug hre cmm debug Enables/Disables debug messages from Hardware Routing Engine (HRE) support software on a Chassis Management Module (CMM). debug hre cmm debug {enable | disable} Syntax Definitions enable Enables warning messages. disable Disables warning messages. Platforms Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines OS-66000 series does not have a HRE so this commands is not supported on these switches. Examples -> debug hre cmm debug enable 3/0 Release History Release 5.
debug health Enables and disables health debugging. debug health {enable | disable} Syntax Definitions enable Enables health debugging. disable Disables health debugging. Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines N/A Examples -> debug health enable Release History Release 5.1; command was introduced.
debug health cpu Displays the history of CPU utilization on a Chassis Management Module (CMM) if no parameters are specified and displays the history of the CPU’s health if parameters are specified. debug health cpu [slot] Syntax Definitions slot Specifies an interface slot number.
Release History Release 5.1; command was introduced. Related Commands debug health page -140 Enables and disables health debugging.
debug health rx Displays health of receive utilization on a particular slot or slot/port. debug health rx [slot[/port]] Syntax Definitions slot Specifies an interface slot number. port Specifies an interface port number.
Related Commands N/A page -142 OmniSwitch Troubleshooting Guide September 2005
debug health memory Displays history of memory utilization on CMM when no slot number is specified and displays history of memory utilization on a particular slot if a slot number is specified. debug health memory [slot] Syntax Definitions slot Specifies an interface slot number.
Release History Release 5.1; command was introduced.
debug gmap flags Displays the GMAP flags and information about GMAP entries in GMAP database.
debug console flow control Enables and disables the flow control for the console. debug console flow control {enable | disable} Syntax Definitions enable Enables flow control. disable Disables flow control. Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines N/A Examples -> debug console flow control enable Release History Release 5.1; command was introduced.
debug console show flow control Displays the current flow control status. debug console show flow control Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines N/A Examples -> debug console show flow control Flow Control: Enabled Output fields are described below: output definitions Flow Control The current flow control status, which can be Enabled or Disabled. Release History Release 5.1; command was introduced.
debug command-info Enables and disables the command-info mode. debug command-info {enable | disable} Syntax Definitions enable Enables command-info mode. disable Disables command-info mode. Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines N/A Examples -> debug command-info enable CLI command info mode on Release History Release 5.1; command was introduced.
debug clishell data Displays the current information about the session. debug clishell data Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines N/A Examples -> debug clishell data Session Id : 3 EUPM User : 0 CLI oper mode : 0 Def sub-parser : 12 I/O ctrl option : 14 Command prefix : MIP appOut : 71578880 Release History Release 5.1; command was introduced.
debug amap database Verifies if the AMAP database is fine or not. debug amap database Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines N/A Examples -> debug amap database AMAP Debug database ok Output fields are described below: output definitions AMAP Debug database The current status of the AMAP database. Release History Release 5.1; command was introduced.
debug chassis show Displays all the debug configurations. debug chassis show Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines N/A Examples -> debug chassis show Release History Release 5.1; command was introduced.
debug chassis secondary emp Enables and disables the Ethernet Management Port (EMP) port on a secondary Chassis Management Module (CMM) debug chassis secondary emp {enable | disable} Syntax Definitions enable Enables the secondary CMM’s EMP port. disable Disables the secondary CMM’s EMP port. Platforms Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines OS-6600 series does not have an EMP port. Examples -> debug chassis secondary emp enable Release History Release 5.1; command was introduced.
debug chassis hello Enables and disables hello messages from the secondary Chassis Management Module (CMM) to the primary CMM. debug chassis hello {enable | disable} Syntax Definitions enable Enables hello messages. disable Disables hello messages. Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines N/A Examples -> debug chassis hello disable Release History Release 5.1; command was introduced.
debug chassis hello timers Enables and disables hello timers from the primary Chassis Management Module (CMM) to the secondary. If the secondary CMM does not respond back in the interval, it is rebooted. debug chassis hello timers {enable | disable} Syntax Definitions enable Enables hello timers. disable Disables hello timers. Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines N/A Examples -> debug chassis hello timers disable Release History Release 5.
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 after a fatal error. disable Disables chassis auto-reboots after a fatal error. on Same as enable. off Same as disable. Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines N/A Examples -> debug chassis auto-reboot enable Release History Release 5.1; command was introduced.
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-reboots after a fatal error. disable Disables NI auto-reboots after a fatal error. Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines N/A Examples -> debug chassis auto-reboot ni enable Release History Release 5.1; command was introduced.
debug vlan vpas Displays the information about all the ports with their IfIndex and the VLAN membership.
2006 2006 2006 2006 2006 2006 2006 2006 2006 2007 2007 2007 2007 2008 2009 2010 2011 2011 2011 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 4001 page -158 105 108 110 111 112 117 150 211 212 1 62 150 211 1 62 1 1 150 211 1 50 51 52 53 54 55 56 57 58 59 60 61 62 100 102 103 104 105 106 107 108 109 110 111 112 114 115 116 117 130 140 141 150 211 212 311 511 711
4001 4001 4002 4002 4002 6001 6001 6001 6002 6002 6002 7001 7001 7001 7002 7002 7002 8001 8002 8003 8004 8005 8006 8007 8008 8009 8010 8011 8012 8013 8014 8015 8016 8017 8018 8019 8020 8021 8022 8023 8024 9001 9001 9001 9002 9002 9002 10001 10001 10001 10002 10002 10002 11001 11002 12001 12002 13001 13002 104 150 1 105 150 1 108 150 1 109 150 1 110 150 1 111 150 611 140 140 140 140 140 140 140 140 140 140 140 140 140 140 140 140 140 140 140 140 140 114 140 1 150 211 1 112 150 1 150 212 1 114 150 1 1 1 1 1
13003 1 13004 1 13005 1 13006 1 13007 1 13008 1 13009 1 13010 1 13011 1 13012 1 13013 1 13014 1 13015 1 13016 1 13017 1 13018 1 13019 1 13020 1 13021 1 13022 1 13023 1 13024 1 14001 1 14001 117 14001 150 14002 1 14002 130 14002 150 16001 1 16002 1 16003 1 16004 1 16005 1 16006 1 16007 1 16008 1 16009 1 16010 1 16011 1 16012 1 16013 1 16014 1 16015 1 16016 1 16017 1 16018 1 16019 1 16020 1 16021 1 16022 1 16023 1 16024 1 40000001 40000001 40000001 40000001 40000001 40000001 40000001 page -160 1 50 51 52 53
40000001 40000001 40000001 40000001 40000001 40000001 40000001 40000002 40000002 40000002 40000002 40000002 40000002 40000002 40000002 40000002 40000002 40000002 40000002 40000002 40000002 56 57 58 59 60 61 62 1 50 51 52 53 54 55 56 57 58 59 60 61 62 qtagged qtagged qtagged qtagged qtagged qtagged qtagged default qtagged qtagged qtagged qtagged qtagged qtagged qtagged qtagged qtagged qtagged qtagged qtagged qtagged forwarding forwarding forwarding forwarding forwarding forwarding forwarding blocking bloc
debug vlan rule protocol-map Displays the protocol map available. If a proprietary protocol type is configured on the switch that will also display in the output of this command.
debug vlan rule ports Displays all the ports available and can be a candidate for VLAN rules. debug vlan rule ports Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines All the ports shown as “+” are in use. If a “+” appears under mobile column then it indicates that the port has been configured as mobile port.
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 8/24 9/1 9/2 10/1 10/2 11/1 11/2 12/1 12/2 13/1 13/2 13/3 13/4 13/5 13/6 13/7 13/8 13/9 13/10 13/11 13/12 13/13 13/14 13/15 13/16 13/17 13/18 13/19 13/20 13/21 13/22 13/23 13/24 14/1 14/2 16/1 16/2 16/3 16/4 16/5 16/6 16/7 16/8 page -164 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + OmniSwitch Troubleshooting Guide September 2005
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 introduced.
debug vlan rule database Displays the rules configured on the switch for Group Mobility. debug vlan rule database Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines N/A Examples -> debug vlan rule database IP NETWORK RULES B ssz=2 p=563bf88 l=563bf88 R ssz=1 p=46fb488 l=563bf88 PORT RULES B ssz=1 p=563bf88 l=563bf88 r=46fb4ac r=563bf88 v=111 v=114 r=563bf88 v=103 Release History Release 5.1; command was introduced.
debug vlan rule communication Displays the communication of the Chassis Management Module (CMM) with all the software modules and all Network Interface (NI) modules for synchronizing the rules configured on the CMM. debug vlan rule communication Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines • GlobSlice indicates the slot number. • If an NI is not present in the chassis then the state will appear as dead.
GlobSlice: 5 state:RX GlobSlice: 6 state:RX GlobSlice: 7 state:RX GlobSlice: 8 state:RX GlobSlice: 9 state:RX GlobSlice:10 state:RX GlobSlice:11 state:RX GlobSlice:12 state:RX GlobSlice:13 state:RX GlobSlice:14 state:DEAD GlobSlice:15 state:RX skt=0x130 rslot=6 rslice=0 rapp=9 rsnp=2 CNXNLESS skt=0x130 rslot=7 rslice=0 rapp=9 rsnp=2 CNXNLESS skt=0x130 rslot=8 rslice=0 rapp=9 rsnp=2 CNXNLESS skt=0x130 rslot=9 rslice=0 rapp=9 rsnp=2 CNXNLESS skt=0x130 rslot=10 rslice=0 rapp=9 rsnp
debug vlan communication Displays the communication of the Chassis management Module (CMM) with all the software modules and all Network Interface (NI) modules. debug vlan communication Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines • GlobSlice indicates the slot number. • If an NI is not present in the chassis then the state will appear as dead.
defaults assumed=0 txrty=0 txfail=0 SNMP sid= 1d defaults assumed=0 txrty=0 txfail=0 Webview sid= 1d defaults assumed=0 txrty=0 txfail=0 IPMS MC sid= 27 defaults assumed=0 txrty=0 txfail=0 Regist sid= 36 defaults assumed=1 txrty=0 txfail=0 GrpMob sid= 2c defaults assumed=0 txrty=0 txfail=0 IP sid= 20 defaults assumed=0 txrty=0 txfail=0 DRC sid= 23 defaults assumed=0 txrty=0 txfail=0 SLB sid= 24 defaults assumed=0 txrty=0 txfail=0 IPX sid= 21 defaults assumed=0 txrty=0 txfail=0 UDP Rly sid= 22 defaults assum
IPMS VL sid= 32 defaults assumed=0 txrty=0 txfail=0 QOS sid= 31 defaults assumed=0 txrty=0 txfail=0 Link Agg sid= 33 defaults assumed=1 txrty=0 txfail=0 Mirror sid= 34 defaults assumed=1 txrty=0 txfail=0 SNMP Agt sid= 35 defaults assumed=0 txrty=0 txfail=0 rap= 17 rsp= 34 CNXN-OR ESTABLISHED notify=80 bfrty=0 rap= 13 rsp= 2 CNXN-OR ESTABLISHED notify=82 bfrty=0 rap= 12 rsp= 1 CNXN-OR ESTABLISHED notify=4 bfrty=0 rap= 23 rsp= 1 CNXN-OR NO-RX notify=0 bfrty=0 rap= 68 rsp= 7 CNXN-O
Related Commands N/A page -172 OmniSwitch Troubleshooting Guide September 2005
debug port information Displays all the information related to an interface. It includes the counters, mobile port configuration, tag, aggregate, phy, LED, and MAC related information debug port information slot/port Syntax Definitions slot Specifies an interface slot number. port Specifies an interface port number. Defaults N/A Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines N/A Examples -> debug port information 11/1 Release History Release 5.
debug qos Configures the type of QoS events that will be displayed in the QoS log.
egress Logs information about packets leaving the switch. rsvp Logs information about RSVP flows. Currently not supported. balance Logs information about flows that are part of a load balancing cluster. Not supported for the OmniSwitch 6624/6648. nimsg Logs information about QoS interfaces. Defaults By default basic information messages are logged (info). Error messages are always logged.
debug systrace Enables or disables sysTrace logging. The system trace, or sysTrace, facility provides a consistent, highlevel mechanism for capturing event records in a history buffer. Captured sysTrace information can be referenced for system debugging or following the unlikely event of a system crash. This trace facility will generally be used by higher level applications. debug systrace {enable | disable} Syntax Definitions enable Enables sysTrace logging. disable Disables sysTrace logging.
Related Commands debug ktrace Enables or disables kTrace logging. debug ktrace appid level Adds or removes a kTrace capture level for a specified subsystem. debug ktrace show Displays current kTrace parameters. debug ktrace show log Displays kTrace log information. debug systrace watch Enables or disables sysTrace log output to the console. debug systrace appid level Adds or removes a sysTrace capture level for a specified subsystem.
debug systrace watch Enables the sysTrace log on the console, or turns off (disables) the console display. debug systrace watch {enable | disable} Syntax Definitions N/A Defaults parameter default enable | disable Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines N/A Examples -> debug systrace watch enable -> debug systrace watch disable Release History Release 5.1; command was introduced. Related Commands debug ktrace Enables or disables kTrace logging.
debug systrace show Displays sysTrace debug log information (e.g., sysTrace status, Application IDs with non-default Severity Level settings).
Related Commands debug ktrace Enables or disables kTrace logging. debug ktrace appid level Adds or removes a kTrace capture level for a specified subsystem. debug ktrace show Displays current kTrace parameters. debug ktrace show log Displays kTrace log information. debug systrace Enables or disables sysTrace logging. debug systrace watch Enables or disables sysTrace log output to the console. debug systrace appid level Adds or removes a sysTrace capture level for a specified subsystem.
debug systrace appid level Adds or removes a sysTrace capture level for a specified application ID (i.e., subsystem). debug systrace appid {app_id | integer} level {level | integer} debug systrace no appid app_id Syntax Definitions app_id An application ID keyword value. Currently supported application IDs are listed below. appid integer A numerical equivalent value for the application ID. Currently supported numeric equivalent values are listed below.
Defaults parameter default level info Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines • You may enter more than one application ID in the command line. Separate each application ID with a space. • Application IDs may be entered in any order. Examples -> -> -> -> debug debug debug debug systrace systrace systrace systrace appid 254 level off appid policy level info appid policy snmp web aaa vlan level alert no appid debug2 Release History Release 5.
debug systrace show log Displays sysTrace log information. debug systrace show log [file] Syntax Definitions file Specifies a particular file from which sysTrace log information will be displayed.
Output fields are described here: output definitions Timestamp The timestamp indicating when the sysTrace log entry occurred. Values can range from 0x00000000 through 0xffffffff. AppID The Application ID for which the stored sysTrace log information is displayed. Values can range from 0x00 through 0xff. Trace Level The Severity Level for which the stored sysTrace log information is displayed. Task The Task for which the stored sysTrace log information is displayed.
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 following some precipitating event (e.g., a system error). show log pmd file_name [type type_string | id registrationidentifier_int | subid subidentifier_int | taskname taskname_string | taskid tasknumber_int | record recordtype_string | address address_int] Syntax Definitions file_name Specifies a file containing the PMD dump information.
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 0 0 2c 4f 0 0 c7 58 0 0 58 40 0 0 53 fc 0 0 b9 f0 0 0 d6 71 0 7 0 d c3 20 0 4e 6f 24 0 0 9e c5 0 23 2a 2 0 5 77 c4 0 2 91 f1 0 1 0 4 2c 6 0 9 3e d4 0 e dd 7e 0 24 2d 4 0 2a 43 e0 0 a1 4 89 0 80 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 18 42 50 3 43 8 d0 0 0 0 0 3 43 9 18 2 6a 7e 38 0 0 0 0 3 43 3 43 7 90 3 18 15 0 ------------------------------------------------------------Registration Ty
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. ->3571290 Record Type -> UserDefined Task Id -> 3571290 Address -> 1adcc50 Size -> 11 53 65 63 6f 6e 64 20 69 74 65 72 61 74 69 6f 6e a ------------------------------------------------------------Registration Type ->Task Task No.
Output fields are described here: output definitions PMD Version The Post Mortem Dump (PMD) version ID. File Dump Type The file dump type. Date Created The date when the log was created. Registration Type The type of data being registered with PMD. Application ID The ID of the Application registering with PMD. Record Type The type of data registered with PMD. Address The address of the data being registered. Size The size (number of bytes) being registered.
debug memory monitor Enables or disables memory monitoring functions. debug memory monitor {enable | disable} Syntax Definitions enable Enables memory monitoring. disable Disables memory monitoring. Defaults parameter default enable | disable disable Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines N/A Examples -> debug memory monitor enable -> debug memory monitor disable Release History Release 5.1; command was introduced.
debug memory monitor show status The debug memory monitor show status command displays memory monitoring status information. debug memory monitor show status Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines N/A Examples -> debug pmd ni 3/0 Release History Release 5.1; command was introduced. Related Commands debug memory monitor show log Displays memory monitoring log information.
debug memory monitor show log Displays memory monitoring log information.
CliShell0 02314da8 272 02b33a3c malloc SSYaccStac SSYaccInit CliShell0 023183d8 512 02b33a3c malloc CliParse clishell_m CliShell0 027b0100 576 02b33a3c malloc CliParse clishell_m CliShell0 0107a128 2404 02b33a3c malloc CliParse clishell_m CliShell0 0107aa98 1280 02b33a3c malloc CliParse clishell_m Stp Vx C Sem024fdcc8 28 0011f038 semCCreate zcSelect stpSock_st LnkAgg Vx C Sem 023182e8 28 0011f038 semCCreate zcSelect lagg_Sock_ AmapMgr Vx C Sem 02318270 28 0011f038 semCCreate zcSelect xmap_main_ GrpMob Vx C
Related Commands debug memory monitor Enables or disables memory monitoring functions. debug memory monitor show log global Displays memory monitoring global statistics. debug memory monitor show log task Displays memory monitoring task statistics. debug memory monitor show log size Displays memory monitoring size statistics.
debug memory monitor show log global Displays memory monitoring global statistics. debug memory monitor show log global Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines N/A Examples -> debug memory monitor show log global Current = 33741 Cumulative = 687952 Output fields are described here: output definitions Current The amount of dynamic memory allocated (currently) since the last enable.
Related Commands debug memory monitor Enables or disables memory monitoring functions. debug memory monitor show log Displays memory monitoring log information. debug memory monitor show log task Displays memory monitoring task statistics. debug memory monitor show log size Displays memory monitoring size statistics.
debug memory monitor show log task Displays memory monitoring task statistics.
Health AAA Ipedr NanDrvr Ftpd Telnetd tCS_CVM tssApp65535_3 SsApp SesMgr SNMPagt TrapMgr EIpc VlanMgr PortMgr Gateway CfgMgr tCS_HSM tCS_CMS tCS_PRB tCS_CCM tCsCSMtask tSwLogTask 249 221312 31500 56 56 9552 28 228 49088 69200 26347 4548 2336 208 804 84 228 1240 188 312 612 586128 127649 222236 105868 74396 56 9552 28 228 198284 202029 210129 63976 2392 149672 75424 140 897491 2500 328 340 12555 15256874 13519+ Output fields are described here: output definitions Task Name The task that “owns” the memory
debug memory monitor show log size Displays memory monitoring size statistics.
Release History Release 5.1; command was introduced. Related Commands debug memory monitor Enables or disables memory monitoring functions. debug memory monitor show log Displays memory monitoring log information. debug memory monitor show log global Displays memory monitoring global statistics. debug memory monitor show log task Displays memory monitoring task statistics.
debug ktrace Enables or disables kTrace logging. The kernel trace, or kTrace, facility provides a consistent, low-level mechanism for capturing integer-based event records in a history buffer. This trace facility will generally be used by lower level functions to track information, such as which task is operating. debug ktrace {enable | disable} Syntax Definitions enable Enables kTrace logging. disable Disables kTrace logging.
Related Commands debug ktrace appid level Adds or removes a kTrace capture level for a specified subsystem. debug ktrace show Displays current kTrace parameters. debug ktrace show log Displays kTrace log information. debug systrace Enables or disables sysTrace logging. debug systrace watch Enables or disables sysTrace log output to the console. debug systrace appid level Adds or removes a sysTrace capture level for a specified subsystem.
debug ktrace show Displays current kTrace parameters (e.g., kTrace status, Application IDs with non-default Severity Level settings).
Related Commands debug ktrace Enables or disables kTrace logging. debug ktrace appid level Adds or removes a kTrace capture level for a specified subsystem. debug ktrace show log Displays kTrace log information. debug systrace Enables or disables sysTrace logging. debug systrace watch Enables or disables sysTrace log output to the console. debug systrace appid level Adds or removes a sysTrace capture level for a specified subsystem. debug systrace show Displays sysTrace debug log information.
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 {level | integer} debug ktrace no appid app_id Syntax Definitions app_id An application ID keyword value. Currently supported application IDs are listed below. appid integer A numerical equivalent value for the application ID. Currently supported numeric equivalent values are listed below. Supported Application IDs and Numeric Equivalents 802.
Defaults parameter default level info (6) Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines • You may enter more than one application ID in the command line. Separate each application ID with a space. • Application IDs may be entered in any order. Examples -> -> -> -> debug debug debug debug ktrace ktrace ktrace ktrace appid 254 level off appid policy level info appid policy snmp web aaa vlan level alert no appid debug2 Release History Release 5.
debug ktrace show log Displays kTrace log information. debug ktrace show log [file] Syntax Definitions file Specifies a particular file from which kTrace log information will be displayed.
Output fields are described here: output definitions Event The event for which kTrace log information is displayed. Timestamp The timestamp for the kTrace log information being displayed. Values can range from 0x00000000 through 0xffffffff. AppID The Application ID (subsystem) for which kTrace log information is displayed. Values can range from 0x00 through 0xff. Level The Severity Level for which kTrace log information is displayed.
page -208 OmniSwitch Troubleshooting Guide September 2005
C Technical Support Commands This chapter describes Technical Support Command Line Interface (CLI) show commands that create log files of the output from multiple standard CLI show commands. These log files can be transferred with FTP to a workstation for off-line analysis and troubleshooting. Note. See the OmniSwitch CLI Reference Guide for more information on standard CLI show commands.
show tech-support Creates a log file of the output of several system-wide Command Line Interface (CLI) commands. show tech-support Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines • This command creates a file called tech_support.
show tech-support layer2 Creates a log file of the output of several Layer 2 Command Line Interface (CLI) commands. show tech-support layer2 Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines • This command creates a file called tech_support_layer2.
show tech-support layer3 Creates a log file of the output of several Layer 3 Command Line Interface (CLI) commands. show tech-support layer3 Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines • This command creates a file called tech_support_layer3.
show tech-support layer3 rip Creates a log file of the output of several Routing Information Protocol (RIP) Command Line Interface (CLI) commands. show tech-support layer3 rip Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines • This command creates a file called tech_support_rip.
show tech-support layer3 pimsm Creates a log file of the output of several Protocol-Independent Multicast Sparse Mode (PIM-SM) Command Line Interface (CLI) commands. show tech-support layer3 pimsm Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines • This command creates a file called tech_support_pimsm.
show tech-support layer3 ospf Creates a log file of the output of several Open Shortest Path First routing (OSPF) Command Line Interface (CLI) commands. show tech-support layer3 ospf Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines • This command creates a file called tech_support_ospf.
show tech-support layer3 mroute Creates a log file of the output of several multicast routing Command Line Interface (CLI) commands. show tech-support layer3 pimsm Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines • This command creates a file called tech_support_mroute.
show tech-support layer3 ipx Creates a log file of the output of several Internet Packet Exchange (IPX) protocol Command Line Interface (CLI) commands. show tech-support layer3 ipx Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 6624, 6648, 7700, 7800, 8800 Usage Guidelines • This command creates a file called tech_support_ipx.
show tech-support layer3 dvmrp Creates a log file of the output of several Distance Vector Multicast Routing Protocol (DVMRP) Command Line Interface (CLI) commands. show tech-support layer3 dvmrp Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines • This command creates a file called tech_support_dvmrp.
show tech-support layer3 bgp Creates a log file of the output of several Border Gateway Protocol (BGP) Command Line Interface (CLI) commands. show tech-support layer3 bgp Syntax Definitions N/A Defaults N/A Platforms Supported OmniSwitch 7700, 7800, 8800 Usage Guidelines • This command creates a file called tech_support_bgp.
page -12 OmniSwitch Troubleshooting Guide September 2005
D Modifying Files with VI Editor The switch has a built in Unix text editor called VI. This section covers some basic VI commands and how to use VI to modify the IP address of the EMP (Ethernet Management Port), which is stored in the boot.params file. The boot.params file can also be modified via MiniBoot.
Useful VI Commands Useful VI Commands The following are some useful VI commands: u - undo the last command. CTL/L -reprint current screen. CTL/F-pages forward one screen. CTL/B-pages back one screen. j -moves cursor down one line. k -moves cursor up one line. h - moves cursor back one character. l - moves cursor forward one character. Enter key - moves cursor to the beginning of next line. 0 -zero moves cursor to beginning of current line. $ -- moves cursor to end of current line.
Sample VI Session Dew - Deletes the current word. P - Puts back text from previous delete. yy-Puts the current line in buffer; leaves the current line intact. p-Places the line in the buffer after the current position of the cursor. ZZ-Exits VI and saves the changes. :q-quits VI session and does not save any of the changes. Sample VI Session The following is a sample way to use the VI editor to modify the boot.params file. Note. The commands performed below are executed from the /flash directory (root).
Sample VI Session page -4 OmniSwitch Troubleshooting Guide September 2005
Index Numerics 802.
show show ip rip redist command 12-14 show spantree command 4-2, 7-4 show spantree ports command 4-3 show stack topology command 1-4 show swlog command 1-7 show tech-support command 1-10, C-2 show tech-support layer2 command 1-10, C-3 show tech-support layer3 bgp command C-11 show tech-support layer3 command 1-10, C-4 show tech-support layer3 dvmrp command C-10 show tech-support layer3 ipx command C-9 show tech-support layer3 mroute command C-8 show tech-support layer3 ospf command C-7 show tech-support lay
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 command 1-22 print_configured_list_8021q_ni command 8-7 print_default_vlan_8021q_cmm command 8-7 slcDumpL2DA command 3-8 slcDumpL2SA command 3-7 slcDumpSlotSlice command 3-10 smctx command 1-23 spyReport command 1-11 stack_topo command 1-24 stp_help command 4-10, 4-25 stp_printf_flag command 4-7 stp_traceprint command 4-10 stpCMM_traceprint command 4-25 stpni_debugLpor
V VI editor D-1 VLANs Debug commands page -4 B-157 OmniSwitch Troubleshooting Guide September 2005