Installation and Configuration for the Avaya C360 Converged Stackable Switches Software Version 4.
© 2006 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document may be incorporated in future releases. For full legal page information, please see the complete document, Avaya Legal Page for Hardware Documentation, Document number 03-600759.
Contents Before you Install the Avaya C360 . . . . . . . . . . . . . . . . . . . . . 13 Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Conventions Used in the Documentation . . . . . . . . . . . . . . . . . . . . . . CLI Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notes, Cautions, and Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . 14 14 15 Section 1: Avaya C360 Overview . . . . . . . . . . . . . . . . . . .
Contents Inter-Connecting Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . To connect stacked switches: . . . . . . . . . . . . . . . . . . . . . . . . 42 42 Making Connections to Network Equipment. . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connecting Cables to Network Equipment . . . . . . . . . . . . . . . . . . . 44 44 44 Installing SFP GBIC Transceivers . . . . . . . . . . . Safety Information . . .
Contents Connecting a Modem to the Console Port . . . . . . . . . . . . . . . . . . . . SNMP Support . . . . . . . . . . . . . . Introduction to SNMP . . . . . . . . SNMP Versions. . . . . . . . . . Managers and Agents . . . . . . Manager/Agent Communication SNMPv1. . . . . . . . . . . . . . . . SNMPv2c . . . . . . . . . . . . . . . SNMPv3. . . . . . . . . . . . . . . . Users . . . . . . . . . . . . . . . Groups . . . . . . . . . . . . . . Views . . . . . . . . . . . . . . . SNMP Commands . . . . . . . . .
Contents Uploading and Downloading Device Configurations and Images . . . . . . . . . Layer 2 Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Layer 3 Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 100 101 SCP Protocol Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 System Logging . . . . . . . . . . System Logging Introduction . System Logging Messages Sinks . . . . . . . . . . . . Message Facilities . . . . .
Contents 802.1x CLI Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Spanning Tree Protocol . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . Spanning Tree Protocol . . . . . . . . . . . Spanning Tree per Port . . . . . . . . . . . Rapid Spanning Tree Protocol (RSTP) . . . About the 802.1w Standard . . . . . . . Port Roles . . . . . . . . . . . . . . . . Spanning Tree Implementation in the C360 Spanning Tree Protocol CLI Commands . . . . . . . . . . .
Contents Weighted Queuing CLI Commands . . . . . . . . . . . . . . . . . . . . . . . . LLDP Agent . . . . . . . . . . . LLDP Agent Overview . . . . Supported TLVs . . . . . Configuring the LLDP Agent LLDP Agent CLI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 146 147 148 149 Chapter 9: Avaya C360 Layer 3 Features . . . . . . . . . . . . . . . . . 151 Obtaining and Activating a License Key . Obtaining a Routing License Key. . . Activating a Routing License Key . .
Contents DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DHCP/BOOTP Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BOOTP/DHCP CLI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . 175 175 176 NetBIOS Re-broadcast Configuration . . . . . . . . . . . . . . . . . . . . . . . . NetBIOS Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NetBIOS Re-broadcast Configuration CLI Commands . . . . . . . . . . . . .
Contents Installing the Java Plug-in. . . . . . . . . . . . . . . . . . . . Installing from the C360 Documentation and Utilities CD Install from the Avaya Web Site . . . . . . . . . . . . . . Install from your Local Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 197 197 197 Installing the On-Line Help and Java Plug-In on your Web Site . . . . . . . . . . 198 Documentation. . . . . . . . . . . . . . . . . . . .
Contents Appendix C: Standards and Compatibility. . . . . . . . . . . . . . . . . Avaya C360 Standards Supported IEEE. . . . . . . . . . . . . . . IETF - Layer 2 . . . . . . . . . IETF - Layer 3 . . . . . . . . . . . . . 221 221 221 222 IETF - Network Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Appendix D: Specifications . . . . . . . . . . . . . . . . . . . . . . . . . 225 Physical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 12 Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.
Before you Install the Avaya C360 Safety Information ! WARNING: ONLY TRAINED AND QUALIFIED PERSONNEL SHOULD BE ALLOWED TO INSTALL OR REPLACE THIS EQUIPMENT. ! ADVERTENCIA: SOLAMENTE PERSONAL CALIFICADO Y ENTRENADO DEBE INSTALAR O REEMPLAZAR ESTE EQUIPO. ! WARNING: EQUIPMENT MUST BE CONNECTED TO AN EARTHED MAINS SOCKET-OUTLET. ! ADVERTENCIA: El equipo se debe conectar a una toma de tierra principal.
Before you Install the Avaya C360 ! ADVERTENCIA: ADVERTENCIA: Los ventiladores están encendidos siempre que el equipo esté conectado al suministro eléctrico. Conventions Used in the Documentation Documentation for this product uses the following conventions to convey instructions and information: CLI Conventions ● Mandatory keywords are in the computer bold font. ● Information displayed on screen is displayed in computer font. ● Variables that you supply are in pointed brackets < >.
Conventions Used in the Documentation Notes, Cautions, and Warnings ! CAUTION: You should take care. You could do something that may damage equipment or result in loss of data. CAUTION: ! PRECAUCIÓN: Debe tener cuidado. Usted podría hacer algo que puede dañar el equipo o resultar en pérdida de datos. PRECAUCION: ! WARNING: This means danger. Failure to follow the instructions or warnings may result in bodily injury.
Before you Install the Avaya C360 16 Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.
Section 1: Avaya C360 Overview Issue 1 July 2006 17
Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.
Chapter 1: Avaya C360 Overview The C360 is a line of converged stackable switches that provide high availability, quality of service (QoS), and IEEE 802.3af Power over Ethernet (PoE) to enhance converged network infrastructure operations. With a range of PoE and non-PoE configurations, the C360 series is a powerful, yet cost-effective option for enterprise applications.
Avaya C360 Overview ● When the switches are stacked, the switches elect one switch as the master, while the other switches act as slaves. The master switch acts as the stack management agent reporting to the management system. ● Management redundancy - if the master unit fails, the remaining switches elect a new switch as the master, and the original stack configuration and IP address are maintained. ● You can add, remove and replace switches in the stack without disrupting operation.
C360 Features and Benefits - Up to two simultaneous encrypted SSH (Secure Shell) connections for multiple CLI-based sessions over the network. Refer to Establishing an SSH Connection on page 66 for further information. - SNMP (Simple Network Management Protocol) "get" and "set" requests (support for SNMPv1, SNMPv2 and SNMPv3). Refer to SNMP Support on page 73 for further information.
Avaya C360 Overview ● Stack redundancy - in the unlikely event that a C360 switch or Octaplane link should fail, stack integrity is maintained if the redundant cable is connected to the stack. The broken link is bypassed and data transmission continues uninterrupted. ● BUPS (Backup Power Supply) - you can connect an additional DC power supply to the BUPS connectors to ensure no disruption if the internal PSU fails. Refer to Connecting a BUPS on page 53 for further information.
C360 Features and Benefits ● Remote Authentication Dial-In User Service (RADIUS) provides flexible administrative control over authentication and authorization processes. Refer to RADIUS on page 80 for further information. ● SNMP v3 adds security features to the SNMP v1 and SNMP v2c feature set. Refer to SNMPv3 on page 75 for further information. ● SSH enables establishing a remote session over a secured tunnel, also called a remote shell.
Avaya C360 Overview ● Port classification to regular/valuable so in case of link failure notification is generated for valuable ports only. Refer to Port Classification on page 139 for further information.
C360 Features and Benefits ● IP routing between VLANs (inter-VLAN routing) for full Layer 3 switching between two or more VLANs, allowing each VLAN to maintain its own autonomous data-link domain ● Address Resolution Protocol (ARP) for identifying a switch through its IP address and its corresponding Media Access Control (MAC) address. Refer to ARP (Address Resolution Protocol) Table Configuration on page 172 for further information.
Avaya C360 Overview ● You can manage the switch from an SNMP-compatible management station that is running platform such as HP OpenView. The switch supports a comprehensive set of MIB extensions and four RMON groups. ● Avaya IM (Integrated Management) network management provides further control and allows you to manage other Avaya equipment in your network. It provides the ease-of-use and features necessary for optimal network utilization.
Section 2: Installing the C360 Issue 1 July 2006 27
Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.
Chapter 2: Avaya C360 Front and Rear Panels This chapter describes the front and rear panels of the C360 switches, including the LEDs, buttons and power inlets: ● C360 Front Panels ● C360 Rear Panel C360 Front Panels The front panel contains LEDs, controls, and connectors. The status LEDs and control buttons provide at-a-glance information. The front panel LEDs consist of Port LEDs and Function LEDs. The Port LEDs display information for each port according to the illuminated function LED.
Avaya C360 Front and Rear Panels Figure 2: C363T-PWR Front Panel Figure 3: C364T and C364T NEBS Front Panel Figure 4: C364T-PWR Front Panel Figure 5: C360 Function LEDs 1 2 3 Figure notes: 1. PoE LED on C360-PWR only 2. Left front panel button 3. Right front panel button 30 Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.
C360 Front Panels Figure 6: Order of Function 'Parameters Selected with the Left/Right Front Panel Buttons Starting Point (after Power-up or Reset) Right Button Left Button LNK 1 PoE COL LAG Tx Hspd Rx FDX Figure notes: 1.
Avaya C360 Front and Rear Panels Table 3: C360 Function LED Descriptions 2 of 3 LED Name Description LED Status The following Function LEDs apply to all ports LNK Port Status OFF - Port is disabled ON - Link is OK Blinking - Port is enabled, but Link is down COL Collision OFF - No collision or full-duplex port for ports 1 to 24/48; always OFF for ports 51 to 52. ON - Collision occurred on line.
C360 Rear Panel Table 3: C360 Function LED Descriptions 3 of 3 LED Name Description LED Status PoE* Power over Ethernet. OFF - PoE disabled for this port ON - PoE is enabled and power is being supplied to an end-station Blinking: ● PoE enabled, but no powered device is detected, or ● Power supply error, or ● Not enough power 3 of 3 *C360-PWR only Tip: Tip: All LEDs light during a reset. Table 4: C360 Right and Left Select buttons On order to... Press...
Avaya C360 Front and Rear Panels Figure 7: C360 Rear Panel 1 2 3 Figure notes: 1. AC Input 2. BUPS DC Input 3. X360STK slot (shown covered) 34 Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.
Chapter 3: Installation The C360 switch is ready to work after you complete the installation instructions described in this chapter.
Installation Site Preparation You can mount the C360 alone or in a stack in a standard 19-inch equipment rack located in a wiring closet or equipment room. You can build a logical stack of up to ten C360 switches.
Rack Mounting (Optional) ● The power source matches the specifications shown in Table 7: Table 7: Power Requirements AC Input voltage Power consumption ● C363T ● C363T-PWR ● C364T ● C364T (NEBS) ● C364T-PWR AC Input current ● C363T ● C363T-PWR ● C364T ● C364T (NEBS) ● C364T-PWR 100 to 240 VAC, 50 to 60 Hz ● ● ● ● ● ● ● ● ● ● 60 W 420 W 90 W 90 W 760 W 1.3 A 4.2 A 1.3 A 1.3 A 7.
Installation Figure 8: Front and Mid-Mount Positions 7.9" 1 (200 mm) 2 3 Front Figure notes: 1. Equipment rack 2. Mid-mount position 3. Front mount position Before you Install the C360 in a Rack ● When installing C360 in a rack, ensure that the equipment is positioned such that it will not cause the rack to become unstable or tip over.
Rack Mounting (Optional) Figure 9: C360 Rack Mounting (except C364T NEBS) 2 1 Figure notes: 1. Front mount position 2. Mid-mount position Figure 10: C360 Rack Mounting - Front Mount (C364T NEBS only) Figure 11: C360 Rack Mounting - Mid Mount (C364T NEBS only) 2. Firmly attach the brackets to the chassis with the screws provided.
Installation - Use four screws to attach each bracket to the switch for non-NEBS switches. - Use eight screws to attach each bracket to the switch for the C364T NEBS switch. 3. Position the switch in the rack. 4. Fasten the switch in the rack with the screws provided. Wall Mounting (Optional) Note: Note: Do not mount the C364T NEBS on a wall. You can fix the C360 to the wall as follows: ! CAUTION: CAUTION: Ensure that the wall and screws can support the weight of the C360 and any installed modules.
Stacking (optional) ! CAUTION: Ensure that ventilation holes are not obstructed. CAUTION: Stacking (optional) There are two main steps for creating stacks: 1. Installing the X360STK Stacking Module 2. Inter-Connecting Switches Installing the X360STK Stacking Module ! CAUTION: C360 switches and stacking modules contain components sensitive to electrostatic discharge. Touching the circuit boards unless instructed to do so may damage them.
Installation 4. Tighten the two screws on the side panel of the stacking module by turning the knurled knobs clockwise. Inter-Connecting Switches Tip: You may stack the C360 with the G700, P333T-PWR, P332G-ML or P332GT-ML. Please refer to Appendix A: Mixed Stacks for further information on mixed stacks. Tip: Note: The two ends of the Octaplane cable terminate with different connectors. Each connector can only be connected to its matching port.
Stacking (optional) 4. If you wish to implement stack redundancy, use the Redundant Cable to connect the port marked “to lower unit" on the bottom switch to the port marked “to upper unit"" on the top switch of the stack. 5. Power up the added modules. ! CAUTION: CAUTION: Do not cross connect two switches with two Octaplane (light-colored) cables. If you wish to cross-connect for redundancy, use one light-colored Octaplane cable and one black redundancy cable.
Installation Figure 14: Plug for Unused Stacking Ports Making Connections to Network Equipment This section describes the physical connections that you can make between the C360 switch and other network equipment.
Installing SFP GBIC Transceivers 2. For all other ports, connect an Ethernet copper cable (not supplied) directly to the ports. The copper ports can operate with 2 pair (4 wire) or 4 pair (8 wire) CAT 5 Ethernet cables (crossed or straight). The maximum cable length is 100 m (328 ft.). 3. Connect the other end of the cable to the Ethernet port of the PC, server, router, workstation, switch, hub, or other end device. 4. Check that the appropriate link (LNK) LED lights up.
Installation Installing and Removing a SFP GBIC Transceiver The SFP GBIC transceiver is fastened using a snap-in clip. To install the SFP GBIC transceiver: ● Insert the transceiver (take care to insert it the right way up) until it clicks in place. ● Refer to Copper GBIC Transceiver Installation Notes on page 47 if you are installing a copper GBIC transceiver. To remove the SFP GBIC transceiver: 1. Press the clip on the base of the transceiver see Figure 15 for the location.
Installing SFP GBIC Transceivers Table 8: Gigabit Fiber Optic Cabling 2 of 2 Gigabit Interface Fiber Type Diameter (µm) Modal Bandwidth (MhzKm) 1000BASE-LX SM 9 N/A 10,000 2 1,310 1000BASE-ELX SM 9 N/A 70,000 10,000 1,550 Maximum Distance (m) Minimum Distance (m) Wavelength (nm) 2 of 2 Copper GBIC Transceiver Installation Notes Before installing a copper SFP transceiver, ensure that auto-negotiation is enabled for the transceiver ports.
Installation 48 Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.
Chapter 4: Powering Up the Avaya C360 This chapter describes the procedures for powering up C360 switches. Connecting the C360 to the main electrical supply provides power to the switch and for Power over Ethernet (PoE). ! WARNING: To isolate the switch completely, you must disconnect all power connections (AC plug, DC power and DC BUPS power).
Powering Up the Avaya C360 Connecting to an AC Power Supply AC Power Cable The C360 switch is supplied with a North American power cordset. Below are guidelines that should be used when obtaining and/or defining a different cordset to be used with the C360.
Connecting to a DC Power Source (C364T NEBS Only) Connecting to a DC Power Source (C364T NEBS Only) The C364T NEBS is rated -36 to -60 VDC, 2A. ! CAUTION: A UL-Listed and CSA-Certified branch circuit protective device of up to 20A must be provided in the building DC mains wiring installation for branch circuit protection. CAUTION: ! CAUTION: Always connect the ground wire first and disconnect it last. CAUTION: Figure 17: Avaya C360 DC Input Terminal Block 2 1 3 Figure notes: 1.
Powering Up the Avaya C360 2. Positive to positive 3. Negative to negative ! WARNING: WARNING: Make sure that you connect the cables between the C360 and the external power supply correctly: 1. Positive to positive 2. Negative to negative ! ADVERTENCIA: ADVERTENCIA: Asegúrese que las polaridades de los cables entre el C360 y la fuente de alimentación externa estén conectados correctamente: ● Positivo ("+") a Positivo ("+") ● Negativo ("-") a Negativo ("-") 6.
Connecting a BUPS Connecting a BUPS Note: You cannot connect the C360 to a DC power supply and BUPS simultaneously. Note: If you deploy a BUPS with the C360, the Powerstax (formerly known as APC (Advanced Power Conversion PLC)) Front End AC-DC Power Shelf (model R2400A111) with Powerstax 800W PSUs (models A0800-085-545-CA1) are to be used.The applied voltage at the C360 BUPS DC terminal block should be from 52 to 55 VDC.
Powering Up the Avaya C360 2. Connect the power cable to the terminals on the C360 and then external DC power supply.
Connecting a BUPS Sample Backup Power Supply Scheme Figure 19 shows a connection example for a stack of three C363T-PWR switches. This configuration provides power supply redundancy and up to 305 W of inline power per C363T-PWR switch. Table 9 lists the equipment required for this scenario. Figure 19: Sample Scheme 1 2 3 Figure notes: 1. AC power 2. BUPS DC input (+) 3.
Powering Up the Avaya C360 Table 9: Required Equipment (C363T-PWR Scheme) 2 of 2 Quantity Description Material code PEC Code 2 Powerstax 800W PSUs (see "Budgeting Power" for details) A0800-085-545-CA1* 3 X360STK Octaplane stacking module 700305899 1 X330RC Redundant Octaplane stacking cable 108563453 4705-065 2 X330SC Short Octaplane stacking cable** 108592445 4705-067 6 Power cables to connect Powerstax Power Shelf to C360-PWR switches.* (16AWG/ 1.
Connecting a BUPS Budgeting Power Note: Note: One Powerstax 800W PSU provides enough power for a stack of ten C363T and/ or C364T switches. When deciding how many 800W PSUs to install in the Powerstax external DC power shelf, you need to take into account the configuration of the powerinline external power parameter in the C360-PWR switch (set using the set powerinline external power CLI command). Refer to Table 10 and Table 11 for guidelines: Table 10: Budgeting Power - C363T-PWR No.
Powering Up the Avaya C360 Post-Installation The following indicate that you have performed the installation procedure correctly: Table 12: Post-Installation Indications Procedure Powering the C360 Indication ● All front panel function LEDs illuminate briefly. - If the PWR LED blinks once every 1 second, then the BUPS is active and the main PSU is down.
Chapter 5: Establishing Switch Access This chapter describes various methods for accessing the C360 CLI and logging in with the appropriate security level: C360 CLI ● CLI Architecture ● Security Levels ● Entering the CLI Establishing Connections ● Establishing a Console Connection ● Assigning C360 IP Stack Address ● Establishing a Telnet Connection ● Establishing an SSH Connection ● Establishing Access to Other Entities in the Stack (C360 Sessions) ● Establishing a Modem (PPP) Connection
Establishing Switch Access CLI Architecture The C360 stack supports both Layer 2 switching and Layer 3 switching. The C360 CLI includes two CLI entities to support this functionality. ● The Switch CLI entity is used to manage Layer 2 switching of the entire stack. CLI commands for managing Layer 2 switching are described in the Reference Guide for the Avaya C360 Converged Stackable Switch, 10-300506. ● The Router CLI entity is used to manage Layer 3 switching of a single module.
Security Levels Tip: Tip: The Web management passwords are the same as those of the CLI. If you change the passwords of the CLI then those passwords become active for Web management as well. Entering the Supervisor Level The Supervisor level is the level in which you first enter C360 CLI and establish user names for up to 10 local users. When you enter the Supervisor level, you are asked for a Login name.
Establishing Switch Access Entering the CLI To enter the CLI, enter your username and password. Your access level is indicated in the prompt as shown in Table 14.
Establishing a Console Connection 1. Use the serial cable supplied to attach the RJ-45 console connector to the Console port of the master C360. Connect the DB-9 connector to the serial (COM) port on your PC/terminal. - The master C360 is indicated by the SYS LED being ON. 2. Ensure that the serial port settings on the terminal are: ● 9600 baud ● 8 bits ● 1 stop bit ● no parity.
Establishing Switch Access Assigning C360 IP Stack Address Note: Note: All C360 switches are shipped with the same default IP address. You must change the IP address of the master C360 switch in a stack in order to guarantee that the stack has its own unique IP address in the network. The network management station or a workstation running a Telnet client can establish communications with the stack once this address had been assigned and the stack has been inserted into the network.
Establishing a Telnet Connection Establishing a Telnet Connection Perform the following steps to establish a Telnet connection to the C360 for configuration of Stack or Router parameters. You can Telnet the Stack Master IP address: 1. Connect your station to the network. 2. Verify that you can communicate with the C360 by pinging the IP of the C360. If there is no response using ping, check the IP address and default gateway of both the C360 and the station. Tip: The C360 default IP address is 149.49.32.
Establishing Switch Access Establishing an SSH Connection Introduction to SSH SSH (Secure Shell) protocol is a security protocol that enables establishing a remote session over a secured tunnel, also called a remote shell. SSH accomplishes this by creating a transparent encrypted channel between the local and remote devices. In addition to remote shell, SSH also provides secure file transfer between the local and remote devices. SSH protocol currently has 2 versions, SSH1 and SSH2.
Establishing an SSH Connection 4. The C360 derives its DH private key y and its DH public key f=(g^y)mod p, and sends the f value to the client, its public host key and the digital signature calculated for all values exchanged so far including f and public host key. The C360 uses DSA cipher and its host private key to calculate the signature. 5. The SSH client verifies the C360 identity. It checks the C360 host public key validity against the ~/.ssh/known_host file.
Establishing Switch Access Figure 21: SSH Session Establishment Process SSH Client Connection Establish Connection Public Key and Encryptions List Private Key and Encryptions List SSH Server Acknowledgement (ACK) User Authentication Username List HOST RSA Key Hostnames List User Passwords Initiate CLI Session Procedure for Establishing an SSH Connection Perform the following steps to establish an SSH connection to the C360 for configuration of Stack or Router parameters.
Establishing an SSH Connection 5. Using your SSH client software, open a session to the Stack Master IP address. 6. When you are prompted for a password, enter the User Level password root in lower case letters (do not use uppercase letters). - The User level prompt will appear when you have established communications with the C360. You can now configure the C360 stack and change its default IP address. SSH Commands The following SSH commands are accessible from Supervisor level.
Establishing Switch Access Establishing Access to Other Entities in the Stack (C360 Sessions) You can use sessions to switch between the CLI of C360 switches, other stack entities, or to switch between Layer 2 and Layer 3 commands. To switch between stack entities use the session [] CLI command. ● is the number of the switch in the stack, counting from the bottom. ● can be switch, router, wan, or mgp. Use switch mode to configure layer 2 commands.
Establishing a Modem (PPP) Connection Establishing a Modem (PPP) Connection Point-to-Point Protocol (PPP) provides a Layer 2 method for transporting multi-protocol datagrams over modem links. Connecting a Modem to the Console Port Before you can establish a PPP connection with a modem can be established, you need to configure the following: ● C360 IP address: refer to Assigning C360 IP Stack Address for further information.
Establishing Switch Access 9. You can now dial into the switch from a remote station, and open a Telnet session to the PPP interface IP address. 72 Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.
SNMP Support SNMP Support Introduction to SNMP SNMP Versions There are currently three versions of SNMP (Simple Network Management Protocol): ● SNMPv1 ● SNMPv2c ● SNMPv3 The C360 supports device access using all three versions of SNMP. Managers and Agents SNMP uses software entities called managers and agents to manage network devices. The manager monitors and controls all other SNMP-managed devices or network nodes on the network. There must be at least one SNMP Manager in a managed network.
Establishing Switch Access ● Retrieve the value immediately after the variable you name - a get-next action. The SNMP manager retrieves values from the MIB tree. Using the get-next function, you do not need to know the exact variable name you are looking for. The SNMP manager takes the variable you name and then uses a sequential search to find the desired variable. ● Change a setting on the agent - a set action The SNMP manager requests the agent to change the value of the MIB variable.
SNMP Support SNMPv3 SNMPv3 enables the following features over SNMPv1 or v2c: ● User authentication with a username and password. Authentication is performed using md5 or sha-1.
Establishing Switch Access ● Authentication Protocol - The authentication protocol to use. Possible values are: No auth, HMAC MD5, or HMAC SHA-1. ● Authentication Password - The authentication password is transformed using the authentication protocol and the SNMP engine ID to create an authentication key. ● Privacy Protocol - The privacy protocol to use. Possible values are: No privacy, DES privacy.
SNMP Support - AuthNoPriv - AuthPriv ● View names: - Read - Allow read-only access to a specified list of Object IDs (OIDs) in the MIB tree. - Write - Allow read-write access to a specified list of OIDs in the MIB tree. - Notify - Allow SNMP notifications from a specified list of OIDs to be sent. Views Each view consists of a name and a list of OIDs in the MIB tree.
Establishing Switch Access Table 16: SNMP CLI Commands 2 of 3 In order to... Use the following command...
SNMP Support Table 16: SNMP CLI Commands 3 of 3 In order to... Use the following command...
Establishing Switch Access RADIUS Introduction to RADIUS User accounts are typically maintained locally on the switch. Therefore, if a site contains multiple Avaya Switches, it is necessary to configure each switch with its own user accounts. Additionally, if for example a "read-write" user has to be changed into a "read-only" user, you must change all the "read-write" passwords configured locally in every switch, in order to prevent him from accessing this level.
RADIUS Figure 22: RADIUS Authentication Procedure User attempts login Lo cal Use r a cco u nt a uth e ntica ted in switch ? No Authentication request sent to RAD IU S Server U ser name and password authenticated? Yes Yes No Authentication R eject sent to switch U ser cannot access sw itch embedded management Perform log -in according to user's privilege level to sw itch RADIUS is also part of IEEE 802.1x port-based network access control. For information on 802.1x, refer to IEEE 802.
Establishing Switch Access RADIUS Commands The following RADIUS commands are accessible from Supervisor level. Table 17: RADIUS CLI Commands In order to... Use the following command... Enable or disable authentication for the C360 switch.
Recovery Password Recovery Password Introduction to Recovery Password The C360 provides a recovery password in the event that you have forgotten the login password for the switch. The recovery password feature enables you to login to the device in a super user mode and change the regular login password. The recovery password feature can be disabled preventing unauthorized user to login to the device using the recovery password.
Establishing Switch Access Allowed Managers Allowed Managers Introduction With the Allowed Managers feature, the network manager can determine who may or may not gain management access to the switch. The feature can be enabled or disabled (default is disabled). When enabled, only those stations that are configured in the Allowed Managers table are able to gain Telnet, HTTP, and SNMP management access to the switch.
Allowed Managers Table 19: Allowed Managers CLI Commands 2 of 2 In order to... Use the following command...
Establishing Switch Access Allowed Protocols Allowed Protocols Introduction With the Allowed Protocols feature, the network manager can determine the IP protocols enabled on the switch. This feature can be used to block access to the switch using specific IP protocols. Each protocol can be independently enabled or disabled on the switch. Tip: Tip: Enabling and disabling the Recovery Password protocol can only be done using a direct console connection via the Console port.
Allowed Protocols Table 20: Allowed Protocol CLI Commands 2 of 2 In order to... Use the following command...
Establishing Switch Access 88 Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.
Section 3: Avaya C360 Configuration Issue 1 July 2006 89
Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.
Chapter 6: Avaya C360 Default Settings This section describes the procedures for the first-time configuration of the C360. The factory defaults are set out in detail in the tables included in this chapter. Configuring the Switch You may configure the C360 using the text-based Command Line Interface (CLI), the built-in C360 Device Manager or Avaya Integrated Management. For instructions on the CLI, see the Reference Guide for the Avaya C360 Converged Stackable Switch, 10-300506.
Avaya C360 Default Settings Table 21: Default Switch Settings 2 of 2 Function Default Setting MAC aging Enabled MAC aging time 5 minutes Keep alive frame transmission Enabled Network time acquisition Enabled, Time protocol IP multicast filtering Disabled 802.1x system-auth-control Disabled 802.1x port-control Auto RADIUS server Disabled Time server IP address 0.0.0.
Configuring the Switch Tip: Tip: Functions operate in their default settings unless configured otherwise.
Avaya C360 Default Settings 94 Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.
Chapter 7: Switch Configuration Introduction This chapter describes the parameters you can define, such as its name and location, time parameters, and so on. In addition, this chapter describes methods for saving and deploying device configurations and monitoring CPU utilization.
Switch Configuration Table 23: Basic Switch Configuration CLI Commands 2 of 2 In order to... Use the following command...
Basic Switch Configuration Operating parameters You can use the following commands to configure and display the mode of operation for the switch and display key parameters. The rules of syntax and output examples are all set out in detail in the Reference Guide for the Avaya C360 Converged Stackable Switch, 10-300506. Table 25: Operating Parameter CLI Commands In order to... Use the following command...
Switch Configuration In order to... Use the following command... Display the time status and parameters show time parameters Display the current time zone offset show timezone Get the time from the time server get time 2 of 2 98 Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.
Uploading and Downloading Device Configurations and Images Uploading and Downloading Device Configurations and Images The C360 allows you to backup and restore device configurations and configure multiple devices using Simple Network Management Protocol (SNMP) and Trivial File Transfer Protocol (TFTP) or Secure Copy Protocol (SCP) to exchange information with the devices. For more information on SNMP, refer to SNMP Support on page 73. For more information on SCP, refer to SCP Protocol Support on page 103.
Switch Configuration Note: Note: *The running configuration is not saved automatically after a reset. If you wish to make the currently running configuration the startup configuration, use the copy running-config startup-config command before preforming a reset. Layer 2 Configuration File The Layer 2 configuration file contains the full Layer 2 configuration of the switch in the format of the CLI commands necessary to configure the device to its current configuration.
Uploading and Downloading Device Configurations and Images In order to... Use the following command... Display the status of file uploads show upload status Display the status of file downloads show download status 2 of 2 Layer 3 Configuration File The Configuration File feature allows the user to read the routing configuration parameters and save them to a file on the station. The routing configuration commands in the file are in CLI format.
Switch Configuration In order to... Use the following command...
SCP Protocol Support SCP Protocol Support In addition to data transfer via an SSH session, the SSH protocol is also used to support SCP for secure file transfer. When using SCP, the C360 is the client, and an SCP server must be installed on the management station. After defining users on the SCP server, the device acts as an SCP client. The procedure described in the Introduction to SSH on page 66 is used with the roles of the C360 and the client computer reversed.
Switch Configuration System Logging System Logging Introduction The C360 System Logging feature is capable of storing system messages on a device, outputting messages to the CLI console, Telnet session, or SSH session, and reporting remotely to a Syslog server. System Logging is an important tool used for routine maintenance, auditing, and monitoring access to the device.
System Logging Sinks System logging messages can be sent via a number of "sinks" or methods. Table 27 provides a list of available sinks. Table 27: Available Sinks Sink Description Console/ Telnet/SSH Logging messages are sent to the console or a Telnet or SSH session in non- blocking mode. Log File Logging messages are saved to a log file in the NVRAM of the master module in the stack. The log file is not erased by an NVRAM initialization.
Switch Configuration Table 28: Supported Message Facilities 2 of 2 Message Facility Codes Description SWITCHFABRIC Switch fabric failures LAG Link Aggregation package messages VLAN VLAN package messages SNMP SNMP agent messages POLICY Policy package messages CLI Command Line interpreter messages STP Spanning tree package messages THRESHOLD RMON alarms messages 2 of 2 Syslog Servers Remote logging using Syslog servers provides the following advantages: ● History and archiving – Storing lo
System Logging - Log file – Informational - Console – Informational - Telnet/SSH session – Warning ● System Logging Commands Tip: The system logging configuration is not saved to NVRAM. The configuration only affects the active session from which the commands are executed. Each session must be configured separately. Tip: ● Clearing the system log file. Tip: Tip: Resetting the device does not clear the log file. Use the CLI commands briefly described below for configuring System Logging.
Switch Configuration In order to... Use the following command... Defines the access level associated with a Syslog server sink. A user cannot specify an admission level higher than the level assigned to him.
Telnet Client Support Telnet Client Support Introduction to Telnet The C360 supports invocation of a Telnet client from the CLI. The Telnet client implementation enables you to control the destination port for connecting daemons that listen on a non-default port. Authentication when connecting to the switch via Telnet is identical to standard console connection authentication (local or RADIUS).
Switch Configuration Monitoring CPU Utilization The C360 provides you with the ability to monitor CPU utilization on each module of the stack. Use the CLI commands briefly described below for enabling and disabling CPU utilization monitoring and viewing CPU utilization statistics. The rules of syntax and output examples are all set out in detail in the Reference Guide for the Avaya C360 Converged Stackable Switch, 10-300506. In order to... Use the following command...
Chapter 8: Avaya C360 Layer 2 Features This section describes the C360 Layer 2 features. It provides the basic procedures for configuring the C360 for Layer 2 operation. The C360 supports a range of Layer 2 features. Each feature has CLI commands associated with it. These commands are used to configure, operate, or monitor switch activity for each of the Layer 2 features. This section of the C360 Installation and Maintenance Guide explains each of the features.
Avaya C360 Layer 2 Features Fast Ethernet Fast Ethernet is a newer version of Ethernet, supporting data transfer rates of 100 Mbps. Fast Ethernet is sufficiently similar to Ethernet to support the use of most existing Ethernet applications and network management tools. The adoption of Fast Ethernet is as 100BASE-T (over copper) or 100BASE-FX (over fiber). Fast Ethernet is standardized as IEEE 802.3u. Gigabit Ethernet Gigabit Ethernet supports data rates of 1 Gbps.
Ethernet Configuring Ethernet Parameters Auto-Negotiation Auto-Negotiation is a protocol that runs between two stations, two switches or a station and a switch. When enabled, Auto-Negotiation negotiates port speed and duplex mode by detecting the highest common denominator port connection for the endstations. For example, if one workstation supports both 10 Mbps and 100 Mbps speed ports, while the other workstation only supports 10 Mbps, then Auto-Negotiation sets the port speed to 10 Mbps.
Avaya C360 Layer 2 Features Priority By its nature, network traffic varies greatly over time, so short-term peak loads may exceed the switch capacity. When this occurs, the switch must buffer frames until there is enough capacity to forward them to the appropriate ports. This, however, can interrupt time-sensitive traffic streams, such as Voice and other converged applications. These packets need to be forwarded with the minimum of delay or buffering.
Ethernet The first half of a MAC address contains the ID number of the device manufacturer. These IDs are regulated by an Internet standards body. The second half of a MAC address represents the serial number assigned to the device by the manufacturer. CAM Table The CAM Table contains a mapping of learned MAC addresses to ports and VLANs.
Avaya C360 Layer 2 Features Table 30: Ethernet Configuration CLI Commands 2 of 3 In order to... Use the following command...
VLANs Table 30: Ethernet Configuration CLI Commands 3 of 3 In order to... Use the following command... Display the current status of the MAC aging function show mac-aging Display the MAC aging time in minutes. show mac-aging-time 3 of 3 VLANs VLAN Overview A VLAN is made up of a group of devices on one or more LANs that are configured so that they operate as if they form an independent LAN, when in fact they may be located on a number of different LAN segments.
Avaya C360 Layer 2 Features Figure 24: VLAN Overview 3 4 ` 1 ` ` 5 ` 2 Figure notes: 1. Management VLAN 2. Management LAN 3. R&D VLAN 4. Device A 5. Device B In virtual topological networks, the network devices may be located in diverse places around the LAN-such as in different departments, on different floors or in different buildings. Connections are made through software.
VLANs Figure 25: VLAN Switching and Bridging 1 3 2 1 3 2 Figure notes: 1. Sales 2. Engineering 3. Marketing VLAN Tagging VLAN Tagging is a method of controlling the distribution of information on the network. The ports on devices supporting VLAN Tagging are configured with the following parameters: ● Port VLAN ID ● Tagging Mode The Port VLAN ID is the number of the VLAN to which the port is assigned.
Avaya C360 Layer 2 Features multi-tenant networks, where each user has his a VLAN for privacy, but the whole building has a shared high-speed connection to the ISP. In order to accomplish this, C360 allows you to set multiple VLANs per port. The three available Port Multi-VLAN binding modes are: ● Bind to All - the port is programmed to support the entire 3K VLANs range. Traffic from any VLAN is forwarded through a port defined as "Bind to All".
VLANs Figure 26: Multiple VLAN Per-port Binding Modes 2 1 3 Figure notes: 1. Bind to All - Any VLAN in the range of 1 to 3,071 will be allowed access through this port - Intended mainly for easy backbone link 2. Static Binding - You manually specify the list of VLAN IDs to be bound to the port, up to 3,071 VLANs - Default mode for every port - Only VLAN 9, and any other VLANs statically configured on the port will be allowed to access this port 3.
Avaya C360 Layer 2 Features Table 31 shows the relationship between the binding mode and the whether the packet is accepted. Table 31: Ingress VLAN Security Binding Mode Packets Permitted Static Only user-defined VIDs Bind to Configured All VIDs defined in the switch Bind to All Any VID (1 to 3,071) VLAN CLI Commands The following table contains a list of the CLI commands for the VLAN feature.
IEEE 802.1x (Port Based Network Access Control) Table 32: VLAN CLI Commands 2 of 2 In order to... Use the following command... Clear a VLAN statically configured on a port clear port static-vlan Clear the dynamic vlans learned by the switch from incoming traffic clear dynamic vlans Display the MAC addresses learned on a specific VLAN show cam vlan 2 of 2 IEEE 802.1x (Port Based Network Access Control) Port Based Network Access Control (IEEE 802.
Avaya C360 Layer 2 Features ● As a result of an authentication attempt, the C360 port can be either in a "blocked" or a "forwarding" state. 802.1x interacts with existing standards to perform its authentication operation. Specifically, it makes use of Extensible Authentication Protocol (EAP) messages encapsulated within Ethernet frames (EAPOL), and EAP over RADIUS for the communication between the Authenticator and the Authentication Server. IEEE 802.
IEEE 802.1x (Port Based Network Access Control) - Enable the RADIUS feature. - Configure the port used to access the RADIUS server as "force-authorized." Tip: You can configure on the RADIUS server a PVID, static VLAN binding and port level for each authenticated user. If the port that the user is connected to is authorized, those parameters will be assigned to the port. Tip: ● Connect the Supplicant - i.e., Windows XP clients - directly to the C360.
Avaya C360 Layer 2 Features In order to... Use the following command...
Spanning Tree Protocol In order to... Use the following command...
Avaya C360 Layer 2 Features a loop in an extended network, bridges may forward traffic indefinitely, which can result in increased traffic and degradation in network performance. The Spanning Tree Algorithm: ● Produces a logical tree topology out of any arrangement of bridges. The result is a single path between any two end stations on an extended network. ● Provides a high degree of fault tolerance.
Spanning Tree Protocol ● Improvement in the time it takes to propagate TC information. Specifically, TC information does not have to be propagated all the way back to the Root Bridge (and back) to be changed. ● Origination of BPDUs on a port-by-port basis. Port Roles At the center of RSTP-specifically as an improvement over STP (802.1d)-are the roles that are assigned to the ports.
Avaya C360 Layer 2 Features Spanning Tree Implementation in the C360 RSTP is implemented in C360 family of products so that it is interoperable with the existing implementation of STP. In order to configure the switch to either common Spanning Tree or Rapid Spanning Tree protocol, use the set spantree version command. The balance of this section lists the conditions and limitations that govern the implementation of Spanning Tree in the C360 family.
Spanning Tree Protocol Spanning Tree Protocol CLI Commands The following table contains a list of CLI commands for the Spanning Tree feature. The rules of syntax and output examples are all set out in detail in the Reference Guide for the Avaya C360 Converged Stackable Switch, 10-300506. In order to... Use the following command...
Avaya C360 Layer 2 Features In order to... Use the following command... Set the port as an RSTP edge port or non-edge port set port edge admin state Set the port point-to-point admin status set port point-to-point admin status Show the port's point-to-point admin and operational RSTP status show port point-to-point status 2 of 2 MAC Security The MAC security function is intended to filter incoming frames (from the line) with an unauthorized source MAC address (SA).
MAC Security currently learnt on this port are preserved and considered as secure MAC, unless they are removed using clear secure mac command. Individual secure MACs can also be added. Tip: Tip: Note: You can add a MAC address to more than one port on the device. This allows a specific device to communicate with the switch via more than one ingress port. However the number of secured MAC addresses on any module cannot exceed 1,024.
Avaya C360 Layer 2 Features LAG (Link Aggregate Group) LAG Overview A LAG uses multiple ports to create a high bandwidth connection with another device. For example: Assigning four 100BASE-T ports to a LAG on an C360 allows the switch to communicate at an effective rate of 400 Mbps with another switch. LAGs provide a cost-effective method for creating a high bandwidth connection. LAGs also provide built-in redundancy for the ports that belong to a LAG.
Port Redundancy LAG Implementation in the C360 This section describes the implementation of the LAG feature in the C360 product family. ● With the C363T and C363T-PWR, you can aggregate the two GBIC ports to form a LAG, you can aggregate the bandwidths of 3 groups of 10/100BASE-T ports in a LAG, for a maximum of four LAGs per switch.
Avaya C360 Layer 2 Features In addition to Link Aggregation Groups - which comprise the basic redundancy mechanism within the switch - the C360 offers an additional port redundancy scheme. To achieve port redundancy, you can define a redundancy relationship between any two ports in a stack. One port is defined as the primary port and the other as the secondary port. If the primary port fails, the secondary port takes over.
Port Redundancy Intermodule Port Redundancy The intermodule port redundancy feature supports one pair of redundant ports per stack. Unlike Port Redundancy definitions, intermodule port redundancy definitions are retained after stack renumbering. In other words, if you remove a switch which is not part of the redundancy scheme, the redundancy definition is unaffected. This makes intermodule port redundancy a better option for very important connections.
Avaya C360 Layer 2 Features Tip: Tip: Intermodule Port Redundancy does not interwork with the Spanning Tree Algorithm. Port Redundancy CLI Commands The following table contains a list of the CLI commands for the Redundancy feature. The rules of syntax and output examples are all set out in detail in the Reference Guide for the Avaya C360 Converged Stackable Switch, 10-300506. In order to... Use the following command...
IP Multicast Filtering Port Classification Overview With the C360, you can classify any port as regular or valuable. Setting a port to valuable means that, in case of Ethernet link failure of that port, a link fault trap can be sent even when the port is disabled. This feature is particularly useful for the link/intermodule redundancy application, where you need to be informed about a link failure on the dormant port and resume traffic quickly. Port Classification CLI Commands In order to...
Avaya C360 Layer 2 Features The C360 supports multicast filtering. The C360 learns which switch ports need to receive which multicast packets and configures the necessary information into the switch's hardware tables. This learning is based on IGMP (version 1 or 2) snooping. The multicast filtering function in the C360 is transparent to the IP hosts and routers. It does not affect the forwarding behavior apart from filtering multicast packets from certain ports where they are not needed.
RMON ● The Group Filtering Delay time is the time that the switch waits between becoming aware of a Multicast group on a certain VLAN and starting to filter traffic for this group. IP Multicast CLI Commands The following table contains a list of the CLI commands for the IP Multicast feature. The rules of syntax and output examples are all set out in detail in the Reference Guide for the Avaya C360 Converged Stackable Switch, 10-300506. In order to... Use the following command...
Avaya C360 Layer 2 Features RMON is the internationally recognized and approved standard for detailed analysis of shared Ethernet media. It ensures consistency in the monitoring and display of statistics between different vendors. RMON's advanced remote networking capabilities provide the tools needed to monitor and analyze the behavior of segments on a network.
SMON In order to... Use the following command... Display the parameters of an Event entry defined by the rmon event command or Device Manager show rmon event Clears all RMON counters in the stack clear rmon statistics 2 of 2 SMON SMON Overview SMON is Avaya's standard-setting switch monitoring technology that has now been adopted as IETF standard RFC 2613.
Avaya C360 Layer 2 Features SMON extends both RMON I for the MAC layer, and RMON 2 for the network layer and higher. SMON monitoring collects and displays data in real-time. Top-down view of all traffic: ● Network view for selected switches ● Network view for selected ports ● VLAN view ● History Tip: Tip: Note: In order to use SMON, you need to install the SMON license on the C360 switch and use Avaya IM with SMON Note: SMON for the network layer is not supported in this version of the C360.
Weighted Queuing Port Mirroring CLI commands In order to... Use the following command... Define a port mirroring source-destination pair in the switch set port mirror Display port mirroring information for the switch show port mirror Cancel port mirroring clear port mirror Port Mirroring Implementation in the C360 Note the following limitations: ● The VLAN binding parameters of the source and destination ports must be identical.
Avaya C360 Layer 2 Features ● When the Priority scheme is set to "Strict", the Lower priority queue will transmit only if none of the Higher priority queues has nothing to transmit. ● When the Priority scheme is set to "WRR" queues will be transmit according to the weight factor. Tip: Tip: By default, the WWR weights between the four C360 priority queues are 1:4:16:64 Weighted Queuing CLI Commands The following table contains a list of the CLI commands for the Weighted Queuing feature.
LLDP Agent attached to the same LAN. These can all be reported to management stations via IEEE-defined Simple Network Management Protocol (SNMP) Management Information Bases (MIBs). LLDP information is transmitted periodically. The IEEE has defined a recommended transmission rate of 30 seconds, however, the transmission rate is adjustable. LLDP devices, after receiving an LLDP message from a neighboring network device, stores the LLDP information in an SNMP MIB.
Avaya C360 Layer 2 Features Configuring the LLDP Agent To configure LLDP: 1. Enable the LLDP agent globally using the set lldp system-control command. C360-1 (super)# set lldp system-control enable Done! This command affects all C360 switches within a stack and activates TLV reception and mandatory TLV transmission on all stack ports according to the administrative LLDP port status (refer to step 2). 2. Configure the administrative lldp port status using the set port lldp CLI command (optional).
LLDP Agent LLDP Agent CLI Commands The following table contains a list of the CLI commands for the LLDP Agent feature. The rules of syntax and output examples are all set out in detail in the Reference Guide for the Avaya C360 Converged Stackable Switch, 10-300506. In order to... Use the following command... Enable or disable the LLDP application globally (per stack).
Avaya C360 Layer 2 Features 150 Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.
Chapter 9: Avaya C360 Layer 3 Features This section describes the C360 Layer 3 features. It provides the basic procedures for configuring the C360 for Layer 3 operation.
Avaya C360 Layer 3 Features Obtaining a Routing License Key To obtain a License Key that enables routing features: 1. Go to http://license-lsg.avaya.com and click "request new license". 152 Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.
Obtaining and Activating a License Key 2. Enter the Certificate Key and Certificate Type. 3. Click Next.
Avaya C360 Layer 3 Features 4. Enter contact information (once per certificate) 5. Click Next. 154 Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.
Obtaining and Activating a License Key 6. View number of licenses left.
Avaya C360 Layer 3 Features 7. Enter serial number of the switch(es) or module. To identify serial numbers use the CLI command: show module-identity. 156 Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.
Obtaining and Activating a License Key 8. Click Generate.
Avaya C360 Layer 3 Features Activating a Routing License Key To activate a Routing License Key: 1. Enter the acquired Routing License Key into the C360 switch using the set license CLI CLI command. set license [module] [license] [featureName] where: module - C360 switch number (the location of the device in the stack) license - license code featureName - routing and press Enter. 2. Reset the module. 3. Check that the license is activated using the show license CLI command.
What is Routing? The Routing Update Message is one such message. Routing Updates generally consist of all or a portion of a routing table. By analyzing Routing Updates from all routers, a router can build a detailed picture of network topology. A Link-State Advertisement is another example of a message sent between routers. Link-State Advertisements inform other routers of the state of the sender's links. Link information can also be used to build a complete picture of the network's topology.
Avaya C360 Layer 3 Features Figure 29: Routing ` ` 1 2 Figure notes: 1. First Hop: ● Protocol address: Destination ● Physical address: Router 1 2. Second Hop: ● Protocol address: Destination ● Physical address: Router 2 The relation between the destination host's protocol address and its physical address is obtained by the routers using the ARP request/reply mechanism, and the information is stored within the ARP table in the router (see The ARP Table on page 173).
Routing Configuration Routing Configuration Forwarding The C360 forwards IP packets between IP networks. When it receives an IP packet through one of its interfaces, it forwards the packet through one of its interfaces. The C360 supports multinetting, enabling it to forward packets between IP subnets on the same VLAN as well as between different VLANs. Forwarding is performed through standard means in Router mode.
Avaya C360 Layer 3 Features IP Configuration IP Configuration CLI Commands In order to... Use the following command...
IP Configuration In order to... Use the following command...
Avaya C360 Layer 3 Features Tip: Tip: If the IP interface is on VLAN #1, continue with Step 7. 6. Create the management/routing VLAN. Use the command set vlan name replacing by the VLAN number, and by the VLAN name. Press Enter. 7. Create an IP interface name. Type: Router(configure)# interface Press Enter. The Router(configure-if:)# prompt appears. 8. Assign the IP address and network mask of the IP interface you have created.
RIP (Routing Interchange Protocol) Configuration operating RIPv1, you must not configure variable length subnet masks (VLMS). Each IP network must have a single mask, implying that all subnets in a given IP network are of the same size. Also, when operating RIPv1, you must not configure supernets, which are networks with a mask smaller than the natural net mask of the address class, such as 192.1.0.0 with mask 255.255.0.0 (smaller than the natural class C mask which is 255.255.255.0).
Avaya C360 Layer 3 Features RIP CLI Commands In order to... Use the following command...
OSPF (Open Shortest Path First) Configuration OSPF (Open Shortest Path First) Configuration OSPF Overview OSPF is a routing protocol developed for IP networks based on the shortest path first or link-state algorithm. It was introduced to overcome the limitations of RIP in increasingly complex network designs. OSPF is based on the cost of a particular path. In contrast, RIP uses hops as a path criterion. Also, updates are sent on a "need to know" basis rather than every 30 seconds as with RIP.
Avaya C360 Layer 3 Features OSPF CLI Commands In order to... Use the following command...
Static Routing Configuration Static Routing Configuration Static Routing Overview When dynamic routing protocols (RIP or OSPF) are not appropriate, you can manually configure static routes to indicate the next hop on the path to the final packet destination. A static route becomes inactive if the interface over which it is defined is disabled. When the interface is enabled, the static route becomes active again. They are never timed-out, or lost over reboot, and can only be removed by manual configuration.
Avaya C360 Layer 3 Features Static Routing Configuration CLI Commands In order to... Use the following command...
Route Redistribution C360 protocol preferences are listed below from the most to the least preferred: 1. Local (directly attached net) 2. High-preference static (manually configured routes) 3. OSPF internal routes 4. RIP 5. OSPF external routes 6. Low-preference static (manually configured routes). Route Redistribution Route redistribution is the interaction of multiple routing protocols. OSPF and RIP can be operated concurrently in the C360.
Avaya C360 Layer 3 Features Route Redistribution Commands In order to... Use the following command... Redistribute routing information from other protocols redistribute ARP (Address Resolution Protocol) Table Configuration ARP Overview IP logical network addresses are independent of physical addresses. Since the physical address must be used to convey data in the form of a frame from one device to another, a mechanism is required to acquire a destination device hardware address from its IP address.
ARP (Address Resolution Protocol) Table Configuration Figure 30: Building an ARP Table Station 1 sends ARP Request Broadcast, specifying IP address of Station 2 Station 2 receives the broadcast and identifies its IP address Station 2 sends an ARP Reply to Station 1 containing Station 2 MAC Address Station 2 updates its ARP table with the Station 1 address mapping Station 1 receives the ARP Reply Station 1 updates its ARP table with the Station 2 address mapping The ARP Table The ARP table is used to
Avaya C360 Layer 3 Features ARP CLI Commands In order to... Use the following command...
BOOTP/DHCP (Dynamic Host Configuration Protocol) Relay Configuration BOOTP/DHCP (Dynamic Host Configuration Protocol) Relay Configuration BOOTP/DHCP Overview BOOTP Short for Bootstrap Protocol, BootP is an Internet protocol that enables a diskless workstation to discover its own IP address, the IP address of a BOOTP server on the network, and a file to be loaded into memory to boot the machine. This enables the workstation to boot without requiring a hard or floppy disk drive.
Avaya C360 Layer 3 Features The DHCP/BOOTP server uses the relayed network information to decide from which subnet the address should be allocated. Therefore, the DHCP/BOOTP server must be configured to allocate addresses from the relayed networks configured on the C360. DHCP/BOOTP Relay in C360 is configurable per VLAN and allows you to specify two DHCP/ BOOTP servers. In this case, it duplicates each request, and sends it to both servers.
VRRP (Virtual Router Redundancy Protocol) Configuration Configuration is performed on a per-interface basis. When a netbios broadcast packet arrives from an interface on which netbios rebroadcast is enabled, the packet is distributed to all other interfaces configured to rebroadcast netbios. If the netbios packet is a net-directed broadcast (e.g., 149.49.255.
Avaya C360 Layer 3 Features takes over the role of master router. This makes VRRP fully interoperable with every host station. VRRP can be activated on an interface using a single command while allowing for the necessary fine-tuning of the many VRRP parameters. For a detailed description of VRRP, refer to VRRP standards and published literature. VRRP Configuration Example 1 Figure 31: VRRP Configuration Example (Case 1, Case 2) Backup Router 2 VRID: 2, IP: 30.30.30.2 Ass. IP: 30.30.30.1 IP: 30.30.30.
VRRP (Virtual Router Redundancy Protocol) Configuration ● By the end of the routers configuration, and when the network is up, the main router for each virtual router will be elected according to this order of preference: - The virtual router IP address is also the router's interface IP address - It has the highest priority (you can configure this parameter) - It has the highest IP address if the previous cases do not apply ● The virtual router IP address needs to be configured as Default Gateway on the
Avaya C360 Layer 3 Features In order to... Use the following command... Set the virtual router advertisement timer value (in seconds) for the virtual router ID ip vrrp timer Set the virtual router priority value used when selecting a master route ip vrrp priority Set or disable the virtual router simple password authentication for the virtual router ID.
Policy Configuration ● The packet protocol ● Matching the packet's source or destination IP address to the configured priority policy. ● Whether the packet source or destination TCP/UDP port number falls within a pre-defined range. In addition, the 802.1p priority of a packet can be modified according to the DSCP value in the IP header based on the DSCP-802.1p mapping configured by the user. The C360 supports Access Control policy.
Avaya C360 Layer 3 Features In order to... Use the following command... Set the source list, destination list, and destination module for copying an entire Policy List ip access-list-copy Set the DSCP-to-COS mapping.
Policy Configuration In order to... Use the following command... Set the policy control source to either local or remote policy server set qos policy source Copy current policy and router configuration to the startup configuration file copy running-config startup-config 3 of 3 Policy Configuration Example Figure 32: C360 Policy 4 5 6 1 8 2 3 7 Figure notes: 1. 2. 3. 4. Voice packet Data packet Unauthorized packet Policy Rules 5. 6. 7. 8.
Avaya C360 Layer 3 Features Policy Configuration Example The following shows configuration of Access List 100: 1. Assigning priority 6 to all TCP traffic originating in network 149.49.0.0 - rule 1: C360-1(super)# ip access-list 100 1 fwd6 tcp 149.49.0.0 0.0.255.255 any done! 2. Assigning priority 3 to all TCP traffic going to the host 172.44.17.1 - rule 2: C360-1(super)# ip access-list 100 2 fwd3 tcp any host 172.44.17.1 done! 3. Denying Telnet sessions originated by the host 192.168.5.
IP Fragmentation and Reassembly 4. fragments are usually not reassembled until final destination IP Fragmentation/Reassembly CLI Commands In order to... Use the following command...
Avaya C360 Layer 3 Features 186 Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.
Chapter 10: Avaya C360 Power over Ethernet Features This chapter describes the C360-PWR PoE (Power over Ethernet Features). It provides the basic procedures for configuring the C360 for PoE operation. It contains the following sections: ● Load Detection ● “Plug and Play" Operation ● Powering Devices ● Power over Ethernet in Converged Networks ● Power over Ethernet CLI Commands Power Over Ethernet The C360-PWR switches provides IEEE 802.
Avaya C360 Power over Ethernet Features How the C360-PWR Switches Detect a Powered Device The C360-PWR switches use the specific resistance powered device signature and PD (powered device) connection verification to determine whether to supply power to a give port. Figure 33 shows the process. Figure 33: Powered Device Detection Start Check Valid Resistance Signature? Yes No Apply Power Yes No PD still connected? Specific Resistance Signature (IEEE 802.
Power Over Ethernet “Plug and Play" Operation You can add and remove powered devices without manually reconfiguring the switch, since it performs a periodic automatic load detection scan on non-powered ports. ● If a powered device that fits the above criteria is detected on a non-powered port, then power is applied to the port. ● If a powered device is removed from a port, then power is denied to that port. The disconnected port is then scanned as well.
Avaya C360 Power over Ethernet Features Power over Ethernet in Converged Networks Figure 34 shows the C364T-PWR as part of an ultra-reliable Avaya network. It provides power to IP telephones, wireless network access devices and Web cameras. Figure 34: Powered Ethernet Application Both the data and power paths from the C360-PWR to the PBX are backed-up. Using LAGs for data with UPSs (Uninterruptible Power Supplies) for power ensures non-stop IP communications.
Power Over Ethernet Power over Ethernet CLI Commands In order to... Use the following command...
Avaya C360 Power over Ethernet Features 192 Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.
Chapter 11: C360 Device Manager This chapter describes the installation procedures for the C360 Device Manager Overview The Device Manager provides the following: ● Managing and monitoring Power over Ethernet. ● Device Configuration - Viewing and modifying the different device configurations. ● Virtual LANs - Viewing and editing Virtual LAN information. ● Link Aggregation Groups (LAGs) - Viewing and editing LAG information. ● Port Redundancy - Setting port redundancy for ports in a C360 Switch.
C360 Device Manager System Requirements Minimum hardware and operating system requirements are: ● Pentium II 400 Mhz-based computer with 128 Mb of RAM ● Screen resolution of 1024 x 768 pixels ● Microsoft Internet Explorer 5 or higher ● Microsoft Windows 2000 Workstation or Windows XP ● Sun Microsystems Java plug-in (supplied on the "Documentation and Utilities" CD) ● Refer to the Release Notes for the exact version of the Java plug-in Configuring the Device Manager You can configure several Dev
Running the Device Manager In order to... Use the following command... Display the SNMP time-out parameter show snmp time-out Display the URL of the Web server with the help files and the Java plug-in show web aux-files-url Running the Device Manager Note: Note: Assign an inband or out-of-band interface IP address to the switch before beginning this procedure. To run the Device Manager: 1. Open your browser. 2. Enter the URL of the switch in the format http://aaa.bbb.ccc.ddd where aaa.bbb.ccc.
C360 Device Manager Figure 35: The Welcome Page 4. If you have the Java plug-in installed, the Device Manager should open in a new window (see Figure 36). Figure 36: Device Manager 196 Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.
Installing the Java Plug-in 5. If you do not have the Java plug-in installed, follow the instructions on the Welcome page to install the plug-in (see Installing the Java Plug-in). Installing the Java Plug-in If the network manager has configured the system, the plug-in should be installed automatically. Note: Note: Ensure that Java or JavaScript is enabled on your Web browser. Please refer to your browser on-line help or documentation for further information.
C360 Device Manager Installing the On-Line Help and Java Plug-In on your Web Site Tip: Tip: This procedure is optional Copying the help files and Java plug-in to a local Web server allows users to access the on-line help for the Embedded Manager and enables automatic Installation and Maintenance of the Java plug-in the first time the users tries to manage the device. 1. Copy the emweb-aux-files directory from the Avaya C360 Documentation and Utilities CD to your local Web server.
Section 4: Troubleshooting and Maintaining the Avaya C360 Issue 1 July 2006 199
Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.
Chapter 12: Troubleshooting the Installation Troubleshooting the Installation This section will allow you to perform basic troubleshooting of the installation. If you are unable to solve the problem after following the procedures in this chapter, please contact Avaya Technical Support.
Troubleshooting the Installation Table 35: Troubleshooting 2 of 3 Problem/Cause Suggested Solution ● Mis-configuration ● Use the show port CLI command to show the port parameters and check they are compatible with the attached device.
Troubleshooting the Installation Table 35: Troubleshooting 3 of 3 Problem/Cause Suggested Solution Stacking not functioning Tip: Use the stack health command to display the status of the stack. See Stack Health on page 204 for further information.
Troubleshooting the Installation Stack Health The C360 software provides a Stack Health feature for verifying the integrity of the C360 and P330 and P330-ML stacking module and cables. Overview The Stack Health feature will identify defective modules and cables that may be installed in the C360 stack. The Stack Health algorithm separately checks all stacking modules and the Octaplane connections (including Redundant cable).
Stack Health Stack Health CLI Commands The following table contains a list of the CLI commands for the Stack Health feature. The syntax and output examples are set out in detail in the Reference Guide for the Avaya C360 Converged Stackable Switch, 10-300506. In order to... Use the following command...
Troubleshooting the Installation 206 Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.
Chapter 13: Maintenance Introduction This section provides basic maintenance information for the C360 and its components. For issues that are not covered in this chapter or in Chapter 12: Troubleshooting the Installation please contact your Avaya representative. ! CAUTION: CAUTION: Please refer to Before you Install the Avaya C360 before undertaking any of the procedures detailed in this section. Replacing the Stacking Module To replace the X360STK stacking module: 1. Power to the switch may remain on.
Maintenance Hardware NVRAM Initialization If you wish to perform a hardware NVRAM initialization, then perform the following steps: ! CAUTION: C360 switches and stacking modules contain components sensitive to electrostatic discharge. Touching the circuit boards unless instructed to do so may damage them. CAUTION: ! PRECAUCIÓN: PRECAUCION: El switch C360 y sus módulos de ampliación contienen componentes sensibles a descargas electrostáticas.
Hardware NVRAM Initialization Figure 37: Location of the NVRAM INIT Jumpers 2 1 Figure notes: 1. SPARE JUMPER 2. NVRAM INIT Jumper 3. Insert the X360STK module into the C360 switch where you wish to perform the NVRAM initialization. Refer to Installing the X360STK Stacking Module for further information. Tip: Refer to the Reference Guide for the Avaya C360 Converged Stackable Switch, 10-300506 for further information on the NVRAM initialization Tip: 4. The NVRAM initialization process starts.
Maintenance 210 Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.
Chapter 14: Updating the Firmware This section provides the basic procedure for downloading and updating the C360 system firmware. ! CAUTION: CAUTION: Refer to Before you Install the Avaya C360 before undertaking any of the procedures detailed in this section. Firmware Download You can perform firmware download using the CLI or Avaya Software Update Manager (part of the Avaya Integrated Management Suite).
Updating the Firmware Tip: Please download both the new Avaya firmware and the new Device Manager versions. Whichever version of the firmware you decide to run, always be sure to match the correct firmware and Device Manager versions. Tip: Download New Version without Overwriting Existing Version Firmware Banks The C360 has two firmware banks, Bank A and Bank B that contain the firmware necessary to run the switch.
Appendix A: Mixed Stacks This appendix covers deployment of the C360 in mixed stack environments. Please refer to the relevant section for information. Tip: For additional information, see the Release Notes or the Avaya Support site: http://support.avaya.com. Tip: You may stack the C360 with P333T-PWR, P332G-ML and P332GT-ML switches and G700 Media Gateway, subject to certain limitations which are described in this appendix. Please read the information carefully before creating mixed stacks.
Mixed Stacks Hardware Compatibility This section describes hardware compatibility issues. Stacking Tip: Tip: It is recommended to put the C360 switches at the bottom or top of a mixed stack for easier connection of cables. You may use the same Octaplane cables for stacking all the switches. However, the stacking modules are not interchangeable. Please refer to Table 36 for information on which stacking module to use.
Hardware Compatibility BUPS The Backup Power Supplies are not interchangeable. Please refer to Table 38 for information on which stacking module to use. Table 38: BUPS Compatibility Switch BUPS C360 Powerstax 800 (refer to Connecting a BUPS on page 53 for further information) G700 N/A P333T-PWR P330 BUPS + Powerstax 800 P332G-ML P330 BUPS-ML P332GT-ML P330 BUPS-ML Tip: Tip: Please refer to the appropriate documentation for further information.
Mixed Stacks Feature Compatibility While most features are the same on all the switches, there are some differences in implementation and functionality. Please refer to Table 39 for further information. Table 39: Feature Compatibility 1 of 2 Feature C360 SSH P333T-PWR G700 P332G-ML P332GT-ML Notes + +1 You can open SSH sessions to the stack or Layer 3 interface. You can access the G700 MGP after opening an SSH connection to the stack IP and then using the session command.
Feature Compatibility Table 39: Feature Compatibility 2 of 2 Feature C360 Layer 3 + VLANs 3,071 P333T-PWR G700 P332G-ML P332GT-ML Notes + 3,071 252 P332G-ML and P332GT-ML will only recognize the first 252 VLANs, the others will not be used. It is recommended not to define more than 252 VLANs in a mixed stack. 2 of 2 1. Software version 4.5 only. Note: Note: Certain CLI commands apply to the C360 only. If you run them on other switches you may receive an "operation failed" message.
Mixed Stacks 218 Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.
Appendix B: Configuring C360 QoS for Avaya IP Telephones Introduction This appendix covers configuring C360 QoS settings for Avaya IP Telephony environments. Table 41: Configuration for ports connected to Avaya IP Telephones Parameter Value CLI command PVID Data VLAN set port vlan / Port tagging None (i.e.
Configuring C360 QoS for Avaya IP Telephones 220 Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.
Appendix C: Standards and Compatibility Avaya C360 Standards Supported The Avaya C360 complies with the following standards. IEEE ● 802.1D Bridges and STA ● 802.1p Priority Tagging on all ports ● 802.1Q VLAN Tagging support on all ports ● 802.1w Rapid Spanning Tree ● 802.3af Power over Ethernet on C360-PWR switches ● 802.3x Flow Control on all ports ● 802.1x Port Based Network Access Control ● 802.3z Gigabit Ethernet ● 802.
Standards and Compatibility ● RFC-2613 SMON support for groups - Data Source Capabilities, Port Copy, VLAN and Priority Statistics ● RFC-2674 Bridge MIB Groups - dot1dbase and dot1dStp fully implemented.
IETF - Network Monitoring IETF - Network Monitoring ● RMON (RFC 1757) support for groups 1,2,3, and 9 - Statistics - History - Alarms - Events ● SMON (RFC 2613) support for groups - Data Source Capabilities - Port Copy - VLAN and Priority Statistics ● Bridge MIB Groups - RFC 2674 - dot1dbase and dot1dStp fully implemented.
Standards and Compatibility 224 Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.
Appendix D: Specifications Physical Height 1U (44.45 mm, 1.75”) Width 431 mm (17”) Depth 365 mm (14.4”) Weight ● C363T ● C363T-PWR ● C364T ● C364T-NEBS ● C364T-PWR 4.9 kg (10.8 lb.) 5.5 kg (12.1 lb.) 5.0 kg (11 lb.) 5.0 kg (11 lb.) 6.8 kg (15 lb.
Specifications Power Requirements C363T C363T-PWR Input voltage 100 to 240 VAC 50/60 Hz 100 to 240 VAC 50/60 Hz Power dissipation 60 W max 420 W max AC Input current 1.3 A max 4.2 A max DC Input current 2 A max 8 A max 226 Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.
Environmental. C364T C364T-NEBS C364T-PWR Input voltage 100 to 240 VAC 50/60 Hz -36 to -60 VDC 100 to 240 VAC 50/60 Hz Power dissipation 90 W max 90 W max 760 W max AC Input current 1.3 A max N/A 7.6 A max DC Input current‘ 2 A max 2 A max 15 A max Environmental. Operating Temp. 0° to 40°C (32° to 104°F) Storage Temp. -40° to 70°C (-14° to 184°F) Rel. Humidity 5% to 95% non-condensing Note: The C364T NEBS complies to the NEBS standard Note: Safety ● UL listed to UL60950-1.
Specifications MTBF Product MTBF (Hours) C363T 300,000 C364T C364T-NEBS 210,000 C363T-PWR 245,000 C364T-PWR 170,000 Interfaces ● C363T: 24 x 10/100 BASE-T RJ-45 port connectors + 2 x SFP GBIC connectors. ● C363T-PWR: 24 x 10/100 PoE BASE-T RJ-45 port connectors + 2 x SFP GBIC connectors. ● C364T: 48 x 10/100 BASE-T PoE RJ-45 port connectors + 2 x SFP GBIC connectors. ● C364T-NEBS: 48 x 10/100 BASE-T PoE RJ-45 port connectors + 2 x SFP GBIC connectors.
GBIC Transceivers The LX transceiver has a Wavelength of 1300 nm, Transmission Rate of 1.25 Gbps, Input Voltage of 3.3V, and Maximum Output Wattage of -2 dBm. SX Transceiver You may connect a 50 µm or 62.5 µm multimode (MMF) fiber cable to a 1000BASE-SX SFF/ SFP GBIC port. The maximum length is 500 m (1,640 ft.) for 50 µm and 220 m (722 ft.) for 62.5 µm cable. The SX transceiver has a Wavelength of 850 nm, Transmission Rate of 1.25 Gbps, Input Voltage of 3.3V, and Maximum Output Wattage of -4 dBm.
Specifications Console Pin Assignments For direct Console communications, connect the C360 to the Console Terminal using the supplied RJ-45 crossed cable and RJ-45 to DB-9 adapter. C360 RJ-45 Pin Name (DCE View) Terminal DB-9 Pins Modem DB-25 Pins 1 For future use NC See note 2 TXD (C360 input) 3 3 3 RXD (C360 output) 2 2 4 CD 4 8 5 GND 5 7 6 DTR 1 20 7 RTS 8 4 8 CTS 7 5 Tip: Tip: Pin 1 of the Modem DB-25 connector is internally connected to Pin 7 GND.
Ethernet Ethernet ● VLANs - Layer 2: 3,071 - Layer 3: 255 ● MAC addresses: minimum 16k ● Priority queuing: 4 queues ● Multicast groups: 1k Issue 1 July 2006 231
Specifications 232 Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.
Index Index Numerical 802.1x support . . . . . . . . . . . . . . . . . . . 123 CLI commands . . . . . . . . . . . . . . . . . 125 configuring procedure . . . . . . . . . . . . . . 124 A AC power, connecting . . . . . Access, restricting management Accessing the switch . . . . . . Activating a routing license . . . ARP table configuration . . . . Auto-negotiation . . . . . . . . Avaya IP Telephones configuring QoS for . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Index network . . . . . . . . . . . supplemental grounding . . . . Connections budgeting power . . . . . . . establishing console . . . . . establishing layer 2 and layer 3 establishing PPP . . . . . . . establishing SSH . . . . . . . establishing Telnet . . . . . . verifying proper . . . . . . . . Console pin assignments . . . . . Conventions in documentation . . Converged networks and PoE . . CPU utilization monitoring . . . . . . . . . . . . . 44 . . . . . . . . . 54 . . . . . . . . . . . . . . . . .
Index installing . . . . . . . . . . . . specifications . . . . . . . . . . Gigabit ethernet . . . . . . . . . . Grounding, connecting supplemental . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 . 228 . 112 . 54 J Java plug-in, installing . . . . . . . . . . . . . . 197 H L Half-duplex . . . . . . . . . . . . . . . . . . . . 113 Hardware NVRAM initialization . . . . . . . . . . . 208 Health, verifying stack . . . . . . . . . . . . . . .
Index M MAC address . . . . . . . . . . . . . . . aging . . . . . . . . . . . . . . . . security . . . . . . . . . . . . . . . MAC security . . . . . . . . . . . . . . Maintenance. . . . . . . . . . . . . . . hardware NVRAM initialization . . . . . replacing the X360STK stacking module Manageability . . . . . . . . . . . . . . Management options . . . . . . . . . . . . . . . . restricting access . . . . . . . . . . . Manager, Device. . . . . . . . . . . . . Mixed-device stacks . . . . . . . . . . .
Index restricting management access . . . . SCP support . . . . . . . . . . . . . SNMP . . . . . . . . . . . . . . . . Settings, device default . . . . . . . . . . Site preparation . . . . . . . . . . . . . SMON . . . . . . . . . . . . . . . . . configuring with CLI . . . . . . . . . . SNMP . . . . . . . . . . . . . . . . . . configuring with CLI . . . . . . . . . . SNMPv1 . . . . . . . . . . . . . . . SNMPv2c . . . . . . . . . . . . . . SNMPv3 . . . . . . . . . . . . . . . Spanning Tree Protocol . . . . .
Index 238 Installation and Configuration Guide Avaya C360 Multilayer Stackable Switches, version 4.