Avaya Integrated Management Release 3.0 Enterprise Network Management Configuration

Transcription

1 Avaya Integrated Management Release 3.0 Enterprise Network Management Configuration Issue 1 June 2005

2 Copyright 2005, Avaya Inc. All Rights Reserved Notice Every effort was made to ensure that the information in this document was complete and accurate at the time of printing. However, information is subject to change. Warranty Avaya Inc. 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 through the following Web site: Preventing Toll Fraud "Toll fraud" is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there may be a risk of toll fraud associated with your system and that, if toll fraud occurs, it can result in substantial additional charges for your telecommunications services. Avaya Fraud Intervention If you suspect that you are being victimized by toll fraud and you need technical assistance or support, in the United States and Canada, call the Technical Service Center's Toll Fraud Intervention Hotline at Disclaimer Avaya is not 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. Customer and/or 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 the Customer or End User. How to Get Help For additional support telephone numbers, go to the Avaya support Web site: If you are: Within the United States, click the Escalation Management link. Then click the appropriate link for the type of support you need. Outside the United States, click the Escalation Management link. Then click the International Services link that includes telephone numbers for the international Centers of Excellence. Providing Telecommunications Security Telecommunications security (of voice, data, and/or video communications) is the prevention of any type of intrusion to (that is, either unauthorized or malicious access to or use of) your company's telecommunications equipment by some party. Your company's "telecommunications equipment" includes both this Avaya product and any other voice/data/video equipment that could be accessed via this Avaya product (that is, "networked equipment"). An "outside party" is anyone who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf. Whereas, a "malicious party" is anyone (including someone who may be otherwise authorized) who accesses your telecommunications equipment with either malicious or mischievous intent. Such intrusions may be either to/through synchronous (time-multiplexed and/or circuit-based), or asynchronous (character-, message-, or packet-based) equipment, or interfaces for reasons of: Utilization (of capabilities special to the accessed equipment) Theft (such as, of intellectual property, financial assets, or toll facility access) Eavesdropping (privacy invasions to humans) Mischief (troubling, but apparently innocuous, tampering) Harm (such as harmful tampering, data loss or alteration, regardless of motive or intent) Be aware that there may be a risk of unauthorized intrusions associated with your system and/or its networked equipment. Also realize that, if such an intrusion should occur, it could result in a variety of losses to your company (including but not limited to, human/data privacy, intellectual property, material assets, financial resources, labor costs, and/or legal costs). Responsibility for Your Company s Telecommunications Security The final responsibility for securing both this system and its networked equipment rests with you - Avaya s customer system administrator, your telecommunications peers, and your managers. Base the fulfillment of your responsibility on acquired knowledge and resources from a variety of sources including but not limited to: Installation documents System administration documents Security documents Hardware-/software-based security tools Shared information between you and your peers Telecommunications security experts To prevent intrusions to your telecommunications equipment, you and your peers should carefully program and configure: Your Avaya-provided telecommunications systems and their interfaces Your Avaya-provided software applications, as well as their underlying hardware/software platforms and interfaces Any other equipment networked to your Avaya products TCP/IP Facilities Customers may experience differences in product performance, reliability and security depending upon network configurations/design and topologies, even when the product performs as warranted. Standards Compliance Avaya Inc. is not responsible for any radio or television interference caused by unauthorized modifications of this equipment or the substitution or attachment of connecting cables and equipment other than those specified by Avaya Inc. The correction of interference caused by such unauthorized modifications, substitution or attachment will be the responsibility of the user. Pursuant to Part 15 of the Federal Communications Commission (FCC) Rules, the user is cautioned that changes or modifications not expressly approved by Avaya Inc. could void the user s authority to operate this equipment. Product Safety Standards This product complies with and conforms to the following international Product Safety standards as applicable: Safety of Information Technology Equipment, IEC 60950, 3rd Edition, or IEC , 1st Edition, including all relevant national deviations as listed in Compliance with IEC for Electrical Equipment (IECEE) CB-96A. Safety of Information Technology Equipment, CAN/CSA-C22.2 No / UL 60950, 3rd Edition, or CAN/CSA-C22.2 No / UL Safety Requirements for Information Technology Equipment, AS/NZS 60950:2000. One or more of the following Mexican national standards, as applicable: NOM 001 SCFI 1993, NOM SCFI , NOM 019 SCFI The equipment described in this document may contain Class 1 LASER Device(s). These devices comply with the following standards: EN , Edition 1.1, CFR and CFR The LASER devices used in Avaya equipment typically operate within the following parameters: Typical Center Wavelength 830 nm nm -1.5 dbm 1270 nm nm -3.0 dbm 1540 nm nm 5.0 dbm Maximum Output Power Luokan 1 Laserlaite Klass 1 Laser Apparat Use of controls or adjustments or performance of procedures other than those specified herein may result in hazardous radiation exposures. Contact your Avaya representative for more laser product information.

3 Electromagnetic Compatibility (EMC) Standards This product complies with and conforms to the following international EMC standards and all relevant national deviations: Limits and Methods of Measurement of Radio Interference of Information Technology Equipment, CISPR 22:1997, EN55022:1998, and AS/NZS Information Technology Equipment - Immunity Characteristics - Limits and Methods of Measurement, CISPR 24:1997 and EN55024:1998, including: Electrostatic Discharge (ESD) IEC Radiated Immunity IEC Electrical Fast Transient IEC Lightning Effects IEC Conducted Immunity IEC Mains Frequency Magnetic Field IEC Voltage Dips and Variations IEC Power Line Emissions, IEC : Electromagnetic compatibility (EMC) - Part 3-2: Limits - Limits for harmonic current emissions. Power Line Emissions, IEC : Electromagnetic compatibility (EMC) - Part 3-3: Limits - Limitation of voltage changes, voltage fluctuations and flicker in public low-voltage supply systems. Federal Communications Commission Statement Part 15: Note: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense. Part 68: Answer-Supervision Signaling Allowing this equipment to be operated in a manner that does not provide proper answer-supervision signaling is in violation of Part 68 rules. This equipment returns answer-supervision signals to the public switched network when: answered by the called station, answered by the attendant, or routed to a recorded announcement that can be administered by the customer premises equipment (CPE) user. This equipment returns answer-supervision signals on all direct inward dialed (DID) calls forwarded back to the public switched telephone network. Permissible exceptions are: A call is unanswered. A busy tone is received. A reorder tone is received. Avaya attests that this registered equipment is capable of providing users access to interstate providers of operator services through the use of access codes. Modification of this equipment by call aggregators to block access dialing codes is a violation of the Telephone Operator Consumers Act of REN Number For MCC1, SCC1, CMC1, G600, and G650 Media Gateways: This equipment complies with Part 68 of the FCC rules. On either the rear or inside the front cover of this equipment is a label that contains, among other information, the FCC registration number, and ringer equivalence number (REN) for this equipment. If requested, this information must be provided to the telephone company. For G350 and G700 Media Gateways: This equipment complies with Part 68 of the FCC rules and the requirements adopted by the ACTA. On the rear of this equipment is a label that contains, among other information, a product identifier in the format US:AAAEQ##TXXXX. The digits represented by ## are the ringer equivalence number (REN) without a decimal point (for example, 03 is a REN of 0.3). If requested, this number must be provided to the telephone company. For all media gateways: The REN is used to determine the quantity of devices that may be connected to the telephone line. Excessive RENs on the telephone line may result in devices not ringing in response to an incoming call. In most, but not all areas, the sum of RENs should not exceed 5.0. To be certain of the number of devices that may be connected to a line, as determined by the total RENs, contact the local telephone company. REN is not required for some types of analog or digital facilities. Means of Connection Connection of this equipment to the telephone network is shown in the following tables. For MCC1, SCC1, CMC1, G600, and G650 Media Gateways: Manufacturer s Port Identifier FIC Code For G350 and G700 Media Gateways: SOC/ REN/ A.S. Code Network Jacks Off premises station OL13C 9.0F RJ2GX, RJ21X, RJ11C DID trunk 02RV2-T 0.0B RJ2GX, RJ21X CO trunk 02GS2 0.3A RJ21X 02LS2 0.3A RJ21X Tie trunk TL31M 9.0F RJ2GX Basic Rate Interface 02IS5 6.0F, 6.0Y RJ49C digital interface 04DU9-BN 6.0F RJ48C, RJ48M 120A4 channel service unit Manufacturer s Port Identifier 04DU9-IKN 6.0F RJ48C, RJ48M 04DU9-ISN 6.0F RJ48C, RJ48M 04DU9-DN 6.0Y RJ48C FIC Code SOC/ REN/ A.S. Code Network Jacks Ground Start CO trunk 02GS2 1.0A RJ11C DID trunk 02RV2-T AS.0 RJ11C Loop Start CO trunk 02LS2 0.5A RJ11C digital interface 04DU9-BN 6.0Y RJ48C 04DU9-DN 6.0Y RJ48C 04DU9-IKN 6.0Y RJ48C 04DU9-ISN 6.0Y RJ48C Basic Rate Interface 02IS5 6.0F RJ49C For all media gateways: If the terminal equipment (for example, the media server or media gateway) causes harm to the telephone network, the telephone company will notify you in advance that temporary discontinuance of service may be required. But if advance notice is not practical, the telephone company will notify the customer as soon as possible. Also, you will be advised of your right to file a complaint with the FCC if you believe it is necessary. The telephone company may make changes in its facilities, equipment, operations or procedures that could affect the operation of the equipment. If this happens, the telephone company will provide advance notice in order for you to make necessary modifications to maintain uninterrupted service. If trouble is experienced with this equipment, for repair or warranty information, please contact the Technical Service Center at or contact your local Avaya representative. If the equipment is causing harm to the telephone network, the telephone company may request that you disconnect the equipment until the problem is resolved.

4 A plug and jack used to connect this equipment to the premises wiring and telephone network must comply with the applicable FCC Part 68 rules and requirements adopted by the ACTA. A compliant telephone cord and modular plug is provided with this product. It is designed to be connected to a compatible modular jack that is also compliant. It is recommended that repairs be performed by Avaya certified technicians. The equipment cannot be used on public coin phone service provided by the telephone company. Connection to party line service is subject to state tariffs. Contact the state public utility commission, public service commission or corporation commission for information. This equipment, if it uses a telephone receiver, is hearing aid compatible. Canadian Department of Communications (DOC) Interference Information This Class A digital apparatus complies with Canadian ICES-003. Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada. This equipment meets the applicable Industry Canada Terminal Equipment Technical Specifications. This is confirmed by the registration number. The abbreviation, IC, before the registration number signifies that registration was performed based on a Declaration of Conformity indicating that Industry Canada technical specifications were met. It does not imply that Industry Canada approved the equipment. To order copies of this and other documents: Call: Avaya Publications Center Voice or FAX or Write: Globalware Solutions 200 Ward Hill Avenue Haverhill, MA USA Attention: Avaya Account Management [email protected] For the most current versions of documentation, go to the Avaya support Web site: Installation and Repairs Before installing this equipment, users should ensure that it is permissible to be connected to the facilities of the local telecommunications company. The equipment must also be installed using an acceptable method of connection. The customer should be aware that compliance with the above conditions may not prevent degradation of service in some situations. Repairs to certified equipment should be coordinated by a representative designated by the supplier. Any repairs or alterations made by the user to this equipment, or equipment malfunctions, may give the telecommunications company cause to request the user to disconnect the equipment. Declarations of Conformity United States FCC Part 68 Supplier s Declaration of Conformity (SDoC) Avaya Inc. in the United States of America hereby certifies that the equipment described in this document and bearing a TIA TSB-168 label identification number complies with the FCC s Rules and Regulations 47 CFR Part 68, and the Administrative Council on Terminal Attachments (ACTA) adopted technical criteria. Avaya further asserts that Avaya handset-equipped terminal equipment described in this document complies with Paragraph of the FCC Rules and Regulations defining Hearing Aid Compatibility and is deemed compatible with hearing aids. Copies of SDoCs signed by the Responsible Party in the U. S. can be obtained by contacting your local sales representative and are available on the following Web site: All Avaya media servers and media gateways are compliant with FCC Part 68, but many have been registered with the FCC before the SDoC process was available. A list of all Avaya registered products may be found at: by conducting a search using "Avaya" as manufacturer. European Union Declarations of Conformity Avaya Inc. declares that the equipment specified in this document bearing the "CE" (Conformité Europeénne) mark conforms to the European Union Radio and Telecommunications Terminal Equipment Directive (1999/5/EC), including the Electromagnetic Compatibility Directive (89/336/EEC) and Low Voltage Directive (73/23/EEC). Copies of these Declarations of Conformity (DoCs) can be obtained by contacting your local sales representative and are available on the following Web site: Japan This is a Class A product based on the standard of the Voluntary Control Council for Interference by Information Technology Equipment (VCCI). If this equipment is used in a domestic environment, radio disturbance may occur, in which case, the user may be required to take corrective actions.

5 Contents Preface Purpose Prequisites Intended Audience Conventions Used in This Book Support Resources Avaya Technology and Consulting (ATAC) Communications, Solutions, and Integration (CSI) Group of Software Services 8 Avaya Technical Service Organization (TSO) Avaya Network Management Software Systems Support Group (NMSSS).. 10 Customized Management Solutions for Avaya Integrated Management Avaya Contact Information Product Documentation How to Access Books on the Web Tell Us What You Think! Chapter 1: Overview Avaya Network Management Applications and Device Managers Network Management Applications Network Management Console Avaya Software Update Manager Avaya Network Configuration Manager Avaya QoS Manager Avaya SMON Manager Avaya Address Manager Device Managers Network Management Framework Chapter 2: Configuring Network Management Applications and Device Managers Overview SNMP Options Configuring SNMPv1 Options for HP OpenView Network Node Manager Configuring SNMPv3 Options Creating an Administrator Community Name Configuring TFTP Server for Solaris Configuring Login Security Issue 1 June

