Aria Suite Lifecycle Manager – Change IP address
Since I am reorganizing my homenetwork, I wanted to move the Aria Products in their own network and created an extra VLAN with another IP subnet. After describing my experience with changing the IP address for Aria Automation and VIDM in a [previous blog], in this blog I will share my experience with changing the IP address of my Aria Suite Lifecycle manager (ASLCM) appliance. The starting situation is as follows:
- ASLCM 8.18 PSPack 4
- Initial deployment started with 8.14.
- DNS Name : vrslcm.infrajedi.local
- IP Addresses : 192.168.1.212
- Certificate : specific certificate, but only with dns names, so no changes are needed.
- Firewall : ASLCM is deployed in the same network as vCenter and the rest of the Aria products, no firewall rules configured.
The new IP will be 172.16.2.212. Firewall is opened (for now) to allow traffic between vCenter and Aria Products so no changed needed for me.
In a large / enterprise environment you may need to:
- update and replace Certificates (if you have IP addresses in the SAN)
- update firewall rules for the new ASLCM IP address.
Changing the IP address of ASLCM again has a different approach as the Aria Automation appliances or VIDM. By default vAPP Options are configured during deployment, but they are only used for changing DNS servers, not for the IP Settings (address, netmask, gateway).
The procedure I followed:
- Shutdown the ASLCM appliance.
- Create a snapshot.
- Change the DNS entry to the new IP address (In Infoblox, Active Directory, whatever you use).
- Change the ASLCM VM portgroup in vCenter.
- Power On the ASLCM VM in vCenter.
- Open the ASLCM VM Console (since SSH is not available after changing the portgroup and the old ip)
- Run the command vami_set_network from the /opt/vmware/share/vami/ directory with the desired settings:
General notation: vami_set_network <interface> (STATICV4|STATICV4+DHCPV6|STATICV4+AUTOV6) <ipv4_addr> <netmask> <gatewayv4>
In my case: /opt/vmware/share/vami/vami_set_network eth0 STATICV4 172.16.2.212 255.255.255.0 172.16.2.1
You can view the IP settings in ASLCM under Settings, System Details:
I did not have the requirement to change the DNS server(s), but as stated above changing the DNS server(s) has a different approach; you have to use the vami_set_dns command from the /opt/vmware/share/vami/ directory AND also change the vApp property vami.DNS.VMware_vRealize_Suite_Life_Cycle_Manager_Appliance
You can check the current DNS settings with the resolvectl command.
That it for this blog. Hope it was useful.
