Configuration Network Management Avaya Advanced Gateway 2330 AG NN , 01.01

Transcription

1 Configuration Network Management Avaya Advanced Gateway 2330 AG NN , August 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 Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. End User agree 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(s) 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 this product. 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 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, AND 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 ). 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. 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(s) 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(s) 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 other trademarks are the property of their respective owners. Downloading documents 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: support Copyright Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation(s) and Product(s) provided by Avaya. All content on this site, the documentation(s) and the product(s) provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is 2 Configuration Network Management August 2010

3 Contents Chapter 1: New in this release...7 Chapter 2: Introduction...9 Navigation...9 Chapter 3: Network management fundamentals...11 Prerequisites...11 Navigation...11 Simple network management protocol...11 Supported SNMP protocols and commands...13 Trap receivers...14 SNMP traps...14 SNMP MIB support...15 SNMP statistics...17 SNMP network management connectivity...18 Remote monitoring...18 RMON MIB groups...18 Performance considerations...19 Dynamic host configuration protocol version DHCPv4 implementation...20 Dynamic host configuration protocol version Autoconfiguration...21 DHCPv6 UDP ports...22 Multicast address...22 Client/Server operation...23 Remote OAM access and network management protocols...24 FTP...24 TFTP...25 Telnet...25 Chapter 4: SNMP configuration...27 Prerequisites to SNMP configuration...27 SNMP configuration procedures...27 SNMP configuration procedure navigation...28 Enabling SNMP server...28 Configuring SNMP source...29 Configuring SNMP server chassis ID...29 Configuring SNMP contact...30 Configuring SNMP location...30 Creating a community string...31 Creating trap source...31 Creating a trap receiver...32 Enabling traps...32 Verifying the configuration...33 Clearing SNMP statistics...34 Chapter 5: RMON configuration...35 Prerequisites to RMON configuration...35 RMON configuration procedures...35 Configuration Network Management August

4 RMON configuration procedure navigation...36 Enabling the RMON service...37 Example of enabling the RMON service...37 Enabling RMON statistics on Ethernet interface...37 Example of enabling Ethernet statistics collection...38 Enabling history statistics collection on Ethernet interface...38 Example of collecting Ethernet history statistics...39 Creating an event...39 Example of creating an event...40 Adding an alarm...40 Example of adding an alarm...42 Clearing the event log...42 Chapter 6: Ethernet statistics display using RMON...43 Monitoring Ethernet statistics procedure navigation...43 Viewing collected statistics on a specific interface...43 Viewing history statistics...44 Viewing the history statistics configuration...44 Viewing configured alarms...44 Viewing events...45 Viewing logs...45 Chapter 7: DHCP configuration...47 DHCP configuration tasks navigation...47 DHCP configuration task navigation...48 Chapter 8: DHCPv4 configuration...49 DHCPv4 configuration procedures...49 DHCPv4 configuration procedure navigation...50 Enabling DHCPv4 server on an interface...50 Configuring DHCPv4 server address pool...50 Configuring the IP phone alternate VLAN ID for the address pool...51 Configuring the Call Server name for the address pool...51 Configuring the client ID for the address pool...52 Committing the address pool...53 Configuring the default router address for the address pool...53 Configuring the DNS server name for the address pool...54 Configuring the domain name for the address pool...54 Configuring addresses to be excluded from address pool...55 Configuring the host IP address for the address pool...55 Configuring the hardware address for the address pool...56 Configuring the lease time for the address pool...56 Configuring the NetBIOS name server for the address pool...57 Configuring network for the address pool...57 Configuring TFTP server name for the address pool...58 Configuring the Wireless Phone server name for the address pool...58 Configuring remote database...59 Enabling DHCPv4 server...59 Configuring DHCP relay...60 Configuring DHCP relay server and gateway addresses...60 Configuring the primary DNS name server...61 Configuring the secondary DNS name server Configuration Network Management August 2010

5 Configuring the default domain name...61 Displaying DNS configuration...62 Chapter 9: DHCPv4 Relay over VLAN...63 Configuring DHCP relay on a VLAN...63 Displaying DHCP relay...64 Procedure job aid: sample command output...64 Example of configuring DHCP relay on a VLAN...64 DHCP Relay configuration...65 DHCP Server A configuration...66 Enabling DHCP client and relay debug messages...68 Chapter 10: DHCPv4 monitoring...69 DHCPv4 monitoring procedures...69 DHCPv4 monitoring procedure navigation...69 Displaying DHCPv4 server configuration...69 Displaying DHCPv4 server interface...70 Displaying DHCPv4 server address pool...70 Displaying DHCPv4 server binding...70 Displaying DHCPv4 server statistics...70 Displaying DHCP relay state...71 Clearing DHCPv4 server statistics...71 Clearing DHCPv4 server bindings...71 Chapter 11: DHCPv6 configuration...73 DHCPv6 configuration procedures...73 DHCPv6 configuration procedure navigation...74 Enabling DHCPv6 client...74 Enabling DHCPv6 server...74 Configuring DHCPv6 pool...75 Configuring prefix list for the DHCPv6 pool...75 Configuring DNS server for the DHCPv6 pool...76 Configuring the domain name for the DHCPv6 pool...76 Configuring the NTP server for the DHCPv6 pool...77 Enabling DHCPv6 relay...77 Chapter 12: DHCPv6 monitoring...79 DHCPv6 monitoring procedures...79 DHCPv6 monitoring procedure navigation...79 Displaying DHCPv6 interface...79 Displaying DHCPv6 pool...79 Displaying DHCPv6 binding...80 Displaying DHCPv6 DUIDs...80 Chapter 13: Configuring access protocols...81 Configuring access protocols procedure navigation...81 Configuring Telnet...81 Configuring the FTP...82 Enabling the TFTP...83 Configuration Network Management August

