SNMP Monitoring. Hardware Monitoring OIDs DefensePro Version 8.x

Transcription

1 SNMP Monitoring Hardware Monitoring OIDs DefensePro Version 8.x Rev. 2-11/11/2018

2 SNMP Monitoring: Hardware Monitoring OIDs Rev 2 Page 2

3 TABLE OF CONTENTS 1 HEALTH RELATED OIDS RDWRDUALPSUSTATUS RSSYSTEMFANSSTATUS RSHWCPUTEMPERATUREVALUE PERFORMANCE RELATED OIDS RSWSDRESOURCEUTILIZATION RSWSDRSRESOURCEUTILIZATION RDWR5SECAVGRESOURCEUTILIZATION RDWR60SECAVGRESOURCEUTILIZATION RSACCIDLE TRAFFIC RELATED OIDS RSPORTSTATSENTRY RSTRAFFICUTILIZATIONPERPOLICY EXTRA INFORMATION MIB BROWSING SNMP Monitoring: Hardware Monitoring OIDs Rev 2 Page 3

4 SNMP Monitoring: Hardware Monitoring OIDs Rev 2 Page 4

5 1 Health Related OIDs These OIDs are used to monitor the physical health of the device and determine if there s any hardware problem happening or if there s probability for one to happen. 1.1 rdwrdualpsustatus This OID shows the status of the device s power supply, be it a single power supply or dual power supply. rdwrdualpsustatus OID: Possible values (integer): 0=singlePwrSupplyOk, 1=firstPwrSupplyFailed, 2=secondPwrSupplyFailed, 3=doublePwrSupplyOk, 4=unknownPwrSupplyFailed. 1.2 rssystemfansstatus These OIDs show the status of the Fans. rssystemfanstatus OID: <fan number 1 to n> Possible values (string): OK, Fail To determine the number of fans present in the system one can do a SNMP Walk of the rssystemfanindex table. The highest index returned will be the number of fans present on the device. rssystemfanindex OID: rshwcputemperaturevalue These OIDs show the temperature in Celsius of the CPUs. rshwcputemperaturevalue OID: <cpu number 1 to n> Possible values (integer): Temperautre degrees in Celsius SNMP Monitoring: Hardware Monitoring OIDs Rev 2 Page 5

6 To determine the number of cpus present in the system one can do a SNMP Walk of the rshwcputemperatureindex table. The highest indes returned will be the number of cpus present on the device. rshwcputemperatureindex OID: The thresholds for temperature related actions can also be obtained via SNMP via the follwing OIDs: rdwrtemperaturewarningthresholdget Integer rdwrtemperatureshutdownthresholdget Integer SNMP Monitoring: Hardware Monitoring OIDs Rev 2 Page 6

7 2 Performance Related OIDs These OIDs are used to monitor the CPU load and other indicators of the device being overloaded, which may result in poor processing performance. 2.1 rswsdresourceutilization This is the highest resource utilization out of all DefensePro cores, including the controller and the engines rswsdresourceutilization OID: Possible Values (integer): 0 to 100 percent utilization. 2.2 rswsdrsresourceutilization This is the resource utilization of the DefensePro controller core rswsdrsresourceutilization OID: Possible Values (integer): 0 to 100 percent utilization. 2.3 rdwr5secavgresourceutilization This OID shows the total controller core utilization on a 5 seconds moving average. rdwr5secavgresourceutilization OID: Possible Values (integer): 0 to 100 percent utilization. 2.4 rdwr60secavgresourceutilization This OID shows the total controller core utilization on a 60 second moving average. rdwr60secavgresourceutilization OID: Possible Values (integer): 0 to 100 percent utilization. SNMP Monitoring: Hardware Monitoring OIDs Rev 2 Page 7

8 2.5 rsaccidle Origin file: accmib.txt These OIDs show the amount of time the DefensePro engines are spending in idle (not loaded). To get to the engine utilization you should subtract this number from 100. rsaccidle OID: <rsACCCPUId> Possible Values (integer): 0 to 100 percent idle. The rsacccpuid is the engine number, starting from 1, and relate to the amount of cores allocated the DefensePro. In ODS-HTQe, there are 18 such engines \ cores. SNMP Monitoring: Hardware Monitoring OIDs Rev 2 Page 8