6 Contents Avaya SMON Manager License Entering the Avaya SMON Manager License Entering SMON Device Licenses Configuring Access Security (HP OpenView Network Node Manager Mode Only) 23 Configuring Proxy Settings (Optional) Configuring the Web Server (Optional) Configuring FTP (Optional) Loading Additional MIBs (Optional) Recording Cold Start Traps Installing Two Versions of Java Plug-In Changing Port Numbers Used by Network Management Applications Configuring the Communication Manager Servers Chapter 3: Getting Started Getting Started with Avaya Network Management in Standalone Mode Discovering Your Voice Network Getting Started with Avaya Network Management in HP OpenView Network Node Manager Mode Appendix A: Supported Devices Index Enterprise Network Management Configuration

7 Preface Purpose The purpose of this book is to provide the following information: A broad overview of Avaya Network Management Applications and Device Managers. Procedures that must be performed after the Avaya Network Management Applications and Device Managers software is installed. Instructions on how to get started managing your network using Avaya Network Management in Stand-Alone mode or in HP OpenView Network Node Management mode. Prequisites Network managers should be knowledgeable about network-wide tasks, such as monitoring switching, configuring VLANs, and setting up rules to enhance quality of service. They should also be knowledgeable about managing specific network devices. Intended Audience This book is written for network managers familiar with network management and its fundamental concepts. Issue 1 June

8 Preface Conventions Used in This Book The following typographical conventions are used: Bold type is used to indicate information that you type, buttons in a window, selections in a menu, and the Enter key on the keyboard. It is also used for emphasis. Courier font is used for any information that the computer screen displays. Arrows indicate options that you select from cascading menus; for example, Select File > Open means choose the Open option from the File menu. Support Resources Avaya provides a variety of planning, consulting, and technical services. The following sections describe the resources and services that are available. Avaya Technology and Consulting (ATAC) Avaya Technology and Consulting (ATAC) works with client teams to develop detailed solutions for connectivity to Avaya Communication Manager solutions. The ATAC also designs network configurations. Communications, Solutions, and Integration (CSI) Group of Software Services Avaya Communications, Solutions, and Integration (CSI) Group of Software Services offers customers the following services: Platform readiness verification Remote implementation and installation Network management server configuration Customer acceptance verification Custom on-site services 8 Enterprise Network Management Configuration

9 Support Resources The CSI Group consists of the following two teams: Converged Solutions Implementation Engineering The Converged Solutions Implementation Engineering (CSIE) team implements multi-site media gateway (G350/G650/G700) deployment projects for both voice and data design. The overall direction of the CSIE team is to bring the correct methodology to these complex deployments that span various regions and to provide continuity to the overall project from the voice and data implementation standpoint. Data Network Implementation Engineering (formerly RNIS) The Data Network Implementation Engineering team implements and/or upgrades existing or new data networks. This team analyzes the customer s network design requirements and performance expectations, and then creates the hardware and software installation specification used to implement data devices including Cajun, VPN, Wireless LAN, Secure Gateways, Extreme, and multi-vendor data equipment. The CSI Group provides support on a contract basis. You can purchase various implementation offers from the CSI Group in Tampa, Florida. See Table 1: Customer-Accessible Resources on page 11 for contact information. Avaya Technical Service Organization (TSO) The Avaya Technical Service Organization (TSO) provides support to the Avaya Integrated Management client teams, field technicians, and customers. The TSO will bill customers for support on a time and materials basis if the following conditions exist: Customers do not provide remote access. Customers do not have a current maintenance agreement. Customers do not procure and install the required systems and software as defined in the Integrated Management Services Support Plan. Customers request support that is outside the purchase agreement. The TSO does not support hardware or software that customers purchase from third-party vendors. Issue 1 June

10 Preface Avaya Network Management Software Systems Support Group (NMSSS) The Avaya Network Management Software Systems Support Group (NMSSS) in Tampa Bay, Florida answers customer calls about products in Avaya Integrated Management. NMSSS will either answer your questions directly or connect you with an associate who can answer questions about the products. Customized Management Solutions for Avaya Integrated Management The Integrated Management Product Team understands customer s needs and is focused on customer satisfaction. See Table 1: Customer-Accessible Resources on page 11 for contact information. The Product Team will assist customers with Avaya Integrated Management projects and will provide: Project Management An Integrated Management project person will work with the customer to access configuration and customization requirements for any or all applications within each Avaya Integrated Management offer. If custom work is required, the evaluation will include a proposed statement of work and price. Note that this offer is not intended to provide installation for customers that choose to implement Integrated Management applications using Avaya Services or third-party implementation services. Training Basic training can be performed remotely using an interactive medium to display the applications and a conference bridge for audio. On-site training can be customized to meet the customer s needs. Customized training will focus on application functionality that is relevant to the customer and provide focused knowledge transfer to facilitate application-specific training. 10 Enterprise Network Management Configuration

11 Support Resources Avaya Contact Information Table 1 and Table 2 provide contact information that you may use if you need assistance during the process of installing and setting up Avaya Integrated Management. To access the links in Table 2, you must be able to access the Avaya intranet. Table 1: Customer-Accessible Resources Resource Avaya Support Center Network Management Software Systems Support (NMSSS) Communications, Solutions, and Integration (CSI) Group of Software Services Integrated Management Product Team Contact Information , prompt 3 Send to: [email protected] Toll Fraud Intervention , prompt 1 Table 2: Avaya Internal Resources Resource Avaya System Management Support Avaya Technology and Consulting (ATAC) Communications, Solutions, and Integration (CSI) Group of Software Services Integrated Management Services Support Plan Contact Information , prompt 2,6 (requires a password) data-implementation-services/ Issue 1 June

12 Preface Product Documentation The latest version of Avaya Integrated Management product documentation, including this book, is available from the Avaya Support Web Site. To view or download these books from the Web, you must have access to the Internet, an Internet browser, and Adobe Acrobat Reader, version 5.0 or later. Adobe Acrobat Reader is provided on the Windows Server CD and is also available from See How to Access Books on the Web for instructions on how to view or download these books. How to Access Books on the Web To view or download books from the Avaya Support Web Site, follow these steps: 1. Access 2. In the left column, click System and Network Management. 3. Scroll to Integrated Management, locate the product name, and click the link corresponding to the software release to display a list of available books for that product. Tell Us What You Think! Let us know how this book measured up to your expectations. Your opinions are crucial to helping us meet your needs! Send us your comments by mail, fax, or as follows: Mail: Fax: Subject: Avaya Inc. Avaya Integrated Management Documentation Team Room 3C Middletown Lincroft Rd. Lincroft, NJ USA Avaya Integrated Management Documentation Team [email protected] Avaya Integrated Management Documentation Team 12 Enterprise Network Management Configuration

13 Chapter 1: Overview Avaya Network Management Applications and Device Managers Avaya Network Management Applications and Device Managers are part of Avaya Integrated Management, which provides a complete set of tools and an applications platform. All of the tools in Avaya Integrated Management are accessible through a common Web-based user interface to facilitate system and network management. Avaya Network Management Applications and Device Managers are SNMP based network management applications. There are different types of applications to fill different network management needs, as further described below. Network Management Applications Avaya Network Management Applications are network-wide applications that allow you to manage Avaya media gateways, Avaya LAN and backbone switches, and wireless access points in your network as a whole. These applications allow you to configure Avaya media gateways and VLANs, monitor switching, set up rules to enhance quality of service, and perform other important network tasks. For example, one Avaya Network Management application is Avaya SMON Manager which provides advanced switch monitoring (Avaya Integrated Management includes a 90-day trial version of Avaya SMON Manager, and you can purchase a license to continue use beyond 90 days). Avaya SMON Manager monitors the Ethernet switching fabric and gives you a complete top-down view of all switched traffic across your network. Other network-wide applications include Avaya Network Configuration Manager for multiple device and port configuration, Avaya QoS Manager for configuring policy-based management, Avaya VLAN Manager for configuring and monitoring VLANs, Avaya Address Manager for mapping hosts to switch ports, and Avaya Software Update Manager for automatically updating your network devices with the most up-to-date software. A further description of the Avaya Network Management Applications is provided in the following sections. For more details about a specific application, refer to the application s user guide. Issue 1 June

14 Overview Network Management Console Avaya Network Management Console is an application that allows you to view the devices in your network. Avaya Network Management Console also provides a platform from which you can launch applications to manage network devices and monitor the traffic on your network. In addition, Network Management Console provides a discovery service that searches your network for devices. Network Management Console uses a client/server architecture, allowing multiple users to access the Avaya Network Management Console simultaneously. Web based technology provides a method for accessing and managing your network from any computer with Internet access. Note: Note: Avaya Network Management Console is not available for Solaris servers. Avaya Software Update Manager Avaya Software Update Manager downloads software to managed Avaya devices. Avaya Software Update Manager can also check the software versions currently in use against the latest versions available from Avaya and recommend updates when a newer version is available. You can use Avaya Software Update Manager to retrieve a new release from Avaya s Web site, store it on your hard disk, and subsequently download it to the appropriate device. Avaya Network Configuration Manager Avaya Network Configuration Manager allows you to save device and module configurations and apply them to devices and modules across the network. Device and module configurations can be stored and applied to selected devices and modules. Avaya Network Configuration Manager makes it easy to create an accurate and consistent network configuration. 14 Enterprise Network Management Configuration

15 Network Management Applications Avaya QoS Manager Avaya QoS Manager allows you to configure policy-based management of the traffic on the network. Policy-based management is one of the newest and fastest growing trends in network management. Policy-based management allows network managers to implement forwarding and routing information bandwidth prioritization based on policies and rules, and focus on QoS. Instead of routing packets only by their destination address, Avaya QoS Manager allows you to assign a priority or block packets based on the source and destination addresses, and protocols. This can help you provide services that rely on consistent levels of forwarding service. Avaya SMON Manager Avaya SMON Manager is a collection of applications that work together with the other Avaya Network Management components to provide a full spectrum of in-depth monitoring of switch traffic and network performance. Avaya SMON Manager consists of a software console application on a workstation and remote monitoring probes in network devices that support SMON. The Avaya SMON Manager console constantly communicates with the SMON devices on your network. The console uses SNMP to gather information from the devices. Avaya SMON Manager provides a suite of powerful graphic display tools to view this information. Avaya SMON Manager provides you with detailed analysis of the traffic flow on your switched network, from a global view down to a specific host, and from total MAC layer traffic down to a specific application protocol all in real-time. SMON monitoring provides the following information: A global view of traffic for all switches on the network. An overall view of traffic passing through a specific switch. Detailed data about the hosts transmitting packets or cells through a switch. An analysis of traffic passing through each port connected to a switch. Avaya Address Manager Avaya Address Manager allows you to see which network devices are directly attached to the ports on your network devices. Using advanced network searches, Avaya Address Manager helps you build, maintain, and display a centralized list of hosts discovered in the network with their MAC and IP addresses, and device port connectivity. In addition, Avaya Address Manager enables you to print or export the list. You can also import connections into Avaya Address Manager. Issue 1 June

16 Overview Avaya Address Manager helps you rapidly locate a host or switch port on the network and find duplicate IP addresses in the network. Device Managers Device Managers are applications that are tailored to manage and monitor Avaya media gateways and LAN and backbone switches. Device Managers allow you to set up, configure, monitor, manage, and diagnose all Avaya network devices. They provide a real-time view of each device, called the chassis view. The view uses color coding to indicate individual port, module, and LAG statuses. You can use the Device Manager to configure port, LAG, and VLAN settings, port security, redundancy modes, and all other device parameters. An example of an Avaya Device Manager is shown in Figure 1. Figure 1: Avaya Device Manager In addition, each device can be monitored using Avaya s Device SMON applications. Device SMON provides switch monitoring capabilities, as well as graphs and pie charts displaying traffic types on ports, VLANs, and switches. 16 Enterprise Network Management Configuration

17 Network Management Framework Network Management Framework Avaya Network Management Applications and Device Managers run within the framework of a network management application. The framework management application provides easy access to Device Managers and Network Management Applications. It also provides a view of your entire network. You can use HP OpenView Network Node Manager as the framework. This is called running Avaya Network Management in HP OpenView Network Node Manager Mode. In this mode, the framework also provides an overall view of the multi-vendor network to the network administrator and defines the scope of the network to Avaya Network Management applications. Alternatively, you an use Avaya Network Management Console to run Avaya Network Management in Standalone Mode. See Network Management Console on page 14 for more information. Note: Note: Avaya Network Management can run in Standalone Mode only on a Windows server. For Solaris installations, Avaya Network Management must run in HP OpenView Network Node Manager Mode. Issue 1 June

18 Overview 18 Enterprise Network Management Configuration

19 Chapter 2: Configuring Network Management Applications and Device Managers Overview This provides Applications and Device Managers. SNMP Options Information on configuring SNMP for Avaya Network Management. Configuring TFTP Server for Solaris Information on configuring TFTP service for Solaris installations. Configuring Login Security Information on configuring secure login mode for Avaya Network Management. Avaya SMON Manager License Information on entering SMON licenses for Avaya Network Management and Device Managers. Configuring Access Security (HP OpenView Network Node Manager Mode Only) - Information on configuring access security for Avaya Network Management in HP-OV NNM Mode. Configuring Proxy Settings (Optional) Information on configuring Avaya Network Management to work through a proxy server. Configuring the Web Server (Optional) Information on configuring a custom web server to work with Avaya Network Management. Configuring FTP (Optional) Information on configuring an FTP server to work with Avaya Network Management. Loading Additional MIBs (Optional) Information on loading additional SNMP MIBs into Avaya Network Management. Recording Cold Start Traps Information on changing the default setting for this feature in HP OpenView Network Node Manager with the recommended value for Avaya Network Management. Installing Two Versions of Java Plug-In Information on how to install two different versions of Java Plug-In in order to use different releases of Device Manager software which require Java Plug-In and Java Plug-In Changing Port Numbers Used by Network Management Applications Information on how to change the TCP port numbers of the Network Management server and client applications. Issue 1 June

