Smarts IP: Discovery is failing with "'ASNM-E-ASNMP_SEND_RECEIVE_ERROR-ASNMP request failure: Error when sending or receiving SNMP data for Host 'X.X.X.X'(Maybe bad credentials)" error
search cancel

Smarts IP: Discovery is failing with "'ASNM-E-ASNMP_SEND_RECEIVE_ERROR-ASNMP request failure: Error when sending or receiving SNMP data for Host 'X.X.X.X'(Maybe bad credentials)" error

book

Article ID: 304026

calendar_today

Updated On:

Products

VMware

Issue/Introduction

Symptoms:


Smarts IP discovery is failing
 

Smarts IP discovery is failing with the following error:

ASNM-E-ASNMP_SEND_RECEIVE_ERROR-ASNMP request failure: Error when sending or receiving SNMP data for Host X.X.XX' (Maybe bad credentials).


Receive "Too Big" Error from ifAlias OID from SNMP Dump/Packet Capture of device in Smarts IP

Cannot discover a device in Smarts IP through SNMP v1 because it fails with ASNM-E-ASNMP_SEND_RECEIVE_ERROR-ASNMP request failure error.

Environment

VMware Smart Assurance - SMARTS

Resolution

If you encounter this issue in your environment, you can work around the issue by setting the maxOIDsPerPacketForASNMP parameter with the following DMCTL command (see Note statement):

invoke ICF_TopologyManager::ICF-TopologyManager insertParameter maxOIDsPerPacketForASNMP 5

Also from Cisco  documentation:

"Cisco IOS XR statistics infrastructure maintains a cache of statistics for all interfaces. This cache is updated every 30 seconds. Use the 'snmp-server ifmib stats cache' command to enable the IF-MIB to retrieve these cached statistics rather than real-time statistics. Accessing cached statistics is less CPU-intensive than accessing real-time statistics."  see link in notes


Additional Information

The maxOIDsPerPacketForASNMP parameter is applicable only for the following OIDs:

OID_IP_FORWARDING          = ".1.3.6.1.2.1.4.1.0";
OID_INTF_DESCR             = ".1.3.6.1.2.1.2.2.1.2";
OID_INTF_TYPE              = ".1.3.6.1.2.1.2.2.1.3";
OID_INTF_MTU               = ".1.3.6.1.2.1.2.2.1.4";
OID_INTF_SPEED             = ".1.3.6.1.2.1.2.2.1.5";
OID_INTF_PHYS_ADDRESS      = ".1.3.6.1.2.1.2.2.1.6";
OID_INTF_STATUS            = ".1.3.6.1.2.1.2.2.1.7";
OID_IP_AD_ENT_ADDR         = ".1.3.6.1.2.1.4.20.1.1";
OID_IP_AD_ENT_INDEX        = ".1.3.6.1.2.1.4.20.1.2";
OID_IP_AD_ENT_NETMASK      = ".1.3.6.1.2.1.4.20.1.3";
OID_INTF_NAME              = ".1.3.6.1.2.1.31.1.1.1.1";
OID_INTF_HC_IN_OCTETS      = ".1.3.6.1.2.1.31.1.1.1.6";
OID_INTF_HIGH_SPEED        = ".1.3.6.1.2.1.31.1.1.1.15";
OID_INTF_ALIAS             = ".1.3.6.1.2.1.31.1.1.1.18";
OID_CIP_ADDR_PREFIX_ORIGIN = ".1.3.6.1.4.1.9.10.86.1.1.1.1.5";

The rest of the OIDs will be discovered with maximum number of varbinds, and the discovery pattern will be followed as normal. Configuring a single OID to be sent in a PDU will cause a lot of overhead, and there will be some trade-off with discovery performance.The default setting in tpmgr-param.conf for maxOIDsPerPacketForASNMP is 19. Therefore, you may be able to configure the above higher than 5, but this level is already tested locally has been proven to work.

Cisco link: http://www.cisco.com/c/en/us/td/docs/routers/xr12000/software/xr12k_r4-2/system_management/command/reference/b_sysman_cr42xr12k/b_sysman_cr42xr12k_chapter_01110.html#wp2214305559