6 6 Configuration Network Management August 2010

7 Chapter 1: New in this release Avaya Advanced Gateway 2330 Configuration Network Management, NN is a new document for Release of the Avaya Advanced Gateway 2330 (AG2330). Configuration Network Management August

8 New in this release 8 Configuration Network Management August 2010

9 Chapter 2: Introduction This document contains procedural and conceptual information to help you to configure and manage the Avaya Advanced Gateway 2330 (AG2330). Navigation Network management fundamentals on page 11 SNMP configuration on page 27 RMON configuration on page 35 Ethernet statistics display using RMON on page 43 DHCP configuration on page 47 DHCPv4 configuration on page 49 DHCPv4 Relay over VLAN on page 63 DHCPv4 monitoring on page 69 DHCPv6 configuration on page 73 DHCPv6 monitoring on page 79 Configuring access protocols on page 81 Configuration Network Management August

10 Introduction 10 Configuration Network Management August 2010

11 Chapter 3: Network management fundamentals This section contains conceptual information to support the administration of the Avaya Advanced Gateway 2330 (AG2330) for performing network management tasks. Read and understand this information before you configure or maintain network management interfaces on the AG2330. Prerequisites You need an understanding of basic network security concepts. Familiarity with SNMPv1 as per RFC 1157 and SNMPv2c as per RFC Familiarity with the structure of management information (SMI) v1 as per RFC 1155 and SMIv2 as per RFC Navigation Simple network management protocol on page 11 Remote monitoring on page 18 Remote OAM access and network management protocols on page 24 Dynamic host configuration protocol version 4 on page 19 Dynamic host configuration protocol version 6 on page 21 Simple network management protocol This section contains conceptual information about the Simple Network Management Protocol (SNMP) service on the AG2330. SNMP is an application layer protocol that facilitates the exchange of management information between network devices. SNMP is part of the Transmission Control Protocol/Internet Protocol (TCP/IP) protocol suite. Use SNMP to manage network performance, find and solve network problems, and plan for network growth. You must have a good understanding of SNMP before you configure the Configuration Network Management August

12 Network management fundamentals SNMP service to access the AG2330 remotely from an SNMP-based network management system. Within the SNMP framework, a managed node can be any hardware device connected to the network, for example, a router, computer, or terminal server. A managed node contains a processing entity called an agent. The agent accesses the management information. The agent contains the two following agent types: master agent sends and receives SNMP protocol messages with the management station sub-agent(s) receives the requests processed by the master agent and sends the response back to the master agent. Sub-agents directly access the management information database. An external management station uses the SNMP protocol to communicate with and send SNMP requests to the master agent. The master agent processes the requests and sends a second request to the appropriate sub-agent to retrieve the information. The sub-agent processes the request and responds to the master agent that then forwards the response to the management station. The master and sub-agent do not use the SNMP protocol to communicate with one another; they use the AgentX protocol. In the case of SNMP traps, the sub-agent sends a notification message to the master agent. The master agent reformats the message and forwards the notification to the destined management station. For an illustration of the SNMP process, see Figure 1: AgentX Architecture on page Configuration Network Management August 2010

13 Simple network management protocol Figure 1: AgentX Architecture You can use any configured and operational interface on the AG2330 to perform SNMP requests. If the management station is in a different network, you must configure the proper routes on both the management station and the AG2330. Supported SNMP protocols and commands The AG2330 supports SNMPv1 (RFC 1157) and SNMPv2c (RFC 1903) protocols. More specifically, the AG2330 supports: get and get-next requests from SNMPv1 and SNMPv2c get-bulk requests from SNMPv2c SNMP traps as per SNMPv1 SNMPv2c notifications SMIv2 enterprise MIBs Configuration Network Management August

