OmniSwitch 6600 Family

High Availability Advanced Workgroup Switching
OmniSwitch 6600 family switches are advanced 10/100 based stackable layer 3 workgroup switches that provide wire rate L2+ switching, L3 routing and advanced services with high availability for IP communications and mission-critical environments. A compact form factor, a rich set of features and a high availability design makes the OS6600 a great choice for the following applications: Enterprise workgroups/LAN wiring closets Edge deployments and branch ofces Converged voice and data environments Power over Ethernet 100BaseFX ber to the desktop
The OmniSwitch 6600 family consists of the OmniSwitch 6600 and OmniSwitch

OmniSwitch OS6600-48

6602 series switches. The OmniSwitch 6600 provides 24/48 10/100 ports in a 1.5U form factor with two expansion slots for optional two port Gigabit stacking modules and/or two port ber or copper Gigabit uplinks and an internal slot on the back of the chassis for pluggable backup power supply.

OmniSwitch OS6600-24

OmniSwitch 6600-24 - 24 10/100 RJ45 ports OmniSwitch 6600-48 - 48 10/100 RJ45 ports OmniSwitch 6600-U24 - 24 SFP based 100BaseFX ports that accept industr y standard 100BaseFX optics.

OmniSwitch OS6600-U24

OmniSwitch 6600-P24 - 24 10/100 RJ45 ports with standards-based PoE (uses external backup power supply)
New to the OS6600 family is the reengineered OS6602 series that is based

OmniSwitch OS6600-P24

on the OS6600, but comes in a new 1U design and has a xed conguration that includes two ports of SFP (small form plugware) for Gigabit connectivity and two ports for stacking built in. The OS6602 is completely interoperable with the OS6600 including a mixed stack virtual chassis.

OmniSwitch OS6602-24

OmniSwitch 6602-24 - 24 10/100 RJ45 OmniSwitch 6602-48 - 24 10/100 RJ45
The Alcatel enterprise 10/100 LAN offering also includes the value based 10/100 L2+ stackable switches OmniStack 6124 and 6148.

OmniSwitch OS6602-48

Complementing the OS6600 and OS6100 10/100 xed conguration switches, the OmniStack 6300 series is the rst Alcatel xed conguration Gigabit Ethernet 10/100/1000 to the desktop series of switches.

A L C AT E L

Alcatel OmniSwitch 6600 Family
Alcatels xed conguration switches are part of the Alcatel enterprise LAN offering that includes the larger capacity, modular-based OmniSwitch 7700, 7800, and 8800 series of core switches. Together this family offers a complete edge-to-core solution with high availability, intelligent performance, and enhanced security in an easy to manage, exible, and scalable package. Alcatel understands the need to control service costs and provides a limited lifetime warranty on all OmniSwitch 6600 family switches.

Virtual Chassis

What is a virtual chassis? Essentially, a virtual chassis takes the best attributes of a modular chassis switch and applies them to lower cost xed conguration switches, allowing the enterprise to manage and scale their network effectively and affordably. With the addition of the OS6602 a virtual chassis can consist of up to eight switches of either the OS6602, the OS6600 or a mix of both. The virtual chassis provides: single IP address management easy synchronization of switch software and congurations across all switches within a single stack dedicated fault tolerant backplane using hardware stacking link aggregation across chassis N:1 management backup because each switch is fully capable of providing management for the virtual chassis When a group of OS6600/OS6602 switches are congured in a virtual chassis, an automatic election takes place to elect the primary and secondary management entity. If the primary or secondary switch fail, recurrent automatic elections take place for their replacement. Another great benet of the virtual chassis is that it can be very quickly and simply scaled up, torn down or recongured to suit the needs of the enterprise.

High Availability

The OS6602/OS6600 support cost effective 1:1 backup power supplies, fault tolerant loop stacking, and virtual chassis link aggregation preventing single points of failure. Any switch within a virtual chassis that provides management functionality and automatic election of primary and secondary managers provides N:1 management redundancy. Quality of service in the network addresses availability by ensuring mission critical applications, such as IP telephony and other delay sensitive applications, receive the expedited forwarding they require to be available and effective. The OS6600 family supports per port queuing, ow-based QoS rules and bandwidth management to help guarantee mission applications are available.

Secure Networking

Security is a primary focus of every CIO. To address this concern, the OS6600 family provides features that support a multi-layered approach to network security. Access to the network is controlled by either ltering out unwanted trafc, forcing authentication of the user, or allowing only pre-authorized devices access. Switch administration controls include support for encrypted management communication and authentication of the administrator. Further switch management granularity can be congured so that administrators only have access to features under their responsibility or expertise. The OS6600 family also supports emerging technologies that identify and quarantine devices that do not meet administrator dened requirements. In the quarantined environment the end device has access to network resources that remediate the device and return it to a state where network access can then be granted.

Simplied Management

OneTouch QoS for simplified networkwide configuration of QoS policies Resource manager for backup/restore switch software and configuration Locator ser vice to locate end devices for troubleshooting and virus containment
Its very common today to nd small IT departments tasked with managing large enterprise networks. Typically, the IT department is staffed with people of varying expertise who dont have the luxury of time or budget for extensive training. To address this situation, large networks need to be easy to install, manage, and troubleshoot. Alcatel tackles this situation by providing OmniVista, a powerful network management platform for its AOS based OmniSwitch family. When an enterprise network uses an all AOS-based solution, training, installation, conguration and troubleshooting is minimized. For that reason, Alcatel designed the OS6600 family to have an AOS-based CLI, just like the larger modular-based OmniSwitch. Additionally, the Web-based manager has the same look and feel across the AOS line of switches and provides a point and click method with online help to ease conguration of new features.

Network Applications

10/100 Advanced Workgroup The AoS based OmniSwitch 6600 series, using the virtual chassis design, provides high availability to support mission critical applications at the edge of your network. When combined with the OmniSwitch 7000/8000 chassis-based solutions, you get the highest availability and easiest to manage edge-to-core network in the industry. The OS6600 familys compact xed form factor design, and modular expandability provides an easy path to scale any workgroup up to 384 10/100 ports and 16 Gigabit Ethernet ports in a single stack.

Power over Ethernet

By adding the OS6600-P24 to your existing virtual chassis, you get seamless migration to standards-based power over Ethernet capability for IP phones, wireless access points, Web cameras or any other 802.3af compliant end-devices.

Fiber to the Desktop

The OS6600-U24 offers the ability to provide 100BaseFX ber to the desktop connectivity that is typically needed for security or extended reach needs. The OS6600-U24s SFP design is costeffective, extremely exible, and supports multimode or single mode ber for distances up to 40km on a per port basis.

