Junos OS

Expand all | Collapse all

SNMPv3 OID

Jump to Best Answer
  • 1.  SNMPv3 OID

     
    Posted 01-24-2018 06:00

    Hi,

     

    I wish to utilise SNMPv3 for monitoring the new Data NEtwork we have. 

     

    It seems rather more complicated than v1 or 2. Does anyone know how to, on the actual box, to view the MIBs that are installed by default and also how to get a full list of objects and OIDs?

     

    Thanks



  • 2.  RE: SNMPv3 OID

     
    Posted 01-24-2018 06:22

    Sorry. Let me re-phrase the question above.

     

    I cannot find the SNMPv3 MIBs. I have the SNMPv2 MIBs from the juniper MIBs site for the version of Junos being used. What I cannot find is WHERE to copy these MIBs onto the Juniper MX240.... Could anyone please let me know where we should load the MIBs too?

     

    Thanks



  • 3.  RE: SNMPv3 OID

     
    Posted 01-24-2018 07:20

    Hi Clive,

     

    We don't have seperate MIB for SNMPv3. You can use the existing MIB for polling purpose. Configuration is shown is below link.

    MIB are loaded in NMS not in MX. In case you want poll from MX, please execute "show snmp mib walk X"

     

    https://kb.juniper.net/InfoCenter/index?page=content&id=KB27284

    https://www.juniper.net/documentation/en_US/junos/topics/concept/snmp-v3-overview-junos-nm.html

    Regards,

    Rahul 



  • 4.  RE: SNMPv3 OID

     
    Posted 01-24-2018 07:54

    Hi rahul,

     

    Yes. I mis-understood the MIBs and realised they were for the PRTG we have.

     

    We have a very basic configuration as below:

     

    set snmp v3 usm local-engine user test-user authentication-sha authentication-key "$9$R1NhKM8LNY4aVbs4JGiH0B1RylKM8dVY1RYgaJDjuOB1SrxNdbwgx7s4JZkq1RESrvW87NVwKvGDji.mcyreLxbwgGjHvWHqP56/reKvxNY2aUDkwsP5TF/9vW8LxdbwgJZjreZUDi.mFn/ApBhclXNdApIcSrvMNdbYaZDikPfzUDO1EhKvoJZDqm"
    set snmp v3 usm local-engine user test-user privacy-aes128 privacy-key "$9$uDOqOcyleW-bsXxNbYgJZ9AtuIEcylLX-tu-VsYoa/CAt1RvWLx7VvMNbY2GUtu01RSrlMWX7cSgoaJDjBIRhevx7VgaZSrZUikTQRhcSvW-ds4oG7NikqPQzSrlevLx7VY2aRh24oJDjP5Q36AOBEKWL36pB1RSyWLx-s2oJGiHm4oCt0OcSwY2oUj"
    set snmp v3 vacm security-to-group security-model usm security-name test-security group test-group
    set snmp v3 vacm access group test-group default-context-prefix security-model usm security-level none read-view test-read
    set snmp v3 target-address test-target address 192.168.50.201
    set snmp v3 target-address test-target target-parameters test-target-parameters
    set snmp v3 target-parameters test-target-parameters parameters message-processing-model v3
    set snmp v3 target-parameters test-target-parameters parameters security-model usm
    set snmp v3 target-parameters test-target-parameters parameters security-level none
    set snmp v3 target-parameters test-target-parameters parameters security-name test-security
    set snmp v3 target-parameters test-target-parameters notify-filter test-filter
    set snmp v3 notify test-notify tag test-tag
    set snmp v3 notify-filter test-filter oid .1 include
    set snmp v3 snmp-community test-community security-name test-security
    set snmp v3 snmp-community test-community tag test-tag
    set snmp view test-view oid .1 include


    And when I use the "run show snmp v3 community" command, I get the following result:

     

    Community                    Security                      Context             Tag             Storage               Status
    index                               name                          name                                     type
    test-community             test-sec                                                test-tag       nonvolatile         active

     

    As a base test, will this work?



  • 5.  RE: SNMPv3 OID

     
    Posted 01-24-2018 07:58

    Hi Clive,

     

    It should work. Hope you're aware about below tool.

     

    https://apps.juniper.net/mib-explorer/

     

    Regards,

    Rahul 



  • 6.  RE: SNMPv3 OID

     
    Posted 01-24-2018 08:06

    Hi Rahul,

     

    Yes. Thank you. I have already downloaded the required MIBs and taken note of the installation order requirements.

     

    I am currently running the latest version of PRTG and letting it complete an automated discovery on the network.

     

    Will let you know how it goes.



  • 7.  RE: SNMPv3 OID

     
    Posted 01-24-2018 09:05

    Hi Rahul,

     

    That did not work. From a traceoptions perspective we get the following (we changed IP to MAC):

     

    Jan 24 17:05:03.313394 snmpd[0] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Jan 24 17:05:03.329971 snmpd[5195] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Jan 24 17:05:03.329991 snmpd[5195] >>> Report-PDU
    Jan 24 17:05:03.330002 snmpd[5195] >>>  Source:      192.168.50.201
    Jan 24 17:05:03.330013 snmpd[5195] >>>  Destination: 192.168.50.200
    Jan 24 17:05:03.330023 snmpd[5195] >>>  Version:     SNMPv3
    Jan 24 17:05:03.330032 snmpd[5195] >>>  Security Parameters:
    Jan 24 17:05:03.330044 snmpd[5195] >>>   SecModel: USM
    Jan 24 17:05:03.330059 snmpd[5195] >>>   EngId: 80 00 0a 4c 03 00 a0 a5 a6 55 d6
    Jan 24 17:05:03.330069 snmpd[5195] >>>   User:
    Jan 24 17:05:03.330081 snmpd[5195] >>>   EngBoots: 1  EngTime: 109634
    Jan 24 17:05:03.330092 snmpd[5195] >>>  Request_id:  0x5195
    Jan 24 17:05:03.330102 snmpd[5195] >>>  Error:       status=0 / vb_index=0
    Jan 24 17:05:03.330118 snmpd[5195] >>>   OID  : usmStatsUnknownEngineIDs.0
    Jan 24 17:05:03.330127 snmpd[5195] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Jan 24 17:05:03.330771 snmpd[0] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Jan 24 17:05:03.330790 snmpd[0] >>> Report-PDU
    Jan 24 17:05:03.330801 snmpd[0] >>>  Source:      192.168.50.201
    Jan 24 17:05:03.330812 snmpd[0] >>>  Destination: 192.168.50.200
    Jan 24 17:05:03.330822 snmpd[0] >>>  Version:     SNMPv3
    Jan 24 17:05:03.330831 snmpd[0] >>>  Security Parameters:
    Jan 24 17:05:03.330841 snmpd[0] >>>   SecModel: USM
    Jan 24 17:05:03.330856 snmpd[0] >>>   EngId: 80 00 0a 4c 03 00 a0 a5 a6 55 d6
    Jan 24 17:05:03.330865 snmpd[0] >>>   User: test
    Jan 24 17:05:03.330877 snmpd[0] >>>   EngBoots: 1  EngTime: 109634
    Jan 24 17:05:03.330887 snmpd[0] >>>  Error:       status=0 / vb_index=0
    Jan 24 17:05:03.330903 snmpd[0] >>>   OID  : usmStatsUnknownUserNames.0
    Jan 24 17:05:03.330912 snmpd[0] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>



  • 8.  RE: SNMPv3 OID

     
    Posted 01-24-2018 10:06

    Hi Clive,

     

    I've tested the below configuration and it's working fine.

     

    [root@TEST ~]# snmpwalk -v3 -u nnmsnmpuser -l AuthNoPriv -a MD5 -A test1234 10.219.36.151 system
    SNMPv2-MIB::sysDescr.0 = STRING: Juniper Networks, Inc. mx480 internet router, kernel JUNOS 15.1R5-S4.2, Build date: 2017-05-24 19:12:20 UTC Copyright (c) 1996-2017 Juniper Networks, Inc.
    SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.2636.1.1.1.2.25
    DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (2628441) 7:18:04.41
    SNMPv2-MIB::sysContact.0 = STRING:
    SNMPv2-MIB::sysName.0 = STRING: jtac-mx480-r2047-re1
    SNMPv2-MIB::sysLocation.0 = STRING:
    SNMPv2-MIB::sysServices.0 = INTEGER: 6

    TEST# show snmp
    v3 {
        usm {
            local-engine {
                user nnmsnmpuser {
                    authentication-md5 {
                        authentication-key "$9$rkGlK8XxdsYoN-VY4aiHO1IcSeNdbaGDwsP5FnCAevM8LNY2aUDkoaFn/A0OX7N-s24aZGjHsYfT3nCAO1Rhev-VwYoJXxjHk.5TRhcSKMXxdw24BIEyev7NVwYoDiTz3t0BTQ9p0BEhylKMxNsYoDjqoajqPfn6p0B1yl8X7bYgMWNb24ZG/CAtBI"; ## SECRET-DATA
                    }
                }
            }
        }
        vacm {
            security-to-group {
                security-model usm {
                    security-name nnmsnmpuser {
                        group snmpgroup;
                    }
                }
            }
            access {
                group snmpgroup {
                    default-context-prefix {
                        security-model usm {
                            security-level authentication {
                                read-view allmibs;
                            }
                        }
                    }
                }
            }
        }
    }
    engine-id {
        use-default-ip-address;
    }
    view allmibs {
        oid .1.3.6.1 include;
        oid .1 include;
    }
    traceoptions {
        file snmpd size 100m;
        flag all;
    }

     

    Regards,

    Rahul

     



  • 9.  RE: SNMPv3 OID

     
    Posted 01-24-2018 10:10

          -v 1|2c|3             specifies SNMP version to use
          -u USER-NAME          set security name (e.g. bert)
          -l LEVEL              set security level (noAuthNoPriv|authNoPriv|authPriv)
          -a PROTOCOL           set authentication protocol (MD5|SHA)
          -A PASSPHRASE         set authentication protocol pass phrase
          -n CONTEXT            set context name (e.g. bridge1)



  • 10.  RE: SNMPv3 OID

     
    Posted 01-25-2018 00:57

    Hi Rahul,

     

    I will give this a go. thank you.

     

     



  • 11.  RE: SNMPv3 OID

     
    Posted 01-25-2018 01:32

    Hi Rahul,

     

    We are using the latest version of PRTG and the Paessler tester. What Monitor system did you use to get this working please?

     

    This has still not worked. Here is the result of the walkthrough and also part of the traceoptions:

     

    25/01/2018 09:00:31 (1 ms) : Device: 192.168.50.200

    25/01/2018 09:00:31 (1 ms) : SNMP V3

    25/01/2018 09:00:31 (1 ms) : Walk snmpwalk -v3 -u test -l AuthNoPriv -a MD5 -A testing123 -n test 192.168.50.200 system

    25/01/2018 09:00:31 (26 ms) : Error: -2007

     

    Jan 25 09:11:46.094166 snmpd[0] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Jan 25 09:11:46.103206 snmpd[1c9e] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Jan 25 09:11:46.103225 snmpd[1c9e] >>> Report-PDU
    Jan 25 09:11:46.103236 snmpd[1c9e] >>>  Source:      192.168.50.201
    Jan 25 09:11:46.103246 snmpd[1c9e] >>>  Destination: 192.168.50.200
    Jan 25 09:11:46.103265 snmpd[1c9e] >>>  Version:     SNMPv3
    Jan 25 09:11:46.103275 snmpd[1c9e] >>>  Security Parameters:
    Jan 25 09:11:46.103283 snmpd[1c9e] >>>   SecModel: USM
    Jan 25 09:11:46.103296 snmpd[1c9e] >>>   EngId: 80 00 0a 4c 01 c3 50 00 02
    Jan 25 09:11:46.103305 snmpd[1c9e] >>>   User:
    Jan 25 09:11:46.103316 snmpd[1c9e] >>>   EngBoots: 1  EngTime: 167637
    Jan 25 09:11:46.103325 snmpd[1c9e] >>>  Request_id:  0x1c9e
    Jan 25 09:11:46.103334 snmpd[1c9e] >>>  Error:       status=0 / vb_index=0
    Jan 25 09:11:46.103349 snmpd[1c9e] >>>   OID  : usmStatsUnknownEngineIDs.0
    Jan 25 09:11:46.103357 snmpd[1c9e] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Jan 25 09:11:46.103983 snmpd[0] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Jan 25 09:11:46.104000 snmpd[0] >>> Report-PDU
    Jan 25 09:11:46.104010 snmpd[0] >>>  Source:      192.168.50.201
    Jan 25 09:11:46.104020 snmpd[0] >>>  Destination: 192.168.50.200
    Jan 25 09:11:46.104029 snmpd[0] >>>  Version:     SNMPv3
    Jan 25 09:11:46.104038 snmpd[0] >>>  Security Parameters:
    Jan 25 09:11:46.104049 snmpd[0] >>>   SecModel: USM
    Jan 25 09:11:46.104062 snmpd[0] >>>   EngId: 80 00 0a 4c 01 c3 50 00 02
    Jan 25 09:11:46.104071 snmpd[0] >>>   User: test
    Jan 25 09:11:46.104081 snmpd[0] >>>   EngBoots: 1  EngTime: 167637
    Jan 25 09:11:46.104091 snmpd[0] >>>  Error:       status=0 / vb_index=0
    Jan 25 09:11:46.104106 snmpd[0] >>>   OID  : usmStatsUnsupportedSecLevels.0
    Jan 25 09:11:46.104114 snmpd[0] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Jan 25 09:11:46.120300 snmpd[b74] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

     

    Thanks

     

     



  • 12.  RE: SNMPv3 OID

     
    Posted 01-25-2018 01:41

    Hi Clive,

     

    I can see you're polling using context test which mean routing-instance test. Can you remove the same and try once?

     

    Walk snmpwalk -v3 -u test -l AuthNoPriv -a MD5 -A testing123 -n test 192.168.50.200 system

     

    Regards,
    Rahul N



  • 13.  RE: SNMPv3 OID

     
    Posted 01-25-2018 02:42

    Hi Rahul,

     

    My apologies. I'm not quite sure I understand. We have simply changed the username to "test". The context is the default and in the poll we have utilised the command as you have suggested.

     

    As I mentioned we are using a DOS implimentation of snmpwalk with all tested on paessler and neither work. We always seem to be getting either Security or authenticaiton problems..... but it is very simple MD5 - Usrname test and key is just testing123 ... not difficult...

     

    Thanks



  • 14.  RE: SNMPv3 OID
    Best Answer

     
    Posted 01-25-2018 02:51

    Hi Clive,

     

    Did you configured the key using below command?

     

    test# set snmp v3 usm local-engine user nnmsnmpuser authentication-md5 authentication-password testing123

     

    Regards,
    Rahul N



  • 15.  RE: SNMPv3 OID

     
    Posted 01-25-2018 02:52

    Hi Rahul,

     

    Interstingly, as noted in a message above, the snmpd log file shows the following:

     

    Jan 25 10:29:40.480985 snmpd[1b31] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Jan 25 10:29:40.481014 snmpd[1b31] >>> Report-PDU
    Jan 25 10:29:40.481025 snmpd[1b31] >>> Source: 192.168.50.69
    Jan 25 10:29:40.481035 snmpd[1b31] >>> Destination: 192.168.50.200
    Jan 25 10:29:40.481044 snmpd[1b31] >>> Version: SNMPv3
    Jan 25 10:29:40.481052 snmpd[1b31] >>> Security Parameters:
    Jan 25 10:29:40.481061 snmpd[1b31] >>> SecModel: USM
    Jan 25 10:29:40.481075 snmpd[1b31] >>> EngId: 80 00 0a 4c 01 c3 50 00 02
    Jan 25 10:29:40.481083 snmpd[1b31] >>> User:
    Jan 25 10:29:40.481095 snmpd[1b31] >>> EngBoots: 1 EngTime: 172312
    Jan 25 10:29:40.481156 snmpd[1b31] >>> Request_id: 0x1b31
    Jan 25 10:29:40.481167 snmpd[1b31] >>> Error: status=0 / vb_index=0
    Jan 25 10:29:40.481188 snmpd[1b31] >>> OID : usmStatsUnknownEngineIDs.0
    Jan 25 10:29:40.481196 snmpd[1b31] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

     

    Note the unknown engine ID.

    In the config we have that set as "set snmp engine-id use-default-ip-address"

     

    What is the default IP address here? We need to use this in the snmpwalk command. Is it the physical interface that the SNMP Server is attached to or something else?

     

    Thanks



  • 16.  RE: SNMPv3 OID

     
    Posted 01-25-2018 02:55

    This is normal message.

     

    [root@JTAC-BNG-SRC ~]# snmpwalk -v3 -u nnmsnmpuser -l AuthNoPriv -a MD5 -A testing123 10.219.36.151 system
    SNMPv2-MIB::sysDescr.0 = STRING: Juniper Networks, Inc. mx480 internet router, kernel JUNOS 13.3R9-S4, Build date: 2016-07-22 23:24:13 UTC Copyright (c) 1996-2016 Juniper Networks, Inc.
    SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.2636.1.1.1.2.25
    DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (1166865) 3:14:28.65
    SNMPv2-MIB::sysContact.0 = STRING:
    SNMPv2-MIB::sysName.0 = STRING: jtac-mx480-r2047-re1
    SNMPv2-MIB::sysLocation.0 = STRING:
    SNMPv2-MIB::sysServices.0 = INTEGER: 6
    [root@JTAC-BNG-SRC ~]#

     

    Jan 25 16:24:36 snmpd[4bec4124] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Jan 25 16:24:36 snmpd[4bec4124] >>> Report-PDU
    Jan 25 16:24:36 snmpd[4bec4124] >>> Source: 10.219.45.218
    Jan 25 16:24:36 snmpd[4bec4124] >>> Destination: 10.219.36.151
    Jan 25 16:24:36 snmpd[4bec4124] >>> Version: SNMPv3
    Jan 25 16:24:36 snmpd[4bec4124] >>> Security Parameters:
    Jan 25 16:24:36 snmpd[4bec4124] >>> SecModel: USM
    Jan 25 16:24:36 snmpd[4bec4124] >>> EngId: 80 00 0a 4c 01 0a db 24 97
    Jan 25 16:24:36 snmpd[4bec4124] >>> User:
    Jan 25 16:24:36 snmpd[4bec4124] >>> EngBoots: 5 EngTime: 11668
    Jan 25 16:24:36 snmpd[4bec4124] >>> Request_id: 0x4bec4124
    Jan 25 16:24:36 snmpd[4bec4124] >>> Error: status=0 / vb_index=0
    Jan 25 16:24:36 snmpd[4bec4124] >>> OID : usmStatsUnknownEngineIDs.0
    Jan 25 16:24:36 snmpd[4bec4124] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Jan 25 16:24:36 snmpd[4bec4123] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Jan 25 16:24:36 snmpd[4bec4123] >>> Get-Next-Request
    Jan 25 16:24:36 snmpd[4bec4123] >>> Source: 10.219.45.218
    Jan 25 16:24:36 snmpd[4bec4123] >>> Destination: 10.219.36.151
    Jan 25 16:24:36 snmpd[4bec4123] >>> Version: SNMPv3
    Jan 25 16:24:36 snmpd[4bec4123] >>> Security Parameters:
    Jan 25 16:24:36 snmpd[4bec4123] >>> SecModel: USM
    Jan 25 16:24:36 snmpd[4bec4123] >>> EngId: 80 00 0a 4c 01 0a db 24 97
    Jan 25 16:24:36 snmpd[4bec4123] >>> User: nnmsnmpuser
    Jan 25 16:24:36 snmpd[4bec4123] >>> EngBoots: 5 EngTime: 11668
    Jan 25 16:24:36 snmpd[4bec4123] >>> Request_id: 0x4bec4123
    Jan 25 16:24:36 snmpd[4bec4123] >>> Error: status=0 / vb_index=0
    Jan 25 16:24:36 snmpd[4bec4123] >>> OID : system
    Jan 25 16:24:36 snmpd[4bec4123] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Jan 25 16:24:36 snmpd[4bec4123] <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
    Jan 25 16:24:36 snmpd[4bec4123] <<< Get-Response
    Jan 25 16:24:36 snmpd[4bec4123] <<< Source: 10.219.36.151
    Jan 25 16:24:36 snmpd[4bec4123] <<< Destination: 10.219.45.218
    Jan 25 16:24:36 snmpd[4bec4123] <<< Version: SNMPv3
    Jan 25 16:24:36 snmpd[4bec4123] <<< Security Parameters:
    Jan 25 16:24:36 snmpd[4bec4123] <<< SecModel: USM
    Jan 25 16:24:36 snmpd[4bec4123] <<< EngId: 80 00 0a 4c 01 0a db 24 97
    Jan 25 16:24:36 snmpd[4bec4123] <<< User: nnmsnmpuser
    Jan 25 16:24:36 snmpd[4bec4123] <<< EngBoots: 5 EngTime: 11668
    Jan 25 16:24:36 snmpd[4bec4123] <<< Request_id: 0x4bec4123
    Jan 25 16:24:36 snmpd[4bec4123] <<< Error: status=0 / vb_index=0
    Jan 25 16:24:36 snmpd[4bec4123] <<< OID : sysDescr.0
    Jan 25 16:24:36 snmpd[4bec4123] <<< type : OctetString
    Jan 25 16:24:36 snmpd[4bec4123] <<< value: "Juniper Networks, Inc. mx480 int
    Jan 25 16:24:36 snmpd[4bec4123] <<< ernet router, kernel JUNOS 13.3R
    Jan 25 16:24:36 snmpd[4bec4123] <<< 9-S4, Build date: 2016-07-22 23:
    Jan 25 16:24:36 snmpd[4bec4123] <<< 24:13 UTC Copyright (c) 1996-201
    Jan 25 16:24:36 snmpd[4bec4123] <<< 6 Juniper Networks, Inc."
    Jan 25 16:24:36 snmpd[4bec4123] <<< HEX : 4a 75 6e 69 70 65 72 20
    Jan 25 16:24:36 snmpd[4bec4123] <<< 4e 65 74 77 6f 72 6b 73
    Jan 25 16:24:36 snmpd[4bec4123] <<< 2c 20 49 6e 63 2e 20 6d
    Jan 25 16:24:36 snmpd[4bec4123] <<< 78 34 38 30 20 69 6e 74
    Jan 25 16:24:36 snmpd[4bec4123] <<< 65 72 6e 65 74 20 72 6f
    Jan 25 16:24:36 snmpd[4bec4123] <<< 75 74 65 72 2c 20 6b 65
    Jan 25 16:24:36 snmpd[4bec4123] <<< 72 6e 65 6c 20 4a 55 4e
    Jan 25 16:24:36 snmpd[4bec4123] <<< 4f 53 20 31 33 2e 33 52
    Jan 25 16:24:36 snmpd[4bec4123] <<< 39 2d 53 34 2c 20 42 75
    Jan 25 16:24:36 snmpd[4bec4123] <<< 69 6c 64 20 64 61 74 65
    Jan 25 16:24:36 snmpd[4bec4123] <<< 3a 20 32 30 31 36 2d 30
    Jan 25 16:24:36 snmpd[4bec4123] <<< 37 2d 32 32 20 32 33 3a
    Jan 25 16:24:36 snmpd[4bec4123] <<< 32 34 3a 31 33 20 55 54
    Jan 25 16:24:36 snmpd[4bec4123] <<< 43 20 43 6f 70 79 72 69
    Jan 25 16:24:36 snmpd[4bec4123] <<< 67 68 74 20 28 63 29 20
    Jan 25 16:24:36 snmpd[4bec4123] <<< 31 39 39 36 2d 32 30 31
    Jan 25 16:24:36 snmpd[4bec4123] <<< 36 20 4a 75 6e 69 70 65
    Jan 25 16:24:36 snmpd[4bec4123] <<< 72 20 4e 65 74 77 6f 72
    Jan 25 16:24:36 snmpd[4bec4123] <<< 6b 73 2c 20 49 6e 63 2e
    Jan 25 16:24:36 snmpd[4bec4123] <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
    Jan 25 16:24:36 snmpd[4bec4125] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

     

    Regards,

    Rahul

     

     



  • 17.  RE: SNMPv3 OID

     
    Posted 01-25-2018 03:22

    Hi Rahul,

     

    I have changed the "Authentication-key" to "authentication-password" and suddenly it all springs to life. It is always something simple. It works so we now have a baseline to work with.

     

    Thank you for all your help. As usual, excellent.

     



  • 18.  RE: SNMPv3 OID

     
    Posted 01-25-2018 04:45

    As a quick add on to this resolution, I have noticed something that maybe should be included in the Juniper documentation or, at the very least, explained....

     

    When configuring the Authentication, we get two options as shown:

     

    Authentication-key

    Authentication-password

     

    Obviously, in our case "password" was required (and I believe this will be in every case..... but, this is the important part, when we then look at the config, there is no "authentication-password" there, even though that is what we configured. It has changed it to "authenticaiton-key", hence in the Juniper documentation it says "key".

     

    This is very mis-leading from a documentaion perspective and should be changed.

     

    Just a thought.... 🙂