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

VoyenceControl: How do I update the IP Address of a Device Server in VoyenceControl? (325100)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 8087Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

How do I update the IP Address of a Device Server in VoyenceControl?

The Application Server is unable to communicate with a Device Server.

Resolution

To update the IP Address of a Device Server you will need to update the infrastructure database, delete a cache file, and restart a few services:

On the Application Server, change directory to $VOYENCE_HOME/cgi-bin.

Source the /etc/voyence.conf file:

source /etc/voyence.conf

Output the infrastructure database to a file with the following command:

./cflist.cgi > output.txt

Open the output.txt file for editing.

Every Device Server has a POP line entry in the infrastructure database.  This line contains the IP Address that will need to be updated. Locate the POP entry line for your Device Server, below is an example:

POP 1000 "voyence-ds" NetList= RsrcList= DevList=1001,1002,1003 EmsList= : ADDR="192.168.1.12" AGE_DAYS=730 CLEANUP_DAYS=90 AD_ENABLE=0 AD_ARPCACHE=0 AD_DFLTROUTE=0 AD_AUTO_RESOURCE=0 AD_DEFAULT_POLL=0 SNMP_TIMEOUT=500 SNMP_RETRY=3 CM_DEBUGSESSION=1 SORTCONFIG=1 CM_MAXMAINTASKS=20 CM_PULLTIMER=1200 MAX_COMM_ATTEMPTS="5" AD_BATCHSIZE=50 AD_NUMHOP=10 RECORDVER="1.0"

The value that you need to update is the value for the ADDR attribute. Set it to your new IP Address.

Save your changes and exit.

Write your changes to the infrastructure database with the following command:

./cfwrite.cgi < output.txt

Delete the $VOYENCE_HOME/data/.rhttps file on both the Application Server and the Device Server.

Restart the apache service on both the Application Server and the Device Server with the following command:

/etc/init.d/httpd restart

Restart the voyence service on the Application Server and the Device Server with the following command:

/etc/init.d/voyence restart

Your Application Server and Device Server should be communicating with each other successfully now.

Related Information

These steps assume you have correctly and appropriately modified the IP Address of the Device Server ahead of time with respect to the operation system's expectations.  This includes modification of the /etc/hosts file or any other.

The $VOYENCE_HOME variable is a reference to the install directory of VoyenceControl.  By default this is /opt/voyence.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - NCM

Take Our Survey

Support Assistant