14 Network management fundamentals SMIv1 standard MIBs SNMP set requests are supported for the following MIB objects: - syscontact - sysname - syslocation SNMP requests use the User Datagram Protocol (UDP) port 161 to reach the agent. The agent sends traps using UDP port 162. Trap receivers When configuring SNMP traps, you must specify the IP address of one or more trap receivers. A trap receiver is a destination SNMP server that will receive the SNMP trap notifications. The AG2330 supports a maximum of 10 trap receivers. SNMP traps A trap is an unsolicited notification sent to an SNMP management station by an agent. The AG2330 supports a maximum of ten trap-hosts. The SNMPV1 and SNMPV2c traps in the AG2330 supports T1/E1 interfaces for the list of alarms as follows: RAIS alarm RRAI alarm RLOS alarm RLOF alarm TAIS alarm TRAI alarm Trap source IP address SNMPv1 and SNMPv2c trap Protocol Data Units (PDU) include the trap source IP address field. By default, the trap source IP address is However, the IP address of configured interface is accepted as trap source IP address with the limitation of IPv4 address. 14 Configuration Network Management August 2010

15 Simple network management protocol SNMP MIB support The AG2330 supports various SNMP standards defined by the RFC documents published by the Internet Engineering Task Force (IETF). For a list of supported SNMP standards, see Supported SNMP standards and standard MIBs on page 15. You can download supported standard MIBs (RFC documents) from the Internet Engineering Task Force web site at The AG2330 also supports a set of enterprise-defined MIBs. For a list of the supported Avaya enterprise-specific MIBs, see Supported enterprise-specific MIBs on page 16. Supported SNMP standards and standard MIBs This section provides a list of SNMP standards and the standard MIBs supported on the AG2330. The following list identifies the tables and groups supported for each MIB. For more information about each MIB, see the RFC. RFC 1155 Structure and Identification of Management Information for TCP/IP-based Internets RFC 1157 A Simple Network Management Protocol (SNMP) RFC 1213 Management Information Base for Network Management of TCP/IP-based internets: MIB-II RFC 1215 Convention for defining Traps for use with the SNMP RFC 1406 Definitions of Managed Objects for the DS1 and E1 Interface Types RFC 1493 Definitions of Managed Objects for Bridges RFC 1757 Remote Network Monitoring Management Information Base statistics group, history group, alarms group, events group RFC 1902 Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2) RFC 1903 Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2) RFC 2096 IP Forwarding Table MIB RFC 2127 ISDN Management Information Base using SMIv2 isdnmibbearergroup, isdnmibsignalinggroup, isdnmibbasicrategroup RFC 2618 RADIUS Authentication Client MIB RFC 2620 RADIUS Accounting Client MIB Configuration Network Management August

16 Network management fundamentals RFC 2674 Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN Extensions Dynamic Host Configuration Protocol (DHCP) Server MIB (draft-ietf-dhc-servermib-06.txt) Supported standard MIBs The AG2330 supports the standard MIBs described in Supported standard MIBs. All MIBs are SMIv2 compliant. Table 1: Supported standard MIBs IANAifType-MIB.mib IF-MIB.mib ISDN-MIB.mib MIB name DIAL-CONTROL-MIB.mib RADIUS-AUTH-CLIENT-MIB.mib RADIUS-ACC-CLIENT-MIB.mib Description Defines the enumerated values of the iftype object from the IANAifType textual convention. Defines the Interfaces Group MIB using SMIv2. Defines ISDN Management Information Base using SMIv2. Defines the Dial Control Management Information Base using SMIv2. Defines the RADIUS Authentication Client MIB. Defines the RADIUS Accounting Client MIB. MAU-MIB.mib Defines the Managed Objects for IEEE Medium Attachment Units. EtherLike-MIB.mib INET-ADDRESS-MIB.mib INTEGRATED-SERVICES-MIB.mib IEEE8021-PAE-MIB.mib Defines the Managed Objects for the Ethernet-like Interface Types. Defines the Textual Conventions for Internet Network Addresses. Defines the Integrated Services Management Information Base using SMIv2. Defines the Dot1x MIB. Supported enterprise-specific MIBs The AG2330 supports the Avaya enterprise-specific MIBs described in Table 2: Supported enterprise-specific MIBs on page 17. All MIBs are SMIv2 compliant. 16 Configuration Network Management August 2010