20 Configuring Network Management Applications and Device Managers Configuring the Communication Manager Servers on page 34 Information on configuring the Communication Manager servers to view them properly in Network Management Console with SystemView. For instructions on how to install Applications and Device Managers see the following books: For instructions on how to install Applications and Device Managers on a Windows server, see Avaya Integrated Management, Release 3.0, Enterprise Network Management Installation and Upgrade, document number For instructions on how to install Applications and Device Managers on a Solaris server, see Avaya Integrated Management, Release 3.0, Network Management for Solaris Installation and Upgrade, document number SNMP Options This section provides information on configuring SNMP options for Avaya Network Management. You should set up read-write communities for all devices and read-only communities for key devices. If you are using SNMPv1, set up user names and passwords. For more information on configuring SNMP, including configuring SNMPv1 options for Stand Alone mode, see Avaya Network Management Console in Standalone Mode User Guide. Configuring SNMPv1 Options for HP OpenView Network Node Manager Once you set the SNMP community string on a device, it can be used to manage a device using Avaya Network Management. To configure SNMPv1 options for HP OpenView Network Node Manager, follow these steps: 1. Start HP OpenView Network Node Manager by typing ovw. 2. In HP OpenView Network Node Manager, select Options > SNMP Configuration. The SNMP Configuration dialog box opens. 3. In the Specific Node tab, click Add. The SNMP Parameters dialog box opens. 4. In the Target field, enter the IP address for the switch that sends trap information. 5. In the Community field, enter public for general read access for another applicable value to limit read access. 6. In the Set Community field, enter the community string assigned to the computer designated as the trap recipient. This provides read/write access. This computer is set up as a trap recipient in the Avaya Switch Web Agent. 20 Enterprise Network Management Configuration

21 SNMP Options 7. Click OK to save the changes and close the SNMP Parameters dialog box. 8. Perform one of the following steps: Click Apply to save the changes and continue adding target switches. Click OK to save changes and close the SNMP Configuration dialog box. For more information on configuring SNMP options for HP OpenView Network Node Manager, see Using Network Node Manager - HP OpenView. Configuring SNMPv3 Options To use SNMPv3 with Avaya Network Management, you must enable Login Mode and configure user names and passwords. For more information on configuring Login Mode and user names and passwords, see the Avaya Secure Access Administration User Guide. To enable HP OpenView Network Node Manager for use with SNMPv3, you must first install the HP-OV NNM SNMP Security Pack. Contact your HP dealer for details. For more information on configuring SNMPv3 when using Avaya Network Management in HP OpenView Network Node Manager mode, see the HP-OV NNM Administrator s Guide and the HP-OV NNM Security Pack Reference Guide. Creating an Administrator Community Name Some features of the Avaya P580/P882 Manager require you to connect to the device using an SNMP community name with Administrator privileges. It is important that you create a community name with Administrator privileges on each Avaya P580/P882 device in your network. You can create a community name with Administrator privileges using the CLI or the Embedded Web Manager. For more information, refer to the Avaya P580/P882 Operations Guide. Issue 1 June

22 Configuring Network Management Applications and Device Managers Configuring TFTP Server for Solaris Avaya Network Configuration Manager and Avaya Software Update Manager use TFTP to transfer files to and from Avaya network devices. To use these applications, you must configure TFTP server settings on your Solaris server. To verify TFTP server configuration, open the /etc/inetd.conf file and search for the following entry: tftp dgram udp wait root /usr/sbin/in.tftpd in.tftpd - s /tftpboot Ensure that there is not a # character at the beginning of this entry. If there is not, TFTP service is enabled on your server. By default, the TFTP server runs in secure mode, allowing access only to files in the /tftpboot directory. Avaya Network Configuration Manager and Avaya Software Update Manager must be configured with /tftpboot as the Secure Network Path to allow required access to files on your server. Configuring Login Security Avaya Network Management offers secure Login Mode which allows definitions of user names and passwords. In this mode, Network Management Application and Device Manager users are prompted for a login name and password. For more information, see the Avaya Secure Access Administration User Guide. Avaya SMON Manager License There are two Avaya Integrated Management offers that provide Avaya SMON Manager the Enterprise Network Management offer and the Network Management on Solaris offer. A 90-day trial version of Avaya SMON Manager is provided. Customers have the option of purchasing the SMON Manager license key. This key is required to fully activate the SMON Manager beyond the 90-day trial period so that Avaya SMON Manager can be used on a permanent basis. 22 Enterprise Network Management Configuration

23 Configuring Access Security (HP OpenView Network Node Manager Mode Only) Entering the Avaya SMON Manager License The first time you launch Avaya SMON Manager, you are prompted for the license key. Enter the license key if you have purchased one. The license key allows unlimited use of Avaya SMON Manager. If you have not purchased a license key, press Enter when you are prompted for the license key. You will be able to use Avaya SMON Manager for the 90-day trial period. To purchase a license key, contact your Avaya representative. Entering SMON Device Licenses An SMON device license is required to use SMON Manager on most Avaya network devices. SMON Manager for P130, P330, and C460 device managers do not require an SMON device license for the first 90 days of use. After 90 days from initial use, the SMON device license is disabled unless you enter a valid permanent SMON device license. For information on entering SMON device licenses, refer to your device s SMON Installation Guide. Note: Note: You can run SMON Manager on the Avaya P580/P882 without an SMON device license. For information on purchasing SMON device licenses for your Avaya network devices, contact your Avaya representative. Configuring Access Security (HP OpenView Network Node Manager Mode Only) To prevent unauthorized users from accessing your network, It is recommended that you configure access security in HP OpenView Network Node Manager. The following procedures provide instructions for configuring access security for Avaya Network Management using the features in HP OpenView Network Node Manager. 1. Open the NNM_Directory\www\conf\session.conf file in a text editor, where NNM_Directory is the directory in which HP OpenView Network Node Manager is installed. For Solaris installations, the file is located in /etc/opt/ov/share/www/conf/session.conf. 2. Change the User Login parameter to on. 3. Save the file. 4. Close the text editor. Issue 1 June

