CiscoFlashDeviceEntry |
|
SEQUENCE |
|
|
|
|
ciscoFlashDeviceIndex |
Unsigned32 |
|
|
ciscoFlashDeviceSize |
Unsigned32 |
|
|
ciscoFlashDeviceMinPartitionSize |
Unsigned32 |
|
|
ciscoFlashDeviceMaxPartitions |
Unsigned32 |
|
|
ciscoFlashDevicePartitions |
Unsigned32 |
|
|
ciscoFlashDeviceChipCount |
Integer32 |
|
|
ciscoFlashDeviceName |
DisplayString |
|
|
ciscoFlashDeviceDescr |
DisplayString |
|
|
ciscoFlashDeviceController |
DisplayString |
|
|
ciscoFlashDeviceCard |
InstancePointer |
|
|
ciscoFlashDeviceProgrammingJumper |
INTEGER |
|
|
ciscoFlashDeviceInitTime |
TimeStamp |
|
|
ciscoFlashDeviceRemovable |
TruthValue |
|
|
ciscoFlashPhyEntIndex |
PhysicalIndex |
|
|
ciscoFlashDeviceNameExtended |
DisplayString |
|
|
ciscoFlashDeviceSizeExtended |
CounterBasedGauge64 |
|
|
ciscoFlashDeviceMinPartitionSizeExtended |
CounterBasedGauge64 |
|
CiscoFlashChipEntry |
|
SEQUENCE |
|
|
|
|
ciscoFlashChipIndex |
Integer32 |
|
|
ciscoFlashChipCode |
DisplayString |
|
|
ciscoFlashChipDescr |
DisplayString |
|
|
ciscoFlashChipWriteRetries |
Counter32 |
|
|
ciscoFlashChipEraseRetries |
Counter32 |
|
|
ciscoFlashChipMaxWriteRetries |
Unsigned32 |
|
|
ciscoFlashChipMaxEraseRetries |
Unsigned32 |
|
CiscoFlashPartitionEntry |
|
SEQUENCE |
|
|
|
|
ciscoFlashPartitionIndex |
Unsigned32 |
|
|
ciscoFlashPartitionStartChip |
Integer32 |
|
|
ciscoFlashPartitionEndChip |
Integer32 |
|
|
ciscoFlashPartitionSize |
Unsigned32 |
|
|
ciscoFlashPartitionFreeSpace |
Gauge32 |
|
|
ciscoFlashPartitionFileCount |
Gauge32 |
|
|
ciscoFlashPartitionChecksumAlgorithm |
INTEGER |
|
|
ciscoFlashPartitionStatus |
INTEGER |
|
|
ciscoFlashPartitionUpgradeMethod |
INTEGER |
|
|
ciscoFlashPartitionName |
DisplayString |
|
|
ciscoFlashPartitionNeedErasure |
TruthValue |
|
|
ciscoFlashPartitionFileNameLength |
Integer32 |
|
|
ciscoFlashPartitionSizeExtended |
CounterBasedGauge64 |
|
|
ciscoFlashPartitionFreeSpaceExtended |
CounterBasedGauge64 |
|
|
ciscoFlashPartitionLowSpaceNotifThreshold |
Percent |
|
CiscoFlashFileByTypeEntry |
|
SEQUENCE |
|
|
|
|
ciscoFlashFileByTypeSize |
Unsigned32 |
|
|
ciscoFlashFileByTypeChecksum |
ChecksumString |
|
|
ciscoFlashFileByTypeStatus |
INTEGER |
|
|
ciscoFlashFileByTypeName |
DisplayString |
|
|
ciscoFlashFileByTypeDate |
DateAndTime |
|
CiscoFlashCopyEntry |
|
SEQUENCE |
|
|
|
|
ciscoFlashCopySerialNumber |
Integer32 |
|
|
ciscoFlashCopyCommand |
INTEGER |
|
|
ciscoFlashCopyProtocol |
INTEGER |
|
|
ciscoFlashCopyServerAddress |
IpAddress |
|
|
ciscoFlashCopySourceName |
DisplayString |
|
|
ciscoFlashCopyDestinationName |
DisplayString |
|
|
ciscoFlashCopyRemoteUserName |
DisplayString |
|
|
ciscoFlashCopyStatus |
INTEGER |
|
|
ciscoFlashCopyNotifyOnCompletion |
TruthValue |
|
|
ciscoFlashCopyTime |
TimeTicks |
|
|
ciscoFlashCopyEntryStatus |
RowStatus |
|
|
ciscoFlashCopyVerify |
TruthValue |
|
|
ciscoFlashCopyServerAddrType |
InetAddressType |
|
|
ciscoFlashCopyServerAddrRev1 |
InetAddress |
|
|
ciscoFlashCopyRemotePassword |
DisplayString |
|
CiscoFlashPartitioningEntry |
|
SEQUENCE |
|
|
|
|
ciscoFlashPartitioningSerialNumber |
Integer32 |
|
|
ciscoFlashPartitioningCommand |
INTEGER |
|
|
ciscoFlashPartitioningDestinationName |
DisplayString |
|
|
ciscoFlashPartitioningPartitionCount |
Unsigned32 |
|
|
ciscoFlashPartitioningPartitionSizes |
DisplayString |
|
|
ciscoFlashPartitioningStatus |
INTEGER |
|
|
ciscoFlashPartitioningNotifyOnCompletion |
TruthValue |
|
|
ciscoFlashPartitioningTime |
TimeTicks |
|
|
ciscoFlashPartitioningEntryStatus |
RowStatus |
|
CiscoFlashMiscOpEntry |
|
SEQUENCE |
|
|
|
|
ciscoFlashMiscOpSerialNumber |
Integer32 |
|
|
ciscoFlashMiscOpCommand |
INTEGER |
|
|
ciscoFlashMiscOpDestinationName |
DisplayString |
|
|
ciscoFlashMiscOpStatus |
INTEGER |
|
|
ciscoFlashMiscOpNotifyOnCompletion |
TruthValue |
|
|
ciscoFlashMiscOpTime |
TimeTicks |
|
|
ciscoFlashMiscOpEntryStatus |
RowStatus |
|
ciscoFlashDeviceEntry |
1.3.6.1.4.1.9.9.10.1.1.2.1 |
An entry in the table of flash device properties for
each initialized flash device.
Each entry can be randomly accessed by using
ciscoFlashDeviceIndex as an index into the table.
Note that removable devices will have an entry in
the table even when they have been removed. However,
a non-removable device that has not been installed
will not have an entry in the table. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CiscoFlashDeviceEntry |
|
|
ciscoFlashDeviceMinPartitionSize |
1.3.6.1.4.1.9.9.10.1.1.2.1.3 |
This object will give the minimum partition size
supported for this device. For systems that execute code
directly out of Flash, the minimum partition size needs
to be the bank size. (Bank size is equal to the size of a
chip multiplied by the width of the device. In most cases,
the device width is 4 bytes, and so the bank size would be
four times the size of a chip). This has to be so because
all programming commands affect the operation of an
entire chip (in our case, an entire bank because all
operations are done on the entire width of the device)
even though the actual command may be localized to a small
portion of each chip. So when executing code out of Flash,
one needs to be able to write and erase some portion of
Flash without affecting the code execution.
For systems that execute code out of DRAM or ROM, it is
possible to partition Flash with a finer granularity (for
eg., at erase sector boundaries) if the system code supports
such granularity.
This object will let a management entity know the
minimum partition size as defined by the system.
If the system does not support partitioning, the value
will be equal to the device size in ciscoFlashDeviceSize.
The maximum number of partitions that could be configured
will be equal to the minimum of
ciscoFlashDeviceMaxPartitions
and
(ciscoFlashDeviceSize / ciscoFlashDeviceMinPartitionSize).
If the total size of the flash device is greater than the
maximum value reportable by this object then this object should
report its maximum value(4,294,967,295) and
ciscoFlashDeviceMinPartitionSizeExtended must be used to report
the flash device's minimum partition size. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Unsigned32 |
1..4294967295 |
|
ciscoFlashChipEntry |
1.3.6.1.4.1.9.9.10.1.1.3.1.1 |
An entry in the table of chip info for each
flash device initialized in the system.
An entry is indexed by two objects - the
device index and the chip index within that
device. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CiscoFlashChipEntry |
|
|
ciscoFlashPartitionEntry |
1.3.6.1.4.1.9.9.10.1.1.4.1.1 |
An entry in the table of flash partition properties
for each initialized flash partition. Each entry
will be indexed by a device number and a partition
number within the device. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CiscoFlashPartitionEntry |
|
|
ciscoFlashFileEntry |
1.3.6.1.4.1.9.9.10.1.1.4.2.1.1 |
An entry in the table of Flash file properties
for each initialized Flash partition. Each entry
represents a file and gives details about the file.
An entry is indexed using the device number,
partition number within the device, and file
number within the partition. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CiscoFlashFileEntry |
|
|
ciscoFlashFileByTypeEntry |
1.3.6.1.4.1.9.9.10.1.1.4.2.2.1 |
An entry in the table of Flash file properties
for each initialized Flash partition. Each entry
represents a file sorted by file type.
This table contains exactly the same set of rows
as are contained in the ciscoFlashFileTable but
in a different order, i.e., ordered by
the type of file, given by ciscoFlashFileType;
the device number, given by ciscoFlashDeviceIndex;
the partition number within the device, given by
ciscoFlashPartitionIndex;
the file number within the partition, given by
ciscoFlashFileIndex. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CiscoFlashFileByTypeEntry |
|
|
ciscoFlashCopyEntry |
1.3.6.1.4.1.9.9.10.1.2.1.1 |
A Flash copy operation entry. Each entry consists
of a command, a source, and optional parameters such
as protocol to be used, a destination, a server address,
etc.
A management station wishing to create an entry should
first generate a pseudo-random serial number to be used
as the index to this sparse table. The station should
then create the associated instance of the row status
object. It must also, either in the same or in successive
PDUs, create the associated instance of the command and
parameter objects. It should also modify the default values
for any of the parameter objects if the defaults are not
appropriate.
Once the appropriate instances of all the command
objects have been created, either by an explicit SNMP
set request or by default, the row status should be set
to active to initiate the operation. Note that this entire
procedure may be initiated via a single set request which
specifies a row status of createAndGo as well as specifies
valid values for the non-defaulted parameter objects.
Once an operation has been activated, it cannot be
stopped.
Once the operation completes, the management station should
retrieve the value of the status object (and time if
desired), and delete the entry. In order to prevent old
entries from clogging the table, entries will be aged out,
but an entry will never be deleted within 5 minutes of
completing. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CiscoFlashCopyEntry |
|
|
ciscoFlashCopyStatus |
1.3.6.1.4.1.9.9.10.1.2.1.1.8 |
The status of the specified copy operation.
copyOperationPending :
operation request is received and
pending for validation and process
copyInProgress :
specified operation is active
copyOperationSuccess :
specified operation is supported and
completed successfully
copyInvalidOperation :
command invalid or command-protocol-device
combination unsupported
copyInvalidProtocol :
invalid protocol specified
copyInvalidSourceName :
invalid source file name specified
For the copy from flash to lex operation, this
error code will be returned when the source file
is not a valid lex image.
copyInvalidDestName :
invalid target name (file or partition or
device name) specified
For the copy from flash to lex operation, this
error code will be returned when no lex devices
are connected to the router or when an invalid
lex interface number has been specified in
the destination string.
copyInvalidServerAddress :
invalid server address specified
copyDeviceBusy :
specified device is in use and locked by
another process
copyDeviceOpenError :
invalid device name
copyDeviceError :
device read, write or erase error
copyDeviceNotProgrammable :
device is read-only but a write or erase
operation was specified
copyDeviceFull :
device is filled to capacity
copyFileOpenError :
invalid file name; file not found in partition
copyFileTransferError :
file transfer was unsuccessfull; network failure
copyFileChecksumError :
file checksum in Flash failed
copyNoMemory :
system running low on memory
copyUnknownFailure :
failure unknown
copyProhibited:
stop user from overwriting current boot image file. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
INTEGER |
copyOperationPending(0), copyInProgress(1), copyOperationSuccess(2), copyInvalidOperation(3), copyInvalidProtocol(4), copyInvalidSourceName(5), copyInvalidDestName(6), copyInvalidServerAddress(7), copyDeviceBusy(8), copyDeviceOpenError(9), copyDeviceError(10), copyDeviceNotProgrammable(11), copyDeviceFull(12), copyFileOpenError(13), copyFileTransferError(14), copyFileChecksumError(15), copyNoMemory(16), copyUnknownFailure(17), copyInvalidSignature(18), copyProhibited(19) |
|
ciscoFlashCopyEntryStatus |
1.3.6.1.4.1.9.9.10.1.2.1.1.11 |
The status of this table entry. |
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
RowStatus |
|
|
ciscoFlashPartitioningEntry |
1.3.6.1.4.1.9.9.10.1.2.2.1 |
A Flash partitioning operation entry. Each entry
consists of the command, the target device, the
partition count, and optionally the partition sizes.
A management station wishing to create an entry should
first generate a pseudo-random serial number to be used
as the index to this sparse table. The station should
then create the associated instance of the row status
object. It must also, either in the same or in successive
PDUs, create the associated instance of the command and
parameter objects. It should also modify the default values
for any of the parameter objects if the defaults are not
appropriate.
Once the appropriate instances of all the command
objects have been created, either by an explicit SNMP
set request or by default, the row status should be set
to active to initiate the operation. Note that this entire
procedure may be initiated via a single set request which
specifies a row status of createAndGo as well as specifies
valid values for the non-defaulted parameter objects.
Once an operation has been activated, it cannot be
stopped.
Once the operation completes, the management station should
retrieve the value of the status object (and time if
desired), and delete the entry. In order to prevent old
entries from clogging the table, entries will be aged out,
but an entry will never be deleted within 5 minutes of
completing. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CiscoFlashPartitioningEntry |
|
|
ciscoFlashPartitioningStatus |
1.3.6.1.4.1.9.9.10.1.2.2.1.6 |
The status of the specified partitioning operation.
partitioningInProgress :
specified operation is active
partitioningOperationSuccess :
specified operation is supported and completed
successfully
partitioningInvalidOperation :
command invalid or command-protocol-device
combination unsupported
partitioningInvalidDestName :
invalid target name (file or partition or
device name) specified
partitioningInvalidPartitionCount :
invalid partition count specified for the
partitioning command
partitioningInvalidPartitionSizes :
invalid partition size, or invalid count of
partition sizes
partitioningDeviceBusy :
specified device is in use and locked by
another process
partitioningDeviceOpenError :
invalid device name
partitioningDeviceError :
device read, write or erase error
partitioningNoMemory :
system running low on memory
partitioningUnknownFailure :
failure unknown |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
INTEGER |
partitioningInProgress(1), partitioningOperationSuccess(2), partitioningInvalidOperation(3), partitioningInvalidDestName(4), partitioningInvalidPartitionCount(5), partitioningInvalidPartitionSizes(6), partitioningDeviceBusy(7), partitioningDeviceOpenError(8), partitioningDeviceError(9), partitioningNoMemory(10), partitioningUnknownFailure(11) |
|
ciscoFlashPartitioningEntryStatus |
1.3.6.1.4.1.9.9.10.1.2.2.1.9 |
The status of this table entry. |
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
RowStatus |
|
|
ciscoFlashMiscOpEntry |
1.3.6.1.4.1.9.9.10.1.2.3.1 |
A Flash operation entry. Each entry consists of a
command, a target, and any optional parameters.
A management station wishing to create an entry should
first generate a pseudo-random serial number to be used
as the index to this sparse table. The station should
then create the associated instance of the row status
object. It must also, either in the same or in successive
PDUs, create the associated instance of the command and
parameter objects. It should also modify the default values
for any of the parameter objects if the defaults are not
appropriate.
Once the appropriate instances of all the command
objects have been created, either by an explicit SNMP
set request or by default, the row status should be set
to active to initiate the operation. Note that this entire
procedure may be initiated via a single set request which
specifies a row status of createAndGo as well as specifies
valid values for the non-defaulted parameter objects.
Once an operation has been activated, it cannot be
stopped.
Once the operation completes, the management station should
retrieve the value of the status object (and time if
desired), and delete the entry. In order to prevent old
entries from clogging the table, entries will be aged out,
but an entry will never be deleted within 5 minutes of
completing. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CiscoFlashMiscOpEntry |
|
|
ciscoFlashMiscOpStatus |
1.3.6.1.4.1.9.9.10.1.2.3.1.4 |
The status of the specified operation.
miscOpInProgress :
specified operation is active
miscOpOperationSuccess :
specified operation is supported and completed
successfully
miscOpInvalidOperation :
command invalid or command-protocol-device
combination unsupported
miscOpInvalidDestName :
invalid target name (file or partition or
device name) specified
miscOpDeviceBusy :
specified device is in use and locked by another
process
miscOpDeviceOpenError :
invalid device name
miscOpDeviceError :
device read, write or erase error
miscOpDeviceNotProgrammable :
device is read-only but a write or erase
operation was specified
miscOpFileOpenError :
invalid file name; file not found in partition
miscOpFileDeleteFailure :
file could not be deleted; delete count exceeded
miscOpFileUndeleteFailure :
file could not be undeleted; undelete count
exceeded
miscOpFileChecksumError :
file has a bad checksum
miscOpNoMemory :
system running low on memory
miscOpUnknownFailure :
failure unknown
miscOpSqueezeFailure :
the squeeze operation failed
miscOpNoSuchFile :
a valid but nonexistent file name was specified
miscOpFormatFailure :
the format operation failed |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
INTEGER |
miscOpInProgress(1), miscOpOperationSuccess(2), miscOpInvalidOperation(3), miscOpInvalidDestName(4), miscOpDeviceBusy(5), miscOpDeviceOpenError(6), miscOpDeviceError(7), miscOpDeviceNotProgrammable(8), miscOpFileOpenError(9), miscOpFileDeleteFailure(10), miscOpFileUndeleteFailure(11), miscOpFileChecksumError(12), miscOpNoMemory(13), miscOpUnknownFailure(14), miscOpSqueezeFailure(18), miscOpNoSuchFile(19), miscOpFormatFailure(20) |
|
ciscoFlashMiscOpEntryStatus |
1.3.6.1.4.1.9.9.10.1.2.3.1.7 |
The status of this table entry. |
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
RowStatus |
|
|