Network Management

 View Only
last person joined: yesterday 

Keep an informative eye on your network with HPE Aruba Networking network management solutions
Expand all | Collapse all

HPE IMC 7.3 and Linux SNMP V3 parameter error

This thread has been viewed 24 times
  • 1.  HPE IMC 7.3 and Linux SNMP V3 parameter error

    Posted Jul 21, 2022 04:21 AM
    Hi All,

    We have a LINUX VM that we would like to monitor using IMC

    I have created the SNMPv3 user on the Linux VM:

    rouser snmp
    createUser snmp SHA "password" AES "password"
    rocommunity public
    trap2sink IP_IMC public

    In IMC, I've added IP and SNMPv3 conf using Priv-AES128 Auth-SHA

    Yet when testing SNMPv3 in IMC, it returns SNMP v3 parameter error.

    Any ideas would be appreciated!



  • 2.  RE: HPE IMC 7.3 and Linux SNMP V3 parameter error

    EMPLOYEE
    Posted Jul 21, 2022 04:49 AM
    Hello there,

    I would advise you to run a Wireshark trace to find where the problem is.
    To be readable you will need to put the passwords in Wireshark to decrypt the trace.

    Regards,

    ------------------------------
    Marina
    HPE
    Sofia
    ------------------------------



  • 3.  RE: HPE IMC 7.3 and Linux SNMP V3 parameter error

    Posted Jul 21, 2022 05:43 AM
    Hi Milenkova,

    Decrypted wireshark trace returns:

    msgAuthenticationParameters: <MISSING>
    msgPrivacyParameters: <MISSING>

    User Datagram Protocol, Src Port: 161, Dst Port: 53810
    Simple Network Management Protocol
    msgVersion: snmpv3 (3)
    msgGlobalData
    msgAuthoritativeEngineID: 80001f8880ed47220e3c86d76200000000
    msgAuthoritativeEngineBoots: 6
    msgAuthoritativeEngineTime: 103570
    msgUserName: dojt_snmp
    msgAuthenticationParameters: <MISSING>
    msgPrivacyParameters: <MISSING>
    msgData: plaintext (0)


  • 4.  RE: HPE IMC 7.3 and Linux SNMP V3 parameter error

    EMPLOYEE
    Posted Jul 21, 2022 06:07 AM
    Hello there,

    Is this output from the snmp get or from the reply?
    Which system is sending with missing parameters?

    If it is the iMC system - , please open a case with support.


    Regards,


    ------------------------------
    Marina
    HPE
    Sofia
    ------------------------------



  • 5.  RE: HPE IMC 7.3 and Linux SNMP V3 parameter error

    Posted Jul 21, 2022 06:14 AM
    Source/Dest as follows:

    257265 1573.717114 IMC LinuxVM SNMP 194 get-request 1.3.6.1.2.1.1.1.0
    257268 1573.719134 LinuxVM IMC SNMP 165 report 1.3.6.1.6.3.15.1.1.5.0
    Frame 257268: 165 bytes on wire (1320 bits), 165 bytes captured (1320 bits) on interface \Device\NPF_{FF504BF9-6F6D-46C8-97D8-44F52131F1DB}, id 0
    Ethernet II, Src: Cisco_ff:fc:a0 (00:08:e3:ff:fc:a0), Dst: Microsof_82:85:04 (00:15:5d:82:85:04)
    Internet Protocol Version 4, Src: Linux, Dst: IMC
    User Datagram Protocol, Src Port: 161, Dst Port: 53810
    Simple Network Management Protocol
    msgVersion: snmpv3 (3)
    msgGlobalData
    msgAuthoritativeEngineID: 80001f8880ed47220e3c86d76200000000
    msgAuthoritativeEngineBoots: 6
    msgAuthoritativeEngineTime: 103886
    msgUserName: dojt_snmp
    msgAuthenticationParameters: <MISSING>
    msgPrivacyParameters: <MISSING>
    msgData: plaintext (0)

    How do we open a case with support when IMC serial number is not recognised by the HPE Enterprise Portal?



  • 6.  RE: HPE IMC 7.3 and Linux SNMP V3 parameter error

    EMPLOYEE
    Posted Jul 21, 2022 06:31 AM
    Hello Steve,

    So far I see : Internet Protocol Version 4, Src: Linux, Dst: IMC.

    I think the problem is on the Linux system.


    Regards,





    ------------------------------
    Marina
    HPE
    Sofia
    ------------------------------



  • 7.  RE: HPE IMC 7.3 and Linux SNMP V3 parameter error

    Posted Jul 21, 2022 07:24 AM
    Thanks Milenkova for the inspection of the trace, I will follow up further with our Linux support vendor.

    Steve


  • 8.  RE: HPE IMC 7.3 and Linux SNMP V3 parameter error

    Posted Jul 25, 2022 11:31 AM
    Hello,

    ello,

    I have also struggled to make SNMPv3 working on Linux.

    First you need to create the V3 user on the linux box using the script "create_user" (at least this is the way it is called on my ubuntu 20.04 LTS, but I don't know about other linux distribution).

    Then you need to reference that user you have created in the snmpd.conf file, along with the objects you want to monitor.

    Finally you must restart the snmpd daemon, so that it is forced to re-read the configuration file.

    That worked for me. Also beware that the agent is READ-ONLY, but it's not an issue for monitoring.

    Best
    Ray