1-- ***************************************************************** 2-- CISCO-FLASH-MIB.my: Cisco Flash MIB file 3-- 4-- April 1995, Ashwin Baindur 5-- 6-- Copyright (c) 1995-2009, 2011, 2013, 2018 by cisco Systems Inc. 7-- All rights reserved. 8-- ***************************************************************** 9 10CISCO-FLASH-MIB DEFINITIONS ::= BEGIN 11 12IMPORTS 13 MODULE-IDENTITY, 14 OBJECT-TYPE, 15 NOTIFICATION-TYPE, 16 IpAddress, 17 Integer32, 18 Unsigned32, 19 Gauge32, 20 Counter32, 21 TimeTicks 22 FROM SNMPv2-SMI 23 MODULE-COMPLIANCE, 24 OBJECT-GROUP, 25 NOTIFICATION-GROUP 26 FROM SNMPv2-CONF 27 TEXTUAL-CONVENTION, 28 DisplayString, 29 TruthValue, 30 TimeStamp, 31 InstancePointer, 32 RowStatus, 33 DateAndTime 34 FROM SNMPv2-TC 35 PhysicalIndex 36 FROM ENTITY-MIB 37 InetAddressType, 38 InetAddress 39 FROM INET-ADDRESS-MIB 40 CounterBasedGauge64 41 FROM HCNUM-TC 42 Percent 43 FROM CISCO-QOS-PIB-MIB 44 ciscoMgmt 45 FROM CISCO-SMI; 46 47 48ciscoFlashMIB MODULE-IDENTITY 49 LAST-UPDATED "201308060000Z" 50 ORGANIZATION "Cisco Systems, Inc." 51 CONTACT-INFO 52 "Cisco Systems 53 Customer Service 54 55 Postal: 170 W. Tasman Drive 56 San Jose, CA 95134 57 USA 58 59 Tel: +1 800 553-NETS 60 61 E-mail: cs-snmp@cisco.com" 62 DESCRIPTION 63 "Added new object ciscoFlashDeviceChangeExtTrap 64 Added new object ciscoFlashDeviceInsertedExtNotif 65 Added new object ciscoFlashDeviceRemovedExtNotif 66 to support flash devices of sizes greater than 4 GB" 67 REVISION "201808140000Z" 68 DESCRIPTION 69 "This MIB provides for the management of Cisco 70 Flash Devices." 71 REVISION "201308060000Z" 72 DESCRIPTION 73 "Added new notification ciscoFlashPartitionLowSpaceNotif. 74 Added new notification ciscoFlashPartitionLowSpaceRecoveryNotif. 75 Added new object ciscoFlashPartitionLowSpaceNotifEnable. 76 Added new object ciscoFlashPartitionLowSpaceNotifThreshold. 77 Added new object group ciscoFlashPartitionInfoGroupRev1. 78 Added new notification group ciscoFlashNotifGroupRev3. 79 Added new compliance group ciscoFlashMIBComplianceRev11 which 80 deprecates ciscoFlashMIBComplianceRev10." 81 REVISION "201103160000Z" 82 DESCRIPTION 83 "Added ciscoFlashDeviceMinPartitionSizeExtended to support flash 84 devices of sizes greater than 4 GB. 85 86 Added new object group ciscoFlashDeviceInfoExtGroupSupRev1. 87 88 Added new compliance group ciscoFlashMIBComplianceRev10 which 89 deprecates ciscoFlashMIBComplianceRev9." 90 REVISION "200906030000Z" 91 DESCRIPTION 92 "Added 'copyProhibited' enum value to ciscoFlashCopyStatus object." 93 REVISION "200812080000Z" 94 DESCRIPTION 95 "Added ciscoFlashDeviceSizeExtended, 96 ciscoFlashPartitionFreeSpaceExtended and 97 ciscoFlashPartitionSizeExtended to support flash devices 98 of sizes greater than 4 GB." 99 REVISION "200703210000Z" 100 DESCRIPTION 101 "Added ciscoFlashFileTypeTable." 102 REVISION "200611080000Z" 103 DESCRIPTION 104 "DISPLAY-HINT for CheckSumString TEXTUAL CONVENTION 105 is changed from 'x' to '1x'." 106 REVISION "200506010000Z" 107 DESCRIPTION 108 "Added ciscoFlashFileDate to ciscoFlashFileTable 109 110 Added ciscoFlashCopyRemotePassword to 111 ciscoFlashCopyTable. 112 113 Added following enumerations to 114 ciscoFlashCopyProtocol - 115 ftp, scp, sftp." 116 REVISION "200501280000Z" 117 DESCRIPTION 118 "Added a new status copyOperationPending(0) 119 to object ciscoFlashCopyStatus." 120 REVISION "200403180000Z" 121 DESCRIPTION 122 "The object ciscoFlashCopyServerAddress is 123 deprecated since it supports only IPv4 address. Two 124 new objects ciscoFlashCopyServerAddrRev1 125 ciscoFlashCopyServerAddrType are defined." 126 REVISION "200304230000Z" 127 DESCRIPTION 128 "Added ciscoFlashDeviceNameExtended to support upto 129 255 characters in flash device name. 130 Deprecated ciscoFlashDeviceName." 131 REVISION "200301311234Z" 132 DESCRIPTION 133 "Add ciscoFlashCopyVerify object to 134 CiscoFlashCopyEntry, & ciscoFlashCopyOpGroup. 135 Fix scalability problem for the following tables and 136 MIB objects: ciscoFlashDevicesSupported, 137 ciscoFlashDeviceTable, ciscoFlashPhyEntIndex (added), 138 ciscoFlashPartitionTable and ciscoFlashFileTable." 139 REVISION "200204010000Z" 140 DESCRIPTION 141 "Added Notifications ciscoFlashDeviceInsertedNotif 142 and ciscoFlashDeviceRemovedNotif. Deprecated the 143 ciscoFlashDeviceChangeTrap. 144 Added Scalars ciscoFlashCfgDevInsNotifEnable and 145 ciscoFlashCfgDevRemNotifEnable to control the above 146 notifications." 147 REVISION "200201250000Z" 148 DESCRIPTION 149 "Added object ciscoFlashFileType to 150 ciscoFlashFileTable and 151 added FlashFileType as a TEXTUAL-CONVENTION." 152 REVISION "200201220000Z" 153 DESCRIPTION 154 "Fixing several problems with the previous 155 version of the MIB: 156 o Changing MAX-ACCESS of ciscoFlashDeviceIndex 157 back to 'not-accessible'. The change described 158 below in REVISION '200102211234Z' was not legal. 159 o Changing the definition of the 160 ciscoFlashDeviceChangeTrap notification. 161 The original definition of this notification include 162 a 'not-accessible' object (ciscoFlashDeviceIndex). 163 It will instead include the following objects: 164 ciscoFlashDeviceMinPartitionSize 165 ciscoFlashDeviceName 166 Instances of these object will carry the value of 167 ciscoFlashDeviceIndex implicitly in their object 168 identifiers. This change is being made without 169 deprecation of the notification and has the 170 potential to cause problems with existing 171 implementations of the notification on the agent 172 and the manager. 173 o Past versions of the MIB have had a incorrectly 174 formatted REVISION/DESCRIPTION section. That will 175 be corrected in this REVISION. 176 o Past versions of the MIB have not defined a 177 NOTIFICATION-GROUP for the notifications defined 178 by this MIB. That will be corrected in this 179 REVISION by adding ciscoFlashNotifGroup. This 180 group will be considered optional for 181 implementation. 182 o Gratuitous ranges specified in Entry definitions 183 have been removed." 184 REVISION "200102211234Z" 185 DESCRIPTION 186 "Change MAX-ACCESS of CiscoFlashDeviceIndex 187 from not-accessible to accessible-to-notfiy" 188 REVISION "9808270000Z" 189 DESCRIPTION 190 "Change ciscoFlashChipCode to match implementation, 191 and remove FlashChipCode as a TEXTUAL-CONVENTION." 192 REVISION "9604170000Z" 193 DESCRIPTION 194 "Add enumerations to objects in ciscoFlashMiscOpTable 195 to support formatting of flash devices." 196 REVISION "9510180000Z" 197 DESCRIPTION 198 "Add enumerations to a couple objects, and clarify 199 several object DESCRIPTIONs." 200 REVISION "9508150000Z" 201 DESCRIPTION 202 "Specify a correct (non-negative) range for several 203 index objects." 204 REVISION "9504290000Z" 205 DESCRIPTION 206 "Miscellaneous updates, including updated description of 207 ciscoFlashDeviceCard object." 208 REVISION "9501130000Z" 209 DESCRIPTION 210 "Initial version of Flash operations MIB module." 211 ::= { ciscoMgmt 10 } 212 213 214 215ChecksumString ::= TEXTUAL-CONVENTION 216 STATUS current 217 DESCRIPTION 218 "Represents the checksum of a file." 219 SYNTAX OCTET STRING 220 221FlashFileType ::= TEXTUAL-CONVENTION 222 STATUS current 223 DESCRIPTION 224 "File types for files in a flash. 225 226 unknown - file type is not one of the following. 227 config - configuration file like 228 startup configuration or 229 running configuration. 230 image - image file. 231 directory - directory entry. 232 crashinfo - file containing crashinfo." 233 SYNTAX INTEGER { 234 unknown(1), 235 config(2), 236 image(3), 237 directory(4), 238 crashinfo(5) 239 } 240ciscoFlashMIBObjects OBJECT IDENTIFIER 241 ::= { ciscoFlashMIB 1 } 242 243ciscoFlashDevice OBJECT IDENTIFIER 244 ::= { ciscoFlashMIBObjects 1 } 245 246ciscoFlashOps OBJECT IDENTIFIER 247 ::= { ciscoFlashMIBObjects 2 } 248 249ciscoFlashMIBTrapPrefix OBJECT IDENTIFIER 250 ::= { ciscoFlashMIBObjects 3 } 251 252ciscoFlashCfg OBJECT IDENTIFIER 253 ::= { ciscoFlashMIBObjects 4 } 254 255 256-- An overview 257-- 258-- This MIB is organized hierarchically as follows : 259-- Device information : 260-- * device level info 261-- * chip info 262-- * partition info 263-- * file info (for files within a partition) 264-- Operations : 265-- * copy operations 266-- * partitioning operations 267-- * miscellaneous operations 268-- Traps 269-- * operation completion traps 270-- * device change trap 271-- 272-- It is organized into the following groups : 273-- Information groups : 274-- Device info group (mandatory device information) 275-- Device optional info group 276-- The optional device information group contains objects 277-- that depend on optional system features, as well as on 278-- features that may be considered optional at the network 279-- management (NM) application level. 280-- Partition information group (mandatory) 281-- The partition information group contains objects related 282-- to a partition. Note that this group is essential since 283-- a device without explicit partitioning is considered to 284-- be a device with a single partition spanning the entire 285-- device. Such a model simplifies the view of the device 286-- and the definition of the objects. 287-- File information group (mandatory) 288-- This group contains objects that provide information 289-- on each file within a partition. 290-- Chip information group (mandatory) 291-- The chip information group contains objects required for 292-- error diagnosis/investigation. 293-- 294-- Operations groups : 295-- File copy operations group (mandatory) 296-- Partitioning operations group (optional) 297-- Miscellaneous operations group (optional) 298-- 299 300-- 301-- Flash Device level information 302 303ciscoFlashDevicesSupported OBJECT-TYPE 304 SYNTAX Unsigned32 305 MAX-ACCESS read-only 306 STATUS current 307 DESCRIPTION 308 "Number of Flash devices supported by the system. 309 If the system does not support any Flash devices, this 310 MIB will not be loaded on that system. The value of this 311 object will therefore be atleast 1." 312 ::= { ciscoFlashDevice 1 } 313 314ciscoFlashDeviceTable OBJECT-TYPE 315 SYNTAX SEQUENCE OF CiscoFlashDeviceEntry 316 MAX-ACCESS not-accessible 317 STATUS current 318 DESCRIPTION 319 "Table of Flash device properties for each initialized 320 Flash device. Each Flash device installed in a system 321 is detected, sized, and initialized when the system 322 image boots up. 323 For removable Flash devices, the device properties 324 will be dynamically deleted and recreated as the 325 device is removed and inserted. Note that in this 326 case, the newly inserted device may not be the same as 327 the earlier removed one. The ciscoFlashDeviceInitTime 328 object is available for a management station to determine 329 the time at which a device was initialized, and thereby 330 detect the change of a removable device. 331 A removable device that has not been installed will 332 also have an entry in this table. This is to let a 333 management station know about a removable device that 334 has been removed. Since a removed device obviously 335 cannot be sized and initialized, the table entry for 336 such a device will have 337 ciscoFlashDeviceSize equal to zero, 338 and the following objects will have 339 an indeterminate value: 340 ciscoFlashDeviceMinPartitionSize, 341 ciscoFlashDeviceMaxPartitions, 342 ciscoFlashDevicePartitions, and 343 ciscoFlashDeviceChipCount. 344 ciscoFlashDeviceRemovable will be 345 true to indicate it is removable." 346 ::= { ciscoFlashDevice 2 } 347 348ciscoFlashDeviceEntry OBJECT-TYPE 349 SYNTAX CiscoFlashDeviceEntry 350 MAX-ACCESS not-accessible 351 STATUS current 352 DESCRIPTION 353 "An entry in the table of flash device properties for 354 each initialized flash device. 355 Each entry can be randomly accessed by using 356 ciscoFlashDeviceIndex as an index into the table. 357 Note that removable devices will have an entry in 358 the table even when they have been removed. However, 359 a non-removable device that has not been installed 360 will not have an entry in the table." 361 INDEX { ciscoFlashDeviceIndex } 362 ::= { ciscoFlashDeviceTable 1 } 363 364CiscoFlashDeviceEntry ::= SEQUENCE { 365 ciscoFlashDeviceIndex Unsigned32, 366 ciscoFlashDeviceSize Unsigned32, 367 ciscoFlashDeviceMinPartitionSize Unsigned32, 368 ciscoFlashDeviceMaxPartitions Unsigned32, 369 ciscoFlashDevicePartitions Unsigned32, 370 ciscoFlashDeviceChipCount Integer32, 371 ciscoFlashDeviceName DisplayString, 372 ciscoFlashDeviceDescr DisplayString, 373 ciscoFlashDeviceController DisplayString, 374 ciscoFlashDeviceCard InstancePointer, 375 ciscoFlashDeviceProgrammingJumper INTEGER, 376 ciscoFlashDeviceInitTime TimeStamp, 377 ciscoFlashDeviceRemovable TruthValue, 378 ciscoFlashPhyEntIndex PhysicalIndex, 379 ciscoFlashDeviceNameExtended DisplayString, 380 ciscoFlashDeviceSizeExtended CounterBasedGauge64, 381 ciscoFlashDeviceMinPartitionSizeExtended CounterBasedGauge64 382} 383 384ciscoFlashDeviceIndex OBJECT-TYPE 385 SYNTAX Unsigned32 (1..4294967295) 386 MAX-ACCESS not-accessible 387 STATUS current 388 DESCRIPTION 389 "Flash device sequence number to index within the 390 table of initialized flash devices. 391 The lowest value should be 1. The highest should be 392 less than or equal to the value of the 393 ciscoFlashDevicesSupported object." 394 ::= { ciscoFlashDeviceEntry 1 } 395 396ciscoFlashDeviceSize OBJECT-TYPE 397 SYNTAX Unsigned32 (1..4294967295) 398 UNITS "bytes" 399 MAX-ACCESS read-only 400 STATUS current 401 DESCRIPTION 402 "Total size of the Flash device. 403 For a removable device, the size will be zero if 404 the device has been removed. 405 406 If the total size of the flash device is greater than the 407 maximum value reportable by this object then this object 408 should report its maximum value(4,294,967,295) and 409 ciscoFlashDeviceSizeExtended must be used to report the 410 flash device's size." 411 ::= { ciscoFlashDeviceEntry 2 } 412 413ciscoFlashDeviceMinPartitionSize OBJECT-TYPE 414 SYNTAX Unsigned32 (1..4294967295) 415 UNITS "bytes" 416 MAX-ACCESS read-only 417 STATUS current 418 DESCRIPTION 419 "This object will give the minimum partition size 420 supported for this device. For systems that execute code 421 directly out of Flash, the minimum partition size needs 422 to be the bank size. (Bank size is equal to the size of a 423 chip multiplied by the width of the device. In most cases, 424 the device width is 4 bytes, and so the bank size would be 425 four times the size of a chip). This has to be so because 426 all programming commands affect the operation of an 427 entire chip (in our case, an entire bank because all 428 operations are done on the entire width of the device) 429 even though the actual command may be localized to a small 430 portion of each chip. So when executing code out of Flash, 431 one needs to be able to write and erase some portion of 432 Flash without affecting the code execution. 433 For systems that execute code out of DRAM or ROM, it is 434 possible to partition Flash with a finer granularity (for 435 eg., at erase sector boundaries) if the system code supports 436 such granularity. 437 438 This object will let a management entity know the 439 minimum partition size as defined by the system. 440 If the system does not support partitioning, the value 441 will be equal to the device size in ciscoFlashDeviceSize. 442 The maximum number of partitions that could be configured 443 will be equal to the minimum of 444 ciscoFlashDeviceMaxPartitions 445 and 446 (ciscoFlashDeviceSize / ciscoFlashDeviceMinPartitionSize). 447 448 If the total size of the flash device is greater than the 449 maximum value reportable by this object then this object should 450 report its maximum value(4,294,967,295) and 451 ciscoFlashDeviceMinPartitionSizeExtended must be used to report 452 the flash device's minimum partition size." 453 ::= { ciscoFlashDeviceEntry 3 } 454 455ciscoFlashDeviceMaxPartitions OBJECT-TYPE 456 SYNTAX Unsigned32 457 MAX-ACCESS read-only 458 STATUS current 459 DESCRIPTION 460 "Max number of partitions supported by the system for 461 this Flash device. Default will be 1, which actually 462 means that partitioning is not supported. Note that 463 this value will be defined by system limitations, not 464 by the flash device itself (for eg., the system may 465 impose a limit of 2 partitions even though the device 466 may be large enough to be partitioned into 4 based on 467 the smallest partition unit supported). 468 On systems that execute code out of Flash, partitioning 469 is a way of creating multiple file systems in the Flash 470 device so that writing into or erasing of one file system 471 can be done while executing code residing in another file 472 system. 473 For systems executing code out of DRAM, partitioning 474 gives a way of sub-dividing a large Flash device for 475 easier management of files." 476 ::= { ciscoFlashDeviceEntry 4 } 477 478ciscoFlashDevicePartitions OBJECT-TYPE 479 SYNTAX Unsigned32 (1..4294967295) 480 MAX-ACCESS read-only 481 STATUS current 482 DESCRIPTION 483 "Flash device partitions actually present. Number of 484 partitions cannot exceed the minimum of 485 ciscoFlashDeviceMaxPartitions 486 and 487 (ciscoFlashDeviceSize / ciscoFlashDeviceMinPartitionSize). 488 Will be equal to at least 1, the case where the partition 489 spans the entire device (actually no partitioning). 490 A partition will contain one or more minimum partition 491 units (where a minimum partition unit is defined by 492 ciscoFlashDeviceMinPartitionSize)." 493 ::= { ciscoFlashDeviceEntry 5 } 494 495ciscoFlashDeviceChipCount OBJECT-TYPE 496 SYNTAX Integer32 (1..64) 497 MAX-ACCESS read-only 498 STATUS current 499 DESCRIPTION 500 "Total number of chips within the Flash device. 501 The purpose of this object is to provide information 502 upfront to a management station on how much chip info 503 to expect and possibly help double check the chip index 504 against an upper limit when randomly retrieving chip 505 info for a partition." 506 ::= { ciscoFlashDeviceEntry 6 } 507 508ciscoFlashDeviceName OBJECT-TYPE 509 SYNTAX DisplayString (SIZE (0..16)) 510 MAX-ACCESS read-only 511 STATUS deprecated 512 DESCRIPTION 513 "Flash device name. This name is used to refer to the 514 device within the system. Flash operations get directed 515 to a device based on this name. 516 The system has a concept of a default device. 517 This would be the primary or most used device in case of 518 multiple devices. The system directs an operation to the 519 default device whenever a device name is not specified. 520 The device name is therefore mandatory except when the 521 operation is being done on the default device, or, 522 the system supports only a single Flash device. 523 The device name will always be available for a 524 removable device, even when the device has been removed." 525 ::= { ciscoFlashDeviceEntry 7 } 526 527ciscoFlashDeviceDescr OBJECT-TYPE 528 SYNTAX DisplayString (SIZE (0..64)) 529 MAX-ACCESS read-only 530 STATUS current 531 DESCRIPTION 532 "Description of a Flash device. The description is meant 533 to explain what the Flash device and its purpose is. 534 Current values are: 535 System flash - for the primary Flash used to store full 536 system images. 537 Boot flash - for the secondary Flash used to store 538 bootstrap images. 539 The ciscoFlashDeviceDescr, ciscoFlashDeviceController 540 (if applicable), and ciscoFlashPhyEntIndex objects are 541 expected to collectively give all information about a 542 Flash device. 543 The device description will always be available for a 544 removable device, even when the device has been removed." 545 ::= { ciscoFlashDeviceEntry 8 } 546 547ciscoFlashDeviceController OBJECT-TYPE 548 SYNTAX DisplayString (SIZE (0..64)) 549 MAX-ACCESS read-only 550 STATUS current 551 DESCRIPTION 552 "Flash device controller. The h/w card that actually 553 controls Flash read/write/erase. Relevant for the AGS+ 554 systems where Flash may be controlled by the MC+, STR or 555 the ENVM cards, cards that may not actually contain the 556 Flash chips. 557 For systems that have removable PCMCIA flash cards that 558 are controlled by a PCMCIA controller chip, this object 559 may contain a description of that controller chip. 560 Where irrelevant (Flash is a direct memory mapped device 561 accessed directly by the main processor), this object will 562 have an empty (NULL) string." 563 ::= { ciscoFlashDeviceEntry 9 } 564 565ciscoFlashDeviceCard OBJECT-TYPE 566 SYNTAX InstancePointer 567 MAX-ACCESS read-only 568 STATUS deprecated 569 DESCRIPTION 570 "This object will point to an instance of a card entry 571 in the cardTable. The card entry will give details about 572 the card on which the Flash device is actually located. 573 For most systems, this is usually the main processor board. 574 On the AGS+ systems, Flash is located on a separate multibus 575 card such as the MC. 576 This object will therefore be used to essentially index 577 into cardTable to retrieve details about the card such as 578 cardDescr, cardSlotNumber, etc." 579 ::= { ciscoFlashDeviceEntry 10 } 580 581ciscoFlashDeviceProgrammingJumper OBJECT-TYPE 582 SYNTAX INTEGER { 583 installed(1), 584 notInstalled(2), 585 unknown(3) 586 } 587 MAX-ACCESS read-only 588 STATUS current 589 DESCRIPTION 590 "This object gives the state of a jumper (if present and can be 591 determined) that controls the programming voltage called Vpp 592 to the Flash device. Vpp is required for programming (erasing 593 and writing) Flash. For certain older technology chips it is 594 also required for identifying the chips (which in turn is 595 required to identify which programming algorithms to use; 596 different chips require different algorithms and commands). 597 The purpose of the jumper, on systems where it is available, 598 is to write protect a Flash device. 599 On most of the newer remote access routers, this jumper is 600 unavailable since users are not expected to visit remote sites 601 just to install and remove the jumpers when upgrading software 602 in the Flash device. The unknown(3) value will be returned for 603 such systems and can be interpreted to mean that a programming 604 jumper is not present or not required on those systems. 605 On systems where the programming jumper state can be read back 606 via a hardware register, the installed(1) or notInstalled(2) 607 value will be returned. 608 This object is expected to be used in conjunction with the 609 ciscoFlashPartitionStatus object whenever that object has 610 the readOnly(1) value. In such a case, this object will 611 indicate whether the programming jumper is a possible reason 612 for the readOnly state." 613 ::= { ciscoFlashDeviceEntry 11 } 614 615ciscoFlashDeviceInitTime OBJECT-TYPE 616 SYNTAX TimeStamp 617 MAX-ACCESS read-only 618 STATUS current 619 DESCRIPTION 620 "System time at which device was initialized. 621 For fixed devices, this will be the system time at 622 boot up. 623 For removable devices, it will be the time at which 624 the device was inserted, which may be boot up time, 625 or a later time (if device was inserted later). 626 If a device (fixed or removable) was repartitioned, 627 it will be the time of repartitioning. 628 The purpose of this object is to help a management 629 station determine if a removable device has been 630 changed. The application should retrieve this 631 object prior to any operation and compare with 632 the previously retrieved value. 633 Note that this time will not be real time but a 634 running time maintained by the system. This running 635 time starts from zero when the system boots up. 636 For a removable device that has been removed, this 637 value will be zero." 638 ::= { ciscoFlashDeviceEntry 12 } 639 640ciscoFlashDeviceRemovable OBJECT-TYPE 641 SYNTAX TruthValue 642 MAX-ACCESS read-only 643 STATUS current 644 DESCRIPTION 645 "Whether Flash device is removable. Generally, only PCMCIA 646 Flash cards will be treated as removable. Socketed Flash 647 chips and Flash SIMM modules will not be treated as removable. 648 Simply put, only those Flash devices that can be inserted 649 or removed without opening the hardware casing will be 650 considered removable. 651 Further, removable Flash devices are expected to have 652 the necessary hardware support - 653 1. on-line removal and insertion 654 2. interrupt generation on removal or insertion." 655 ::= { ciscoFlashDeviceEntry 13 } 656 657ciscoFlashPhyEntIndex OBJECT-TYPE 658 SYNTAX PhysicalIndex 659 MAX-ACCESS read-only 660 STATUS current 661 DESCRIPTION 662 "This object indicates the physical entity index of a 663 physical entity in entPhysicalTable which the flash 664 device actually located." 665 ::= { ciscoFlashDeviceEntry 14 } 666 667ciscoFlashDeviceNameExtended OBJECT-TYPE 668 SYNTAX DisplayString (SIZE (0..255)) 669 MAX-ACCESS read-only 670 STATUS current 671 DESCRIPTION 672 "Extended Flash device name whose size can be upto 673 255 characters. This name is used to refer to the 674 device within the system. Flash operations get directed 675 to a device based on this name. 676 The system has a concept of a default device. 677 This would be the primary or most used device in case 678 of multiple devices. The system directs an operation 679 to the default device whenever a device name is not 680 specified. The device name is therefore mandatory 681 except when the operation is being done on the 682 default device, or, the system supports only a single 683 Flash device. The device name will always be available 684 for a removable device, even when the device has been 685 removed." 686 ::= { ciscoFlashDeviceEntry 15 } 687 688ciscoFlashDeviceSizeExtended OBJECT-TYPE 689 SYNTAX CounterBasedGauge64 690 UNITS "bytes" 691 MAX-ACCESS read-only 692 STATUS current 693 DESCRIPTION 694 "Total size of the Flash device. 695 For a removable device, the size will be zero if 696 the device has been removed. 697 698 This object is a 64-bit version of ciscoFlashDeviceSize." 699 ::= { ciscoFlashDeviceEntry 16 } 700 701ciscoFlashDeviceMinPartitionSizeExtended OBJECT-TYPE 702 SYNTAX CounterBasedGauge64 703 MAX-ACCESS read-only 704 STATUS current 705 DESCRIPTION 706 "This object provides the minimum partition size supported for 707 this device. This object is a 64-bit version of 708 ciscoFlashDeviceMinPatitionSize." 709 ::= { ciscoFlashDeviceEntry 17 } 710 711 712-- Flash device sub group : Chip level information 713 714ciscoFlashChips OBJECT IDENTIFIER 715 ::= { ciscoFlashDevice 3 } 716 717 718ciscoFlashChipTable OBJECT-TYPE 719 SYNTAX SEQUENCE OF CiscoFlashChipEntry 720 MAX-ACCESS not-accessible 721 STATUS current 722 DESCRIPTION 723 "Table of Flash device chip properties for each 724 initialized Flash device. 725 This table is meant primarily for aiding error 726 diagnosis." 727 ::= { ciscoFlashChips 1 } 728 729ciscoFlashChipEntry OBJECT-TYPE 730 SYNTAX CiscoFlashChipEntry 731 MAX-ACCESS not-accessible 732 STATUS current 733 DESCRIPTION 734 "An entry in the table of chip info for each 735 flash device initialized in the system. 736 An entry is indexed by two objects - the 737 device index and the chip index within that 738 device." 739 INDEX { 740 ciscoFlashDeviceIndex, 741 ciscoFlashChipIndex 742 } 743 ::= { ciscoFlashChipTable 1 } 744 745CiscoFlashChipEntry ::= SEQUENCE { 746 ciscoFlashChipIndex Integer32, 747 ciscoFlashChipCode DisplayString, 748 ciscoFlashChipDescr DisplayString, 749 ciscoFlashChipWriteRetries Counter32, 750 ciscoFlashChipEraseRetries Counter32, 751 ciscoFlashChipMaxWriteRetries Unsigned32, 752 ciscoFlashChipMaxEraseRetries Unsigned32 753} 754 755ciscoFlashChipIndex OBJECT-TYPE 756 SYNTAX Integer32 (1..64) 757 MAX-ACCESS not-accessible 758 STATUS current 759 DESCRIPTION 760 "Chip sequence number within selected flash device. 761 Used to index within chip info table. 762 Value starts from 1 and should not be greater than 763 ciscoFlashDeviceChipCount for that device. 764 When retrieving chip information for chips within a 765 partition, the sequence number should lie between 766 ciscoFlashPartitionStartChip & ciscoFlashPartitionEndChip 767 (both inclusive)." 768 ::= { ciscoFlashChipEntry 1 } 769 770ciscoFlashChipCode OBJECT-TYPE 771 SYNTAX DisplayString (SIZE (0..5)) 772 MAX-ACCESS read-only 773 STATUS current 774 DESCRIPTION 775 "Manufacturer and device code for a chip. 776 Lower byte will contain the device code. 777 Upper byte will contain the manufacturer code. 778 If a chip code is unknown because it could not 779 be queried out of the chip, the value of this 780 object will be 00:00. 781 Since programming algorithms differ from chip type to 782 chip type, this chip code should be used to determine 783 which algorithms to use (and thereby whether the chip 784 is supported in the first place)." 785 ::= { ciscoFlashChipEntry 2 } 786 787ciscoFlashChipDescr OBJECT-TYPE 788 SYNTAX DisplayString (SIZE (0..32)) 789 MAX-ACCESS read-only 790 STATUS current 791 DESCRIPTION 792 "Flash chip name corresponding to the chip code. 793 The name will contain the manufacturer and the 794 chip type. It will be of the form : 795 Intel 27F008SA. 796 In the case where a chip code is unknown, this 797 object will be an empty (NULL) string. 798 In the case where the chip code is known but the 799 chip is not supported by the system, this object 800 will be an empty (NULL) string. 801 A management station is therefore expected to use the 802 chip code and the chip description in conjunction 803 to provide additional information whenever the 804 ciscoFlashPartitionStatus object has the readOnly(1) 805 value." 806 ::= { ciscoFlashChipEntry 3 } 807 808ciscoFlashChipWriteRetries OBJECT-TYPE 809 SYNTAX Counter32 810 MAX-ACCESS read-only 811 STATUS current 812 DESCRIPTION 813 "This object will provide a cumulative count 814 (since last system boot up or initialization) of 815 the number of write retries that were done in the chip. 816 If no writes have been done to Flash, the count 817 will be zero. Typically, a maximum of 25 retries are 818 done on a single location before flagging a write 819 error. 820 A management station is expected to get this object 821 for each chip in a partition after a write failure 822 in that partition. To keep a track of retries for 823 a given write operation, the management station would 824 have to retrieve the values for the concerned chips 825 before and after any write operation." 826 ::= { ciscoFlashChipEntry 4 } 827 828ciscoFlashChipEraseRetries OBJECT-TYPE 829 SYNTAX Counter32 830 MAX-ACCESS read-only 831 STATUS current 832 DESCRIPTION 833 "This object will provide a cumulative count 834 (since last system boot up or initialization) of 835 the number of erase retries that were done in the chip. 836 Typically, a maximum of 2000 retries are done in a 837 single erase zone (which may be a full chip or a 838 portion, depending on the chip technology) before 839 flagging an erase error. 840 A management station is expected to get this object 841 for each chip in a partition after an erase failure 842 in that partition. To keep a track of retries for 843 a given erase operation, the management station would 844 have to retrieve the values for the concerned chips 845 before and after any erase operation. 846 Note that erase may be done through an independent 847 command, or through a copy-to-flash command." 848 ::= { ciscoFlashChipEntry 5 } 849 850ciscoFlashChipMaxWriteRetries OBJECT-TYPE 851 SYNTAX Unsigned32 852 MAX-ACCESS read-only 853 STATUS current 854 DESCRIPTION 855 "The maximum number of write retries done at any 856 single location before declaring a write failure." 857 ::= { ciscoFlashChipEntry 6 } 858 859ciscoFlashChipMaxEraseRetries OBJECT-TYPE 860 SYNTAX Unsigned32 861 MAX-ACCESS read-only 862 STATUS current 863 DESCRIPTION 864 "The maximum number of erase retries done within 865 an erase sector before declaring an erase failure." 866 ::= { ciscoFlashChipEntry 7 } 867 868 869-- Flash device sub group : Partition level information 870-- 871-- Flash Partition level information : 872-- A flash partition is a logical sub-division of a flash 873-- device and may or may not be equal to the entire device 874-- itself. When there is no explicit partitioning done, 875-- a single partition is assumed to exist, spanning the 876-- entire device. 877-- Partitioning has some restrictions : 878-- * a partition must always start and end at the boundary of 879-- a system defined minimum unit. Therefore a device must 880-- have atleast two such minimum units in order to be 881-- partitioned. 882-- * existing files and file systems on a device always 883-- override any partitioning commands when it comes to 884-- partitioning a Flash device. In other words, the existence 885-- or configuration of partitions in a Flash device is always 886-- first determined by the location of existing files in 887-- the device. 888-- * partitioning of a device cannot be changed if it 889-- can cause loss of existing files in a partition. 890-- Those files have to be explicitly erased (by erasing the 891-- partition containing them). 892 893ciscoFlashPartitions OBJECT IDENTIFIER 894 ::= { ciscoFlashDevice 4 } 895 896 897ciscoFlashPartitionTable OBJECT-TYPE 898 SYNTAX SEQUENCE OF CiscoFlashPartitionEntry 899 MAX-ACCESS not-accessible 900 STATUS current 901 DESCRIPTION 902 "Table of flash device partition properties for each 903 initialized flash partition. Whenever there is no 904 explicit partitioning done, a single partition spanning 905 the entire device will be assumed to exist. There will 906 therefore always be atleast one partition on a device." 907 ::= { ciscoFlashPartitions 1 } 908 909ciscoFlashPartitionEntry OBJECT-TYPE 910 SYNTAX CiscoFlashPartitionEntry 911 MAX-ACCESS not-accessible 912 STATUS current 913 DESCRIPTION 914 "An entry in the table of flash partition properties 915 for each initialized flash partition. Each entry 916 will be indexed by a device number and a partition 917 number within the device." 918 INDEX { 919 ciscoFlashDeviceIndex, 920 ciscoFlashPartitionIndex 921 } 922 ::= { ciscoFlashPartitionTable 1 } 923 924CiscoFlashPartitionEntry ::= SEQUENCE { 925 ciscoFlashPartitionIndex Unsigned32, 926 ciscoFlashPartitionStartChip Integer32, 927 ciscoFlashPartitionEndChip Integer32, 928 ciscoFlashPartitionSize Unsigned32, 929 ciscoFlashPartitionFreeSpace Gauge32, 930 ciscoFlashPartitionFileCount Gauge32, 931 ciscoFlashPartitionChecksumAlgorithm INTEGER, 932 ciscoFlashPartitionStatus INTEGER, 933 ciscoFlashPartitionUpgradeMethod INTEGER, 934 ciscoFlashPartitionName DisplayString, 935 ciscoFlashPartitionNeedErasure TruthValue, 936 ciscoFlashPartitionFileNameLength Integer32, 937 ciscoFlashPartitionSizeExtended CounterBasedGauge64, 938 ciscoFlashPartitionFreeSpaceExtended CounterBasedGauge64, 939 ciscoFlashPartitionLowSpaceNotifThreshold Percent 940} 941 942ciscoFlashPartitionIndex OBJECT-TYPE 943 SYNTAX Unsigned32 (1..4294967295) 944 MAX-ACCESS not-accessible 945 STATUS current 946 DESCRIPTION 947 "Flash partition sequence number used to index within 948 table of initialized flash partitions." 949 ::= { ciscoFlashPartitionEntry 1 } 950 951ciscoFlashPartitionStartChip OBJECT-TYPE 952 SYNTAX Integer32 (1..64) 953 MAX-ACCESS read-only 954 STATUS current 955 DESCRIPTION 956 "Chip sequence number of first chip in partition. 957 Used as an index into the chip table." 958 ::= { ciscoFlashPartitionEntry 2 } 959 960ciscoFlashPartitionEndChip OBJECT-TYPE 961 SYNTAX Integer32 (1..64) 962 MAX-ACCESS read-only 963 STATUS current 964 DESCRIPTION 965 "Chip sequence number of last chip in partition. 966 Used as an index into the chip table." 967 ::= { ciscoFlashPartitionEntry 3 } 968 969ciscoFlashPartitionSize OBJECT-TYPE 970 SYNTAX Unsigned32 (1..4294967295) 971 UNITS "bytes" 972 MAX-ACCESS read-only 973 STATUS current 974 DESCRIPTION 975 "Flash partition size. It should be an integral 976 multiple of ciscoFlashDeviceMinPartitionSize. 977 If there is a single partition, this size will be equal 978 to ciscoFlashDeviceSize. 979 980 If the size of the flash partition is greater than the 981 maximum value reportable by this object then this object 982 should report its maximum value(4,294,967,295) and 983 ciscoFlashPartitionSizeExtended must be used to report the 984 flash partition's size." 985 ::= { ciscoFlashPartitionEntry 4 } 986 987ciscoFlashPartitionFreeSpace OBJECT-TYPE 988 SYNTAX Gauge32 989 UNITS "bytes" 990 MAX-ACCESS read-only 991 STATUS current 992 DESCRIPTION 993 "Free space within a Flash partition. 994 Note that the actual size of a file in Flash includes 995 a small overhead that represents the file system's 996 file header. 997 Certain file systems may also have a partition or 998 device header overhead to be considered when 999 computing the free space. 1000 Free space will be computed as total partition size 1001 less size of all existing files (valid/invalid/deleted 1002 files and including file header of each file), 1003 less size of any partition header, less size of 1004 header of next file to be copied in. In short, this 1005 object will give the size of the largest file that 1006 can be copied in. The management entity will not be 1007 expected to know or use any overheads such as file 1008 and partition header lengths, since such overheads 1009 may vary from file system to file system. 1010 Deleted files in Flash do not free up space. 1011 A partition may have to be erased in order to reclaim 1012 the space occupied by files. 1013 1014 If the free space within a flash partition is greater than 1015 the maximum value reportable by this object then this object 1016 should report its maximum value(4,294,967,295) and 1017 ciscoFlashPartitionFreeSpaceExtended 1018 must be used to report the flash partition's free space." 1019 ::= { ciscoFlashPartitionEntry 5 } 1020 1021ciscoFlashPartitionFileCount OBJECT-TYPE 1022 SYNTAX Gauge32 1023 MAX-ACCESS read-only 1024 STATUS current 1025 DESCRIPTION 1026 "Count of all files in a flash partition. Both 1027 good and bad (deleted or invalid checksum) files 1028 will be included in this count." 1029 ::= { ciscoFlashPartitionEntry 6 } 1030 1031ciscoFlashPartitionChecksumAlgorithm OBJECT-TYPE 1032 SYNTAX INTEGER { 1033 simpleChecksum(1), 1034 undefined(2), 1035 simpleCRC(3) 1036 } 1037 MAX-ACCESS read-only 1038 STATUS current 1039 DESCRIPTION 1040 "Checksum algorithm identifier for checksum method 1041 used by the file system. Normally, this would be 1042 fixed for a particular file system. When a file 1043 system writes a file to Flash, it checksums the 1044 data written. The checksum then serves as a way 1045 to validate the data read back whenever the file 1046 is opened for reading. 1047 Since there is no way, when using TFTP, to guarantee 1048 that a network download has been error free (since 1049 UDP checksums may not have been enabled), this 1050 object together with the ciscoFlashFileChecksum 1051 object provides a method for any management station 1052 to regenerate the checksum of the original file 1053 on the server and compare checksums to ensure that 1054 the file download to Flash was error free. 1055 simpleChecksum represents a simple 1s complement 1056 addition of short word values. Other algorithm 1057 values will be added as necessary." 1058 ::= { ciscoFlashPartitionEntry 7 } 1059 1060ciscoFlashPartitionStatus OBJECT-TYPE 1061 SYNTAX INTEGER { 1062 readOnly(1), 1063 runFromFlash(2), 1064 readWrite(3) 1065 } 1066 MAX-ACCESS read-only 1067 STATUS current 1068 DESCRIPTION 1069 "Flash partition status can be : 1070 1071 * readOnly if device is not programmable either because 1072 chips could not be recognized or an erroneous mismatch 1073 of chips was detected. Chip recognition may fail either 1074 because the chips are not supported by the system, 1075 or because the Vpp voltage required to identify chips 1076 has been disabled via the programming jumper. 1077 The ciscoFlashDeviceProgrammingJumper, ciscoFlashChipCode, 1078 and ciscoFlashChipDescr objects can be examined to get 1079 more details on the cause of this status 1080 * runFromFlash (RFF) if current image is running from 1081 this partition. 1082 The ciscoFlashPartitionUpgradeMethod object will then 1083 indicate whether the Flash Load Helper can be used 1084 to write a file to this partition or not. 1085 1086 * readWrite if partition is programmable." 1087 ::= { ciscoFlashPartitionEntry 8 } 1088 1089ciscoFlashPartitionUpgradeMethod OBJECT-TYPE 1090 SYNTAX INTEGER { 1091 unknown(1), 1092 rxbootFLH(2), 1093 direct(3) 1094 } 1095 MAX-ACCESS read-only 1096 STATUS current 1097 DESCRIPTION 1098 "Flash partition upgrade method, ie., method by which 1099 new files can be downloaded into the partition. 1100 FLH stands for Flash Load Helper, a feature provided 1101 on run-from-Flash systems for upgrading Flash. This 1102 feature uses the bootstrap code in ROMs to help in 1103 automatic download. 1104 This object should be retrieved if the partition 1105 status is runFromFlash(2). 1106 If the partition status is readOnly(1), the upgrade 1107 method would depend on the reason for the readOnly 1108 status. For eg., it may simply be a matter of installing 1109 the programming jumper, or it may require execution of a 1110 later version of software that supports the Flash chips. 1111 1112 unknown - the current system image does not know 1113 how Flash can be programmed. A possible 1114 method would be to reload the ROM image 1115 and perform the upgrade manually. 1116 rxbootFLH - the Flash Load Helper is available to 1117 download files to Flash. A copy-to-flash 1118 command can be used and this system image 1119 will automatically reload the Rxboot image 1120 in ROM and direct it to carry out the 1121 download request. 1122 direct - will be done directly by this image." 1123 ::= { ciscoFlashPartitionEntry 9 } 1124 1125ciscoFlashPartitionName OBJECT-TYPE 1126 SYNTAX DisplayString (SIZE (0..16)) 1127 MAX-ACCESS read-only 1128 STATUS current 1129 DESCRIPTION 1130 "Flash partition name used to refer to a partition 1131 by the system. This can be any alpha-numeric character 1132 string of the form AAAAAAAAnn, where A represents an 1133 optional alpha character and n a numeric character. 1134 Any numeric characters must always form the trailing 1135 part of the string. The system will strip off the alpha 1136 characters and use the numeric portion to map to a 1137 partition index. 1138 Flash operations get directed to a device partition 1139 based on this name. 1140 The system has a concept of a default partition. This 1141 would be the first partition in the device. The system 1142 directs an operation to the default partition whenever 1143 a partition name is not specified. 1144 The partition name is therefore mandatory except when 1145 the operation is being done on the default partition, or 1146 the device has just one partition (is not partitioned)." 1147 ::= { ciscoFlashPartitionEntry 10 } 1148 1149ciscoFlashPartitionNeedErasure OBJECT-TYPE 1150 SYNTAX TruthValue 1151 MAX-ACCESS read-only 1152 STATUS current 1153 DESCRIPTION 1154 "This object indicates whether a partition requires 1155 erasure before any write operations can be done in it. 1156 A management station should therefore retrieve this 1157 object prior to attempting any write operation. 1158 A partition requires erasure after it becomes full 1159 free space left is less than or equal to the 1160 (filesystem file header size). 1161 A partition also requires erasure if the system does 1162 not find the existence of any file system when it 1163 boots up. 1164 The partition may be erased explicitly through the 1165 erase(5) command, or by using the copyToFlashWithErase(1) 1166 command. 1167 If a copyToFlashWithoutErase(2) command is issued 1168 when this object has the TRUE value, the command 1169 will fail." 1170 ::= { ciscoFlashPartitionEntry 11 } 1171 1172ciscoFlashPartitionFileNameLength OBJECT-TYPE 1173 SYNTAX Integer32 (1..256) 1174 MAX-ACCESS read-only 1175 STATUS current 1176 DESCRIPTION 1177 "Maximum file name length supported by the file 1178 system. 1179 Max file name length will depend on the file 1180 system implemented. Today, all file systems 1181 support a max length of at least 48 bytes. 1182 A management entity must use this object when 1183 prompting a user for, or deriving the Flash file 1184 name length." 1185 ::= { ciscoFlashPartitionEntry 12 } 1186 1187ciscoFlashPartitionSizeExtended OBJECT-TYPE 1188 SYNTAX CounterBasedGauge64 1189 UNITS "bytes" 1190 MAX-ACCESS read-only 1191 STATUS current 1192 DESCRIPTION 1193 "Flash partition size. It should be an integral 1194 multiple of ciscoFlashDeviceMinPartitionSize. 1195 If there is a single partition, this size will be equal 1196 to ciscoFlashDeviceSize. 1197 1198 This object is a 64-bit version of ciscoFlashPartitionSize" 1199 ::= { ciscoFlashPartitionEntry 13 } 1200 1201ciscoFlashPartitionFreeSpaceExtended OBJECT-TYPE 1202 SYNTAX CounterBasedGauge64 1203 UNITS "bytes" 1204 MAX-ACCESS read-only 1205 STATUS current 1206 DESCRIPTION 1207 "Free space within a Flash partition. 1208 Note that the actual size of a file in Flash includes 1209 a small overhead that represents the file system's 1210 file header. 1211 Certain file systems may also have a partition or 1212 device header overhead to be considered when 1213 computing the free space. 1214 Free space will be computed as total partition size 1215 less size of all existing files (valid/invalid/deleted 1216 files and including file header of each file), 1217 less size of any partition header, less size of 1218 header of next file to be copied in. In short, this 1219 object will give the size of the largest file that 1220 can be copied in. The management entity will not be 1221 expected to know or use any overheads such as file 1222 and partition header lengths, since such overheads 1223 may vary from file system to file system. 1224 Deleted files in Flash do not free up space. 1225 A partition may have to be erased in order to reclaim 1226 the space occupied by files. 1227 1228 This object is a 64-bit version of ciscoFlashPartitionFreeSpace" 1229 ::= { ciscoFlashPartitionEntry 14 } 1230 1231ciscoFlashPartitionLowSpaceNotifThreshold OBJECT-TYPE 1232 SYNTAX Percent 1233 MAX-ACCESS read-write 1234 STATUS current 1235 DESCRIPTION 1236 "This object specifies the minimum threshold value in percentage 1237 of free space for each partition. If the free space available 1238 goes below this threshold value and if 1239 ciscoFlashPartionLowSpaceNotifEnable is set to true, 1240 ciscoFlashPartitionLowSpaceNotif will be generated. When the 1241 available free space comes back to the threshold value 1242 ciscoFlashPartionLowSpaceRecoveryNotif will be generated." 1243 ::= { ciscoFlashPartitionEntry 15 } 1244 1245 1246-- Flash partition sub group : File level information 1247 1248ciscoFlashFiles OBJECT IDENTIFIER 1249 ::= { ciscoFlashPartitions 2 } 1250 1251 1252ciscoFlashFileTable OBJECT-TYPE 1253 SYNTAX SEQUENCE OF CiscoFlashFileEntry 1254 MAX-ACCESS not-accessible 1255 STATUS current 1256 DESCRIPTION 1257 "Table of information for files in a Flash partition." 1258 ::= { ciscoFlashFiles 1 } 1259 1260ciscoFlashFileEntry OBJECT-TYPE 1261 SYNTAX CiscoFlashFileEntry 1262 MAX-ACCESS not-accessible 1263 STATUS current 1264 DESCRIPTION 1265 "An entry in the table of Flash file properties 1266 for each initialized Flash partition. Each entry 1267 represents a file and gives details about the file. 1268 An entry is indexed using the device number, 1269 partition number within the device, and file 1270 number within the partition." 1271 INDEX { 1272 ciscoFlashDeviceIndex, 1273 ciscoFlashPartitionIndex, 1274 ciscoFlashFileIndex 1275 } 1276 ::= { ciscoFlashFileTable 1 } 1277 1278CiscoFlashFileEntry ::= SEQUENCE { 1279 ciscoFlashFileIndex Unsigned32, 1280 ciscoFlashFileSize Unsigned32, 1281 ciscoFlashFileChecksum ChecksumString, 1282 ciscoFlashFileStatus INTEGER, 1283 ciscoFlashFileName DisplayString, 1284 ciscoFlashFileType FlashFileType, 1285 ciscoFlashFileDate DateAndTime 1286} 1287 1288ciscoFlashFileIndex OBJECT-TYPE 1289 SYNTAX Unsigned32 (1..4294967295) 1290 MAX-ACCESS not-accessible 1291 STATUS current 1292 DESCRIPTION 1293 "Flash file sequence number used to index within 1294 a Flash partition directory table." 1295 ::= { ciscoFlashFileEntry 1 } 1296 1297ciscoFlashFileSize OBJECT-TYPE 1298 SYNTAX Unsigned32 1299 UNITS "bytes" 1300 MAX-ACCESS read-only 1301 STATUS current 1302 DESCRIPTION 1303 "Size of the file in bytes. Note that this size does 1304 not include the size of the filesystem file header. 1305 File size will always be non-zero." 1306 ::= { ciscoFlashFileEntry 2 } 1307 1308ciscoFlashFileChecksum OBJECT-TYPE 1309 SYNTAX ChecksumString 1310 MAX-ACCESS read-only 1311 STATUS current 1312 DESCRIPTION 1313 "File checksum stored in the file header. This 1314 checksum is computed and stored when the file is 1315 written into Flash. It serves to validate the data 1316 written into Flash. 1317 Whereas the system will generate and store the checksum 1318 internally in hexadecimal form, this object will 1319 provide the checksum in a string form. 1320 The checksum will be available for all valid and 1321 invalid-checksum files." 1322 ::= { ciscoFlashFileEntry 3 } 1323 1324ciscoFlashFileStatus OBJECT-TYPE 1325 SYNTAX INTEGER { 1326 deleted(1), 1327 invalidChecksum(2), 1328 valid(3) 1329 } 1330 MAX-ACCESS read-only 1331 STATUS current 1332 DESCRIPTION 1333 "Status of a file. 1334 A file could be explicitly deleted if the file system 1335 supports such a user command facility. Alternately, 1336 an existing good file would be automatically deleted 1337 if another good file with the same name were copied in. 1338 Note that deleted files continue to occupy prime 1339 Flash real estate. 1340 1341 A file is marked as having an invalid checksum if any 1342 checksum mismatch was detected while writing or reading 1343 the file. Incomplete files (files truncated either 1344 because of lack of free space, or a network download 1345 failure) are also written with a bad checksum and 1346 marked as invalid." 1347 ::= { ciscoFlashFileEntry 4 } 1348 1349ciscoFlashFileName OBJECT-TYPE 1350 SYNTAX DisplayString (SIZE (1..255)) 1351 MAX-ACCESS read-only 1352 STATUS current 1353 DESCRIPTION 1354 "Flash file name as specified by the user copying in 1355 the file. The name should not include the colon (:) 1356 character as it is a special separator character used 1357 to delineate the device name, partition name, and the 1358 file name." 1359 ::= { ciscoFlashFileEntry 5 } 1360 1361ciscoFlashFileType OBJECT-TYPE 1362 SYNTAX FlashFileType 1363 MAX-ACCESS read-only 1364 STATUS current 1365 DESCRIPTION 1366 "Type of the file." 1367 ::= { ciscoFlashFileEntry 6 } 1368 1369ciscoFlashFileDate OBJECT-TYPE 1370 SYNTAX DateAndTime 1371 MAX-ACCESS read-only 1372 STATUS current 1373 DESCRIPTION 1374 "The time at which this file was created." 1375 ::= { ciscoFlashFileEntry 7 } 1376 1377 1378 1379ciscoFlashFileByTypeTable OBJECT-TYPE 1380 SYNTAX SEQUENCE OF CiscoFlashFileByTypeEntry 1381 MAX-ACCESS not-accessible 1382 STATUS current 1383 DESCRIPTION 1384 "Table of information for files on the manageable 1385 flash devices sorted by File Types." 1386 ::= { ciscoFlashFiles 2 } 1387 1388ciscoFlashFileByTypeEntry OBJECT-TYPE 1389 SYNTAX CiscoFlashFileByTypeEntry 1390 MAX-ACCESS not-accessible 1391 STATUS current 1392 DESCRIPTION 1393 "An entry in the table of Flash file properties 1394 for each initialized Flash partition. Each entry 1395 represents a file sorted by file type. 1396 1397 This table contains exactly the same set of rows 1398 as are contained in the ciscoFlashFileTable but 1399 in a different order, i.e., ordered by 1400 1401 the type of file, given by ciscoFlashFileType; 1402 the device number, given by ciscoFlashDeviceIndex; 1403 the partition number within the device, given by 1404 ciscoFlashPartitionIndex; 1405 the file number within the partition, given by 1406 ciscoFlashFileIndex." 1407 INDEX { 1408 ciscoFlashFileType, 1409 ciscoFlashDeviceIndex, 1410 ciscoFlashPartitionIndex, 1411 ciscoFlashFileIndex 1412 } 1413 ::= { ciscoFlashFileByTypeTable 1 } 1414 1415CiscoFlashFileByTypeEntry ::= SEQUENCE { 1416 ciscoFlashFileByTypeSize Unsigned32, 1417 ciscoFlashFileByTypeChecksum ChecksumString, 1418 ciscoFlashFileByTypeStatus INTEGER, 1419 ciscoFlashFileByTypeName DisplayString, 1420 ciscoFlashFileByTypeDate DateAndTime 1421} 1422 1423ciscoFlashFileByTypeSize OBJECT-TYPE 1424 SYNTAX Unsigned32 1425 UNITS "bytes" 1426 MAX-ACCESS read-only 1427 STATUS current 1428 DESCRIPTION 1429 "This object represents exactly the 1430 same info as ciscoFlashFileSize 1431 object in ciscoFlashFileTable." 1432 ::= { ciscoFlashFileByTypeEntry 1 } 1433 1434ciscoFlashFileByTypeChecksum OBJECT-TYPE 1435 SYNTAX ChecksumString 1436 MAX-ACCESS read-only 1437 STATUS current 1438 DESCRIPTION 1439 "This object represents exactly the 1440 same info as ciscoFlashFileChecksum 1441 object in ciscoFlashFileTable." 1442 ::= { ciscoFlashFileByTypeEntry 2 } 1443 1444ciscoFlashFileByTypeStatus OBJECT-TYPE 1445 SYNTAX INTEGER { 1446 deleted(1), 1447 invalidChecksum(2), 1448 valid(3) 1449 } 1450 MAX-ACCESS read-only 1451 STATUS current 1452 DESCRIPTION 1453 "This object represents exactly the 1454 same info as ciscoFlashFileStatus 1455 object in ciscoFlashFileTable." 1456 ::= { ciscoFlashFileByTypeEntry 3 } 1457 1458ciscoFlashFileByTypeName OBJECT-TYPE 1459 SYNTAX DisplayString (SIZE (1..255)) 1460 MAX-ACCESS read-only 1461 STATUS current 1462 DESCRIPTION 1463 "This object represents exactly the 1464 same info as ciscoFlashFileName 1465 object in ciscoFlashFileTable." 1466 ::= { ciscoFlashFileByTypeEntry 4 } 1467 1468ciscoFlashFileByTypeDate OBJECT-TYPE 1469 SYNTAX DateAndTime 1470 MAX-ACCESS read-only 1471 STATUS current 1472 DESCRIPTION 1473 "This object represents exactly the 1474 same info as ciscoFlashFileDate 1475 object in ciscoFlashFileTable." 1476 ::= { ciscoFlashFileByTypeEntry 5 } 1477 1478 1479-- End of Flash information 1480-- Start of Flash operations 1481-- Operations are for 1482-- copying to/from flash 1483-- partitioning 1484-- misc (erasing, file verification, ...) 1485 1486ciscoFlashCopyTable OBJECT-TYPE 1487 SYNTAX SEQUENCE OF CiscoFlashCopyEntry 1488 MAX-ACCESS not-accessible 1489 STATUS current 1490 DESCRIPTION 1491 "A table of Flash copy operation entries. Each 1492 entry represents a Flash copy operation (to or 1493 from Flash) that has been initiated." 1494 ::= { ciscoFlashOps 1 } 1495 1496ciscoFlashCopyEntry OBJECT-TYPE 1497 SYNTAX CiscoFlashCopyEntry 1498 MAX-ACCESS not-accessible 1499 STATUS current 1500 DESCRIPTION 1501 "A Flash copy operation entry. Each entry consists 1502 of a command, a source, and optional parameters such 1503 as protocol to be used, a destination, a server address, 1504 etc. 1505 1506 A management station wishing to create an entry should 1507 first generate a pseudo-random serial number to be used 1508 as the index to this sparse table. The station should 1509 then create the associated instance of the row status 1510 object. It must also, either in the same or in successive 1511 PDUs, create the associated instance of the command and 1512 parameter objects. It should also modify the default values 1513 for any of the parameter objects if the defaults are not 1514 appropriate. 1515 1516 Once the appropriate instances of all the command 1517 objects have been created, either by an explicit SNMP 1518 set request or by default, the row status should be set 1519 to active to initiate the operation. Note that this entire 1520 procedure may be initiated via a single set request which 1521 specifies a row status of createAndGo as well as specifies 1522 valid values for the non-defaulted parameter objects. 1523 1524 Once an operation has been activated, it cannot be 1525 stopped. 1526 1527 Once the operation completes, the management station should 1528 retrieve the value of the status object (and time if 1529 desired), and delete the entry. In order to prevent old 1530 entries from clogging the table, entries will be aged out, 1531 but an entry will never be deleted within 5 minutes of 1532 completing." 1533 INDEX { ciscoFlashCopySerialNumber } 1534 ::= { ciscoFlashCopyTable 1 } 1535 1536CiscoFlashCopyEntry ::= SEQUENCE { 1537 ciscoFlashCopySerialNumber Integer32, 1538 ciscoFlashCopyCommand INTEGER, 1539 ciscoFlashCopyProtocol INTEGER, 1540 ciscoFlashCopyServerAddress IpAddress, 1541 ciscoFlashCopySourceName DisplayString, 1542 ciscoFlashCopyDestinationName DisplayString, 1543 ciscoFlashCopyRemoteUserName DisplayString, 1544 ciscoFlashCopyStatus INTEGER, 1545 ciscoFlashCopyNotifyOnCompletion TruthValue, 1546 ciscoFlashCopyTime TimeTicks, 1547 ciscoFlashCopyEntryStatus RowStatus, 1548 ciscoFlashCopyVerify TruthValue, 1549 ciscoFlashCopyServerAddrType InetAddressType, 1550 ciscoFlashCopyServerAddrRev1 InetAddress, 1551 ciscoFlashCopyRemotePassword DisplayString 1552} 1553 1554ciscoFlashCopySerialNumber OBJECT-TYPE 1555 SYNTAX Integer32 (0..2147483647) 1556 MAX-ACCESS not-accessible 1557 STATUS current 1558 DESCRIPTION 1559 "Object which specifies a unique entry in the 1560 table. A management station wishing to initiate a 1561 copy operation should use a pseudo-random value for 1562 this object when creating or modifying an instance of 1563 a ciscoFlashCopyEntry." 1564 ::= { ciscoFlashCopyEntry 1 } 1565 1566ciscoFlashCopyCommand OBJECT-TYPE 1567 SYNTAX INTEGER { 1568 copyToFlashWithErase(1), 1569 copyToFlashWithoutErase(2), 1570 copyFromFlash(3), 1571 copyFromFlhLog(4) 1572 } 1573 MAX-ACCESS read-create 1574 STATUS current 1575 DESCRIPTION 1576 "The copy command to be executed. Mandatory. 1577 Note that it is possible for a system to support 1578 multiple file systems (different file systems on 1579 different Flash devices, or different file systems 1580 on different partitions within a device). Each such 1581 file system may support only a subset of these commands. 1582 If a command is unsupported, the invalidOperation(3) 1583 error will be reported in the operation status. 1584 1585 Command Remarks 1586 copyToFlashWithErase Copy a file to flash; erase 1587 flash before copy. 1588 Use the TFTP or rcp protocol. 1589 copyToFlashWithoutErase Copy a file to flash; do not 1590 erase. 1591 Note that this command will fail 1592 if the PartitionNeedErasure 1593 object specifies that the 1594 partition being copied to needs 1595 erasure. 1596 Use the TFTP or rcp protocol. 1597 copyFromFlash Copy a file from flash using 1598 the TFTP, rcp or lex protocol. 1599 Note that the lex protocol 1600 can only be used to copy to a 1601 lex device. 1602 copyFromFlhLog Copy contents of FLH log to 1603 server using TFTP protocol. 1604 1605 1606 Command table Parameters 1607 copyToFlashWithErase CopyProtocol 1608 CopyServerAddress 1609 CopySourceName 1610 CopyDestinationName (opt) 1611 CopyRemoteUserName (opt) 1612 CopyNotifyOnCompletion (opt) 1613 copyToFlashWithoutErase CopyProtocol 1614 CopyServerAddress 1615 CopySourceName 1616 CopyDestinationName (opt) 1617 CopyRemoteUserName (opt) 1618 CopyNotifyOnCompletion (opt) 1619 copyFromFlash CopyProtocol 1620 CopyServerAddress 1621 CopySourceName 1622 CopyDestinationName (opt) 1623 CopyRemoteUserName (opt) 1624 CopyNotifyOnCompletion (opt) 1625 copyFromFlhLog CopyProtocol 1626 CopyServerAddress 1627 CopyDestinationName 1628 CopyNotifyOnCompletion (opt)" 1629 ::= { ciscoFlashCopyEntry 2 } 1630 1631ciscoFlashCopyProtocol OBJECT-TYPE 1632 SYNTAX INTEGER { 1633 tftp(1), 1634 rcp(2), 1635 lex(3), 1636 ftp(4), 1637 scp(5), 1638 sftp(6) 1639 } 1640 MAX-ACCESS read-create 1641 STATUS current 1642 DESCRIPTION 1643 "The protocol to be used for any copy. Optional. 1644 Will default to tftp if not specified. 1645 1646 Since feature support depends on a software release, 1647 version number within the release, platform, and 1648 maybe the image type (subset type), a management 1649 station would be expected to somehow determine 1650 the protocol support for a command." 1651 DEFVAL { tftp } 1652 ::= { ciscoFlashCopyEntry 3 } 1653 1654ciscoFlashCopyServerAddress OBJECT-TYPE 1655 SYNTAX IpAddress 1656 MAX-ACCESS read-create 1657 STATUS deprecated 1658 DESCRIPTION 1659 "The server address to be used for any copy. Optional. 1660 Will default to 'FFFFFFFF'H (or 255.255.255.255). 1661 1662 Since this object can just hold only IPv4 Transport 1663 type, it is deprecated and replaced by 1664 ciscoFlashCopyServerAddrRev1." 1665 DEFVAL { 'FFFFFFFF'H } 1666 ::= { ciscoFlashCopyEntry 4 } 1667 1668ciscoFlashCopySourceName OBJECT-TYPE 1669 SYNTAX DisplayString (SIZE (1..255)) 1670 MAX-ACCESS read-create 1671 STATUS current 1672 DESCRIPTION 1673 "Source file name, either in Flash or on a server, 1674 depending on the type of copy command. Mandatory. 1675 1676 For a copy from Flash: 1677 File name must be of the form 1678 [device>:][:] 1679 where is a value obtained from FlashDeviceName, 1680 is obtained from FlashPartitionName 1681 and is the name of a file in Flash. 1682 A management station could derive its own partition name 1683 as per the description for the ciscoFlashPartitionName 1684 object. 1685 If <device> is not specified, the default Flash device 1686 will be assumed. 1687 If <partition> is not specified, the default partition 1688 will be assumed. If a device is not partitioned into 2 1689 or more partitions, this value may be left out. 1690 1691 For a copy to Flash, the file name will be as per 1692 the file naming conventions and path to the file on 1693 the server." 1694 ::= { ciscoFlashCopyEntry 5 } 1695 1696ciscoFlashCopyDestinationName OBJECT-TYPE 1697 SYNTAX DisplayString (SIZE (0..255)) 1698 MAX-ACCESS read-create 1699 STATUS current 1700 DESCRIPTION 1701 "Destination file name. 1702 1703 For a copy to Flash: 1704 File name must be of the form 1705 {device>:][<partition>:]<file> 1706 where <device> is a value obtained from FlashDeviceName, 1707 <partition> is obtained from FlashPartitionName 1708 and <file> is any character string that does not have 1709 embedded colon characters. 1710 A management station could derive its own partition name 1711 as per the description for the ciscoFlashPartitionName 1712 object. 1713 If <device> is not specified, the default Flash device 1714 will be assumed. 1715 If <partition> is not specified, the default partition 1716 will be assumed. If a device is not partitioned into 2 1717 or more partitions, this value may be left out. 1718 If <file> is not specified, it will default to <file> 1719 specified in ciscoFlashCopySourceName. 1720 1721 For a copy from Flash via tftp or rcp, the file name will be 1722 as per the file naming conventions and destination sub-directory 1723 on the server. If not specified, <file> from the source 1724 file name will be used. 1725 For a copy from Flash via lex, this string will consist 1726 of numeric characters specifying the interface on the 1727 lex box that will receive the source flash image." 1728 DEFVAL { ''B } 1729 ::= { ciscoFlashCopyEntry 6 } 1730 1731ciscoFlashCopyRemoteUserName OBJECT-TYPE 1732 SYNTAX DisplayString (SIZE (1..255)) 1733 MAX-ACCESS read-create 1734 STATUS current 1735 DESCRIPTION 1736 "Remote user name for copy via rcp protocol. Optional. 1737 This object will be ignored for protocols other than 1738 rcp. 1739 If specified, it will override the remote user-name 1740 configured through the 1741 rcmd remote-username 1742 configuration command. 1743 The remote user-name is sent as the server user-name 1744 in an rcp command request sent by the system to a 1745 remote rcp server." 1746 ::= { ciscoFlashCopyEntry 7 } 1747 1748ciscoFlashCopyStatus OBJECT-TYPE 1749 SYNTAX INTEGER { 1750 copyOperationPending(0), 1751 copyInProgress(1), 1752 copyOperationSuccess(2), 1753 copyInvalidOperation(3), 1754 copyInvalidProtocol(4), 1755 copyInvalidSourceName(5), 1756 copyInvalidDestName(6), 1757 copyInvalidServerAddress(7), 1758 copyDeviceBusy(8), 1759 copyDeviceOpenError(9), 1760 copyDeviceError(10), 1761 copyDeviceNotProgrammable(11), 1762 copyDeviceFull(12), 1763 copyFileOpenError(13), 1764 copyFileTransferError(14), 1765 copyFileChecksumError(15), 1766 copyNoMemory(16), 1767 copyUnknownFailure(17), 1768 copyInvalidSignature(18), 1769 copyProhibited(19) 1770 } 1771 MAX-ACCESS read-only 1772 STATUS current 1773 DESCRIPTION 1774 "The status of the specified copy operation. 1775 1776 copyOperationPending : 1777 operation request is received and 1778 pending for validation and process 1779 1780 copyInProgress : 1781 specified operation is active 1782 1783 copyOperationSuccess : 1784 specified operation is supported and 1785 completed successfully 1786 1787 copyInvalidOperation : 1788 command invalid or command-protocol-device 1789 combination unsupported 1790 1791 copyInvalidProtocol : 1792 invalid protocol specified 1793 1794 copyInvalidSourceName : 1795 invalid source file name specified 1796 For the copy from flash to lex operation, this 1797 error code will be returned when the source file 1798 is not a valid lex image. 1799 1800 copyInvalidDestName : 1801 invalid target name (file or partition or 1802 device name) specified 1803 For the copy from flash to lex operation, this 1804 error code will be returned when no lex devices 1805 are connected to the router or when an invalid 1806 lex interface number has been specified in 1807 the destination string. 1808 1809 copyInvalidServerAddress : 1810 invalid server address specified 1811 1812 copyDeviceBusy : 1813 specified device is in use and locked by 1814 another process 1815 1816 copyDeviceOpenError : 1817 invalid device name 1818 1819 copyDeviceError : 1820 device read, write or erase error 1821 1822 copyDeviceNotProgrammable : 1823 device is read-only but a write or erase 1824 operation was specified 1825 1826 copyDeviceFull : 1827 device is filled to capacity 1828 1829 copyFileOpenError : 1830 invalid file name; file not found in partition 1831 1832 copyFileTransferError : 1833 file transfer was unsuccessfull; network failure 1834 1835 copyFileChecksumError : 1836 file checksum in Flash failed 1837 1838 copyNoMemory : 1839 system running low on memory 1840 1841 copyUnknownFailure : 1842 failure unknown 1843 1844 copyProhibited: 1845 stop user from overwriting current boot image file." 1846 ::= { ciscoFlashCopyEntry 8 } 1847 1848ciscoFlashCopyNotifyOnCompletion OBJECT-TYPE 1849 SYNTAX TruthValue 1850 MAX-ACCESS read-create 1851 STATUS current 1852 DESCRIPTION 1853 "Specifies whether or not a notification should be 1854 generated on the completion of the copy operation. 1855 If specified, ciscoFlashCopyCompletionTrap 1856 will be generated. It is the responsibility of the 1857 management entity to ensure that the SNMP administrative 1858 model is configured in such a way as to allow the 1859 notification to be delivered." 1860 DEFVAL { false } 1861 ::= { ciscoFlashCopyEntry 9 } 1862 1863ciscoFlashCopyTime OBJECT-TYPE 1864 SYNTAX TimeTicks 1865 MAX-ACCESS read-only 1866 STATUS current 1867 DESCRIPTION 1868 "Time taken for the copy operation. This object will 1869 be like a stopwatch, starting when the operation 1870 starts, stopping when the operation completes. 1871 If a management entity keeps a database of completion 1872 times for various operations, it can then use the 1873 stopwatch capability to display percentage completion 1874 time." 1875 ::= { ciscoFlashCopyEntry 10 } 1876 1877ciscoFlashCopyEntryStatus OBJECT-TYPE 1878 SYNTAX RowStatus 1879 MAX-ACCESS read-create 1880 STATUS current 1881 DESCRIPTION 1882 "The status of this table entry." 1883 ::= { ciscoFlashCopyEntry 11 } 1884 1885ciscoFlashCopyVerify OBJECT-TYPE 1886 SYNTAX TruthValue 1887 MAX-ACCESS read-create 1888 STATUS current 1889 DESCRIPTION 1890 "Specifies whether the file that is copied need to 1891 be verified for integrity / authenticity, after 1892 copy succeeds. If it is set to true, and if the 1893 file that is copied doesn't have integrity /authenticity 1894 attachement, or the integrity / authenticity check 1895 fails, then the command will be aborted, and the file 1896 that is copied will be deleted from the destination 1897 file system." 1898 DEFVAL { false } 1899 ::= { ciscoFlashCopyEntry 12 } 1900 1901ciscoFlashCopyServerAddrType OBJECT-TYPE 1902 SYNTAX InetAddressType 1903 MAX-ACCESS read-create 1904 STATUS current 1905 DESCRIPTION 1906 "This object indicates the transport type of the 1907 address contained in 1908 ciscoFlashCopyServerAddrRev1. Optional. 1909 Will default to '1' (IPv4 address type)." 1910 DEFVAL { ipv4 } 1911 ::= { ciscoFlashCopyEntry 13 } 1912 1913ciscoFlashCopyServerAddrRev1 OBJECT-TYPE 1914 SYNTAX InetAddress 1915 MAX-ACCESS read-create 1916 STATUS current 1917 DESCRIPTION 1918 "The server address to be used for any copy. Optional. 1919 Will default to 'FFFFFFFF'H (or 255.255.255.255). 1920 1921 The Format of this address depends on the value of the 1922 ciscoFlashCopyServerAddrType. 1923 1924 This object deprecates the old 1925 ciscoFlashCopyServerAddress object." 1926 DEFVAL { 'FFFFFFFF'H } 1927 ::= { ciscoFlashCopyEntry 14 } 1928 1929ciscoFlashCopyRemotePassword OBJECT-TYPE 1930 SYNTAX DisplayString (SIZE (1..40)) 1931 MAX-ACCESS read-create 1932 STATUS current 1933 DESCRIPTION 1934 "Password used by ftp, sftp or scp for copying a file 1935 to/from an ftp/sftp/scp server. This object must be 1936 created when the ciscoFlashCopyProtocol is ftp, sftp or 1937 scp. Reading it returns a zero-length string for 1938 security reasons." 1939 ::= { ciscoFlashCopyEntry 15 } 1940 1941 1942 1943ciscoFlashPartitioningTable OBJECT-TYPE 1944 SYNTAX SEQUENCE OF CiscoFlashPartitioningEntry 1945 MAX-ACCESS not-accessible 1946 STATUS current 1947 DESCRIPTION 1948 "A table of Flash partitioning operation entries. Each 1949 entry represents a Flash partitioning operation that 1950 has been initiated." 1951 ::= { ciscoFlashOps 2 } 1952 1953ciscoFlashPartitioningEntry OBJECT-TYPE 1954 SYNTAX CiscoFlashPartitioningEntry 1955 MAX-ACCESS not-accessible 1956 STATUS current 1957 DESCRIPTION 1958 "A Flash partitioning operation entry. Each entry 1959 consists of the command, the target device, the 1960 partition count, and optionally the partition sizes. 1961 1962 A management station wishing to create an entry should 1963 first generate a pseudo-random serial number to be used 1964 as the index to this sparse table. The station should 1965 then create the associated instance of the row status 1966 object. It must also, either in the same or in successive 1967 PDUs, create the associated instance of the command and 1968 parameter objects. It should also modify the default values 1969 for any of the parameter objects if the defaults are not 1970 appropriate. 1971 1972 Once the appropriate instances of all the command 1973 objects have been created, either by an explicit SNMP 1974 set request or by default, the row status should be set 1975 to active to initiate the operation. Note that this entire 1976 procedure may be initiated via a single set request which 1977 specifies a row status of createAndGo as well as specifies 1978 valid values for the non-defaulted parameter objects. 1979 1980 Once an operation has been activated, it cannot be 1981 stopped. 1982 1983 Once the operation completes, the management station should 1984 retrieve the value of the status object (and time if 1985 desired), and delete the entry. In order to prevent old 1986 entries from clogging the table, entries will be aged out, 1987 but an entry will never be deleted within 5 minutes of 1988 completing." 1989 INDEX { ciscoFlashPartitioningSerialNumber } 1990 ::= { ciscoFlashPartitioningTable 1 } 1991 1992CiscoFlashPartitioningEntry ::= SEQUENCE { 1993 ciscoFlashPartitioningSerialNumber Integer32, 1994 ciscoFlashPartitioningCommand INTEGER, 1995 ciscoFlashPartitioningDestinationName DisplayString, 1996 ciscoFlashPartitioningPartitionCount Unsigned32, 1997 ciscoFlashPartitioningPartitionSizes DisplayString, 1998 ciscoFlashPartitioningStatus INTEGER, 1999 ciscoFlashPartitioningNotifyOnCompletion TruthValue, 2000 ciscoFlashPartitioningTime TimeTicks, 2001 ciscoFlashPartitioningEntryStatus RowStatus 2002} 2003 2004ciscoFlashPartitioningSerialNumber OBJECT-TYPE 2005 SYNTAX Integer32 (0..2147483647) 2006 MAX-ACCESS not-accessible 2007 STATUS current 2008 DESCRIPTION 2009 "Object which specifies a unique entry in the partitioning 2010 operations table. A management station wishing to initiate 2011 a partitioning operation should use a pseudo-random value 2012 for this object when creating or modifying an instance of 2013 a ciscoFlashPartitioningEntry." 2014 ::= { ciscoFlashPartitioningEntry 1 } 2015 2016ciscoFlashPartitioningCommand OBJECT-TYPE 2017 SYNTAX INTEGER { 2018 partition(1) 2019 } 2020 MAX-ACCESS read-create 2021 STATUS current 2022 DESCRIPTION 2023 "The partitioning command to be executed. Mandatory. 2024 If the command is unsupported, the 2025 partitioningInvalidOperation 2026 error will be reported in the operation status. 2027 2028 Command Remarks 2029 partition Partition a Flash device. 2030 All the prerequisites for 2031 partitioning must be met for 2032 this command to succeed. 2033 2034 Command table Parameters 2035 1) partition PartitioningDestinationName 2036 PartitioningPartitionCount 2037 PartitioningPartitionSizes (opt) 2038 PartitioningNotifyOnCompletion (opt)" 2039 DEFVAL { partition } 2040 ::= { ciscoFlashPartitioningEntry 2 } 2041 2042ciscoFlashPartitioningDestinationName OBJECT-TYPE 2043 SYNTAX DisplayString (SIZE (0..255)) 2044 MAX-ACCESS read-create 2045 STATUS current 2046 DESCRIPTION 2047 "Destination device name. This name will be the value 2048 obtained from FlashDeviceName. 2049 If the name is not specified, the default Flash device 2050 will be assumed." 2051 DEFVAL { ''B } 2052 ::= { ciscoFlashPartitioningEntry 3 } 2053 2054ciscoFlashPartitioningPartitionCount OBJECT-TYPE 2055 SYNTAX Unsigned32 (1..4294967295) 2056 MAX-ACCESS read-create 2057 STATUS current 2058 DESCRIPTION 2059 "This object is used to specify the number of 2060 partitions to be created. Its value cannot exceed 2061 the value of ciscoFlashDeviceMaxPartitions. 2062 2063 To undo partitioning (revert to a single partition), 2064 this object must have the value 1." 2065 DEFVAL { 2 } 2066 ::= { ciscoFlashPartitioningEntry 4 } 2067 2068ciscoFlashPartitioningPartitionSizes OBJECT-TYPE 2069 SYNTAX DisplayString 2070 MAX-ACCESS read-create 2071 STATUS current 2072 DESCRIPTION 2073 "This object is used to explicitly specify the size 2074 of each partition to be created. 2075 The size of each partition will be in units of 2076 ciscoFlashDeviceMinPartitionSize. 2077 The value of this object will be in the form: 2078 <part1>:<part2>...:<partn> 2079 2080 If partition sizes are not specified, the system 2081 will calculate default sizes based on the partition 2082 count, the minimum partition size, and the device 2083 size. Partition size need not be specified when 2084 undoing partitioning (partition count is 1). 2085 If partition sizes are specified, the number of 2086 sizes specified must exactly match the partition 2087 count. If not, the partitioning command will be 2088 rejected with the invalidPartitionSizes error ." 2089 DEFVAL { ''B } 2090 ::= { ciscoFlashPartitioningEntry 5 } 2091 2092ciscoFlashPartitioningStatus OBJECT-TYPE 2093 SYNTAX INTEGER { 2094 partitioningInProgress(1), 2095 partitioningOperationSuccess(2), 2096 partitioningInvalidOperation(3), 2097 partitioningInvalidDestName(4), 2098 partitioningInvalidPartitionCount(5), 2099 partitioningInvalidPartitionSizes(6), 2100 partitioningDeviceBusy(7), 2101 partitioningDeviceOpenError(8), 2102 partitioningDeviceError(9), 2103 partitioningNoMemory(10), 2104 partitioningUnknownFailure(11) 2105 } 2106 MAX-ACCESS read-only 2107 STATUS current 2108 DESCRIPTION 2109 "The status of the specified partitioning operation. 2110 partitioningInProgress : 2111 specified operation is active 2112 2113 partitioningOperationSuccess : 2114 specified operation is supported and completed 2115 successfully 2116 2117 partitioningInvalidOperation : 2118 command invalid or command-protocol-device 2119 combination unsupported 2120 2121 partitioningInvalidDestName : 2122 invalid target name (file or partition or 2123 device name) specified 2124 2125 partitioningInvalidPartitionCount : 2126 invalid partition count specified for the 2127 partitioning command 2128 2129 partitioningInvalidPartitionSizes : 2130 invalid partition size, or invalid count of 2131 partition sizes 2132 2133 partitioningDeviceBusy : 2134 specified device is in use and locked by 2135 another process 2136 2137 partitioningDeviceOpenError : 2138 invalid device name 2139 2140 partitioningDeviceError : 2141 device read, write or erase error 2142 2143 partitioningNoMemory : 2144 system running low on memory 2145 2146 partitioningUnknownFailure : 2147 failure unknown" 2148 ::= { ciscoFlashPartitioningEntry 6 } 2149 2150ciscoFlashPartitioningNotifyOnCompletion OBJECT-TYPE 2151 SYNTAX TruthValue 2152 MAX-ACCESS read-create 2153 STATUS current 2154 DESCRIPTION 2155 "Specifies whether or not a notification should be 2156 generated on the completion of the partitioning operation. 2157 If specified, ciscoFlashPartitioningCompletionTrap 2158 will be generated. It is the responsibility of the 2159 management entity to ensure that the SNMP administrative 2160 model is configured in such a way as to allow the 2161 notification to be delivered." 2162 DEFVAL { false } 2163 ::= { ciscoFlashPartitioningEntry 7 } 2164 2165ciscoFlashPartitioningTime OBJECT-TYPE 2166 SYNTAX TimeTicks 2167 MAX-ACCESS read-only 2168 STATUS current 2169 DESCRIPTION 2170 "Time taken for the operation. This object will 2171 be like a stopwatch, starting when the operation 2172 starts, stopping when the operation completes. 2173 If a management entity keeps a database of completion 2174 times for various operations, it can then use the 2175 stopwatch capability to display percentage completion 2176 time." 2177 ::= { ciscoFlashPartitioningEntry 8 } 2178 2179ciscoFlashPartitioningEntryStatus OBJECT-TYPE 2180 SYNTAX RowStatus 2181 MAX-ACCESS read-create 2182 STATUS current 2183 DESCRIPTION 2184 "The status of this table entry." 2185 ::= { ciscoFlashPartitioningEntry 9 } 2186 2187 2188 2189ciscoFlashMiscOpTable OBJECT-TYPE 2190 SYNTAX SEQUENCE OF CiscoFlashMiscOpEntry 2191 MAX-ACCESS not-accessible 2192 STATUS current 2193 DESCRIPTION 2194 "A table of misc Flash operation entries. Each 2195 entry represents a Flash operation that 2196 has been initiated." 2197 ::= { ciscoFlashOps 3 } 2198 2199ciscoFlashMiscOpEntry OBJECT-TYPE 2200 SYNTAX CiscoFlashMiscOpEntry 2201 MAX-ACCESS not-accessible 2202 STATUS current 2203 DESCRIPTION 2204 "A Flash operation entry. Each entry consists of a 2205 command, a target, and any optional parameters. 2206 2207 A management station wishing to create an entry should 2208 first generate a pseudo-random serial number to be used 2209 as the index to this sparse table. The station should 2210 then create the associated instance of the row status 2211 object. It must also, either in the same or in successive 2212 PDUs, create the associated instance of the command and 2213 parameter objects. It should also modify the default values 2214 for any of the parameter objects if the defaults are not 2215 appropriate. 2216 2217 Once the appropriate instances of all the command 2218 objects have been created, either by an explicit SNMP 2219 set request or by default, the row status should be set 2220 to active to initiate the operation. Note that this entire 2221 procedure may be initiated via a single set request which 2222 specifies a row status of createAndGo as well as specifies 2223 valid values for the non-defaulted parameter objects. 2224 2225 Once an operation has been activated, it cannot be 2226 stopped. 2227 2228 Once the operation completes, the management station should 2229 retrieve the value of the status object (and time if 2230 desired), and delete the entry. In order to prevent old 2231 entries from clogging the table, entries will be aged out, 2232 but an entry will never be deleted within 5 minutes of 2233 completing." 2234 INDEX { ciscoFlashMiscOpSerialNumber } 2235 ::= { ciscoFlashMiscOpTable 1 } 2236 2237CiscoFlashMiscOpEntry ::= SEQUENCE { 2238 ciscoFlashMiscOpSerialNumber Integer32, 2239 ciscoFlashMiscOpCommand INTEGER, 2240 ciscoFlashMiscOpDestinationName DisplayString, 2241 ciscoFlashMiscOpStatus INTEGER, 2242 ciscoFlashMiscOpNotifyOnCompletion TruthValue, 2243 ciscoFlashMiscOpTime TimeTicks, 2244 ciscoFlashMiscOpEntryStatus RowStatus 2245} 2246 2247ciscoFlashMiscOpSerialNumber OBJECT-TYPE 2248 SYNTAX Integer32 (0..2147483647) 2249 MAX-ACCESS not-accessible 2250 STATUS current 2251 DESCRIPTION 2252 "Object which specifies a unique entry in the 2253 table. A management station wishing to initiate a 2254 flash operation should use a pseudo-random value for 2255 this object when creating or modifying an instance of 2256 a ciscoFlashMiscOpEntry." 2257 ::= { ciscoFlashMiscOpEntry 1 } 2258 2259ciscoFlashMiscOpCommand OBJECT-TYPE 2260 SYNTAX INTEGER { 2261 erase(1), 2262 verify(2), 2263 delete(3), 2264 undelete(4), 2265 squeeze(5), 2266 format(6) 2267 } 2268 MAX-ACCESS read-create 2269 STATUS current 2270 DESCRIPTION 2271 "The command to be executed. Mandatory. 2272 Note that it is possible for a system to support 2273 multiple file systems (different file systems on 2274 different Flash devices, or different file systems 2275 on different partitions within a device). Each such 2276 file system may support only a subset of these commands. 2277 If a command is unsupported, the miscOpInvalidOperation(3) 2278 error will be reported in the operation status. 2279 2280 Command Remarks 2281 erase Erase flash. 2282 verify Verify flash file checksum. 2283 delete Delete a file. 2284 undelete Revive a deleted file . 2285 Note that there are limits on 2286 the number of times a file can 2287 be deleted and undeleted. When 2288 this limit is exceeded, the 2289 system will return the appropriate 2290 error. 2291 squeeze Recover space occupied by 2292 deleted files. This command 2293 preserves the good files, erases 2294 out the file system, then restores 2295 the preserved good files. 2296 format Format a flash device. 2297 2298 Command table Parameters 2299 erase MiscOpDestinationName 2300 MiscOpNotifyOnCompletion (opt) 2301 verify MiscOpDestinationName 2302 MiscOpNotifyOnCompletion (opt) 2303 delete MiscOpDestinationName 2304 MiscOpNotifyOnCompletion (opt) 2305 undelete MiscOpDestinationName 2306 MiscOpNotifyOnCompletion (opt) 2307 squeeze MiscOpDestinationName 2308 MiscOpNotifyOnCompletion (opt) 2309 format MiscOpDestinationName 2310 MiscOpNotifyOnCompletion (opt)" 2311 ::= { ciscoFlashMiscOpEntry 2 } 2312 2313ciscoFlashMiscOpDestinationName OBJECT-TYPE 2314 SYNTAX DisplayString (SIZE (0..255)) 2315 MAX-ACCESS read-create 2316 STATUS current 2317 DESCRIPTION 2318 "Destination file, or partition name. 2319 File name must be of the form 2320 [device>:][<partition>:]<file> 2321 where <device> is a value obtained from FlashDeviceName, 2322 <partition> is obtained from FlashPartitionName 2323 and <file> is the name of a file in Flash. 2324 While leading and/or trailing whitespaces are acceptable, 2325 no whitespaces are allowed within the path itself. 2326 2327 A management station could derive its own partition name 2328 as per the description for the ciscoFlashPartitionName 2329 object. 2330 If <device> is not specified, the default Flash device 2331 will be assumed. 2332 If <partition> is not specified, the default partition 2333 will be assumed. If a device is not partitioned into 2 2334 or more partitions, this value may be left out. 2335 2336 For an operation on a partition, eg., the erase 2337 command, this object would specify the partition name 2338 in the form: 2339 [device>:][<partition>:]" 2340 DEFVAL { ''B } 2341 ::= { ciscoFlashMiscOpEntry 3 } 2342 2343ciscoFlashMiscOpStatus OBJECT-TYPE 2344 SYNTAX INTEGER { 2345 miscOpInProgress(1), 2346 miscOpOperationSuccess(2), 2347 miscOpInvalidOperation(3), 2348 miscOpInvalidDestName(4), 2349 miscOpDeviceBusy(5), 2350 miscOpDeviceOpenError(6), 2351 miscOpDeviceError(7), 2352 miscOpDeviceNotProgrammable(8), 2353 miscOpFileOpenError(9), 2354 miscOpFileDeleteFailure(10), 2355 miscOpFileUndeleteFailure(11), 2356 miscOpFileChecksumError(12), 2357 miscOpNoMemory(13), 2358 miscOpUnknownFailure(14), 2359 miscOpSqueezeFailure(18), 2360 miscOpNoSuchFile(19), 2361 miscOpFormatFailure(20) 2362 } 2363 MAX-ACCESS read-only 2364 STATUS current 2365 DESCRIPTION 2366 "The status of the specified operation. 2367 miscOpInProgress : 2368 specified operation is active 2369 2370 miscOpOperationSuccess : 2371 specified operation is supported and completed 2372 successfully 2373 2374 miscOpInvalidOperation : 2375 command invalid or command-protocol-device 2376 combination unsupported 2377 2378 miscOpInvalidDestName : 2379 invalid target name (file or partition or 2380 device name) specified 2381 2382 miscOpDeviceBusy : 2383 specified device is in use and locked by another 2384 process 2385 2386 miscOpDeviceOpenError : 2387 invalid device name 2388 2389 miscOpDeviceError : 2390 device read, write or erase error 2391 2392 miscOpDeviceNotProgrammable : 2393 device is read-only but a write or erase 2394 operation was specified 2395 2396 miscOpFileOpenError : 2397 invalid file name; file not found in partition 2398 2399 miscOpFileDeleteFailure : 2400 file could not be deleted; delete count exceeded 2401 2402 miscOpFileUndeleteFailure : 2403 file could not be undeleted; undelete count 2404 exceeded 2405 2406 miscOpFileChecksumError : 2407 file has a bad checksum 2408 2409 miscOpNoMemory : 2410 system running low on memory 2411 2412 miscOpUnknownFailure : 2413 failure unknown 2414 2415 miscOpSqueezeFailure : 2416 the squeeze operation failed 2417 2418 miscOpNoSuchFile : 2419 a valid but nonexistent file name was specified 2420 2421 miscOpFormatFailure : 2422 the format operation failed" 2423 ::= { ciscoFlashMiscOpEntry 4 } 2424 2425ciscoFlashMiscOpNotifyOnCompletion OBJECT-TYPE 2426 SYNTAX TruthValue 2427 MAX-ACCESS read-create 2428 STATUS current 2429 DESCRIPTION 2430 "Specifies whether or not a notification should be 2431 generated on the completion of an operation. 2432 If specified, ciscoFlashMiscOpCompletionTrap 2433 will be generated. It is the responsibility of the 2434 management entity to ensure that the SNMP administrative 2435 model is configured in such a way as to allow the 2436 notification to be delivered." 2437 DEFVAL { false } 2438 ::= { ciscoFlashMiscOpEntry 5 } 2439 2440ciscoFlashMiscOpTime OBJECT-TYPE 2441 SYNTAX TimeTicks 2442 MAX-ACCESS read-only 2443 STATUS current 2444 DESCRIPTION 2445 "Time taken for the operation. This object will 2446 be like a stopwatch, starting when the operation 2447 starts, stopping when the operation completes. 2448 If a management entity keeps a database of completion 2449 times for various operations, it can then use the 2450 stopwatch capability to display percentage completion 2451 time." 2452 ::= { ciscoFlashMiscOpEntry 6 } 2453 2454ciscoFlashMiscOpEntryStatus OBJECT-TYPE 2455 SYNTAX RowStatus 2456 MAX-ACCESS read-create 2457 STATUS current 2458 DESCRIPTION 2459 "The status of this table entry." 2460 ::= { ciscoFlashMiscOpEntry 7 } 2461 2462 2463 2464-- Configuration 2465 2466ciscoFlashCfgDevInsNotifEnable OBJECT-TYPE 2467 SYNTAX TruthValue 2468 MAX-ACCESS read-write 2469 STATUS current 2470 DESCRIPTION 2471 "Specifies whether or not a notification should be 2472 generated on the insertion of a Flash device. 2473 2474 If the value of this object is 'true' then the 2475 ciscoFlashDeviceInsertedNotif notification 2476 will be generated. 2477 2478 If the value of this object is 'false' then the 2479 ciscoFlashDeviceInsertedNotif notification 2480 will not be generated. 2481 2482 It is the responsibility of the management entity to 2483 ensure that the SNMP administrative model is 2484 configured in such a way as to allow the 2485 notification to be delivered." 2486 DEFVAL { false } 2487 ::= { ciscoFlashCfg 1 } 2488 2489ciscoFlashCfgDevRemNotifEnable OBJECT-TYPE 2490 SYNTAX TruthValue 2491 MAX-ACCESS read-write 2492 STATUS current 2493 DESCRIPTION 2494 "Specifies whether or not a notification should be 2495 generated on the removal of a Flash device. 2496 2497 If the value of this object is 'true' then the 2498 ciscoFlashDeviceRemovedNotif notification 2499 will be generated. 2500 2501 If the value of this object is 'false' then the 2502 ciscoFlashDeviceRemovedNotif notification 2503 will not be generated. 2504 2505 It is the responsibility of the management entity to 2506 ensure that the SNMP administrative model is 2507 configured in such a way as to allow the 2508 notification to be delivered." 2509 DEFVAL { false } 2510 ::= { ciscoFlashCfg 2 } 2511 2512ciscoFlashPartitionLowSpaceNotifEnable OBJECT-TYPE 2513 SYNTAX TruthValue 2514 MAX-ACCESS read-write 2515 STATUS current 2516 DESCRIPTION 2517 "This object specifies whether or not a notification should be 2518 generated when the free space falls below the threshold value on 2519 a flash partition and on recovery from low space. 2520 2521 If the value of this object is 'true' then 2522 ciscoFlashPartitionLowSpaceNotif and 2523 ciscoFlashPartitionLowSpaceRecoveryNotif notifications will be 2524 generated. 2525 2526 If the value of this object is 'false' then the 2527 ciscoFlashPartitionLowSpaceNotif and 2528 ciscoFlashPartitionLowSpaceRecoveryNotif notifications 2529 will not be generated. 2530 2531 It is the responsibility of the management entity to 2532 ensure that the SNMP administrative model is 2533 configured in such a way as to allow the 2534 notifications to be delivered." 2535 ::= { ciscoFlashCfg 3 } 2536-- Traps (or notifications ??) 2537 2538ciscoFlashMIBTraps OBJECT IDENTIFIER 2539 ::= { ciscoFlashMIBTrapPrefix 0 } 2540 2541 2542ciscoFlashCopyCompletionTrap NOTIFICATION-TYPE 2543 OBJECTS { ciscoFlashCopyStatus } 2544 STATUS current 2545 DESCRIPTION 2546 "A ciscoFlashCopyCompletionTrap is sent at the 2547 completion of a flash copy operation if such a trap 2548 was requested when the operation was initiated." 2549 ::= { ciscoFlashMIBTraps 1 } 2550 2551ciscoFlashPartitioningCompletionTrap NOTIFICATION-TYPE 2552 OBJECTS { ciscoFlashPartitioningStatus } 2553 STATUS current 2554 DESCRIPTION 2555 "A ciscoFlashPartitioningCompletionTrap is sent at the 2556 completion of a partitioning operation if such a trap 2557 was requested when the operation was initiated." 2558 ::= { ciscoFlashMIBTraps 2 } 2559 2560ciscoFlashMiscOpCompletionTrap NOTIFICATION-TYPE 2561 OBJECTS { ciscoFlashMiscOpStatus } 2562 STATUS current 2563 DESCRIPTION 2564 "A ciscoFlashMiscOpCompletionTrap is sent at the 2565 completion of a miscellaneous flash operation 2566 (enumerated in ciscoFlashMiscOpCommand) if such a trap 2567 was requested when the operation was initiated." 2568 ::= { ciscoFlashMIBTraps 3 } 2569 2570ciscoFlashDeviceChangeTrap NOTIFICATION-TYPE 2571 OBJECTS { 2572 ciscoFlashDeviceMinPartitionSize, 2573 ciscoFlashDeviceName 2574 } 2575 STATUS deprecated 2576 DESCRIPTION 2577 "A ciscoFlashDeviceChangeTrap is sent whenever a 2578 removable Flash device is inserted or removed." 2579 ::= { ciscoFlashMIBTraps 4 } 2580 2581ciscoFlashDeviceInsertedNotif NOTIFICATION-TYPE 2582 OBJECTS { 2583 ciscoFlashDeviceMinPartitionSize, 2584 ciscoFlashDeviceName 2585 } 2586 STATUS deprecated 2587 DESCRIPTION 2588 "A ciscoFlashDeviceInsertedNotif notification is sent 2589 whenever a removable Flash device is inserted." 2590 ::= { ciscoFlashMIBTraps 5 } 2591 2592ciscoFlashDeviceRemovedNotif NOTIFICATION-TYPE 2593 OBJECTS { ciscoFlashDeviceName } 2594 STATUS deprecated 2595 DESCRIPTION 2596 "A ciscoFlashDeviceRemovedNotif notification is sent 2597 whenever a removable Flash device is removed." 2598 ::= { ciscoFlashMIBTraps 6 } 2599 2600ciscoFlashDeviceInsertedNotifRev1 NOTIFICATION-TYPE 2601 OBJECTS { 2602 ciscoFlashDeviceMinPartitionSize, 2603 ciscoFlashDeviceNameExtended 2604 } 2605 STATUS current 2606 DESCRIPTION 2607 "A ciscoFlashDeviceInsertedNotif notification is sent 2608 whenever a removable Flash device is inserted 2609 2610 ciscoFlashDeviceInsertedNotifRev1 depcrecates 2611 ciscoFlashDeviceInsertedNotif since it uses 2612 ciscoFlashDeviceName as a varbind which is 2613 deprecated" 2614 ::= { ciscoFlashMIBTraps 7 } 2615 2616ciscoFlashDeviceRemovedNotifRev1 NOTIFICATION-TYPE 2617 OBJECTS { ciscoFlashDeviceNameExtended } 2618 STATUS current 2619 DESCRIPTION 2620 "A ciscoFlashDeviceRemovedNotif notification is sent 2621 whenever a removable Flash device is removed. 2622 2623 ciscoFlashDeviceRemovedNotifRev1 depcrecates 2624 ciscoFlashDeviceRemovedNotif since it uses 2625 ciscoFlashDeviceName as a varbind which is 2626 deprecated" 2627 ::= { ciscoFlashMIBTraps 8 } 2628 2629ciscoFlashPartitionLowSpaceNotif NOTIFICATION-TYPE 2630 OBJECTS { 2631 ciscoFlashPartitionName, 2632 ciscoFlashPartitionFreeSpaceExtended, 2633 ciscoFlashPartitionLowSpaceNotifThreshold 2634 } 2635 STATUS current 2636 DESCRIPTION 2637 "A ciscoFlashPartitionLowSpaceNotif notification is sent 2638 when the percentage of free space in a flash partition falls 2639 below ciscoFlashPartitionLowSpaceNotifThreshold.This 2640 notification will be generated when the value of 2641 ciscoFlashPartitionLowSpaceNotifEnable is 2642 true. 2643 2644 ciscoFlashPartitionName indicates the name of the flash 2645 partition for which this notification has been sent. 2646 2647 ciscoFlashPartitionFreeSpaceExtended indicates the free space 2648 available with in the flash partition. 2649 2650 ciscoFlashPartitionLowSpaceNotifThreshold indicates the minimum 2651 threshold value in percentage of free space for each partition." 2652 ::= { ciscoFlashMIBTraps 9 } 2653 2654ciscoFlashPartitionLowSpaceRecoveryNotif NOTIFICATION-TYPE 2655 OBJECTS { 2656 ciscoFlashPartitionName, 2657 ciscoFlashPartitionFreeSpaceExtended, 2658 ciscoFlashPartitionLowSpaceNotifThreshold 2659 } 2660 STATUS current 2661 DESCRIPTION 2662 "A ciscoFlashPartitionLowSpaceRecoveryNotif notification is sent 2663 whenever the free space in a flash partition becomes 2664 normal once it has gone low. This notification will be 2665 generated 2666 when the value of ciscoFlashPartitionLowSpaceNotifEnable is 2667 true. This trap is generated as a recovery notification for 2668 ciscoFlashPartitionLowSpaceNotif. 2669 2670 ciscoFlashPartitionName indicates the name of the flash 2671 partition for which this notification has been sent. 2672 2673 ciscoFlashPartitionFreeSpaceExtended indicates the free space 2674 available with in the flash partition. 2675 2676 ciscoFlashPartitionLowSpaceNotifThreshold indicates the minimum 2677 threshold value in percentage of free space for each partition." 2678 ::= { ciscoFlashMIBTraps 10 } 2679 2680-- Conformance information 2681 2682ciscoFlashDeviceChangeExtTrap NOTIFICATION-TYPE 2683 OBJECTS { 2684 ciscoFlashDeviceMinPartitionSizeExtended, 2685 ciscoFlashDeviceNameExtended 2686 } 2687 STATUS current 2688 DESCRIPTION 2689 "A ciscoFlashDeviceChangeExtTrap is sent whenever a 2690 removable Flash device is inserted or removed." 2691 ::= { ciscoFlashMIBTraps 11 } 2692 2693ciscoFlashDeviceInsertedExtNotif NOTIFICATION-TYPE 2694 OBJECTS { 2695 ciscoFlashDeviceMinPartitionSizeExtended, 2696 ciscoFlashDeviceNameExtended 2697 } 2698 STATUS current 2699 DESCRIPTION 2700 "A ciscoFlashDeviceInsertedExtNotif notification is sent 2701 whenever a removable Flash device is inserted." 2702 ::= { ciscoFlashMIBTraps 12 } 2703 2704ciscoFlashDeviceRemovedExtNotif NOTIFICATION-TYPE 2705 OBJECTS { 2706 ciscoFlashDeviceMinPartitionSizeExtended, 2707 ciscoFlashDeviceNameExtended 2708 } 2709 STATUS current 2710 DESCRIPTION 2711 "A ciscoFlashDeviceRemovedExtNotif notification is sent 2712 whenever a removable Flash device removed." 2713 ::= { ciscoFlashMIBTraps 13 } 2714 2715ciscoFlashMIBConformance OBJECT IDENTIFIER 2716 ::= { ciscoFlashMIB 2 } 2717 2718ciscoFlashMIBCompliances OBJECT IDENTIFIER 2719 ::= { ciscoFlashMIBConformance 1 } 2720 2721ciscoFlashMIBGroups OBJECT IDENTIFIER 2722 ::= { ciscoFlashMIBConformance 2 } 2723 2724 2725-- Compliance statements 2726 2727ciscoFlashMIBCompliance MODULE-COMPLIANCE 2728 STATUS deprecated 2729 DESCRIPTION 2730 "The compliance statement for entities that support 2731 the Cisco Flash MIB." 2732 MODULE -- this module 2733 MANDATORY-GROUPS { 2734 ciscoFlashDeviceInfoGroup, 2735 ciscoFlashPartitionInfoGroup, 2736 ciscoFlashFileInfoGroup, 2737 ciscoFlashChipInfoGroup, 2738 ciscoFlashCopyOpGroup 2739 } 2740 2741 GROUP ciscoFlashDeviceOptionalInfoGroup 2742 DESCRIPTION 2743 "The Flash device optional group contains 2744 objects for features that may be optional 2745 or not available across all systems. 2746 An example is the partitioning feature." 2747 2748 GROUP ciscoFlashPartitioningOpGroup 2749 DESCRIPTION 2750 "The Flash partitioning operations group is 2751 optional. It is intended whenever partitioning 2752 is supported." 2753 2754 GROUP ciscoFlashMiscOpGroup 2755 DESCRIPTION 2756 "The Flash miscellaneous operations group is 2757 optional. It contains operations that are not 2758 essential or not universally supported across 2759 all platforms." 2760 ::= { ciscoFlashMIBCompliances 1 } 2761 2762ciscoFlashMIBComplianceRev1 MODULE-COMPLIANCE 2763 STATUS deprecated 2764 DESCRIPTION 2765 "The compliance statement for entities that support 2766 the Cisco Flash MIB. 2767 2768 This compliance is deprecated by 2769 ciscoFlashMIBComplianceRev2." 2770 MODULE -- this module 2771 MANDATORY-GROUPS { 2772 ciscoFlashDeviceInfoGroup, 2773 ciscoFlashPartitionInfoGroup, 2774 ciscoFlashFileInfoGroupRev1, 2775 ciscoFlashChipInfoGroup, 2776 ciscoFlashCopyOpGroup 2777 } 2778 2779 GROUP ciscoFlashDeviceOptionalInfoGroup 2780 DESCRIPTION 2781 "The Flash device optional group contains 2782 objects for features that may be optional 2783 or not available across all systems. 2784 An example is the partitioning feature." 2785 2786 GROUP ciscoFlashPartitioningOpGroup 2787 DESCRIPTION 2788 "The Flash partitioning operations group is 2789 optional. It is intended whenever partitioning 2790 is supported." 2791 2792 GROUP ciscoFlashMiscOpGroup 2793 DESCRIPTION 2794 "The Flash miscellaneous operations group is 2795 optional. It contains operations that are not 2796 essential or not universally supported across 2797 all platforms." 2798 ::= { ciscoFlashMIBCompliances 2 } 2799 2800ciscoFlashMIBComplianceRev2 MODULE-COMPLIANCE 2801 STATUS deprecated 2802 DESCRIPTION 2803 "The compliance statement for entities that support 2804 the Cisco Flash MIB. 2805 2806 This compliance is deprecated by 2807 ciscoFlashMIBComplianceRev3." 2808 MODULE -- this module 2809 MANDATORY-GROUPS { 2810 ciscoFlashDeviceInfoGroupRev1, 2811 ciscoFlashPartitionInfoGroup, 2812 ciscoFlashFileInfoGroupRev1, 2813 ciscoFlashChipInfoGroup, 2814 ciscoFlashCopyOpGroup 2815 } 2816 2817 GROUP ciscoFlashDeviceOptionalInfoGroup 2818 DESCRIPTION 2819 "The Flash device optional group contains 2820 objects for features that may be optional 2821 or not available across all systems. 2822 An example is the partitioning feature." 2823 2824 GROUP ciscoFlashPartitioningOpGroup 2825 DESCRIPTION 2826 "The Flash partitioning operations group is 2827 optional. It is intended whenever partitioning 2828 is supported." 2829 2830 GROUP ciscoFlashMiscOpGroup 2831 DESCRIPTION 2832 "The Flash miscellaneous operations group is 2833 optional. It contains operations that are not 2834 essential or not universally supported across 2835 all platforms." 2836 2837 GROUP ciscoFlashNotifGroup 2838 DESCRIPTION 2839 "This group contains Notifications 2840 representing flash operations." 2841 ::= { ciscoFlashMIBCompliances 3 } 2842 2843ciscoFlashMIBComplianceRev3 MODULE-COMPLIANCE 2844 STATUS deprecated 2845 DESCRIPTION 2846 "The compliance statement for entities that support 2847 the Cisco Flash MIB. 2848 2849 This compliance is deprecated by 2850 ciscoFlashMIBComplianceRev4." 2851 MODULE -- this module 2852 MANDATORY-GROUPS { 2853 ciscoFlashDeviceInfoGroupRev1, 2854 ciscoFlashPartitionInfoGroup, 2855 ciscoFlashFileInfoGroupRev1, 2856 ciscoFlashChipInfoGroup, 2857 ciscoFlashCopyOpGroupRev1 2858 } 2859 2860 GROUP ciscoFlashDeviceOptionalInfoGroupRev1 2861 DESCRIPTION 2862 "The Flash device optional group contains 2863 objects for features that may be optional 2864 or not available across all systems. 2865 An example is the partitioning feature." 2866 2867 GROUP ciscoFlashPartitioningOpGroup 2868 DESCRIPTION 2869 "The Flash partitioning operations group is 2870 optional. It is intended whenever partitioning 2871 is supported." 2872 2873 GROUP ciscoFlashMiscOpGroup 2874 DESCRIPTION 2875 "The Flash miscellaneous operations group is 2876 optional. It contains operations that are not 2877 essential or not universally supported across 2878 all platforms." 2879 2880 GROUP ciscoFlashNotifGroupRev1 2881 DESCRIPTION 2882 "This group contains Notifications 2883 representing flash operations." 2884 ::= { ciscoFlashMIBCompliances 4 } 2885 2886ciscoFlashMIBComplianceRev4 MODULE-COMPLIANCE 2887 STATUS deprecated 2888 DESCRIPTION 2889 "The compliance statement for entities that support 2890 the Cisco Flash MIB. 2891 2892 This compliance is deprecated by 2893 ciscoFlashMIBComplianceRev5." 2894 MODULE -- this module 2895 MANDATORY-GROUPS { 2896 ciscoFlashDeviceInfoGroupRev2, 2897 ciscoFlashPartitionInfoGroup, 2898 ciscoFlashFileInfoGroupRev1, 2899 ciscoFlashChipInfoGroup, 2900 ciscoFlashCopyOpGroupRev1 2901 } 2902 2903 GROUP ciscoFlashDeviceOptionalInfoGroupRev1 2904 DESCRIPTION 2905 "The Flash device optional group contains 2906 objects for features that may be optional 2907 or not available across all systems. 2908 An example is the partitioning feature." 2909 2910 GROUP ciscoFlashPartitioningOpGroup 2911 DESCRIPTION 2912 "The Flash partitioning operations group is 2913 optional. It is intended whenever partitioning 2914 is supported." 2915 2916 GROUP ciscoFlashMiscOpGroup 2917 DESCRIPTION 2918 "The Flash miscellaneous operations group is 2919 optional. It contains operations that are not 2920 essential or not universally supported across 2921 all platforms." 2922 2923 GROUP ciscoFlashNotifGroupRev1 2924 DESCRIPTION 2925 "This group contains Notifications 2926 representing flash operations." 2927 ::= { ciscoFlashMIBCompliances 5 } 2928 2929ciscoFlashMIBComplianceRev5 MODULE-COMPLIANCE 2930 STATUS deprecated 2931 DESCRIPTION 2932 "The compliance statement for entities that support 2933 the Cisco Flash MIB. 2934 2935 This compliance is deprecated by 2936 ciscoFlashMIBComplianceRev6." 2937 MODULE -- this module 2938 MANDATORY-GROUPS { 2939 ciscoFlashDeviceInfoGroupRev2, 2940 ciscoFlashPartitionInfoGroup, 2941 ciscoFlashFileInfoGroupRev1, 2942 ciscoFlashChipInfoGroup, 2943 ciscoFlashCopyOpGroupRev2 2944 } 2945 2946 GROUP ciscoFlashDeviceOptionalInfoGroup 2947 DESCRIPTION 2948 "The Flash device optional group contains 2949 objects for features that may be optional 2950 or not available across all systems. 2951 An example is the partitioning feature." 2952 2953 GROUP ciscoFlashPartitioningOpGroup 2954 DESCRIPTION 2955 "The Flash partitioning operations group is 2956 optional. It is intended whenever partitioning 2957 is supported." 2958 2959 GROUP ciscoFlashMiscOpGroup 2960 DESCRIPTION 2961 "The Flash miscellaneous operations group is 2962 optional. It contains operations that are not 2963 essential or not universally supported across 2964 all platforms." 2965 2966 GROUP ciscoFlashNotifGroupRev1 2967 DESCRIPTION 2968 "This group contains Notifications 2969 representing flash operations." 2970 ::= { ciscoFlashMIBCompliances 6 } 2971 2972ciscoFlashMIBComplianceRev6 MODULE-COMPLIANCE 2973 STATUS deprecated 2974 DESCRIPTION 2975 "The compliance statement for entities that support 2976 the Cisco Flash MIB. 2977 2978 This compliance is deprecated by 2979 ciscoFlashMIBComplianceRev7." 2980 MODULE -- this module 2981 MANDATORY-GROUPS { 2982 ciscoFlashDeviceInfoGroupRev2, 2983 ciscoFlashPartitionInfoGroup, 2984 ciscoFlashFileInfoGroupRev1, 2985 ciscoFlashChipInfoGroup, 2986 ciscoFlashCopyOpGroupRev2 2987 } 2988 2989 GROUP ciscoFlashDeviceOptionalInfoGroupRev1 2990 DESCRIPTION 2991 "The Flash device optional group contains 2992 objects for features that may be optional 2993 or not available across all systems. 2994 An example is the partitioning feature." 2995 2996 GROUP ciscoFlashPartitioningOpGroup 2997 DESCRIPTION 2998 "The Flash partitioning operations group is 2999 optional. It is intended whenever partitioning 3000 is supported." 3001 3002 GROUP ciscoFlashMiscOpGroup 3003 DESCRIPTION 3004 "The Flash miscellaneous operations group is 3005 optional. It contains operations that are not 3006 essential or not universally supported across 3007 all platforms." 3008 3009 GROUP ciscoFlashNotifGroupRev2 3010 DESCRIPTION 3011 "This group contains Notifications 3012 representing flash operations." 3013 ::= { ciscoFlashMIBCompliances 7 } 3014 3015ciscoFlashMIBComplianceRev7 MODULE-COMPLIANCE 3016 STATUS deprecated 3017 DESCRIPTION 3018 "The compliance statement for entities that support 3019 the Cisco Flash MIB. 3020 3021 This compliance is deprecated by 3022 ciscoFlashMIBComplianceRev8." 3023 MODULE -- this module 3024 MANDATORY-GROUPS { 3025 ciscoFlashDeviceInfoGroupRev2, 3026 ciscoFlashPartitionInfoGroup, 3027 ciscoFlashFileInfoGroupRev1, 3028 ciscoFlashFileInfoGroupSupp1, 3029 ciscoFlashChipInfoGroup, 3030 ciscoFlashCopyOpGroupRev2, 3031 ciscoFlashCopyOpGroupRev3 3032 } 3033 3034 GROUP ciscoFlashDeviceOptionalInfoGroupRev1 3035 DESCRIPTION 3036 "The Flash device optional group contains 3037 objects for features that may be optional 3038 or not available across all systems. 3039 An example is the partitioning feature." 3040 3041 GROUP ciscoFlashPartitioningOpGroup 3042 DESCRIPTION 3043 "The Flash partitioning operations group is 3044 optional. It is intended whenever partitioning 3045 is supported." 3046 3047 GROUP ciscoFlashMiscOpGroup 3048 DESCRIPTION 3049 "The Flash miscellaneous operations group is 3050 optional. It contains operations that are not 3051 essential or not universally supported across 3052 all platforms." 3053 3054 GROUP ciscoFlashNotifGroupRev2 3055 DESCRIPTION 3056 "This group contains Notifications 3057 representing flash operations." 3058 ::= { ciscoFlashMIBCompliances 8 } 3059 3060ciscoFlashMIBComplianceRev8 MODULE-COMPLIANCE 3061 STATUS deprecated 3062 DESCRIPTION 3063 "The compliance statement for entities that support 3064 the Cisco Flash MIB. 3065 3066 This compliance is deprecated by 3067 ciscoFlashMIBComplianceRev9." 3068 MODULE -- this module 3069 MANDATORY-GROUPS { 3070 ciscoFlashDeviceInfoGroupRev2, 3071 ciscoFlashPartitionInfoGroup, 3072 ciscoFlashFileInfoGroupRev1, 3073 ciscoFlashFileInfoGroupSupp1, 3074 ciscoFlashChipInfoGroup, 3075 ciscoFlashCopyOpGroupRev2, 3076 ciscoFlashCopyOpGroupRev3 3077 } 3078 3079 GROUP ciscoFlashDeviceOptionalInfoGroupRev1 3080 DESCRIPTION 3081 "The Flash device optional group contains 3082 objects for features that may be optional 3083 or not available across all systems. 3084 An example is the partitioning feature." 3085 3086 GROUP ciscoFlashPartitioningOpGroup 3087 DESCRIPTION 3088 "The Flash partitioning operations group is 3089 optional. It is intended whenever partitioning 3090 is supported." 3091 3092 GROUP ciscoFlashMiscOpGroup 3093 DESCRIPTION 3094 "The Flash miscellaneous operations group is 3095 optional. It contains operations that are not 3096 essential or not universally supported across 3097 all platforms." 3098 3099 GROUP ciscoFlashNotifGroupRev2 3100 DESCRIPTION 3101 "This group contains Notifications 3102 representing flash operations." 3103 3104 GROUP ciscoFlashFileTypeInfoGroup 3105 DESCRIPTION 3106 "This group contain objects for the device 3107 to represent Flash Files sorted by FlashFileType." 3108 ::= { ciscoFlashMIBCompliances 9 } 3109 3110ciscoFlashMIBComplianceRev9 MODULE-COMPLIANCE 3111 STATUS deprecated 3112 DESCRIPTION 3113 "The compliance statement for entities that support 3114 the Cisco Flash MIB. 3115 3116 This compliance is deprecated by 3117 ciscoFlashMIBComplianceRev10." 3118 MODULE -- this module 3119 MANDATORY-GROUPS { 3120 ciscoFlashPartitionInfoGroup, 3121 ciscoFlashFileInfoGroupRev1, 3122 ciscoFlashFileInfoGroupSupp1, 3123 ciscoFlashChipInfoGroup, 3124 ciscoFlashCopyOpGroupRev2, 3125 ciscoFlashCopyOpGroupRev3 3126 } 3127 3128 GROUP ciscoFlashDeviceOptionalInfoGroupRev1 3129 DESCRIPTION 3130 "The Flash device optional group contains 3131 objects for features that may be optional 3132 or not available across all systems. 3133 An example is the partitioning feature." 3134 3135 GROUP ciscoFlashPartitioningOpGroup 3136 DESCRIPTION 3137 "The Flash partitioning operations group is 3138 optional. It is intended whenever partitioning 3139 is supported." 3140 3141 GROUP ciscoFlashMiscOpGroup 3142 DESCRIPTION 3143 "The Flash miscellaneous operations group is 3144 optional. It contains operations that are not 3145 essential or not universally supported across 3146 all platforms." 3147 3148 GROUP ciscoFlashNotifGroupRev2 3149 DESCRIPTION 3150 "This group contains Notifications 3151 representing flash operations." 3152 3153 GROUP ciscoFlashFileTypeInfoGroup 3154 DESCRIPTION 3155 "This group contain objects for the device 3156 to represent Flash Files sorted by 3157 FlashFileType." 3158 3159 GROUP ciscoFlashDeviceInfoGroupRev2 3160 DESCRIPTION 3161 "This group contain objects for the device 3162 to represent Flash Files sorted by 3163 FlashFileType." 3164 3165 GROUP ciscoFlashDeviceInfoExtGroup 3166 DESCRIPTION 3167 "This group is mandatory for device which suppoorts 3168 flash devices of sizes greater than 4 GB and also 3169 supports ciscoFlashDeviceInfoGroupRev2." 3170 3171 GROUP ciscoFlashPartitionInfoExtGroup 3172 DESCRIPTION 3173 "This group is mandatory for device which suppoorts 3174 flash devices of sizes greater than 4 GB." 3175 ::= { ciscoFlashMIBCompliances 10 } 3176 3177ciscoFlashMIBComplianceRev10 MODULE-COMPLIANCE 3178 STATUS deprecated 3179 DESCRIPTION 3180 "The compliance statement for entities that supports 3181 the Cisco Flash MIB. 3182 3183 This compliance is deprecated by 3184 ciscoFlashMIBComplianceRev11." 3185 MODULE -- this module 3186 MANDATORY-GROUPS { 3187 ciscoFlashPartitionInfoGroup, 3188 ciscoFlashFileInfoGroupRev1, 3189 ciscoFlashFileInfoGroupSupp1, 3190 ciscoFlashChipInfoGroup, 3191 ciscoFlashCopyOpGroupRev2, 3192 ciscoFlashCopyOpGroupRev3 3193 } 3194 3195 GROUP ciscoFlashDeviceOptionalInfoGroupRev1 3196 DESCRIPTION 3197 "The Flash device optional group contains objects for features 3198 that may be optional or not available across all systems. 3199 An example is the partitioning feature" 3200 3201 GROUP ciscoFlashPartitioningOpGroup 3202 DESCRIPTION 3203 "The Flash partitioning operations group is optional. It is 3204 intended whenever partitioning is supported." 3205 3206 GROUP ciscoFlashMiscOpGroup 3207 DESCRIPTION 3208 "The Flash miscellaneous operations group is optional. It 3209 contains operations that are not essential or not universally 3210 supported across all platforms" 3211 3212 GROUP ciscoFlashNotifGroupRev2 3213 DESCRIPTION 3214 "This group contains Notifications representing flash operations" 3215 3216 GROUP ciscoFlashFileTypeInfoGroup 3217 DESCRIPTION 3218 "This group contain objects for the device to represent Flash 3219 Files sorted by FlashFileType" 3220 3221 GROUP ciscoFlashDeviceInfoGroupRev2 3222 DESCRIPTION 3223 "This group contain objects for the device to represent Flash 3224 Files sorted by FlashFileType" 3225 3226 GROUP ciscoFlashDeviceInfoExtGroup 3227 DESCRIPTION 3228 "This group is mandatory for device which suppoorts 3229 flash devices of sizes greater than 4 GB and also 3230 supports ciscoFlashDeviceInfoGroupRev2." 3231 3232 GROUP ciscoFlashPartitionInfoExtGroup 3233 DESCRIPTION 3234 "This group is mandatory for device which suppoorts 3235 flash devices of sizes greater than 4 GB" 3236 3237 GROUP ciscoFlashDeviceInfoExtGroupSupRev1 3238 DESCRIPTION 3239 "This group is mandatory for device which suppoorts 3240 flash devices of sizes greater than 4 GB and also 3241 supports ciscoFlashDeviceInfoGroupRev2." 3242 ::= { ciscoFlashMIBCompliances 11 } 3243 3244ciscoFlashMIBComplianceRev11 MODULE-COMPLIANCE 3245 STATUS current 3246 DESCRIPTION 3247 "The compliance statement for entities that supports 3248 the Cisco Flash MIB." 3249 MODULE -- this module 3250 MANDATORY-GROUPS { 3251 ciscoFlashPartitionInfoGroupRev1, 3252 ciscoFlashFileInfoGroupRev1, 3253 ciscoFlashFileInfoGroupSupp1, 3254 ciscoFlashChipInfoGroup, 3255 ciscoFlashCopyOpGroupRev2, 3256 ciscoFlashCopyOpGroupRev3 3257 } 3258 3259 GROUP ciscoFlashDeviceOptionalInfoGroupRev1 3260 DESCRIPTION 3261 "The Flash device optional group contains objects for features 3262 that may be optional or not available across all systems. 3263 An example is the partitioning feature" 3264 3265 GROUP ciscoFlashPartitioningOpGroup 3266 DESCRIPTION 3267 "The Flash partitioning operations group is optional. It is 3268 intended whenever partitioning is supported." 3269 3270 GROUP ciscoFlashMiscOpGroup 3271 DESCRIPTION 3272 "The Flash miscellaneous operations group is optional. It 3273 contains operations that are not essential or not universally 3274 supported across all platforms" 3275 3276 GROUP ciscoFlashNotifGroupRev3 3277 DESCRIPTION 3278 "This group contains Notifications representing flash operations" 3279 3280 GROUP ciscoFlashFileTypeInfoGroup 3281 DESCRIPTION 3282 "This group contain objects for the device to represent Flash 3283 Files sorted by FlashFileType" 3284 3285 GROUP ciscoFlashDeviceInfoGroupRev2 3286 DESCRIPTION 3287 "This group contain objects for the device to represent Flash 3288 Files sorted by FlashFileType" 3289 3290 GROUP ciscoFlashDeviceInfoExtGroup 3291 DESCRIPTION 3292 "This group is mandatory for device which suppoorts 3293 flash devices of sizes greater than 4 GB and also 3294 supports ciscoFlashDeviceInfoGroupRev2." 3295 3296 GROUP ciscoFlashPartitionInfoExtGroup 3297 DESCRIPTION 3298 "This group is mandatory for device which suppoorts 3299 flash devices of sizes greater than 4 GB" 3300 3301 GROUP ciscoFlashDeviceInfoExtGroupSupRev1 3302 DESCRIPTION 3303 "This group is mandatory for device which suppoorts 3304 flash devices of sizes greater than 4 GB and also 3305 supports ciscoFlashDeviceInfoGroupRev2." 3306 ::= { ciscoFlashMIBCompliances 12 } 3307 3308-- Units of conformance 3309 3310ciscoFlashDeviceInfoGroup OBJECT-GROUP 3311 OBJECTS { 3312 ciscoFlashDevicesSupported, 3313 ciscoFlashDeviceSize, 3314 ciscoFlashDeviceName, 3315 ciscoFlashDeviceDescr, 3316 ciscoFlashDeviceProgrammingJumper, 3317 ciscoFlashDeviceInitTime, 3318 ciscoFlashDeviceChipCount, 3319 ciscoFlashDeviceRemovable 3320 } 3321 STATUS deprecated 3322 DESCRIPTION 3323 "A collection of objects providing mandatory Flash 3324 device level information." 3325 ::= { ciscoFlashMIBGroups 1 } 3326 3327ciscoFlashDeviceOptionalInfoGroup OBJECT-GROUP 3328 OBJECTS { 3329 ciscoFlashDeviceMinPartitionSize, 3330 ciscoFlashDeviceMaxPartitions, 3331 ciscoFlashDevicePartitions, 3332 ciscoFlashDeviceController, 3333 ciscoFlashDeviceCard 3334 } 3335 STATUS deprecated 3336 DESCRIPTION 3337 "A collection of optional objects providing 3338 Flash device level information." 3339 ::= { ciscoFlashMIBGroups 2 } 3340 3341ciscoFlashChipInfoGroup OBJECT-GROUP 3342 OBJECTS { 3343 ciscoFlashChipCode, 3344 ciscoFlashChipDescr, 3345 ciscoFlashChipWriteRetries, 3346 ciscoFlashChipEraseRetries, 3347 ciscoFlashChipMaxWriteRetries, 3348 ciscoFlashChipMaxEraseRetries 3349 } 3350 STATUS current 3351 DESCRIPTION 3352 "A collection of objects providing Flash 3353 chip level information." 3354 ::= { ciscoFlashMIBGroups 3 } 3355 3356ciscoFlashPartitionInfoGroup OBJECT-GROUP 3357 OBJECTS { 3358 ciscoFlashPartitionStartChip, 3359 ciscoFlashPartitionEndChip, 3360 ciscoFlashPartitionSize, 3361 ciscoFlashPartitionFreeSpace, 3362 ciscoFlashPartitionFileCount, 3363 ciscoFlashPartitionChecksumAlgorithm, 3364 ciscoFlashPartitionStatus, 3365 ciscoFlashPartitionUpgradeMethod, 3366 ciscoFlashPartitionName, 3367 ciscoFlashPartitionNeedErasure, 3368 ciscoFlashPartitionFileNameLength 3369 } 3370 STATUS deprecated 3371 DESCRIPTION 3372 "A collection of objects providing Flash 3373 partition level information. Where a Flash 3374 device has not been partitioned or does 3375 not support partitioning, a partition is 3376 synonymous with the entire device." 3377 ::= { ciscoFlashMIBGroups 4 } 3378 3379ciscoFlashFileInfoGroup OBJECT-GROUP 3380 OBJECTS { 3381 ciscoFlashFileSize, 3382 ciscoFlashFileChecksum, 3383 ciscoFlashFileStatus, 3384 ciscoFlashFileName 3385 } 3386 STATUS deprecated 3387 DESCRIPTION 3388 "A collection of objects providing Flash 3389 file level information." 3390 ::= { ciscoFlashMIBGroups 5 } 3391 3392ciscoFlashCopyOpGroup OBJECT-GROUP 3393 OBJECTS { 3394 ciscoFlashCopyCommand, 3395 ciscoFlashCopyProtocol, 3396 ciscoFlashCopyServerAddress, 3397 ciscoFlashCopySourceName, 3398 ciscoFlashCopyDestinationName, 3399 ciscoFlashCopyRemoteUserName, 3400 ciscoFlashCopyStatus, 3401 ciscoFlashCopyNotifyOnCompletion, 3402 ciscoFlashCopyTime, 3403 ciscoFlashCopyEntryStatus 3404 } 3405 STATUS deprecated 3406 DESCRIPTION 3407 "A collection of objects providing the ability 3408 to copy files to and from a Flash partition." 3409 ::= { ciscoFlashMIBGroups 6 } 3410 3411ciscoFlashPartitioningOpGroup OBJECT-GROUP 3412 OBJECTS { 3413 ciscoFlashPartitioningCommand, 3414 ciscoFlashPartitioningDestinationName, 3415 ciscoFlashPartitioningPartitionCount, 3416 ciscoFlashPartitioningPartitionSizes, 3417 ciscoFlashPartitioningStatus, 3418 ciscoFlashPartitioningNotifyOnCompletion, 3419 ciscoFlashPartitioningTime, 3420 ciscoFlashPartitioningEntryStatus 3421 } 3422 STATUS current 3423 DESCRIPTION 3424 "A collection of objects providing the ability 3425 to partition a Flash device." 3426 ::= { ciscoFlashMIBGroups 7 } 3427 3428ciscoFlashMiscOpGroup OBJECT-GROUP 3429 OBJECTS { 3430 ciscoFlashMiscOpCommand, 3431 ciscoFlashMiscOpDestinationName, 3432 ciscoFlashMiscOpStatus, 3433 ciscoFlashMiscOpNotifyOnCompletion, 3434 ciscoFlashMiscOpTime, 3435 ciscoFlashMiscOpEntryStatus 3436 } 3437 STATUS current 3438 DESCRIPTION 3439 "A collection of objects providing the ability 3440 to perform misc operations (erase, file verification, 3441 etc) in a Flash device." 3442 ::= { ciscoFlashMIBGroups 8 } 3443 3444ciscoFlashNotifGroup NOTIFICATION-GROUP 3445 NOTIFICATIONS { 3446 ciscoFlashCopyCompletionTrap, 3447 ciscoFlashPartitioningCompletionTrap, 3448 ciscoFlashMiscOpCompletionTrap, 3449 ciscoFlashDeviceChangeTrap 3450 } 3451 STATUS deprecated 3452 DESCRIPTION 3453 "The set of notification defined by this MIB." 3454 ::= { ciscoFlashMIBGroups 9 } 3455 3456ciscoFlashFileInfoGroupRev1 OBJECT-GROUP 3457 OBJECTS { 3458 ciscoFlashFileSize, 3459 ciscoFlashFileChecksum, 3460 ciscoFlashFileStatus, 3461 ciscoFlashFileName, 3462 ciscoFlashFileType 3463 } 3464 STATUS current 3465 DESCRIPTION 3466 "A collection of objects providing Flash 3467 file level information." 3468 ::= { ciscoFlashMIBGroups 10 } 3469 3470ciscoFlashNotifGroupRev1 NOTIFICATION-GROUP 3471 NOTIFICATIONS { 3472 ciscoFlashCopyCompletionTrap, 3473 ciscoFlashPartitioningCompletionTrap, 3474 ciscoFlashMiscOpCompletionTrap, 3475 ciscoFlashDeviceInsertedNotif, 3476 ciscoFlashDeviceRemovedNotif 3477 } 3478 STATUS deprecated 3479 DESCRIPTION 3480 "The set of notification defined by this MIB." 3481 ::= { ciscoFlashMIBGroups 11 } 3482 3483ciscoFlashDeviceInfoGroupRev1 OBJECT-GROUP 3484 OBJECTS { 3485 ciscoFlashDevicesSupported, 3486 ciscoFlashDeviceSize, 3487 ciscoFlashDeviceName, 3488 ciscoFlashDeviceDescr, 3489 ciscoFlashDeviceProgrammingJumper, 3490 ciscoFlashDeviceInitTime, 3491 ciscoFlashDeviceChipCount, 3492 ciscoFlashDeviceRemovable, 3493 ciscoFlashCfgDevInsNotifEnable, 3494 ciscoFlashCfgDevRemNotifEnable 3495 } 3496 STATUS deprecated 3497 DESCRIPTION 3498 "A collection of objects providing mandatory Flash 3499 device level information." 3500 ::= { ciscoFlashMIBGroups 12 } 3501 3502ciscoFlashDeviceOptionalInfoGroupRev1 OBJECT-GROUP 3503 OBJECTS { 3504 ciscoFlashDeviceMinPartitionSize, 3505 ciscoFlashDeviceMaxPartitions, 3506 ciscoFlashDevicePartitions, 3507 ciscoFlashDeviceController, 3508 ciscoFlashPhyEntIndex 3509 } 3510 STATUS current 3511 DESCRIPTION 3512 "A collection of optional objects providing 3513 Flash device level information. This deprecates 3514 ciscoFlashDeviceOptionalInfoGroup object group." 3515 ::= { ciscoFlashMIBGroups 13 } 3516 3517ciscoFlashCopyOpGroupRev1 OBJECT-GROUP 3518 OBJECTS { 3519 ciscoFlashCopyCommand, 3520 ciscoFlashCopyProtocol, 3521 ciscoFlashCopyServerAddress, 3522 ciscoFlashCopySourceName, 3523 ciscoFlashCopyDestinationName, 3524 ciscoFlashCopyRemoteUserName, 3525 ciscoFlashCopyStatus, 3526 ciscoFlashCopyNotifyOnCompletion, 3527 ciscoFlashCopyTime, 3528 ciscoFlashCopyEntryStatus, 3529 ciscoFlashCopyVerify 3530 } 3531 STATUS deprecated 3532 DESCRIPTION 3533 "A collection of objects providing the ability 3534 to copy files to and from a Flash partition. 3535 3536 This group is deprecated by new group 3537 ciscoFlashCopyOpGroupRev2." 3538 ::= { ciscoFlashMIBGroups 14 } 3539 3540ciscoFlashDeviceInfoGroupRev2 OBJECT-GROUP 3541 OBJECTS { 3542 ciscoFlashDevicesSupported, 3543 ciscoFlashDeviceSize, 3544 ciscoFlashDeviceNameExtended, 3545 ciscoFlashDeviceDescr, 3546 ciscoFlashDeviceProgrammingJumper, 3547 ciscoFlashDeviceInitTime, 3548 ciscoFlashDeviceChipCount, 3549 ciscoFlashDeviceRemovable, 3550 ciscoFlashCfgDevInsNotifEnable, 3551 ciscoFlashCfgDevRemNotifEnable 3552 } 3553 STATUS current 3554 DESCRIPTION 3555 "A collection of objects providing mandatory Flash 3556 device level information." 3557 ::= { ciscoFlashMIBGroups 15 } 3558 3559ciscoFlashCopyOpGroupRev2 OBJECT-GROUP 3560 OBJECTS { 3561 ciscoFlashCopyCommand, 3562 ciscoFlashCopyProtocol, 3563 ciscoFlashCopySourceName, 3564 ciscoFlashCopyDestinationName, 3565 ciscoFlashCopyRemoteUserName, 3566 ciscoFlashCopyStatus, 3567 ciscoFlashCopyNotifyOnCompletion, 3568 ciscoFlashCopyTime, 3569 ciscoFlashCopyEntryStatus, 3570 ciscoFlashCopyVerify, 3571 ciscoFlashCopyServerAddrType, 3572 ciscoFlashCopyServerAddrRev1 3573 } 3574 STATUS current 3575 DESCRIPTION 3576 "A collection of objects providing the ability 3577 to copy files to and from a Flash partition. 3578 3579 This Group deprecates ciscoFlashCopyOpGroupRev1." 3580 ::= { ciscoFlashMIBGroups 16 } 3581 3582ciscoFlashNotifGroupRev2 NOTIFICATION-GROUP 3583 NOTIFICATIONS { 3584 ciscoFlashCopyCompletionTrap, 3585 ciscoFlashPartitioningCompletionTrap, 3586 ciscoFlashMiscOpCompletionTrap, 3587 ciscoFlashDeviceInsertedNotifRev1, 3588 ciscoFlashDeviceRemovedNotifRev1 3589 } 3590 STATUS deprecated 3591 DESCRIPTION 3592 "The set of notification defined by this MIB. 3593 ciscoFlashNotifGroupRev2 object is superseded by ciscoFlashNotifGroupRev3." 3594 ::= { ciscoFlashMIBGroups 17 } 3595 3596ciscoFlashCopyOpGroupRev3 OBJECT-GROUP 3597 OBJECTS { ciscoFlashCopyRemotePassword } 3598 STATUS current 3599 DESCRIPTION 3600 "A collection of objects providing the ability 3601 to copy files to and from a Flash partition. 3602 3603 This Group supplements ciscoFlashCopyOpGroupRev2." 3604 ::= { ciscoFlashMIBGroups 18 } 3605 3606ciscoFlashFileInfoGroupSupp1 OBJECT-GROUP 3607 OBJECTS { ciscoFlashFileDate } 3608 STATUS current 3609 DESCRIPTION 3610 "A collection of objects providing Flash 3611 file level information in addition to the 3612 objects found in ciscoFlashFileInfoGroupRev1." 3613 ::= { ciscoFlashMIBGroups 19 } 3614 3615ciscoFlashFileTypeInfoGroup OBJECT-GROUP 3616 OBJECTS { 3617 ciscoFlashFileByTypeSize, 3618 ciscoFlashFileByTypeChecksum, 3619 ciscoFlashFileByTypeStatus, 3620 ciscoFlashFileByTypeName, 3621 ciscoFlashFileByTypeDate 3622 } 3623 STATUS current 3624 DESCRIPTION 3625 "A collection of objects providing Flash 3626 file information which are sorted by file type." 3627 ::= { ciscoFlashMIBGroups 20 } 3628 3629ciscoFlashDeviceInfoExtGroup OBJECT-GROUP 3630 OBJECTS { ciscoFlashDeviceSizeExtended } 3631 STATUS current 3632 DESCRIPTION 3633 "A collection of objects providing high capacity 3634 mandatory Flash device level information." 3635 ::= { ciscoFlashMIBGroups 21 } 3636 3637ciscoFlashPartitionInfoExtGroup OBJECT-GROUP 3638 OBJECTS { 3639 ciscoFlashPartitionSizeExtended, 3640 ciscoFlashPartitionFreeSpaceExtended 3641 } 3642 STATUS current 3643 DESCRIPTION 3644 "A collection of objects providing haigh capacity 3645 Flash partition level information." 3646 ::= { ciscoFlashMIBGroups 22 } 3647 3648ciscoFlashDeviceInfoExtGroupSupRev1 OBJECT-GROUP 3649 OBJECTS { ciscoFlashDeviceMinPartitionSizeExtended } 3650 STATUS current 3651 DESCRIPTION 3652 "A collection of objects providing high capacity 3653 mandatory Flash device level information. 3654 3655 This Group is supplement to ciscoFlashDeviceInfoExtGroup." 3656 ::= { ciscoFlashMIBGroups 23 } 3657 3658ciscoFlashPartitionInfoGroupRev1 OBJECT-GROUP 3659 OBJECTS { 3660 ciscoFlashPartitionStartChip, 3661 ciscoFlashPartitionEndChip, 3662 ciscoFlashPartitionSize, 3663 ciscoFlashPartitionFreeSpace, 3664 ciscoFlashPartitionFileCount, 3665 ciscoFlashPartitionChecksumAlgorithm, 3666 ciscoFlashPartitionStatus, 3667 ciscoFlashPartitionUpgradeMethod, 3668 ciscoFlashPartitionName, 3669 ciscoFlashPartitionNeedErasure, 3670 ciscoFlashPartitionFileNameLength, 3671 ciscoFlashPartitionLowSpaceNotifThreshold, 3672 ciscoFlashPartitionLowSpaceNotifEnable 3673 } 3674 STATUS current 3675 DESCRIPTION 3676 "A collection of objects providing Flash 3677 partition level information. Where a Flash 3678 device has not been partitioned or does 3679 not support partitioning, a partition is 3680 synonymous with the entire device." 3681 ::= { ciscoFlashMIBGroups 24 } 3682 3683ciscoFlashNotifGroupRev3 NOTIFICATION-GROUP 3684 NOTIFICATIONS { 3685 ciscoFlashCopyCompletionTrap, 3686 ciscoFlashPartitioningCompletionTrap, 3687 ciscoFlashMiscOpCompletionTrap, 3688 ciscoFlashDeviceInsertedNotifRev1, 3689 ciscoFlashDeviceRemovedNotifRev1, 3690 ciscoFlashPartitionLowSpaceNotif, 3691 ciscoFlashPartitionLowSpaceRecoveryNotif, 3692 ciscoFlashDeviceChangeExtTrap, 3693 ciscoFlashDeviceInsertedExtNotif, 3694 ciscoFlashDeviceRemovedExtNotif 3695 } 3696 STATUS current 3697 DESCRIPTION 3698 "The set of notification defined by this MIB." 3699 ::= { ciscoFlashMIBGroups 25 } 3700 3701END 3702 3703