24 Configuring Network Management Applications and Device Managers 5. Open a command line window. 6. Enter Ovhtpasswd <new_user> where new_user is the user name for accessing Avaya Network Management. 7. Open the NNM_Directory\www\etc\htpasswd file in a text editor, where NNM_Directory is the directory in which HP OpenView Network Node Manager is installed. For Solaris installations, this file is located in /etc/opt/ov/share/www/etc/htpasswd. 8. Ensure that the user added in Step 6 appears. 9. Close the file. Access security is configured for Avaya Network Management in HP OpenView Network Node Manager Mode. Configuring Proxy Settings (Optional) If your network has a non-permissive firewall, you must configure Avaya Network Management to work with your proxy server. This will enable Avaya Software Update Manager s Analyze and Retrieve from the Web functions. To configure Avaya Network Management to work with your proxy server, follow these steps: 1. Type ovstop at a command-line prompt to stop HP OpenView Network Node background processes, if they are running. 2. Open the Avaya_Net_Mgt/cvs/private/gen/cv.prop file in a text editor, where Avaya_Net_Mgt is the directory in which Avaya Network Management is installed. For Solaris installations, the file is located in /opt/avaya/privatennm/gen/cv.prop. 3. Edit the line starting proxy.host= to proxy.host=<proxy_name> where Proxy_name is the IP address or DNS name of your proxy server. For example, proxy.host=avaya.proxy.com. 4. Edit the line starting proxy.port= to proxy.port=<proxy_port> where Proxy_port is the port used by your proxy server. For example, proxy.port= Save the file. Avaya Network Management is configured to work with your proxy server. 24 Enterprise Network Management Configuration

25 Configuring the Web Server (Optional) Configuring the Web Server (Optional) The Avaya Integrated Management application installs the Apache 2.0 HTTP server and configures it for use with Avaya Integrated Management applications. For installations using a custom HTTP server, insert the definitions script into the HTTP server s configuration file. To configure Avaya Network Management for Solaris to use the web server, perform the following steps: 1. Open the file /opt/avaya/privatennm/gen/cv.prop. 2. Edit the entry ov.http.port= to ov.http.port=<ov_http_port> where OV_http_port is the port used by your web server. For example, ov.http.port=8080. The port to be used is found in your web server configuration. To use Voice Integration services, perform the following steps: 1. Open the file /etc/profile. 2. Add entries for AIM_FPM=<fpm_ip_address> and AIM_MSA=<msa_ip_address> where fpm_ip_address is the IP address of the server running Avaya Fault and Performance Manager and msa_ip_address is the server running Avaya MultiSite Administration. 3. After you add the AIM_FPM and AIM_MSA entries, add an entry export AIM_FPM AIM_MSA to enable the server to use the values you configured. Issue 1 June

26 Configuring Network Management Applications and Device Managers Following is an example of a configuration script for an Apache web server running with Avaya Network Management in HP OpenView Network Node Manager Mode on a Windows server. PassEnv AIM_FPM PassEnv AIM_MSA PassEnv CV_PATH #Aliases: Alias /launch_nnm "C:/Program Files/Avaya/Network Management/Ntov/ Launch" <Directory "C:/Program Files/Avaya/Network Management/Ntov/Launch"> AddHandler cgi-script.covpl Options +ExecCGI AllowOverride None Order allow,deny Allow from all </Directory> Alias /nm_nnm "C:/Program Files/Avaya/Network Management/Ntov" Alias /nm_nnm "C:/Program Files/Avaya/Network Management/Ntov" <Directory "C:/Program Files/Avaya/Network Management/Ntov"> AddHandler cgi-script.covpl Options +ExecCGI AllowOverride None Order allow,deny Allow from all </Directory> #Access restriction: <Directory "C:/Program Files/Avaya/Network Management/Ntov/Gen/ resources/private"> Deny from all </Directory> 26 Enterprise Network Management Configuration

27 Configuring the Web Server (Optional) Following is an example of a configuration script for an Apache web server running with Avaya Network Management in Standalone Mode on a Windows server: PassEnv AIM_FPM PassEnv AIM_MSA PassEnv CV_PATH #Aliases: Alias /launch "C:/Program Files/Avaya/Network Management/CVS/Launch" <Directory "C:/Program Files/Avaya/Network Management/CVS/Launch"> AddHandler cgi-script.cvpl Options +ExecCGI AllowOverride None Order allow,deny Allow from all </Directory> Alias /nm "C:/Program Files/Avaya/Network Management/CVS Alias /nm "C:/Program Files/Avaya/Network Management/CVS <Directory "C:/Program Files/Avaya/Network Management/CVS"> AddHandler cgi-script.cvpl Options +ExecCGI AllowOverride None Order allow,deny Allow from all </Directory> #Access restriction: <Directory "C:/Program Files/Avaya/Network Management/CVS/Gen/resources/ private"> Deny from all </Directory> Issue 1 June

28 Configuring Network Management Applications and Device Managers Following is an example of a configuration script for an Apache web server running with Avaya Network Management in HP OpenView Network Node Manager Mode on a Solaris server: PassEnv AIM_MSA PassEnv AIM_FPM #Aliases: Alias /launch_nnm /opt/avaya/nm/launch <Directory /opt/avaya/nm/launch > AddHandler cgi-script.covpl Options +ExecCGI AllowOverride None Order allow,deny Allow from all </Directory> Alias /nm_nnm /opt/avaya/nm Alias /NM_nnm /opt/avaya/nm <Directory /opt/avaya/nm > AddHandler cgi-script.covpl Options +ExecCGI AllowOverride None Order allow,deny Allow from all </Directory> #Access Restriction: <Directory /opt/avaya/nm/gen/resources/private > Deny from all </Directory> Configuring FTP (Optional) FTP is supported by Avaya Software Update Manager and Avaya Network Configuration Manager for certain network switches and gateways. To configure FTP service on your Windows server, follow these steps: 1. Create a user on the Windows server. 2. Select Start > Control Panel > Administrative Tools > Internet Services Manager. 3. Select Default FTP Site. 4. Select the Home Directory tab. 5. Under FTP Site Directory, select Read and Write. 6. Click Apply to save changes. 7. Close the Control Panel. 8. Open Avaya Software Update Manager. 9. Select File > Options. The Options dialog box opens. 28 Enterprise Network Management Configuration

29 Loading Additional MIBs (Optional) 10. In the FTP Global Use field, select Enabled. 11. In the FTP User Name and Password field, enter the user name and password you created. 12. In the FTP Server Page field, enter the path of the FTP Site Directory on your server. 13. Click Apply to save the changes. The FTP server is configured to work with Avaya Software Update Manager. Note: Note: The procedure is identical for Network Configuration Manager. To configure FTP service on your Solaris serve, follow these stepsr: 1. Open the /etc/inetd.conf and search for the entry: ftp stream tcp6 nowait root /usr/sbin/in.ftpd in.ftpd -a Verify that the entry does not begin with a # character. 2. Open Avaya Software Update Manager. 3. Select File > Options. The Options dialog box appears. 4. In the FTP Global Use field, select Enabled. 5. In the FTP User Name and Password field, enter the user name and password you created. 6. In the FTP Server Page field, enter the path of the FTP Site Directory on your computer. 7. Click Apply to save the changes. The FTP server is configured to work with Avaya Software Update Manager. Loading Additional MIBs (Optional) Some Avaya MIBs are loaded automatically when you install Avaya Network Management. If you want to install additional MIBs, follow these steps: 1. In HP OpenView Network Node Manager, select Options > Load/Unload MIBs:SNMP. The Load/Unload MIBs:SNMP dialog box appears. 2. Click Load. A directory browser appears. 3. Navigate to the <Install_Directory>/snmpmibs directory, where Install_Directory is the directory in which you installed Avaya Network Management. 4. Select the MIBs you wish to add to the MIBs database. 5. Click Open. The new MIBs are loaded. For more information, see Managing Your Network with HP OpenView Network Node Manager 6.2. Issue 1 June