17 Simple network management protocol Table 2: Supported enterprise-specific MIBs MIB name BUNDLE-MIB.mib CHASSIS-MIB.mib CONFIG-MGMT-MIB.mib DSX-TC-MIB.mib DSX-TE1-MIB.mib ENVIRONMENT-MIB.mib IP-MIB.mib SNMP-MIB.mib SYSTEM-MIB.mib NORTEL-MIB.mib ENTERPRISE-DATA-MIB.mib QOSSLA-MIB.mib Description Defines objects related to bundle and link configuration. Defines objects related to chassis serial number and model number. Defines objects related to saving configurations for network. Defines textual conventions for DSX MIBs. This MIB should be compiled before any other DSX MIBs. This MIB does not contain any objects that can be used for management operations. Defines objects for interface cards that support TE1. These include configuration and statistics for ANSI/ATT/IETF and USER. These objects only pertain to Layer 1. Defines environment-related objects, for example, temperature and fans. Defines objects related to IP addressable interfaces and static routes. Defines objects related to SNMP community and trap_host configurations Defines objects related to system information, for example, IP address, host name, and DNS Defines the Nortel Networks top-level MIB Defines the EDN enterprise Data root MIB Defines the QOS SLA notifications SNMP statistics The AG2330 supports operational show commands that provide extensive statistical information about the SNMP data stream. For detailed statistics collection on Ethernet interfaces, the AG2330 uses the remote monitoring (RMON) standard. For more information on RMON, see Remote monitoring on page 18. Configuration Network Management August

18 Network management fundamentals SNMP network management connectivity Network management connectivity for the SNMP service is established by using the command line interface (CLI). For more information about how to configure a management interface, see Avaya Advanced Gateway 2330 Commissioning (NN ). Remote monitoring Remote monitoring (RMON) is an industry standard, RFC 1757, that uses SNMP to monitor Ethernet LAN segments and provide network statistics. Configure RMON on the AG2330 to obtain information about the Layer 1 and Layer 2 environments. RMON collects information about physical connections, performance, and configuration. Use RMON to detect a sudden change in network traffic and solve a problem before it becomes critical. RMON runs continuously even when there are no clients checking statistics. You can configure RMON to send trap messages when an error condition occurs that exceeds a configured maximum threshold. An RMON agent is a noninteractive monitor on a LAN segment. The agent reads and copies each frame sent on the local LAN and updates counters based on the contents of the frames. The agent saves the captured information until a remote managing station requests it. The managing station is not actively involved in the data collection. You can configure RMON on the Ethernet LAN ports. RMON MIB groups The AG2330 supports the MIB groups identified in Table 3: Supported RMONv1 MIB groups on page 18. Only SNMP get operations on the RMON MIB are supported. Set operations are not supported. Table 3: Supported RMONv1 MIB groups Statistics RMON group Function Elements Contains statistics measured by the probe for each monitored interface on the device. Packets dropped and sent, bytes sent (octets), broadcast and multicast packets, CRC errors, runts, giants, fragments, jabbers, collisions, and counters for packets ranging from 64 to 128, 128 to 256, 256 to 512, 18 Configuration Network Management August 2010

19 Dynamic host configuration protocol version 4 History Alarm Event RMON group Function Elements Records periodic statistical samples from a network and stores them for later retrieval. Takes periodic statistical samples from variables in the probe and compares them with configured thresholds. If the monitored variable exceeds a threshold, an event is generated. Controls the generation and notification of events from the device. 512 to 1024, and 1024 to 1518 bytes. Sample period, number of samples, and items sampled. Alarm type, interval, starting threshold, and stop threshold. Includes the alarm table and requires the implementation of the event group. Event type, description, and last time the event sent. Performance considerations Management traffic is a concern when you use remote monitoring. When you monitor at finer levels of granularity, there are a number of interactions between the application and the RMON agent that raise the possibility of congestion caused by the increased management traffic. If you collect statistics infrequently, the data collection does not use significant bandwidth but it offers little valuable information. Keep timing and traffic levels in mind when you configure remote monitoring. RMON agents are economical in their use of network bandwidth. Based on 10-second polling intervals, traffic loads for common RMON functions such as providing a summary screen of activity, network statistics, or host statistics consume a small fraction of 1% of Ethernet bandwidth. As a result, RMON agents typically do not affect normal Ethernet segment activities. Dynamic host configuration protocol version 4 The Dynamic Host Configuration Protocol version 4 (DHCPv4) provides the configuration parameters and IP addresses to the Internet Hosts. DHCPv4 is built on a client-server model. The DHCPv4 servers allocate network addresses and configuration parameters to dynamically configured DHCPv4 clients. The communication between DHCPv4 clients and DHCPv4 servers passes through Bootstrap Protocol (BOOTP) relay agent. Configuration Network Management August

