AVP: Unable to change Host and Virtual Machine network parameters using SDM user guide.

Doc ID    SOLN317072
Version:    4.0
Status:    Published
Published date:    16 Jun 2021
Created Date:    23 Oct 2017
Author:   
Bala Venkata Phaneendra Vallabhaneni
 

Details

 S8300/G450. Customer wants to change the IP addresses of AVP,Utility Server and CM from Class B to Class A.

 

Problem Clarification

Facing two issues.

1. Customer is unable to run serverInitialNetworkConfig script on AVP from root folder.

2. Unable to change corporate IP addresses of CM and Utility Server from AVP services port.

 

Cause

  1. serverInitialNetworkConfig scripts is located at /opt/avaya/bin/serverInitialNetworkConfig on AVP but the script is being executed from the / folder due to which it is failing.
  2. Each individual VM network settings should be changed from the respective corporate network subnet, but Customer was trying to do this from service port.

 

 

Solution

  1. Run the full script path /opt/avaya/bin/serverInitialNetworkConfig to execute the AVP host network parameter changes
  2. Connect to each Virtual machine from its existing network subnet and perform the network changes. Network connection .will be lost once the change command is executed and need to re-connect to the VM from the new subnet.
  3. In this case the order of change is AVP (from services port cli), CM (from CM webpage on CM IP subnet) and Utility Server (connect via corporate IP subnet and  run VMware_conf.sh from cli)
In 7.1.x

the script to be used is

initial_conf.sh
 
Example:
Deploying Avaya Aura® Utility Services on Amazon Web Services
Chapter 6
 
Deploying Avaya Aura® Utility Services
P. 33 Configuring the Utility Services OVA using vSphere client
 

Additional Relevant Phrases

Need to change subnet mask for our LSP Need to change Subnet Mask for the CM

Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy