13
LinkProof Recommended OID for SNMP Monitoring

LinkProof Recommended OIDs for Monitoring

  • Upload
    others

  • View
    3

  • Download
    0

Embed Size (px)

Citation preview

Page 1: LinkProof Recommended OIDs for Monitoring

LinkProof Recommended OID for SNMP Monitoring

Page 2: LinkProof Recommended OIDs for Monitoring

SNMP Monitoring: LinkProof OIDs Page 2

Page 3: LinkProof Recommended OIDs for Monitoring

SNMP Monitoring: LinkProof OIDs Page 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

Page 4: LinkProof Recommended OIDs for Monitoring

SNMP Monitoring: LinkProof OIDs Page 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.

Page 5: LinkProof Recommended OIDs for Monitoring

SNMP Monitoring: LinkProof OIDs Page 5

Page 6: LinkProof Recommended OIDs for Monitoring

SNMP Monitoring: LinkProof OIDs Page 6

2 Logical Router and Firewall servers statistics

Description Name OID The name of the farm to which the server belongs. Note: This OID is required to know from which server the statistics were taken

rsMLBLogicalNHRServerStatisticsFarmName .1.3.6.1.4.1.89.35.1.38.115.1.1

The name assigned by the user to the server. Note: This OID is required to know from which server the statistics were taken

rsMLBLogicalNHRServerStatisticsName .1.3.6.1.4.1.89.35.1.38.115.1.2

number of currently active users attached to this serve

rsMLBLogicalNHRServerStatisticsAttachedUsersNumber

.1.3.6.1.4.1.89.35.1.38.115.1.3

Maximal number of frames per second dispatched to server since last reset

rsMLBLogicalNHRServerStatisticsPeakLoad .1.3.6.1.4.1.89.35.1.38.115.1.4

Number of frames per second dispatched to server

rsMLBLogicalNHRServerStatisticsFramesRate .1.3.6.1.4.1.89.35.1.38.115.1.5

Number of frames per second dispatched to server

rsMLBLogicalNHRServerStatisticsFramesLoad .1.3.6.1.4.1.89.35.1.38.115.1.6

Maximal number of bytes per second dispatched to server since last reset

rsMLBLogicalNHRServerStatisticsPeakBytesLoad

.1.3.6.1.4.1.89.35.1.38.115.1.7

Number of bytes per second dispatched to server

rsMLBLogicalNHRServerStatisticsBytesRate .1.3.6.1.4.1.89.35.1.38.115.1.8

Number of bytes dispatched to server

rsMLBLogicalNHRServerStatisticsBytesLoad .1.3.6.1.4.1.89.35.1.38.115.1.9

Total number of frames dispatched to server

rsMLBLogicalNHRServerStatisticsTotalFramesLoad

.1.3.6.1.4.1.89.35.1.38.115.1.10

Page 7: LinkProof Recommended OIDs for Monitoring

SNMP Monitoring: LinkProof OIDs Page 7

Description Name OID Number of inbound bytes per second dispatched to server

rsMLBLogicalNHRServerStatisticsInBytesRate .1.3.6.1.4.1.89.35.1.38.115.1.11

Number of outbound bytes per second dispatched to server

rsMLBLogicalNHRServerStatisticsOutBytesRate

.1.3.6.1.4.1.89.35.1.38.115.1.12

Number of inbound bytes dispatched to server

rsMLBLogicalNHRServerStatisticsInBytesLoad .1.3.6.1.4.1.89.35.1.38.115.1.13

Number of outbound bytes dispatched to server

rsMLBLogicalNHRServerStatisticsOutBytesLoad

.1.3.6.1.4.1.89.35.1.38.115.1.14

Uncompressible traffic (in bytes) dispatched to server

rsMLBLogicalNHRServerStatisticsOutBytesNonCompressibleLoad

.1.3.6.1.4.1.89.35.1.38.115.1.15

Total traffic that would be dispatched to server if the compression was not enabled

rsMLBLogicalNHRServerStatisticsOutBytesB4CompressLoad

.1.3.6.1.4.1.89.35.1.38.115.1.16

Uncompressible traffic (in kbps) dispatched to server

rsMLBLogicalNHRServerStatisticsOutBytesNonCompressibleRate

.1.3.6.1.4.1.89.35.1.38.115.1.17

Traffic in kbps that would be dispatched to server if the compression was not enabled

rsMLBLogicalNHRServerStatisticsOutBytesB4CompressRate

.1.3.6.1.4.1.89.35.1.38.115.1.18

Page 8: LinkProof Recommended OIDs for Monitoring

SNMP Monitoring: LinkProof OIDs Page 8

3 Physical Server

Description Name OID The Name of the server. This OID is required to know from which server the statistics were taken

rsMLBPhysicalServerName 1.3.6.1.4.1.89.35.1.38.108.1.1

Number of currently active users attached to this server.

rsMLBPhysicalServerAttachedUsersNumber 1.3.6.1.4.1.89.35.1.38.108.1.2

