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).
Parsed from file CISCO-FLASH-MIB.mib
Module: CISCO-FLASH-MIB
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.
ciscoFlashDeviceMinPartitionSize OBJECT-TYPE
SYNTAX Integer32
UNITS "bytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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).
"
View at oid-info.com
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).
Parsed from file cisco-flash.mib.txt
Company: None
Module: CISCO-FLASH-MIB
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.
ciscoFlashDeviceMinPartitionSize OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) UNITS "bytes" MAX-ACCESS read-only STATUS current DESCRIPTION "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)." ::= { ciscoFlashDeviceEntry 3 }
ciscoFlashDeviceMinPartitionSize OBJECT-TYPE SYNTAX Gauge(1..4294967295) ACCESS read-only STATUS mandatory DESCRIPTION "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." ::= { ciscoFlashDeviceEntry 3 }
Automatically extracted from Cisco "SNMP v2 MIBs".
ciscoFlashDeviceMinPartitionSize OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) UNITS "bytes" MAX-ACCESS read-only STATUS current DESCRIPTION "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). " ::= { ciscoFlashDeviceEntry 3 }
ciscoFlashDeviceMinPartitionSize OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) UNITS "bytes" MAX-ACCESS read-only STATUS current DESCRIPTION "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." ::= { ciscoFlashDeviceEntry 3 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.10.1.1.2.1.1 | ciscoFlashDeviceIndex | 0 | 0 | Flash device sequence number to index within the table of initialized flash devices. The lowest value should be 1. The highest sh… |
| 1.3.6.1.4.1.9.9.10.1.1.2.1.2 | ciscoFlashDeviceSize | 0 | 0 | Total size of the Flash device. For a removable device, the size will be zero if the device has been removed. |
| 1.3.6.1.4.1.9.9.10.1.1.2.1.4 | ciscoFlashDeviceMaxPartitions | 0 | 0 | Max number of partitions supported by the system for this Flash device. Default will be 1, which actually means that partitioning… |
| 1.3.6.1.4.1.9.9.10.1.1.2.1.5 | ciscoFlashDevicePartitions | 0 | 0 | Flash device partitions actually present. Number of partitions cannot exceed the minimum of ciscoFlashDeviceMaxPartitions and (cisc… |
| 1.3.6.1.4.1.9.9.10.1.1.2.1.6 | ciscoFlashDeviceChipCount | 0 | 0 | Total number of chips within the Flash device. The purpose of this object is to provide information upfront to a management stati… |
| 1.3.6.1.4.1.9.9.10.1.1.2.1.7 | ciscoFlashDeviceName | 0 | 0 | Flash device name. This name is used to refer to the device within the system. Flash operations get directed to a device based on… |
| 1.3.6.1.4.1.9.9.10.1.1.2.1.8 | ciscoFlashDeviceDescr | 0 | 0 | Description of a Flash device. The description is meant to explain what the Flash device and its purpose is. Current values are: S… |
| 1.3.6.1.4.1.9.9.10.1.1.2.1.9 | ciscoFlashDeviceController | 0 | 0 | Flash device controller. The h/w card that actually controls Flash read/write/erase. Relevant for the AGS+ systems where Flash ma… |
| 1.3.6.1.4.1.9.9.10.1.1.2.1.10 | ciscoFlashDeviceCard | 0 | 0 | This object will point to an instance of a card entry in the cardTable. The card entry will give details about the card on which … |
| 1.3.6.1.4.1.9.9.10.1.1.2.1.11 | ciscoFlashDeviceProgrammingJumper | 0 | 0 | This object gives the state of a jumper (if present and can be determined) that controls the programming voltage called Vpp to th… |
| 1.3.6.1.4.1.9.9.10.1.1.2.1.12 | ciscoFlashDeviceInitTime | 0 | 0 | System time at which device was initialized. For fixed devices, this will be the system time at boot up. For removable devices, it… |
| 1.3.6.1.4.1.9.9.10.1.1.2.1.13 | ciscoFlashDeviceRemovable | 0 | 0 | Whether Flash device is removable. Generally, only PCMCIA Flash cards will be treated as removable. Socketed Flash chips and Flas… |
| 1.3.6.1.4.1.9.9.10.1.1.2.1.14 | ciscoFlashPhyEntIndex | 0 | 0 | This object indicates the physical entity index of a physical entity in entPhysicalTable which the flash device actually located. |
| 1.3.6.1.4.1.9.9.10.1.1.2.1.15 | ciscoFlashDeviceNameExtended | 0 | 0 | Extended Flash device name whose size can be upto 255 characters. This name is used to refer to the device within the system. Fla… |
| 1.3.6.1.4.1.9.9.10.1.1.2.1.16 | ciscoFlashDeviceSizeExtended | 0 | 0 | Total size of the Flash device. For a removable device, the size will be zero if the device has been removed. This object is a 64-… |
| 1.3.6.1.4.1.9.9.10.1.1.2.1.17 | ciscoFlashDeviceMinPartitionSizeExtended | 0 | 0 | This object provides the minimum partition size supported for this device. This object is a 64-bit version of ciscoFlashDeviceMin… |