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

Smarts NCM : Juniper Device Fails to Pull SystemProperties (515699)

Last Updated: 5/29/2020Categories: TroubleshootingTotal Views: 3834Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Juniper Device fails to pull SystemProperties and the following below error is located in the $VOYENCE_HOME/logs/commmgr.log.

Dec 06 14:50:43 -924641536/pull(256653)#4: [01;32mExecuting function "Juniper Router::getSystemProperties"[00m...
Dec 06 14:50:43 -924641536/pull(256653)#5: SNMP-GET(.1.3.6.1.2.1.1.2.0)->1.3.6.1.4.1.2636.1.1.1.2.21
Dec 06 14:50:43 -924641536/pull(256653)#4: DASL: Looking for 1.1.1.2.21 in XML file Juniper/JuniperModels.xml
Dec 06 14:50:43 -924641536/pull(256653)#1: Using Custom Data File /opt/smarts-ncm/custompackage/pkgxml/Juniper/JuniperModels.xml
Dec 06 14:50:43 -924641536/pull(256653)#4: RunTimeContext::getFileData /opt/smarts-ncm/custompackage/pkgxml/Juniper/JuniperModels.xml Fri Dec 1 13:39:23 2017 4804 bytes
Dec 06 14:50:43 -924641536/pull(256653)#4: RESULT: Unable to determine model for Oid '1.1.1.2.21'
Dec 06 14:50:43 -924641536/pull(256653)#4: DASL: Model from XML =
Dec 06 14:50:43 -924641536/pull(256653)#4: RESULT: Could not locate model name for device
Dec 06 14:50:43 -924641536/pull(256653)#4: DASL: stdGetModel: "" in #0

And

Dec 06 16:16:18 -325167360/pull(256679)#1: Error in validating Oid: RTSNMPVar::getDASLValueFromVb: Can't read OID(1.3.6.1.2.1.25.6.3.1.2.1) (syntax:129)   NOSUCHOBJECT/NOSUCHINSTANCE/ENDOFMIBVIEW (TSNOTE) (RTSNMPVar.cpp#640)

Resolution

To resolve the issue do the following:

Log on to Device Server or Combination Server as root.

Copy the hwfuncs.inc file from the $VOYENCE_HOME/package/juniper/ directory to the $VOYENCE_HOME/custompackage/juniper/ directory.

Check and make sure the file ownership and permissions are the same of root/voyence and 440

Edit the $VOYENCE_HOME/custompackage/juniper/hwfuncs.inc file

Go down to the getOsVersion() function which starts on or about line 237

Replace the following code

else{
retVal = sysDescr;
}

with

else {
var<regex> basenameRegex = "JUNOS ([a-zA-Z0-9\\.-]+)*";
basenameRegex = sysDescr;
if (basenameRegex.match)
{ retVal = basenameRegex[1]; }
}

Save and exit the hwfuncs.inc file

Restart services by running "service voyence restart"

Execute Pull system properties on the device.

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