We're Sorry, Full Content Access is for Members Only...

If you like to keep on reading, Become a Member Now! Here is why:

  • Learn any CCNA, CCNP and CCIE R&S Topic. Explained As Simple As Possible.
  • Try for Just $1. The Best Dollar You've Ever Spent on Your Cisco Career!
  • Full Access to our 651 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

451 Sign Ups in the last 30 days

100% Satisfaction Guaranteed!
You may cancel your monthly membership at any time.
No Questions Asked!

Tags: ,

Forum Replies

  1. Hi Sims,

    Once you have access through SNMP, you will have access to the entire Management Information Base (MIB).

    With views, it’s possible to limit this to certain (sub)trees.

    Cisco has some good examples here:


    Like this one:

    snmp-server view myview mib-2 included
    snmp-server view myview atEntry excluded
    snmp-server view myview cisco included

    It includes access to the MIB-II and Cisco MIB but denies access to the atEntry MIB.

  2. Hi Hussam,

    Glad to hear you like it.

    If you want to play around with Observium, it’s best to use the tutorial that you can find on the Observium website:


    Once you have Observium up and running, the only thing you need to do is to use the cloud icon in GNS3 to connect a physical network card (or a virtual one if you use vmware) to your GNS3 routers:

    This is an older video but it’s probably still 99% the same on the latest GNS3 version.


  3. Hello Justin

    When you specify the security level in the following command

    R1(config)#snmp-server group MYGROUP v3 priv

    you are specifying that SNMP packets will be authenticated and encrypted.

    When issuing the command:

    R1(config)#snmp-server user MYUSER MYGROUP v3 auth md5 MYPASS123 priv aes 128 MYKEY123

    you are specifying that the user will indeed use the User Based Security Model (USM) for SNMPv3 that has been configured in the previous command. The priv keyword in the second command is not the same as that in the first. In the first, you have the option of

    ... Continue reading in our forum

  4. Hello Tejpal

    Yes, you are correct that the statements are confusing. First of all, let’s look at what the noAuthNoPriv level of security actually does. For SNMP v1 and v2, noAuthNoPriv will indeed result in no username authentication and no encryption. However, only the community string will be used to match for authentication.

    For SNMP v3, because it doesn’t use the concept of a community string, the noAuthNoPriv level will result in no encryption but a username will be used for authentication.

    Because of these differences, the statements were made in thi

    ... Continue reading in our forum

  5. I will try this again sometime.

36 more replies! Ask a question or join the discussion by visiting our Community Forum