Avaya Integrated Management Release 3.1 Integrated Management Database Configuration

Transcription

1 Avaya Integrated Management Release 3.1 Integrated Management Database Configuration Issue 4 February 2006

2 2006 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document may be incorporated in future releases. For full legal page information, please see the complete document, Avaya Legal Page for Software Documentation, Document number To locate this document on the website, simply go to and search for the document number in the search box. Documentation disclaimer Avaya Inc. 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. Link disclaimer Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all of the time and we have no control over the availability of the linked pages. 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: Copyright Except where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law. 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:

3 Contents Preface Purpose Prerequisites Intended Audience Conventions Used in This Book Additional Resources Tell Us What You Think! Product Documentation How to Access Books on the Web Chapter 1: Resources and Notices Getting Help with the Installation Avaya Technology and Consulting (ATAC) Communications, Solutions, and Integration (CSI) Group of Software Services Avaya Technical Service Organization (TSO) Avaya Network Management Software Systems Support Group (NMSSS) Customized Management Solutions for Avaya Integrated Management Avaya Contact Information Third-Party Resources System Security Notices Network Security Toll Fraud Security Avaya Disclaimer Toll Fraud Intervention Chapter 2: Overview What s New in this Release PC Requirements Configuration Checklist Chapter 3: Setting Up IMD Administering an Existing Installation Procedure 1: Log into the Integrated Management Database Procedure 2: Configure the Security Defaults for IMD Procedure 3: Configure the SNMP Settings Procedure 4: Administer SSH Keys for S87xx Voice Systems Issue 4 February

4 Contents Configuring a New Installation Procedure 1: Log into the Integrated Management Database Procedure 2: Add Locations Procedure 3: Configure Notification Procedure 4: Configure the Security Defaults for IMD Procedure 5: Configure the SNMP Settings Procedure 6: Add Elements Add a Voice System Add a Messaging System or Other Application Server Add a Proxy Agent Configuration Add an NMSI/NMS Configuration Procedure 7: Create FPM Roles Procedure 8: Add Users Procedure 9: Assign FPM Roles to Users Adding an SSG as a Proxy Server Importing Configuration Data Viewing the IMD Administration Log Index Avaya Integrated Management Database Configuration

5 Preface Purpose This book explains how to configure Avaya Integrated Management database (IMD). Prerequisites Setting up IMD requires familiarity with network administration, knowledge of the Red Hat implementation of the Linux operating system, and proficiency with Linux administration. This knowledge is not taught in this book but is essential for a successful installation. For this reason, we highly recommend that workstation or network administrators take the primary role in initial configuration. Intended Audience We wrote this book for workstation or network administrators. Conventions Used in This Book In this book, we use the following typographical conventions: We use bold type for emphasis and for any information that you should type; for example: save translation. We use Courier font for any information that the computer screen displays; for example: login. We use arrows to indicate options that you should select on cascading menus; for example: Select File>Open means choose the Open option from the File menu. Issue 4 February

6 Preface Additional Resources For help using IMD, access the IMD online help. It explains how to perform basic administration tasks. To access the online help, click Help on the IMD page. 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! You can send us your comments by mail, fax, or , as follows: Mail: Avaya, Inc. IMD Documentation Team Room 3C Middletown Lincroft Rd. Lincroft, NJ USA Fax: IMD Documentation Team document@avaya.com 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 Avaya Integrated Management CDs and is also available from See How to Access Books on the Web on page 7 for instructions on how to view or download these books. 6 Avaya Integrated Management Database Configuration

7 How to Access Books on the Web How to Access Books on the Web To view or download books from the Avaya Support Web Site, follow these steps: 1. Access 2. Click Find Documentation and Downloads by Product Name. 3. Click the letter I in the alphabet listing. 4. Locate the Integrated Management product or offer name and click the corresponding link. 5. Click View All Documents to display a list of available books for that product or offer. Issue 4 February

8 Preface 8 Avaya Integrated Management Database Configuration

9 Chapter 1: Resources and Notices Avaya provides our customers with a variety of planning, consulting, and technical services. The sections below briefly describe the resources and services that are available. Client executives are your primary contact to obtain information and explore options to meet your specific business needs. Getting Help with the Installation If you are located within the United States and you want help installing or setting up IMD, call your Avaya representative. If you are located outside the United States, call your Avaya representative or distributor. Call at least 4 weeks before the date on which you want to install and configure IMD. Avaya Technology and Consulting (ATAC) Avaya Technology and Consulting (ATAC) works with client teams to develop detailed solutions for connectivity to Avaya media servers running Communication Manager software. The ATAC also designs network configurations to support IMD. 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 Issue 4 February

