Max number of partitions supported by the system for
this Flash device. Default will be 1, which actually
means that partitioning is not supported. Note that
this value will be defined by system limitations, not
by the flash device itself (for eg., the system may
impose a limit of 2 partitions even though the device
may be large enough to be partitioned into 4 based on
the smallest partition unit supported).
On systems that execute code out of Flash, partitioning
is a way of creating multiple file systems in the Flash
device so that writing into or erasing of one file system
can be done while executing code residing in another file
system.
For systems executing code out of DRAM, partitioning
gives a way of sub-dividing a large Flash device for
easier management of files.
Parsed from file CISCO-FLASH-MIB.mib
Module: CISCO-FLASH-MIB
Max number of partitions supported by the system for
this Flash device. Default will be 1, which actually
means that partitioning is not supported. Note that
this value will be defined by system limitations, not
by the flash device itself (for eg., the system may
impose a limit of 2 partitions even though the device
may be large enough to be partitioned into 4 based on
the smallest partition unit supported).
On systems that execute code out of Flash, partitioning
is a way of creating multiple file systems in the Flash
device so that writing into or erasing of one file system
can be done while executing code residing in another file
system.
For systems executing code out of DRAM, partitioning
gives a way of sub-dividing a large Flash device for
easier management of files.
ciscoFlashDeviceMaxPartitions OBJECT-TYPE
SYNTAX Integer32 (1..8)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Max number of partitions supported by the system for
this Flash device. Default will be 1, which actually
means that partitioning is not supported. Note that
this value will be defined by system limitations, not
by the flash device itself (for eg., the system may
impose a limit of 2 partitions even though the device
may be large enough to be partitioned into 4 based on
the smallest partition unit supported).
On systems that execute code out of Flash, partitioning
is a way of creating multiple file systems in the Flash
device so that writing into or erasing of one file system
can be done while executing code residing in another file
system.
For systems executing code out of DRAM, partitioning
gives a way of sub-dividing a large Flash device for
easier management of files.
"
View at oid-info.com
Max number of partitions supported by the system for
this Flash device. Default will be 1, which actually
means that partitioning is not supported. Note that
this value will be defined by system limitations, not
by the flash device itself (for eg., the system may
impose a limit of 2 partitions even though the device
may be large enough to be partitioned into 4 based on
the smallest partition unit supported).
On systems that execute code out of Flash, partitioning
is a way of creating multiple file systems in the Flash
device so that writing into or erasing of one file system
can be done while executing code residing in another file
system.
For systems executing code out of DRAM, partitioning
gives a way of sub-dividing a large Flash device for
easier management of files.
Parsed from file cisco-flash.mib.txt
Company: None
Module: CISCO-FLASH-MIB
Max number of partitions supported by the system for
this Flash device. Default will be 1, which actually
means that partitioning is not supported. Note that
this value will be defined by system limitations, not
by the flash device itself (for eg., the system may
impose a limit of 2 partitions even though the device
may be large enough to be partitioned into 4 based on
the smallest partition unit supported).
On systems that execute code out of Flash, partitioning
is a way of creating multiple file systems in the Flash
device so that writing into or erasing of one file system
can be done while executing code residing in another file
system.
For systems executing code out of DRAM, partitioning
gives a way of sub-dividing a large Flash device for
easier management of files.
ciscoFlashDeviceMaxPartitions OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Max number of partitions supported by the system for this Flash device. Default will be 1, which actually means that partitioning is not supported. Note that this value will be defined by system limitations, not by the flash device itself (for eg., the system may impose a limit of 2 partitions even though the device may be large enough to be partitioned into 4 based on the smallest partition unit supported). On systems that execute code out of Flash, partitioning is a way of creating multiple file systems in the Flash device so that writing into or erasing of one file system can be done while executing code residing in another file system. For systems executing code out of DRAM, partitioning gives a way of sub-dividing a large Flash device for easier management of files." ::= { ciscoFlashDeviceEntry 4 }
ciscoFlashDeviceMaxPartitions OBJECT-TYPE SYNTAX Gauge ACCESS read-only STATUS mandatory DESCRIPTION "Max number of partitions supported by the system for this Flash device. Default will be 1, which actually means that partitioning is not supported. Note that this value will be defined by system limitations, not by the flash device itself (for eg., the system may impose a limit of 2 partitions even though the device may be large enough to be partitioned into 4 based on the smallest partition unit supported). On systems that execute code out of Flash, partitioning is a way of creating multiple file systems in the Flash device so that writing into or erasing of one file system can be done while executing code residing in another file system. For systems executing code out of DRAM, partitioning gives a way of sub-dividing a large Flash device for easier management of files." ::= { ciscoFlashDeviceEntry 4 }
Automatically extracted from Cisco "SNMP v2 MIBs".
ciscoFlashDeviceMaxPartitions OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Max number of partitions supported by the system for this Flash device. Default will be 1, which actually means that partitioning is not supported. Note that this value will be defined by system limitations, not by the flash device itself (for eg., the system may impose a limit of 2 partitions even though the device may be large enough to be partitioned into 4 based on the smallest partition unit supported). On systems that execute code out of Flash, partitioning is a way of creating multiple file systems in the Flash device so that writing into or erasing of one file system can be done while executing code residing in another file system. For systems executing code out of DRAM, partitioning gives a way of sub-dividing a large Flash device for easier management of files. " ::= { ciscoFlashDeviceEntry 4 }
ciscoFlashDeviceMaxPartitions OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Max number of partitions supported by the system for this Flash device. Default will be 1, which actually means that partitioning is not supported. Note that this value will be defined by system limitations, not by the flash device itself (for eg., the system may impose a limit of 2 partitions even though the device may be large enough to be partitioned into 4 based on the smallest partition unit supported). On systems that execute code out of Flash, partitioning is a way of creating multiple file systems in the Flash device so that writing into or erasing of one file system can be done while executing code residing in another file system. For systems executing code out of DRAM, partitioning gives a way of sub-dividing a large Flash device for easier management of files." ::= { ciscoFlashDeviceEntry 4 }
| 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.3 | ciscoFlashDeviceMinPartitionSize | 0 | 0 | This object will give the minimum partition size supported for this device. For systems that execute code directly out of Flash, … |
| 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… |