20 Network management fundamentals The DHCPv4 server provides the following parameters to the DHCPv4 client: IP address Default gateway Domain Name Server (DNS) address NetBIOS setting DHCPv4 implementation The DHCPv4 server and BOOTP relay implementation need the following modules: Remote Database on page 20 DHCPv4 server address pool on page 20 DHCPv4 relay functionality on page 20 Remote Database The remote database maintains current bindings and the leases for the DHCPv4 server, that are allocated to the clients. This database also times out the leases and ensures that there is no conflict in address assignments. The storage happens in memory or on to the flash for permanent store or to a remote host URL location using FTP. Storing the lease database in the flash is not recommended due to restricted file system limitations. It is recommended to store the lease database on to a remote host by configuring a URL location. The DHCPv4 server uses ftp to transfer the leases to the URL location and on every reboot restores the leases from this URL location. The maximum number of leases that the DHCPv4 server can support is limited to the amount of memory needed to store a lease record and the amount of system memory available. It is limited to have a total 4000 leases as the maximum upper limit for 256 MB of system memory. DHCPv4 server address pool The DHCPv4 server stores the DHCP parameters for the client in server pools. Each pool has an associated name and serves a specific subnet. The parameters like IP address range, lease times, MAC address, and client IDs are associated with each pool entry. These entries are configured for manual or dynamic binding. DHCPv4 relay functionality The DHCPv4 relay functionality is used to relay the DHCPv4 client requests to the DHCPv4 server and get the DHCP parameters. The DHCPv4 server accepts relayed requests only from the relay servers configured. 20 Configuration Network Management August 2010

21 Dynamic host configuration protocol version 6 DHCPv4 over VLAN With Release 10.2 and later, you can configure DHCP server and DHCP Relay on VLAN interfaces. Dynamic host configuration protocol version 6 The Dynamic Host Configuration Protocol version 6 (DHCPv6) supports Internet Protocol version 6 (IPv6). DHCPv6 enables DHCPv6 servers to transmit configuration parameters to IPv6 nodes using extensions. It automatically allocates reusable network addresses and reduces the cost of managing IPv6 nodes in environments where administrators require more control over the allocation of IP addresses. DHCPv6 server manages network resources such as IP addresses, Network Time Protocol (NTP), Domain Name System (DNS), and other server addresses at a centralized location. DHCP relay facilitates initial communication between the DHCPv6 server and the DHCPv6 client when they are on different links. DHCPv6 model works across relays without a DHCPv6 server on each link. Autoconfiguration Autoconfiguration is a mechanism that does not require any manual intervention to configure a host in a network environment. Following are the types of autoconfiguration methods: Stateless address autoconfiguration on page 21 Stateful address autoconfiguration on page 21 Stateless address autoconfiguration The stateless address autoconfiguration does not require a manually configured server but enables IPv6 hosts to configure the IP addresses using a local IPv6 router. However, this method lacks network access control capabilities and manages only IP addressing. Stateful address autoconfiguration The stateful autoconfiguration involves a client and a server. When an unconfigured node is unable to locate router advertisements on the network it uses DHCPv6 to configure an interface. Configuration Network Management August

22 Network management fundamentals DHCPv6 UDP ports DHCPv6 uses the following Internet User Datagram Protocol (UDP) ports: 546 on page on page DHCPv6 servers use 546 client port as the destination port to send messages to clients and relays. In addition, the relays or agents use this port as the destination port for messages sent to the clients. 547 DHCPv6 clients use 547 agent port as the destination port to send messages to agents or relays. In addition, relays use this port as the destination port for messages sent to the servers. Multicast address DHCPv6 uses the following multicast addresses: DHCP agent address FF02::1:2 on page 22 DHCP server address FF05::1:3 on page 22 DHCP agent address FF02::1:2 DHCP clients use this link-scoped multicast address to communicate with the on-link agent. All agents within the same DHCP domain belong to this multicast group. DHCP server address FF05::1:3 DHCP clients or relays use this site-scoped multicast address to communicate with servers within the site in one of the following scenarios: When the client or relay sends messages to all servers. When the client or relay does not know the server s unicast address. 22 Configuration Network Management August 2010

23 Dynamic host configuration protocol version 6 Client/Server operation DHCPv6 servers and DHCPv6 clients on the same link communicate directly with each other. DHCPv6 requires relays to be set up on the client s link when the client and the server are on different links. Relays receive messages from the client and forward them to a set of DHCPv6 servers. When the client and the server are on the same link on page 23 When the client and the server are on different link on page 23 When the client and the server are on the same link The client and the server on the same link communicate with each other as follows: 1. The client sends a SOLICIT message to locate suitable servers. 2. Multiple servers respond to the SOLICIT message by sending a DHCP ADVERTISE message to the client. 3. The client sends a DHCP REQUEST message to the DHCPv6 server that has the highest preference value. 4. The server responds to the client s message by sending a DHCP REPLY message. The DHCP REPLY message contains the IPv6 address and configuration parameters required by the client. 5. The client sends a DHCP RELEASE message to return one or more IPv6 addresses to the server when it has completed using an IPv6 address. Figure 2: Client and server on same link When the client and the server are on different link The client and the server on different links communicate with each other as follows: Configuration Network Management August

