Documentation Roadmap Avaya Ethernet Routing Switch 4500 Series

Transcription

1 Documentation Roadmap Avaya Ethernet Routing Switch 4500 Series 5.4 NN , November 2010

2 2010 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes. Documentation disclaimer Documentation means information published by Avaya in varying mediums which may include product information, operating instructions and performance specifications that Avaya generally makes available to users of its products. Documentation does not include marketing materials. Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of documentation unless such modifications, additions, or deletions were performed by Avaya. End User agrees to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User. Link disclaimer Avaya is not responsible for the contents or reliability of any linked Web sites referenced within this site or documentation provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages. Warranty Avaya provides a limited warranty on its Hardware and Software ( Product(s) ). Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language, as well as information regarding support for this Product while under warranty is available to Avaya customers and other parties through the Avaya Support Web site: Please note that if you acquired the Product(s) from an authorized Avaya reseller outside of the United States and Canada, the warranty is provided to you by said Avaya reseller and not by Avaya. Licenses THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA AUTHORIZED RESELLER; AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS YOU AND END USER ), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE ( AVAYA ). Copyright Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation, Software, or Hardware provided by Avaya. All content on this site, the documentation and the Product provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and software unless expressly authorized by Avaya. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a criminal, as well as a civil offense under the applicable law. Third-party components Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements ( Third Party Components ), which may contain terms that expand or limit rights to use certain portions of the Product ( Third Party Terms ). Information regarding distributed Linux OS source code (for those Products that have distributed the Linux OS source code), and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Web site: Trademarks The trademarks, logos and service marks ( Marks ) displayed in this site, the Documentation and Product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, or other third parties. Users are not permitted to use such Marks without prior written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the Documentation and Product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party. Avaya is a registered trademark of Avaya Inc. All non-avaya trademarks are the property of their respective owners, and Linux is a registered trademark of Linus Torvalds. Downloading Documentation For the most current versions of Documentation, see the Avaya Support Web site: Contact Avaya Support Avaya provides a telephone number for you to use to report problems or to ask questions about your Product. The support telephone number is in the United States. For additional support telephone numbers, see the Avaya Web site: 2 Documentation Roadmap November 2010

3 Contents Chapter 1: Customer service...5 Getting technical documentation...5 Getting product training...5 Getting help from a distributor or reseller...5 Getting technical support from the Avaya Web site...6 Chapter 2: New in this release...7 Features...7 Other changes...8 Chapter 3: Introduction...11 Navigation...11 Chapter 4: Roadmap...13 Navigation...13 New features in Release Customer documentation packaging...23 Product Fundamentals...24 Installation and Commissioning...25 Upgrades and Patches...26 Operations...26 Administration and Security...27 Fault and Performance Management...28 Documentation file formats...28 Chapter 5: Information quality...29 Chapter 6: Text conventions...31 Navigation...31 Angle brackets...31 Bold or Bold Courier text...32 Braces...32 Brackets...32 Ellipses...33 Italic text...33 Plain Courier text...33 Separator...33 Vertical bar...33 cr convention...34 Chapter 7: Modular, task-based information...35 Navigation...35 Task-based documentation...35 How to use task-based documentation...36 Task flow overview...37 Work flows, task flows, and procedures...37 Task-based documentation terms...38 Documentation Roadmap November

4 4 Documentation Roadmap November 2010

5 Chapter 1: Customer service Visit the Avaya Web site to access the complete range of services and support that Avaya provides. Go to or go to one of the pages listed in the following sections. Navigation Getting technical documentation on page 5 Getting product training on page 5 Getting help from a distributor or reseller on page 5 Getting technical support from the Avaya Web site on page 6 Getting technical documentation To download and print selected technical publications and release notes directly from the Internet, go to Getting product training Ongoing product training is available. For more information or to register, you can access the Web site at From this Web site, you can locate the Training contacts link on the left-hand navigation pane. Getting help from a distributor or reseller If you purchased a service contract for your Avaya product from a distributor or authorized reseller, contact the technical support staff for that distributor or reseller for assistance. Documentation Roadmap November

6 Customer service Getting technical support from the Avaya Web site The easiest and most effective way to get technical support for Avaya products is from the Avaya Technical Support Web site at 6 Documentation Roadmap November 2010

7 Chapter 2: New in this release The following sections detail what s new in Avaya Ethernet Routing Switch 4500 Series Documentation for Release 5.4 Features on page 7 Other changes on page 8 Features See the following sections for information about new features in Release AB (LLDP) Network Policy CLI on page D compliancy on page 14 ADAC Enhancements on page 14 Additional SFP Support on page 14 Auto QoS 802.1AB MED Interoperability on page 15 Auto QoS ADAC Interoperability on page 16 DHCP Client on page 16 DHCP option 82 on page 16 DHCP snooping improvements on page 16 Dual Syslog Server Support on page 17 EAP MHMA multivlan enhancement on page 17 Energy Saver on page 17 IPFIX on page 18 L3 Dynamic Routing Table Allocation on page 18 L3 Non Local Static Routes (NLSR) on page 18 L3 Open Shortest Path First (OSPF) on page 18 L3 Routing Information Protocol (RIP) on page 19 L3 Routing Policies on page 19 MLT Hash Calculation on page 19 MLT/LAG Scaling (32/8) on page 19 Documentation Roadmap November

