This object allows for the dynamic creation and deletion
of entries within the etsysSyslogServerTable as well as
the activation and deactivation of these entries.
When this object's value is set to notInService(2) this
server will not be sent any messages, nor will any of its
counters be incremented.
The agent should not delete a row, except in the case of
the loss of persistent storage.
Refer to the RowStatus convention for further details on
the behavior of this object.
Parsed from file enterasys-syslog-client-mib.txt
Company: None
Module: ENTERASYS-SYSLOG-CLIENT-MIB
This object allows for the dynamic creation and deletion
of entries within the etsysSyslogServerTable as well as
the activation and deactivation of these entries.
When this object's value is set to notInService(2) this
server will not be sent any messages, nor will any of its
counters be incremented.
The agent should not delete a row, except in the case of
the loss of persistent storage.
Refer to the RowStatus convention for further details on
the behavior of this object.
Parsed from file ENTERASYS-SYSLOG-CLIENT-MIB.mib
Module: ENTERASYS-SYSLOG-CLIENT-MIB
Vendor: Enterasys Networks
Module: ENTERASYS-SYSLOG-CLIENT-MIB
[Automatically extracted from oidview.com]
etsysSyslogServerRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object allows for the dynamic creation and deletion of entries within the etsysSyslogServerTable as well as the activation and deactivation of these entries. When this object's value is set to notInService(2) this server will not be sent any messages, nor will any of its counters be incremented. The agent should not delete a row, except in the case of the loss of persistent storage. Refer to the RowStatus convention for further details on the behavior of this object." REFERENCE "RFC2579 (Textual Conventions for SMIv2)" ::= { etsysSyslogServerEntry 9 }
etsysSyslogServerRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object allows for the dynamic creation and deletion of entries within the etsysSyslogServerTable as well as the activation and deactivation of these entries. When this object's value is set to notInService(2) this server will not be sent any messages, nor will any of its counters be incremented. The agent should not delete a row, except in the case of the loss of persistent storage. Refer to the RowStatus convention for further details on the behavior of this object." REFERENCE "RFC2579 (Textual Conventions for SMIv2)" ::= { etsysSyslogServerEntry 9 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.5624.1.2.14.2.4.1.1 | etsysSyslogServerIndex | 0 | 0 | A unique arbitrary identifier for this syslog server. |
| 1.3.6.1.4.1.5624.1.2.14.2.4.1.2 | etsysSyslogServerDescription | 0 | 0 | Administratively assigned textual description of this syslog server. |
| 1.3.6.1.4.1.5624.1.2.14.2.4.1.3 | etsysSyslogServerAddressType | 0 | 0 | The type of Internet address by which the Syslog server is specified in etsysSyslogServerAddress. Not all address types may be su… |
| 1.3.6.1.4.1.5624.1.2.14.2.4.1.4 | etsysSyslogServerAddress | 0 | 0 | The Internet address for the Syslog message server. The use of DNS domain names is discouraged, and agent support for them is opt… |
| 1.3.6.1.4.1.5624.1.2.14.2.4.1.5 | etsysSyslogServerUdpPort | 0 | 0 | The UDP port number the client is using to send requests to this server. If an entity only supports sending messages using a singl… |
| 1.3.6.1.4.1.5624.1.2.14.2.4.1.6 | etsysSyslogServerFacility | 0 | 0 | The syslog facility (local0-local7) that will be encoded in messages sent to this server. If an entity only supports encoding a s… |
| 1.3.6.1.4.1.5624.1.2.14.2.4.1.7 | etsysSyslogServerSeverity | 0 | 0 | The maximum severity level of the messages that should be forwarded to the syslog server. The higher the level, the lower the se… |
| 1.3.6.1.4.1.5624.1.2.14.2.4.1.8 | etsysSyslogServerMessagesIgnored | 0 | 0 | This is a count of messages not sent to this server because the severity level of the message was above etsysSyslogServerSeverity… |