10 Resources and Notices 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 12 for contact information. Avaya Technical Service Organization (TSO) The Avaya Technical Service Organization (TSO) provides support for IMD to 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 Avaya 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. 10 Avaya Integrated Management Database Configuration

11 Getting Help with the Installation Avaya Network Management Software Systems Support Group (NMSSS) The Network Management Software Systems Support (NMSSS) group in Tampa Bay answers customer calls about applications in Avaya Integrated Management. NMSSS will either answer your questions directly or connect you with an associate who can answer questions about your application. 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 12 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. Issue 4 February

12 Resources and Notices 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 Contact Information Avaya Support Center Network Management Software Systems Support (NMSSS) Communications, Solutions, and Integration (CSI) Group of Software Services Integrated Management Product Team , prompt 3 Send to: AIMtraining@avaya.com 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/ 12 Avaya Integrated Management Database Configuration

13 Third-Party Resources Third-Party Resources The table below lists contact information for third-party vendors. Table 3: Vendor web sites Vendor Microsoft Red Hat Linux Web Sites Main site: Main site: System Security Notices Customers are solely responsible for the security of their system, network, and access to hardware and software. The sections below define the precautions that all customers should take to maintain the security of their systems. Network Security IMD uses the standard security features on the supported Red Hat Linux operating system. Avaya strongly recommends that customers use passwords to prohibit access to their systems and to routinely change those passwords to maintain security. SECURITY ALERT:! SECURITY ALERT: Customers should always change passwords immediately after external vendors have completed installation, maintenance, troubleshooting, or other tasks on their system. Issue 4 February

14 Resources and Notices Toll Fraud Security Although IMD is generally not at risk for toll fraud, customers are solely responsible for the security of their entire telecommunications system. Toll Fraud is the unauthorized use of a company s telecommunications system by unauthorized parties. Unauthorized parties are persons other than the company s employees, agents, subcontractors, or persons working on behalf of the company. Toll fraud can result in substantial additional charges for the company s telecommunications services. The company s system manager is responsible for the security of the company s system, which includes programming and configuring the equipment to prevent unauthorized use. Avaya Disclaimer Avaya does not warrant that this product is immune from or will prevent unauthorized use of common-carrier telecommunications services or facilities accessed through or connected to it. Avaya will not be responsible for any charges that result from such unauthorized use. Toll Fraud Intervention If customers suspect that they are a victims of toll fraud and need technical assistance, they should refer to the phone number listed in Customer-Accessible Resources on page Avaya Integrated Management Database Configuration

15 Chapter 2: Overview Avaya Integrated Management Database is a common data store for device data (such as configurations of voice systems, SIP servers, messaging systems, system adjuncts, and managed applications) that is shared by Avaya Integrated Management applications. The following Avaya Integrated Management applications use the information stored in IMD: Avaya MultiSite Administration (MSA) Avaya Fault and Performance Manager (FPM) Avaya Proxy Agent (PA) What s New in this Release Avaya Integrated Management Database Release 3.1 introduces the following enhancements: Support for the following media servers: - S8400 server - S8720 server A new element type for the Avaya Voice Over IP Monitoring Manager server. The ability to copy an existing element and use that element as a basis for a new element. The ability for Avaya MultiSite Administration Release 3.1 to support secure access to the Modular Messaging adjunct via LDAP over SSL. Enhancements for Avaya Fault and Performance Manager: - The ability for Avaya Fault and Performance Manager to access media gateways via a global default SNMP configuration. - An Assist function that runs Avaya Communication Manager commands automatically. You must assign this function to Avaya Fault and Performance Manager roles. - The ability to assign the HelpDesk function to Avaya Fault and Performance Manager roles. Issue 4 February

