Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

"IP already exists in the network" after upgrading to VCSA 6.7 (56434)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 19856Language:
Chinese (Simplified)JapaneseEnglish

11 like this article

Subscribe to get an email
newsletter with new updates

11 people found this helpful Please provide article feedback:

Symptoms

Upgrading vCenter Server Appliance to 6.7 fails.

In the var/log/vmware/upgrade/upgrade-export.log file, you see entries similar to:

2018-06-04T05:06:36.991Z  Stderr: 04/06/2018 05:06:36 [ERROR] Cannot run /sbin/ifup eth0 command. Unknown error. Return code : 256 output: Make sure the interface is down or not assigned any IP
eth0 is DOWN or not assigned an IP. Bringnig eth0 up...
Can not find the manual filename, let us search for the auto filename
Performing duplicate address check for IPv4 address xx.xx.xx.xx
Error: IP already exists in the network

Unable to set the network parameters

2018-06-04T05:06:36.991Z  ERROR: setnet failed : {
"detail": [
{
"id": "install.setnet.set.network.vami",
"translatable": "Error setting network. Details : %(0)s",
"localized": "Error setting network. Details : 04/06/2018 05:06:36 [ERROR] Cannot run /sbin/ifup eth0 command. Unknown error. Return code : 256 output: Make sure the interface is down or not assigned any IP\neth0 is DOWN or n
ot assigned an IP. Bringnig eth0 up...\nCan not find the manual filename, let us search for the auto filename\nPerforming duplicate address check for IPv4 address xx.xx.xx.xx\n\u001b[1;31mError: IP already exists in the network\u001b[0;39
m\n\nUnable to set the network parameters\n",
"args": [
"04/06/2018 05:06:36 [ERROR] Cannot run /sbin/ifup eth0 command. Unknown error. Return code : 256 output: Make sure the interface is down or not assigned any IP\neth0 is DOWN or not assigned an IP. Bringnig eth0 up...\nCa
n not find the manual filename, let us search for the auto filename\nPerforming duplicate address check for IPv4 address xx.xx.xx.xx\n\u001b[1;31mError: IP already exists in the network\u001b[0;39m\n\nUnable to set the network parameters\
n"
]
},
{
"id": "install.setnet.set.network",
"translatable": "Failed to set network",
"localized": "Failed to set network"
}
],
"resolution": null,
"componentKey": "setnet",
"problemId": null
}
. Stderr:
2018-06-04T05:06:37.16Z ERROR apply_networking Command /bin/python /bin/setnet --locale en --statusFile /var/log/vmware/upgrade/setnet_status.json completed with non-zero exit code 1.
2018-06-04T05:06:37.17Z INFO transfer_network Capturing network state after applying source networking.

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This issue occurs when the source VCSA is still shutting down (holding the IP address) and at the same time the target is setting the network.

Resolution

This issue is resolved in vCenter Server Appliance 6.7 Update 1, available at VMware Downloads.

Workaround

To workaround this issue if you do not want to upgrade:

Note: It is mandatory to take a snapshot before performing the steps mentioned above below.

If there are any other issues faced during the upgrade, revert to the snapshot taken, instead of powering on the source VCSA directly.

Take an SSH session to the vCenter Appliance and run these commands:

mv /usr/sbin/shutdown /usr/sbin/shutdown-backup

echo -e '#!/bin/bash\nsystemctl start systemd-networkd\nip link set eth0 down\nip link set eth1 down\n/usr/sbin/shutdown-backup -h now' > /usr/sbin/shutdown
chmod +x /usr/sbin/shutdown

Once these changes are applied proceed with the upgrade.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

Related Versions:

VMware vCenter Server Appliance 6.7.x

Take Our Survey

Support Assistant