Enterasys Security Router X-PeditionTM User Manual page 466

Enterasys Syslog Client MIB
Table B-46 Enterasys Syslog Client MIB (continued)
Field
etsysSyslogServerGroup
etsysSyslogServerDefaultsGroup
Compliance Statements
etsysSyslogClientCompliance
etsysSyslogClientControl
etsysSyslogServerUdpPort
etsysSyslogServerFacility
etsysSyslogServerSeverity
etsysSyslogServerDefaultUdpPort
etsysSyslogServerDefaultFacility
etsysSyslogServerDefaultSeverity
etsysSyslogApplicationAllowedServers
B-24 XSR SNMP Proprietary and Associated Standard MIBs
Description
A collection of objects providing descriptions of syslog servers for sending
system messages to:
• estetsysSyslogServerMaxEntries
• etsysSyslogServerNumEntries
• etsysSyslogServerTableNextAvailableIndex
• etsysSyslogServerDescription
• etsysSyslogServerAddressType
• etsysSyslogServerAddress
• etsysSyslogServerUdpPort
• etsysSyslogServerFacility
• etsysSyslogServerSeverity
• etsysSyslogServerMessagesIgnored
• etsysSyslogServerRowStatus
A collection of objects providing default values for the syslog servers that can
optionally be overridden on a per server basis with etsysSyslogServerFacility,
etsysSyslogServerSeverity, or etsysSyslogServerUdpPort.
The compliance statement for devices that support sending system messages
to a syslog server.
Write access is not required for implementations that do not support
configuring BOTH console AND persistent logging. Implementations may
choose to support only a subset of the client controls. Sets which attempt to
modify unsupported controls should fail.
Write access is not required for implementations that do not support
configuring the UDP port number on a per server basis.
Write access is not required for implementations that do not support
configuring the syslog facility on a per server basis.
Write access is not required for implementations that do not support
configuring the message severity level on a per server basis.
Write access is not required for implementations that do not support
configuring the UDP port number at all, or do not want to support a
configurable default.
Write access is not required for implementations that do not support
configuring the syslog facility at all, or do not want to support a configurable
default.
Write access is not required for implementations that do not support
configuring the syslog facility at all, or do not want to support a configurable
default.
Write access is not required for implementations that do not support
configuring the syslog facility at all, or do not support specification of allowable
servers per application.