16 Overview Security enhancements: - Avaya Integrated Management Database automatically prompts you to change your password after you log in initially using the admin login. - The ability for you to specify the minimum number of characters for passwords. By default, all passwords must be at least eight characters in length and contain at least one alphabetic character and one numeric character. - The ability for you to implement password aging for all logins. After the number of days you specify has elapsed, Avaya Integrated Management Database will prompt the user to change the password. New passwords cannot match any one of the previous four passwords the user has used for this account. - The ability for you to specify how often users can change their passwords. By default, users can change their passwords once per day. PC Requirements To access Avaya Integrated Management Database, your PC should meet the following requirements: Parameter Operating system Other software Processor RAM Available Disk Space CD-ROM Network Connectivity IP Addresses Display Requirement Windows XP Professional Windows 2000 with Service Pack 2 or later, or Windows 2003 Internet Explorer 6.0 with Service Pack 1 and Java Runtime Environment (provided) 600 MHz 256 MB Minimum: 100 MB on the drive that contains the Windows System folder (normally but not always the C: drive) Maximum: Up to 1GB (if this computer is running all Integrated Management client applications) Optional TCP/IP Static or dynamic (DNS preferred) SVGA 16 Avaya Integrated Management Database Configuration

17 Configuration Checklist Configuration Checklist If you upgraded from Avaya Integrated Management Database 3.0, log into the system and administer the system. See Administering an Existing Installation on page 20. If you performed a new installation of the Avaya Integrated Management Release 3.1 software, you must configure IMD. See Configuring a New Installation on page 24. Issue 4 February

18 Overview 18 Avaya Integrated Management Database Configuration

19 Chapter 3: Setting Up IMD In Avaya Integrated Management, the device data (such as configurations of voice systems, messaging systems, system adjuncts, and managed applications) and user accounts are stored in the Integrated Management Database (IMD) and shared by the Integrated Management applications (for example, Avaya MultiSite Administration, Avaya Fault and Performance Manager, and Avaya Proxy Agent). The Avaya Integrated Management applications retrieve this data and verify user accounts from IMD. You must configure IMD before you can use the Integrated Management applications. If you upgraded from Avaya Integrated Management Database 3.0, go to Administering an Existing Installation on page 20. If you performed a new installation of the Avaya Integrated Management Release 3.1 software, go to Configuring a New Installation on page 24. Issue 4 February

20 Setting Up IMD Administering an Existing Installation If you upgraded Avaya Integrated Management Release 3.0 software, perform the following steps: 1. Log into IMD. (See Procedure 1: Log into the Integrated Management Database on page 20.) 2. Configure the security defaults for IMD. (See Procedure 2: Configure the Security Defaults for IMD on page 21.) 3. Configure the SNMP settings. (See Procedure 3: Configure the SNMP Settings on page 22.) 4. If you have an Avaya S87xx voice system configured for high availability and SSH access in IMD, you should enter the SSH keys for both the active server and the standby server. (See Procedure 4: Administer SSH Keys for S87xx Voice Systems on page 23.) Procedure 1: Log into the Integrated Management Database To log into IMD: 1. Using Microsoft Internet Explorer 6.0 or later, go to the IP address or hostname of the Linux server to view the Avaya Integrated Management Launch Products page. 2. On the System Management tab, click Avaya Integrated Management Database. The Logon page appears. 3. In the User ID box, type admin. 4. In the Password box, enter your password, and click Logon. The Integrated Management Database Administrator page appears. Go to Procedure 2: Configure the Security Defaults for IMD on page Avaya Integrated Management Database Configuration

21 Administering an Existing Installation Procedure 2: Configure the Security Defaults for IMD Use this procedure to change the defaults for the following security settings: how often users can change their passwords the minimum length of passwords how often passwords expire the number failed login attempts before the user is locked out of the system To configure the defaults for the security settings: 1. Click Security in the navigation panel. The Change Security Defaults page appears. 2. From the Allowed Password Change Frequency box, select how often users can change their passwords. Choices are Daily, None, Hourly, Weekly, and Monthly. 3. In the Password Minimum Length box, enter the minimum length of passwords. 4. In the Password Aging Interval box, enter the number of days at which passwords will expire. 5. In the Invalid Password Attempts box, enter the number of failed login attempts at which the user is locked out of the system. 6. When finished, click Save. When finished, go to Procedure 3: Configure the SNMP Settings on page 22. Issue 4 February

22 Setting Up IMD Procedure 3: Configure the SNMP Settings In IMD R3.1, you can define a global default SNMP configuration for FPM. FPM uses this default configuration to access media gateways and other devices that do not have an SNMP community string directly defined. To configure the SNMP settings: 1. Click SNMP in the navigation panel. The Change SNMP Configuration page appears. 2. If you want to enable SNMPv1, click the SNMPv1 Enabled check box. 3. If you want to enable SNMPv2, click the SNMPv2 Enabled check box. 4. In the SNMP Read Community box, enter the SNMP get community string. This is used to validate SNMP get requests. 5. In the SNMP Write Community box, enter the SNMP set community string. This is used to validate SNMP set requests. 6. When finished, click Save. Note: Note: In Release 3.1, IMD supports the following new capabilities for FPM roles: - Assist - Helper - MovePN If you use FPM, go to Procedure 7: Create FPM Roles on page 36 to assign these new capabilities to FPM roles. If you have an S87xx voice system with SSH enabled, go to Procedure 4: Administer SSH Keys for S87xx Voice Systems on page Avaya Integrated Management Database Configuration