Maximal number of frames per second dispatched to server since last reset

rsMLBPhysicalServerPeakLoad 1.3.6.1.4.1.89.35.1.38.108.1.3

Number of frames per second dispatched to server.

rsMLBPhysicalServerFramesRate 1.3.6.1.4.1.89.35.1.38.108.1.4

Number of frames per second dispatched to server

rsMLBPhysicalServerFramesLoad 1.3.6.1.4.1.89.35.1.38.108.1.5

Maximal number of bytes per second dispatched to server since last reset.

rsMLBPhysicalServerPeakBytesLoad 1.3.6.1.4.1.89.35.1.38.108.1.7

Number of bytes per second dispatched to server.

rsMLBPhysicalServerBytesRate 1.3.6.1.4.1.89.35.1.38.108.1.10

Number of bytes dispatched to server.

rsMLBPhysicalServerBytesLoad 1.3.6.1.4.1.89.35.1.38.108.1.11

Number of inbound (from farm) bytes per second dispatched to server.

rsMLBPhysicalServerInBytesRate 1.3.6.1.4.1.89.35.1.38.108.1.15

Number of inbound (from farm) bytes dispatched to server.

rsMLBPhysicalServerInBytesLoad 1.3.6.1.4.1.89.35.1.38.108.1.16

Number r of outbound (to farm) bytes per second dispatched to server.

rsMLBPhysicalServerOutBytesRate 1.3.6.1.4.1.89.35.1.38.108.1.18

Number of outbound (to farm) bytes dispatched to server.

rsMLBPhysicalServerOutBytesLoad 1.3.6.1.4.1.89.35.1.38.108.1.19

Number of discarded packets for rsMLBPhysicalServerDiscardedPacketNum 1.3.6.1.4.1.89.35.1.38.108.1.22

Page 9: LinkProof Recommended OIDs for Monitoring

SNMP Monitoring: LinkProof OIDs Page 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 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.

ipForwDatagrams 1.3.6.1.2.1.4.6

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 1.3.6.1.2.1.4.8

Page 10: LinkProof Recommended OIDs for Monitoring

SNMP Monitoring: LinkProof OIDs Page 10

Description Name OID The total number of input datagrams received from interfaces, including those received in err

ipInReceives 1.3.6.1.2.1.4.3

The number of input datagrams 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.

ipInHdrErrors 1.3.6.1.2.1.4.4

The number of input datagrams 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., 0.0.0.0) 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.

ipInAddrErrors 1.3.6.1.2.1.4.5

The number of locally-addressed datagrams received successfully but discarded because of an unknown or unsupported protocol.

ipInUnknownProtos 1.3.6.1.2.1.4.7

The total number of input datagrams successfully delivered to IP user-protocols (including ICMP).

ipInDelivers 1.3.6.1.2.1.4.9

The total number of IP datagrams ipOutRequests 1.3.6.1.2.1.4.10

Page 11: LinkProof Recommended OIDs for Monitoring

SNMP Monitoring: LinkProof OIDs Page 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 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.

ipOutDiscards 1.3.6.1.2.1.4.11

The number of IP datagrams 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.

ipOutNoRoutes 1.3.6.1.2.1.4.12

The number of IP fragments received which needed to be reassembled at this entity.

ipReasmReqds 1.3.6.1.2.1.4.14

The number of IP datagrams successfully re- assembled.

ipReasmOKs 1.3.6.1.2.1.4.15

The number of failures detected by the IP re-assembly algorithm (for whatever reason:timed out, errors,

ipReasmFails 1.3.6.1.2.1.4.16

Page 12: LinkProof Recommended OIDs for Monitoring

SNMP Monitoring: LinkProof OIDs Page 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 have been successfully fragmented at this entity.

ipFragOks 1.3.6.1.2.1.4.17

The number of IP datagrams that 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.

ipFragFails 1.3.6.1.2.1.4.18

The number of IP datagram fragments that have been generated as a result of fragmentation at this entity.

ipFragCreates 1.3.6.1.2.1.4.19

5 Throughput Usage

Description Name OID Resource Utilization of WSD. Considers network utilization and internal CPU utilization

rsWSDResourceUtilization 1.3.6.1.4.1.89.35.1.53

Resource Utilization of internal rsWSDRSResourceUtilization 1.3.6.1.4.1.89.35.1.54

Page 13: LinkProof Recommended OIDs for Monitoring

SNMP Monitoring: LinkProof OIDs Page 13

Description Name OID CPU utilization

Resource Utilization of network utilization

rsWSDREResourceUtilization 1.3.6.1.4.1.89.35.1.55

Average 5 seconds Resource Utilization of internal CPU utilization

rdwr5SecAvgResourceUtilization 1.3.6.1.4.1.89.35.1.112

Average 60 seconds Resource Utilization of internal CPU utilization

rdwr60SecAvgResourceUtilization 1.3.6.1.4.1.89.35.1.113