Snmp Monitor Stats
This scenario shows how to monitor Ethernet statistics using SNMP.
Test Ethernet Stats Through SNMP
Description
Some ping operations are performed and SNMP monitorization is used to check if interface statistics are properly increased.
Scenario
Step 1: Set the following configuration in DUT1 :
set interfaces ethernet eth0 address 10.0.0.2/24 set protocols static route 0.0.0.0/0 interface eth0 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 2: Set the following configuration in DUT0 :
set interfaces ethernet eth1 address 10.0.0.1/24 set protocols static route 0.0.0.0/0 interface eth1 set service snmp community 'COMMUNITY2TEST!' set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 3: Run command service snmp walk local-agent v1 COMMUNITY2TEST! oid 1.3.6.1.4.1.2007.6.3.1.10.5 | grep eth1 at DUT0 and expect this output:
Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetStatsRxBytes."eth1" = INTEGER: 1138170994 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetStatsRxPackets."eth1" = INTEGER: 883787 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetStatsRxErrors."eth1" = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetStatsRxMulticasts."eth1" = INTEGER: 622 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetStatsRxBroadcasts."eth1" = INTEGER: 61 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetStatsTxBytes."eth1" = INTEGER: 1014852736 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetStatsTxPackets."eth1" = INTEGER: 866754 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetStatsTxErrors."eth1" = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetStatsTxMulticasts."eth1" = INTEGER: 533 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetStatsTxBroadcasts."eth1" = INTEGER: 34
Note
Generate some traffic between DUT0 and DUT1.
Step 4: Ping IP address 10.0.0.2 from DUT0:
admin@DUT0$ ping 10.0.0.2 count 5 size 56 timeout 1Show output
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data. 64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=0.619 ms 64 bytes from 10.0.0.2: icmp_seq=2 ttl=64 time=0.370 ms 64 bytes from 10.0.0.2: icmp_seq=3 ttl=64 time=0.344 ms 64 bytes from 10.0.0.2: icmp_seq=4 ttl=64 time=0.285 ms 64 bytes from 10.0.0.2: icmp_seq=5 ttl=64 time=0.346 ms --- 10.0.0.2 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4090ms rtt min/avg/max/mdev = 0.285/0.392/0.619/0.116 ms
Step 5: Ping IP address 224.0.0.1 from DUT0:
admin@DUT0$ ping 224.0.0.1 count 1 size 56 timeout 1Show output
PING 224.0.0.1 (224.0.0.1) 56(84) bytes of data. --- 224.0.0.1 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms
Step 6: Ping IP address 224.0.0.1 from DUT1:
admin@DUT1$ ping 224.0.0.1 count 1 size 56 timeout 1Show output
PING 224.0.0.1 (224.0.0.1) 56(84) bytes of data. --- 224.0.0.1 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms
Step 7: Send arp ping from DUT0 to IP address 1.1.1.1:
admin@DUT0$ arping 1.1.1.1 interface eth1 timeout 5 count 1Show output
ARPING 1.1.1.1 from 10.0.0.1 eth1 Sent 1 probes (1 broadcast(s)) Received 0 response(s)
Step 8: Send arp ping from DUT1 to IP address 1.1.1.1:
admin@DUT1$ arping 1.1.1.1 interface eth0 timeout 5 count 1Show output
ARPING 1.1.1.1 from 10.0.0.2 eth0 Sent 1 probes (1 broadcast(s)) Received 0 response(s)
Note
Repeat previous SNMP command to check new statistics (it may take some time to refresh the information).