The first 255 characters of the text of the most recent
message in the operator log. For opcom messages that
exceed 255 characters, the remainder of the message will be
contained in sOpcomTwo, sOpcomThree, sOpcomFour, sOpcomFive,
sOpcomSix, and sOpcomSeven depending on the length of the
message.
All operator log messages are sent as sOpcomMessage traps and
retained in the internal trap table. To retrieve a previous
message, resend the trap (see sTrapResendSeqNum).
Parsed from file NMSYSMGR.MIB.txt
Company: None
Module: COMTEK-VMS-NM-SYSMGR-MIB
The first 255 characters of the text of the most recent
message in the operator log. For opcom messages that
exceed 255 characters, the remainder of the message will be
contained in sOpcomTwo, sOpcomThree, sOpcomFour, sOpcomFive,
sOpcomSix, and sOpcomSeven depending on the length of the
message.
All operator log messages are sent as sOpcomMessage traps and
retained in the internal trap table. To retrieve a previous
message, resend the trap (see sTrapResendSeqNum).
Parsed from file COMTEK-VMS-NM-SYSMGR-MIB.mib
Module: COMTEK-VMS-NM-SYSMGR-MIB
Vendor: Comtek Services Inc.
Module: COMTEK-VMS-NM-SYSMGR-MIB
[Automatically extracted from oidview.com]
sOpcomOne OBJECT-TYPE SYNTAX DisplayString (SIZE (1..255)) ACCESS read-only STATUS mandatory DESCRIPTION "The first 255 characters of the text of the most recent message in the operator log. For opcom messages that exceed 255 characters, the remainder of the message will be contained in sOpcomTwo, sOpcomThree, sOpcomFour, sOpcomFive, sOpcomSix, and sOpcomSeven depending on the length of the message. All operator log messages are sent as sOpcomMessage traps and retained in the internal trap table. To retrieve a previous message, resend the trap (see sTrapResendSeqNum)." ::= { sErrInfo 3 }
sOpcomOne OBJECT-TYPE SYNTAX DisplayString (SIZE (1..255)) ACCESS read-only STATUS mandatory DESCRIPTION "The first 255 characters of the text of the most recent message in the operator log. For opcom messages that exceed 255 characters, the remainder of the message will be contained in sOpcomTwo, sOpcomThree, sOpcomFour, sOpcomFive, sOpcomSix, and sOpcomSeven depending on the length of the message. All operator log messages are sent as sOpcomMessage traps and retained in the internal trap table. To retrieve a previous message, resend the trap (see sTrapResendSeqNum)." ::= { sErrInfo 3 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.597.4.3.4.3.0 | sOpcomOne | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.597.4.3.4.1 | sHwErrInfo | 3 | 10 | None |
| 1.3.6.1.4.1.597.4.3.4.2 | sSwErrInfo | 5 | 10 | None |
| 1.3.6.1.4.1.597.4.3.4.4 | sOpcomTwo | 1 | 1 | Part 2 of an opcom message. |
| 1.3.6.1.4.1.597.4.3.4.5 | sOpcomThree | 1 | 1 | Part 3 of an opcom message. |
| 1.3.6.1.4.1.597.4.3.4.6 | sOpcomFour | 1 | 1 | Part 4 of an opcom message. |
| 1.3.6.1.4.1.597.4.3.4.7 | sOpcomFive | 1 | 1 | Part 5 of an opcom message. |
| 1.3.6.1.4.1.597.4.3.4.8 | sOpcomReplyId | 1 | 1 | Request number to be associated with the operator reply. This number identifies a previous Opcom request. This variable is reset… |
| 1.3.6.1.4.1.597.4.3.4.9 | sOpcomReplyStatus | 1 | 1 | Completion status to accompany opcom reply. This variable is reset to noStatus when a reply is successfully sent. (See sOpcomRep… |
| 1.3.6.1.4.1.597.4.3.4.10 | sOpcomReplyText | 1 | 1 | Text to be sent for an operator reply message. This variable is reset to null when a reply is successfully sent. (See sOpcomRepl… |
| 1.3.6.1.4.1.597.4.3.4.11 | sOpcomReplySend | 1 | 1 | Flag which is used to trigger sending of an operator reply message. To send an operator reply, set the sOpcomReplyId, sOpcomRepl… |
| 1.3.6.1.4.1.597.4.3.4.12 | sOpcomSix | 1 | 1 | Part 6 of an opcom message. |
| 1.3.6.1.4.1.597.4.3.4.13 | sOpcomSeven | 1 | 1 | Part 7 of an opcom message. |