Fiber PoE Cat 5

Product Specications

Feature

Simplified manageability Dual image and conguration le storage for local backup Certied and working directories allow automatic fallback to known good congurations Intuitive AOS CLI. Provides common CLI from edge to core when used with OS7000/8000 Remote Telnet Port based port mirroring supports 1 session per 24 port or 2 sessions per 48 port switch User readable conguration les allow ofine editing IGMPv1/v2 snooping to optimize multicast trafc System event logging RMON support statistics, history, alarms, events NTP - Network time protocol to synchronize network devices AMAP - Alcatel protocol to assist in building topology maps in OmniVista
VLAN support 255 VLANs with 4,094 VLAN tag value support Per port, 802.1Q, DHCP, IPX and authenticated VLAN support Routing protocol support RIPv1/v2 OSPF VRRP RDP High availability 802.1w Rapid Recovery Spanning Tree allows subsecond failover to redundant link 802.1d Spanning Tree for loop free topology and link redundancy Fast forwarding mode on user ports to bypass 30 second delay for Spanning Tree Static and 802.3ad dynamic link aggregation supports automatic conguration of link aggregates with other switches (up to six aggregates with up to eight links per aggregate) Broadcast storm control Redundant 1:1 power supply

Quality of ser vice 4 hardware queues per port and strict priority queue servicing to support mission critical applications Layer 2: SA/DA MAC/MAC Group, SA/DA VLAN, SA/DA slot/port/group, SA/DA Interface type Layer 3 (IP only): SA/DA IP address/group, Multicast address & Group (accept or deny), IP Protocol Layer 4: source/Dest TCP/UDP port & and TCP/UDP Protocol 802.1p stamping per port, TOS/DSCP stamping on a packet based on SA/DA (slot/port, IP address, IP protocol, L4 port) QoS remapping: 802.1p to 802.1p (per port only) IP-TOS to 802.1p (Global rule), DSCP to 802.1p (Global rule) Classication per port, 802.1p (CoS) value, MAC SA/DA, ToS precedence, DSCP value, IP SA/DA, TCP/UDP port 802.1p (CoS), ToS, DSCP marking to label mission critical packets with QoS information Egress ow-based rate limiting
Advanced security 802.1x industry standard port-based authentication challenges users with a name and password before allowing network access Learned port security or MAC address lockdown allows only known devices to have network access, preventing unauthorized network device access RADIUS admin authentication prevents unauthorized switch management Secure Shell (SSH), Secure Socket Layer (SSL) and SNMPv3 for encrypted remote management communication Access control lists to lter out unwanted trafc, including denial of service attacks (ACLs per MAC SA/DA, IP SA/DA, TCP/UDP port) Operating environment Total heat dissipation OS6600-24: 226 BTU/hr OS6600-P24: 413 BTU/hr OS6600-U24: 330 BTU/hr OS6602-24: 151 BTU/hr OS6600-48: 326 BTU/hr OS6602-48: 226 BTU/hr Storage temperature: 14 to 158 F (-10 to 70 C) Operating temperature: 32 to 113 F (0 to 45 C) Humidity: 5% to 95% (Noncondensing)
Operating altitude: Sea level to 10,000 feet (3 km) Noise level OS6600 series: 56 dB OS6602 series: 47 dB Number of power supplies supported All models support a primary power supply and backup power supply for chassis power OS6600-P24 external power supply module supports 1 additional internal power supply for PoE power OS6600-BPS-P provides 2 power supplies; 1 for backup chassis power and 1 for backup PoE power OS6600 AC power supply Input power: 162 watts AC Input voltage: 85 ~ 270 VAC Input current: 1.8 Amps AC @ 90VAC or 0.704 Amp AC @ 230 VAC Input frequency: 47 to 63 ( 3%) HZ OS6602 AC power supply Input power: 140 watts AC Input voltage: 100 to 240 VAC Input current: 1.4 Amps AC @ 100 VAC or 0.61 Amps AC @ 230 VAC Input frequency: 47 to 63 Hz (3%)

OS6602 DC power supply Input power range: 136.8 watts DC to 115.2 watts DC rated Input voltage range: 36 to 72 VDC Nominal input voltage: 48 VDC Input current range: 3.8 Amps DC to 1.6 Amps DC rated OS6600 PoE power supply Input power: 379.5 watts AC Input voltage: 88 ~ 264 VAC Input current: 3.3 Amps AC @ 115 VAC or 1.65 Amps AC @ 230 VAC Input frequency: 47 to 63 ( 3%) HZ Note: the maximum power available for the PoE is 210 watts DC Warranty Limited lifetime hardware warranty: Limited to the original owner, and will be provided for up to ve years after products End of Sales announcement. Faulty parts will be replaced within ve (5) business days-AVR (Advance Replacement) RMA Ser vice and support Please ontact your Alcatel representative

Form Factor

Description
OS6600-24/48 OS6600-P24 OS6600-U24 OS6602-24/48
1.5U, 24/48 10/100 RJ-45 ports with 2 expansion slots
1.5U, 24/48 10/100 RJ-45 ports with PoE support and 2 expansion slots (2.6x17.12x14.6)In (6.6x43.48x37)Cm 6600-Plbs YES, 2 port Gigabit miniGBIC module, 2 port stacking module RJ-45 YES NO External, requires OS6600-BPS-P, provides chassis and PoE backup power
1.5U, 24 100BaseFX SFP ports with 2 expansion slots
1.0U, 24/4810/100 RJ-45 ports with 2 Gigabit stack ports and 2 Gigabit miniGBIC ports built in (1.74x17.32x16.11)In (4.42x44x40.92)Cm 6602-lbs 6602-48 13.66 lbs N/A
Dimensions (HxWxD) Weight Modular expansion Console Connector PoE Support 100Base Fiber support (Optional) Backup Power
(2.6x17.12x13.94)In (6.6x17.12x35.4)Cm 6600-24 12.46 lbs 6600-48 13.66 lbs YES, 2 port Gigabit miniGBIC module, 2 port stacking module DB-9 NO NO Internal, requires OS6600-BPS
(2.6x17.12x13.94)In (6.6x43.48x35.4)Cm 6600-U24 12.46 lbs YES, 2 port Gigabit miniGBIC module, 2 port stacking module RJ-45 NO YES, 100BaseFX SFP Internal, requires OS6600-BPS
RJ-45 NO NO Internal, requires OS6602-BPS. Also supports DC backup using the OS6602-BPSDC

Certications/Safety

