The attribute name of which the error log event is associated. For example, it can be NetBackup job's Kbytes attribute, tape drive's number of drives, or VxVM's subdisk's size, or VCS's service's status etc.
Parsed from file vrts.mib.txt
Company: None
Module: VRTS-SNMP-MIBv1
The attribute name of which the error log event is associated. For example, it can be NetBackup job's Kbytes attribute, tape drive's number of drives, or VxVM's subdisk's size, or VCS's service's status etc.
Parsed from file VRTS-SNMP-MIBv1.mib
Module: VRTS-SNMP-MIBv1
Vendor: Veritas
Module: VRTS-SNMP-MIBv1 (vrts.mib)
Type: TABULAR
Access: read-only
Syntax: DisplayString
Automatically extracted from www.mibdepot.com
logAttrName OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "The attribute name of which the error log event is associated. For example, it can be NetBackup job's Kbytes attribute, tape drive's number of drives, or VxVM's subdisk's size, or VCS's service's status etc." ::= { logEntry 6 }
logAttrName OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "The attribute name of which the error log event is associated. For example, it can be NetBackup job's Kbytes attribute, tape drive's number of drives, or VxVM's subdisk's size, or VCS's service's status etc." ::= { logEntry 6 }
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.4.1.1035.301.1.1.1.1 | logIndex | 0 | 0 | It is the unique index of error log and message to be monitored. |
1.3.6.1.4.1.1035.301.1.1.1.2 | logHost | 0 | 0 | The hostname where log error event happened. |
1.3.6.1.4.1.1035.301.1.1.1.3 | logPrdCode | 0 | 0 | The VERITAS product code of which the error log event is associated, it can be 0: NetBackup, 1: VxVM, 2: VxFS, 7: VCS etc. |
1.3.6.1.4.1.1035.301.1.1.1.4 | logPrdName | 0 | 0 | The VERITAS product name of which the error log event is associated, it can be NetBackup, VxVM, VxFS, VCS etc. |
1.3.6.1.4.1.1035.301.1.1.1.5 | logObjName | 0 | 0 | The object name of which the error log event is associated. For example, it can be NetBackup job, tape drive, or VxVM's subdisk… |
1.3.6.1.4.1.1035.301.1.1.1.7 | logFile | 0 | 0 | The log file name where the error strings are detected. |
1.3.6.1.4.1.1035.301.1.1.1.8 | logErrStrs | 0 | 0 | The error strings to monitor. |
1.3.6.1.4.1.1035.301.1.1.1.9 | logDesc | 0 | 0 | The description of the error log event. |
1.3.6.1.4.1.1035.301.1.1.1.10 | logResolution | 0 | 0 | The resolution of the error log event. |
1.3.6.1.4.1.1035.301.1.1.1.99 | logErrFlag | 0 | 0 | Set the flag to 1 to indicate the error strings is found in the specified error log. 0 means no error. |
1.3.6.1.4.1.1035.301.1.1.1.100 | logErrcode | 0 | 0 | The error code of log error. |
1.3.6.1.4.1.1035.301.1.1.1.101 | logErrmsg | 0 | 0 | The error message of log error. |
1.3.6.1.4.1.1035.301.1.1.1.102 | logErrFix | 0 | 0 | Setting this error fix flag to 1 to kick off the logErrFixCmd. |
1.3.6.1.4.1.1035.301.1.1.1.103 | logErrFixCmd | 0 | 0 | The command that gets run when the logErrFix column is set to 1. |