30 Configuring Network Management Applications and Device Managers Recording Cold Start Traps The default setting in HP OpenView Network Node Manager is not to record cold start traps in the Event Log. To change the default setting and record cold start traps in the Event Log, follow these steps: 1. In HP OpenView Network Node Manager, select Options > Event Configuration. The Event Configuration dialog box opens. 2. In the Enterprises window, select snmptraps. 3. In the Events for Enterprise snmptraps ( ) window, double-click SNMP_Cold_Start. The Modify Events dialog box opens. 4. Click the Event Messages tab. 5. Click Log and display in category. 6. Select a category in which cold start traps will be displayed. 7. Click OK. Cold start traps appear in the selected category. 30 Enterprise Network Management Configuration

31 Installing Two Versions of Java Plug-In Installing Two Versions of Java Plug-In Different releases of Device Manager software installed on certain Device Managers require different releases of the Java Plug-In. If not installed properly, using Java Plug-In and Java Plug-In on the same station may prevent Avaya Network Management Console from opening on a remote Internet Explorer browser. Table 3 shows which version of the Java Plug-In is required for the Avaya Device Manager. Table 3: Device Manager Software and Java Plug-In Versions Device Manager Version Java Plug-In Required Avaya P130 Manager Avaya P330 Manager Avaya P330-ML Manager Avaya C460 Manager Avaya C360 Manager Avaya G700 Manager Avaya G350 Manager In order to use both versions of the Java Plug-In at the same time, follow these steps: 1. If you installed Java Plug-In before Java Plug-In 1.3.1, remove Java Plug-In Install Java Plug-In During the installation, ensure that the Internet Explorer checkbox in the Browser Registration dialog box is not checked. 3. Install Java Plug-In During the installation, ensure that the Internet Explorer checkbox in the Browser Registration dialog box is not checked. 4. After both Java Plug-Ins are installed, ensure that both Java Plug-Ins are not set to be the default plug-in for Internet Explorer. To do this, follow these steps for each Java Plug-In version: a. Select Start > Settings> Control Panel > Java Plug-In. The Java Plug-In control panel dialog box appears. b. Click the Browser tab. The Browser Settings dialog box appears. Issue 1 June