Safety Standards AS/NZS 3260 (Australia Safety Standard); CAN/CSA-C22.2 no.60950-00; CB Report and Cert. (International safety of ITE) with all national deviations (IEC 950); CE Marking per Low Voltage Directive (LVD) (European Safety Directive); CDRH Letter of Approval (US FDA Approval); 21 CFR 1040 (part of Laser Certication per EN 608251 & EN 60825-2); EN60825-1 (Laser Evaluation) &EN60825-2 (Laser Evaluation): 1994, A11: 1996 (European Safety of Lasers Products); EN60950: 2000/A1-4, A11+Deviations (European Safety of ITE); ETS Storage Class 1.1/ Transportation Class 2.3/Stationary Use Class 3.1; FCC 21 CFR Subpart J (US Safety of Laser Products); GOST (Russian Federation Certicate); TS 001; TUV GS Mark (German Notied Body) EN 60950; ULAR: Argentina Certication & S Mark (Argentina Safety Approval); UL 60950 EMC Standards AS/NZS 3548 (Australia Emissions) Class A/B*; 1997 Class A&B* (International Emissions); 15, Subpart B&J, Class A/B*; 1998 Class A/B* (European Emissions); BSMI, Class A; CE Marking per EMC Directive; EN50082-1; CISPR22: EN55022: CNS 13438:1997 Class A (Taiwan Emissions); FCC 47 CFR Part

89/336/EEC EMC Directive (European Requirements);
EN55024: 1998 includes EN61000-4-2, 3, 4, 5, 6, 7, 11 (European
Immunity); EN60555-2; EN61000-3-2 (European Harmonics & Flicker); EN61000-3-3 (European Harmonics & Flicker); EN61000-4-2; EN61000-4-3; EN61000-4-4; EN61000-4-5; N61000-4-6; EN61000-4-8; EN61000-411; ICES-003 Class A&B*; IEC 1000-3-2; IEC 60950; MIC Mark (Korean Emissions & Immunity Approval); NOM/NYCE (Mexican Product Safety & EMC Authorities); NOM-019-SCFI 1994 & NOM-019-SCFI-1998; VCCI Class A&B* (Japan Emissions); VCCI-V3/97.04, Class A & B*
*OS6602 series switches are Class A certied only

Standards

Standards (abridged) IEEE 802.1D Spanning Tree Protocol IEEE 802.1D-1998 Priority and Dynamic Multicast Filtering IEEE 802.1p IEEE 802.1Q VLAN Tagging IEEE 802.1w Rapid Reconguration (Fast Spanning Tree) IEEE 802.1x Port-based network access control IEEE 802.3 10BaseT Ethernet IEEE 802.3ab 1000BaseT twistedpair Gigabit Ethernet IEEE 802.3ad Dynamic link aggregates IEEE 802.3af Power over Ethernet IEEE 802.3u 100BaseTX, 100BaseFX Fast Ethernet IEEE 802.3x Full Duplex with Flow Control IEEE 802.3z 1000BaseX ber optic Gigabit Ethernet RFC 768 UDP RFC 791 IP RFC 792 ICMP RFC 793 TCP RFC 826 ARP RFC 854 Telnet RFC 903 Reverse ARP RFC 925 Multi-LAN ARP/Proxy ARP RFC 1058 RIPv1 RFC 1191 Path MTU Discovery RFC 1493 Bridge MIB RFC 1519 Classless Inter-Domain Routing (CIDR) RFC 1542 BOOTP RFC 1587 OSPF NSSA Option RFC 1724 RIP v2 MIB RFC 1757 RMON (groups 1, 2, 3, and 9) RFC 1765 OSPF Database Overow RFC 1812 IP router requirements RFC 1850 OSPF2 MIB RFC 1907 MIB-II RFC 2011 SNMPv2 MIB for the IP using SMIv2 RFC 2012 SNMPv2 MIB for the TCP using SMIv2 RFC 2013 SNMPv2 MIB for the UDP using SMIv2 RFC 2096 IP Forwarding MIB RFC 2138 RADIUS RFC 2233 Interfaces MIB RFC 2236 IGMP & IGMPv2 RFC 2328 OSPFv2 RFC 2338 VRRP RFC 2453 RIPv2 RFC 2644 IP router requirements RFC 2665 Ethernet MIB RFC 2674 VLAN Management MIB RFC 2737 (Entity MIB using SMIv2) Version2 RFC 2819 Remote Network Monitoring MIB RFC 2863 Interfaces Group MIB RFC 2933 IGMP v2 MIB

Ordering Information

Model Number Description

OS6600-24

OmniSwitch 6600 chassis w/DES, 3DES, RC2 & RC4. [ECCN 5A002] 24 port 10/10 chassis with 2 open slots for optional uplinks or stacking module and one slot in back for an optional redundant and hot swappable backup AC power supply. Advanced routing and/or authentication software is sold separately. Country specic power cord required. OmniSwitch 6600 chassis w/DES, 3DES, RC2 & RC4. [ECCN 5A002] 24 port power over Ethernet 10/100 chassis with 2 open slots for optional uplinks or stacking module. Chassis power and power over Ethernet are provided through internal power supplies. Maxmum of 210 watts of power avalable to power in-line 802.3af compliant devices. Backup power for the chassis and power over Ethernet provided by a separate external redundant power supply chassis. Advanced routing and/or authentication software is sold separately. Country-specic power cord required. OS6600 chassis w/SSL (DES,3DES,RC2,RC4). [ECCN 5A002]. 24 port 100BaseFX SFP chassis with two open slots for optional expansion modules and one slot in back for an optional redundant and hot swappable backup AC Power Supply. SFP ports accept industry standard 100Base-FX optical transceivers which are sold separately. Advanced routing and/or authentication software is sold separately. OS6602 chassis w/SSL (DES,3DES,RC2,RC4). [ECCN 5A002]. 24 port 10/100 chassis with 2 ports Gig SFP and 2 ports stacking built in and one slot in back for an optional redundant and hot swappable backup AC power supply. Advanced routing and/or Authentication software is sold separately. OS6602 chassis w/SSL (DES,3DES,RC2,RC4). [ECCN 5A002]. 48 port 10/100 chassis with 2 ports Gig SFP and 2 ports stacking built in and one slot in back for an optional redundant and hot swappable backup AC Power Supply. Advanced Routing and/or authentication software is sold separately. OmniSwitch 6600 chassis w/DES, 3DES, RC2 & RC4. [ECCN 5A002] 48 port 10/100 chassis with 2 open slots for optional uplinks or stacking module and one slot in back for an optional redundant and hot swappable backup AC power supply. Advanced routing and/or authentication software is sold separately. Country specic power cord required. Hot Swappable AC Backup Power Supply for the OmniSwitch 6600 series switch. Backup power supply is optional. Country specic power cord required Hot Swappable AC Backup Power Supply for the OmniSwitch 6602 series switch. Backup power supply is optional. Country specic power cord required. DC Backup Power Supply for the OmniSwitch 6602 series switch. Backup power supply is optional. Stacking Kit for the OmniSwitch 6600 switches, includes one 2 port stacking module and one 30cm in length stacking cable. Same stacking module as the OS6600-RST-KIT, but with a short cable. Redundant stacking kit for the OmniSwitch 6600 switches, includes one 2 port stacking module and one 1 meter in length stacking cable. Same stacking module as the OS6600STK-KIT, but with a longer cable.

