how to configure an ip connect high reliability

Avaya Solution and Interoperability Test Lab

How to Configure an IP Connect High Reliability Configuration using Avaya S8700-Series Media Servers, IPSI and Media Processor Duplication – Issue 1.0

Abstract

These Application Notes describe how to configure an IP Connect High Reliability configuration using separate control networks for IP Server Interface (IPSI) connectivity to the Avaya S8700-Series Media Servers, with IPSI and Media Processor duplication. These Application Notes were written at the request of a customer.

SH; Reviewed: PV 4/13/06

Solution & Interoperability Test Lab Application Notes © 2006 Avaya Inc. All Rights Reserved.

1 of 29 sa-ip-hr.doc

1. Introduction These Application Notes describe how to configure an IP Connect High Reliability configuration using separate control networks for IP Server Interface (IPSI) connectivity to the Avaya S8700-Series Media Servers, with IPSI and Media Processor duplication. High reliability in an IP Connect configuration can be implemented by using two TN2312BP IPSI circuit packs, with one IPSI in each Avaya G650 Media Gateway carrier (i.e., carrier A and carrier B) in a cabinet or port network. A cabinet or port network is a stack of Avaya G650 Media Gateways that are TDM-cabled together. One IPSI is the active IPSI and the other one is the standby IPSI. In the event of an active IPSI failure, the standby IPSI will become active. Each IPSI is connected to a separate Control Network (i.e., A and B) providing connectivity to each Avaya S8700-Series Media Server to eliminate single points of failure. Two Cisco Catalyst 2950 Ethernet switches are used in these Application Notes, one for each Control Network. Each Avaya S8700-Series Media Server is also configured to use the Corporate LAN interface in addition to being able to access each Control Network. The TN2602AP IP Media Processor circuit pack provides audio processing for the following types of calls:

• TDM-to-IP • IP-to-TDM • IP-to-IP

Note: The TN2602AP IP Media Processor is not supported in the CMC1 and G600 Media Gateways. For more information about the TN2602AP circuit pack, refer to [5] in Section 8. Two TN2602AP circuit packs may be installed in a single port network for bearer signal duplication. One TN2602AP is the active IP Media Processor and the other one is the standby IP Media Processor. In the event of an active Media Processor failure, active connections will failover to the standby Media Processor and remain active. This duplication prevents active calls in progress from being dropped in case of failure. Both TN2602AP circuit packs must be hardware version 2, and must have firmware version 21 or higher for bearer duplication. Note: The 4606, 4612, and 4624 telephones do not support the bearer duplication feature of the TN2602AP circuit pack. If these telephones are used while an interchange from active to standby Media Processor occurs, calls may be dropped. The following were tested using the configuration in these Application Notes:

• Separate control networks for IPSI connectivity • IPSI duplication • Media Processor duplication




Figure 1 illustrates the Credit Card and Banking Configuration used to verify these Application Notes. The reference configuration represents a typical financial customer. It is a hub and spoke architecture where the Main Office consists of Avaya S8710 Media Servers with two Avaya G650 Media Gateway carriers in an IP Connect High Reliability configuration. Each Avaya S8710 Media Server in the Main Office is configured to use the Corporate LAN interface in addition to being able to access the IPSIs located in the port network at the Main Office using separate Control Networks. The Branch Offices register to C-LANs in the Avaya G650 Media Gateway carriers at the Main Office. The Branch Offices also have local survivability options. This includes an Avaya S8300 Media Server licensed as a Local Survivable Processor (LSP) in an Avaya G700 Media Gateway at Branch 3, an Avaya S8500 Media Server also licensed as an LSP at Branch 4, and Standard Local Survivability Mode configured for the Avaya G250 Media Gateway at Branch 5. Each office has trunks to the Public Switched Telephone Network (PSTN). The Main Office also has the Avaya Call Management System, which is used for contact center administration and reporting for all offices. All IP Telephones at all offices register to Avaya Communication Manager running on the Avaya S8710 Media Servers at the Main Office. The configuration of the local survivability options used in each branch will not be covered in these Application Notes. Note: The administration of the network infrastructure shown in Figure 1 is not the focus of these Application Notes and will not be covered. Instead, the focus of these Application Notes is to use separate control networks for IPSI connectivity to the Avaya Media Servers with IPSI and Media Processor duplication at the Main Office location in Figure 1.




!

Figu

re 1

– N

etw

ork

Con

figur

atio

n D

iagr

am




Table 1 lists the IP address assignment for the equipment shown in Figure 1.

Equipment IP Network/Mask Description S8710 Media Server – 1 Ethernet 0 Active Server Ethernet 1 Ethernet 2 Ethernet 3 Active Server Ethernet 4 Active Server Gateway

10.1.5.11/24 10.1.5.10/24 192.11.13.6/30 192.11.13.13/30 10.1.6.11/24 10.1.6.10/24 10.1.2.11/24 10.1.2.10/24 10.1.2.1/24

Control Network A Active server address for Control Network A Services Port Server Duplication Link Control Network B Active server address for Control Network B Corporate LAN Active server address for Corporate Network Gateway address

S8710 Media Server – 2 Ethernet 0 Active Server Ethernet 1 Ethernet 2 Ethernet 3 Active Server Ethernet 4 Active Server Gateway

10.1.5.12/24 10.1.5.10/24 192.11.13.6/30 192.11.13.14/30 10.1.6.12/24 10.1.6.10/24 10.1.2.12/24 10.1.2.10/24 10.1.2.1/24

Control Network A Active server address for Control Network A Services Port Server Duplication Link Control Network B Active server address for Control Network B Corporate LAN Active server address for Corporate Network Gateway address

IPSI – A Gateway

10.1.5.20/24 10.1.5.1/24

IPSI connected to Control Network A Gateway address

IPSI – B Gateway

10.1.6.20/24 10.1.6.1/24

IPSI connected to Control Network B Gateway address

MedPro – A Shared Virtual Gateway

10.1.2.15/24 10.1.2.30/24 10.1.2.1/24

Media Processor in Avaya G650 – A Virtual address of Media Processor Gateway address

MedPro – B Shared Virtual Gateway

10.1.2.17/24 10.1.2.30/24 10.1.2.1/24

Media Processor in Avaya G650 – B Virtual address of Media Processor Gateway address

Table 1 – IP Address Assignment




2. Equipment and Software Validated The following hardware and software versions were used for this configuration: Equipment Version Avaya S8710 Media Server 3.1 Load 628.6 and Service Pack 11410 Avaya G650 Media Gateway Avaya TN2312BP IPSI Avaya TN799DP C-LAN Avaya TN2602AP MEDPRO

HW12 FW030 HW01 FW017 HW02 FW21

Avaya 4610SW IP Telephone 2.3 Avaya 4620SW IP Telephone 2.3 Avaya 4621SW IP Telephone 2.3 Avaya 4622SW IP Telephone 2.3 Avaya 4625SW IP Telephone 2.5 Cisco Catalyst 2950 12.1(22)

Table 2 – Equipment and Version Validated




3. IP Server Interface (IPSI) Configuration The following procedure shows how to configure the IPSI circuit pack located in each of the Avaya G650 Media Gateway carriers. There are two Ethernet ports on the front of the IPSI circuit pack. The upper port is the Services port with a pre-configured IP address of 192.11.13.6 and a subnet mask of 255.255.255.252. The lower port is the Control Network port. Step Description

1. Configure the IP address of a laptop to 192.11.13.5 with a subnet mask of 255.255.255.252 and connect the Ethernet port of the laptop to the Services port of the IPSI for Control Network A using an Ethernet crossover cable.

2. Telnet to 192.11.13.6, the IP address of the Services port, and type “ipsilogin” at the command prompt to log in to the IPSI with the default login and password.

3. Figure 2 shows how to configure the IP address and default gateway for the IPSI connected to Control Network A using the IP addresses listed in Table 1.

Figure 2 – Avaya IPSI Circuit Pack Configuration for Control Network A

TN2312 IPSI IP Admin Utility Copyright Avaya Inc, 2003, All Rights Reserved [IPSI]: ipsilogin Login: craft Password: [IPADMIN]: set control interface 10.1.5.20 255.255.255.0 WARNING! The control network interface IP operating parameters will be updated upon exiting IPADMIN! See the "set control interface" command help and the "show route" command output (and command help) before AND after changing any IP operating parameters. It is highly recommended that you reset the IPSI when done, and run the "show route" command again to insure the routing table is exactly as you expect it to be. [IPADMIN]: set control gateway 10.1.5.1 WARNING! The control network interface IP operating parameters will be updated upon exiting IPADMIN! See the "set control interface" command help and the "show route" command output (and command help) before AND after changing any IP operating parameters. It is highly recommended that you reset the IPSI when done, and run the "show route" command again to insure the routing table is exactly as you expect it to be. [IPADMIN]: reset




