HPE StoreOnce Traps Test
Hardware errors/failures, if not promptly detected and resolved, can prove to be fatal to the availability and overall health of the target backup server. Similarly, warning messages serve as early indicators of 'probable' failures/errors that can occur on the backup server. This test intercepts the traps sent by the backup system, extracts information related to hardware errors/failures, warnings, devices etc from the traps, and reports the count and detailed description of these trap messages to the eG manager. This information enables administrators to detect current and potential hardware failures, understand the nature of these failures, and accordingly decide on the remedial measures.
Target of the test : HPE StoreOnce Backup system
Agent deploying the test : A remote agent
Outputs of the test : One set of results for each type of failure event that occurred on the hardware of the target HPE StoreOnce Backup system being monitored.
| Parameters | Description | ||||||
|---|---|---|---|---|---|---|---|
|
Test Period |
How often should the test be executed. |
||||||
|
Host |
The host for which the test is to be configured. |
||||||
|
Port |
The port at which the host is listening. By default, this is set to Null. |
||||||
|
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 |
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:
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. In some cases, multiple trap OIDs may be associated with a single value. For instance, if two different OIDs (1.3.6.1.4.1.9156.1.1.4 and 1.3.6.1.4.9156.1.1.5) representing a failure condition needs to be monitored by the test, then, your specification should be: Trap6:.1.3.6.1.4.1.9156.1.1.4;.1.3.6.1.4.9156.1.1.5-any. Here, a semi-colon is used as a separator to separate the OIDs and the value should be specified after the last OID. |
||||||
|
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. |
||||||
|
Detailed Diagnosis |
To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
|
| Measurement | Description | Measurement Unit | Interpretation |
|---|---|---|---|
|
Number of messages |
Indicates the number of events of this type that were captured during the last measurement period. |
|
Compare the value of this measure across the events of each type to figure out the type for which maximum number of traps messages were captured. Ideally, the value of this measure should be zero. A high value is an indication of performance degradation of the backup server. The detailed diagnosis capability, provides you with a more detailed information about the events that were captured by this measure. |
The detailed diagnosis of the Number of messages measure provides you with a more detailed information about the events that were captured by this measure.
Figure 1 : The detailed diagnosis of the Number of messages measure
