M o n i t o r i n g J u n i p e r E X S w i t c h
10
temperature and potential failure of the hardware components due to a sudden shoot up of temperature, understand
the nature of these failures, and accordingly decide on the remedial measures.
Purpose
Intercepts the temperature traps sent by the hardware components of the switch, extracts
information related to temperature errors/failures from the traps, and reports the count of these
trap messages to the eG manager
Target of the
test
A Juniper EX Switch
Agent
deploying the
test
An external agent
Configurable
parameters for
the test
1.
TESTPERIOD
- How often should the test be executed
2.
HOST
- The host for which the test is to be configured.
3.
SOURCEADDRESS
- Specify a comma-separated list of IP addresses or address patterns
of the hosts from which traps are considered in this test. For example,
10.0.0.1,192.168.10.*
. A leading '*' signifies any number of leading characters, while a
trailing '*' signifies any number of trailing characters.
4.
OIDVALUE
- Provide a comma-separated list of OID and value pairs returned by the traps.
The values are to be expressed in the form,
DisplayName:OID-OIDValue
. For example,
assume that the following OIDs are to be considered by this test: .1.3.6.1.4.1.9156.1.1.2
and .1.3.6.1.4.1.9156.1.1.3. The values of these OIDs are as given hereunder:
OID
Value
.1.3.6.1.4.1.9156.1.1.2
Host_system
.1.3.6.1.4.1.9156.1.1.3
NETWORK
In
this
case
the
OIDVALUE
parameter
can
be
configured
as
Trap1:.1.3.6.1.4.1.9156.1.1.2-Host_system
,Trap2:
.1.3.6.1.4.1.9156.1.1.3-
Network
, where
Trap1
and
Trap2
are the display names that appear as descriptors of this test in the monitor
interface.
An * can be used in the OID/value patterns to denote any number of leading or trailing
characters (as the case may be). For example, to monitor all the OIDs that return values
which begin with the letter 'F', set this parameter to
Failed:*-F*
.
Typically, if a valid value is specified for an OID in the
OID-value
pair configured, then the
test considers the configured OID for monitoring only when the actual value of the OID
matches with its configured value. For instance, in the example above, if the value of OID
.1.3.6.1.4.1.9156.1.1.2
is found to be
HOST
and not
Host_
system, then the test ignores OID
.1.3.6.1.4.1.9156.1.1.2
while monitoring. In some cases however, an OID might not be
associated with a separate value – instead, the OID itself might represent a value. While
configuring such OIDs for monitoring, your
OIDVALUE
specification should be:
DisplayName:OID-any
. For instance, to ensure that the test monitors the OID
.1.3.6.1.4.1.9156.1.1.5
, which in itself, say represents a failure condition, then your
specification would be:
Trap5: .1.3.6.1.4.1.9156.1.1.5-any
.