23 Administering an Existing Installation Procedure 4: Administer SSH Keys for S87xx Voice Systems If you have an Avaya S87xx voice system that is configured for high availability and SSH access in IMD, you should enter the SSH keys for both the active server and the standby server. To specify the SSH keys for both servers of an S87xx system: 1. Click Elements in the navigation panel. The Elements page appears. 2. Click Edit for the S87xx voice system. The Edit Element page appears. 3. Click MSA. 4. Make sure the Use SSH check box is enabled. 5. In the SSH Key box, enter the RSA SSH key for the server you specified in the IP Address box. (See the Avaya Communication Manager documentation for information on how to determine the RSA SSH key.) Note: Note: If you do not enter the RSA SSH key, the key will not be validated, but SSH will be used for encryption only. 6. In the Alternate SSH Key box, enter the RSA SSH key for the server you specified in the Alternate IP Address box. 7. When finished, click Update. 8. Repeat Steps 2 through 7 for any other S87xx voice systems that are configured for high availability and SSH access. Issue 4 February

24 Setting Up IMD Configuring a New Installation If you performed a new installation of the Avaya Integrated Management Release 3.1 software, you must configure IMD. To configure IMD, perform the following steps: 1. Log into IMD. (See Procedure 1: Log into the Integrated Management Database on page 24.) 2. Add locations to IMD. (See Procedure 2: Add Locations on page 25.) 3. Configure notification. (See Procedure 3: Configure Notification on page 25.) 4. Configure the security defaults for IMD. (See Procedure 4: Configure the Security Defaults for IMD on page 26.) 5. Configure the SNMP settings. (See Procedure 5: Configure the SNMP Settings on page 27.) 6. Add elements to IMD. (See Procedure 6: Add Elements on page 27.) 7. Create FPM Roles. (See Procedure 7: Create FPM Roles on page 36.) 8. Add users to IMD. (See Procedure 8: Add Users on page 38.) 9. Assign FPM roles to users. (See Procedure 9: Assign FPM Roles to Users on page 39.) Procedure 1: Log into the Integrated Management Database To log into IMD: 1. Using Microsoft Internet Explorer 6.0 or later, go to the IP address or hostname of the Linux server to view the Avaya Integrated Management Launch Products page. 2. On the System Management tab, click Avaya Integrated Management Database. The Logon page appears. The first time you log into IMD, you must change the default password. 3. Click Change Password. The Change Password page appears. 4. In the User ID box, type admin. 5. In the Current Password box, enter admin In the New Password box, enter your new password. 7. In the Re-Type New Password box, re-enter your new password. 8. Click Change Password. The message Status: Password successfully changed appears. 24 Avaya Integrated Management Database Configuration

25 Configuring a New Installation 9. Click Go to IMD Login. The Logon page appears. 10. In the User ID box, type admin. 11. In the Password box, enter your new password, and click Logon. The Integrated Management Database Administrator page appears. Go to Procedure 2: Add Locations on page 25. Procedure 2: Add Locations You should add at least one location to IMD. To add a location: 1. Click Locations in the navigation panel. The Locations page appears. 2. Click New location. The Add Location page appears. 3. Enter the information for the new location. Note: Note: It is important to enter the following information for a location: - contact - telephone number of the contact - address of the contact 4. When finished, click Add. 5. Repeat Steps 2 through 4 for each location. When finished, go to Procedure 3: Configure Notification on page 25. Procedure 3: Configure Notification You must configure the SMTP server so that MSA and FPM can send notifications. To configure the server information: 1. Click Server in the navigation panel. The Change SMTP Server Configuration page appears. 2. In the Primary SMTP Server area, enter the IP address or fully-qualified domain name (FQDN) of the primary SMTP server in the SMTP Server IP Address box. Issue 4 February

