NV v7.1.4 ; FP03 ; windows
Is there any necessary sequence / order for entries in trapd.log?
[1] For example, when trapd.log is automatically generated, following
occur in this sequence:
cpqSsFanStatusChange {1.3.6.1.4.1.232.8} 6 1 A 4 0
"LOGONLY" -
Storage System fan status changed to $1.
cpqSeCpuThresholdPassed {1.3.6.1.4.1.232} 6 1001 A 3 2
"LOGONLY" -
CPU internal corrected errors have passed a set threshold.
[2] For human readable reasons, I would order them this way:
cpqSeCpuThresholdPassed {1.3.6.1.4.1.232} 6 1001 A 3 2
"LOGONLY" -
CPU internal corrected errors have passed a set threshold.
cpqSsFanStatusChange {1.3.6.1.4.1.232.8} 6 1 A 4 0
"LOGONLY" -
Storage System fan status changed to $1.
Perhaps, the when trapd.log is parsed, there is NO _exact_ match on OID?
In other words, if the actual OID is 1.3.6.1.4.1.232.8 ; will scenario
[2] STOP parsing at 1.3.6.1.4.1.232 ?
What do you think?
--
Best Regards,
mds
mds resource
877.596.8237
-
Dare to fix things before they break . . .
-
Our capacity for understanding is inversely proportional to how much
we think we know. The more I know, the more I know I don't know . . .
--
signature.asc
Description: Digital signature
|