Avaya Solution & Interoperability Test Lab

Instructions for Changing the Network Configuration of the Avaya IP Communications Development Environment Version 10

Abstract
These Application Notes describe the procedure for altering the networking configuration the Avaya IP Communications Development Environment.

Reviewed: 12/16/2008

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

1 of 19

1. Introduction
This document contains instructions which allow the end user to modify the IP addresses of Communication Manager, Applications Enablement Services or SIP Enablement Services virtual machine images of the Avaya IP Communications Development Environment (IPCoDE). It is suggested that you make a copy of the existing machine image before you start to ease recovery should you make a mistake or get your virtual machine in a state you can not recover from. The user should note that the Avaya IP Communications Development Environment is not intended to be a group development tool. It is suggested that modifying the IP addresses be done only to allow the connection of other network equipment (IP telephones, servers, etc) to the product configuration for the purpose of facilitating testing of other applications and network configurations.

2. Possible Networked Configurations

These instructions have been used to convert the installed product configurations (host only, on 192.168.17.*) to a bridged configuration on the same 192.168.17.* subnet (shown in Figure 1: Bridged to Private Network), as well as to change the IP addresses of the AE Services and Communication Manager servers to an alternate (e.g. 135.8.17.*) subnet (shown in Figure 2: Bridged to Corporate Network).

Reviewed: 12/16/2008

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

2 of 19

SES R3.1.1 192.168.17.130

CM R3.1.2 192.168.17.129

AES R3.1.2 192.168.17.128

VMware Network: 192.168.17.x

Development Tools, Application 192.168.17.10

Host (Development Tools, Application, DADS Console) 192.168.17.1

192.168.17.*

Figure 1: Bridged to Private Network

Reviewed: 12/16/2008

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

3 of 19

SES R3.1.1 135.8.17.130

CM R3.1.2 135.8.17.129

AES R3.1.2 135.8.17.128

VMware Network: 135.8.17.*

Development Tools, Application 135.8.17.5 Host (Development Tools, Application, DADS Console) 135.8.17.1

135.8.*.* Rest of Corporate LAN

Figure 2: Bridged to Corporate Network

3. Detailed Instructions
It is suggested that the individual performing the changes, read through these instructions completely before starting with any changes. It is assumed that IPCoDE is installed on VMWare workstation. The instructions will need to be altered for the different user interfaces on other VMWare products.

Reviewed: 12/16/2008

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

4 of 19

These instructions work starting with release 3.01.0002 of the Avaya IP Communications Development Environment. Attempting to use these instructions on an older release will be unsuccessful. There are faster ways to perform some of these operations. If you are familiar with them feel free to use them as long as the net effect is the same. In places the document refers to <new-XX-IP>. It is assumed that the reader has acquired static IP addresses from their IP management team for use when putting IPCoDE on a corporate LAN. The mechanism for acquiring a static IP will vary from one customer to the next.

3.1. Make a copy of an existing machine

To make a copy of an existing virtual machine, navigate to C:\Program Files\Avaya\Avaya IPCoDE. Use the windows copy and paste capability to copy the AES, CM and or SES directory to a new location to preserve a copy of the Virtual Machine. Note that the virtual machine can be re-installed from the DVD, the copy action is merely a convenience in case you want to start over for some reason.

3.2. Bridged to a Private Network

Make the changes described in section 3.4

3.3. Bridged to a Corporate Network

Make the changes described in section 3.5. When referred to from that section make the corresponding change described in section 3.4

3.4. Changing a virtual machine from host only to bridged

This change is needed if you intend on accessing the simulated server (AE Services, Communication Manager or SES) from a device (e.g. PC) external to the host PC that is running VMWare. You need to make this change to each machine that you wish to externalize. 1. Start VMWare, but do not power on the virtual machines. 2. Application Enablement Services Instructions a. Go to the system settings panel in VMWare for the Applications Enablement Services server and change the Ethernet interface to be bridged i. Right click on the AES tab in the virtual machines window ii. Choose Settings iii. Click on Ethernet iv. Set the Network Connection to Bridged 3. Communication Manager Instructions a. Go to the system settings panel in VMWare for the Communication Management server and change the Ethernet interface to be bridged i. Right click on the CM tab in the virtual machines window
Reviewed: 12/16/2008 Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved. 5 of 19