26 Setting Up IMD 3. In the SMTP Service TCP Port box, enter the TCP port number of the server. The TCP port number for SMTP is usually In the SMTP Server Login box, enter the login ID for the SMTP server. The login ID is optional. 5. In the SMTP Server Password box, enter the password for the SMTP server. The password is optional. 6. In the Re-Type SMTP Server Password box, re-enter the password for the SMTP server. 7. In the Avaya IM From box, enter the account that you want to appear in the From field in the messages sent from MSA and FPM. 8. In the Secondary SMTP Server area, enter the IP address or FQDN of the secondary server in the SMTP Server IP Address box. (The secondary SMTP server is used for redundancy and back up purposes.) 9. In the SMTP Service TCP Port box, enter the TCP port number of the server. 10. In the SMTP Server Login box, enter the login ID for the SMTP server. 11. In the SMTP Server Password box, enter the password for the SMTP server. 12. In the Re-Type SMTP Server Password box, re-enter the password for the SMTP server. 13. In the Avaya IM From box, enter the account that you want to appear in the From field in the messages sent from MSA and FPM. 14. When finished, click Save. When finished, go to Procedure 4: Configure the Security Defaults for IMD on page 26. Procedure 4: Configure the Security Defaults for IMD Use this procedure to change the defaults for the following security settings: how often users can change their passwords the minimum length of passwords how often passwords expire the number failed login attempts before the user is locked out of the system To configure the defaults for the security settings: 1. Click Security in the navigation panel. The Change Security Defaults page appears. 2. From the Allowed Password Change Frequency box, select how often users can change their passwords. Choices are Daily, None, Hourly, Weekly, and Monthly. 3. In the Password Minimum Length box, enter the minimum length of passwords. 26 Avaya Integrated Management Database Configuration

27 Configuring a New Installation 4. In the Password Aging Interval box, enter the number of days at which passwords will expire. 5. In the Invalid Password Attempts box, enter the number of failed login attempts at which the user is locked out of the system. 6. When finished, click Save. When finished, go to Procedure 5: Configure the SNMP Settings on page 27. Procedure 5: Configure the SNMP Settings In IMD R3.1, you can define a global default SNMP configuration for FPM. FPM uses this default configuration to access media gateways and other devices that do not have an SNMP community string directly defined. To configure the SNMP settings: 1. Click SNMP in the navigation panel. The Change SNMP Configuration page appears. 2. If you want to enable SNMPv1, click the SNMPv1 Enabled check box. 3. If you want to enable SNMPv2, click the SNMPv2 Enabled check box. 4. In the SNMP Read Community box, enter the SNMP get community string. This is used to validate SNMP get requests. 5. In the SNMP Write Community box, enter the SNMP set community string. This is used to validate SNMP set requests. 6. When finished, click Save. When finished, go to Procedure 6: Add Elements on page 27. Procedure 6: Add Elements You can add the following elements: voice systems messaging systems IVR systems call management systems SIP servers Proxy Agent Avaya Voice Over IP Monitoring Manager servers NMSI/NMS Issue 4 February

28 Setting Up IMD Add a Voice System To add a voice system: 1. Click Elements in the navigation panel. The Elements page appears. 2. Click New Element. The Add Element page appears. 3. In the Element Name box, enter the name of the element. 4. From the Element Type box, select Voice System. 5. In the Sold To Number box, enter the location. 6. In the Product Id box, enter the product ID for the voice system. Note: Note: The product ID is required for voice systems that are managed by a Proxy Agent application. 7. In the Note box, enter any notes you want for the voice system. This box is a note pad in which you can enter up to 255 characters. 8. From the Location box, select the location for the voice system. 9. From the Platform Type box, select the type of voice system. 10. Select the Active check box if you want the new voice system element to be activated when you are finished adding it. (This check box is enabled by default.) 11. If you want to use MSA with this voice system: a. From the MSA box, select the MSA system you want to use. b. In the Login box, enter the SAT login for the voice system. c. In the Password box, enter the password for the SAT login. d. In the Re-enter Password box, re-enter the password for the SAT login. e. In the IP Address box, enter the SAT IP address. f. If you have an Avaya S87xx voice system that is configured for high availability, enter the alternate SAT IP address in the Alternate IP Address box. g. If the system uses SSH authentication: 1. Select the Use SSH check box. 2. In the SSH Key box, enter the RSA SSH key. (See the Avaya Communication Manager documentation for information on how to determine the RSA SSH key.) If you have an Avaya S87xx voice system that is configured for high availability, enter the RSA SSH key for the server you specified in the IP Address box. 28 Avaya Integrated Management Database Configuration

