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

VMware Smart Assurance SMARTS: During device discovery processor and memory instances get deleted on HostResrcs driver probe  (74510)

Last Updated: 1/13/2020Categories: TroubleshootingTotal Views: 5035Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Here is an example, where it is observed that the Processor and Memory instances are being deleted post creation during the device discovery.

Debug enabled domain log has below entries:
[August 9, 2019 10:13:21 AM GMT+01:00 +537ms] t@1583335168 Discovery #1
ASL_MSG-*-ASLP-discovery/ic-cisco-router-crs-health.asl: discovery/ic-cisco-router-crs-health.asl: CREATE CPU: lbg-XXX
[August 9, 2019 10:13:21 AM GMT+01:00 +730ms] t@1583335168 Discovery #1
ASL_MSG-*-ASLP-discovery/ic-cisco-router-crs-health.asl: discovery/ic-cisco-router-crs-health.asl.1.3.6.1.4.1.9.9.221.1.1.1.1.3 [7000.1] = 50726F6XXX73736F72
[August 9, 2019 10:13:23 AM GMT+01:00 +492ms] t@1583335168 Discovery #1
AD_MSG-*-AD_LOG-at 'ProbeClosure t@1583335168', while discovering 'lbg-XXX', invoking HostResrcs-Probe
[August 9, 2019 10:13:23 AM GMT+01:00 +774ms] t@1583335168 Discovery #1
DSCV-W-DELETE_COMPONENT-'PSR-lbg-XXX/7' is no longer found on 'lbg-XXX'. It is removed from topology
[August 9, 2019 10:13:24 AM GMT+01:00 +466ms] t@1583335168 Discovery #1
ASL_MSG-*-ASLP-discovery/ic-hostresources-arista-mib2-other.asl: discovery/ic-hostresources-arista-mib2-other.asl: HOST_OS: lbg-XXX
[August 9, 2019 10:13:24 AM GMT+01:00 +466ms] t@1583335168 Discovery #1
ASL_MSG-*-ASLP-discovery/ic-hostresources-arista-mib2-other.asl:    .1.3.6.1.2.1.1.1 [0] = <Device OS details>
[August 9, 2019 10:13:24 AM GMT+01:00 +470ms] t@1583335168 Discovery #1
DSCV-W-DELETE_COMPONENT-'MEM-lbg-XXX/7000.1 [Processor]' is no longer found on 'lbg-XXX'. It is removed from topology

Cause

Below field certification was deployed on prior Smarts installation 9.2.x:

#Cisco 4431 ISR
.1.3.6.1.4.1.9.1.1935 {
TYPE = Router
VENDOR = Cisco
MODEL = CISCO-4431-ISR
CERTIFICATION = TEMPLATE
CONT = Cisco-Router-Entity
HOSTRESRCS = Arista-MIB2
NEIGHBOR = Cisco-Cdp
HEALTH = Cisco-Router-CRS-EntSensor
VLAN = Cisco-CVI-Vlan
INSTRUMENTATION:
Card-Fault                         = CiscoEntityFRU
Environment                        = CiscoEntityFRU:DeviceID
CPU/Memory                         = CiscoRouter:DeviceID
Interface-Fault                    = MIB2
Interface-Performance              = CiscoRouter
Interface-Ethernet-Performance     = CiscoRouter_Ethernet
}

Post upgrade to the Smarts IP version 9.5.1 patch 1, the device official certification doesn't have the entry HOSTRESRCS = Arista-MIB2. Earlier field certification has been commented out.

A reloadoid was performed on the domain successfully with below command:
sm_tpmgr -s <Incharge Domain> --reloadoid

However it is observed that the HostResrcs driver (ic-hostresources-arista-mib2-other.asl) is still invoked during device discovery.

The above reloadoid command does not clear the GA_SelectiveDriver entries on the IP domain which is responsible to run the HostResrcs Probe.

Impact / Risks

Processor and Memory instances get deleted during device discovery

Resolution

The HostResrcs-Probe is run via GA_SelectiveDriver::HostResrcs-Probe which selects based on certification. In order to clear the entry of HostResrcs-Probe from the GA_SelectiveDriver in IP domain post making changes to the certification, follow the below steps:

1. Verify that the selector pattern does not include the device OID (.1.3.6.1.4.1.9.1.1935 in this example) mapped with any HostResrcs driver with the below:

./dmctl -s <IP Domain Name> get GA_SelectiveDriver::HostResrcs-Probe

2. If it is present, remove the same using the below command:

./dmctl -s <IP Domain Name> invoke GA_SelectiveDriver::HostResrcs-Probe removeSelector .1.3.6.1.4.1.9.1.1935 | tee

3. Rediscover the device

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
•
[解決済み] UAG-4037：UAG を Hyper-V 上に展開する際、deployentOptions パラメータが適用されない (2961505)

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 Smart Assurance

Related Versions:

VMware Smart Assurance - SMARTS

Take Our Survey

Support Assistant