32 Configuring Network Management Applications and Device Managers Note: c. Click the check box for Microsoft Internet Explorer to deselect it, and click the Apply button. d. Close the Java Plug-In control panel dialog box. Note: It is recommended that you back up the Windows registry before continuing with this procedure. 5. Create a new registry file with any text editor, such as Notepad, by adding the.reg extension to the filename, for example, jrefix.reg. 6. Add the following 5 lines to the file: Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\CLSID\{8AD9C E-11D1-B3E F499D93}\ [HKEY_CLASSES_ROOT\CLSID\{8AD9C E-11D1-B3E F499D93}\ 7. Save and close the file. 8. Double-click the filename to execute the file. 9. Click the OK button in the dialog box to confirm merging the file with the registry. Now when you open two different Device Manager applications that require two different Java Plug-Ins, two separate Internet Explorer sessions are launched. 32 Enterprise Network Management Configuration

33 Changing Port Numbers Used by Network Management Applications Changing Port Numbers Used by Network Management Applications You are able to change the TCP port numbers of the Network Management server and client applications. You can use a firewall to block incoming and outgoing TCP connections to port numbers that are not used by the Network Management Applications. Firewalls may be set on the Network Management server station and on any client station that is used to remotely access the server machine. The firewall on the web server port (the default installation is set to port 80) is required to allow http connections. The port numbers are listed in the cv.prop file in the following locations: <Avaya application location>\network Management\private\gen\(in standalone mode) <Avaya application location>\network Management\privateNNM\gen\(in NNM mode) The cv.prop file contains a list of properties. Most of the properties define fixed port numbers used by the Network Management Applications. Two of the properties,.rmiport.min=2900 and.rmiport.max=2950, define a range of 50 port numbers. To change the port numbers, follow these steps: 1. Stop the Network Management server (or HP OpenView server). 2. Change the ports in the cv.prop file. 3. Run the updateresources.bat batch file that resides in the same directory as the cv.prop file. 4. Restart the server. Issue 1 June

34 Configuring Network Management Applications and Device Managers Configuring the Communication Manager Servers To see the Communication Manager servers properly in the Network Management Console with SystemView, you must perform the following steps for each Communication Manager: 1. From Internet Explorer, enter the IP address of the Communication Manager server, and press the Enter key. 2. Log into the Communication Manager server. 3. Click Launch Maintenance Web Interface. The Integrated Management Maintenance Web Pages page appears. 4. Click SNMP Agents in the left panel. The SNMP Agents page appears. 5. On the SNMP Agents page, do the following: a. If the Master Agent status is Down, click the Start button to turn the Master Agent on. b. Under the IP Addresses for SNMP Access section, do one of the following: Select the Any IP address option button for all IP addresses to have SNMP access. Select the Following IP addresses option button and enter the IP addresses to which you want to give SNMP access. c. Under the SNMP Users/Communities section, do one of the following: Check the Enable SNMP Version 1 checkbox and enter the community names. Check the Enable SNMP Version 2c checkbox and enter the community names. Check the Enable SNMP Version 3 checkbox and enter the user name and password for the read-only user and read-write user. d. Under the Communication Manager SNMP Agent section, check the Enable Agent checkbox and enter any string, such as abcdefgh, for the Agent ACP Login password. e. Click the Submit button. 6. Click SNMP Traps in the left panel. The SNMP Traps page appears. 7. Click the Add button. The Add Trap Destination page appears. 34 Enterprise Network Management Configuration

35 Configuring the Communication Manager Servers Note: 8. On the Add Trap Destination page, do the following: a. Ensure the checkbox for Check to enable this destination is checked. b. Enter the IP address of the management station, and then do one of the following: Check the SNMP version 1 option button, and enter the community name. Check the SNMP version 2c option button, ensure notification type is trap, and enter the community name. Check the SNMP version 3 option button, ensure notification type is trap, and enter the user name and password. c. Click the Add button. 9. Click Firewall in the left panel. The Firewall page appears. 10. On the Firewall page, do the following: a. Click the Advanced Setting button. b. Ensure the input and output check boxes for port 161 and port 162 are checked. c. Click the Submit button. 11. Open the Network Management Console application. 12. Select File > Options. 13. Select the CM Servers Passwords tab. 14. Enter the IP address, user name, and password for each Communication Manager server. 15. Select the SNMP Access tab. 16. Set up the SNMP rule for the Communication Manager server IP addresses. Note: The SNMP time-out value must be set to 60 seconds, and the retries value must be set to Run Network Discovery. See Steps 5 through 9 in Discovering Your Voice Network on page 38. Issue 1 June

36 Configuring Network Management Applications and Device Managers 36 Enterprise Network Management Configuration

37 Chapter 3: Getting Started Getting Started with Avaya Network Management in Standalone Mode After installing Avaya Network Management to run in Standalone Mode, the following steps will help you start managing your network using Avaya Network Management. 1. Ensure that Avaya Network Management Server is running. Avaya Network Management Server is a Windows service and should start automatically when you boot the server station. To check the status of Avaya Network Management Server, select Start > Programs > Avaya > Network Management Server > Avaya Network Management Server Status. A dialog box opens with the current Network Management Server status. If Network Management Server is not running, start Network Management Server. To start Network Management Server, select Start > Programs > Avaya > Network Management Server > Start Avaya Network Management Server. 2. Start Avaya Network Management Console.discover the subnets and objects in your network and save the results in the current Network Map. See Discovering Your Voice Network on page 38 for more information. 3. Configure your Communication Manager server to work with Avaya Network Management Console. See Configuring the Communication Manager Servers on page Add Avaya Network Management Server to the device s list of Trap Managers. For more information, refer to each device manager s user guide or on-line help. 5. Configure the devices in your network. Device configuration can be performed using the Device Managers and Avaya Network Configuration Manager. For instructions on configuring devices, see the user guide for each Device Manager, the Avaya Network Configuration Manager User Guide, or the on-line help. Issue 1 June

38 Getting Started Discovering Your Voice Network The first time you open Network Management Console, you must discover your voice network. The steps outlined below provide a high-level description of how to discover your network. For more detailed information, see Discovering Your Network in the Avaya Network Management Console User Guide. 1. Open the Network Management Console Double-click the Network Management Console desktop icon to open the Network Management Console. 2. Define SNMPv3 Users From the toolbar In the Network Management Console window, select Actions > Avaya Secure Access Administration and define SNMPv3/CLI users. See the appropriate application user guide for details. Note: Note: The SNMPv3 Authentication Type must be MD5, and the Privacy Type must be DES. 3. Define SNMP Rules From the toolbar In the Network Management Console window, select File > Options. The Options dialog box appears. Click the SNMP Rules tab and define the SNMPv3/SNMPv1 options that fit your network. See the Network Management Console User Guide for details. 4. Configure the Communication Manager servers See Configuring the Communication Manager Servers on page 34 for the procedure you must perform in order to see the Communication Manager servers properly in the Network Management Console with SystemView. The Communication Manager servers will be queried for phone extensions and user names. 5. Open the IP Discovery dialog box From the toolbar In the Network Management Console window, select Actions > IP Discovery. The IP Discovery dialog box appears in the Discovery window. 6. Define the Default Gateway From the toolbar in the Discovery window, select File > Options and then click the IP Discovery tab. Enter the IP address of the default gateway for this station. Blank is acceptable. 7. Choose the Device Types In Discovery window, click the Discovered Types tab. Choose the types of devices you want to discover. If you want to see regular IP stations and unsupported devices, move Generic IP and Generic SNMP from the Undiscovered Types list to the Discovered Types list. 8. Add Subnets to Discover From the toolbar in the Discovery window, select Edit > Add. The Add New Subnet dialog box appears. Enter the Subnet IP address and then either the Subnet Mask address or the Router IP address. Repeat this step for all subnets you want to discover. 38 Enterprise Network Management Configuration

39 Getting Started with Avaya Network Management in HP OpenView Network Node Manager Mode Note: Note: If you are using the Router IP address, make sure the SNMP rules are correct for this router. 9. Run Network Discovery From the toolbar in the Discovery window, select Actions > Start Network Discovery. Network discovery begins immediately. Network discovery may take some time depending on the size of your network. Getting Started with Avaya Network Management in HP OpenView Network Node Manager Mode The tasks listed in this section should be performed only after completing the post-installation tasks provided in Chapter 2: Configuring Network Management Applications and Device Managers on page 19. After installing Avaya Network Management to run in HP OpenView Network Node Manager Mode, the following steps will help you start managing your network using Avaya Network Management. 1. Ensure that HP OpenView Network Node Manager background processes are running. HP OpenView Network Node Manager background processes are a Windows service and should start automatically when you boot the server station. If HP OpenView Network Node Manager background processes are not running, start them. To start the background processes, select Start > Programs > HP OpenView > Network Node Manager Admin > NNM Services - Start. 2. Start HP OpenView Network Node Manager.HP OpenView Network Node Manager 3. Discover the subnets and nodes in your network. For instructions on discovering your network, refer to HP Network Node Manager for Windows NT User Guide. 4. Add the HP OpenView Network Node Manager server to the device s list of Trap Managers. For more information, refer to each Device Manager s user guide or on-line help. 5. Configure the devices in your network. Device configuration can be performed using the Device Managers and Avaya Network Configuration Manager. For instructions on configuring devices, refer to each Device Manager s user guide, Avaya Network Configuration Manager User Guide, or the on-line help. Issue 1 June

40 Getting Started 40 Enterprise Network Management Configuration

41 Appendix A: Supported Devices Table 4 provides a list of Avaya Network Management Applications and shows the devices that are supported by each application. Not every Network Management Application supports every device. Table 4: Supported Devices for Avaya Network Management Applications Application Avaya Network Management Console Avaya SMON Manager Avaya Network Configuration Manager Avaya QoS Manager Avaya Software Update Manager Avaya Address Manager Supported Devices P130, P330, P580/P882, G350, W310, C360, C460 P130, P330, P580/P882, W310, C360, C460 P130, P330, P580/P882, G350, W310, C360, C460 P130, P330, P580/P882, G350, W310, C360, C460 P130, P330, P580/P882, G350, W310, C360, C460 P130, P330, P580/P882, G350, W310, C360, C460 Issue 1 June

42 Supported Devices 42 Enterprise Network Management Configuration

43 Index Index Symbols >, meaning of in text A Avaya support resources support web site Avaya Network Management Applications Avaya Address Manager Avaya Network Configuration Manager Avaya QoS Manager Avaya SMON Manager Avaya Software Update Manager Network Management Console B bold text, meaning of C contact information for Avaya courier font, meaning of D Device Managers F feedback about this book J Java Plug-In version version R resources Avaya Communications, Solutions, and Integration (CSI) Group of Software Services Avaya Network Management Software Systems Support Group (NMSSS) Avaya Technical Service Organization (TSO) Avaya Technology and Consulting (ATAC) Customized Management Solutions for Avaya Integrated Management S SNMP SNMP rule for Communication Manager SNMPv3 Authentication Type Privacy Type T TFTP Server typographical conventions Issue 1 June

44 Index 44 Enterprise Network Management Configuration