8 New in this release QoS Agent enable/disable on page 20 QoS DSCP Mutation on page 20 QoS Egress Queue Shaping on page 20 QoS traffic profile filter set support on page 20 QoS Extended IP/L2 Filters on page 21 QoS Queue Set Support on page 21 QoS Traffic Profile Filter Set on page 21 RADIUS Accounting (RFC2866) on page 21 Show and copy running-config enhancements on page 22 Show software status on page 22 Software Licensing on page 22 Sticky MAC address on page 23 Time Domain Reflectometer on page 23 Other changes See the following sections for information about changes that are not feature-related: Enterprise Device Manager on page 8 Enterprise Device Manager Enterprise Device Manager (EDM) replaces both the Java-based Device Manager and Webbased management user interfaces. EDM is an embedded element management and configuration application for Avaya Ethernet Routing Switch 4500 Series switches. EDM provides a Web-based graphical user interface through a standard Web browser for the convenience of full configuration and management on the switch, and retains the look and feel of Device Manager. Multiple Port Configuration Among the many functions available in EDM, you can configure port-specific features for a single port, a group of ports, or all ports. Multiple Port Configuration appears as a pane in the work area wherever this function is available. By default the pane appears and you can close and open it with a click of the task bar. 8 Documentation Roadmap November 2010

9 Other changes You can also select a single port, a group of ports, or the entire switch on the EDM Device Physical View. To select items on the Device Physical View you can click the entire switch, click a port, Ctlr+click to select more than one port, or click and drag to select a group of ports. For more information about EDM, see Avaya Ethernet Routing Switch 4500 Series Fundamentals (NN ). Documentation Roadmap November

10 New in this release 10 Documentation Roadmap November 2010

11 Chapter 3: Introduction This document explains the organization of the technical documentation for the Avaya Ethernet Routing Switch 4500 Series Release 5.4. Use this document to understand where you can find specific types of information in the customer documentation suite. Navigation Roadmap on page 13 Information quality on page 29 Text conventions on page 31 Modular, task-based information on page 35 Customer service on page 5 Documentation Roadmap November

12 Introduction 12 Documentation Roadmap November 2010

13 Chapter 4: Roadmap This section is a roadmap for the Avaya Ethernet Routing Switch 4500 Series documentation. Use this section to find the correct document for the task you need to perform. Avaya Ethernet Routing Switch 4500 Series technical documents are structured with an emphasis on the tasks you perform. Navigation New features in Release 5.4 on page 13 Customer documentation packaging on page 23 Product Fundamentals on page 24 Installation and Commissioning on page 25 Upgrades and Patches on page 26 Administration and Security on page 27 Operations on page 26 Fault and Performance Management on page 28 Documentation file formats on page 28 New features in Release 5.4 This section describes the new features supported on the Avaya Ethernet Routing Switch 4500 Series switches AB (LLDP) Network Policy CLI You can configure 802.1AB MED network policies to dynamically configure voice VLAN, DSCP, priority, and VLAN tagging on the switch for voice traffic received from an IP phone. When you enable LLDP and configure the MED network policies on the switch, the switch sends the network policies to the IP Phone. The IP phone processes the data in the LLDP PDU Documentation Roadmap November

14 Roadmap and transmits the voice traffic with the appropriate VLAN ID, VLAN tagging, DSCP and priority information. You can configure MED network policies on a switch port that has ADAC enabled. The network policies have priority over the ADAC configuration on the port D compliancy To prevent broadcast storms in a complex network, when a port drops and comes back up frequently you can use 802.1D Compliance mode. When you configure 802.1D compliance mode, the system sets the Spanning Tree Protocol (STP) state of the port to disabled when the port link is down. ADAC Enhancements ADAC Enhancements provide increased flexibility in deployments that use Auto-Detect Auto- Configuration (ADAC) as follows: expanded support for up to 8 ADAC uplinks and 8 call-server links individual ports or any combination of MLT, DMLT or LAG per switch or stack the ability to change the non-adac VLANs on a port without disabling ADAC Additional SFP Support The following table lists the additional SFPs supported by Avaya ERS 4500 Release 5.4. Avaya PEC AA E6 AA E6 AA E6 AA E6 Description 1-port 1000BaseXD DDI SFP (connector: LC) nm. 1-port 1000BaseXD DDI SFP (connector: LC) nm. 1-port 1000BaseZX DDI SFP (connector: LC) nm. 1-port 1000BaseCWDM SFP (connector: LC) nm, 40km. AA E6 1-port 1000BaseCWDM DDI SFP (connector: LC) nm, 40km. AA E6 1-port 1000BaseCWDM DDI SFP (connector: LC) nm, 40km. AA E6 1-port 1000BaseCWDM DDI SFP (connector: LC) nm, 40km. AA E6 1-port 1000BaseCWDM DDI SFP (connector: LC) nm, 40km. 14 Documentation Roadmap November 2010

