The Internet address for the Syslog message server.
The use of DNS domain names is discouraged, and agent
support for them is optional. Deciding when, and how
often, to resolve them is an issue. Not resolving them
often enough means you might lose synchronization with
the associated entry in the DNS server, and resolving
them too often might leave you without access to the
Syslog server during critical network events.
Parsed from file enterasys-syslog-client-mib.txt
Company: None
Module: ENTERASYS-SYSLOG-CLIENT-MIB
The Internet address for the Syslog message server.
The use of DNS domain names is discouraged, and agent
support for them is optional. Deciding when, and how
often, to resolve them is an issue. Not resolving them
often enough means you might lose synchronization with
the associated entry in the DNS server, and resolving
them too often might leave you without access to the
Syslog server during critical network events.
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]
etsysSyslogServerAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The Internet address for the Syslog message server. The use of DNS domain names is discouraged, and agent support for them is optional. Deciding when, and how often, to resolve them is an issue. Not resolving them often enough means you might lose synchronization with the associated entry in the DNS server, and resolving them too often might leave you without access to the Syslog server during critical network events." ::= { etsysSyslogServerEntry 4 }
etsysSyslogServerAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The Internet address for the Syslog message server. The use of DNS domain names is discouraged, and agent support for them is optional. Deciding when, and how often, to resolve them is an issue. Not resolving them often enough means you might lose synchronization with the associated entry in the DNS server, and resolving them too often might leave you without access to the Syslog server during critical network events." ::= { etsysSyslogServerEntry 4 }
| 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.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… |
| 1.3.6.1.4.1.5624.1.2.14.2.4.1.9 | etsysSyslogServerRowStatus | 0 | 0 | This object allows for the dynamic creation and deletion of entries within the etsysSyslogServerTable as well as the activation a… |