CISCO-CONFIG-MAN-MIB.mib object view, vendor Cisco
Introduction
Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2024 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers).
This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.
ActiveXperts Network Monitor 2024 can import MIB file CISCO-CONFIG-MAN-MIB and use it to monitor vendor specific OID's.
CISCO-CONFIG-MAN-MIB file content
Object view of CISCO-CONFIG-MAN-MIB:
| Scalar Object |
| ccmHistoryRunningLastChanged |
.1.3.6.1.4.1.9.9.43.1.1.1 |
|
The value of sysUpTime when the running configuration
was last changed.
If the value of ccmHistoryRunningLastChanged is greater than
ccmHistoryRunningLastSaved, the configuration has been
changed but not saved.
|
| ccmHistoryRunningLastSaved |
.1.3.6.1.4.1.9.9.43.1.1.2 |
|
The value of sysUpTime when the running configuration
was last saved (written).
If the value of ccmHistoryRunningLastChanged is greater than
ccmHistoryRunningLastSaved, the configuration has been
changed but not saved.
What constitutes a safe saving of the running
configuration is a management policy issue beyond the
scope of this MIB. For some installations, writing the
running configuration to a terminal may be a way of
capturing and saving it. Others may use local or
remote storage. Thus ANY write is considered saving
for the purposes of the MIB.
|
| ccmHistoryStartupLastChanged |
.1.3.6.1.4.1.9.9.43.1.1.3 |
|
The value of sysUpTime when the startup configuration
was last written to. In general this is the
default configuration used when cold starting the
system. It may have been changed by a save of the
running configuration or by a copy from elsewhere.
|
| ccmHistoryMaxEventEntries |
.1.3.6.1.4.1.9.9.43.1.1.4 |
|
The maximum number of entries that can be held in
ccmHistoryEventTable.
The recommended value for implementations is 10.
|
| ccmHistoryEventEntriesBumped |
.1.3.6.1.4.1.9.9.43.1.1.5 |
|
The number of times the oldest entry in ccmHistoryEventTable
was deleted to make room for a new entry.
|
| ccmHistoryEventEntry |
.1.3.6.1.4.1.9.9.43.1.1.6.1 |
|
Information about a configuration event on this router.
|
| Tabular Object |
| ccmHistoryEventIndex |
.1.3.6.1.4.1.9.9.43.1.1.6.1.1 |
|
A monotonically increasing integer for the sole purpose of
indexing events. When it reaches the maximum value, an
extremely unlikely event, the agent wraps the value back
to 1 and may flush existing entries.
|
| ccmHistoryEventTime |
.1.3.6.1.4.1.9.9.43.1.1.6.1.2 |
|
The value of sysUpTime when the event occurred.
|
| ccmHistoryEventCommandSource |
.1.3.6.1.4.1.9.9.43.1.1.6.1.3 |
|
The source of the command that instigated the event.
|
| ccmHistoryEventConfigSource |
.1.3.6.1.4.1.9.9.43.1.1.6.1.4 |
|
The configuration data source for the event.
|
| ccmHistoryEventConfigDestination |
.1.3.6.1.4.1.9.9.43.1.1.6.1.5 |
|
The configuration data destination for the event.
|
| ccmHistoryEventTerminalType |
.1.3.6.1.4.1.9.9.43.1.1.6.1.6 |
|
If ccmHistoryEventCommandSource is 'commandLine',
the terminal type, otherwise 'notApplicable'.
|
| ccmHistoryEventTerminalNumber |
.1.3.6.1.4.1.9.9.43.1.1.6.1.7 |
|
If ccmHistoryEventCommandSource is 'commandLine',
the terminal number. The value is -1 if not available
or not applicable.
|
| ccmHistoryEventTerminalUser |
.1.3.6.1.4.1.9.9.43.1.1.6.1.8 |
|
If ccmHistoryEventCommandSource is 'commandLine',
the name of the logged in user. The length is zero if
not available or not applicable.
|
| ccmHistoryEventTerminalLocation |
.1.3.6.1.4.1.9.9.43.1.1.6.1.9 |
|
If ccmHistoryEventCommandSource is 'commandLine',
the hard-wired location of the terminal or the remote host
for an incoming connection. The length is zero if not
available or not applicable.
|
| ccmHistoryEventCommandSourceAddress |
.1.3.6.1.4.1.9.9.43.1.1.6.1.10 |
|
If ccmHistoryEventTerminalType is 'virtual', the internet
address of the connected system.
If ccmHistoryEventCommandSource is 'snmp', the internet
address of the requester.
The value is 0.0.0.0 if not available or not applicable.
|
| ccmHistoryEventVirtualHostName |
.1.3.6.1.4.1.9.9.43.1.1.6.1.11 |
|
If ccmHistoryEventTerminalType is 'virtual', the host
name of the connected system. The length is zero if
not available or not applicable.
|
| ccmHistoryEventServerAddress |
.1.3.6.1.4.1.9.9.43.1.1.6.1.12 |
|
If ccmHistoryEventConfigSource or
ccmHistoryEventConfigDestination is 'networkTftp' or
'networkRcp', the internet address of the storage file
server. The value is 0.0.0.0 if not applicable or not
available.
|
| ccmHistoryEventFile |
.1.3.6.1.4.1.9.9.43.1.1.6.1.13 |
|
If ccmHistoryEventConfigSource or
ccmHistoryEventConfigDestination is 'networkTftp' or
'networkRcp', the configuration file name at the
storage file server. The length is zero if not
available or not applicable.
|
| ccmHistoryEventRcpUser |
.1.3.6.1.4.1.9.9.43.1.1.6.1.14 |
|
If ccmHistoryEventConfigSource or
ccmHistoryEventConfigDestination is 'networkRcp', the
remote user name. The length is zero if not applicable
or not available.
|
| Table |
| ccmHistoryEventTable |
.1.3.6.1.4.1.9.9.43.1.1.6 |
|
A table of configuration events on this router.
|
| Trap |
| ciscoConfigManEvent |
.1.3.6.1.4.1.9.9.43.2.0.1 |
|
Notification of a configuration management event as
recorded in ccmHistoryEventTable.
|
| Object Identifier |
| ciscoConfigManMIB |
.1.3.6.1.4.1.9.9.43 |
|
Configuration management MIB.
The MIB represents a model of configuration data that
exists in various locations:
running in use by the running system
terminal operator's mind or attached hardware
local saved locally in NVRAM or flash
remote saved to some server on the network
Although some of the system functions that relate here
can be used for general file storage and transfer, this
MIB intends to include only such operations as clearly
relate to configuration. Its primary emphasis is to
track changes and saves of the running configuration.
As saved data moves further from startup use, such as
into different local flash files or onto the network,
tracking becomes difficult to impossible, so the MIB's
interest and functions are confined in that area.
|
| ciscoConfigManMIBObjects |
.1.3.6.1.4.1.9.9.43.1 |
| ccmHistory |
.1.3.6.1.4.1.9.9.43.1.1 |
| ciscoConfigManMIBNotificationPrefix |
.1.3.6.1.4.1.9.9.43.2 |
| ciscoConfigManMIBNotifications |
.1.3.6.1.4.1.9.9.43.2.0 |
| ciscoConfigManMIBConformance |
.1.3.6.1.4.1.9.9.43.3 |
| ciscoConfigManMIBCompliances |
.1.3.6.1.4.1.9.9.43.3.1 |
| ciscoConfigManMIBGroups |
.1.3.6.1.4.1.9.9.43.3.2 |
| Group |
| ciscoConfigManHistoryGroup |
.1.3.6.1.4.1.9.9.43.3.2.1 |
|
Configuration history.
|
