Network Management

 View Only
  • 1.  SNMP V3 test is broken

    Posted Aug 12, 2019 08:08 AM

    Possible causes:

    1. The device cannot be pinged. 2. SNMP settings/Telnet settings/SSH settings is incorrect. 3. Invalid characters are found. 4. device returns a failure.

    but from host shell no issue found

     

    $ ping -c1 10.0.220.16
    PING 10.0.220.16 (10.0.220.16) 56(84) bytes of data.
    64 bytes from 10.0.220.16: icmp_seq=1 ttl=255 time=0.945 ms
    
    $ snmpget -v3 -u 123 -l authPriv -a MD5 -A 123 -x DES -X 123 10.0.220.16 SNMPv2-MIB::sysDescr.0
    
    SNMPv2-MIB::sysDescr.0 = STRING: HP J8698A Switch 5412zl, revision K.16.02.0026, ROM K.15.30 (/ws/swbuildm/maint_spokane_qaoff/code/build/btm(swbuildm_ma)

     

    Any and all suggestions are welcome.


    #snmp


  • 2.  RE: SNMP V3 test is broken

    Posted Aug 13, 2019 05:04 AM

    Hello,

    What version of IMC are you running? There was an SNMP Template issue in 7.3 E0605P06 and I vaguely recall an issue with SNMPv3 Test in particular that failed on earlier versions, despite it actually working correctly.

    Please make sure you are running the latest version, the issue should be fixed:

    https://h10145.www1.hpe.com/downloads/SoftwareReleases.aspx?ProductNumber=JG747AAE



  • 3.  RE: SNMP V3 test is broken

    Posted Aug 13, 2019 06:08 AM

    Thank you for answer. With v7.3 E0605P06 and v7.3 E0703 issue is present too. I will try downgrade to v7.3 (E0506P09)



  • 4.  RE: SNMP V3 test is broken

    Posted Aug 13, 2019 07:42 AM

     

    If it's not a version issue, please check a Wireshark packet capture during IMC 'Test' with SNMPv3 credentials. That should allow you to see what's going wrong.

    You should expect to see a GET-Request for the OID corresponding to the Hostname, followed by a SET-Request to set the hostname to the device's current hostname (leaving it unchanged - but if this works, SNMP RW should be working).



  • 5.  RE: SNMP V3 test is broken

    Posted Aug 13, 2019 07:57 AM

    in my experience IMC is very picky about the response IP of the SNMPv3 flow.

    Please make sure the switch is responding with the IP it is managed by IMC

    with Procurve:

    snmp-server resp dst

    or

    snmp-ser resp <ip in imc>

    hth