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

Changes made to Network settings on the SRM Appliance 8.2/ 8.2.0.1 are not persistent post a reboot. (74796)

Last Updated: 10/27/2020Categories: TroubleshootingTotal Views: 5695Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Any changes made to the network settings on the SRM Appliance for 8.2 and 8.2.0.1, like a DNS or a default gateway change, are not persistent post a reboot of the Appliance and reverts to initial value configured during deployment.

Purpose

Changes cannot be made to the Network settings on the SRM appliance, post the deployment, and overwrites to initial value configured during deployment, post a reboot.

Cause

The appliance takes its network configuration from the OVF environment. This network configuration is applied on every boot. So when you change the network configuration from the SRM Configure UI, in static environment the network configuration from the deployment will be applied on every boot.

Resolution

This has been identified as a known issue on SRM Appliance version 8.2 and 8.2.0.1. The issue has to be set for a fix on SRM Appliance version 8.2.0.2 or later.

Workaround

When deploying OVF type in settings manually rather than coping and pasting from notepad or word document.

Alternative workaround.

The IP address can be set manually as per the photon OS guide.

https://vmware.github.io/photon/assets/files/html/3.0/photon_admin/configuring-network-interfaces.html

Alternative workaround.

Disable the vami_set_network on the SRM Appliance:

Log into the appliance and delete a flag file. This will cause VAOS service to skip setting the ovf network configuration on every boot. This is the preferable way, because it will enable you to modify the network from the DR Config UI. In order VAOS service to skip the network configuration you have to manually delete the "/opt/vmware/etc/vami/flags/vami_setnetwork" file from the appliance and then all network configuration done through the Configuration Service will be preserved.

1. Take a snapshot of the SRM Appliance
2. Remove the file vami_setnetwork with below command
rm /opt/vmware/etc/vami/flags/vami_setnetwork
3. Edit your network configuration from the DR Config VAMI Page

Related Information

This issue has been ported for a fix on SRM Appliance version 8.2.0.2.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

KB
•
Download and Install VMware Fusion (2014097)

KB
•
iOS デバイス向け Workspace ONE GPS 追跡の概要 (50100627)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Site Recovery Manager

Related Versions:

VMware Site Recovery Manager 8.2.x

Take Our Survey

Support Assistant