29 Configuring a New Installation Note: Note: If you do not enter the RSA SSH key, the key will not be validated, but SSH will be used for encryption only. 3. If you have an Avaya S87xx voice system that is configured for high availability, in the Alternate SSH Key box, enter the RSA SSH key for the server you specified in the Alternate IP Address box. h. In the Telnet/SSH Port box, enter the SAT port number. i. If the system uses ASG: 1. In the ASG Key box, enter the ASG key. 2. In the Re-enter ASG Key box, re-enter the ASG key. j. In the Total Channels box, enter the total number of channels. k. In the Dedicated Channels box, enter the number of dedicated channels. 12. If you want to use FPM with this voice system: a. From the FPM box, select the FPM system you want to use. b. In the Login box, enter the SAT login for the voice system. c. In the Password box, enter the password for the SAT login. d. In the Re-enter Password box, re-enter the password for the SAT login. e. In the IP Address box, enter the SAT IP address. f. If you have an Avaya S87xx voice system that is configured for high availability, enter the alternate SAT IP address In the Alternate IP Address box. g. If the system uses SSH authentication: 1. Select the Use SSH check box. 2. In the SSH Key box, enter the RSA SSH key. (See the Avaya Communication Manager documentation for information on how to determine the RSA SSH key.) If you have an Avaya S87xx voice system that is configured for high availability, enter the RSA SSH key for the server you specified in the IP Address box. Note: Note: If you do not enter the RSA SSH key, the key will not be validated, but SSH will be used for encryption only. 3. If you have an Avaya S87xx voice system that is configured for high availability, in the Alternate SSH Key box, enter the RSA SSH key for the server you specified in the Alternate IP Address box. h. In the Telnet/SSH Port box, enter the SAT port number. i. If the system uses ASG: 1. In the ASG Key box, enter the ASG key. 2. In the Re-enter ASG Key box, re-enter the ASG key. Issue 4 February

30 Setting Up IMD j. In the Management URL, enter the URL of the voice system s management application. The FPM NMSI will use this URL to launch the web-based management of the element from the NMSI maps. k. From the Sub Map Type box, select the sub map. l. If you set the Sub Map Type to USA or Custom, enter the name of the sub map in the Sub Map Name box. 13. If you want to use Proxy Agent with this voice system: a. From the Proxy box, select the Proxy Agent system you want to use. b. In the Login box, enter the SAT login for the voice system. c. In the Password box, enter the password for the SAT login. d. In the Re-enter Password box, re-enter the password for the SAT login. e. In the IP Address box, enter the SAT IP address. f. In the Telnet Port box, enter the SAT port number. g. If the system uses ASG: 1. In the ASG Key box, enter the ASG key. 2. In the Re-enter ASG Key box, re-enter the ASG key. h. From the Sub Map Type box, select the sub map. i. If you set the Sub Map Type to USA or Custom, enter the name of the sub map in the Sub Map Name box. j. If you want to forward alarms, select the Forward Alarms check box. k. If you want to assign a filter set, enter the name of the filter set in the Filter Set Name box. A filter set is a collection of filter records. A filter record contains one or more of the following types of filtering criteria: Pattern matching - can include pattern files and character strings Alarm severity Day of the week Time of day The Filter Set feature allows you to create filters that Proxy Agent applies to alarms in order to block the forwarding of certain alarms to the Initialization and Administration system (INADS). See Avaya Integrated Management Release 3.1 Proxy Agent Configuration, , Issue 7 for more information about the Filter Set feature. 14. When finished, click Add. 15. Repeat Steps 2 through 14 to add another voice system. When you are finished adding elements, go to Procedure 7: Create FPM Roles on page Avaya Integrated Management Database Configuration

31 Configuring a New Installation Add a Messaging System or Other Application Server Use this procedure to add: a messaging system (such as Intuity Audix LX) a Call Management System a Conversant/Avaya IVR system a SIP server (such as Avaya SIP Enablement Services server) an Avaya Voice Over IP Monitoring Manager server To add a messaging system, Call Management System, or other element: 1. Click Elements in the navigation panel. The Elements page appears. 2. Click New Element. The Add Element page appears. 3. In the Element Name box, enter the name of the element. 4. From the Element Type box, select Other. 5. In the Sold To Number box, enter the location. 6. In the Product Id box, enter the product ID for the system. Note: Note: The product ID is required for voice systems that are managed by a Proxy Agent application. 7. In the Note box, enter any notes you want for the system. This box is a note pad in which you can enter up to 255 characters. 8. From the Location box, select the location for the system. 9. From the Platform Type box, select the type of system. 10. Select the Active check box if you want the new element to be activated when you are finished adding it. (This check box is enabled by default.) 11. If you just added an Intuity Audix 5.1 or later system, an Intuity LX system, or an MMA Messaging Server and want to use MSA with this system: a. From the MSA box, select the MSA system you want to use. b. In the Login box, enter the login for the messaging system. c. In the Password box, enter the password for the messaging system login. d. In the Re-enter Password box, re-enter the password for the messaging system login. e. In the IP Address box, enter the IP address of the messaging system. f. If the system uses SSH authentication: Issue 4 February