Step Description 4. Use the “show route” command to verify the configuration of the default gateway.

Figure 3 – IPSI Default Gateway

5. Use the “show qos” command to show view the QoS settings for the IPSI. VLAN id is set to 0 by default and cannot be changed. The following commands may be used if changes are required:

• “set diffserv” command to change the Diffserv value • “set user priority” command to change the user priority • “set VLAN tagging on” command to enable VLAN tagging

The “reset” command is required in order to activate the changes.

Figure 4 – IPSI QoS settings

6. Connect the Ethernet port of the laptop to the Services port of the IPSI for Control Network B using an Ethernet crossover cable. Repeat Steps 2 through 5 to configure the IPSI for Control Network B.

[IPADMIN]: show route ROUTE NET TABLE destination gateway flags Refcnt Use Interface ---------------------------------------------------------------------------- 0.0.0.0 10.1.5.1 3 2 225729 motfcc1 10.1.5.0 10.1.5.20 101 0 0 motfcc1 192.11.13.0 192.11.13.6 101 0 0 motfcc2 192.168.13.0 192.168.13.65 101 0 0 pkt3 ---------------------------------------------------------------------------- ROUTE HOST TABLE destination gateway flags Refcnt Use Interface ---------------------------------------------------------------------------- 127.0.0.1 127.0.0.1 5 0 4 lo0 ----------------------------------------------------------------------------

[IPADMIN]: show qos QoS values currently in use: VLAN tagging : on VLAN id : 0 VLAN user priority : 7 Diffserv value : 34 QoS values to be used after next reset: VLAN tagging : on VLAN id : 0 VLAN user priority : 7 Diffserv value : 34




4. Avaya Media Server Configuration This section shows how to configure the Avaya S8710 Media Servers. The assumption is that the appropriate license and authentication files have been installed on the servers and that login and password credentials are available. Configure the IP address of a laptop to 192.11.13.5 with a subnet mask of 255.255.255.252, and connect the Ethernet port of the laptop to the Services port (Ethernet port 1) of one of the Avaya S8710 Media Servers using an Ethernet crossover cable. The services port uses the pre-configured IP address 192.11.13.6 with a subnet mask of 255.255.255.252.




Step Description

1. Launch a web browser and connect to URL http://192.11.13.6 with proxies turned off. Supply the appropriate login and password credentials when prompted.

2. Click “Launch Maintenance Web Interface” on the main menu. Click “Configure Server” under the Server Configuration category in the lower left pane.

Figure 5 – Maintenance Web Interface




Step Description 3. Click “Continue” on the Review Notices page. Click “Continue” on the “Back Up Data” page.

Click the “Configure individual services” radio button. Check the “The Corporate LAN interface of both servers is on the same subnet” and “The Control Network interface of both servers is on the same subnet” boxes. Click “Continue”.

Figure 6 – Copy Settings (Server 1)




Step Description 4. Click “Set Identities” on the left pane to set the hostname or identity of each Server. Select “1”

for the “This is server number” field. Assign the Ethernet ports based on the information in Table 1. Click Continue.

Figure 7 – Set Identities




Step Description 5. Click “Configure Interfaces” on the left pane to assign the IP address for each Ethernet port

using the information provided in Table 1. Check the “Enable VLAN 802.1q priority tagging” box to globally enable tagging on the S8710 Media Server if VLANs are used. The command “change ipserver-interface” in Figure 16 will set the 802.1p and DiffServ values on tagged traffic to the IPSI.

Figure 8 – Configure Interfaces




Step Description 6. Figure 9 shows the lower half of the “Configure Interfaces” page. Click “Change” to save the

settings.

Figure 9 – Configure Interfaces (Continued)




Step Description 7. Connect the Ethernet port of the laptop to the Services port (Ethernet port 1) of the other

Avaya S8710 Media Server using an Ethernet crossover cable. Repeat Steps 1 through 6 to configure the identity and Ethernet ports of the second media server. The only difference is that “2” is selected in the “This is server number” field in Step 4 as shown in Figure 10.

