The syslog message severity. All syslog messages of the specified severity for
which the Bits are set, will be sent to this syslog server. When setting this object
in a 'createAndGo' request, all lower bits upto and including the desired bit position
must be set. For example, if bit info(4) needs to be set then bits critical(0),
error(1), warning(2), notice(3) and info(4) must also be set in the request.
Consequently, all syslog messages of a given severity and higher will be sent to
the syslog server. It is not possible to send messages that match only a few selected
non-contiguous severities.
Parsed from file v73e2b4.mib.txt
Company: None
Module: EXTREME-SERVICES-MIB
The syslog message severity. All syslog messages of the specified severity for
which the Bits are set, will be sent to this syslog server. When setting this object
in a 'createAndGo' request, all lower bits upto and including the desired bit position
must be set. For example, if bit info(4) needs to be set then bits critical(0),
error(1), warning(2), notice(3) and info(4) must also be set in the request.
Consequently, all syslog messages of a given severity and higher will be sent to
the syslog server. It is not possible to send messages that match only a few selected
non-contiguous severities.
Parsed from file EXTREME-SERVICES-MIB.mib
Module: EXTREME-SERVICES-MIB
Vendor: Extreme Networks
Module: EXTREME-SERVICES-MIB
[Automatically extracted from oidview.com]
extremeRemoteSyslogServerSeverity OBJECT-TYPE SYNTAX BITS { critical(0), error(1), warning(2), notice(3), info(4), debugSummary(5), debugVerbose(6), debugData(7) } MAX-ACCESS read-create STATUS current DESCRIPTION "The syslog message severity. All syslog messages of the specified severity for which the Bits are set, will be sent to this syslog server. When setting this object in a 'createAndGo' request, all lower bits upto and including the desired bit position must be set. For example, if bit info(4) needs to be set then bits critical(0), error(1), warning(2), notice(3) and info(4) must also be set in the request. Consequently, all syslog messages of a given severity and higher will be sent to the syslog server. It is not possible to send messages that match only a few selected non-contiguous severities." DEFVAL { '11111111'B } ::= { extremeRemoteSyslogServerEntry 5 }
extremeRemoteSyslogServerSeverity OBJECT-TYPE SYNTAX BITS { critical(0), error(1), warning(2), notice(3), info(4), debugSummary(5), debugVerbose(6), debugData(7) } MAX-ACCESS read-create STATUS current DESCRIPTION "The syslog message severity. All syslog messages of the specified severity for which the Bits are set, will be sent to this syslog server. When setting this object in a 'createAndGo' request, all lower bits upto and including the desired bit position must be set. For example, if bit info(4) needs to be set then bits critical(0), error(1), warning(2), notice(3) and info(4) must also be set in the request. Consequently, all syslog messages of a given severity and higher will be sent to the syslog server. It is not possible to send messages that match only a few selected non-contiguous severities." DEFVAL { '11111111'B } ::= { extremeRemoteSyslogServerEntry 5 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1916.1.26.1.1.1.1 | extremeRemoteSyslogServerAddressType | 0 | 0 | The type of address specified in the object 'extremeRemoteSyslogServerAddress'. Currently, only 'ipv4' and 'dns' are supported. |
| 1.3.6.1.4.1.1916.1.26.1.1.1.2 | extremeRemoteSyslogServerAddress | 0 | 0 | The address of the remote syslog server. This can be a DNS name or an IPv4 address. |
| 1.3.6.1.4.1.1916.1.26.1.1.1.3 | extremeRemoteSyslogServerPort | 0 | 0 | The UDP port number of the remote syslog server to which syslog messages will be sent. |
| 1.3.6.1.4.1.1916.1.26.1.1.1.4 | extremeRemoteSyslogServerFacility | 0 | 0 | The facility which will be sent in all syslog messages to this remote syslog server. |
| 1.3.6.1.4.1.1916.1.26.1.1.1.6 | extremeRemoteSyslogServerStatus | 0 | 0 | The status of the Row as per standard row status conventions. Only 'createAndGo', 'active' and 'destroy' will be supported. It is… |