Temperature Traps Test

Temperature fluctuation of hardware components, if not promptly detected and resolved, can prove to be fatal to the availability and overall health of a Juniper EX Switch. This test 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. This information enables administrators to detect current 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.

Target of the test : A Juniper EX Switch

Agent deploying the test : An external agent

Outputs of the test : One set of results for each type of failure event that occurred on the target Juniper EX Switch.

Configurable parameters for the test
Parameters	Description
Test Period	How often should the test be executed
Host	The host for which the test is to be configured.
Source Address	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.
OID Value	By default, this parameter is pre-configured with a comma-separated list of Display name:OID pairs returned by the traps for specific failure events/conditions. The DisplayName in every pair will appear as descriptors of this test in the monitor interface. You can, if you so wish, override this default specification by appending more DisplayName:OID pairs to the pre-configured list. This way, you can instruct the test to receive traps for failure conditions that are of interest to you. For example, say you want to capture the traps generated for abnormal temperature on the target Juniper EX Switch. To achieve this, you need to append an entry of the following format: DisplayName:OID-any. Typically, the DisplayName can be any meaningful text string that qualifies the failure condition that is to be captured. Since our example seeks to capture an abnormal temperature condition, let us use 'HighTemperature' as the appropriate DisplayName. The OID that reports abnormal temperature on Juniper EX Switch is .1.3.6.1.4.1.2636.4.1.7. Therefore, the entry you need to append to the default list will be: HighTemperature:..1.3.6.1.4.1.2636.4.1.7-any. Similarly, you can append more entries. However, make sure that the new entries are also comma-separated.
ShowOID	Specifying True against ShowOID will ensure that the detailed diagnosis of this test shows the OID strings along with their corresponding values. If you enter False, then the values alone will appear in the detailed diagnosis page, and not the OIDs.
TrapOIDs	By default, this parameter is set to all, indicating that the eG agent considers all the traps received from the specified sourceaddresses. To make sure that the agent considers only specific traps received from the SourceAddress, then provide a comma-separated list of OIDs in the trapoids text box. A series of OID patterns can also be specified here, so that the test considers only those OIDs that match the specified pattern(s). For instance, 94.2,.1.3.6.1.4.25, where * indicates leading and/or trailing spaces.
DD Frequency	Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Temperature alerts	Indicates the number of times this event was triggered during the last measurement period.	Number	The failure events may be generated due to the temperature failure of the hardware components of the Juniper EX Switch. If the failure events are not rectified within a certain pre-defined timeperiod, the switch will be shutdown automatically. Ideally, the value of this measure should be zero. A high value is an indication of performance degradation of the Juniper EX Switch.