Figure 10 – Set Identities (Server 2)




5. Avaya Communication Manager Configuration The following configuration was entered via the System Access Terminal (SAT).

5.1. IP Port Network and Media Processor Options Step Description

1. An Avaya representative must administer the fields or install a license file that enables the options identified by these fields shown in the following “Optional Features” screens. Use the “display system-parameters customer-options” command to verify that the Maximum TN2602 Boards with 320 VoIP Channels reflects the number of TN2602 circuit packs in the system.

Figure 11 – Optional Features (Page 2)

display system-parameters customer-options Page 2 of 11 OPTIONAL FEATURES IP PORT CAPACITIES USED Maximum Administered H.323 Trunks: 500 5 Maximum Concurrently Registered IP Stations: 2000 32 Maximum Administered Remote Office Trunks: 8000 2 Maximum Concurrently Registered Remote Office Stations: 12000 4 Maximum Concurrently Registered IP eCons: 0 0 Max Concur Registered Unauthenticated H.323 Stations: 600 0 Maximum Video Capable H.323 Stations: 0 0 Maximum Video Capable IP Softphones: 0 0 Maximum Administered SIP Trunks: 20 0 Maximum Number of DS1 Boards with Echo Cancellation: 5 0 Maximum TN2501 VAL Boards: 3 2 Maximum G250/G350/G700 VAL Sources: 10 3 Maximum TN2602 Boards with 80 VoIP Channels: 20 0 Maximum TN2602 Boards with 320 VoIP Channels: 5 2 Maximum Number of Expanded Meet-me Conference Ports: 5 0 (NOTE: You must logoff & login to effect the permission changes.)




Step Description 2. Use the “display system-parameters customer-options” command to verify that the “Internet

Protocol (IP) PNC” field on Page 4 set to “y”.


display system-parameters customer-options Page 4 of 11 OPTIONAL FEATURES Emergency Access to Attendant? y IP Stations? y Enable 'dadmin' Login? y Internet Protocol (IP) PNC? y Enhanced Conferencing? y ISDN Feature Plus? y Enhanced EC500? n ISDN Network Call Redirection? y Enterprise Survivable Server? n ISDN-BRI Trunks? y Enterprise Wide Licensing? n ISDN-PRI? y ESS Administration? y Local Survivable Processor? n Extended Cvg/Fwd Admin? n Malicious Call Trace? y External Device Alarm Admin? n Media Encryption Over IP? y Five Port Networks Max Per MCC? n Mode Code for Centralized Voice Mail? n Flexible Billing? n Forced Entry of Account Codes? n Multifrequency Signaling? y Global Call Classification? n Multimedia Appl. Server Interface (MASI)? n Hospitality (Basic)? y Multimedia Call Handling (Basic)? y Hospitality (G3V3 Enhancements)? y Multimedia Call Handling (Enhanced)? y IP Trunks? y IP Attendant Consoles? y (NOTE: You must logoff & login to effect the permission changes.)




Step Description 3. Go to Page 5 of the “Optional Features” screen and verify that the “Port Network Support”

field is set to “y”. A port network or cabinet is a stack of Avaya G650 Media Gateways that are TDM-cabled together.


display system-parameters customer-options Page 5 of 11 OPTIONAL FEATURES Multinational Locations? n Station and Trunk MSP? n Multiple Level Precedence & Preemption? n Station as Virtual Extension? n Multiple Locations? y System Management Data Transfer? n Personal Station Access (PSA)? y Tenant Partitioning? n Posted Messages? n Terminal Trans. Init. (TTI)? y PNC Duplication? n Time of Day Routing? y Port Network Support? y Uniform Dialing Plan? y Usage Allocation Enhancements? y Processor and System MSP? n TN2501 VAL Maximum Capacity? y Private Networking? y Processor Ethernet? y Wideband Switching? y Wireless? n Remote Office? y Restrict Call Forward Off Net? y Secondary Data Module? y (NOTE: You must logoff & login to effect the permission changes.)




5.2. IP Node Names Use the “change node-names ip” command to add new node names for each TN2602 Media Processor. Figure 14 displays the node names and IP addresses assigned to the Media Processors. change node-names ip Page 1 of 1

