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

VMware Smart Assurance NCM: Cisco Nexus 5k series devices pull-all or pull hardware job shows complete, but there is no configuration information on the GUI (513339)

Last Updated: 8/26/2020Categories: TroubleshootingTotal Views: 4119Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The Cisco Nexus 5k devices does discover and appears to complete a pull-all or pull hardware, but does not load any configuration information in the GUI. In reviewing the commmgr and session logs it appears that all communication completed successfully and no indication of a problem. Then NCM tries to parse the data and insert it into the PostgreSLQ Control Database (controldb), but it fails when the parser encounters the following error in the $VOYENCE_HOME/ncmcore/logs/powerup.log file:

Powerup.log:

DEBUG [com.powerup.configmgr.server.services.repository.impl.DeviceStateXMLMarshaller] (http-apr-8881-exec-5) Unmarshalling config unit of type - PhysicalHardware
ERROR [com.powerup.service.marshal.castor.CastorObjectMarshaller] (http-apr-8881-exec-5) CastorObjectMarshaller.fromXML
org.exolab.castor.xml.MarshalException: element "HardwareElement" occurs more than once. (parent class: com.powerup.configmgr.common.domain.PhysicalHardware)
Caused by: ValidationException: element "HardwareElement" occurs more than once. (parent class: com.powerup.configmgr.common.domain.PhysicalHardware)
location: /PhysicalHardware/HardwareElement

Daemon.log doesn't show any xml parsing error:

<Message>
<![CDATA[
System Properties pull complete
]]>
</Message></Result><Result config-unit-type="Identity" status="1" error-code="0" action-id="abc000"><Name>Identity</Name>
<Message>
<![CDATA[
Identity pull for <device name> complete
]]>
</Message></Result><Result config-unit-type="PhysicalHardware" status="1" error-code="0" action-id="abc000"><Name>PhysicalHardware</Name>
<Message>
<![CDATA[
PhysicalHardware data changed!!!
]]>

Cause

Device has extra hardware details causing NCM DB to fail to parse it.

Resolution

Follow the below steps to implement the workaround:
1) Log into the Device Server or Combination Server with root privileges.
2) Run: source /etc/voyence.conf
3) Navigate to $VOYENCE_HOME/custompackage directory, check if you have cisco/nexus sub directories.
If it doesn't exist, create the folders, so that you have directory structure as $VOYENCE_HOME/custompackage/cisco/nexus/
4) Copy the attached hwinvfuncs.inc file and place it in the $VOYENCE_HOME/custompackage/cisco/nexus/ directory.
5) Restart the services by running: service voyence restart.
6) Clear the device cache.
7) Execute Pull All on the device.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

hwinvfuncs.inc

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:

Related Versions:

VMware Smart Assurance - NCM

Take Our Survey

Support Assistant