24 Network management fundamentals 1. The client sends SOLICIT message to locate servers that are able to offer the required services. 2. The relay forwards the client s message to servers by sending RELAY- FORWARD message. 3. The servers respond to the client s message by sending a SERVER-FORWARD message. 4. The relay forwards the servers messages to the client by sending ADVERTISE messages. Figure 3: Client and server on different link Remote OAM access and network management protocols The AG2330 supports a variety of remote-access and network management protocols for system operation, maintenance, and administration (OAM) tasks. This section provides information about the following topics: FTP on page 24 TFTP on page 25 Telnet on page 25 FTP The AG2330 supports the File Transfer Protocol (FTP) as documented in RFC 959. FTP is not a secure file transfer protocol. FTP does not encrypt transferred data. Use FTP access only after you determine that it is safe to do so in your specific network scenario. If you need to transfer data over a network or network segment that is not secure, use the Secure FTP 24 Configuration Network Management August 2010

25 Remote OAM access and network management protocols capability provided by the SSH service. For more information on SSH, see Avaya Advanced Gateway 2330 Security Configuration and Management, NN The AG2330 supports a maximum of 4 FTP sessions at a time. FTP is disabled by default on the AG2330. TFTP The Trivial File Transfer Protocol (TFTP) (RFC 1350) is a version of the FTP but does not use a password. TFTP is not a secure file transfer protocol. Use TFTP access only after you determine that it is safe to do so in your specific network scenario. If you need to transfer data over a network or network segment that is not secure, use the Secure FTP capability provided by the SSH service. For more information on SSH, see Avaya Advanced Gateway 2330 Security Configuration and Management, NN The AG2330 supports a maximum of 4 TFTP sessions at a time and more than 32MB of image downloading is not supported. TFTP is disabled by default on the AG2330. Telnet The AG2330 supports Telnet (RFC 854). Use a Telnet session to log on to the AG2330 to perform system OAM tasks. Telnet is not a secure remote access protocol; data transmitted in a Telnet session is not encrypted and passwords are transmitted in clear text. Use Telnet only after you determine that it is safe to use it in your specific network scenario. If your management network is not secure, use the Secure Shell (SSH) protocol to log on remotely. For more information on SSH, see Avaya Advanced Gateway 2330 Security Configuration and Management, NN The AG2330 supports a maximum of 16 Telnet sessions, if no console session is active. With an active console session, a maximum of 15 Telnet sessions is supported. Telnet is disabled by default on the AG2330. Configuration Network Management August

26 Network management fundamentals 26 Configuration Network Management August 2010

27 Chapter 4: SNMP configuration Configure the Simple Network Management Protocol (SNMP) on the Avaya Advanced Gateway 2330 (AG2330). Prerequisites to SNMP configuration Before you perform SNMP configuration ensure that the interfaces are functional. Ensure that proper routes are added to the manager and the agent, if the management station is in a different network. Ensure that the MIB file is uploaded to the management station. SNMP configuration procedures This task flow shows you the sequence of procedures you use to configure SNMP on the AG2330. To link to any procedure, go to SNMP configuration procedure navigation on page 28 Configuration Network Management August

28 SNMP configuration Figure 4: SNMP configuration procedures SNMP configuration procedure navigation Creating a community string on page 31 Creating a trap receiver on page 32 Verifying the configuration on page 33 Clearing SNMP statistics on page 34 Enabling SNMP server Enable SNMP server to access next-level commands for configuring the MIB database for all systems. 1. To enter configuration mode, enter: 28 Configuration Network Management August 2010

29 Configuring SNMP source 2. To select SNMP server configuration, enter: snmp-server 3. To enable the SNMP server, enter: snmp-enable Configuring SNMP source Configure the SNMP source IP address. 1. To enter configuration mode, enter: 2. To select SNMP server configuration, enter: snmp-server 3. To configure the SNMP source, enter: snmp-source <IP address> Table 4: Variable definitions Variable <IP address> Value SNMP source IP address Configuring SNMP server chassis ID Configure SNMP server chassis ID to name the SNMP host system. 1. To enter configuration mode, enter: 2. To select SNMP server configuration, enter: snmp-server 3. To configure the SNMP server chassis ID: chassis-id <name> Configuration Network Management August

30 SNMP configuration Table 5: Variable definitions Variable <name> Value name of the host system Configuring SNMP contact Configure SNMP contact to specify a contact person for the SNMP MIB. 1. To enter configuration mode, enter: 2. To select SNMP server configuration, enter: snmp-server 3. To configure SNMP contact, enter: contact < name > Table 6: Variable definitions Variable < name > Value name of the person to contact regarding the SNMP MIB. Use up to eight characters and enclose in quotes. Configuring SNMP location Configuring SNMP location defines the SNMP host system location. 1. To enter configuration mode, enter: 2. To select SNMP server configuration, enter: snmp-server 3. To configure SNMP location, enter: location <"string"> 30 Configuration Network Management August 2010