OS6600-P24

OS6600-U24

OS6602-24

OS6602-48

OS6600-48

OS6600-BPS

OS6602-BPS

OS6602-BPS-DC

OS6600-STK-KIT

OS6600-RST-KIT
Alcatel OmniSwitch 6600 Series

OS6600-3M-KIT

Extended length stacking kit for the OmniSwitch 6600, includes one 2 port stacking module and one 3 meter in length stacking cable. Same stacking module as the OS6600STK-KIT, but with a longer cable. OSmeter stacking cable. Compatible with OS6602 series switches OScentimeter stacking cable. Compatible with OS6602 series switches OSmeter stacking cable. Compatible with OS6602 series switches 2 port Copper Gigabit Ethernet expansion module with 2 RJ-45 connectors. 2 port mini-GBIC universal Gigabit Ethernet expansion module. Requires mini-GBIC transceiver. 100BaseFM multimode 62.5/125 and 50/125 micron ber, supports distances up to 2km; uses LC connectors 100BaseFS single mode 9/125 nm ber, supports distances up to 15 km; uses LC connectors. 100BaseFS single mode 9/125 nm ber, supports distances up to 40 km; uses LC connectors. 100BaseFM multimode 62.5/125 and 50/125-micron ber, supports distances up to 2km; uses MTRJ connectors. OS6600 Advanced Routing Software. Includes support for OSPF. OS6600 Authenticated Software w/MD5. [ECCN 5D002] OmniSwitch 7000 Authentication Services software is for Authenticated VLANs and administrative access (user or user partitioned commands) utilizing a remote AAA server. Support is provided for standards-based RADIUS and standards-based LDAP v3 for authorization, authorization and accounting, and RSA ACE/Server direct for authentication based on one-time password tokens (SecurID). Authenticated SBR-MS sw w/MD5, RC4, MD4, DES. [ECCN 5D002] OmniSwitch 6600 Authentication Services software bundled with Funk Software's Steel-Belted Radius Enterprise Edition for Microsoft Windows. Authenticated SBR-Sun sw w/MD5, RC4, MD4, DES. [ECCN 5D002] OmniSwitch 6600 Authentication Services software bundled with Funk MiniGBIC Transceiver (SFP MSA) 1000Base-SX for Multimode ber MiniGBIC Transceiver (SFP MSA) 1000Base-LX for singlemode ber MiniGBIC Transceiver (SFP MSA) 1000Base-LH for singlemode ber
OS6600-CBL-1M OS6600-CBL-30CM OS6600-CBL-3M OS6600-GNI-C2 OS6600-GNI-U2

SFP-100-LC-MM

SFP-100-LC-SM15

SFP-100-LC-SM40

SFP-100-MTRJ-MM
OS6600-SW-AR OS6600-SW-AS

OS6600-SW-SBR-N

OS6600-SW-SBR-S
MiniGBIC-SX MiniGBIC-LX MiniGBIC-LH-70
www.alcatel.com/enterprise
Alcatel 26801 West Agoura Road Calabasas, CA 91301 USA Contact Center (800) 995-2612 US/Canada (818) 880-3500 Outside US www.alcatel.com/enterprise

Product specications contained in this document are subject to change without notice. Contact your local Alcatel representative for the most current information. Copyright 2004 Alcatel Internetworking, Inc. All rights reserved. This document may not be reproduced in whole or in part without the expressed written permission of Alcatel Internetworking, Inc. Alcatel and the Alcatel logo are registered trademarks of Alcatel. All other trademarks are the property of their respective owners. P/N 031228-04 Rev. B 09/04

5793320 56b3eb543dbc0 54397f0 53f0140 535c750 5340e52f3d52513e0 522fad0 522b370 51e7cc0 58b99e0 4fbd180 4fba330 4f926d0 4f70ac0 4e7cdb0 4e787f0 4e74000 4add0a0 4ada6e0 4ad7080 4acf630 499bba0 4898d60 46d39e0 46132e0 44b3b00 4b7e520 58fbbf67ec480 4ae03b0 5b38d50 590d420 5873ff0 72194a0 586e060 4f83f90 4f7b1c0 429ef90 429c5d0 42652e0 42611b0 4e45ae0 74f8e70

210 250

0% 0% 0% 0% 0% 0% 0% 0% 3% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 1% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 3% 0% 79% 93%
( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( (
80) 82) 0) 57) 70) 924) 164) 3) 6664) 152) 27) 0) 7) 15) 398) 19) 23) 24) 41) 1318) 804) 36) 3) 4) 2) 1) 2) 2) 28) 336) 3419) 371) 66) 0) 2) 0) 0) 455) 0) 0) 13) 86) 0) 0) 8) 0) 0) 0) 0) 0) 1) 41) 6051) 19) 154794) 193565)
0% 0% 0% 0% 0% 0% 0% 0% 26% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 9% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 16% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 23% 0% 12% 97%
0) 0) 0) 0) 0) 0) 0) 0) 17) 0) 0) 0) 0) 0) 0) 0) 0) 0) 0) 6) 0) 0) 0) 0) 0) 0) 0) 0) 0) 0) 11) 0) 0) 0) 0) 0) 0) 0) 0) 0) 0) 0) 0) 0) 0 0) 0) 0) 0) 0) 0) 0) 15) 0) 8) 65)

page 1-12

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.
Working: [Kernel]->i NAME ---------tExcTask tLogTask tShell tWdbTask IPC_tick tDrcIprm tOspf ENTRY TID PRI ------------ -------- --excTask logTask 753fshell 41b150520 73ae6aIPC_tick iprmMain 499bbaospfMain 4898dSTATUS PC SP ERRNO DELAY ---------- -------- -------- ------- ----PEND 17fd68 7544d40 3dPEND 17fd68 753f0 READY 15c0e0 41b09a0 PEND 158540 73ae0 READY PEND+T 158540 499b520 b 243 SUSPEND 158540 48986d0 b 299
value = 0 = 0x0 Working: [Kernel]->
In the above example, the OSPF task is suspended. Typically when a task is suspended, the system will automatically reboot and generate a system dump file. In the event that the system does not reboot, then try to gather the task trace and memory dump for that specific task using the following command:

