LinkProof Recommended OID for SNMP Monitoring

Transcription

1 LinkProof Recommended OID for SNMP Monitoring

2 SNMP Monitoring: LinkProof OIDs Page 2

3 TABLE OF CONTENTS 1 General 4 2 Logical Router and Firewall servers statistics 6 3 Physical Server 8 4 IP Statistics 9 5 Throughput Usage 12 SNMP Monitoring: LinkProof OIDs Page 3

4 1 General The following information about Radware s LinkProof product is available through APSolute Vision and CLI under various menu options. If you wish to incorporate other management devices and tools to gather this type of statistical information via SNMP, this document contains a partial list of the variables available and their corresponding Object Identifiers. The OIDs in this document are based on version 6.21, but most of them are valid for all versions. Administrators can download the appropriate SNMP MIB files for their Radware products from Radware Customer Portal and compile them for use with various SNMP monitoring tools. Each version of the LinkProof software requires specific MIBs to be compiled and administrators should take care to obtain the correct collection of MIBS from the Radware web site. Typically, these MIBS are bundled in ZIP format and contain each of the appropriate files needed. Alternately, administrators can poll Radware devices for specific OIDs without necessarily compiling the entire MIB to an SNMP monitoring device. This document provides information about some of the more commonly requested OIDs used to collect information about the LinkProof and its activity. In some cases, depending on the SNMP tool used, OIDs may need to have.0 added to the end of the GET request. The document is based on Radware s knowledge and experience in various Carrier deployment projects. Note It is recommended by Radware that customers will adjust their monitoring policy to their already existing IT policy in regards to what counters to monitor, how often to measure them and what is considered a threshold to watch. SNMP Monitoring: LinkProof OIDs Page 4

5 SNMP Monitoring: LinkProof OIDs Page 5

6 2 Logical Router and Firewall servers statistics Description Name OID The name of the farm to which the rsmlblogicalnhrserverstatisticsfarmname server belongs. Note: This OID is required to know from which server the statistics were taken The name assigned by the user to rsmlblogicalnhrserverstatisticsname the server. Note: This OID is required to know from which server the statistics were taken number of currently active users rsmlblogicalnhrserverstatisticsattachedus attached to this serve ersnumber Maximal number of frames per rsmlblogicalnhrserverstatisticspeakload second since last reset Number of frames per second rsmlblogicalnhrserverstatisticsframesrate Number of frames per second rsmlblogicalnhrserverstatisticsframesload Maximal number of bytes per rsmlblogicalnhrserverstatisticspeakbytesl second since last reset oad Number of bytes per second rsmlblogicalnhrserverstatisticsbytesrate Number of bytes dispatched to rsmlblogicalnhrserverstatisticsbytesload server Total number of frames dispatched to server rsmlblogicalnhrserverstatisticstotalframes Load SNMP Monitoring: LinkProof OIDs Page 6

7 Description Name OID Number of inbound bytes per rsmlblogicalnhrserverstatisticsinbytesrate second Number of outbound bytes per rsmlblogicalnhrserverstatisticsoutbytesra second te Number of inbound bytes rsmlblogicalnhrserverstatisticsinbytesload Number of outbound bytes rsmlblogicalnhrserverstatisticsoutbyteslo ad Uncompressible traffic (in bytes) rsmlblogicalnhrserverstatisticsoutbytesno ncompressibleload Total traffic that would be rsmlblogicalnhrserverstatisticsoutbytesb if the compression was not enabled CompressLoad Uncompressible traffic (in kbps) rsmlblogicalnhrserverstatisticsoutbytesno Traffic in kbps that would be if the compression was not enabled ncompressiblerate rsmlblogicalnhrserverstatisticsoutbytesb4 CompressRate SNMP Monitoring: LinkProof OIDs Page 7