IP NODE NAMES Name IP Address Name IP Address BO6 10 .16 .2 .10 . . . G250-BR5 10 .15 .2 .11 . . . aesserver 10 .1 .1 .50 . . . br3-lsp 10 .13 .2 .10 . . . br4-elsp 10 .14 .2 .9 . . . br4-lsp 10 .14 .2 .10 . . . br5 10 .15 .2 .10 . . . cc-ess1 10 .2 .2 .11 . . . cc-ess2 10 .2 .2 .12 . . . ccaesbr4 10 .14 .1 .50 . . . cf-1a03 10 .1 .2 .15 . . . cf-1b03 10 .1 .2 .17 . . . clan-1a02 10 .1 .2 .21 . . . clan-1a04 10 .1 .2 .23 . . . clan-1b02 10 .1 .2 .25 . . . clan-2a02 10 .2 .2 .21 . . . ( 16 of 28 administered node-names were displayed ) Use 'list node-names' command to see all the administered node-names Use 'change node-names ip xxx' to change a node-name 'xxx' or add a node-name

Figure 14 – IP Node Names




5.3. Cabinet Configuration Both Avaya G650 Media Gateway carriers at the Main Office will be configured as carriers within one cabinet. Use the “add cabinet” command to add the cabinet. Use the “change cabinet” command to view the cabinet. Figure 15 displays the information for this cabinet. Note that “G650-rack-mount-stack” is specified in the “Cabinet Layout” field. change cabinet 1 Page 1 of 1

CABINET CABINET DESCRIPTION Cabinet: 1 Cabinet Layout: G650-rack-mount-stack Cabinet Type: expansion-portnetwork Location: 1 IP Network Region: 1 Rack: 1 Room: 1B-337 Floor: Building: CARRIER DESCRIPTION Carrier Carrier Type Number E not-used PN 01 D not-used PN 01 C not-used PN 01 B G650-port PN 01 A G650-port PN 01

Figure 15 – Cabinet Configuration




5.4. IPSI Configuration The following step configures a primary and secondary IPSI in Port Network 1 at the Main Office. Use the “add ipserver-interface command to administer the primary and secondary IPSIs in cabinet 1. Use the “change ipserver-interface” command to view the IPSI configuration after the IPSIs have been added. The Avaya S8710 Media Server will use the values listed under QoS parameters when the “Enable VLAN 802.1q priority tagging” box is checked in Figure 8.

change ipserver-interface 1 Page 1 of 1 IP SERVER INTERFACE (IPSI) ADMINISTRATION - PORT NETWORK 1 IP Control? y Socket Encryption? y Ignore Connectivity in Server Arbitration? n Enable QoS? y Administer secondary ip server interface board? y Primary IPSI QoS Parameters ------------ -------------- Location: 1A01 Call Control 802.1p: 7 Host: 10.1.5.20 Call Control DiffServ: 34 DHCP ID: ipsi-A01a Secondary IPSI -------------- Location: 1B01 Host: 10.1.6.20 DHCP ID: ipsi-A01b

Figure 16 – IPSI Administration – Port Network 1




5.5. Enable IPSI Control of Port Networks The following step will allow the IPSI to control the Port Networks. Use the “change system-parameters ipserver-interface” command to enable IPSI control of Port Networks. Enter an identifier in the “Switch Identifier” field. Set the “IPSI Control of Port Network” field to “enabled”.

change system-parameters ipserver-interface Page 1 of 1 IP SERVER INTERFACE (IPSI) SYSTEM PARAMETERS SERVER INFORMATION IPSI Host Name Prefix: Primary Control Subnet Address: . . . * Secondary Control Subnet Address: . . . * OPTIONS Switch Identifier: A IPSI Control of Port Networks: enabled NOTE: * indicates data changed on the Server

Figure 17 – IPSI Control of Port Networks




5.6. Enable IPSI Duplication The following step will enable IPSI duplication. IPSI duplication requires that all IPSI connected port networks have a primary (Control Network A) IPSI in one G650 carrier and a secondary (Control Network B) IPSI in another G650 carrier of the port network. IPSI duplication is not supported in a single Avaya G650 carrier. Use the “change system-parameters duplication command to enable the IPSI duplication feature. Note: If CMC1 and G600 carriers exist in a configuration, the “Enable Operation of IPSI Duplication” field cannot be set to “y”.

change system-parameters duplication Page 1 of 1 DUPLICATION RELATED SYSTEM PARAMETERS Enable Operation of IPSI Duplication? y