31 Creating a community string Table 7: Variable definitions Variable <"string"> Value location of the host system, specified in quotation marks. Creating a community string Create the community string to configure the AG2330 for performing the SNMP operation. You can configure a maximum of 10 SNMP community strings. 1. To enter configuration mode, enter: 2. To select SNMP server configuration, enter: snmp-server 3. To create a community string: community <string> [ access_privilege {ro rw} ] Table 8: Variable definitions Variable <string> Value Specifies a new community string for SNMP configuration. Creating trap source Create trap source to configure SNMP trap messages to be sent to a specific IP address or the system default address. 1. To enter configuration mode, enter: 2. To select SNMP server configuration, enter: Configuration Network Management August

32 SNMP configuration snmp-server 3. Create trap source trap-source host <IP address> Table 9: Variable definitions Variable <IP address> Value trap source IP address Creating a trap receiver Create a trap receiver or trap host to receive the trap/notification. You can configure a maximum of 10 trap hosts. 1. To enter configuration mode, enter: 2. To select SNMP server configuration, enter: snmp-server 3. Create a trap receiver: trap-host <ip address> [community string] Table 10: Variable definitions Variable <ip address> Value is the IP address of the trap host. Use version 4 or version 6 IP address. Enabling traps Use this procedure to enable traps. 1. To enter configuration mode, enter: 32 Configuration Network Management August 2010

33 Verifying the configuration 2. To select SNMP server configuration, enter: snmp-server 3. To enable specific traps, enter [no] enable traps {bundle config enable-all environment snmp sntp system} Table 11: Variable definitions Variable [no] bundle config enable-all environment snmp sntp system Value Disables the specified trap. Enables or disables bundle group of traps. Enables or disables Configuration group traps. Enables or disables all traps. Enables or disables Environment group traps. Enables or disables SNMP group related traps. Enables or disables SNTP client traps. Enables or disables system group traps. Verifying the configuration Verify the community string and trap host configuration. 1. Display the configured SNMP community: show snmp communities 2. Display the configured SNMP source address: show snmp snmp-source 3. Display SNMP generic information: show snmp status 4. Display the configured trap hosts: show snmp trap-host Configuration Network Management August

34 SNMP configuration 5. Display the configured trap source address: show snmp trap-source 6. Display the configured trap version: show snmp trap-version 7. Display the list of traps enabled or disabled: show snmp traps Clearing SNMP statistics Clear the SNMP statistics to release the events generated by the agent. Clear SNMP statistics: clear snmp_stats 34 Configuration Network Management August 2010

35 Chapter 5: RMON configuration Configure the remote monitoring (RMON) feature on the Avaya Advanced Gateway Prerequisites to RMON configuration Before you configure RMON, you must configure at least one Ethernet interface for monitoring. For more information on configuring Ethernet interfaces, see Avaya Advanced Gateway 2330 Configuration Ethernet Layer 2, NN Ensure that the MIB file is uploaded to the management station. RMON configuration procedures This task flow shows you the sequence of procedures you use to configure RMON on the AG2330. To link to any task, see RMON configuration procedure navigation on page 36 Configuration Network Management August

36 RMON configuration Figure 5: RMON configuration procedures RMON configuration procedure navigation Enabling the RMON service on page 37 Enabling RMON statistics on Ethernet interface on page 37 Enabling history statistics collection on Ethernet interface on page Configuration Network Management August 2010

37 Enabling the RMON service Creating an event on page 39 Adding an alarm on page 40 Enabling the RMON service Enable the RMON service globally on the AG2330 to collect Ethernet statistics. 1. To enable the configuration mode, enter: 2. Enable the RMON service: rmon enable On the AG2330, use the no operator to disable a feature. For example, to disable the RMON service, the command is no rmon enable. Example of enabling the RMON service Enable the RMON service globally: AG/configure# rmon enable Enabling RMON statistics on Ethernet interface Configure RMON on an Ethernet port to collect statistics for that port. You can collect information on the packet volumes, broadcast and unicast traffic, packet size distributions, and errors. Prerequisites The Ethernet interface is configured. For information on configuring Ethernet interfaces, see Avaya Advanced Gateway 2330 Configuration Ethernet Layer 2, NN To enter the configuration mode, enter: 2. Enable statistics collection: Configuration Network Management August

38 RMON configuration rmon statistics ethernet<slot/port> [<owner>] On the AG2330, use the no operator to disable a feature. For example, to disable statistics collection, the command is no rmon statistics ethernet<slot/ port> [<owner>]. Table 12: Variable definitions <owner> <slot/port> Variable Value specifies the owner of the RMON port. The default owner is CLI-Manager. identifies the Ethernet interface on which to enable statistics collection. Identify the interface using slot/ port. Example of enabling Ethernet statistics collection Enable Ethernet statistics collection on Ethernet interface slot 0, port 2: AG/configure/rmon# statistics ethernet0/2 Enabling history statistics collection on Ethernet interface Enable collection of Ethernet history statistics to compare behavior and build baselines and trending information. The probe collects the statistics at specified intervals and saves a specified number of samples for later retrieval. You can configure a maximum of 10 history controls per interface. Prerequisites The Ethernet interface is configured. For information on configuring Ethernet interfaces, see Avaya Advanced Gateway 2330 Configuration Ethernet Layer 2, NN Ethernet statistics collection is enabled for the interface. 1. To enter the configuration mode, enter: 2. Enable collection of Ethernet history statistics: rmon history ethernet<slot/port> [<interval>] [<buckets>] [<owner>] 38 Configuration Network Management August 2010

