Getting port down events when the admin status is down

Products

• VMware Smart Assurance

Issue/Introduction

This article explains the workarouind for following symptoms observed in Smarts.

• 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

  
  
  

Environment

SMARTS - 10.1.x

SMARTS DM -2.x

Cause

A problem with history table handling.

Resolution

• 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:

• 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.