0% found this document useful (0 votes)
104 views4 pages

SNMP Configuration and Monitoring Guide

Simple Network Management Protocol (SNMP) is used to monitor network devices and retrieve statistics. It defines Object Identifiers (OIDs) to represent device parameters that can be queried. Popular monitoring tools like PRTG and SolarWinds support SNMP to monitor devices configured with SNMP v2c or v3. SNMP v3 adds authentication, encryption, and access control. IP SLA and NetFlow can also be configured to monitor network connectivity and traffic flows between devices. Syslog captures device messages that can help with troubleshooting.

Uploaded by

Erwin Zacarias
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
104 views4 pages

SNMP Configuration and Monitoring Guide

Simple Network Management Protocol (SNMP) is used to monitor network devices and retrieve statistics. It defines Object Identifiers (OIDs) to represent device parameters that can be queried. Popular monitoring tools like PRTG and SolarWinds support SNMP to monitor devices configured with SNMP v2c or v3. SNMP v3 adds authentication, encryption, and access control. IP SLA and NetFlow can also be configured to monitor network connectivity and traffic flows between devices. Syslog captures device messages that can help with troubleshooting.

Uploaded by

Erwin Zacarias
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Simple Network Management Protocol

 grabs statistic from devices


 Object ID (OIDs management information base) for everything

Monitoring applications
 MRTG (Open Source)
 PRTG
 Solarwinds
 Openview (HP)
 Cisco works

SNMP versions
v1
v2c - defacto standard
- community string ro/rw access
- simplicity but lacks security
v3 - user-base authentication
- encryption
- snmp group defines certain sensors on the device that could be used
For basic/advanced monitoring

Configuring SNMPv2:
R1(config)# snmp-server community CISCO ro

On PRTG:
Devices/Local Probe
- Right-Click
- Select add Device

Add Device in Group Local probe


Device Name:
IP Version:
IPv4-Address/DNS Name:
Device Icon:
Device Type
Sensor Management
* Automatic device Identification (standard, recommended)

Credentials for SNMP Devices


inherit from (unchecked)
SNMP Version
* v2c
Community String "CISCO"
Note: You can add sensors such as Ping, CPU, Free Memory, Uptime and Bandwidth

SNMPv3 Configuration
 There are three elements that you have to put in place in order for snmpv3
monitoring to work
o View – restrict what somebody is able to see
o Group – identifies the authentication and encryption method to use
o User – provides the actual credentials that you put into your
monitoring system to monitor your device

Configuring SNMPv3
R1(config)#snmp-server view VIEW iso included
Note: You may Search for Cisco SNMP Object Navigator
R1(config)#snmp-server group MONITOR v3 priv read VIEW
Note: priv authentication with encryption
R1(config)#snmp-server user USER group MONITOR v3 auth sha USERpass priv des56 cisco
Note: “cisco” pre-shared key

ON PRTG:
Add Device
Name:
IP Address:
Icon:
Device Type:
Manual
Credential For:
v3
Athentication
User: user
Password: USERpass
encryption type: des
encryption key: cisco
contact name

Right-Click on monitored device


Auto-Discover/Run Auto-Discovery

Capturing Syslog
 syslog captures key status message from Cisco Devices
 each device can store syslog messages locally or on a remote server
 syslog uses udp port 514

Syslog tool:
 Kiwi syslogs
 splunk

Configuration:
R1(config)# logging x.x.x.x
R1(config)# logging trap notifications

NetFlow
 netflow tracks the flows on the net
 traffic accounting:
 per ip address
 per protocol
 per port
 no default port number (unique port per device)

Configuration:
R1(config)# ip flow-export destination x.x.x.x 9991
R1(config)# ip flow-export version 9
R1(config)# interface fa0/0
R1(config-if)# ip flow ingress
R1(config-if)# ip flow egress

On PRTG:
Add Sensor
Search directly
netflow
version9

Basic Sensor Settings


Sensor Name: NetFlow "R1"
NetFlow 9 Specific Settings
Receive NetFlow: 9991
Active Flow timeout: 15

IP SLA
------

Probe: 1
R1(config)# ip sla 1
R1(config-ip-sla)#icmp-echo x.x.x.x
R1(config-ip-sla-echo)#timeout 1000 ##(miliseconds)
R1(config-ip-sla-echo)# frequency 3 ##(default 60 seconds)
R1(config-ip-sla-echo)# request-data-size 200 ##(in bytes)
R1(config-ip-sla-echo)# exit

Verification:
show running-config | section sla

Probe: 2
R1(config)# ip sla 2
R1(config-ip-sla)#icmp-echo x.x.x.x
R1(config-ip-sla-echo)#timeout 1000 ##(miliseconds)
R1(config-ip-sla-echo)# frequency 3 ##(default 60 seconds)
R1(config-ip-sla-echo)# request-data-size 200 ##(in bytes)
R1(config-ip-sla-echo)# exit

running sla:
R1(config)# ip sla schedule 1 life forever start-time now
R1(config)# ip sla schedule 2 life forever start-time now
R1#show ip sla statistics

Beyond CCNA Configuration:


R1(config)# track 1 rtr 1 ###respons time reporter old name of sla
R1(config)# track 2 rtr 2
R1# show running-config | include track
R1(config)# ip route x.x.x.x x.x.x.x x.x.x.x track 1
R1(config)# ip route x.x.x.x x.x.x.x x.x.x.x track 2

You might also like