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: Getting port down events when the admin status is down (518157)

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

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The user is currently addressing an existing issue of Interface/Port Down alarms before sending them to their console.
They see the following notifications below:

ICS_Notification::NOTIFICATION-Port_PORT-aaa-bbb.ccc.ddd.com/444_Down
ICS_Notification::NOTIFICATION-Port_PORT-aaa-bbb.ccc.ddd.com/555_Down

User was informed that these alarms should not be occurring because the interfaces were Admin down.  User reviewed the SNMP and physical interfaces were Admin down and the sub-interfaces were lowerLayerDown.
However, when inspected from the Smarts console, the device in question did not have any discovered relationship between the physiccal interfacce and the sub-interface.
User verified the Juniper device does support the MIB and the data appeared to be correct.
When turned on debug and rediscover the device, we can see that the ic-ifmib-stack.asl was being called and returned valid data:

December 13, 2017 11:14:25 PM GMT+00:00 +662ms 1951114 3389994752 ALWAYS Discovery #10 ASL_MSG-ASLP discovery/ic-ifmib-stack.asl: discovery/ic-ifmib-stack.asl: MIB2_IFSTACK: aaa-bbb.ccc.ddd.com
December 13, 2017 11:14:25 PM GMT+00:00 +662ms 1951115 3389994752 ALWAYS Discovery #10 ASL_MSG-ASLP discovery/ic-ifmib-stack.asl: .1.3.6.1.2.1.31.1.2.1.3.[444.222] = 1
December 13, 2017 11:14:25 PM GMT+00:00 +663ms 1951116 3389994752 ALWAYS Discovery #10 ASL_MSG-ASLP discovery/ic-ifmib-stack.asl: discovery/ic-ifmib-stack.asl: MIB2_IFSTACK: aaa-bbb.ccc.ddd.com
December 13, 2017 11:14:25 PM GMT+00:00 +663ms 1951117 3389994752 ALWAYS Discovery #10 ASL_MSG-ASLP discovery/ic-ifmib-stack.asl: .1.3.6.1.2.1.31.1.2.1.3.[555.333] = 1

The correct behavior should be that if the physical interface is admin down, the sub-interface should not be alarming, but it is.
User set the EnableMIB2PortDiscovery flag to TRUE.  Initial discovery discovers the correct interface/port relationship.  However, after the second and so on discovery, the physical port/interface is removed.

Cause

A problem with history table handling

Resolution

Issue is addressed in the IP 9.5.0.4 version of the ic-juniper-mib-port.asl

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