install and config cm solution

8/14/2019 Install and Config Cm Solution

1/54

Installing and Configuring AvayaAura Communication ManagerSolutionRelease 6.0

03-603559Release 6.0

June 2010Issue 1


2/54

2010 Avaya Inc.All Rights Reserved.

NoticeWhile reasonable efforts have been made to ensure that the information in thisdocument is complete and accurate at the time of printing, Avaya assumes noliability for any errors. Avaya reserves the right to make changes andcorrections to the information in this document without the obligation to notifyany person or organization of such changes.

Documentation disclaimer Avaya shall not be responsible for any modifications, additions, or deletions tothe original published version of this documentation unless such modifications,additions, or deletions were performed by Avaya.

End User agree to indemnify and hold harmless Avaya, Avaya's agents,servants and employees against all claims, lawsuits, demands and judgmentsarising out of, or in connection with, subsequent modifications, additions ordeletions to this documentation, to the extent made by End User.

Link disclaimer Avaya is not responsible for the contents or reliability of any linked Websitesreferenced within this site or documentation(s) provided by Avaya. Avaya is notresponsible for the accuracy of any information, statement or content providedon these sites and does not necessarily endorse the products, services, orinformation described or offered within them. Avaya does not guarantee thatthese links will work all the time and has no control over the availability of thelinked pages.

Warranty Avaya provides a limited warranty on this product. Refer to your salesagreement to establish the terms of the limited warranty. In addition, Avayasstandard warranty language, as well as information regarding support for thisproduct, while under warranty, is available to Avaya customers and other

parties through the Avaya Support Website: http://www.avaya.com/support .Please note that if you acquired the product from an authorized Avaya reselleroutside of the United States and Canada, the warranty is provided to you by thesaid Avaya reseller and not by Avaya.

LicensesThe software license terms available on the Avaya Website,http://support.avaya.com/licenseinfo/ are applicable to anyone who downloads,uses and/or installs Avaya software, purchased from Avaya Inc., any Avayaaffiliate, or an authorized Avaya reseller (as applicable) under a commercialagreement with Avaya or an authorized Avaya reseller. Unless otherwiseagreed to by Avaya in writing, Avaya does not extend this license if thesoftware was obtained from anyone other than Avaya, an Avaya affiliate or an

Avaya authorized reseller, and Avaya reserves the right to take legal actionagainst you and anyone else using or selling the software without a license. Byinstalling, downloading or using the software, or authorizing others to do so,you, on behalf of yourself and the entity for whom you are installing,downloading or using the software (hereinafter referred to interchangeably asyou and end user), agree to these terms and conditions and create a

binding contract between you and Avaya Inc. Or the applicable Avaya affiliate(Avaya). Avaya grants End User a license within the scope of the license typesdescribed below. The applicable number of licenses and units of capacity forwhich the license is granted will be one (1), unless a different number oflicenses or units of capacity is specified in the Documentation or othermaterials available to End User. Designated Processor means a singlestand-alone computing device. Server means a Designated Processor thathosts a software application to be accessed by multiple users. Softwaremeans the computer programs in object code, originally licensed by Avaya andultimately utilized by End User, whether as stand-alone products orpre-installed on Hardware. Hardware means the standard hardware originallysold by Avaya and ultimately utilized by End User.

License types Designated System(s) License (DS):

End User may install and use each copy of the Software on onlyone Designated Processor, unless a different number ofDesignated Processors is indicated in the Documentation or other

materials available to End User. Avaya may require the DesignatedProcessor(s) to be identified by type, serial number, feature key,location or other specific designation, or to be provided by EndUser to Avaya through electronic means established by Avayaspecifically for this purpose.

Concurrent User License (CU):End User may install and use the Software on multiple DesignatedProcessors or one or more Servers, so long as only the licensednumber of Units are accessing and using the Software at any giventime. A Unit means the unit on which Avaya, at its sole discretion,bases the pricing of its licenses and can be, without limitation, anagent, port or user, an e-mail or voice mail account in the name of aperson or corporate function (e.g., webmaster or helpdesk), or adirectory entry in the administrative database utilized by the

Software that permits one user to interface with the Software. Unitsmay be linked to a specific, identified Server.

Named User License (NU):End User may: (i) install and use the Software on a singleDesignated Processor or Server per authorized Named User(defined below); or (ii) install and use the Software on a Server solong as only authorized Named Users access and use theSoftware. Named User means a user or device that has beenexpressly authorized by Avaya to access and use the Software. At

Avaya's sole discretion, a Named User may be, without limitation,designated by name, corporate function (for example, webmasteror helpdesk), an e-mail or voice mail account in the name of aperson or corporate function, or a directory entry in theadministrative database utilized by the Software that permits one

user to interface with the Software. Shrinkwrap License (SR):Customer may install and use the Software in accordance with theterms and conditions of the applicable license agreements, such asshrinkwrap or clickthrough license accompanying or applicableto the Software (Shrinkwrap License). (See Third-partyComponents for more information).

CopyrightExcept where expressly stated otherwise, no use should be made of materialson this site, the Documentation(s) and Product(s) provided by Avaya. Allcontent on this site, the documentation(s) and the product(s) provided by

Avaya including the selection, arrangement and design of the content is ownedeither by Avaya or its licensors and is protected by copyright and otherintellectual property laws including the sui generis rights relating to theprotection of databases. You may not modify, copy, reproduce, r epublish,upload, post, transmit or distribute in any way any content, in whole or in part,including any code and software. Unauthorized reproduction, transmission,dissemination, storage, and or use without the express written consent of

Avaya can be a criminal, as well as a civil, offense under the applicable law.Third Party ComponentsCertain software programs or portions thereof included in t he Product maycontain software distributed under third party agreements (Third PartyComponents), which may contain terms that expand or limit rights to usecertain portions of the Product (Third Party Terms). Information regardingdistributed Linux OS source code (for those Products that have distributed theLinux OS source code), and identifying the copyright holders of the Third PartyComponents and the Third Party Terms that apply to them is available on the

Avaya Support Website: http://support.avaya.com/Copyright .

Preventing toll fraudToll fraud is the unauthorized use of your telecommunications system by anunauthorized party (for example, a person who is not a corporate employee,agent, subcontractor, or is not working on your company's behalf). Be awarethat there can be a risk of toll fraud associated with your system and that, if tollfraud occurs, it can result in substantial additional charges for yourtelecommunications services.

Avaya fraud interventionIf you suspect that you are being victimized by toll fr aud and you need technicalassistance or support, call Technical Service Center Toll Fraud InterventionHotline at +1-800-643-2353 for the United States and Canada. For additionalsupport telephone numbers, see the Avaya Support Website:http://www.support.avaya.com/.Suspected security vulnerabilities with Avaya products should be reported to

Avaya by sending mail to: [email protected] .

TrademarksAvaya and Avaya Aura are trademarks of Avaya Inc .The trademarks, logos and service marks (Marks) displayed in this site, thedocumentation(s) and product(s) provided by Avaya are the registered orunregistered Marks of Avaya, its affiliates, or other third parties. Users are notpermitted to use such Marks without prior written consent from Avaya or suchthird party which may own the Mark. Nothing contained in this site, thedocumentation(s) and product(s) should be construed as granting, byimplication, estoppel, or otherwise, any license or right in and to the Markswithout the express written permission of Avaya or the applicable third party.

All non-Avaya trademarks are the property of their respective owners.

Downloading documentsFor the most current versions of documentation, see the Avaya SupportWebsite: http://www.avaya.com/support.

Contact Avaya Support Avaya provides a telephone number for you to use to report problems or to askquestions about your product. The support telephone number is1-800-242-2121 in the United States. For additional support telephonenumbers, see the Avaya Website: http://www.avaya.com/support.
http://www.avaya.com/supporthttp://support.avaya.com/licenseinfo/http://support.avaya.com/Copyrighthttp://www.support.avaya.com/mailto:[email protected]://www.avaya.com/supporthttp://www.avaya.com/support/mailto:[email protected]://www.support.avaya.com/http://support.avaya.com/Copyrighthttp://support.avaya.com/licenseinfo/http://www.avaya.com/supporthttp://www.avaya.com/support/http://www.avaya.com/support


3/54

Issue 1 June 2010 3

Chapter 1: Purpose of this document . . . . . . . . . . . . . . . . . . . 5An overview of setting Communication Manager . . . . . . . . . . . . . . . . . . 5

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 2: Installing UPS and Ethernet switch . . . . . . . . . . . . . . 7Installing the SNMP Module in the UPS . . . . . . . . . . . . . . . . . . . . . . . 7UPS and Ethernet Switch Mounting Brackets . . . . . . . . . . . . . . . . . . . . 8

Chapter 3: SNMP configuration . . . . . . . . . . . . . . . . . . . . . . 9Configuring the SNMP modules in the UPS . . . . . . . . . . . . . . . . . . . . . 9

Default IP addresses for the UPS . . . . . . . . . . . . . . . . . . . . . . . . 10Prerequisites for configuring the SNMP module . . . . . . . . . . . . . . . . 10Administering the SNMP module . . . . . . . . . . . . . . . . . . . . . . . . 11Setting selected traps (alarming) . . . . . . . . . . . . . . . . . . . . . . . . 12

Configuring the SNMP subagent in the Avaya Ethernet switch (if used) . . . . . 12Default IP addresses for the Ethernet switch . . . . . . . . . . . . . . . . . . 13Preparing to configure the Ethernet switch . . . . . . . . . . . . . . . . . . . 13Configuring the Ethernet switch . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 4: IP interface configuration . . . . . . . . . . . . . . . . . . . 17Connecting to the IPSIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

IPSI address configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Programming the IPSI for static addressing . . . . . . . . . . . . . . . . . 17

Setting the VLAN and diffserv parameters . . . . . . . . . . . . . . . . . . . . . 20

Chapter 5: IP interface translations . . . . . . . . . . . . . . . . . . . 23Inputting initial system translations . . . . . . . . . . . . . . . . . . . . . . . . . 23

Adding media gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Enabling the IPSI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Adding the IPSI to the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Enabling IPSI duplication (duplicated control network only) . . . . . . . . . . . . 26

Setting the alarm activation level . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Saving translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Verifying connectivity to the server . . . . . . . . . . . . . . . . . . . . . . . . . 27

Verifying that the IPSIs are translated . . . . . . . . . . . . . . . . . . . . . . . . 27

Upgrading the IPSI firmware version (if necessary) . . . . . . . . . . . . . . . . 28

Enabling control of the IPSIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Contents


4/54


5/54

Issue 1 June 2010 5

Chapter 1: Purpose of this document

The purpose of this document is to provide the information, references, and procedures to the Avaya Partners and customer administrators, who will install Communication Manager andperform the initial administration to set up an enterprise telephony application.

An overview of setting Communication Manager The following tasks together help in setting Communication Manager for an enterprisetelephony application:

Task Reference

Installing UPS in rack if purchased from Avaya This document

Installing Ethernet switch in rack if purchasedfrom Avaya

This document

Configuring SNMP on UPS and Ethernet switch This document

Installing S8800 in rack Installing the Avaya S8800 Server for Avaya Aura Communication Manager,03-603444

Installing and configuring CommunicationManager

Installing and configuring CommunicationManager, 03-603558

Installing and configuring port networks, if beingused

Installing the Avaya G650 Media Gateway,03-300685

Installing and administering H.248 MediaGateways, if being used

Quick Start for Hardware Installation: Avaya G430 Media Gateway

Quick Start for Hardware Installation: Avaya G450 Media Gateway

Administering IPSIs This document

Verifying installation This documentCompleting postinstallation tasks This document


6/54

Chapter 1: Purpose of this document

6 Installing and Configuring Avaya Aura Communication Manager Solution

Note:Note: This document covers the minimum Communication Manager administration

tasks. For the complete information on Communication Manager administration,see Administering Avaya Aura Communication Manager 03-300509.

Prerequisites

Before using this document, make sure that the following prerequisites are fulfilled:

1. Installation and administration documents of the servers, gateways, and CommunicationManager are available for reference

2. Required data such as IP addresses to allocate to the servers, gateways are ready on theworksheets

3. Necessary enterprise and purchase information is registered with Avaya at least twoweeks in advance

4. Avaya has sent license and system ID information that is necessary for CommunicationManager administration


7/54

Issue 1 June 2010 7

Chapter 2: Installing UPS and Ethernetswitch

Installing the SNMP Module in the UPS


8/54

Chapter 2: Installing UPS and Ethernet switch


UPS and Ethernet Switch Mounting Brackets


9/54

Issue 1 June 2010 9

Chapter 3: SNMP configuration

After you install and connect the control network equipment, you must configure the SNMPmodules in each Avaya-supplied UPS to send alarms or traps to the servers. This processrequires that you also configure the SNMP subagent in the Avaya-supplied Ethernet switch.

! Important:Important: Use the procedures in this section to configure Avaya-supplied equipment only.

Configuring the SNMP modules in the UPS

! Important:Important: These procedures apply only to a new, Avaya-supplied uninterruptible power

supply (UPS) with a Simple Network Management Protocol (SNMP) module. Donot use these procedures to set traps on a UPS that Avaya does not supply. Fornon Avaya supplied UPS hardware, see manuals supplied with the UPS forinstructions on how to configure those UPS devices.

You must configure the SNMP module in the UPS to report alarms to the server when hardwareproblems occur. The module reports an alarm if commercial power is lost or battery resourcesare depleted.

For the SNMP module to properly report alarms, you must configure a unique IP address for theUPS on both the SNMP module and the server. This IP address can be a customer-providedaddress or the Avaya-provided default address. At a minimum, you must configure the followingitems:

The IP address

The subnet mask

The gateway IP address

The trap receiver IP address

The community string (get, set, trap)

The brand, the model, or the firmware load of the SNMP module that Avaya supplies canchange without notice because a third-party manufactures the SNMP module. For this reason,this document does not provide specific instructions on how to connect to and configure theSNMP module. For more information, see the documentation that comes with the SNMPmodule. For the default password and the configuration commands, see the local configurationsection of that user guide.


10/54



Default IP addresses for the UPS

The following table shows the default IP addresses for the UPS.

For how to administer the SNMP module in the UPS, see Administering the SNMP module onpage 11 .

Prerequisites for configuring the SNMP module

Before you configure the SNMP module, you must complete the following prerequisites:

Your Services laptop computer is plugged into the correct administration port on the SNMPmodule on the UPS.

The UPS is plugged into a nonswitched electrical outlet.

The communication protocol on your computer has the following port settings so that youcan use your terminal emulation program:- 9600 baud- No parity- 8 data bits- 1 stop bit- No flow control

Note:Note: Avaya Terminal Emulation and HyperTerminal are supported terminal emulation

applications.

If a Network Management System (NMS) is used to monitor the UPS, you must coordinatethe assignment of community names with the network administrator. If an NMS is notused, you can set the community names to any unique string values.

IP address for the UPS 198.152.254.239Gateway address for the UPS 198.152.254.201

IP address for thetrap receiver (server)

Customer provided


11/54

Configuring the SNMP modules in the UPS

Issue 1 June 2010 11

! SECURITY ALERT:!SECURITYALERT: The Get and Set community name strings are initially configured with the default

values of Public and Private, respectively. These community name stringsfunction as passwords for their respective SNMP operation. Avaya recommendsthat you change these community name strings to something other than the

default values. If you leave the defaults in place, a serious security issue canresult.

For information about which traps to set, see Setting selected traps (alarming) on page 12 .

If the control network is nondedicated, ensure that the 162/udp port for input to server isenabled and the default is disabled. If you do not enable the 162/udp port and disable thedefault, the server cannot receive the traps from either UPS.

Administering the SNMP module

Note:Note: Use the default IP addresses.

1. Connect the RS-232 serial port of your Services laptop computer to the DB-9 connector onthe back of the SNMP module for UPS1. Use the DB-9 to DB-9 serial cable that is suppliedwith the SNMP module.

2. Open a VT-100 terminal emulation session on your computer.

3. Set the IP address for the UPS.

4. Set the subnet mask for the UPS.

5. Set the gateway address for the UPS.

6. Set the IP address of the trap receiver for the UPS.7. Set the SNMP community name string for Get, Set, and Trap. For information on which

traps to set, see Setting selected traps (alarming) on page 12 .

8. When you finish, disconnect your computer from the UPS.

9. Connect one end of a CAT5 straight-through cable to the RJ45 connector on the UPSSNMP module and the other end of the cable to the next available port on the Ethernetswitch for the network.

For a connectivity guide, see the quick start for hardware installation documentcorresponding to your server.

After you configure the SNMP module in the UPS, you must configure the SNMP subagent onthe Avaya Ethernet switch.


12/54


13/54

Configuring the SNMP subagent in the Avaya Ethernet switch (if used)


Default IP addresses for the Ethernet switch

The following table shows the default values for the Ethernet switch.

For how to administer the SNMP subagent in the Ethernet switch, see Configuring the Ethernetswitch on page 14 .

Preparing to configure the Ethernet switch

Before you configure the Ethernet switch, you must complete the following prerequisites:

The Ethernet switch power cord is connected to the back of the switch and to the back of aUPS.

The communication protocol on your computer has the following port settings so that youcan use your terminal emulation program:- 9600 baud- No parity- 8 data bits- 1 stop bit- No flow control

Note:Note: Avaya Terminal Emulation and HyperTerminal are supported terminal emulation

applications.

If a Network Management System (NMS) is to monitor the Ethernet switch, youcoordinated the assignment of community names with the network administrator. If anNMS is not used, you set the community names to unique string values.

Parameter Single controlnetwork

Duplicated controlnetwork

IP address for the Ethernet switch 198.152.254.240 198.152.255.240

IP address for thetrap receiver (server)

Customer provided Customer provided


14/54


15/54

Configuring the SNMP subagent in the Avaya Ethernet switch (if used)


10. If the port networks are IP-PNC, ensure that all appropriate ports on the Ethernet switchare locked to 100 speed and full duplex.

11. When you finish, disconnect your computer from the Ethernet switch.

12. If two Ethernet switches are present for the network, repeat Steps 1 through 10 for thesecond switch.


16/54




17/54


Chapter 4: IP interface configuration

Once you connect the IPSIs to the control network, the IPSIs might generate an alarm if thefirmware is not the most current. The alarm stops automatically once you upgrade the IPSIfirmware. This chapter covers information on IP interface configuration.

Connecting to the IPSIsConnect CAT5 cables from the IPSI circuit packs to the customer LAN.

IPSI address configurationThe IPSI circuit pack receives an IP address statically with static IP addressing.

Refer to Programming the IPSI for static addressing on page 17

Programming the IPSI for static addressing

! Important:Important: If an IPSI is in a port network that is backed up with the Survivable Core Server

option you must use static addressing for the Survivable Core Server to provideservice to the port network.

You administer the static IP address for the circuit pack directly through the Ethernet portconnection on the faceplate (top port). See Figure 1 .


18/54



Figure 1: Connecting the laptop directly to the IPSI

Note:Note: Ensure that you have the password before proceeding.

Depending on the operating system on the Services laptop computer, you might need to clearthe Address Resolution Protocol (ARP) cache before entering a new IP address. If you enter anIP address and your computer cannot connect, try clearing the cache.

1. On your laptop computer, click Start > Run to open the Run dialog box.

2. Type command and click OK to open a MS-DOS Command Line window.

3. Clear the Address Resolution Protocol (ARP) cache in the laptop.

4. To log into the IPSI, use SSH and the IP address 192.11.13.6 .

Note:Note: While connected to the IPSI, type help or ? to obtain online help. Most

commands have two or three letter abbreviations.

Figure notes:

1. Services laptop computer

2. PCMCIA Network Interface Card (NIC)

3. NIC adapter cable (if necessary)

4. CAT5 crossover cable to IPSI

cadlipsi KLC 031502

1

2

CLK

SERVICE

NETWORK

3

4


19/54

IPSI address configuration


5. Type ipsilogin and press Enter .

Note:Note: The craft login used on the IPSI has a different password from the craft login used

on the servers.

6. Log in as craft .

Prompt = [IPADMIN]:

7. Type show control interface and press Enter and then type show port 1 andpress Enter to see the current control interface settings.

8. To set the control interface, type set control interface ipaddr netmask andpress Enter , where ipaddr is the customer-provided IP address and netmask is thecustomer provided subnet mask.

9. Type quit and press Enter to save the changes and exit the IPSI session.

10. Log back in to the IPSI using SSH.

11. Type show control interface and press Enter .The system displays IP address, subnet mask, and default gateway information.Verify that the proper information was entered.

12. If a default gateway is used, enter the gateway IP address withset control gateway gatewayaddr , where gatewayaddr is the customer-provided

IP address for their gateway.13. Type quit and press Enter to save the changes and exit the IPSI session.

14. Log back in to the IPSI using SSH.

15. Use show control interface to verify the administration.


20/54



16. Type exit and press Enter .

Setting the VLAN and diffserv parameters1. Connect to the IPSI and log in as craft .

2. To display the quality of service values, type show qos and press Enter .

3. Use the set commands in the list below to set the VLAN, diffserv, and port parameters. Ifthe customer does not specify different values, use these recommended values.

Note:Note: Use Help to obtain syntax guidelines for these commands.

! Important:Important: The settings for these parameters on the IPSIs must be consistent with the

settings on the servers and other network devices such as Ethernet switches.

set vlan priority 6

set diffserv 46

set vlan tag on

set port negotiation 1 disable

set port duplex 1 full

set port speed 1 100

4. Type show qos and press Enter to check the administered values.

5. Type reset and press Enter to capture the updated parameter values.

The reset terminates the administration session and automatically logs you out.

6. Log in again and use the show qos command to ensure that the parameter settings arecorrect.

7. Disconnect the laptop from the IPSIfaceplate.

8. Check the LED on the IPSIfaceplate. Verify that the display shows the letters I and P and afilled-in V at the bottom. (See Figure 2 ).


21/54

Setting the VLAN and diffserv parameters


Figure 2: IPSI LED display for static address

Note:Note: Clear the ARP cache on the laptop before connecting to another IPSI. If you do

not clear the cache, the laptop appears to stop and does not connect to the nextIPSI.

9. Repeat this procedure for each IPSI circuit pack.

Figure notes:

1. IPSI has a static IP address 2. IPSI has connectivity and an IP address

ledlip1 KLC 030502

1

2

CLK

SERVICE

NETWORK


22/54




23/54


Chapter 5: IP interface translations

To administer IPSI circuit packs, use a terminal emulation program to issue CommunicationManager SAT commands.

For Communication Manager terminal emulation, use Avaya Native Configuration Manager.

You also can use Avaya Site Administration to issue SAT commands. To administer some of thefeatures in the latest release of Communication Manager, you must use the latest version of

Avaya Site Administration.

Perform these tasks to administer IPSI circuit packs:

Inputting initial system translations on page 23 Adding media gateways on page 24 Enabling the IPSI on page 25 Adding the IPSI to the system on page 26 Enabling IPSI duplication (duplicated control network only) on page 26 Setting the alarm activation level on page 27 Saving translations on page 27 Verifying connectivity to the server on page 27 Verifying that the IPSIs are translated on page 27 Upgrading the IPSI firmware version (if necessary) on page 28 Enabling control of the IPSIs on page 28

Inputting initial system translations1. Open a SAT session.

2. Enter translations:

If the system translations were prepared offsite, install the prepared translations and resetCommunication Manager using the SAT command reset system 4 .

If translations have not been prepared offsite, enter minimal translations to verifyconnectivity to the port networks.

3. After you enter the translations, type save translation and press Enter to save thetranslations to the hard disk drive.


24/54



4. Type reset system 4 and press Enter to have the software read the copiedtranslations.

Adding media gatewaysNote:

Note: If system translations have been loaded on the server, media gateways do notneed to be added to administer the IPSI.

1. Type add cabinet n and press Enter , where n is the cabinet number, for each stack ofmedia gateways that is controlled by one TN2312BP IPSI circuit pack.

A cabinet is defined as a group of up to five G650 Media Gateways that are mounted in arack and TDM-connected.

2. Fill in the carrier location letter and the carrier type for each media gateway in the cabinet.

add cabinet 1 Page 1 of 1CABINET

CABINET DESCRIPTION Cabinet: 30 Cabinet Layout: G650-rack-mount-stack Cabinet Type: expansion-portnetwork

Location: 1 IP Network Region:1Rack: Room: Floor: Building:

CARRIER DESCRIPTION Carrier Carrier Type Number

E not-used D not-used C not-used B not-used

A G650-port


25/54

Enabling the IPSI


Enabling the IPSI1. Type change system-parameters ipserver-interface and press Enter .

2. On the IP Server Interface System Parameters screen, verify that the primary controlsubnetwork address is correct.

The control subnetwork addresses typically match the most significant three octets of theIP addresses of the server for the media gateway. The most significant three octets are thefirst three groups of digits in the IP address. Use the Network Configuration option on theSystem Management Interface to see the IP address of the server.

3. If the information in the Control Subnet Address field is incorrect, use the SystemManagement Interface to change the server configuration to match the Server IP addressin the Network Configuration option. Then return to this procedure.

4. Set the Switch Identifier field to the switch ID letter. Acceptable switch ID letters are Athrough J. A is the default setting.

5. Set the IPSI Control of Port Networks field to enabled .

6. Press Enter to save the changes.

change system-parameters ipserver-interface Page 1 of 1 IP SERVER INTERFACE (IPSI) SYSTEM PARAMETERS

SERVER INFORMATION

Primary Control Subnet Address: Secondary Control Subnet Address:

OPTIONS

Switch Identifier: init@svs8730-1-srv1> IPSI Control of Port Networks: enabled A-side IPSI Preference: enabled IPSI Socket Sanity Timeout: 3

QoS PARAMETERS 802.1p: 6 DiffServ: 46


26/54



Adding the IPSI to the systemUse the IP Server Interface Administration - Port Network SAT screen to add an IPSI.

1. Type add ipserver-interface PNnumber and press Enter .

2. In the Host field, enter the IP address for the IPSI that is listed in the Location field.

3. Set the IP Control field to y.

4. Verify that all the other fields are populated and submit the screen to save the changes.

5. Repeat this procedure for each port network.

Enabling IPSI duplication (duplicated control networkonly)

Port networks with duplicated IPSIs have both primary and secondary IPSI circuit packs. If youdisable IPSI duplication, all primary IPSI circuit packs must be active.

Use the System-Parameters Duplication SAT screen to enable IPSI duplication.

1. Enter change system-parameters duplication .

2. Enter y in the Enable Operation of IPSI Duplication field.

3. Submit the screen to save the changes.

add ipserver-interface 8 IP SERVER INTERFACE (IPSI) ADMINISTRATION - PORT NETWORK 3

IP Control? y Ignore Connectivity in Server Arbitration? nEncryption? n Administer secondary ip server interface board? n

PRIMARY IPSI QoS AND ETHERNET SETTINGSLocation: 3A01 Use System Level Parameter Values? y

Subnet Mask: /24 802.1p: 6IP Address: DiffServ: 46

Gateway: Auto? y


27/54

Setting the alarm activation level


Setting the alarm activation level1. At the SAT, type change system-parameters maintenance and press Enter .

2. In the CPE Alarm Activation Level field, enter none , warning , minor , or major ,according to the customer request.

3. Press Enter to save the changes

Saving translationsTo save the translations to the hard disk drive, at the SAT, enter save translation .

Verifying connectivity to the server1. Open the System Management Interface and log on as craft .

2. From the Administration menu, click Server (Maintenance) .

3. On the left navigation menu, click Ping .

4. Click one of the following options for the Endpoints to Ping field:

Host Name Or IP address : This will ping a computer of the specified IP address orthe host name.

IPSI's with cab number (1~99) : This will ping the specified IPSI.

Other server via duplication link : This will ping the other server.

5. Click Do not look up symbolic names for host addresses , if required.

6. Click Bypass normal routing tables and send directly to a host , if required.

7. Click Execute Ping .

8. Verify that all endpoints respond correctly.

Verifying that the IPSIs are translated1. Use SSH to open a SAT session on the server.


28/54



2. Enter list ipserver-interface .

3. Verify that all ISPI circuit packs are translated.

Upgrading the IPSI firmware version (if necessary)You might need to upgrade the firmware on some or all the IPSIs. All IPSIs must have the samefirmware load.

1. Log on to the System Management Interface and click Administration > Server(Maintenance) > IPSI Version .

2. Select Query All and click View .

3. Verify the firmware release for each IPSI.

4. If an upgrade is required, follow the steps given below:

Log in to the Avaya support Web site at http://support.avaya.com .

Click Downloads .

In the pop-up window, type Communication Manager .

In the list of downloads, click the link associated with the desired firmware name.

Click the Downloads tab.

Click the desired firmware link.

Enabling control of the IPSIs1. Ensure that the IPSIs have the same, current firmware.

2. On the SAT, type change system-parameters ipserver-interface and pressEnter .

3. Ensure the IPSI Control of Port Networks: field is set to enabled .

4. Press Enter to save the changes.


29/54


Chapter 6: Server Roles

Communication Manager templates and their roles A server on which a Communication Manager template is installed can be configured to one ofthe permitted roles for the template. The following table summarizes the CommunicationManager templates and their permitted roles:

Verifying that the main server identifies thenew survivable remote server

The prerequisite to this task is the configuration of the survivable remote server. See Installingand Configuring Avaya Aura Communication Manager , 03-603558 for information onconfiguring a server role.

1. Wait several minutes after you reset the survivable remote server. On the main server,enter list survivable-processor to verify that the survivable remote serverregisters, and that translations are updated.

Communication Manager template Permitted server role

Duplex Main/Survivable Core (CM Duplex) MAIN or Survivable Core Server

Simplex Main/Survivable Core (CM Simplex) MAIN or Survivable Core Server

Simplex Survivable Remote (CM_SurvRemote) Survivable Remote Server

Embedded Survivable Remote (CM_onlyEmbed) MAIN on Embedded Server

Embedded Survivable Core (CM_SurvRemoteEmbed) Survivable Remote Server onEmbedded Server


30/54

Chapter 6: Server Roles


2. If the survivable remote server is registered, the Service State? field shows in-service and the Translations Updated field shows the time and the date of the update.

Readministering media gateways

Note:Note: You will not need to perform this task if you have installed a new media gateway

and Communication Manager servers as part of first-time installation.

If you are including a survivable remote as an alternate controller, you must change thecontroller list for each Avaya H.248 Media Gateway. This change enables the media gateway toseek service from the survivable remote server if the connection to the main server fails.

For procedures on how to change the controller list of the media gateway, see one of thefollowing documents:

Installing and Upgrading the Avaya G430 Media Gateway , 03-603233

Installing and Upgrading the Avaya G450 Media Gateway , 03-602054

list survivable-processor Page 1 of xxSURVIVABLE PROCESSORS

Record Name Type Reg Act Transactions NetNumber IP Address Updated Rgn

1 ESSCid020Sid097 ESS S n 1172.21.22.39

No V6 Entry2 ESSCid030Sid096 ESS S n 1

172.21.22.40No V6 Entry

3 ESSCid040Sid095 ESS S n 1172.21.22.41

No V6 Entry4 ess1pe ESS D n 26

172.21.22.36No V6 Entry


31/54


Chapter 7: Postinstallation administration

This chapter has sections that will help you to accomplish postinstallation administration andverification tasks.

Verifying translations1. Open a SAT session on the server.

2. To view all the administered circuit packs in the system, type list configuration alland press Enter .

3. To verify the location of the IPSI circuit packs , type list ipserver-interface andpress Enter .

For more information, see your planning documents and check the administration status on thefollowing items:

list station

list trunk-group

list hunt-group

Setting rules for daylight savings timeUse the System Platform Web Console to set the date, time, and time zone on the server. Youmust use SAT commands to set the rules for daylight savings time.

1. Enter change daylight-savings-rules .

2. In the Change Day , Month , Date , Time , and Increment columns, type the appropriatestart and stop information for each rule. For example, 1:00 in the Increment field means tomove the clock forward or back by one hour at the transition point.

You can set up to 15 customized daylight savings time rules. If you have media gatewaysin several different time zones, you can set up rules for these media gateways on aper-location basis. A daylight savings time rule specifies the exact time when you want totransition to and from daylight savings time. The rule also specifies the increment at whichto make the transitions.


32/54



Note:Note: The default daylight savings rule is 0, which means that no daylight savings

transition occurs. You can change any rule except rule 0. You cannot delete adaylight savings rule if the rule is in use on either the Locations screen or theDate and Time screens.

3. When you finish, press Enter to save the changes.

Setting locations (if necessary) After you set the rules for daylight savings time, you must set the locations for all port networks.Port networks can be in different time zones. Use SAT commands to set the locations for theport networks.

1. Enter change locations .

2. In the ARS Prefix 1 Required for 10-Digit NANP Calls? field, type y.The system displays the location information.

3. Click Submit to save the changes.

change locations Page 1 of 5 LOCATIONS

ARS Prefix 1 Required For 10-Digit NANP Calls? y

Number Name Timezone Daylight-Savings Number Plan Offset Rule Area Code 1 Main + 00:00 0 2 CA - 02:00 0 3 : 4 : 5 : 6 :

7 : 8 : 9 : 10 : 11 :


33/54

Verifying the date and the time (main server only)


Note:Note: The location of a port network is defined on the Cabinet SAT screen ( change

cabinet X ). The location of a network region is defined on theip-network-region SAT screen ( change ip-network-region X ).Thelocation of an H.248 media gateway is defined on the change media-gateway SAT screen ( change media-gateway X ). The Location field in theip-network-region SAT screen is part of the association to thedaylight-savings-rule by which a IP phone behaves.

Verifying the date and the time (main server only)Use SAT commands to verify the date and time.

1.Enter display time .

2. Verify that the date and the time of day are correct.

If the date and the time of day are correct, go to 5.

If the date and time of day are not correct, proceed to step 3.

3. Verify connectivity to any administered Network Time Server:

a. On the System Platform Web Console, click Server Management > Date / TimeConfiguration .

b. In the Time Server field, enter the IP address of the Network Time Server.

c. Click Ping . If the Network Time Server is not administered:

1. On the left navigation menu, click Server Date/Time .

2. Set the correct date and the correct time. Verify that the time zone is correct.

display time Page 1 of 1 DATE AND TIME

DATE

Day of the Week: Friday Month: June Day of the Month: 9 Year: 2006

TIME

Hour: 14 Minute: 19 Second: 36 Type: Standard

Daylight Savings Rule: 0

WARNING: Changing the date or time may impact BCMS, CDR, SCHEDULED
http://-/?-http://-/?-


34/54



Note:Note: This operation results in rebooting the server and will disrupt the Communication

Manager service.

4. Repeat this procedure, beginning with step 1.

5. Verify that the Daylight Savings Rule field is correct.

0 if this server is in a location that does not use daylight savings time

1-15 use an administered rule. The rule is administered using the SAT commanddaylight-savings-rules. For more information on the daylight-savings-rules, see Settingrules for daylight savings time on page 31 .

Note:Note: The daylight savings rule setting on this screen is the rule that is used by the

Communication Manager software. Additional daylight savings rules can beimplemented for the specific locations of hardware supported by theCommunication Manager software. For more information, see Setting locations (ifnecessary) on page 32 .

Clearing and resolving alarms1. Log on to the System Management Interface and click Administration > Server

(Maintenance) > Current Alarms .

For duplicated servers, you can resolve alarms on the active server only.

2. Select the server alarms to clear and click Clear .

Note:Note: Use SAT commands or other standard troubleshooting procedures, to resolve

any major alarms.

Backing up configuration informationUse this procedure to back up configuration information for System Platform and the solutiontemplate (all virtual machines) using System Platform Web Console.

1. Click Server Management > Backup/Restore .2. Click Backup .


35/54

Backing up configuration information


! Important:Important: The backup file size can reach 3 GB. Ensure that you have that much free space

at the location where you are storing the backup archive.

3. Select where to store or send the backup files:

Local : Stores the backup archive file on System Platform in the /vspdata/backup/archive directory.

SFTP : Stores the backup archive file on the designated SFTP host server as well ason the System Platform server.

Email : Sends the backup archive file to the e-mail address that you specify as well asstores the file on the System Platform server.

Note:Note: Avaya does not recommend that you use the Email option due to the large size of

backup files. The backup file size can reach 3 GB.

4. Enter other information as appropriate.

5. Click Backup Now .


36/54




37/54


Chapter 8: Installation verification

This chapter provides the following information about how to verify the server installation andconfiguration:

Testing the IPSI circuit packs

Testing the license file

Checking LED status indicators- Servers- Avaya Ethernet switches- Uninterruptible power supplies (UPSs)- Circuit packs

Testing the IPSI circuit packThe following steps test the clock and packet interface components within the TN2312BP IPSIcircuit pack.

1. In a SAT command line, type test ipserver-interface UUC and press Enter ,where UUC is the cabinet and the carrier in which the circuit pack is located.

2. Verify that the Test Results screen shows PASS in the Results column.

Testing the license file

! Important:Important: Wait at least 30 minutes after you install the Communication Manager license

before you run this test.

1. On a SAT command line, type test license and press Enter .

2. Verify that the Test Results screen shows PASS in the Results column.


38/54



Before leaving the site Provide the default LAN security settings to the customer.

LEDs

S8800 LEDs

Figure 3: LEDs on the front panel of the S8800 Server

The functions of the front-panel LEDs are as follows:

Table 1: S8800 front-panel LEDs

LED Description

1 Hard disk drive activity LED (green)

2 Hard disk drive status LED (amber)

3 Power on LED


39/54

LEDs


Figure 4: LEDs on the back panel of the S8800 Server

The functions of the back-panel LEDs are as follows:

4 Service Locator LEDThe LED has the following three states: Off : The server is either a simplex server or the active

server in a duplex pair and there are no gatewaysregistered to it and the server is not the master of any portnetworks.

Flashing : The server is the standby server of the pair. Steady : The server is the active server in a duplex pair

and one or more gateways are registered to it or theserver is the master of one or more port networks. It isalso possible that both gateways are registered and theserver is the master of port networks.

5 DVD drive activity LED

Table 2: S8800 back-panel LEDs

LED Description

1 Ethernet activity LED

2 Ethernet link LED

Table 1: S8800 front-panel LEDs

LED Description


40/54



Additional server LED informationFor more information on server LEDs, seeInstalling the Avaya S8800 Server for Avaya Aura Communication Manager , 03-603444.

3 AC power LED (green)

4 DC power LED (green)

5 Power supply error LED (amber)

6 System error LED (amber)

7 System locator LED (blue)

8 Power LED (green)

Table 2: S8800 back-panel LEDs

LED Description


41/54

Avaya C360 Ethernet switch LEDs


Avaya C360 Ethernet switch LEDsThe C360 series converged, stackable, Ethernet switches include:

C363T: 24-port

C363T-PWR: 24-port power over Ethernet (PoE)

C364T: 48-port

C364T-PWR: 48-port PoE

The front panel of the C360-Series switches has:

One port LED that is associated with each port

Three system status LEDs

Seven port function LEDs

The C363T-PWR and the C364T-PWR switches have an additional PoE LED. The port functionLEDs are selectable with a set of two left/right buttons. The port LEDs display the status of theselected function for each port.

For more information about the on/off and blinking states of the LEDs, see the documentationfor the Ethernet switch.

System and port function LEDs on C360 Avaya Ethernet switches

LED Name Description

System LEDs

PWR Power status

SYS System status

ROUT Routing mode

Port Function LEDs

LNK Link status

COL Collision status

Tx Transmit to line

Rx Receive from line

FDX Full duplex mode

Hspd High-speed modeLAG Link aggregation group for trunking

PoE (PWR versions only) Power over Ethernet status


42/54



UPS LEDsThe UPS LEDs flash briefly after the UPS is plugged in. The normal mode LED flashes after aself-test to indicate that the UPS is in standby mode.

For more information, see the UPS user guide for the Powerware UPS.

Figure 5: LEDs on the Powerware 9125 UPS

Figure notes:1. Normal mode indicator 2. Battery mode indicator 3. Bypass mode indicator 4. Test/Alarm reset button

5. Off button6. On button7. Bar graph indicators8. Alarm indicators

12

3

4 5 6

7

8

ledlups KLC 030102


43/54

TN2312BP IPSI LEDs


TN2312BP IPSI LEDsTN2312BP IP Server Interface (IPSI) circuit pack LEDs include:

Standard LEDs and connector slots

A programmable LED display, which indicates:- The type of IPSI IP address. For a static address, the display shows I P .

(Figure 7: IPSI LED display for a static IP address on page 45 )

For more information on troubleshooting the configuration of the server hardware, see Appendix A: Installation troubleshooting on page 47 .


44/54



Figure 6: TN2312BP IPSI circuit pack faceplate

Figure notes:

1. Red LED (ON indicates power up/failure)2. Green LED (ON indicates circuit pack in use)3. Amber LED (ON indicates maintenance diagnostics/

testing)4. Yellow LED (tone clock status)5. Emergency transfer LED

6. Services RJ45 connector 7. Network control RJ45 connector 8. Four-character LED display

9.Pushbutton switch

10. Slot for the maintenance cable

ckdfips2 KLC 091403

CLK

SERVICE

NETWORK

7 0 0 0 6 0 6 4 3

A V A Y A

0 1 D R 0 6 1 4 2 2 4 6

TN2312AP IPSI

3

4

5

8

9

1

2

6

7

10


45/54


46/54




47/54


Appendix A: Installation troubleshooting

This section provides some simple strategies to help you troubleshoot an installation of aserver. This section includes:

Troubleshooting the installation of the server hardware on page 47

Troubleshooting the configuration of the server hardware on page 48

Troubleshooting the installation of the license file and the Avaya authentication file onpage 50

Troubleshooting the installation of the server hardware.

Problem Possible solution

No power to theUPS

Ensure that the UPS is plugged into the outlet. Ensure that the outlet has power. For other solutions, see the user guide for the UPS.

No power to theEthernet switch

Ensure that the Ethernet switch is plugged into the UPS or the outlet. Ensure that the UPS or outlet has power. For other solutions, see the user guide for the Ethernet switch.

No power to theserver

Ensure that the power supply of the server is seated. Ensure that the server is plugged into the UPS. Ensure that the UPS has power. Push the power button on the front of the server.

Note:Note: "No power to the server" means that the server is not

functioning, probably because it is not receiving powersupply.

The IPSI LEDsflash

Ensure that the IPSI is in the correct slot. Use slot 1 for the G650Media Gateway.

Ping the IPSI from server. Ping the server from the IPSI.


48/54


48

Troubleshooting the configuration of the server hardware



Cannot log in to theUPS subagent

Ensure that the SNMP subagent is installed in the UPS. Ensure that you are connected to the correct Ethernet port. Ensure that you have the correct login ID and password. For

more information, see the user guide for the SNMP subagent. Ensure that the network card on the laptop computer is

configured correctly.

Cannot log in to theEthernet switch

Ensure that you are connected to the correct Ethernet port. (Onthe Ethernet switch, the correct port is labeled Console)

Ensure that you have the correct login ID and password. See theuser guide for the Ethernet switch.

Ensure that the network card on the Services laptop computer isconfigured correctly.

Cannot log in to theserver

Check the link LED on the server. If the LED is off, a cable orhardware problem exists.

Ensure that you are using SSH and not telnet. Ensure that you are connected to the Services Ethernet port. Ensure that you are using a cross-over cable between the

Services laptop computer and the server. Ensure that the ARP cache is cleared on the Services laptop

computer. In an MS-DOS window, type arp -d and press Enter .

Ensure that you have connectivity. In an MS-DOS window, type ping and press

Enter . Ensure that the NIC on the Services laptop computer is

configured correctly.

Cannot access theSAT

Ensure that you are using the correct IP address and port 5022. Ensure that you are using SSH and not telnet. Ensure that you are using the correct login and password.

Cannot ping out tothe customer network

Ensure that in the LAN security settings output from server foricmp is enabled.

1 of 2


49/54



Cannot ping theserver from thecustomer network

Ensure that in the LAN security settings input to server for icmpis enabled.

Cannot access theserver remotely

Ensure that in the LAN security settings input to server ischecked for SSH (Linux commands), https (Web access), anddef-sat (SAT commands access). Change the LAN securitysettings on the Web interface with a direct connection to theserver.

The LED display onIPSI is flashing

An IP address is not assigned to the IPSI LED (static IPaddressing).

Cannot access theIPSI for staticaddressing

Ensure that you are plugged into the Services (top) port on theIPSI.

Ensure that the ARP cache is cleared on the Services laptop

computer. In an MS-DOS command window, type arp -d192.11.13.6 and press Enter .

No V shows on theIPSI LED

The IPSI is not connected to the Ethernet switch or the network.Connect a cable to the bottom port on the faceplate and to theEthernet switch or the customer network.

Make sure port on the Ethernet switch that is assigned to thatIPSI is enabled.

The V on the IPSILED is not filled in

An IP address is not assigned to the IPSI. The IPSI is not administered.

The systemgenerates an alarmwhen first connect toIPSI

The IPSI does not have the current firmware. Upgrade thefirmware.

Cannot log in to theserver

If you are connecting laptop to the services port of the server,ensure that IP forwarding is enabled at the System Domain(Domain-0) command line.

Troubleshooting the configuration of the server hardware (continued)


2 of 2


50/54


50

Troubleshooting the installation of the license file andthe Avaya authentication file


Cannot get license file from thePLDS site

Provide the correct LAC. Search for your entitlements and locate the LAC. See

Searching for entitlements in Getting Started with Avaya PLDS .

Cannot install the license file onthe WebLM server

The file might be corrupt. Download the file again fromthe PLDS.

Note:Note: If the license file cannot be installed on the

WebLM server, the WebLM server returnsan error message, indicating why the filewill not install. Read the WebLM errormessage and correct the problem asindicated in the error message. A corruptfile is one of the reasons why the file mightnot install.

The server is in no-license mode Download a license file from the PLDS and install it onthe WebLM server.

Note:Note: If Communication Manager is in no-license

mode, it will indicate the nature of theerror. Read the error message and correctthe problem as indicated in the errormessage. A missing file is one of thereasons why Communication Manager isin no-license mode.

Cannot use the administrationcommands

The server might be in no license mode because the30-day grace period has expired. Download a licensefile from the PLDS and install it in WebLM. See thetroubleshooting step for the server being in no-licensemode.


51/54

Troubleshooting the installation of the license file and the Avaya authentication file


ASG on Avaya services loginsdoes not work

Reinstall the Avaya authentication file on the SystemPlatform Console Domain.

If ASG on Avaya services logins still does not work,create a replacement authentication and install it onthe System Platform Console Domain.

Authentication file installed on theSystem Platform ConsoleDomain is not present on theCommunication Manager server

Administer a super-user login on the active server.



52/54


53/54

Installing and Configuring Avaya Aura Communication Manager Solution June 2010 53

Index

Index

Aadd

IP interface information . . . . . . . . . . . . . 26media gateways . . . . . . . . . . . . . . . . 24

administer IPSI circuit pack . . . . . . . . . . . . . . . . 17

alarm activation levelsetting . . . . . . . . . . . . . . . . . . . . . 27

alarmssetting selected traps . . . . . . . . . . . . . . 12viewing . . . . . . . . . . . . . . . . . . . . . 34

CC363T or C364T Ethernet switch

configuring . . . . . . . . . . . . . . . . . . . 12LEDs . . . . . . . . . . . . . . . . . . . . . 41security alert . . . . . . . . . . . . . . . . . . 12

configure Avaya C363T or C364T Ethernet switch . . . . . 12server . . . . . . . . . . . . . . . . . . . . . 23UPS . . . . . . . . . . . . . . . . . . . . . . . 9

Ddate and time, verifying . . . . . . . . . . . . . . . 33daylight savings rules

location . . . . . . . . . . . . . . . . . . . . 32setting . . . . . . . . . . . . . . . . . . . . . 31

DHCP IP addressingIPSI circuit pack . . . . . . . . . . . . . . . . 17

diffserv parameters, setting . . . . . . . . . . . . . 20

EEthernet switch

configuring . . . . . . . . . . . . . . . . . . . 14default IP addresses . . . . . . . . . . . . . . 13preparing to configure . . . . . . . . . . . . . . 13

Ffaceplate

TN2312BP circuit pack . . . . . . . . . . . . . 43

Iinputting translations . . . . . . . . . . . . . . . . 23installation

troubleshooting . . . . . . . . . . . . . . . . . 47installing

translation file . . . . . . . . . . . . . . . . . . 27IP address

set static . . . . . . . . . . . . . . . . . . . . 17IP address, set static . . . . . . . . . . . . . . . . 17IP interface

enabling control . . . . . . . . . . . . . . . . . 28upgrading firmware version . . . . . . . . . . . 28verify translations . . . . . . . . . . . . . . . . 27

IP interface informationadding to translations . . . . . . . . . . . . . . 26

IPSIconnecting to . . . . . . . . . . . . . . . . . . 17LEDs . . . . . . . . . . . . . . . . . . . . . . 43program switch ID and cabinet . . . . . . . . . . 17

LLED

additional information . . . . . . . . . . . . . . 40LEDs

Avaya Ethernet switches . . . . . . . . . . . . . 41

IPSI . . . . . . . . . . . . . . . . . . . . . . 43server LEDs . . . . . . . . . . . . . . . . . . . 38UPS . . . . . . . . . . . . . . . . . . . . . . 42

license file, testing . . . . . . . . . . . . . . . . . 37location

setting for media gateways . . . . . . . . . . . . 32

Mmedia gateways, adding . . . . . . . . . . . . . . 24

P

post installation tasks . . . . . . . . . . . . . . . . 38

Ssaving translations . . . . . . . . . . . . . . . 23 , 27server

configuring . . . . . . . . . . . . . . . . . . . 23


54/54

Index

LED, additional information . . . . . . . . . . . 40verify connectivity . . . . . . . . . . . . . . . . 27

setalarm activation level . . . . . . . . . . . . . . 27daylight savings rules . . . . . . . . . . . . . . 31selected traps (alarming) . . . . . . . . . . . . 12static IP address . . . . . . . . . . . . . . . . 17

set static IP address . . . . . . . . . . . . . . . . 17SNMP

preparing to configure . . . . . . . . . . . . . . 10SNMP modules

administering . . . . . . . . . . . . . . . . . . . 11spanning tree

enabling . . . . . . . . . . . . . . . . . . . . 14setting version . . . . . . . . . . . . . . . . . 14

static IP addressingIPSI circuit pack . . . . . . . . . . . . . . . . 17setting . . . . . . . . . . . . . . . . . . . . . 17

static IP addressing, setting . . . . . . . . . . . . . 17Survivable remote server

main server identifies survivable remote server . . 29readminister media gateway . . . . . . . . . . . 30

Ttable 9 . . . . . . . . . . . . . . . . . . . . . 38 , 39testing

license file . . . . . . . . . . . . . . . . . . . 37server installation . . . . . . . . . . . . . . . . 37TN2312BP . . . . . . . . . . . . . . . . . . . 37

TN2312BPfaceplate . . . . . . . . . . . . . . . . . . . . 43LEDs . . . . . . . . . . . . . . . . . . . . . 43program switch ID and cabinet . . . . . . . . . . 17

TN2312BP, testing . . . . . . . . . . . . . . . . . 37translation file

installing . . . . . . . . . . . . . . . . . . . . 27translations

inputting . . . . . . . . . . . . . . . . . . . . 23IP interface . . . . . . . . . . . . . . . . . . . 23saving . . . . . . . . . . . . . . . . . . . . 23 , 27verifying . . . . . . . . . . . . . . . . . . . . 31

troubleshooting, server installation . . . . . . . . . 47

Uupgrading

IP interface firmware version . . . . . . . . . . 28

UPSdefault IP addresses for S8400 and S8500 . . . . 10LEDs . . . . . . . . . . . . . . . . . . . . . 42security alert . . . . . . . . . . . . . . . . . . . 9SNMP module . . . . . . . . . . . . . . . . . . 9

f

Vverify

connectivity to servers . . . . . . . . . . . . . . 27date and time . . . . . . . . . . . . . . . . . . 33IP interface translated . . . . . . . . . . . . . . 27

translations . . . . . . . . . . . . . . . . . . . 31view alarms . . . . . . . . . . . . . . . . . . . . 34VLAN parameters, setting . . . . . . . . . . . . . . 20

install and config cm solution

Documents