Figure 18 – IPSI Duplication Configuration




5.7. TN2602 Media Processor Configuration Use the “add ip-interface” command to administer the primary and secondary TN2602 Media Processors. After the Media Processors have been added, use the “display ip-interface” command to view the TN2602 Media Processor configuration. Figure 19 displays the TN2602 Media Processor configuration. Use the Node Name specified in Figure 14 for each Media Processor circuit pack. The IP address specified in the “Shared Virtual Addresss” field will be used by the active Media Processor.

display ip-interface 1a03 Page 1 of 1 IP INTERFACES Critical Reliable Bearer? y Type: MEDPRO Slot: 01A03 Slot: 01B03 Co Code/Suffix: TN2602 de/Suffix: TN2602 Node Name: cf-1a03 Node Name: cf-1b03 IP Address: 10 .1 .2 .15 IP Address: 10 .1 .2 .17 Subnet Mask: 255.255.255.0 Gateway Address: 10 .1 .2 .1 Enable Ethernet Port? y Enable Ethernet Port? y Network Region: 1 VLAN: 2 VLAN: 2 VOIP Channels: 320 Shared Virtual Address: 10 .1 .2 .30 Virtual MAC Table: 1 Virtual MAC Address: 02:04:0d:4a:53:c0 ETHERNET OPTIONS Auto? y Auto? y

Figure 19 – TN2602 Media Processor Configuration

5.8. Save Configuration Use the “save translation all” command to save the Avaya Communication Manager configuration.

save translation all SAVE TRANSLATION Command Completion Status Error Code Success 0

Figure 20 – Save Translation




6. Verification Steps The following steps can be performed to verify that the IP Connect High Reliability configuration is working: Step Description

1. Use the “status port-network” command to verify the status of the port network. Verify that the statuses of the “Active” and “Standby” fields are in the “up” state.

Figure 21 – Port Network Status

2. Use the “list ip server-interface” command to verify the service and control states of the IPSI circuit packs. Verify the “Serv State” field is in the “IN” state for both active and standby IPSI circuit packs. The “Control State” field should be “act-aa” for the active IPSI and “standby” for the standby IPSI.

Figure 22 – IP Server Interface Information

list ipserver-interface IP SERVER INTERFACE INFORMATION Port Pri/ Primary/ Primary/ Primary/ State Of Ntwk Sec Secondary Secondary Secondary Serv Control Health Num Bd Loc IP Address Host Name DHCP ID State State C P E G ---- ------ --------------- ---------------- --------- ----- ------- ------- 1 1A01 10.1.5.20 10.1.5.20 ipsi-A01a IN actv-aa 0.0.0.0 1B01 10.1.6.20 10.1.6.20 ipsi-A01b IN standby 0.0.0.0 2 2A01 10.2.2.20 10.2.2.20 ipsi-A02a IN actv-aa 0.0.0.0

status port-network 1 PORT NETWORK STATUS Major Minor Warning Carrier PN Control Internet Protocol (IP) PN Alarms Alarms Alarms Locs Active Standby Connected Port Network 1 0 0 34 01A up up 01B TDM Service Control Dedicated TONE/ Service System System Bus State Channel Tones CLOCK State Clock Tones A in y n 01B in standby standby B in n y 01A in active active Service Major Minor Bus Open Bus PKT State Alarms Alarms Faults Leads 1 in n n 0 0




Step Description 3. Place a call from a phone in the Main Office to another phone in the same site. Verify that the

phone rings and can be answered. Verify two-way talk path between the two phones. 4. Disconnect the Ethernet cable connected to the active IPSI. Use the “list ip server-interface”

command to verify the control state of the “standby” IPSI in Step 2 has changed to “actv-aa”. The “set ipserver-interface” command can also be used to manually switch the active and standby IPSI circuit packs.

5. Verify the call stays up between the two stations and that there is still a two-way talk path. 6. Place a call from an IP phone in the Main Office to a DCP phone in the same site. Verify that

the phone rings and can be answered. Verify two-way talk path between the two phones. 7. Use the “status media-processor” command to verify the status of the Media Processor and that

a call is active on a DSP of the active Media Processor.

Figure 23 – Media Processor Status before Failover

