Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

Smarts NCM/VoyenceControl: What is a custompackage change? How do I make a custompackage change? (322789)

Last Updated: 3/29/2011Categories: How toTotal Views: 2349Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Resolution

What is a custompackage change in Smarts Network Configuration Manager (Smarts NCM)/VoyenceControl?
How do I make a custompackage change?

What is a custompackage change?

The Smarts NCM/VoyenceControl device server architecture allows local customizations to device drivers and control/data files in a directory separate from the distribution directory.  This enables customers to create modified versions of these files without altering the files distributed with the product.

By creating copies of the distributed files and making modifications to the copies, customers are insulated from the possibility of having their customizations overwritten during the application of maintenance or future product releases.  This feature is provided through the use of a custompackage directory, which can be searched prior to the device driver package directory distributed with the software. Device drivers or control files found in the custompackage directory take precedence over the same files found in the package directory; if they are absent, the system defaults to using the files from the device driver package directory.

Officially released hot fixes, DSRs, and other driver components will always be installed in the package directory, not in the custompackage directory.

How do I make a custompackage change?

To make a custompackage change, you must duplicate all directory structure and copy the original file you wish to modify under the custompackage directory.

For example:

You need to add a filter to the Cisco IOS Router driver to ignore a particular line when checking synchronization between startup and running configs.  The original file is located at $VOYENCE_HOME/package/pkgxml/CiscoIOSRouter/CiscoIOSRouter.pkg.

Copy or create the file(s) and directory structure from the $VOYENCE_HOME/package directory to the $VOYENCE_HOME/custompackage directory:

mkdir $VOYENCE_HOME/custompackage/pkgxml
mkdir $VOYENCE_HOME/custompackage/pkgxml/CiscoIOSRouter
cp $VOYENCE_HOME/package/pkgxml/CiscoIOSRouter/CiscoIOSRouter.pkg $VOYENCE_HOME/custompackage/pkgxml/CiscoIOSRouter/CiscoIOSRouter.pkg

Make changes to the file under custompackage.

As root, restart the voyence service to recompile the drivers with your changes (not always necessary, but required more often than not).

/etc/init.d/voyence restart

Related Information

More details on custompackage changes can be found in $VOYENCE_HOME/package/customizationREADME.txt
$VOYENCE_HOME refers to the installation directory of VoyenceControl.  By default this is /opt/voyence or C:\Program Files\VoyenceControl.

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