Enterasys Configuration Change Mib - Enterasys Security Router X-PeditionTM User Manual

Enterasys Configuration Change MIB

Table B-43 etsysConfigurationManagement (continued)
Field
etsysConfigMgmtChangeNextAvailableIndex
sysConfigMgmtPersistentStorageChSum
Enterasys Configuration Change MIB
The Enterasys Configuration Change MIB supports parameters for SNMP management entities to
determine if and when configuration changes have occurred. Refer to the supported fields in the
following table.
Table B-44 etsysConfigurationChange MIB
Field
etsysConfigChangeNonVolatile Group
etsysConfigChangeNonVolatileCount
etsysConfigChangeNonVolatileTime
etsysConfigChangeNonVolatileMethod
etsysConfigChangeVolatile Group
etsysConfigChangeVolatileCount
etsysConfigChangeVolatileTime
etsysConfigChangeVolatileMethod
etsysConfigChangeFirmware Group
etsysConfigChangeFirmwareCount
etsysConfigChangeFirmwareTime
etsysConfigChangeFirmwareMethod
Conformance Information
etsysConfigChangeNonVolatileGroup
etsysConfigChangeVolatileGroup
B-20 XSR SNMP Proprietary and Associated Standard MIBs
Description
The numerically lowest available index within the XSR, which may be used
for the value of etsysConfigMgmtChangeIndex in the creation of a new
entry in the etsysConfigMgmtChangeTable.
The MD5 message digest of the content of the following files will be stored
in this field: startup-config, private-config, user.dat.
Initially when the device comes up we calculate the MD5 message digest
for those files and store them in this field, then this field get updated upon
any changes to the content of those files.
Description
The number of successful non-volatile, or persistent configuration changes.
The date and time of the last successful non-volatile, or persistent, configuration
change.
The method used to make the last non-volatile change. That is, SNMP, TELNET,
and CLI. If the individual user login or source IP address is available, they should
be included in this string.
Example format: <TELNET: 192.168.0.1: JohnJones>
Sum of successful volatile, or non-persistent, configuration changes.
The date and time of the last successful volatile, or non-persistent, configuration
change.
The method used to make the last volatile change. i.e.: SNMP, TELNET, LM, CLI.
If the individual user login, or source IP address, is available they should be
included in this string.
Example format: <TELNET: 192.168.0.1: JohnJones>
The number of successful firmware image downloads:
etsysConfigChangeFirmware 1
The date and time of the last successful firmware image download.
The method that was used to cause the last firmware change. i.e. SNMP,
TELNET, LM, CLI. If the individual user login, or the source IP address, is available
they are included in this string.
example format: <TELNET: 192.168.0.1: JohnJones>
A collection of objects providing non-volatile configuration change data.
A collection of objects providing volatile configuration change data.