15 New features in Release 5.4 Avaya PEC Description AA E6 1-port 1000BaseCWDM DDI SFP (connector: LC) nm, 40km. AA E6 1-port 1000BaseCWDM DDI SFP (connector: LC) nm, 40km. AA E6 1-port 1000BaseCWDM DDI SFP (connector: LC) nm, 40km. AA E6 1-port 1000BaseCWDM DDI SFP (connector: LC) nm, 70km. AA E6 1-port 1000BaseCWDM DDI SFP (connector: LC) nm, 70km. AA E6 1-port 1000BaseCWDM DDI SFP (connector: LC) nm, 70km. AA E6 1-port 1000BaseCWDM DDI SFP (connector: LC) nm, 70km. AA E6 1-port 1000BaseCWDM DDI SFP (connector: LC) nm, 70km. AA E6 1-port 1000BaseCWDM DDI SFP (connector: LC) nm, 70km. AA E6 1-port 1000BaseCWDM DDI SFP (connector: LC) nm, 70km. AA E6 1-port 1000BaseCWDM DDI SFP (connector: LC) nm, 70km. AA E6 1-port 1000Base DDI SFP (connector: LC) nm, 120km. Auto QoS 802.1AB MED Interoperability Auto QoS 802.1AB MED Interoperability enhances Automatic QoS implementation on the switch so you can use both features simultaneously. If you configure 802.1AB MED, the switch publishes the private Automatic QoS DSCP value to the end device rather than the default value defined by the network policy. If Automatic QoS (formerly called NT-on-NT QoS) is enabled on a port, when 802.1AB MED is configured, the switch publishes the private NT-on-NT DSCP value to the end device rather than the default as defined by the network policy. When you enable Auto QoS and 802.1AB is notified, the network policy DSCP changes the output to 0x2F. If you disable Auto QoS, the network policy reverts to the previous/default setting. You can set the network policy DSCP after you configure Auto QoS; these changes are considered a temporary change to the network policy DSCP value on a per port basis. So when you restart the switch, the network policy DSCP value reverts to the Auto QoS value of 0x2F, Documentation Roadmap November

16 Roadmap and the temporary network policy DSCP value is lost. If you disable Auto QoS, the network policy DSCP reverts to the per port settings which were present before you enabled Auto QoS. Auto QoS ADAC Interoperability With Release 5.4 you can use Automatic QoS and ADAC simultaneously on a port. That is, you can enable ADAC and configure Automatic Qos on the same port so that ADAC can use the Automatic QoS DSCP markings. DHCP Client You can configure the switch to use Dynamic Host Configuration Protocol (DHCP) Client as an alternative method to bootp, or other means, to configure the switch to assign an IPv4 address to the management VLAN. When you use DHCP Client, the switch can retrieve IP address, netmask, default gateway, and Domain Name Server (DNS) information for a maximum of three DNS servers. Because the switch should not perform as a DHCP relay while DHCP client is operating, DHCP client operates only when the switch is started up. DHCP option 82 DHCP option 82 is an extension of Dynamic Host Configuration Protocol (RFC3046 and RFC3993) that enables the switch to send information about DHCP clients to the authenticating DHCP server. When you enable option 82, in either Layer 2 or Layer 3 mode, the switch inserts additional port-based identification information into the DHCP packets traversing the switch enroute to the DHCP server. The DHCP server stores this additional identification information within the IP allocation record to assist in tracking of end device locations. When a VLAN is operating in Layer 2 mode, you must first enable DHCP Snooping to use DHCP Option 82. When a VLAN is operating in Layer 3 (IP Routing) mode, you must configure DHCP Relay globally on the switch and client VLANs to use DHCP Option 82. DHCP snooping improvements Release 5.4 adds DHCP Snooping Improvements that include: a larger DHCP Snooping table 1024 entries for each unit or stack that better supports IP Phone and PC deployment the ability to manually add entries to, or delete entries from, the DHCP snooping table so that you can protect statically configured IP devices with applications that rely on DHCP 16 Documentation Roadmap November 2010