39 Example of collecting Ethernet history statistics On the AG2330, use the no operator to disable a feature. For example, to disable history statistics collection, the command is no rmon history ethernet<slot/port> [<interval>] [<buckets>] [<owner>]. Table 13: Variable definitions <buckets> <interval> <owner> <slot/port> Variable Value specifies the number of samples to maintain. The default value is 50 and the maximum number is 100. specifies the interval, in seconds, at which to collect statistics. The default value is 1800 seconds. specifies the owner of the RMON port. The default owner is CLI-Manager. identifies the Ethernet interface on which to enable statistics collection. Identify the interface using slot/port. Example of collecting Ethernet history statistics Collect Ethernet history statistics on the Ethernet interface in slot 1, port 2 with an interval of 100 and buckets set to 20: AG/configure# rmon history ethernet1/ Creating an event Create an event to control the sending of SNMP trap messages to the remote client. The probe can signal the occurrence of many types of events such as exceeded thresholds or captured packets. The maximum number of events is 100. The maximum number of RMON logs on the AG2330 is To enter the configuration mode, enter: 2. Create an event: Configuration Network Management August

40 RMON configuration rmon event <index> <type> [community <community>] [description <description>] [owner <owner>] On the AG2330, use the no operator to disable a feature. For example, to disable an event, the command is no rmon event <index> <type> [community <community>] [description <description>] [owner <owner>]. Table 14: Variable definitions <community> <description> <index> <owner> <type> Variable Value specifies an SNMP community name if <type> is set to trap (2) or log-trap (3) specifies a text description for the event. The value must be specified in quotation marks (" "). specifies an index number for this event. The maximum number of events is 100 specifies the owner of the RMON event Specifies the type of event as one of the following: log (1) trap (2) log-trap (3) Example of creating an event Create an event to log information: AG/configure# rmon event 2 log description "event 2" owner Manager-2 Adding an alarm Add an alarm to set thresholds to signal when values require further attention. The maximum number of alarms is Configuration Network Management August 2010

41 Adding an alarm Prerequisites An RMON event exists in the system. 1. To enter the configuration mode, enter: 2. Add an alarm: rmon alarm <index> <variable> <interval> <rthreshold> <fthreshold> <revent> <fevent> [<type>] [<startup>] [<owner>] On the AG2330, use the no operator to disable a feature. For example, to disable an event, the command is no rmon alarm <index> <variable> <interval> <rthreshold> <fthreshold> <revent> <fevent> [<type>] [<startup>] [<owner>]. Table 15: Variable definitions <fevent> <fthreshold> <index> <interval> <owner> <revent> <rthreshold> <startup> <type> Variable Value specifies the index number of the RMON event to trigger when the value is lower than the falling threshold sets the falling alarm threshold. If the value is lower than this threshold, it causes a falling alarm specifies an index number for this alarm. The maximum number of alarms is 100 specifies the interval, in seconds, at which to poll specifies the owner of the RMON alarm. The default owner is CLI-Manager specifies the index number of the RMON event to trigger when the value is higher than the rising threshold sets the rising alarm threshold. If the value exceeds this threshold, it causes a rising alarm specifies the type of alarm generated when the event first occurs: rising, falling, or rise_fall. The default is rise_fall specifies the sampling method as either absolute or delta (the difference). The default is absolute Configuration Network Management August

42 RMON configuration <variable> Variable Value specifies the MIB object to monitor using ASN.1. ASN.1 describes a managed object in machine-independent format Example of adding an alarm Create a rising alarm to monitor the delta every 100 seconds: AG/configure# rmon alarm type delta startup rising owner Manager-1 Clearing the event log Use this procedure to clear the event log. To clear the event log, enter: clear event_log 42 Configuration Network Management August 2010

43 Chapter 6: Ethernet statistics display using RMON Monitor Ethernet statistics to view configuration information and collected data to identify trends and potential network issues. Monitoring Ethernet statistics procedure navigation Viewing collected statistics on a specific interface on page 43 Viewing history statistics on page 44 Viewing the history statistics configuration on page 44 Viewing configured alarms on page 44 Viewing events on page 45 Viewing logs on page 45 Viewing collected statistics on a specific interface Display the collected statistics on a specific interface to display all the readings of the etherstats table of the RMON MIB. Display statistics for a specific interface: show rmon statistics ethernet<slot/port> Table 16: Variable definitions <slot/port> Variable Value identifies the Ethernet interface on which to enable statistics collection. Identify the interface using slot/port Configuration Network Management August