SNMP failure during Spectrum Secure Domain Connector (SDC) discovery using SNMPv3

Products

• CA Spectrum

Issue/Introduction

After deleting a switch and remodeling because of device replacing, the new switch cannot be discovered via SDC. It seems that devices are only reachable via ICMP, but not via SNMPv3, what's not correct. 

Discovery error messages:  

   model does not exist (111.222.333.444)
    model SPC-OCC-10447: Error discovering the device at 111.222.333.444
 
    This device has responded to an ICMP ping request, but not to an SNMP request.
 
    Probable causes for SNMP failure:
        The device may not be responding to SNMP requests. If the device is busy with network traffic, SNMP requests could be ignored.
        Timeout and Retry values could be too low. Increase and try again.
        The selected SNMPv3 profile may be incorrect. SNMP devices will not respond to SNMP requests if the v3 credentials are not valid for the device.
        Check the device for Access Lists. If the device has an Access List, your machine will have to be added to receive SNMP requests.

Cause

Corrupt SNMPv3 cache on the SDC system.

Resolution

For 10.3.0 and below, restart the SDConnector process on the SDC system to clear out the SNMPv3 cache

For 10.3.1 and above, you can do either of the following:

1. Restart the SDConnector process on the SDC system to clear out the SNMPv3 cache

2. Run the Command Line Interface (CLI) 0x10336 update action command on the model handle of the SDC model to flush the SNMPv3 cache on the SDC system:
    a. Find the model handle of the SDC model
    b. Log into the SpectroSERVER system as the user that owns the Spectrum installation
    c. If on Windows, start a bash shell by running "bash -login"
    d. cd to the $SPECROOT/vnmsh directory and enter the following command to start a CLI session:

./connect

    e. Enter the following command to flush the SNMPv3 cache on the SDC system where <MH> is the model handle of the SDC model:

./update action=0x10336 mh=<MH>