The BOOTP REQ field shows that we havent waited long enough. (The seconds shown is 0, when it should be greater than or equal to 3.)
handle_uevent_udprelay_cmm(d): received on ipcp socket relayDebug handle_event_ipc_Ludprelay_cmm: num oef bytes received = v368elCMM =-1 handle_event_ni_udprelay_cmm: Recieved message from the NI handle_event_ni_udprelay_cmm: Recieved message from the NI for regular UDP pack
Finally, the Dshell command bootpSizeCheck turns on/off the bootpSizeCheck function. (By default it is off.) To turn it on enter the following:
Working: [Kernel]-> bootpSizeCheck = 1
To turn it on enter the following:
Working: [Kernel]-> bootpSixeCheck = 0
Note. OS-6600 supports minimum of 64 byte size packets.

page 5-7

page 5-8

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.
Introduction on page 6-1 Troubleshooting a DNS Failure on page 6-2 DNS Configuration Considerations on page 6-3
The primary function of Domain Name Service or DNS enables the user to enter a pre-configured name rather than an IP address to reach another host, via telnet, ftp, or ping. Once requested the switch contacts a DNS server to find out what IP address is mapped to the name. If the server finds the entry a response is sent to the switch indicating what IP address the name is associated with. The switch then attempts to execute the command to the IP address. You can set up to 3 DNS servers from the CLI, WebView, or through SNMP. If one server does not know the resolution the next server is queried to see if it knows the resolution. You can also configure a domain name that the switch can belong to. For example, say you want to set the domain name to Alcatel.com rather than entering
-> ping switch1.Alcatel.com

you could just enter

-> ping switch1
For all other domains you still need to enter the full syntax (ping switch2.xylan.com).

page 6-1

Troubleshooting a DNS Failure
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. If ping fails, verify IP configuration. If ping is successful, verify that UDP port 53 is not being filtered.

port 7/23 (gp=406)

ipni_rtlkup x.x.x.x
[Slot 9]->ipni_rtlkup "10.255.13.21" route 10.255.13.21 directly to vlan 3 value = 20 = 0x14

ipni_arp_count

[Slot 9]->ipni_arp_count ipni_arp_count: arp_count = 4 value = 4 = 0x4

ipni_arptimeoutdump

[Slot 9]->ipni_arptimeoutdump 10.255.13.35: if_index=13, vlan=3 tmo=300. 192.168.5.3: if_index=8, vlan=5 tmo=300. 192.168.10.3: if_index=9, vlan=10 tmo=300. 192.168.11.3: if_index=4, vlan=1 tmo=300. 192.168.55.3: if_index=14, vlan=55 tmo=300. value = 0 = 0x0

page 12-85

[Slot 9]->ipni_ifShow 10.0.0.1: if_index=37(vlan), vlan=2, flags=0x43, state=0x1 Netmask: 255.255.248.0 Broadcast address: 10.0.7.255 Ethernet Address: 00:d0:95:f6:f7:20 VRRP Ethernet Address: 00:00:00:00:00:00 Arp timeout is 300. Maximum Transfer Unit size is 1500 10.0.8.1: if_index=4(vlan), vlan=8, flags=0x43, state=0x1 Netmask: 255.255.248.0 Broadcast address: 10.0.15.255 Ethernet Address: 00:d0:95:f6:f7:20 VRRP Ethernet Address: 00:00:00:00:00:00 Arp timeout is 300. Maximum Transfer Unit size is 1500

ipni_routeCount

[Slot 9]->ipni_routeCount routes: 9 other: 1 value = 0 = 0x0 ecmps: 0 unique destinations: 9 arps: 8

page 12-86

13 Troubleshooting Virtual Router Redundancy Protocol (VRRP)
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

page 13-1

Overview
Troubleshooting Virtual Router Redundancy Protocol (VRRP)
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). This is a configurable item. A virtual router is defined by the VRID and a set of IP addresses. Thus a router may associate a virtual router with a real address on an interface as well as different addresses for the virtual router and the interface. The mapping between VRID and addresses must be coordinated among all VRRP routers on a LAN. It is allowed reuse the same VRID with a different address mapping on a different VLAN. Each Virtual Router is restricted to a single VLAN. Only the Master Router for each Virtual Router sends periodic VRRP Advertisements. A back-up router will not preempt a Master unless it has a higher priority. It is possible to preempt all preempt attempts. The only exception is when there is a VRRP router that has the virtual router as an interface address. In that case that router will always preempt. After election of the Master Router, the Master Router will send VRRP Advertisements. As long the Backup Router receives the VRRP Advertisements, it will only listen. The moment its not receiving VRRP advertisements for a configured amount of time, the Backup Router will announce itself as new Master Router in the VLAN. In case more then one Backup Router exist, the one with the second highest priority will become Master Router. It should be noted that while the VRRP router must reply to ARP messages for the IP/MAC address information it must not reply to echo request unless the virtual address is a real address on that switch. VRRP defines three possible types of authentication. Do not mistake this authentication for access to the network or its resources. This refers to whether or not a VRRP router will accept another VRRP routers messages. The 3 types are None, Simple Text Password, and IP security.