8 3 Physical Server Description Name OID The Name of the server. This OID rsmlbphysicalservername is required to know from which server the statistics were taken Number of currently active users rsmlbphysicalserverattachedusersnumber attached to this server. Maximal number of frames per rsmlbphysicalserverpeakload second since last reset Number of frames per second rsmlbphysicalserverframesrate Number of frames per second rsmlbphysicalserverframesload Maximal number of bytes per rsmlbphysicalserverpeakbytesload second since last reset. Number of bytes per second rsmlbphysicalserverbytesrate Number of bytes dispatched to rsmlbphysicalserverbytesload server. Number of inbound (from farm) rsmlbphysicalserverinbytesrate bytes per second dispatched to server. Number of inbound (from farm) rsmlbphysicalserverinbytesload bytes. Number r of outbound (to farm) rsmlbphysicalserveroutbytesrate bytes per second dispatched to server. Number of outbound (to farm) rsmlbphysicalserveroutbytesload bytes. Number of discarded packets for rsmlbphysicalserverdiscardedpacketnum SNMP Monitoring: LinkProof OIDs Page 8

9 Description Name OID that NHR since the last device reboot. The packet were discarded since DiscardFlag was enabled and the NHR reached its limit 4 IP Statistics Description Name OID The number of input datagrams for ipforwdatagrams which this entity was not their final IP destination, as a result of which an attempt was made to find a route to forward them to that final destination. In entities which do not act as IP Gateways, this counter will include only those packets which were Source-Routed via this entity, and the Source- Route option processing was successful. The number of input IP datagrams for which no problems were encountered to prevent their continued processing, but which were discarded (e.g., for lack of buffer space). Note that this counter does not include any datagrams discarded while awaiting re-assembly. ipindiscards SNMP Monitoring: LinkProof OIDs Page 9

10 Description Name OID The total number of input ipinreceives datagrams received from interfaces, including those received in err The number of input datagrams ipinhdrerrors discarded due to errors in their IP headers, including bad checksums, version number mismatch, other format errors, time-to-live exceeded, errors discovered in processing their IP options, etc. The number of input datagrams ipinaddrerrors discarded because the IP address in their IP header's destination field was not a valid address to be received at this entity.this count includes invalid addresses (e.g., ) and addresses of unsupported Classes (e.g., Class E). For entities which are not IP Gateways and therefore do not forward datagrams, this counter includes datagrams discarded because the destination address was not a local address. The number of locally-addressed ipinunknownprotos datagrams received successfully but discarded because of an unknown or unsupported protocol. The total number of input ipindelivers datagrams successfully delivered to IP user-protocols (including ICMP). The total number of IP datagrams ipoutrequests SNMP Monitoring: LinkProof OIDs Page 10

11 Description Name OID which local IP user-protocols (including ICMP) supplied to IP in requests for transmission. Note that this counter does not include any datagrams counted in ipforwdatagrams. The number of output IP datagrams ipoutdiscards for which no problem was encountered to prevent their transmission to their destination, but which were discarded (e.g., for lack of buffer space). Note that this counter would include datagrams counted in ipforwdatagrams if any such packets met this (discretionary) discard criterion. The number of IP datagrams ipoutnoroutes discarded because no route could be found to transmit them to their destination. Note that this counter includes any packets counted in ipforwdatagrams which meet this `no-route' criterion. Note that this includes any datagarms which a host cannot route because all of its default gateways are down. The number of IP fragments ipreasmreqds received which needed to be reassembled at this entity. The number of IP datagrams ipreasmoks successfully re- assembled. The number of failures detected by the IP re-assembly algorithm (for whatever reason:timed out, errors, ipreasmfails SNMP Monitoring: LinkProof OIDs Page 11

12 Description Name OID etc). Note that this is not necessarily a count of discarded IP fragments since some algorithms (notably the algorithm in RFC 815) can lose track of the number of fragments by combining them as they are received. The number of IP datagrams that ipfragoks have been successfully fragmented at this entity. The number of IP datagrams that ipfragfails have been discarded because they needed to be fragmented at this entity but could not be, e.g., because their Don't Fragment flag was set. The number of IP datagram fragments that have been generated as a result of fragmentation at this entity. ipfragcreates Throughput Usage Description Name OID Resource Utilization of WSD. rswsdresourceutilization Considers network utilization and internal CPU utilization Resource Utilization of internal rswsdrsresourceutilization SNMP Monitoring: LinkProof OIDs Page 12

13 Description Name OID CPU utilization Resource Utilization of rswsdreresourceutilization network utilization Average 5 seconds Resource rdwr5secavgresourceutilization Utilization of internal CPU utilization Average 60 seconds Resource Utilization of internal CPU utilization rdwr60secavgresourceutilization SNMP Monitoring: LinkProof OIDs Page 13