17 New features in Release 5.4 Snooping table entries; applications such as Dynamic ARP Inspection (DAI) and IP Source Guard (IPSG) Dual Syslog Server Support You can use the Dual Syslog Server Support feature to configure a second syslog server to run in tandem with the first. If you configure Dual Syslog Server Support, the system sends syslog messages simultaneously to both servers to ensure that syslog messages are logged, even if one of the servers becomes unavailable. EAP MHMA multivlan enhancement In this release you can assign multiple EAP and non-eap hosts to different VLANs on the same port. Energy Saver Avaya Energy Saver (AES) can reduce network infrastructure power consumption without impact to network connectivity. AES reduces direct power consumption by up to 40% because it uses intelligent switching capacity reduction in off-peak mode. AES can also use Power over Ethernet (PoE) port power priority levels to shut down PoE ports and provide more power savings. You can configure AES using ACLI and EDM. Enterprise Device Manager Enterprise Device Manager (EDM) replaces both the Java-based Device Manager and Webbased management user interfaces. EDM is an embedded element management and configuration application for Avaya Ethernet Routing Switch 4500 Series switches. EDM provides a Web-based graphical user interface through a standard Web browser for the convenience of full configuration and management on the switch, and retains the look and feel of Device Manager. Erasable ACLI audit log Release 5.4 introduces ACLI commands to preserve or erase the contents of the ACLI audit log. Documentation Roadmap November

18 Roadmap IPFIX With Release 5.4 IP Flow Information export (IPFIX) is part of the Base License of the Avaya Ethernet Routing Switch 4500 Series. You can use IPFIX to monitor traffic flows when you configure observation points to collect flow statistics over specified time periods. The ERS 4500 IPFIX implementation supports the Netflow 9 export type. Other types, including Avaya IP Flow Manager, NetQoS Harvester, and Fluke Collector have been tested for compatibility. L3 Dynamic Routing Table Allocation With Release 5.4 ERS 4500 supports dynamic routing protocols such as RIPv1/v2, OSPFv2, and Route Policies. The maximum routing table implemented in the Avaya ERS 4500 hardware is 512 maximum route entries. This feature allows you to manually configure the 510 IPv4 route entries between the routing protocols. For example, you can distribute entries for local routes (IPV4 VLAN interfaces) and entries for static routes (including non-local static). The remaining route entries will be available for dynamic routing protocols (RIP and OSPF). L3 Non Local Static Routes (NLSR) NLSR manages static routes where the next hop is not local and is reachable through another route, and when there are multiple paths to a network. Where there are two or more ways to reach a network, NLSR reduces the number of static routes by adding only one static route with a remote gateway. When a non-local route is added to the best route, the non-local next hop is retrieved from the routing table and the information is used to add the new static route. L3 Open Shortest Path First (OSPF) L3 Open Shortest Path First (OSPF) is a dynamic routing protocol that discovers network topology and calculates the shortest path to each destination based on cumulative cost. OSPF can reduce central processing unit (CPU) and memory resource requirements in a large network by partitioning the network into contiguous areas. OSPF supports authentication to guard against attack. You must install an Advanced License to use OSPF. 18 Documentation Roadmap November 2010

19 New features in Release 5.4 L3 Routing Information Protocol (RIP) Layer 3 Routing Information Protocol (RIP) RIPv1 and RIPv2 (RFC 1058 and RFC 2453) provides a simple distance vector interior gateway protocol you can use for dynamic routing in smaller networks. RIP is used to discover routes in a network based on information from directly-connected routers. RIP implementation can be useful in large networks where static route administration is impractical. RIP adds routes to networks in the routing table, but has no image of the overall network because it relies on neighbor information. L3 Routing Policies Release 5.4 supports the following routing policies: In/Accept policies can be applied to incoming route updates before they are added to the routing table. For RIP, In/Accept policies can be applied to all incoming packets with one policy for each RIP interface. For OSPF, In/Accept policies can be applied to external routes based on the advertising router ID, and there is only one policy for the entire switch. In/Accept policies are applied before addition to the routing table from the OSPF Link State Database (LSDB). Out/Announce policies are applied to outgoing route updates before the route packets are sent. For RIP, Out/Announce policies can be applied to all outgoing packets and have one policy for each RIP interface. There is no Out/Announce policy supported for OSPF. Redistribute policies provide notification when a route is added to, or deleted from, the route table. RIP does not support Redistribute policies. For OSPF, redistributed routes are sent as external routes and there is one policy for the entire switch or stack. MLT Hash Calculation New ACLI commands can calculate which link of a MultiLink Trunk, Distributed MultiLink Trunk, or Link Aggregation Group a packet will traverse within the switch. MLT/LAG Scaling (32/8) MultiLink Trunking (MLT) and Link Aggregation Group (LAG) scaling supports up to 32 trunk groups with up to 8 links per trunk for MLT, Distributed MultiLink Trunking (DMLT) and 802.3AD LAG. Documentation Roadmap November

20 Roadmap QoS Agent enable/disable You can enable or disable QoS Agent using ACLI to provide a straightforward method to enable or disable all QoS functions on a switch or stack to allow easier repair of QoS configurations. QoS DSCP Mutation In the current QoS implementation of Trusted interface class, the IPv4 traffic received on trusted interfaces is remarked at the layer 2 level; that is, the 802.1p user priority value is updated based on the DSCP value in the packet at ingress and the installed DSCP-to-CoS mapping data. The remarked CoS value is used for queuing at egress and, possibly, for downstream packet processing in a tagged VLAN environment. In some cases, you may need to remark the packet DSCP value at egress, based on the incoming DSCP value at ingress. With Release 5.4 you can use the DSCP mutation operation to define individual filters to match and remark targeted DSCP values. You can easily extend the DSCP-to-COS Mapping Table to specify DSCP mutation values and to apply values automatically on Trusted interfaces. QoS Egress Queue Shaping ERS 4500 supports both port-based shaping and per-port per-egress queue shaping. With Release 5.4, you can implement egress queue shaping to provide control on a per queue by queue basis. This enhancement allows the flow to be shaped at a CoS level. QoS traffic profile filter set support QoS traffic profile filter set support offers the advantages of generic filter sets that combine Layer 2 and Layer 3 options into a single set. The following are some characteristics of QoS traffic profile filter set support: The filter sets can be associated with policy-based or classifier-based metering criteria (for either individual filters or blocks of filters). Filter set components (filters and actions) can be added or deleted while the filter set is associated with a port. Multiple filter sets can be applied to a port. Streamlined filter, meter and action definition. Automatic precedence assignment. 20 Documentation Roadmap November 2010

21 New features in Release 5.4 QoS traffic profile filter set metering You can use policy-based and classifier-based metering modes with traffic profile sets, for either individual filters or blocks of filters. QoS Extended IP/L2 Filters Release 5.4 introduces the following configurable QoS IP and L2 filtering options: New Layer3 (IP) filtering options IPv4 Flags, TCP Control Flags, and IPv4 Options Additional Layer2 filtering options Frame Tag, Frame Type, Inner VLAN ID Existing packet type filtering options Unknown IP Multicast, Known IP Multicast, Unknown Non-IP Multicast, Known Non-IP Multicast, Non-IP Traffic QoS Queue Set Support With Release 5.4, you can configure up to 8 queues and also configure queue set allocation. The default queue set allocation is 2 queues with medium allocation. A QoS queue set is used to logically represent the queuing capabilities associated with an egress QoS interface. A queue set is comprised of a number of related queuing components that dictate the queuing behavior supported by the set itself. QoS Traffic Profile Filter Set Release 5.4 introduces configuration and control of generic filter sets. Generic filter sets allow combinations of Layer 2 and Layer 3 options into a single set. Avaya Ethernet Routing Switch 4500 Series also supports filter set templates for NSNA and User Based Policy (UBP) applications. A filter set is a collection of individual classifiers, classifier blocks, and the associated actions and metering criteria. Filter sets act as a template applied to an interface based on internal or external events. Filter sets can be associated with metering criteria that is applied to all filter set policies. You can add or delete filter set components while the filter set is in use, for example - associated with a port. You can also apply multiple filter sets per port. RADIUS Accounting (RFC2866) The switch can use enhancements to RADIUS Accounting (RFC2866), in particular, the Framed-IP-Address attribute, to send detailed RADIUS accounting updates to the RADIUS Documentation Roadmap November

22 Roadmap server. You can use this feature to improve integration with the Avaya Identity Engines security platform. RADIUS server reachability You can use RADIUS server reachability to configure the switch to use ICMP packets or dummy RADIUS requests to determine the reachability of the RADIUS server. Show and copy running-config enhancements The operation of the show running-config ACLI command has been modified. By default, show running-config displays only parameters that differ from the default configuration. With Release 5.4, you can use the verbose qualifier to display the entire ASCII configuration for the switch or stack, or you can use the module qualifier in the command to display the ASCII configuration for a specific feature. The operation of the copy running-config tftp ACLI command has been modified. By default, copy running-config tftp copies the complete contents of the running configuration file to a specified file on the TFTP server. With Release 5.4, you can use the module qualifier in the command to display the ASCII configuration for a specific feature, or you can use the verbose qualifier to copy the entire ASCII configuration for the switch or stack. The operation of the copy running-config usb ACLI command has been modified. By default, copy running-config usb copies the complete contents of the running configuration file to a USB mass storage device. With Release 5.4, you can use the module qualifier in the command to display the ASCII configuration for a specific feature, or you can use the verbose qualifier to copy the entire ASCII configuration for the switch or stack. Show software status You can display the currently loaded and operational switch or stack software status for both agent and diagnostic loads. With the show boot ACLI command and variables, you can view the agent or diagnostic load status individually, or together. The Boot Image, EDM tab displays agent and diagnostic load status information together. Software Licensing Software Licensing provides a mechanism to license a set of product features based on the license you purchase. Release 5.4 introduces Advanced licensing to enable Open Shortest Path Protocol (OSPF). 22 Documentation Roadmap November 2010

