CISCO-SYS-INFO-LOG-MIB
The CISCO-SYS-INFO-LOG-MIB manages the periodic execution of CLI commands on Cisco IOS devices and configures the destination for storing the resulting output logs. It monitors the operational status of the system information logging feature, including command schedules, execution counts, and remote file transfer parameters.
Imported Objects
Objects
35 total| Object Name |
|---|
ciscoSysInfoLogMIBThis MIB provides the configuration of System Information
Logging feature, which allows a certain number of commands
to be executed periodically via command line interface,
and stores the result into a file on a configured server. MODULE-IDENTITY .1.3.6.1.4.1.9.9.330 |
IMPORTSThis MIB provides the configuration of System Information
Logging feature, which allows a certain number of commands
to be executed periodically via command line interface,
and stores the result into a file on a configured server. Unknown .1.3.6.1.4.1.9.9.330 |
ciscoSysInfoLogMIBNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.330.0 |
csilLoggingFailNotifA csilLoggingFailNotif is sent for an unsuccessful system
information logging process, specifically when value of
csilServerLastStatus is changed to any one of the failure
states (2, 3, 4, 5, 6 and 8). NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.330.0.1 |
ciscoSysInfoLogMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.330.1 |
csilGlobalConfig OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.330.1.1 |
csilSysInfoLogEnabledSpecifies whether System Information Logging has been
enabled in the system or not.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.330.1.1.1 |
csilSysInfoLogNotifEnabledThis object controls whether notifications will be generated
by system logging process or not.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.330.1.1.2 |
csilServerConfig OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.330.1.2 |
csilMaxServerAllowedSpecifies the maximum number of entries that can be configured
in csilServerTable. A value of zero indicates no limit on the
numbers of entries in the csilServerTable.rw Unsigned32 .1.3.6.1.4.1.9.9.330.1.2.1 |
csilMaxProfilePerServerAllowedIndicates the maximum number of command profiles allowed to
configure for a logging server. A profile defines a set of
commands that will be used for system information logging
purpose.ro Unsigned32 UNITS "profiles" .1.3.6.1.4.1.9.9.330.1.2.2 |
csilServerTableA table of servers used to keep the data files for System
Information Logging purpose. SEQUENCE OF CsilServerEntry .1.3.6.1.4.1.9.9.330.1.2.3 |
csilServerEntryInformation about a server to keep the data file for System
Information Logging purpose. Entries in this table can be
created or deleted using csilServerRowStatus object. CsilServerEntry .1.3.6.1.4.1.9.9.330.1.2.3.1 |
csilServerIndexAn arbitrary index assigned by the NMS to identify the
entry. Maximum value of this object is limited by the
value of csilMaxServerAllowed. Unsigned32 .1.3.6.1.4.1.9.9.330.1.2.3.1.1 |
csilServerAddressTypeSpecifies the type of address used to determine the address
of the server to be used for logging system information.rw InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.330.1.2.3.1.2 |
csilServerAddressSpecifies the address of the remote host used for logging
system information.rw InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.330.1.2.3.1.3 |
csilServerProfileIndexSpecifies the profile assigned to this server. A profile is a
set of specific commands defined in csilCommandConfigTable,
which will be executed in the period specified by the object
csilServerInterval for logging system information to the
server.rw Unsigned32 .1.3.6.1.4.1.9.9.330.1.2.3.1.4 |
csilServerProtocolSpecifies the file transfer protocol to be used for logging
system information.
- tftp(1): indicates that tftp is used for logging system
information.
- rcp(2): indicates that rcp is used for logging system
information.
- ftp(3): indicates that ftp is used for logging system
information.rw Enumeration .1.3.6.1.4.1.9.9.330.1.2.3.1.5 |
csilServerRcpUserNameSpecifies the remote user name used to download system
information via RCP protocol. This object must be set when
csilServerProtocol is set to rcp(2). This object will have
no effect for protocols other than RCP.rw SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.330.1.2.3.1.6 |
csilServerIntervalA period of time, measured in unit of minutes. This object
specifies how often the command set is executed for
logging system information.rw Unsigned32 UNITS "minutes" .1.3.6.1.4.1.9.9.330.1.2.3.1.7 |
csilServerLoggingFileNameSpecifies the file name used for logging system
information.rw SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.330.1.2.3.1.8 |
csilServerLastStatusIndicates the status of the last system information
logging process into the server.
- none(1): initial state. No process has been started.
- noLogFile(2): there is no log file has been configured.
- noCommand(3): there is no command has been configured.
- linkBlock(4): another process might have taken the
rcp or tftp connection at the time the interval
is due.
- authError(5): authentication failed.
- addrError(6): an error occurs due to the destination
address is not reachable.
- copying(7) : logging process to destination server is
in progress.
- writeError(8): an error occurs while copying logging
information to the server.
- success(9): logging process completed successfully.
- ftpError(10): an error occurs during ftp operation.ro Enumeration .1.3.6.1.4.1.9.9.330.1.2.3.1.9 |
csilServerRowStatusThis object is used to manage the creation, modification
and deletion of rows in the table.
Except of csilServerRcpUserName, all other objects need to
be set before csilServerRowStatus can be set to 'active'.
When this object is set to be 'active', the entry can not be
modified.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.330.1.2.3.1.10 |
csilCommandConfig OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.330.1.3 |
csilMaxCommandPerProfileSpecifies the maximum commands allowed in a profile. A
value of zero indicates no limitation on the number of
commands allowed in a profile.rw Unsigned32 .1.3.6.1.4.1.9.9.330.1.3.1 |
csilCommandsTableA table of commands for System Information Logging
purpose. SEQUENCE OF CsilCommandsEntry .1.3.6.1.4.1.9.9.330.1.3.2 |
csilCommandsEntryAn entry contains the command logging information regarding
a profile and a command index combination. Entries in this
table can be created or deleted using csilCommandStatus
object. CsilCommandsEntry .1.3.6.1.4.1.9.9.330.1.3.2.1 |
csilCommandProfileIndexAn arbitrary index assigned by NMS to uniquely identify a
profile. A profile contains a set of commands that will be
executed periodically for the purpose of logging system
information. Unsigned32 .1.3.6.1.4.1.9.9.330.1.3.2.1.1 |
csilCommandIndexAn arbitrary index assigned by NMS, which is combined with
the value of csilCommandProfileIndex object to uniquely
identify an entry. Unsigned32 .1.3.6.1.4.1.9.9.330.1.3.2.1.2 |
csilCommandStringSpecifies the command to be executed.rw SnmpAdminString .1.3.6.1.4.1.9.9.330.1.3.2.1.3 |
csilCommandExecOrderSpecifies the order in which the command specified in the
object csilCommandLog will be executed periodically for
loging system information. Value of this object need not to
be consistent as it can be changed during the configuration
of the command set. Execution order of commands in the
lower part of the list will be moved up or pushed down when
a command is removed from or inserted to a position in the
middle of the list, respectively. For example, there is a
list of three commands 'show A', 'show B' and 'show C' with
the execution orders as 1, 2 and 3 respectively. If 'show
B' is removed from the list, the execution order of 'show
C' will be changed from 3 to 2. If 'show D' is added to the
list with the execution order as 2, the execution order of
'show B' and 'show C' will be changed to 3 and 4,
respectively.
Execution order of new commands appended to the list must be
continuous with the execution order of the last existing
command on the list, otherwise it will be rejected.rw Unsigned32 .1.3.6.1.4.1.9.9.330.1.3.2.1.4 |
csilCommandStatusThis object is used to manage the creation, modification and
deletion of rows in this table.
Value of this object can be set to 'active' only when value of
other columns have been assigned. The entry may not be
modified when value of this object is 'active'.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.330.1.3.2.1.5 |
ciscoSysInfoLogMIBConform OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.330.2 |
ciscoSysInfoLogMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.330.2.1 |
ciscoSysInfoLogMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.330.2.2 |
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.