SNMPv3 Devices Not Showing in CA Performance Management (CAPM)

Products

• CA Performance Management - Usage and Administration
• DX NetOps

Issue/Introduction

• Devices are configured properly but still not showing properly in CAPM.
• The device names are showing as IP instead of device name.
• Device type showing as pingable instead of switch, router, etc.

DX NetOps Performance Management Data Aggregator fails to discover device using SNMPv3.

The correct SNMP Profile is in use but it's failing to discover the device.

Environment

All supported DX NetOps Performance Management Data Aggregator releases

Cause

After enabling debug for discovery, the following Warning messages appear in the karaf.log from the DC. This indicates that a bad user name is being passed to the target device.

2018-09-28 12:15:11,300 | INFO  | tory-thread-8172 | IcmpDiscoveryRunner              | mp.collector.IcmpDiscoveryRunner   73 | 197 - com.ca.im.data-collection-manager.icmp.collector - 3.5.0.RELEASE-191 |  | Starting ICMP range discovery for 1 ip addresses

2018-09-28 12:15:11,305 | INFO  | xecutor-thread-2 | IcmpDiscoveryRunner              | mp.collector.IcmpDiscoveryRunner  219 | 197 - com.ca.im.data-collection-manager.icmp.collector - 3.5.0.RELEASE-191 |  | ICMP range discovery complete with 1 responding IPs.

2018-09-28 12:15:11,306 | WARN  | Response Pool.0  | TooBigListener                   | dm.snmp.collector.TooBigListener  279 | 196 - com.ca.im.data-collection-manager.snmp - 3.5.0.RELEASE-191 |  | TooBigListener received non response PDU.  Sending timeout ResponseEvent to original response listener.  Original Response Event:ResponseEvent [source=ReportProcessor, address=<DeviceIP>/161, request=GETNEXT[{contextEngineID=80:00:1f:88:16:7e:1f:8e:7e, contextName=}, requestID=918186017, errorStatus=0, errorIndex=50, VBS[1.3.6.1.2.1.1.3 = Null]], response=REPORT[{contextEngineID=80:00:1f:88:03:cc:16:7e:1f:8e:7e, contextName=}, requestID=0, errorStatus=0, errorIndex=0, VBS[1.3.6.1.6.3.15.1.1.3.0 = 153489]], userObject=SnmpV3Profile [profileId=4740@161, name=Test2, rank=4, authProtocol=MD5, privProtocol=AES128, userName=<encryptedString>

, authPassword=<encryptedString>

, privPassword=<encryptedString>

], error=null], original request:AsyncSnmp4jRequest [request=Snmp4jRequest [target=UserTarget[address=<DeviceIP>/161,version=3,timeout=3000,retries=2,securityLevel=3,securityModel=3,securityName=4740@161,preferredTransports=null, authoritativeEngineID=], pdu=GETNEXT[{contextEngineID=80:00:1f:88:16:7e:1f:8e:7e, contextName=}, requestID=918186017, errorStatus=0, errorIndex=50, VBS[1.3.6.1.2.1.1.3 = Null]]],

    listener=com.ca.im.dm.snmp.collector.SnmpProfileDiscoveryTask@4adcb7f,

    userObject=SnmpV3Profile [profileId=4740@161, name=Test2, rank=4, authProtocol=MD5, privProtocol=AES128, userName=<encryptedString>

, authPassword=<encryptedString>

, privPassword=<encryptedString>

]]

Resolution

Ensure the SNMP Profile used for Discovery contains the correct credentials.

Additional Information

OID Reference for usmStatsUnknownUserNames - 1.3.6.1.6.3.15.1.1.3

The following debug was used to determine the cause. Take these steps to enable the discovery debug on the DC host discovering the device.

1. Navigate to the following directory (default paths shown):
   • /opt/IMDataCollector/apache-karaf-2.4.3/etc
2. Make a backup copy of the original configuration file:
   • cp org.ops4j.pax.logging.cfg org.ops4j.pax.logging.cfg_Orig
3. Edit the org.ops4j.pax.logging.cfg file adding the below entries. If already added to the file ensure they are uncommented to enable them.
4. Save the file which activates the debug. No restarts are needed.

log4j.logger.com.ca.im.dm.snmp.collector.SnmpProfileDiscoveryTask=debug
log4j.logger.com.ca.im.dm.snmp.snmp4j.USMProxy=DEBUG,sift 
log4j.additivity.com.ca.im.dm.snmp.snmp4j.USMProxy=false 
log4j.logger.com.ca.im.dm.snmp.snmp4j.MPv3Proxy=DEBUG,sift 
log4j.additivity.com.ca.im.dm.snmp.snmp4j.MPv3Proxy=false