1. Network Management Specification
10.1.5pdnSyslogSeverityThreshold (RW):
The valid values are emerg (0), alert (1), critical (2), error (3), warning (4), notice (5), info (6), debug (7). This value corresponds to a minimum severity level that a syslog messages can be set. All syslog message with an enum value greater than the threshold will not be sent. The values are obtain from the RFC 3164, The BSD Syslog Protocol:
emerg | (0) - Emergency: system is unusable |
alert | (1) - Alert: action must be taken immediately |
critical (2) - Critical: critical conditions | |
error | (3) - Error: error conditions |
warning (4) - Warning: warning conditions | |
notice | (5) - Notice: normal but significant condition |
info | (6) - Informational: informational messages |
debug | (7) - Debug: |
10.1.6pdnSyslogRemoteDaemon (RW):
This value allows user to disable or enable syslog messages going to a remote daemon.
10.1.7pdnEntitySyslogTable (NA):
This table supports retrieval of the syslog messages. It is indexed by the entPhysicalIndex and the pdnSyslogNumber. It allows the clasification of messages per entity (for example, per port card). The table objects are :
10.1.7.1pdnEntitySyslogNumber (NA):
This is a sequentially increasing index of syslog messages starting at 1. When the table reaches its maximum size (as defined by pdnSyslogMaxTableSize) then the oldest message will be dropped without renumbering any messages that remain. The index is reset to 1 on a device reset or when the table is cleared (using pdnSyslogClearTable).
10.1.7.2pdnEntitySyslogMessage (RO): The text of the syslog message.
10.1.8pdnSyslogNumOfMsgInTable (RO):
This value let the users know how many syslog messages are currently in the syslog table.
10.1.9pdnSyslogMaxTableSize (RO):
The maximum number of syslog message the syslog table can hold.
10.1.10 pdnSyslogClearTable (RW):
Valid values are noOp(1) and clear (2). This object clears all the entries in the syslog message table.
10.1.11 pdnSyslogMsgToConsole (RW):
Valid values are disable (1), enable (2). This allows messages to be sent to the device’s console port. Note this is intended for debug use only! It is not recommended to be used to monitor syslog message on a regular bases. If one needs to constantly monitor the syslog messages, then they should use the remote syslog daemon, or other user interfaces.
June 2003 | 93 |
