We’ll inform Rene about adding some information about SNMPv3 as well. In the meantime, here is some general information:
SNMPv3 hasn’t changed much from v2 as far as the protocol itself is concerned other than the addition of cryptographic security. Security is the main focus of v3 because security has been the biggest weakness of the protocol since its inception.
Additional changes include new textual conventions, concepts and terminology.
As for the actual configuration of the protocol on Cisco devices, one of the major differences is that you no longer create an SNMP community name, but you create a username, password, and apply authentication and encryption algorithms such as SHA and AES.
So where SNMP commands in v2 would look like this:
Router(config)#snmp-server community StringRW rw SNMPRW
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.
These SNMPv3 commands are not saved in the running config but in the private config. You can’t retrieve the passwords, the usernames will show up though with show snmp user.
The snmp-server host command specifies the recipient of an SNMP notification either as a trap or a response to an inform request.
If you don’t specify the server as Rene has not in his example, you are able to connect to the router and send responses to SNMP inform requests only. Traps require further configuration on the router because they are initiated by the router itself. Informs are initiated by external SNMP queriers.
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 specifying auth, noauth or priv while in the second command you either include the priv keyword or you don’t. If you use the priv keyword, you then must specify the encryption method and key sizes.
Take a look at the following two command references from Cisco:
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 this way. However, I will let Rene know so that he can clarify this a little more.
I am having doubt regarding snmp and netflow, that where should we configure these protocols in a network topology i.e. switch, router, firewall or servers in DMZ?
It all depends on what kinds of things you want to capture. For netflow, you can specify particular ports from which to capture traffic. You can choose these ports based on what information you want to gain. For example, if you want to follow the traffic that is flowing to and from a web server on your network, configure netflow to monitor the particular port on a switch that the server is connected to. If you want to examine backbone traffic, choose the port channel you have configured between your primary switches and your edge router.
For SNMP, the idea is the same. Do you want to examine particular attributes of traffic to and from your DMZ? Choose the appropriate ports.
In general, when choosing switches as the location to monitor, you are monitoring more specific traffic. Traffic that goes over routers and firewalls is usually consolidated traffic of many combined users.
Ultimately, you have to first define what you are looking for in order to proceed to practically decide on what ports to monitor.
Is this because des is not the same as Des56? Can you help me get this working? Do I have to get an NMS to be able to get it working? or Can I continue to use snmpget? Btw, smmpget worked just fine getting snmpv2 object info.
Thanks for your help!!! I should have started studying here a long time ago I would have advanced in my studies much more had I done that.