CISCOSB-SYSLOG-MIB
The CISCOSB-SYSLOG-MIB module enables monitoring and management of syslog service states and message counters on Cisco Service Broker (CISCOSB) devices. It facilitates the collection of system log event data, including message generation rates and service operational status, for centralized logging and troubleshooting.
Imported Objects
Objects
44 total| Object Name |
|---|
rlSyslogThe private MIB module definition for SYSLOG services in CISCOSB devices. MODULE-IDENTITY .1.3.6.1.4.1.9.6.1.101.82 |
rlSyslogPrivate OBJECT IDENTIFIER .1.3.6.1.4.1.9.6.1.101.82.2 |
rlSyslogGlobalEnableGlobal enable for syslog flash, syslog cache and syslog UDP. When set to false, only console logging is performed.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.6.1.101.82.2.1 |
rlSyslogMinLogToConsoleSeverityThe minimal severity to log to console. Lower severity will not be written to console. Value notActive indicate this activity is disabled.rw RlSyslogSeverity .1.3.6.1.4.1.9.6.1.101.82.2.2 |
rlSyslogMinLogToFileSeverityThe minimal severity to log to LogFile. Lower severity will not be written to the LogFile. Value notActive indicates this activity is disabled.rw RlSyslogSeverity .1.3.6.1.4.1.9.6.1.101.82.2.3 |
rlSyslogMinLogToCacheSeverityThe minimal severity to log to memory cache. Lower severity will not be read from cache. Value notActive indicate this activity is disabled. Note that all events are logged to cache unless its severity is notActive.rw RlSyslogSeverity .1.3.6.1.4.1.9.6.1.101.82.2.4 |
rlSyslogClearLogfileSetting to a value other than 0 results in deleting the log file.rw Unsigned32 .1.3.6.1.4.1.9.6.1.101.82.2.5 |
rlSyslogClearCacheSetting to a value other than 0 results in clearing the memory cache.rw Unsigned32 .1.3.6.1.4.1.9.6.1.101.82.2.6 |
rlSyslogMibVersionThe Syslog MIB's version. It's 1.ro INTEGER .1.3.6.1.4.1.9.6.1.101.82.2.7 |
rlSyslogLogTableA table containing events sent to the system log file. SEQUENCE OF RlSyslogLogEntry .1.3.6.1.4.1.9.6.1.101.82.2.8 |
rlSyslogLogEntryA log entry RlSyslogLogEntry .1.3.6.1.4.1.9.6.1.101.82.2.8.1 |
rlSyslogLogCounterA counter that identifies this entry - used to differentiate logged entries. And the order given is the order of logging. A entries may not form sequence of this value. (Time is not a differentiating element as logged entries may come in a sequence.ro Unsigned32 .1.3.6.1.4.1.9.6.1.101.82.2.8.1.1 |
rlSyslogLogDateTimeThe time in string (formated DD-MMM-YYYY HH:MM:SS e.g 14-Apr-2002 10:33:31), when the error was logged..ro DisplayString .1.3.6.1.4.1.9.6.1.101.82.2.8.1.2 |
rlSyslogLogAppMnemonicApplication that created this error.ro DisplayString .1.3.6.1.4.1.9.6.1.101.82.2.8.1.3 |
rlSyslogLogSeveritySeverity of the reported error.ro RlSyslogSeverity .1.3.6.1.4.1.9.6.1.101.82.2.8.1.4 |
rlSyslogLogMessageMnemonicShort identifier of this message that created this error.ro DisplayString .1.3.6.1.4.1.9.6.1.101.82.2.8.1.5 |
rlSyslogLogText1The text of the logged message without time and date - part 1.ro DisplayString .1.3.6.1.4.1.9.6.1.101.82.2.8.1.6 |
rlSyslogLogText2The text of the logged message without time and date - part 2.ro DisplayString .1.3.6.1.4.1.9.6.1.101.82.2.8.1.7 |
rlSyslogLogText3The text of the logged message without time and date - part 3.ro DisplayString .1.3.6.1.4.1.9.6.1.101.82.2.8.1.8 |
rlSyslogLogText4The text of the logged message without time and date - part 4.ro DisplayString .1.3.6.1.4.1.9.6.1.101.82.2.8.1.9 |
rlSyslogLogCacheTableA table containing errors registered to system cache. SEQUENCE OF RlSyslogLogCacheEntry .1.3.6.1.4.1.9.6.1.101.82.2.9 |
rlSyslogLogCacheEntryA log history entry RlSyslogLogCacheEntry .1.3.6.1.4.1.9.6.1.101.82.2.9.1 |
rlSyslogLogCacheCounterA counter that identifies this entry - used to differentiate logged entries. And the order given is the order of logging. A entries may not form sequence of this value. (Time is not a differentiating element as logged entries may come in a sequence.ro Unsigned32 .1.3.6.1.4.1.9.6.1.101.82.2.9.1.1 |
rlSyslogLogCacheDateTimeThe time in string (formated DD-MMM-YYYY HH:MM:SS e.g 14-Apr-2002 10:33:31), when the eroor was logged..ro DisplayString .1.3.6.1.4.1.9.6.1.101.82.2.9.1.2 |
rlSyslogLogCacheAppMnemonicApplication that created this error.ro DisplayString .1.3.6.1.4.1.9.6.1.101.82.2.9.1.3 |
rlSyslogLogCacheSeveritySeverity of the reported error.ro RlSyslogSeverity .1.3.6.1.4.1.9.6.1.101.82.2.9.1.4 |
rlSyslogLogCacheMessageMnemonicShort identifier of this message that created this error.ro DisplayString .1.3.6.1.4.1.9.6.1.101.82.2.9.1.5 |
rlSyslogLogCacheText1The text of the logged message without time and date - part 1.ro DisplayString .1.3.6.1.4.1.9.6.1.101.82.2.9.1.6 |
rlSyslogLogCacheText2The text of the logged message without time and date - part 2.ro DisplayString .1.3.6.1.4.1.9.6.1.101.82.2.9.1.7 |
rlSyslogLogCacheText3The text of the logged message without time and date - part 3.ro DisplayString .1.3.6.1.4.1.9.6.1.101.82.2.9.1.8 |
rlSyslogLogCacheText4The text of the logged message without time and date - part 4.ro DisplayString .1.3.6.1.4.1.9.6.1.101.82.2.9.1.9 |
rlSyslogConsoleMessagesIgnoredThis is a count of messages not sent to the console because the severity level of the message was above rlSyslogMinLogToConsoleSeverity, the higher the level, the lower the severity.ro Counter32 .1.3.6.1.4.1.9.6.1.101.82.2.10 |
rlSyslogFileMessagesIgnoredThis is a count of messages not sent to the file because the severity level of the message was above rlSyslogMinLogToFileSeverity, the higher the level, the lower the severity.ro Counter32 .1.3.6.1.4.1.9.6.1.101.82.2.11 |
rlSyslogFileMessagesLoggedThis is a count of all the messages currently held in the Log file.ro Counter32 .1.3.6.1.4.1.9.6.1.101.82.2.12 |
rlSyslogCacheTotalMessagesThis is a count of all the messages currently held in the cache.ro Counter32 .1.3.6.1.4.1.9.6.1.101.82.2.13 |
rlSyslogAggregationEnableenable/disable Syslog aggregationrw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.6.1.101.82.2.14 |
rlSyslogAggregationAgingTimeaging time for Syslog aggregated messagesrw Unsigned32 .1.3.6.1.4.1.9.6.1.101.82.2.15 |
rlSyslogMinLogToWebSeverityThe minimal severity to log to WEB client. Lower severity will not be displayed in WEB client. Value notActive indicate this activity is disabled.rw RlSyslogSeverity .1.3.6.1.4.1.9.6.1.101.82.2.16 |
rlSyslogAlarmFlagThe MIB is initiated by false and it is set to true every time when a syslog message with severity >= min_severity_to_alarm_threshold (host parameter) is generated.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.6.1.101.82.2.17 |
rlSyslogOriginIdDefines the origin field of the SYSLOG message packets sent to the SYSLOG serverrw Enumeration .1.3.6.1.4.1.9.6.1.101.82.2.18 |
rlSyslogOriginIdStringDefines the string origin of the SYSLOG message packets sent to the SYSLOG serverrw DisplayString .1.3.6.1.4.1.9.6.1.101.82.2.19 |
rlSyslogHeaderSendingEnabledEnabled sending/not sending of syslog header in syslog messages to syslog collectors.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.6.1.101.82.2.20 |
rlSyslogPhaseOneTests OBJECT IDENTIFIER .1.3.6.1.4.1.9.6.1.101.82.3 |
rlSyslogPhaseOneTestGeneratorWriting a value to this leaf results in a test being run on the host.rw Enumeration .1.3.6.1.4.1.9.6.1.101.82.3.1 |
More MIBs from Cisco
Browse all CiscoMIBs →The CISCO-ENTITY-VENDORTYPE-OID-MIB maps Cisco-specific hardware component identifiers to the ENTITY-MIB's entPhysicalTable, enabling precise differentiation of physical device types such as line cards, power supplies, and fans within Cisco infrastructure. This mapping ensures that SNMP management systems can accurately correlate physical inventory entries with vendor-specific component definitions for accurate device discovery and monitoring.
The CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB provides SNMP-based monitoring and management of Cisco Unified Computing System (UCS) hardware components, including chassis, blades, fabric interconnects, and power supplies. It exposes critical operational metrics such as device status, port states, temperature readings, fan speeds, and power consumption data for infrastructure health assessment.
The CISCO-UNIFIED-COMPUTING-ADAPTOR-MIB enables SNMP-based monitoring and management of physical and virtual network adapter interfaces, including link status, traffic counters, error statistics, and port configuration parameters, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers.
The CISCO-UNIFIED-COMPUTING-TC-MIB module defines standard textual conventions and data type definitions required for monitoring Cisco Unified Computing System (UCS) hardware components, including server blades, fabric interconnects, and chassis resources. These definitions enable consistent interpretation of specific UCS metrics such as power supply status, fan speeds, thermal readings, and port utilization across SNMP management applications.
The CISCO-UNIFIED-COMPUTING-FABRIC-MIB enables SNMP-based monitoring and management of the Cisco UCS Fabric Interconnects and associated fabric switching infrastructure, exposing metrics for port states, link utilization, error counters, and fabric topology status. It facilitates granular visibility into the physical and logical fabric layers, including uplink/downlink interfaces, VLAN configurations, and fabric failover conditions within the unified computing environment.
The STARENT-MIB module provides SNMP management and monitoring capabilities for Cisco ASR 5000 and ASR 5500 multimedia core platforms, specifically exposing metrics related to 2G/3G/4G and WiFi subscriber sessions, inline service states, and carrier-class high-availability status.