4.

5.

6. 7. 8. 9. 10.

ii. Choose Settings iii. Click on Ethernet iv. Set the Network Connection to Bridged SIP Enablement Services Instructions a. Go to the system settings panel in VMWare for the SIP Enablement Services server and change the Ethernet interface to be bridged i. Right click on the SES tab in the virtual machines window ii. Choose Settings iii. Click on Ethernet iv. Set the Network Connection to Bridged Change the PCs IP address to an available IP address in the 192.168.17.xx subnet (e.g 192.168.17.10) using the network connections properties for the physical interface. Connect the external devices to a hub/switch Configure the external devices with available IP addresses in the 192.168.17.xx. Connect the PC to the hub/switch. Change the subnet mask associated with the VMnet1 interface to 192.168.18.0 so it passes requests between the devices on either side of this interface.

Click on the > button at the end of the row labeled VMware Network Adapter VMnet1

Reviewed: 12/16/2008

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

6 of 19

Set the IP Address to 192.168.18.0 when setting up a private LAN configuration to prevent the adaptor from interfering with packet traffic between the virtual LAN endpoints (Communication Manager, Application Enablement Services and/or SIP Enablement Services), and the external network IP devices. If setting up a corporate LAN configuration, the subnet mask setting does not matter (unless your corporate LAN has a 192.168.17.* subnet and you are leaving the Application Enablement Services, Communication Manager and/or SIP enablement Services server on the 192.168.17 subnet in which case you need to set the mask to 192.168.18.0 just like the private network case.

11. Power on the virtual machines. 12. Once the virtual machines are running, try to ping from the virtual machine to the PCs IP address, in both directions.

Reviewed: 12/16/2008

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

7 of 19

13. If the ping is successful, you are done. If it is unsuccessful, check to make sure you properly implemented each step in this procedure. If you have verified the proper data in each step, try the Microsoft repair tool. Shutdown the virtual machines (`sudo /sbin/shutdown h now`), and then restart MS Windows. This is known to repair many odd issues with Microsoft products. If it fixes the issue, the problem was that the changes that were being made to the VMware virtual NICs were not taking in real time.

3.5. Changing Communication Manager, Applications Enablement Services or SIP Enablement Services servers IP addresses to a new subnet
3.5.1. Instructions for reconfiguring the Applications Enablement Services IP address.

1. From the Linux Console login as craft password: craft01 2. Run the script to reconfigure /etc/hosts and /etc/sysconfig/network-scripts/ifcfgeth0 by running:
sudo /root/bin/newIP <new-AES-IP> <networkMASK> <Gateway> <DNServer>

3. Verify the changes by looking at

o o /etc/hosts /etc/sysconfig/network-scripts/ifcfg-eth0

4. Go to the control panel in VMWare for the Applications Enablement Services server and change the Ethernet interface to be bridged o Right click on the AES tab in the virtual machines window o Choose Settings o Click on Ethernet o Set the Network Connection to Bridged 5. Then restart the system.
o sudo /sbin/shutdown r now

6. Once the Applications Enablement Services serverhas restarted, from browser like IE Explorer navigate to the address http://<new-AES-IP>:8080/MVAP a) Login as craft/craft01 b) Go to CTI OAM Admin Administration Switch Connections c) Select the cmsim transport link and click the Edit CLAN IPs button d) Add <new-CM-IP-adddress> as a new CLAN. e) Delete the existing 192.168.17.129 CLAN entry. f) Go to CTI OAM Admin Administration Switch Connections
Reviewed: 12/16/2008 Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved. 8 of 19

g) Select the cmsim transport link and click the Edit H.323 Gatekeeper button h) Enter the IP address of Communication Manager <new-CM-IP-adddress> into the text box and click on Add Name or IP. i) Delete the existing 192.168.17.129 IP address in the H.323 Gatekeeper List. Note: If the connection enters an invalid password state on the Switch Connection Summary page, reset the password to devconnect123456 using the [edit] capability for the cmsim Switch Connection available via CTI OAM Admin Administration Switch Connections.

3.5.2. Instructions for reconfiguring Communication Managers IP address

1. Go to the control panel in VMWare for CM and change the Ethernet interface to be bridged o Right click on the CM tab in the virtual machines window o Choose Settings o Click on Ethernet o Set the Network Connection to Bridged 2. From the Communication Manager Linux console login as craft password: crftpw o Run the script to reconfigure /etc/hosts and /etc/sysconfig/networkscripts/ifcfg-eth0 by running:
sudo /root/bin/newIP <hostIP> <networkMASK> <Gateway> <DNServer>

Verify the changes by looking at /etc/hosts /etc/sysconfig/network-scripts/ifcfg-eth0 and observing the new IP address for cmsim 3. Then restart the system. sudo /sbin/shutdown r now 4. If you are changing from one private host only subnet to another you will need to change the subnet in VMware Edit Virtual Network Settings. Select the Host Virtual Networking Mapping tab, and then click on the > on the right side of the panel on the VMnet1 row. Select Subnet and then change the IP address for the subnet so it does not match the subnet you are switching to.

3.5.2.1 Setting the Communication Managers IP Address in the vfmgui.ini file

When the DADS console is launched there is a command line argument imbedded that provides the IP address of Communication Manager to the tool. In the case where you have modified the Communication Manager IP address you must modify an .ini file with the new Communication Manager IP address.
Reviewed: 12/16/2008 Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved. 9 of 19

1. Navigate to C:\Program Files\Avaya\Avaya IPCoDE\Tools 2. Open the vfmgui.ini file with notepad

3. Change the IP address of Communication Manager to the value you are using 4. Save the file using File Save 5. Close Notepad

3.5.3. Instructions for reconfiguring SIP Enablement Services servers IP address

First let me stress making a copy of the SIP Enablement Services virtual machine image. It is easy to make a mistake during these changes which will render your SIP Enablement Services unusable. These instructions have been modified (and simplified believe it or not) starting in release 4.00.0003. Please follow them closely. 1. Login to the VMware Linux console window with craft/craft01 credentials. 2. Provision a layered IP address by issuing the following command:
sudo /sbin/ifconfig eth0:1 <new-IP-addr> netmask <new-NetMask> up

where <new-IP-addr> is replaced by the new system IP address, and <new-NetMask> is replaced by the new network mask i. If you get an error response back like SIOCSIFADDR: Invalid argument or other failure indication, check your command line; Keywords like netmask and up are significant. 3. Open the web based OA&M interface for SIP Enablement Services by using a browser and navigating to http://192.168.17.130/admin 4. Login to the web based OA&M interface (http://192.168.17.130/admin) as craft/craft01 5. Open the Administration interface 6. Select the Hosts link from the menu on the left 7. Select List Hosts 8. Click on Edit for the existing Host (192.168.17.130) 9. Change the Host IP Address* to the <new-IP-addr> 10. Click on Update at the bottom of the page 11. Select the Server Configuration link from the menu on the left 12. Select the System Properties link from the displayed page. 13. Modify the SIP License Host* field from 192.168.17.130 to <new-IP-addr> 14. Click Update and then OK to confirm the change.
Reviewed: 12/16/2008 Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved. 10 of 19

15. If you are using a Communication Manager in conjunction with the SIP Enablement Services, you must change the Communication Manager Servers address that corresponds to Communication Manager (192.168.17.129) to the <new-IP-addr-of-CM> using the edit media server functionality. i. Click on Communication Manager Servers ii. Click on List Media Servers iii. Click on Edit on the row for cmsim iv. Change the SIP Trunk IP Address and the Media Server Admin Address to the appropriate IP address for CM. Note: Check this IP address twice before continuing, it is possible to setup a loopback to the SIP Enablement Services server, if you use the SIP Enablement Services servers IP address here and really confuse yourself (and others). v. Click the Update button at the bottom of the page in the right panel. 16. Run the newIP script to reconfigure /etc/hosts and /etc/sysconfig/network-scripts/ifcfgeth0 by running:
sudo /root/bin/newIP <hostIP> <new-networkMASK> <Gateway> <DNServer>

Verify the changes by looking at /etc/hosts /etc/sysconfig/network-scripts/ifcfg-eth0 and observing the new IP information for sessim.

