BGP cannot discover StackSwitchSystem devices such as the CISCO Cat38xxstack

Products

• VMware Smart Assurance

Issue/Introduction

Those discovering the #CISCO Cat38xxstack  #CISCO Cat38xxstack  .1.3.6.1.4.1.9.1.1745 in 10.1 IP will find that this device discovers as a StackSwitchSystem in IP. However, BGP will not import and discover them.

In addition, Smarts SAM version 10.1.x will show the StackSwitchSystem as a Node.

Environment

VMware Smart Assurance - SMARTS

Cause

• BGP 10.x does not have the Class StackSwitchSystem, so it cannot be added to the topology in BGP until the code change was applied in 10.1.5 
• SAM 10.x does not have the Class StackSwitchSystem, so it cannot be added to the topology in SAM until the code change was applied in 10.1.5

Resolution

Upgrade to Smarts NPM and SAM 10.1.5 or newer version to resolve this issue.

Workaround:

It is strongly recommended to upgrade. See Release Notes.

If an upgrade is not possible at this time: You can revert back to using a field cert for the following device. This would go into the local/conf/discovery/oid2type_Field.conf file of your test domain, and you can check to confirm that the devices discover in IP and BGP as desired.

#CISCO Cat38xxstack  #CISCO Cat38xxstack  
.1.3.6.1.4.1.9.1.1745 
{    
 TYPE = Switch    
 VENDOR = Cisco    
 MODEL = Cat38xxstack    
 CERTIFICATION = TEMPLATE    
 CONT = Cisco-IOSXE-Switch    
 NEIGHBOR = LLDP-CDP    
 HEALTH = Cisco-Router 
 VLAN = Cisco-Membership 

INSTRUMENTATION:    
 Card-Fault    = CiscoEntityFRU    
 Environment   = CiscoEnvMon:DeviceID    
 CPU/Memory    = CiscoRouter:DeviceID    
 Interface-Fault  = MIB2    
 Interface-Performance = CiscoRouter    
 Interface-Ethernet-Performance  = CiscoRouter_Ethernet 
 Port-Fault   = MIB2    
 Port-Performance  = MIB2    
 Port-Ethernet-Performance    = dot3_Ethernet
}
 ./sm_tpmgr -s <AM_domain> --reloadoid