SNMP-based monitoring of s5720 Switches

My problems:

Recently, cacti is used to monitor a s5720 switch. The monitoring module is a template of a lower version, so a switch of a higher version cannot obtain data.

Find the cause based on the principle:

Because SNMP-based monitoring is used, the oId (Object descriptor) must be obtained for obtaining data using SNMP ). The most accurate way to obtain the oId is to contact the device manufacturer. The s5720 oid is obtained by I contact the vendor for your reference.

Category	Node Information	Oid of the corresponding node	Remarks
Device status monitoring	CPU utilization	1.3.6.1.4.1.2011.5.25.31.1.1.1.1.5	The box device gets the size of CPU utilization and memory utilization and can also use another node DEVICE-MIB. Install a patch above v100r003sph009 before using this node in v100r003. CPU usage: 1.3.6.1.4.1.2011.6.3.4.1.2 Memory size: 1.3.6.1.4.1.2011.6.3.5.1.1.2 (These two nodes are not recommended) MIB tables involved:ENTITY-EXTENT-MIB
	Memory usage	1.3.6.1.4.1.2011.5.25.31.1.1.1.1.7
	Memory size	1.3.6.1.4.1.2011.5.25.31.1.1.1.1.9
	Device operating temperature	1.3.6.1.4.1.2011.5.25.31.1.1.1.1.11
	Optical module Temperature	1.3.6.1.4.1.2011.5.25.31.1.1.3.1.5
	Optical module Voltage	1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6
	Optical module offset current	1.3.6.1.4.1.2011.5.25.31.1.1.3.1.7
	Optical Transceiver power	1.3.6.1.4.1.2011.5.25.31.1.1.3.1.8
	Luminous power of optical modules	1.3.6.1.4.1.2011.5.25.31.1.1.3.1.9
	Trap	1. device temperature alarms and alarm recovery: 1.3.6.1.4.1.2011.5.25.129.2.2.1 1.3.6.1.4.1.2011.5.25.129.2.2.2 2 Storage Capacity full warning and recovery: 1.3.6.1.4.1.2011.5.25.129.2.6.1 1.3.6.1.4.1.2011.5.25.129.2.6.2 3. Fan alarm and recovery: 1.3.6.1.4.1.2011.5.25.219.2.6.5 1.3.6.1.4.1.2011.5.25.219.2.6.6 4. Power Supply alarms and recovery: 1.3.6.1.4.1.2011.5.25.219.2.5.5 1.3.6.1.4.1.2011.5.25.219.2.5.6	Entity-trap
Port Traffic Monitoring	Port Traffic Statistics	1.3.6.1.2.1.2.2.1 refer to the MIB Manual	This table includes the inbound and outbound traffic of the port, the statistics of unicast and multicast packets, and so on. For details, refer to if-MiB in the MIB reference manual. Currently, traffic statistics for vlanif and trunk are not supported.
	Port updown status	1.3.6.1.2.1.2.2.1.8	-
	Trap	Port bandwidth utilization trap: Corresponding MIB node: Hwifmonitorinputratethreshold 1.3.6.1.4.1.2011.5.25.41.1.7.1.1.9 Hwifmonitoroutputratethreshold 1.3.6.1.4.1.2011.5.25.41.1.7.1.1.113 Alert trap for CRC increase: 1.3.6.1.4.1.2011.5.25.41.4.1 hwifmonitorcrcerrorrising You can configure the CRC parameter under the corresponding port. Trap-threshold error-Statistics ***	For s3300 & 5300 or s3700 & s5700 v100r005 and later versions, s9300 & s7700 v100r003 and later versions support alarms when port utilization reaches the threshold. The default bandwidth usage is 100%. You can monitor related alarms by setting the threshold value. Command Line setting method: interface View Trap-threshold {input-rate | output-rate}Bandwidth-in-use[Resume-RateResume-Threshold] Alarm trap for CRC growth, supported by v100r005c01spc100 and later versions. Name involving MIB table: IF-MIB
Mac vlan arp monitoring	MAC address	1.3.6.1.2.1.17.4.3.1.1	Name involved MIB table: BRIDEG-MIB, ETHARP-MIB,L2MAN-MIB
	Dynamic Mac Query	1.3.6.1.4.1.2011.5.25.42.2.1.3.1
	Static Mac Query	1.3.6.1.4.1.2011.5.25.42.2.1.2.1
	Dynamic ARP Query	1.3.6.1.4.1.2011.5.25.123.1.17
	Static ARP Query	1.3.6.1.4.1.2011.5.25.123.1.18.1
Business-related monitoring	Access to the MIB node of lldp	1.0.8802.1.1.2.1.4.1.1	Note: The command line SNMP-Agent MIB-view attached ded iso-view ISO must be available. Explanation: These two commands only allow to read the Internet node by default, such as: ISO (1 ). org (3 ). DOD (6 ). internet (1 ). X others is not permitted to visit. but the lldp MIB oidis: ISO (1 ). STD (0 ). iso8802 (8802 ). ieee802dot1 (1 ). ieee802dot1mibs (1 ). lldpmib (2) It does not include the lldp mib oid, so we must use command to include lldp MIB subtree. SNMP-Agent MIB-view attached ded iso-view ISO
	STP port status	1.3.6.1.2.1.17.2.15.1.3
	Rrpp ring Attribute Table	1.3.6.1.4.1.2011.5.25.113.2.2.1.4
	Active/standby status of vrrp Local Machine	1.3.6.1.2.1.68.1.3.1.3
Configuration saving, multi-node packaging example	Automatically save configurations through related nodes	Related steps: for example, create instance 1 and package the following two nodes: 1. The value of 1.3.6.1.4.1.2011.6.10.1.2.4.1.2 is 1 (Operation Type 1. Save the configuration file as the Startup File ). 2. Set the value 1.3.6.1.4.1.2011.6.10.1.2.4.1.9 to 4 (4: Create and go). delete an existing instance (6: destory) before each creation ). Package the two nodes to save the files through the network management.	Involved table name: CONFIG-MAN-MIB

 

Check whether the oId has data output:

Run the snmpwalk-v snmp Protocol version-C Community (community) Host address OID (for example, snmpwalk-V 2C-C public X. x. x. X 1.3.6.1.2.1.2.2.1). This command is used to obtain traffic information of all ports of the s5720 switch. Specific parameter resolution please visit the website: http://www.net-snmp.org/docs/mibs/interfaces.html

Add or modify the cacti monitoring template:

The most important thing is to modify the data template oid.

Below are some helpful links:

Description of NET-SNMP parameters: http://www.net-snmp.org/docs/mibs/interfaces.html

This article is from the "Running Horse" blog. For more information, contact the author!

SNMP-based monitoring of  s5720 Switches