32 Setting Up IMD Note: Note: 1. Select the Use SSH check box. 2. In the SSH Key box, enter the RSA SSH key. (See the messaging system documentation for information on how to determine the RSA SSH key.) Note: If you do not enter the RSA SSH key, the key will not be validated, but SSH will be used for encryption only. g. In the Telnet/SSH/LDAP Port box, enter the TCP port number that should be used to connect to the messaging system. h. In the System Password box, enter the password for the system. The system password is not usually required. i. In the Re-enter System Password box, re-enter the password for the system. j. From the Queue Name box, select the voice system queue for the messaging system. MSA uses a voice system queue to control connectivity to a messaging system. While the MSA server makes a separate telnet connection to the messaging system, the voice system queue you specify here will control the starting and stopping of this connection. k. In the Total Channels box, enter the total number of channels. l. In the Dedicated Channels box, enter the number of dedicated channels. m. If you are adding a Modular Messaging system (that is, you selected Modular Messaging in the Platform Type box), enter the Base DN of the system in the Base DN box. The default setting is ou=people, dc=avaya. Change this setting only if you are sure it is a different value. 12. If you want to use FPM with this system: a. From the FPM box, select the FPM system you want to use. b. In the IP Address box, enter the IP address of the system. c. If the system uses SSH authentication: 1. Select the Use SSH check box. 2. In the SSH Key box, enter the RSA SSH key. (See the messaging system documentation for information on how to determine the RSA SSH key.) Note: If you do not enter the RSA SSH key, the key will not be validated, but SSH will be used for encryption only. d. In the Telnet/SSH Port box, enter the port number of the messaging system. e. In the Management URL, enter the URL of the element s management application. The FPM NMSI will use this URL to launch web-based management of the element from the NMSI maps. f. From the Sub Map Type box, select the sub map. g. If you set the Sub Map Type to USA or Custom, enter the name of the sub map in the Sub Map Name box. 32 Avaya Integrated Management Database Configuration

33 Configuring a New Installation 13. If you want to use Proxy Agent with this system: a. From the Proxy box, select the Proxy Agent system you want to use. b. In the IP Address box, enter the IP address of the system. c. In the Telnet Port box, enter the port number of the system. d. From the Sub Map Type box, select the sub map. e. If you set the Sub Map Type to USA or Custom, enter the name of the sub map in the Sub Map Name box. f. If you want to forward alarms, select the Forward Alarms check box. g. If you want to assign a filter set, enter the name of the filter set in the Filter Set Name box. A filter set is a collection of filter records. A filter record contains one or more of the following types of filtering criteria: Pattern matching - can include pattern files and character strings Alarm severity Day of the week Time of day The Filter Set feature allows you to create filters that Proxy Agent applies to alarms in order to block the forwarding of certain alarms to the Initialization and Administration system (INADS). 14. When finished, click Add. 15. Repeat Steps 2 through 14 to add another system. When you are finished adding elements, go to Procedure 7: Create FPM Roles on page 36. Add a Proxy Agent Configuration Use this procedure if you want to add a Proxy Agent configuration. To add a Proxy Agent configuration: 1. Click Elements in the navigation panel. The Elements page appears. 2. Click New Element. The Add Element page appears. 3. In the Element Name box, enter the name of the element. 4. From the Element Type box, select Integrated Mgmt. 5. In the Sold To Number box, enter the location. 6. In the Note box, enter any notes you want for the system. This box is a note pad in which you can enter up to 255 characters. Issue 4 February

