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 IP: Discovery Errors when ContextMapping and ContextName are different (517095)

Last Updated: 12/17/2018Categories: TroubleshootingTotal Views: 4621Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

When performing a discovery and the discovery for the device failed with the following message:

[07-Nov-2017 01:43:42 PM EST +253ms] t@920540928 Discovery #26
ASL_MSG-*-ASLP-discovery/ic-cisco-find-context.asl: discovery/ic-cisco-find-context.asl: Start driver to get:management context data

[07-Nov-2017 01:44:03 PM EST +276ms] t@920540928 Discovery #26
SNMP-E-AGENTERRORSTATS-Below message for SNMP agent at 'aaa.bbb.ccc.ddd:xxx', was suppressed 1 times since 05-Nov-2017 09:47:40 AM EST
SWFE-ETIMEOUT-GET_NEXT request timed out for Agent : aaa.bbb.ccc.ddd, OID: .1.3.6.1.2.1.4.20.1.2
SNMP-ERESPONSE-No response from aaa.bbb.ccc.ddd, port xxx
SNMP-ETIMEOUT-Timed out; in file "/work/redcurrent/DMT-9.4.2.0/10/smarts/snmp/lib/SNMP_RequestsSender.c" at line 1337

[07-Nov-2017 01:44:03 PM EST +277ms] t@920540928 Discovery #26
ASL_MSG-*-ASLP-discovery/ic-cisco-context-data.asl: discovery/ic-cisco-context-data.aslCurrent Context Name: <context name>

Tcp ping would time out.  If as in this situation there is no data, then SNMP agent should return NoSuchInstance reply instead of simply timing out which is not a valid response and hence the discovery error.

Cause

Customer have configured a vrf "<vrf name>" with the context "<context name>" and these information are populated via the below oids.

{10, ".1.3.6.1.6.3.18.1.1.1.5"} #snmpCommunityContextName
{20, ".1.3.6.1.4.1.9.9.468.1.1.1.2"} #ciscoContextMapping

The reason to include and read the ciscoContextMappingOID (i.e .1.3.6.1.4.1.9.9.468.1.1.1.2) is because of implementing a strategy on managing a Cisco Nexus switch with multiple VRFs using SNMPv3.
Previously with SNMPv2, one can use the VDC contexts to map to each VRF.  This would populate the SNMP-COMMUNITY-MIB::snmpCommunityContextName (.1.3.6.1.6.3.18.1.1.1.5) OID.  Smarts would query this OID when discovering the device and then use the <community>@<context> syntax to discover and aggregate the results.  However, when the VDC/VRF mapping is removed (a Cisco SNMPv2 command), the SNMP-COMMUNITY-MIB::snmpCommunityContextName OID is no longer populated.  This results in only the default VRF being discovered.
An option to achieve this is to map a SNMPv3 security context to a VRF.  This means that Smarts would have to be modified to discover all the security context on the Nexus switch.  As per recommnedation from Cisco, we can use "CISCO-CONTEXT-MAPPING-MIB" to discover the context which should populated for both SNMPv2c and SNMPv3.
To do this, Smarts discovery included a logic to walk both the "snmpCommunityContextName" and "ciscoContextMapping" and add all the context information to a tables and use it to walk the context for information.
The problem is, if there are overlapping details, the information would get overridden in the table and thus retaining only unique entries.  Thus a code change was made so when the context and VRF name are different, Smarts would seem them as two different context and hence the issue with discovery in this case.

Resolution

Provided customer a work around that will be included in future patch. Estimated for Q2 in 2018.

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 - SMARTS

Take Our Survey

Support Assistant