Loading...
Loading...
If the IP address range is not part of subnet 192.168.100.113/27, validation of the upgrade using the ACM UI fails with an alert similar to the following: [ERROR] IP Address: “172.16.100.101” is not part of subnet 192.168.100.113/27. Please provide some other unused ip in file /data01/tmp/patch/ip_details.properties. Make sure both IP and Gateway are same in that file. Alternatively, an upgrade precheck performed using the RUCK utility may show the following message:
During an Integration Data Protection Appliance upgrade, the Appliance Configuration Manager component is redeployed, and data will be copied from the old version of this VM to the new. The newly created ACM is assigned a temporary IP (192.168.100.113 by default) on an isolated internal network to allow both VMs to run simultaneously and transfer data between them without conflict. If this IP (192.168.100.113) is unavailable, or the isolated internal IP range has been modified to avoid collision with an external network, the upgrade fails. Checks during initial upgrade validation and RUCK have been implemented to reduce the chances of this occurring.
NOTE: The resolution described in this document may only be performed after an upgrade validation has been attempted in the Appliance Configuration Manager UI. If only RUCK is run prior to validation, the files recommended for modification will not yet exist, therefore if you see this on a RUCK precheck report do not perform any actions since this will only be applied during upgrade, this is an alert for RPS to advise the customer but if support is needed during upgrade below steps must be followed. An alternative temporary IP must be provided, and added to the "/data01/tmp/patch/ip_details.properties" file on the ACM. In the example shown below, the Integration Data Protection Appliance internal private network range had been moved from 192.168.100.113/27 to 172.16.100.113/27. To identify the correct IP to use run the following command on the ACM: ifconfig Note the IP listed for eth0 and use the first three octet. For example, if the IP for eth0 is 10.1.2.100, you would then use 10.1.2.113 as the IP for the ip_details.propreties file. See more Info below. The appropriate IP is added to the "ip_details.properties" file. File "/data01/tmp/patch/ip_details.properties" Before Changes idpa-acm:~ # cat /data01/tmp/patch/ip_details.properties acm_temp_private_ip=192.168.100.113 netmask=255.255.255.224 gateway=192.168.100.113 File "/data01/tmp/patch/ip_details.properties" After Changes idpa-acm:~ # cat /data01/tmp/patch/ip_details.properties acm_temp_private_ip=172.16.100.113 netmask=255.255.255.224 gateway=172.16.100.113 Once an appropriate IP address has been provided in this file, validation should be run again and complete as intended.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.