User Guide Addendum for the Avaya P550R and P880 Multiservice Switches, Software Version 5.3.2

Transcription

1 User Guide Addendum for the Avaya P550R and P880 Multiservice Switches, Software Version Overview New Software Features This addendum provides information and procedures that will be added to later versions of the user documentation. Version of the application software is supported only by the M5501R-SUP (P550R) and M5500R-SUPA (P880) supervisor modules. This addendum is updated periodically with new information. To download the most current version of this document, see the support.avaya.com. Click Product Documentation. This addendum includes the following topics: New Software Features on page 1 Configuring Short-Lived IP Protocol Filters on page 2 Documentation Updates and Corrections on page 5 Technical Support on page 13 Documentation Feedback on page 13 Version provides support for the following new software feature: Short-lived protocol filters. This feature helps conserve the forwarding engine resources of the switch. By using a shortlived protocol filter, you can set the switch to use the slow 2002 Avaya, Inc. January 7,

2 User Guide Addendum for the Avaya P550R and P880, v5.3.2 path to route packets of a specific short-lived protocol. And by using the slow path to route short-lived protocol traffic, you conserve the resources of the forwarding engines. For information on how to configure short-lived protocol filters, see "Configuring Short-Lived IP Protocol Filters" on page 2. Configuring Short-Lived IP Protocol Filters Overview This feature helps conserve the forwarding engine resources of the switch. Depending on the configuration of your network, the forwarding cache may contain a high number of entries for shortlived protocols, for example, DNS and NTP. These short-lived protocol entries consume resources that could otherwise be used for data traffic of other protocols such as FTP, Telnet, HTTP, RealAudio, and online games. If the forwarding cache contains a high number of short-lived protocol entries, you can set the switch to use the slow path to route packets of a specific short-lived protocol. By using the slow path to route short-lived protocol traffic, you conserve the resources of the forwarding engines, which provide the fast in band routing engine (FIRE) and fast out of band routing engine (FORE). For information about the slow path and FIRE and FORE paths, see Routing Overview in Chapter 1, Introduction, of the Avaya P550R, P580, P880, and P882 Multiservice Switch User Guide, Version To configure short-lived protocol filters, your user account must be assigned one of the following access types: Read-write Administrator Custom access type that has read-write permission for the routing feature You can configure short-lived IP protocol filters only by using the CLI. This feature is not available in the Web Agent or SNMP. 2 January 7, 2003 Part No

3 Doc. No Enabling a Short-Lived IP Protocol Filter Overview If you enable a filter for a short-lived IP protocol, the switch uses the slow path to route packets of the protocol. For information about the slow path, see Routing Overview in Chapter 1, Introduction, of the Avaya P550R, P580, P880, and P882 Multiservice Switch User Guide, Version By default a filter is enabled for DNS and NTP packets. To route the packets of other short-lived protocols by means of the slow path, you must enable a filter for the protocol. Command To enable a filter for a short-lived IP protocol, enter Global Configuration mode and use the following command: ip short-lived {tcp udp} <port> Table 1. Keywords, Arguments, and Options Keyword, Argument, or Option {tcp udp} <port> Definition Enter tcp if the protocol that you want to filter uses a TCP port. Enter udp if the protocol that you want to filter uses a UDP port. The TCP or UDP port number that the protocol uses. Enter a port number from 0 through Examples To send all SNMP packets to supervisor module for slow path routing, enter the following command: ip short-lived udp 161 To send all BOOTP and DHCP packets to the supervisor for slow path routing, enter the following command: ip short-lived udp 67 ip short-lived udp 68 Disabling a Short-Lived IP Protocol Filter Overview If you disable a filter for a short-lived IP protocol, the switch uses either the fast in band routing engine (FIRE) path or the fast out of band routing engine (FORE) path to route packets of the protocol. Part No January 7,

4 User Guide Addendum for the Avaya P550R and P880, v5.3.2 For information about the FIRE and FORE paths, see Routing Overview in Chapter 1, Introduction, of the Avaya P550R, P580, P880, and P882 Multiservice Switch User Guide, Version Command To disable the filter for a short-lived IP protocol, enter Global Configuration mode and use the following command: no ip short-lived {tcp udp} <port> Table 2. Keywords, Arguments, and Options Keyword, Argument, or Option {tcp udp} <port> Definition Enter tcp if the protocol that you want to filter uses a TCP port. Enter udp if the protocol that you want to filter uses a UDP port. The TCP or UDP port number that the protocol uses. Examples To disable the short-lived IP protocol filter for DNS, enter the following command: no ip short-lived udp 53 To disable the short-lived IP protocol filter for NTP, enter the following command: no ip short-lived udp 123 Displaying Short-Lived IP Protocol Filters Command To display the short-lived IP protocol filters that are currently enabled, enter Global Configuration mode and use the following command: show ip short-lived Example After you enter the show ip short-lived command, the switch displays the filters that are currently enabled. For example: ip short-lived tcp 112 ip short-lived udp 53 ip short-lived udp January 7, 2003 Part No

5 Doc. No Documentation Updates and Corrections The following information will be added or changed in the next revision of the documentation for the Avaya P550R and P880 Multiservice switches. Avaya P550R, P580, P880, and P882 Multiservice Switch User Guide Using the Web Agent to Configure the Switch Creating IP Static Routes The following note will be added to Configuring the Switch Using the Web Agent in Chapter 2, Initialize and Setup. * Note: Use of Microsoft Internet Explorer Version 6.0 with Service Pack 1 is not currently supported. The following statement will be added to Creating a Static Route in Chapter 9, Configuring IP Routing. * Important: Do not create a static route to a local interface. This configuration is not supported. Protocol Event Log The following note will be added to Configuring the Protocol Event Log in Chapter 17, Monitoring the Avaya Multiservice Switch. * Important: If enabled, protocol event logging displays system messages that help Avaya Technical Support troubleshoot network problems. Avaya recommends that logging of protocol events be enabled only during troubleshooting sessions. If protocol event logging is enabled during normal network operation, the switch may display messages that users may incorrectly interpret as indications of protocol failures. For more information on advanced troubleshooting, see Chapter 17, Monitoring the Avaya Multiservice Switch, in the Avaya P550R, P580, P880, and P882 Multiservice Switch User Guide, Version VTP Snooping The following note will be added to Configuring VLAN Trunk Protocol (VTP) Snooping in Chapter 4, Using VLANs, Spanning Tree, Hunt Groups, and VTP Snooping. * Note: When VTP Snooping creates VLANs on the Avaya Multiservice switches, the hash table size for the VLANs Part No January 7,

6 User Guide Addendum for the Avaya P550R and P880, v5.3.2 is automatically set to 64. Depending on the number of VLANs that are created, you may need to manually change this hash table setting. For information on the relationship between hash table sizes and the number of VLANs that are configured on the switch, see Relationship between VLANs, AFT, and Hash Table Sizes, in Chapter 6, Managing the Address Forwarding Table. Remote Fault Detection The following information will be added to Configuring Physical Port Parameters on Gigabit Ports in Chapter 5, Configuring Port Parameters. Remote fault detection is a proprietary feature that prevents a loss of traffic if a physical or signaling error occurs on a switch-to-switch fiber link. A remote fault is an error that one switch can detect but the other switch cannot. For example, if a transmit fiber breaks, the remote port continues to receive data and so detects that the link is good. However, the remote port cannot detect that the data it transmits is not received by the local port. If remote fault detection is enabled and a remote fault occurs, the local switch sends a message to inform the remote switch of the fault. The remote switch then shuts down the remote port. If the receive signal is restored on the local port, the local port sends a message to the remote switch, which then turns on the remote port again. * Important: Remote fault detection must be enabled on both the local port and remote port for the feature to work. For example, in Figure 1: 1. Port 1 on Switch A is not receiving traffic from Port 2 on Switch B. This problem could occur because: The transmitter on port 2 is not functioning. The receiver on port 1 is not functioning. The fiber is broken or disconnected. 6 January 7, 2003 Part No