17. Use a Linux command window (still logged in as craft/craft01) and issue the command: initial_setup 18. Review the information in the IP Network Configuration window; i. Leave the DNS Domain Name set to avaya.com ii. Tab or use the down arrow key till OK is highlighted and hit Enter on the keyboard. 19. On the Redundancy Configuration window: i. Leave the default choice of Simplex selected, tab until OK is highlighted and hit Enter on the keyboard. 20. Enter Finish 21. Enter y to the Stop watchdog now? (y/n) [y] prompt. 22. Enter n to the Do you wish to re-initialize SES Database? (y/n) [n] prompt. 23. Enter y to the Start SES Services now (y/n) [y] prompt. 24. Go to the system settings panel in VMWare for the SIP Enablement Services virtual machine and change the Ethernet interface to be bridged i. Right click on the SES tab in the virtual machines window ii. Choose Settings iii. Click on Ethernet iv. Set the Network Connection to Bridged 25. Reboot the server using the reboot command from a Linux prompt.

Reviewed: 12/16/2008

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

11 of 19

26. Shutdown and restart any SIP Softphones, change their settings to reference the new IP address for the SIP Enablement Services server. 27. If you are using Communication Manager in conjunction with the SIP Enablement Services server, Communication Manager provisioning changes are required. Use the system access terminal (SAT) provisioning interface to perform the following steps: i. Busy out signaling group 1 via the busyout signaling-group 1 command. ii. Change the IP address of sessim via the change node-names IP command. iii. Release the signaling group from the busyout state via the command release signaling-group 1 command. iv. Save the translations by issuing a save translations command.

In previous IPCoDE releases the service state of the SIP trunk between Communication Manager and the SIP Enablement Services server was an issue. This appears to be fixed. If not follow these instructions to drive it into service. Commonly it appears that when stopping and starting SIP Enablement Services or Communication Manager servers, the Communication Manager to SIP Enablement Services signaling link winds up in an out-of-service condition. Remedy this by using the busyout signaling-group X and release signaling-group X commands at the system access terminal. Check the status using the status signaling-group 1 and status trunk 5 commands. You can also validate Communication Manager to SIP Enablement Services connectivity using the Test-Link link on the List Media Servers web page of SIP Enablement Services administration user interface. Additionally, when changing IP address of SIP Enablement Services you must stop (exit) and restart the SIP Softphone.

3.6. Settings for IP Phone

Note that the settings here are for a corporate LAN setup where the subnet is 135.8.117.xxx, and a subnet mask of 255.255.254.0. The Call Servers (Communication Manager) IP address was 135.8.117.123, and the Router must be set to the NIC on the PC for the configuration to work. Telephone configuration Telephone: Call Server: Call Server Port: Router: Set to NIC on PC Mask: File Server: 802.10:
Reviewed: 12/16/2008

Private LAN 192.168.17.20 192.168.17.129 1719 192.168.17.10 255.255.255.0 0.0.0.0 Auto

Corporate LAN 135.8.117.125 135.8.117.123 1719 135.8.116.77 255.255.254.0 0.0.0.0 Auto

12 of 19

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

VLAN ID: VLAN Test:

0 60

0 -

Reviewed: 12/16/2008

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

13 of 19

4. Additional References
None

Reviewed: 12/16/2008

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

14 of 19

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 this document along with the full title name and filename, located in the lower right corner, directly to the Avaya Solution & Interoperability Test Lab at interoplabnotes@list.avaya.com

Reviewed: 12/16/2008

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

15 of 19

Appendix A
This appendix contains screen shots and written information from a working private LAN configuration setup.
IP Station Configuration IP Address 192.168.17.20 Call Server: 192.168.17.129 Call Server Port 1719 Router: 192.168.17.222 (VMware host PC address) Subnet Mask: 255.255.255.0 File Server: 0.0.0.0 802.1Q=off

Application PC Configuration IP address 192.168.17.10 Subnet Mask 255.255.255.0 Default Gateway 192.168.17.222 (VMware host PC address)

Host PC configuration

Reviewed: 12/16/2008

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

16 of 19

VMNET 1 Adaptor

VMware network adaptor for CM virtual machine

Reviewed: 12/16/2008

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

17 of 19

From VMware Edit--> Virtual Network Settings ...

Reviewed: 12/16/2008

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

18 of 19

Click on the ">" button on the VMware Network Adapter VMnet1 row.

Reviewed: 12/16/2008

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

19 of 19