23 Customer documentation packaging With Release 5.4, the licensing feature is enhanced to make licensing easy when upgrading the switch or replace units in a stack, including the Base Unit. The group based licensing corresponds to the current licensing level. Every feature falls under a particular licensing level. There are three levels of license Basic, Advanced, and Premier. When you apply a license, you get access to all features that belong to that license level and the lower level licenses. For example if you apply an Advanced License, then you will get access to all the features of Basic and Advanced. If you apply a Premier License, then all the features of Basic, Advanced and Premier are accessible. By default, the switch is ships with the Basic License. Sticky MAC address Sticky MAC address enhances MAC address security if you require a high level of control and simpler configuration and operation. Sticky MAC address secures the MAC address to a specified port so that if the address moves to another port, the system raises an intrusion event. When you use Sticky MAC address, the switch performs initial auto-learning of MAC addresses and can store the automatically learned addresses across switch reboots. Time Domain Reflectometer The Time Domain Reflectometer (TDR) is a diagnostic tool that you can use to test connectivity of copper Ethernet cables connected to the switch port. You can perform cable diagnostics on any port in the switch or stack, and you can initiate multiple port tests simultaneously. You can initiate TDR tests and obtain test results from ACLI or EDM. Customer documentation packaging Avaya technical documents are organized according to job functions. For information about how the Avaya Ethernet Routing Switch 4500 Series documentation suite is organized, see the following figure. Documentation Roadmap November

24 Roadmap Figure 1: Avaya Ethernet Routing Switch 4500 Series documentation packaging Product Fundamentals Product Fundamentals documentation includes product overview and information that applies to all areas of the product. Table 1: Avaya Ethernet Routing Switch 4500 Series product fundamentals documents Document title Avaya Ethernet Routing Switch 4500 Series Regulatory Information,NN Avaya Ethernet Routing Switch 4500 Series Documentation Roadmap, NN Avaya Ethernet Routing Switch 4500 Series Fundamentals, NN Description This document provides regulatory and precautionary messages applicable to the Avaya Ethernet Routing Switch 4500 Series. This document contains an overview of the documentation suite and explains how to use task-based documentation. This document provides instructions to use the Avaya Ethernet Routing Switch Documentation Roadmap November 2010

25 Installation and Commissioning Document title Avaya Ethernet Routing Switch 4500 Series Terminology, NN Description Series user interfaces, including Avaya command line interface (ACLI) and Enterprise Device Manager (EDM), and includes procedures to use configuration files. This document contains common terms and acronyms used in the Avaya Ethernet Routing Switch 4500 Series documentation suite. Installation and Commissioning Installation and Commissioning documentation includes information that supports initial installation and commissioning (initial configuration) activities, including preparation, processes, safety requirements, and instructions for rollback procedures. The following table describes Avaya Ethernet Routing Switch 4500 Series installation and commissioning documents. Table 2: Avaya Ethernet Routing Switch 4500 Series installation and commissioning documents Document title Avaya Ethernet Routing Switch 4500 Series Installation, NN Avaya Ethernet Routing Switch 4500 Series Installation SFPs and XFPs, NN Avaya Ethernet Routing Switch 4500 Series Configuration System, NN Description This document provides instructions to install the Avaya Ethernet Routing Switch 4500 Series in an equipment rack (individually or in a stack) or on a shelf. It also provides instructions to perform the initial IP configuration on the switch using CLI, BootP, or the IP.CFG file. It also provides instructions to verify the switch status using the front-panel LEDs. This document provides instructions to install small form factor pluggable transceivers, 10 Gigabit small form factor pluggable transceivers, and includes specifications for these hardware components. This document provides instructions to perform basic configuration of the Avaya Ethernet Routing Switch 4500 Series including procedures to configure the switch IP address after hardware installation. It also provides instructions to configure system- Documentation Roadmap November

26 Roadmap Document title Description level features such as stacking, feature licensing, Simple Network Time Protocol, BootP, Domain Name System, PoE, and LLDP. Upgrades and Patches Upgrades and Patches documentation includes information to upgrade software and hardware components. The Avaya Ethernet Routing Switch 4500 Series documentation suite does not contain a separate document for Upgrades and Patches. For information about changing switch software, see Avaya Ethernet Routing Switch 4500 Series Configuration System, NN Information about updating switch software also appears in Avaya Ethernet Routing Switch 4500 Series Release Notes, NN The following table describes Avaya Ethernet Routing Switch 4500 Series upgrades and patches documents. Table 3: Avaya Ethernet Routing Switch 4500 Series upgrades and patches documents Document title Avaya Ethernet Routing Switch 4500 Series Release Notes, NN Description This document describes new features and important information about the latest release. Release Notes includes a list of known issues (including workarounds where appropriate) and a list of fixed issues. Operations Operations documents include information that supports tasks related to configuration (postcommissioning) of services or applications, routine maintenance of hardware or software, and accounting or billing activities. The following table describes Avaya Ethernet Routing Switch 4500 Series operations documents. 26 Documentation Roadmap November 2010