34 Setting Up IMD 7. From the Location box, select the location for the system. 8. From the Platform Type box, select Proxy Agent. 9. Select the Active check box if you want the new element to be activated when you are finished adding it. (This check box is enabled by default.) 10. From the Proxy box, select the Proxy Agent system you want to use. 11. Select the SNMPv1 Enable check box if you want to enable SNMPv In the SNMPv1 Write box, enter Proxy Agent s set community string. The NMS uses this to validate SNMP set requests. Valid options are g3pa (default) Any name that identifies a private network! CAUTION: CAUTION: You must administer the name of the set community string to match the set community string on the NMS. The name must match on both systems, otherwise the set request will fail. 13. In the SNMPv1 Read box, enter Proxy Agent s SNMP get community string. The NMS uses this to validate SNMP get requests. Valid options are public (default) Any name that identifies a private network! CAUTION: CAUTION: You must administer the name of the get community string (public or private) to match the get community string on the NMS. The name must match on both systems, otherwise the get request will fail. 14. From the Default Map Type box, select the default submap. This is the map that you want to use to view managed nodes and their associated instances of Proxy Agent. You may want to select a default submap if you think that you will want to view most of the managed nodes in the same way. If you select a default, you will not have to specify a submap for each individual node using the MANAGED NODES screen. Any new managed nodes that you add will automatically use the default map, unless you specify otherwise (for that individual managed node) using the MANAGED NODES screen. Any change you specify in the MANAGED NODES screen overrides the default submap selection for that managed node only. Valid options are Generic (default) Select the Generic submap to view all the managed nodes and Proxy Agent computers on one submap. USA Select the USA submap to show the location of managed nodes in the U.S. The associated state submap shows managed nodes in that state. 34 Avaya Integrated Management Database Configuration

35 Configuring a New Installation Custom Select the Custom submap to organize managed nodes by categories, such as private networks, regions, functions, or international locations. Use the associated submap name (Default Map Name) to identify groups or locations within the categories, such as: - Private Network may consist of the Lab and Testing groups - Regions may consist of North, East, South, and West groups - Functions may consist of Telemarketing, Sales, and Customer Service groups - International locations may consist of Africa, Spain, and Greece groups 15. If you set the default map type to USA or Custom, enter the name of the submap in the Default Map Name box. 16. In the Network Manager 1 IP box, enter the IP address of the first NMS network manager. Valid options are: Asterisk (*) The asterisk allows access to all NMS network managers. The asterisk is not valid if you want to use Receive Trap access. IP address of the NMS in dot format (for example, ) 17. From the drop-down list box associated with the Network Manager 1 IP box, select the type of access the network manager has to Proxy Agent. Valid options are: Read/Write Allows the network manager to read and write data to the Note: Note: Fault and Performance Manager requires read/write access. Read Only Allows the network manager only to read data. The network manager cannot change MIB objects that are set with the SNMP SET command. Receive Traps Allows the network manager to receive SNMP traps from Proxy Agent. Note: Note: Fault and Performance Manager requires SNMP trap reception. 18. Repeat Steps 16 and 17 for each network manager. 19. When finished, click Add. 20. Repeat Steps 2 through 19 to add another Proxy Agent configuration. When you are finished adding elements, go to Procedure 7: Create FPM Roles on page 36. Issue 4 February

36 Setting Up IMD Add an NMSI/NMS Configuration Use this procedure if you want to add an NMSI/NMS configuration. To add an NMS/NMSI configuration: 1. Click Elements in the navigation panel. The Elements page appears. 2. Click New Element. The Add Element page appears. 3. In the Element Name box, enter the name of the element. 4. From the Element Type box, select Integrated Mgmt. 5. In the Sold To Number box, enter the location. 6. In the Note box, enter any notes you want for the system. This box is a note pad in which you can enter up to 255 characters. 7. From the Location box, select the location for the system. 8. From the Platform Type box, select NMSI/NMS. 9. Select the Active check box if you want the new element to be activated when you are finished adding it. (This check box is enabled by default.) 10. From the NMS box, select the NMS system you want to use. 11. If you are using HP OpenView, select the OpenView NMSI check box. 12. In the Map Name box, enter the name of the map you want to use. 13. From the FPM Applications box, select the appropriate FPM system. 14. When finished, click Add. 15. Repeat Steps 2 through 14 to add another NMSI/NMS configuration. When you are finished adding elements, go to Procedure 7: Create FPM Roles on page 36. Procedure 7: Create FPM Roles Use this procedure to create roles that you will assign to FPM users. You can set each role to have one or more of the following capabilities: CreateReports Allows the user to - create new reports that will be stored on the FPM server for future use - schedule reports to be run automatically in the background by the FPM server 36 Avaya Integrated Management Database Configuration