7 Doc. No Switch A detects the error condition and sends a message to Switch B, which shuts down Port 2. (When the port is shut down, its status changes from Okay to No Link. The port status is displayed in the Status field of the Physical Port Configuration Web page.) Figure 1. Remote fault detection Switch A, Port 1 Tx Rx X Rx Tx Switch B, Port 2 Enable remote fault detection on both ends of a switch-to-switch connection, in the following two cases: When two Gigabit ports that do not support auto-negotiation are connected. When a Gigabit port that supports auto-negotiation is connected to a Gigabit port that does not support autonegotiation. For a list of Gigabit modules that do not support auto-negotiation, see Table 5-3, Gigabit Modules Not Supporting Autonegotiation. Restrictions: Autonegotiation and remote fault detection cannot be enabled at the same time. To enable remote fault detection, autonegotiation must be disabled. When autonegotiation is enabled, remote fault detection is automatically disabled. If the switch is operating in Fabric mode 1, 80-series Gigabit modules support remote fault detection on only one port. If you enable remote fault detection on more than one port, a loss of traffic occurs. If the switch is operating in Fabric mode 2, 80-series Gigabit modules support remote fault detection on two ports; however, the ports must be on different fabric ports. If you enable remote fault detection on two ports that are on the same fabric port, a loss of data occurs. For information on the relationship between fabric ports and physical ports, see How Hunt Groups Load Share in Chapter 4, Using VLANs, Spanning Tree, Hunt Groups, and VTP Snooping. 50-series modules support remote fault detection on any number of ports. Part No January 7,