27 Administration and Security Table 4: Avaya Ethernet Routing Switch 4500 Series operations documents Document title Avaya Ethernet Routing Switch 4500 Series Configuration VLANs, Spanning Tree, and Multi-Link Trunking, NN Avaya Ethernet Routing Switch 4500 Series Configuration Quality of Service, NN Avaya Ethernet Routing Switch 4500 Series Configuration IP Routing and Multicast, NN Description This document describes procedures and conceptual information to configure VLANs, Spanning Tree, Link Aggregation Control Protocol, and Multi-Link Trunking on the Avaya Ethernet Routing Switch 4500 Series. This document provides procedures and conceptual information to configure Quality of Service on the Avaya Ethernet Routing Switch 4500 Series. This document provides procedures and conceptual information to configure IP routing features on the Avaya Ethernet Routing Switch 4500 Series, including static routes, Proxy ARP, DHCP Relay, and UDP forwarding. It also provides procedures and conceptual information to manage multicast traffic using IGMP snooping. Administration and Security Administration and Security documentation includes information that supports tasks that operations personnel perform that relate to network administration or product security, including the configuration and management of systems data and users. The documentation also includes the management and protection of resources from unauthorized or detrimental access and use. The following table describes Avaya Ethernet Routing Switch 4500 Series administration and security documents. Table 5: Avaya Ethernet Routing Switch 4500 Series administration and security documents Document title Avaya Ethernet Routing Switch 4500 Series Configuration Security, NN Description This document provides procedures and conceptual information to administer and configure security features for the Avaya Ethernet Routing Switch 4500 Series, including MAC-based security, RADIUS, EAPOL, SSH, and NSNA. Documentation Roadmap November

28 Roadmap Fault and Performance Management Fault and Performance Management documents include information that supports the tasks that operations personnel perform that relate to managing or preventing faults, troubleshooting, and monitoring and improving the performance of the network or product The following table describes Avaya Ethernet Routing Switch 4500 Series fault and performance management documents. Table 6: Avaya Ethernet Routing Switch 4500 Series fault and performance management documents Document title Avaya Ethernet Routing Switch 4500 Series Configuration System Monitoring, NN Avaya Ethernet Routing Switch 4500 Series Troubleshooting, NN Description This document provides information about system diagnostics tools including syslog, Remote Monitoring, port mirroring, and displaying port and chassis statistics. This document describes common problems and error messages and the techniques to resolve them. Documentation file formats To locate the Avaya Ethernet Routing Switch 4500 Series software Release 5.4 documentation on the Avaya Web site, see Customer service on page 5, or the documentation CD. The following document is also available in print format: Avaya Ethernet Routing Switch 4500 Series Regulatory Information, NN Documentation Roadmap November 2010

29 Chapter 5: Information quality Avaya technical documents are tested by subject matter experts (SMEs) throughout the product development lifecycle. SMEs from Design, Product Verification (PV), Product Line Management (PLM), Verification Office (VO), and Global Network Product Support (GNPS), all contribute to document quality. Avaya releases technical documents in the early stages of development that have not completed all testing milestones, on a limited basis. Documents that have not completed testing bear a Draft watermark on every page to indicate that the content they contain may change as the product is refined and document testing is completed. Draft documents are not widely available. Documentation Roadmap November

30 Information quality 30 Documentation Roadmap November 2010

31 Chapter 6: Text conventions This chapter describes the text conventions used in the Avaya Ethernet Routing Switch 4500 Series documentation. Navigation Angle brackets on page 31 Bold or Bold Courier text on page 32 Braces on page 32 Brackets on page 32 Ellipses on page 33 Italic text on page 33 Plain Courier text on page 33 Separator on page 33 Vertical bar on page 33 cr convention on page 34 Angle brackets Indicates that you choose the text to enter based on the description inside the brackets. Do not type the brackets when entering the command. Example: If the command syntax is ping <ip_address>, you enter ping Documentation Roadmap November

32 Text conventions Bold or Bold Courier text Bold or Bold Courier text indicates command names. Example 2 displays how text that you must type appear. Example 3 displays how file paths appear. Example Use the info command. Example Enter show ip {alerts routes}. Example Protocols > IP identifies the IP command on the Protocols menu. Braces Braces ({ }) indicate required elements in syntax descriptions where more than one option is available. You must choose only one option. Do not type the braces when you enter the command. Example: If the command syntax is show ip {alerts routes}, you must enter either show ip alerts or show ip routes, but not both. Brackets Brackets ([ ]) indicate optional elements in syntax descriptions. Do not type the brackets when you enter the command. Example: If the command syntax is show ip interfaces [-alerts], you can enter either show ip interfaces or show ip interfaces -alerts. 32 Documentation Roadmap November 2010

33 Ellipses Ellipses An ellipsis (...) indicates that you repeat the last element of the command as needed. Example: If the command syntax is ethernet/2/1 [ <parameter> <value> ]..., you enter ethernet/2/1 and as many parameter-value pairs as you need. Italic text Italic text indicates book titles or new terms followed by a definition. Example: Avaya Ethernet Routing Switch 4500 Series Release Notes, NN Plain Courier text Plain Courier text indicates system output, for example, prompts and system messages. Example: Set Trap Monitor Filters Separator A separator ( >) shows menu paths. Example: Protocols > IP identifies the IP command on the Protocols menu. Vertical bar A vertical bar ( ) separates choices for command keywords and arguments. Enter only one choice. Do not type the vertical line when you enter the command. Example: If the command syntax is show ip {alerts routes}, you enter either show ip alerts or show ip alerts, but not both. Documentation Roadmap November

34 Text conventions cr convention In ACLI procedures, when you see <cr> as an option for a command, you can press the Enter key on your keyboard to execute the command. 34 Documentation Roadmap November 2010

35 Chapter 7: Modular, task-based information Modular, task-based information (MTBI) is a quick reference for using the Avaya Ethernet Routing Switch 4500 Series task-based documentation. MTBI describes the structure of task-based information and how it can be used most effectively. Navigation Task-based documentation on page 35 How to use task-based documentation on page 36 Task flow overview on page 37 Work flows, task flows, and procedures on page 37 Task-based documentation terms on page 38 Task-based documentation Task-based documentation is a new way of packaging customer information in a structured, modular, task-centric format. Task-based documentation focuses on what the user must do and the sequence in which to perform tasks. The goal is to make Avaya documentation easy to find, easy to use, timely, and accurate. The following figure describes the relationship between work flows, task flows, and procedures. Documentation Roadmap November

36 Modular, task-based information Figure 2: Work flows, task flows, and procedures in task-based documentation How to use task-based documentation In task-based documentation, procedural information is included in the document. Conceptual and reference information is provided, and the user is guided on how to use conceptual and reference material by identified prerequisites or direct links and references. The user navigates the information by following the flows that are provided for tasks and procedures. 36 Documentation Roadmap November 2010

37 Task flow overview Task flow overview Task flows are flowcharts that illustrate which procedures and decisions are involved to complete an activity. The task flows guide you through activities to use the Avaya Ethernet Routing Switch 4500 Series, whether it is configuration, upgrading, installation, maintenance, or troubleshooting. Each flow provides the prerequisites and links to the tasks or procedures. To perform or refer to a procedure, always follow the task flow. Following the task flows ensures that you meet all the requirements for successful completion of the task. Work flows, task flows, and procedures Work flows, task flows, and procedures have similar elements to maintain consistency and usability. Each of the following sections have a specific function: Purpose statements on page 37 Prerequisites on page 37 Work flows or task flows on page 38 Procedure steps on page 38 Example procedures on page 38 Variable definitions on page 38 Job aid on page 38 To understand the relationship between work flows, task flows, and procedures, see Figure 2: Work flows, task flows, and procedures in task-based documentation on page 36. Purpose statements Purpose statements explain why or when you would perform a work flow, task, or procedure and impact. Prerequisites Prerequisites list everything you must do or understand before you start the workflow, task, or procedure. Prerequisites can include tasks that should already be completed, risks, Documentation Roadmap November

38 Modular, task-based information confirmation of system status, required knowledge, time estimates or limitations, and links to supporting information. The prerequisite section is omitted if no required prerequisites exist. Work flows or task flows This section is the flow chart diagram that represents the task flow with navigational links to the tasks or procedures in the flow. Procedure steps Procedures provide numerical steps that help you perform the procedure. Each step is a single action. Example procedures Some procedures use examples to show how to correctly perform the procedure with realistic settings. Variable definitions Variable definitions provide the possible values, ranges, or definitions of variables used in the procedure steps. If variables are not used in the procedure, then the variables definition section is omitted. Job aid Job aids provide information help to successfully perform the procedure. The job aid is only used when required. Task-based documentation terms The following table describes task-based documentation terms. 38 Documentation Roadmap November 2010

39 Task-based documentation terms Work flow Task or task flow Procedure Step Variable Term Description A high or top-level group of tasks. A logical group of procedures represented as a single action in a flowchart diagram. Complex tasks can be divided into simpler tasks or subtasks. A logical group of single action steps in a task. A single action performed in a procedure. A placeholder in procedure steps representing a value or definition. Restructuring Avaya technical documents into a task-based format is an ongoing initiative. The documentation for some Avaya products is already converted to the new format. Documentation Roadmap November

40 Modular, task-based information 40 Documentation Roadmap November 2010