9 3 Traffic Related OIDs These OIDs are used to monitor network traffic and other indicators of the interfaces being overloaded, which may result on poor network performance. 3.1 rsportstatsentry Origin file: genericmib.txt This OID monitors different metrics related to the device s physical network interfaces. rsportstatsentry OID: <unit>.<port number> Possible values (integer): <unit> per second The possible values for the <unit> octet can be the following: 2 Inbound Octets per Second (rsportstatsinoctetspersec) 3 Inbound Packets per Second (rsportstatsinpktspersec) 4 Inbound Discards per Second (rsportstatsindiscardspersec) 5 Inbound Errors per Second (rsportstatsinerrorspersec) 6 Outbound Octets per Second (rsportstatsoutoctetspersec) 7 Outbound Packets per Second (rsportstatsoutpktspersec) 8 Outbound Discards per Second (rsportstatsoutdiscardspersec) 9 Outbound Errors per Second (rsportstatsouterrorspersec) To determine the number of physical network interfaces present in the system one can do a SNMP Walk of the rsportstatsportnumber table. The highest index returned will be the number of physical network interfaces present on the device. rsportstatsportnumber OID: rstrafficutilizationperpolicy This OID monitors different metrics related to the device traffic monitoring per policy (the same data that is shown in the traffic utilization graphs in Apsolute Vision). DefensePro issues the statistics at 15-second internals. rstrafficutilizationperpolicy OID: <protocol>.<field> The possible values for the <protocol> octect can be the following: 1- UDP related statistics (rstrafficutilizationperpolicytableudp) 2- TCP related statistics (rstrafficutilizationperpolicytabletcp) SNMP Monitoring: Hardware Monitoring OIDs Rev 2 Page 9

10 3- ICMP related statistics (rstrafficutilizationperpolicytableicmp) 4- OTHER related statistics (rstrafficutilizationperpolicytableother) 5- SCTP related statistics (rstrafficutilizationperpolicytablesctp) 6- IGMP related statistics (rstrafficutilizationperpolicytableigmp) The possible values for the <field> octect can be the following 1- Policy name rspolicynameperpolicy 2- New connections rsnewconnectionsperpolicy 3- Concurrent connections rsconcurconnections 4- Dropped packets rsdroppedpacketsperpolicy 5- Dropped bytes rsdroppedbytesperpolicy 6- Received packets rsreceivedpacketsperpolicy 7- Received bytes rsreceivedbytesperpolicy SNMP Monitoring: Hardware Monitoring OIDs Rev 2 Page 10

11 4 Extra Information The System Uptime of the device can be obtained from: rswsdsysuptime (radwaremib.txt) - String This string comes in the regular System Uptime format. The number of CPUs present in the system can be obtained from: rdwrdevicecpusnumber (radwaremib.txt) - Integer The number of cores present in the system can be obtained from: rscoresnumber (radwaremib.txt) Integer The software version running on the system can be obtained from: rndbrgversion (radwaremib.txt) Integer The attack DB version present in the system can be obtained from: rsidsattackdbversion (IDS.mib) String The CPU frequency in the system can be obtained from: rscpufrequency (radwaremib.txt) Integer The base MAC address in the system can be obtained from: rswsdsysbasemacaddress (radwaremib.txt) - String The system serial number can be obtained from: rndserialnumber (radwaremib.txt) String The throughput licnese installed in the system can also be obtained from: rdwrdevicethroughput (radwaremib.txt) String MIB browsing For SNMP browsing from Windows based computers a simple application called ManageEngine MibBrowser can be used. This application is free for personal use and can be downloaded from SNMP Monitoring: Hardware Monitoring OIDs Rev 2 Page 11

12 North America International Radware Inc. Radware Ltd. 575 Corporate Drive 22 Raoul Wallenberg St. Mahwah, NJ Tel Aviv 69710, Israel Tel: Tel: Radware, Ltd. All Rights Reserved. Radware and all other Radware product and service names are registered trademarks of Radware in the U.S. and other countries. All other trademarks and names are the property of their respective owners. Printed in the U.S.A SNMP Monitoring: Hardware Monitoring OIDs Rev 2 Page 12