Foundry NetIron M2404C and M2404F Metro Access Switches
Configuring SAA via SNMP (Rev. 01)
Introduction
© 2008 Foundry Networks, Inc
Page 5 of 40
Architecture
DISMAN-PING-MIB
The Disman-Ping MIB provides the capability of controlling the use of the ping function at a
remote host. It contains objects to manage ping requests on the device.
The management of ping tests is performed by an entry in pingCtlTable. All objects in
pingCtlTable have maximum access read-create. A separate test is created through setting the value
of pingCtlRowStatus to 5 (create-and-wait). Before the test can be initiated a mandatory field must
be set:
•
pingCtlTargetAddress
- Specifies the host address to be used at a remote host for performing a
ping operation.
After specifying the IP addressed to which the probes will be sent, the ping test can be initiated by
setting the value of pingCtlAdminStatus to enabled. The rest of the objects described in the
definition can be optionally configured, but the objects definitions provide default values for them
in case the user does not specify any. They allow the user to control the properties of a ping test,
such as the number of packets to be sent, the timeout interval, the interval of time in which a test
will be repeated, whether or not to store probe statistics for the test, what kind of notifications to
generate for the test, etc.
The scalar object pingMaxConcurrentRequests is used to specify the maximum number of
concurrent active ping requests that are allowed within an agent implementation. The standard
allows a maximum limit to be set in an implementation, or it can be hard-coded and read-only. The
current proposal for implementation suggests a maximum-limit implementation, with a maximum
limit of 50 concurrent tests.
This MIB contains the following objects:
Figure 1: DISMAN-PING-MIB
pingMaxConcurrent Requests
This object contains the maximum number of concurrent active ping requests that are allowed
within an agent implementation. A value of 0 for this object implies that there is no limit for the
number of concurrent active requests in effect.
pingCtlTable
This table defines the pingControlTable for providing, via SNMP, the capability of performing
ping operations at a remote host. The results of these operations are stored in the pingResultsTable
and the pingProbeHistoryTable. This table contains the following objects: