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 597 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

 

393 New Members signed up the last 30 days!

satisfaction-guaranteed

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

Tags:


Forum Replies

  1. Great lesson! I had to implement an SNMP change control recently. Nice to have a great refresher.

  2. good explaination

     

    Fahad ALFadani

    KSA
    <div id="__if72ru4sdfsdfruh7fewui_once" style=“display: none;”></div>
    <div id="__zsc_once"></div>

  3. Hi Wilfried,

    You might also like LibreNMS.

    It’s the exact same thing as Observium but it’s free. It supports instant updates and alerting out of the box. For Observium you’ll have to pay when you want automatic updates and alerting.

    Rene

  4. Hi Rene,
    What is the difference between SNMP get and get next?

  5. maher1 says:

    Hi Ananth,

    That’s a good question.

    We have already seen in this lesson the usage of SNMP GET sent from the SNMP Manager is to gather a specific object instance from the SNMP agent.

    Or The GETNEXT command requests a list of instances from a remote entity, but expects the next variable in the tree back. So meaning If a GETNEXT is issued on an object then the agent MUST return the next instance in the MIB tree.

    Does it make sense?

1 more reply! Ask a question or join the discussion by visiting our Community Forum