How to associate a VLAN in the ASP Management and VM Network to match the Avaya MGP (2025)

Description:

In anticipation of an upgrade to CM 10.2, we planned to swap out an LSP from CM 8 to CM 10.2 using the same ip addresses. After the swap out, both the AVP and CM IP address were not reachable from the media-gateway.

After some troubleshooting, we noticed the media-gateway was not on the default vlan of 1 but instead on vlan 205. This vlan mismatch needed to be resolved and the simplest way was to re-configure the ASP host and virtual machines to be on vlan 205. The following are steps show how to do this.

Steps:

To verify that the media-gateway is configured for a vlan, log into the CLI of the gateway and do a "show run"

The following lines of code indicate that the vlan of the primary interface (the IP address of the system) is set to vlan 205:

set vlan 205 name "V205"

set port vlan 205 10/3

set port classification 10/3 regular

set port vlan 205 10/4

set port classification 10/4 regular

!

interface Vlan 1

 exit

!

interface Vlan 205

 icc-vlan

 ip address 192.168.5.20    255.255.255.0 

 pmi

 exit

What this means is that for the ASP and any virtual machines on the ASP will need to be configured for vlan 205 if the gateway will communicate with the ASP and it's virtual devices.

To change the vlans on the ASP, connect directly to the services port of the s8300e blade using the 192.11.13.5/30 ip address schema. The ip address of the services port is 192.11.13.6 and the netmask is 255.255.255.252.

You will need to change the Management Network along with the VM Network.

Log into the web interface of the ASP, go to vSwitch0 and click on the pencil for the Management Network - as you can see, the VLAN ID for both are set to the default of 1:

Change the VLAN ID to the appropriate VLAN in this case from 1 to 205:

Then do the same on the VM Network:

Both VLANs for the VM Network and Management Network should now be on the modified VLAN:

You may need to reboot the AVP, but make sure to check that you can ping the AVP and CM ip addresses from the gateway.

Manufacturer Release notes:

Disclaimer: intlx Solutions Knowledge Base

The information contained in this knowledge base ("Content") is provided for informational purposes only and is intended to be a general resource. intlx Solutions does not guarantee the accuracy, completeness, or timeliness of the Content.

Use at Your Own Risk: By accessing and using the Content, you agree that you do so at your own risk. intlx Solutions assumes no responsibility for any errors or omissions in the Content, nor for any damages or losses you may suffer arising out of or related to the use of the Content.

Current Customers: If you are a current intlx Solutions customer and have questions or require further clarification on any information presented here, please do not hesitate to contact our support team directly. They are available to assist you and ensure you have the most up-to-date information specific to your needs.

Not a Customer? If you are not currently an intlx Solutions customer but are interested in learning more about our solutions and how we can help your business, please click here. We look forward to the opportunity to discuss your needs and explore how a partnership with intlx Solutions can benefit you.

Thank you for your understanding.