This shows a functional stream is now being sent to slot 5 port 15, and gives the multicast streams IP address(es). The expiry timer shows the number of seconds left before the particular stream times out on the slot/port if an IGMP message is not received. When the switch receives an IGMP message it will reset the timer to 260 seconds; this process repeats until the station leaves the stream, or the stream itself fails for some reason. If your device cannot join a stream, you will not see it in the list. The next step to take is to repeat the show ip multicast groups command on the next switch in line between the end station and the stream source until you find out where the stream fails. You will find a point where a stream exists on one switch, but not on the next one in line to the destination. The task then becomes configuring those units to properly pass IP Multicast traffic (see the Configuring IP Multicast chapter in the appropriate OmniSwitch Network Configuration Guide.

page 14-2

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. First, does the device lose the stream when the Expiry timer reaches zero in the show ip multicast groups command?
-> show ip multicast groups Destination IP Source IP VLAN Slot/Port Expire --------------------+--------------------+----+---------+-----224.0.0.9 10.10.10.5/224.0.1.22 10.10.10.5/224.0.1.24 10.10.10.5/224.77.1.0 10.10.10.5/224.77.205.58 10.10.10.5/239.255.255.250 10.10.10.5/239.255.255.254 10.10.10.5/239.255.255.254 10.10.10.5/23 260
Once this timer reaches zero, the switch will stop sending the multicast stream to this port, as it believes there are no longer any devices requesting it. This could happen if in the VLAN where the device connects, an IP multicast router does not exist. The multicast client will send IGMP messages on layer 3, and if the VLAN has no L3 instance, there is no way for it to listen to those messages. It is then recommended to have at least one IP multicast router configured and enabled on the VLAN. Issue a show vlan command to check the configuration of the VLAN. For example:
-> show vlan 1 Name : Administrative State: Operational State : Spanning Tree State : Authentication : IP Router Port : IPX Router Port : VLAN 1, enabled, disabled, enabled, disabled, none, none
Assign the VLAN an IP address that is proper for your network:
-> vlan 1 router ip 10.10.10.7 mask 255.255.255.0
Then reissue the show vlan command to verify:
-> show vlan 1 Name : Administrative State: Operational State : Spanning Tree State : Authentication : IP Router Port : IPX Router Port : VLAN 1, enabled, disabled, enabled, disabled, 10.10.10.7 none

255.255.255.0

forward
Now that an IP address has been assigned, recheck the show ip multicast groups command and verify that the slot/port in question has an entry. You should see the timer decrement and reset as described above.

-> show ip multicast forwarding Source Destination Multicast Group Source IP Type VLAN Slot/Port Type VLAN Slot/Port -------------------+-------------------+----+----+---------+----+----+--------224.77.1.0 10.10.10.68 NATV 1 5/13 NATV 1 5/15 224.77.205.58 10.10.10.68 NATV 1 5/13 NATV 1 5/15
Is your switch set up so that there are policies preventing multicast traffic from entering or leaving a particular VLAN? Use the show ip multicast policy-cache command to check:
-> show ip multicast policy-cache Policy Group Address Src Address Vlan Port Disp Time -------+----------------+----------------+------+------+------+-----MBR 224.0.0.9 10.10.10.5/23 ACPT 133 MBR 224.0.1.22 10.10.10.5/23 ACPT 132 MBR 224.0.1.24 10.10.10.5/23 ACPT 136 MBR 224.77.0.0 10.10.10.5/13 ACPT 138 MBR 224.77.1.0 10.10.10.5/15 ACPT 259 MBR 224.77.205.58 10.10.10.5/15 ACPT 258 MBR 239.255.255.250 10.10.10.5/23 ACPT 137 MBR 239.255.255.250 10.10.10.5/23 ACPT 258 MBR 239.255.255.254 10.10.10.5/23 ACPT 259
The DISP column should display ACPT for Accept. IPMS follows the IGMP V2 specification, which means that the queriers are elected based on the switch/ router with the lowest IP address. During startup, all switches will be listed because they all send initial IGMP queries. After the official querier is elected, the other switches will stop flooding IGMP queries of their own. Eventually, only one querier in the network will remain, and will be the only one listed in the show ip multicast queriers command for all switches in the VLAN. The querier periodically sends a Membership Query message to the all-systems group (224.0.0.1). The hosts then respond with a host membership report message to the group address for the stream(s) they want to receive. The querier receives the message, and adds the group to its membership list.
-> show ip multicast queriers Source IP VLAN Slot/Port Expire Type --------------------+----+---------+------+------10.10.10.5/Dynamic
Type of Dynamic means that the IP address was learned via IGMP messages, so the address should be alive and functioning; it is worth verifying that you can ping the addresses along your path, however.

page 14-5

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 isnt on an IP VLAN. This is probably due to a querying problem. IPMS cannot send IGMP queries on a VLAN that doesnt have an IP address, but you can still have another switch in the same VLAN that is configured for IP and is querying. In this case, things will work because there is still a querier present, even if it is not a local switch. Remember that queriers are required for the re-solicitation of IGMP clients. Queries are sent every 120 seconds, to which all clients must respond with a membership report. Also check the flood limits (show interfaces flood rate) to see if the switch is dropping packets due to them being over the limit: You want to see Flood only in an IPMS environment. If you see:

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-Lucents OmniSwitch provides useful commands for narrowing down the problem. One of the most useful commands used in troubleshooting SLB problems on the OmniSwitch product line is the show ip slb clusters command. For example:
As shown in the example above, this command will provide pertinent information in verifying which server cluster(s) are inaccessible or malfunctioning. After you have determined which SLB cluster is not accessible, performing the show ip slb cluster cluster-name command will provide more detailed information on the configuration and status of the above named SLB cluster. The show active policy rule and show policy condition commands are also useful when troubleshooting SLB problems:
-> show active policy rule Policy SLB-rule-FTP ( L3): -> show policy condition Condition Name SLB-cond-FTP *IP : From Prec Enab Act Refl Log Save api 65000 Yes Yes No No Yes SLB-cond-FTP -> SLB-act-FTP Matches 7

From api

Src -> Dest Any -> 172.160.1.100

page 17-5

page 17-6
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.
Introduction on page 18-1 Troubleshooting AVLAN on page 18-2 Useful Notes on Client Issues on page 18-5 Troubleshooting Using Debug Systrace on page 18-5 Dshell Troubleshooting on page 18-12 Troubleshooting AVLAN on OmniSwitch 6850/9000 Series on page 18-16
The main function of Authenticated VLAN is to control user access to network resources based on VLAN assignment and user login process. This process is sometimes called user authentication or Layer 2 Authentication. The term Authenticated VLANs (AVLANs) and Layer 2 Authenticaion are synonymous. Note. This document does not discuss the basic operation of the AVLAN. To learn about how AVLAN works, refer to the Managing Authentication Servers and the Configuring Authenticated VLANs chapters in the appropriate OmniSwitch Network Configuration Guide.

page 18-1

Troubleshooting AVLAN
Troubleshooting Authenticated VLANs

-> show aaa server Server name = radA Server type IP Address 1 Retry number Time out (sec) Authentication port Accounting port =
= RADIUS, = 192.168.10.100, = 3, = 2, = 1812 1813
Make sure the authentication port set on the switch matches the RADIUS server. Make sure a physical connection is established between the switch and the RADIUS server. Also, check if the auth-ip is configured on the switch. For example:
-> show aaa avlan auth-ip Vlan number Authenticated Ip Address ---------------+------------------------

page 18-17

192.168.1.253 192.168.50.253
If the client is able to reach the authentication page but still receives a wrong username or password message, than check if the RADIUS server is configured with the proper username and password. Make sure the authentication type is both configured properly on the client and the server. For example, if MD5 is the authentication type set on the client, then the RADIUS server must allow MD5. If you notice the client sends out a RADIUS request but is constantly rejected, check the server log to find out the reason. A set of AVLAN debug systrace and Dshell commands is also available. These commands are identical to those available on the 6800, 7000 and 8000 AOS series. For more information on the proper usage, please refer to Troubleshooting Using Debug Systrace on page 18-5 and Dshell Troubleshooting on page 18-12. Note: that to use the adHelp command on the AOS 9000 Series, you must first telnet to the specific NI before executing the command. For example:
-> telnet 127.2. [slot number].1
Useful Notes and Guidelines
Window Vista client must have User Access Control disabled to allow IP release/renew. New Window Vista's TCP auto-tuning feature will cause slow authentication process. IE 7 client must manually install the AVLAN certificate to get a proper login page to display. Disable pop up blocker on Safari 3 to allow the IP release/renew page to come up. If using telnet authentication, a manual IP release and renew is required to get the new IP after authen-

tication.

page 18-18

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 on page 19-2 Troubleshooting Using Debug CLI on page 19-4 Dshell Troubleshooting on page 19-7 Troubleshooting 802.1x on OmniSwitch 6850/9000 Series on page 19-10 Dshell Troubleshooting 802.1x on OmniSwitch 6850/9000 Series on page 19-14

September 2005

page 19-1
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.1x authentication.
Layer-2: show vlan port mobile cfg ignore port mobile def authent enabled restore bpdu -------+--------+----+--------+---------+---------+------2/1 on 1 on-avlan on on on 2/2 on 1 on-avlan on on on 2/3 on 1 on-8021x on on on 2/4 on 1 on-8021x on on on
3 Check the physical status and VLAN assignment of the port.
Layer-2: show vlan port 2/3 vlan type status --------+---------+-------------1 default forwarding 101 mobile forwarding
4 Check the status of the MAC address table on the 802.1x port.
Layer-2: show mac-address-table 2/3 Legend: Mac Address: * = address not valid Vlan Mac Address Type Protocol Operation Interface ------+-------------------+--------------+-----------+------------+----------101 00:0f:1f:d5:54:95 learned 10800 bridging 2/3 Total number of Valid MAC addresses above = 1
5 If a user can not move to VLAN-X after authentication, it could mean that authentication is disabled on
that VLAN, or that the Radius server didn't return a specific VLAN number in the return list attribute. Please verify that the server is configured properly with the correct return list attribute type as explained in the user guide. To move a user into a specific VLAN, Radius server has to return the attribute "AlcatelAuth-Group" with a valid Authenticated VLAN number.

Troubleshooting 802.1x on OmniSwitch 6850/9000 Series
Troubleshooting 802.1x on OmniSwitch 6850/ 9000 Series
1 Verify that the port is configured for 802.1x authentication.
-> show vlan port mobile cfg ignore ingress port mobile def authent enabled restore bpdu filtering -------+--------+----+--------+---------+---------+-------+---------2/37 on 1 on-8021x on on off off 2/38 on 1 on-8021x on on off off 2/39 on 1 on-8021x on on off off 2/40 on 1 on-8021x on on off off 2/41 on 1 on-8021x on on off off 2/42 on 1 on-8021x on on off off 2/43 on 1 on-8021x on on off off 2/44 on 1 on-8021x on on off off 2/45 on 1 on-8021x on on off off 2/46 on 1 on-8021x on on off off 2/47 on 1 on-8021x on on off off 2/48 on 1 on-8021x on on off off
2 Check the physical status and VLAN assignment of the port.
-> show vlan port 2/37 vlan type status --------+---------+-------------1 default forwarding 2 mobile forwarding
3 Check the status of the MAC address table on the 802.1x port.
-> show mac-address-table 2/37 Legend: Mac Address: * = address not valid Vlan Mac Address Type Protocol Operation Interface ------+-------------------+--------------+-----------+------------+----------1 00:15:c5:1f:16:0e learned 800 bridging 2/37 Total number of Valid MAC addresses above = 1
4 If a user can not move to VLAN-X after authentication, it could mean that authentication is disabled on
that VLAN or that the RADIUS server didn't return a specific VLAN number in the return list attribute. Please verify that the server is configured properly with the correct return list attribute type as explained in the user guide. To move a user into a specific VLAN, RADIUS server has to return the attribute "AlcatelAuth-Group" with a valid Authenticated VLAN number.
-> show vlan 1 Name : VLAN 1, Administrative State: enabled, Operational State : disabled, 1x1 Spanning Tree State : enabled,

page 19-10

Flat Spanning Tree State : enabled, Authentication : enabled, IP Router Port : on, IPX Router Port : none, Mobile Tag : off
Verify the status of the 802.1x port using the show 802.1x (show 802.1x slot/port can also be used to verify the status of a specific 802.1x port) command.
-> show 802.1x 802.1x configuration for slot 2 port 37: direction = both, operational directions = both, port-control = auto, quiet-period (seconds) = 60, tx-period (seconds) = 30, supp-timeout (seconds) = 30, server-timeout (seconds) = 30, max-req = 2, re-authperiod (seconds) = 3600, reauthentication = no, Supplicant polling retry count = 2

Multicast Vector Table

Indicates multicast domain membership for fabric ports. On fabric ingress, frames are put into a given fabric ports multicast FIFO based on this vector.

IPC Mapping

On ingress, Coronado IPC QIDs are identified based on agreed upon values (for Roma the values are selected from offsets 12 through 15). On egress, an internal Roma table maps IPC QIDs to fabric ports (one-to-one).

page -23

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). In order to support basic system operation, the Roma driver must maintain the correct destination port mapping on the Roma ASIC chips, including any required multicast and IPC port mapping; appropriate internal flow control thresholds should be maintained as well. These form a small but significant part of the initialization process and the Roma driver needs to adapt in case of changes to NI slot configuration. However, the high level sequencing and selection of Roma Driver activity is mostly a function of a set of external events, most of which can be termed hot swap events. The following 10 scenarios represent high-level states for the Roma Driver which correspond to its handling of some kind of major.

Initialization

This state is entered when the Roma Driver is first spawned as a task on the primary CMM. Early on, the fabric slot and NI slot configuration must be completely determined to effectively program the Roma ASICs. An overview of the ASIC setup follows:
Bit Slice oriented setup - includes programming chip IDs and master chip selection. Fabric Port setup - includes calendar, flow control, and multicast vector setup Synchronizing Roma chips - includes starting primary cycle and timer resets Manual link acquisition - verify that all links are up, includes retries Automatic HW recovery mechanism setup - includes link acquisition and hot swap During switch operation, this is the state that the Roma Driver will be in the vast majority of the time.
Remaining in this state implies there are no changes to: physical Fabric slot configuration, NI slot configuration, the primary CMM slot, or detected framing errors. Processing in this state consists of an infinite loop where the following tasks are performed:

supported message types

error flash graft igmp ipmrm init mip misc
probes prunes routes time tm
parameter message_type default error
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., 1255). 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., ip dvmrp debug-type all or no ip dvmrp debug-type all).
-> -> -> -> ip ip no no dvmrp debug-type all dvmrp debug-type tm igmp flash ip dvmrp debug-type misc ip dvmrp debug-type all
ip dvmrp debug-level show ip dvmrp debug Defines the level of debugging for DVMRP protocol on the switch. Displays the current level of debugging for DVMRP protocol, as well as the current DVMRP debugging status for all message types.
ALADVMRPDEBUGCONFIG alaDvmrpDebugAll alaDvmrpDebugError alaDvmrpDebugFlash alaDvmrpDebugGrafts alaDvmrpDebugIgmp alaDvmrpDebugInit alaDvmrpDebugIpmrm alaDvmrpDebugMip alaDvmrpDebugNbr alaDvmrpDebugProbes alaDvmrpDebugPrunes alaDvmrpDebugRoutes alaDvmrpDebugTime alaDvmrpDebugTm

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
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.
-> show ip dvmrp debug Debug Level Error Flash Grafts IGMP IPMRM Init MIP Misc Nbr Probes Prunes Routes Time TM = = = = = = = = = = = = = = = 1, on, off, off, off, off, off, off, off on, off, off, on, off, off,
output definitions Debug Level error Flash The current debug level value. For information on setting this parameter, see the ip dvmrp debug-level command on page B-8. The current debugging status for DVMRP Error messages. Options include on or off. The current debugging status for DVMRP Flash processing. Options include on or off.
output definitions (continued) Grafts IGMP IPMRM Init MIP The current debugging status for DVMRP Graft processing. Options include on or off. The current debugging status for DVMRP Internet Group Management Protocol (IGMP) packet processing. Options include on or off. The current debugging status for DVMRP IP Multicast Routing Manager (IPMRM) interaction. Options include on or off. The current debugging status for DVMRP Initialization. Options include on or off. The current debugging status for DVMRP MIP (Management Internal Protocol) processing. Includes CLI and SNMP. Options include on or off. The current status of miscellaneous DVMRP debugging. Options include on or off. The current debugging status for DVMRP Neighbor processing. Options include on or off. The current debugging status for DVMRP Probe processing. Options include on or off. The current debugging status for DVMRP Prune processing. Options include on or off. The current debugging status for DVMRP Route processing. Options include on or off. The current debugging status for DVMRP Timer processing. Options include on or off. The current debugging status for DVMRP Task Manager interaction. Options include on or off.

