Dedicated sideband interfaces on NSX Advanced Load Balancer Service Engines use the following configuration parameters. For existing SEs, these parameters can be populated in the /etc/ovf_config file.


All parameters in this file are comma-separated and the file format is slightly different from the YML file used for spinning up new Service Engines. However, the parameters and their respective formats are exactly the same as they are for new Service Engines.

YAML parameters

YAML Parameter





IP address of the dedicated ASM vNIC on the SE (this is NOT the IP address of the ASM)




Comma-separated, static routes to reach the ASM devices. Even /32 routes can be provided.


If there is a single static route, provide the same and ensure the square brackets are matched. Also, if the ASM virtual service IPs are in the same subnet as the dedicated interfaces, provide the gateway as the default gateway for the subnet.

[ asm-vip-network1/mask1 via gateway1, asm-vip-network2/mask2 via gateway2 ] or [ asm-vip-network1/mask1 via gateway1 ]

avi.asm-static-routes.SE: [ via, via]


ID of the dedicated ASM vNIC and is typically 3 on CSP (vNIC0 is management interface, vNIC1 is data-in interface, and vNIC2 is data-out interface)

numeric vNIC ID

avi.asm-vnic-id.SE: '3'


Follow the below-mentioned steps to add a dedicated ASM vNIC on an existing SE CSP service. In this example, vNIC 3 is used which is actually the fourth NIC on the CSP service.

  1. Navigate to Configuration > Services > Action > Power Off to power off the SE service on Cisco CSP.

  2. To add a new vNIC to the SE with desired parameters, navigate to Configuration > Services > Action > Service Edit and click Add vNIC and provide VLAN id, VLAN type, VLAN tagged, network Name, Model, and click Submit.

  3. Navigate to Configuration > Services > Action and select Power On to power on the SE service on Cisco CSP.

To configure on the Service Engine, follow the instructions below using the bash shell:

  • SSH to NSX Advanced Load Balancer SE IP and perform the following steps.

ssh admin@<SE-MGMT-IP&gt bash# bash# sudo su bash# /opt/avi/scripts/ bash# mv /var/run/avi/ovf_properties.saved /home/admin

Move the file and do not copy this file. Edit it to provide the three comma-separated ASM-dedicated NIC related parameters. The file looks like the following:

bash# cat /home/admin/ovf_properties.saved AVICNTRL:, AVICNTRL_AUTHTOKEN: 1403771c- fc59-4d76-89b2-b3c35682b342, avi.default-gw.SE:, avi.asm-ip.SE:, avi.asm-static-routes.SE: [ via, via], avi.asm-vnic-id.SE: '3', avi.mgmt-ip.SE:, ovf_source: CSP, uuid: FCE9B12D-A1B0-4EF3-B922-BDC2A5F8AA11} bash# cp /home/admin/ovf_properties.saved /etc/ovf_config bash# /opt/avi/scripts/
  • Verify that the dedicated vNIC information is applied correctly and the ASM virtual service IPs are reachable through this interface. In this case, the interface eth3 is dedicated ASM interface and it is configured with IP