status media-processor board 1a03 MEDIA-PROCESSOR STATUS Duplication State: active Duplication State: standby Board Location: 01A03 Board Location: 01B03 Source IP Address: 10.1.2.15 Source IP Address: 10.1.2.17 Node Name: cf-1a03 Node Name: cf-1b03 Subnet Mask: 255.255.255.0 Subnet Mask: 255.255.255.0 Gateway Address: 10.1.2.1 Gateway Address: 10.1.2.1 MAC Address: 00:04:0d:a1:1c:ae MAC Address: 00:04:0d:a1:1c:bd Ethernet Enabled? yes Ethernet Enabled? yes COMMON DUPLICATED VALUES Links Alarms Standby Refreshed: yes Locked: no Links Alarms mpcl: up mj: 0 Network Region: 1 mpcl: up mj: 0 eth: up mn: 0 Shared IP Address: 10.1.2.30 eth: up mn: 0 peer: up wn: 0 Shared Virt-MAC: 02:04:0d:4a:53:c0 peer: up wn: 0 DSP Channel Status DSP 1: in-service/idle DSP 1: in-service/standby DSP 2: in-service/idle DSP 2: in-service/standby DSP 3: in-service/active, 1 calls DSP 3: in-service/standby DSP 4: in-service/idle DSP 4: in-service/standby




Step Description 8. Disconnect the Ethernet cable connected to the active Media Processor. Use the “status media-

processor” command to verify the status of the Media Processors after failover to the standby Media Processor. Figure 24 shows that the standby Media Processor is now active and that the call is now active on DSP 2. The “set media-processor” command can also be used to manually switch the active and standby Media Processors”. Use the “status media-processor” command to verify that the status of the other TN2602 Media Processor is now active.

Figure 24 – Media Processor Status after Failover

status media-processor board 1a03 MEDIA-PROCESSOR STATUS Duplication State: standby Duplication State: active Board Location: 01A03 Board Location: 01B03 Source IP Address: 10.1.2.15 Source IP Address: 10.1.2.17 Node Name: cf-1a03 Node Name: cf-1b03 Subnet Mask: 255.255.255.0 Subnet Mask: 255.255.255.0 Gateway Address: 10.1.2.1 Gateway Address: 10.1.2.1 MAC Address: 00:04:0d:a1:1c:ae MAC Address: 00:04:0d:a1:1c:bd Ethernet Enabled? yes Ethernet Enabled? yes COMMON DUPLICATED VALUES Links Alarms Standby Refreshed: yes Locked: no Links Alarms mpcl: up mj: 0 Network Region: 1 mpcl: up mj: 0 eth: up mn: 0 Shared IP Address: 10.1.2.30 eth: up mn: 0 peer: up wn: 0 Shared Virt-MAC: 02:04:0d:4a:53:c0 peer: up wn: 0 DSP Channel Status DSP 1: in-service/standby DSP 1: in-service/idle DSP 2: in-service/standby DSP 2: in-service/active, 1 calls DSP 3: in-service/standby DSP 3: in-service/idle DSP 4: in-service/standby DSP 4: in-service/idle




7. Conclusion These Application Notes describe how to configure High Reliability in an IP Connect configuration. High Reliability was achieved using separate control networks for each IPSI in a separate Avaya G650 Media Gateway carrier in a cabinet or port network with IPSI and Media Processor duplication.

8. Additional References The following Avaya product documentation can be found at http://support.avaya.com.

[1] Overview for Avaya Communication Manager, Release 3.1, Issue 2, February 2006, Document ID: 03-300468.

[2] Installing and Configuring the Avaya S8700-Series Media Server, Release 3.1, Issue 5, February 2006, Document ID: 03-300145.

[3] Installing the Avaya G650 Media Gateway, Release 3.1, Issue 1, February 2006, Document ID: 03-300685.

[4] Hardware Description and Reference for Avaya Communication Manager, Issue 5, February 2006, Document ID: 555-245-207.




© 2006 Avaya Inc. All Rights Reserved. Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by ® and ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. The information provided in these Application Notes is subject to change without notice. The configurations, technical data, and recommendations provided in these Application Notes are believed to be accurate and dependable, but are presented without express or implied warranty. Users are responsible for their application of any products specified in these Application Notes. Please e-mail any questions or comments pertaining to these Application Notes along with the full title and filename, located in the lower right corner, directly to the Avaya Solution & Interoperability Test Lab at [email protected]




how to configure an ip connect high reliability

Documents