RIP must be enabled on the switch with the ip rip status CLI command before you can configure the

debug level.

The debug level applies to all debug types that are configured. You cannot set different levels for each
When the debug level is set to 0, the log is turned off.
-> ip rip debug-level 3
ip rip debug-type show ip rip debug Configures the type of RIP messages to debug. Displays the current RIP debug levels and types.
alaRipLogTable alaRipDebugLevel

show ip rip debug

Displays the current RIP debug levels and types. show ip rip debug
-> 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 Types/Selections Debug level. The valid range 0255. The default level is 0. The status of each debug type is shown here (on/off). See page B-34 for a description of debug types.
ip rip debug-level ip rip debug-type Configures RIP debugging level. Configures the type of RIP messages to debug.

dispDrcRipDebug

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
slot The slot number of the Network Interface (NI) module.
The debug slot information command combines the functions of the debug interfaces backpressure, show interfaces counters, debug interfaces led, debug interfaces mdix, debug ipc pools slot, debug interfaces phy, debug interfaces mac, and debug interfaces port structure commands.
-> debug slot information 1 ######################################### debug interfaces 1 backpressure ######################################### Slot Backpressure ------+-------------1 disable ######################################### show interfaces 1 counters ######################################### 1/16, InOctets = 258342824, OutOctets InUcastPkts = 1198288, OutUcastPkts InMcastPkts = 132887, OutMcastPkts InBcastPkts = 639052, OutBcastPkts InPauseFrames = 0, OutPauseFrames 1/18, InOctets = 24973594, OutOctets InUcastPkts = 316757, OutUcastPkts InMcastPkts = 354, OutMcastPkts InBcastPkts = 2172, OutBcastPkts InPauseFrames = 0, OutPauseFrames 1/20, InOctets = 1504323, OutOctets InUcastPkts = 9547, OutUcastPkts InMcastPkts = 1333, OutMcastPkts InBcastPkts = 196, OutBcastPkts
241185604, 628318, 99632, 2488, 0 102309903, 481006, 134096, 639437, 0 77527634, 172421, 133117, 641403,

page -39

InPauseFrames =

OutPauseFrames =

######################################### 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/21 normal OFF 1/22 normal OFF 1/23 normal OFF 1/24 normal OFF ######################################### debug interfaces 1 mdix ######################################### 1/1 disable enable 1/2 disable enable 1/3 disable enable 1/4 disable enable 1/5 disable enable 1/6 disable enable 1/7 disable enable 1/8 enable enable 1/9 disable enable 1/10 disable enable 1/11 disable enable 1/12 disable enable 1/13 disable enable 1/14 disable enable 1/15 disable enable 1/16 disable enable 1/17 disable enable 1/18 disable enable 1/19 disable enable 1/20 enable enable 1/21 disable enable 1/22 disable enable 1/23 disable enable 1/24 enable enable

inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive forwarding forwarding forwarding forwarding forwarding forwarding forwarding

page -160

40000002
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 blocking blocking blocking blocking blocking blocking blocking blocking blocking blocking blocking blocking blocking

page -161

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 protocol-map

page -162

debug vlan rule ports
Displays all the ports available and can be a candidate for VLAN rules. debug vlan rule ports
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.
-> debug vlan rule ports port candidate mobile -----+-----------+--------1/1 1/2 2/1 2/2 2/3 + 2/4 + 2/5 + 2/6 2/7 2/8 + 2/9 + 2/10 + 2/11 2/12 4/1 4/2 6/1 6/2 7/1 7/2 8/1 + 8/2 + 8/3 + 8/4 + 8/5 + 8/6 + 8/7 + -

page -163

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
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
+ + + + + + + + + + + + + + + +

page -165

debug vlan rule database
Displays the rules configured on the switch for Group Mobility. debug vlan rule database