Shutdown Traps Test
This test provides administrators with a heads up on those failure events that have caused/could cause the storage system to come to a standstill!
Target of the test : A NetApp Unified Storage
Agent deploying the test : An external/remote agent
Outputs of the test : One set of results for each type of failure event that occurred on the target storage system.
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 high temperature on the target NetApp Unified Storage. 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 high temperature condition, let us use 'Over Temperature' as the appropriate DisplayName. The OID that reports high temperature on the target storage is .1.3.6.1.4.1.789.0.95. Therefore, the entry you need to append to the default list will be: Over Temperature:.1.3.6.1.4.1.789.0.95-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. |
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 failure events that caused system shutdown during the last measurement period. |
Number |
The failure events may be generated due to the failure of hardware units like fans, chassis power supply etc, failure of the cluster node, the shell Interface module failure etc. When such failure events are generated, the storage system will shutdown automatically and the storage sytem must be restarted only after rectifying the failure. Ideally, the value of this measure should be zero. A high value is an indication of performance degradation of the storage system. The detailed diagnosis capability, if enabled provides you with a more detailed information about the failure events that were captured by this measure. |