8 User Guide Addendum for the Avaya P550R and P880, v5.3.2 Command Reference Guide for the Avaya P550R, P580, P880, and P882 Multiservice Switches clear tcp The clear tcp command will be added to Chapter 10, IP. Command Mode: Global Configuration. Description: Ends the TCP session that you specify. Syntax: clear tcp [all local <local-ip-address> <local-tcp-port> remote <remote-ip-address> <remote-tcp-port> Keyword, Argument, or Option all local <local-ip-address> <local-tcp-port> remote <remote-ip-address> <remote-tcp port> Definition Ends all TCP sessions on the switch. Ends a specific TCP session on the local switch. The local IP address for which you want to end the TCP session. The local TCP port number for which you want to end the TCP session. The associated TCP session on the remote switch. The associated remote IP address for which you want to end the TCP session. The associated remote TCP port number for which you want to end the TCP session. Systems: Avaya P550R, P580, P880, and P882 Multiservice switches. set debug The set debug command will be added to Chapter 31, User Interface. Command Mode: Global Configuration. Description: Enables or disables debug mode. If enabled, this mode displays system messages that help Avaya Technical Support troubleshoot network problems. 8 January 7, 2003 Part No

9 Doc. No * Important: Avaya recommends that debug mode be enabled only during troubleshooting sessions. If debug mode is enabled during normal network operation, the switch may display messages that users incorrectly interpret as indications of system failures. For more information on advanced troubleshooting, see Chapter 17, Monitoring the Avaya Multiservice Switch, in the Avaya P550R, P580, P880, and P882 Multiservice Switch User Guide, Version By default, this mode is disabled. Syntax: set debug {on off} Keyword, Argument, or Option on off Definition Enables debug mode. Disables debug mode. Systems: Avaya P550R, P580, P880, and P882 Multiservice switches. show customaccess-type Command Mode: User. Description: Displays the custom access types that are currently configured on the switch. Syntax: show custom-access-type Sample Output: The following example displays the custom access types that are currently configured on a switch: Avaya>show custom-access-type Type Name Sys Cfg Mod Port Cfg Event Mgmt L2 Switching admin CAT Routing Part No January 7,

10 User Guide Addendum for the Avaya P550R and P880, v5.3.2 Systems: Avaya P550R, P580, P880, and P882 Multiservice switches. snmp-server community The following text replaces the text in snmp-server community of Chapter 25, SNMP. Command Mode: Global Configuration. Description: Sets up an SNMP community string. SNMP community strings control a management station's access to MIB objects. For more information about setting up SNMP communities, see Chapter 2, Initialize and Setup, in the Avaya P550R, P580, P880, and P882 Multiservice Switch User Guide, Version Syntax: To Create: snmp-server community <community-string> {ro rw none} [{normal admin <catname>}] [<ip-addr>] To Delete: [no] snmp-server community <community-string> Table 3. New Keywords, Arguments, and Options Keyword, Argument, or Option <community-string> {ro rw none} Definition The SNMP community string that you want to configure. The permission that you want to assign to the community string. Options are: ro Specifies read-only permission. Allows authorized management stations only to view MIB objects. rw Specifies read-write permission. Allows authorized management stations to view and modify MIB objects. none Specifies no permission. Allows management stations to neither view or modify MIB objects. 1 of 2 10 January 7, 2003 Part No

11 Doc. No Table 3. New Keywords, Arguments, and Options Keyword, Argument, or Option [{normal admin <catname>}] [<ip-addr>] Definition The security level that you want to assign the community string. Options are: normal Specifies that this community string can access all MIB objects except admin MIB objects. admin Specifies that this community string can access all MIB objects including admin MIB objects. <catname> The custom access type that you want to assign to the community string. The default security level is normal. The IP address of the probe. 2 of 2 Sample Output: The following example sets up the user1 community string with read-write access and normal security level: Avaya(configure)# snmp-server community user1 rw normal Systems: Avaya P550R, P580, P880, and P882 Multiservice switches. username The following text replaces the text in username of Chapter 31, User Interface. Command Mode: Enable. Description: Creates a new user account. Syntax: To Create: username <name> password [encrypted-type1] <passwd> [access-type {read-only read-write admin <catname>}] [mgmt-type [all] [localcli] [remote-cli] [web]] To Delete: [no] username <name> Part No January 7,

12 User Guide Addendum for the Avaya P550R and P880, v5.3.2 Table 4. Keywords, Arguments, and Options Parameter <name> [encrypted-type1] <passwd> [access-type {readonly read-write admin <catname>}] [mgmt-type [all] [local-cli] [remotecli] [web]] Definition The user name that you want to create. Indicates that user password is an MD5-encrypted string. If you enter the [encrypted-type1] option, you must enter an MD5- encrypted string for the <passwd> argument. The password for the user name. The access type for the user. Options are: read-only read-write admin <catname> The <catname> variable assigns a custom access type to the user. For information about custom access types, see Chapter 2, Initialize and Setup, in the Avaya P550R, P580, P880, and P882 Multiservice Switch User Guide. The default access type is read-only. The management interfaces to which you want the user to have access. Options are: all All management interfaces. local-cli CLI on the PC that is connected to the serial port on the supervisor module. remote-cli CLI by means of a Telnet connection. web Web Agent. The default setting is all. Sample Output: The following example creates the username boston with a password of mass and an access-type of admin: Avaya# username boston password mass access-type admin Systems: Avaya P550R, P580, P880, and P882 Multiservice switches. 12 January 7, 2003 Part No

13 Doc. No Technical Support To contact Avaya Technical Support: * Note: These are new phone numbers as of October 1, From the United States: From North America: Outside North America: Contact your distributor Documentation Feedback If you have comments about the technical accuracy or general quality of this document, please send us an message at: LSG-CTechPubs@avayactc.com Please cite the document title, part number, and page reference, if appropriate. Part No January 7,

14 User Guide Addendum for the Avaya P550R and P880, v January 7, 2003 Part No