| CiscoImageCheckOpEntry |
|
| SEQUENCE |
|
|
|
| |
ciscoImageCheckSerialNum |
Integer32 |
|
| |
ciscoImageCheckImageName |
SnmpAdminString |
|
| |
ciscoImageCheckStatus |
INTEGER |
|
| |
ciscoImageCheckEntryStatus |
RowStatus |
|
| CiscoImgChkResultsEntry |
|
| SEQUENCE |
|
|
|
| |
ciscoImgChkFeatureIndex |
Integer32 |
|
| |
ciscoImgChkCapabIndex |
Integer32 |
|
| |
ciscoImgChkFeatureName |
SnmpAdminString |
|
| |
ciscoImgChkCapabilityName |
SnmpAdminString |
|
| |
ciscoImgChkCapabilityReq |
INTEGER |
|
| |
ciscoImgChkInCompDescr |
SnmpAdminString |
|
| ciscoImageCheckOpEntry |
1.3.6.1.4.1.9.9.99990.1.1.1.1 |
| An Image check operation entry. Each entry consists
of an image name, current status of the check
operation and a row status.
A management station wishing to create an entry should
first generate a pseudo-random serial number to be used
as the index to this sparse table. The station should
then create the associated instance of the row status
object. It must also, create the associated instance
of the image name. This image is checked for
compatibility with the image already running on the
active supervisor.
Once the appropriate instances of all the mandatory
objects have been created, either by an explicit SNMP
set request or by default, the row status should be set
to active to initiate the operation. Note that this entire
procedure may be initiated via a single set request which
specifies a row status of createAndGo.
Once an operation has been activated, it cannot be
stopped.
Once the operation completes, the management station should
retrieve the value of the status object and delete the
entry. In order to prevent old entries from clogging the
table, entries will be aged out, but an entry will never
be deleted within 5 minutes of completing.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
CiscoImageCheckOpEntry |
|
|
| ciscoImageCheckStatus |
1.3.6.1.4.1.9.9.99990.1.1.1.1.3 |
| The current status of the image check operation.
If the status is inCompatLoose(3) or
inCompatStrict(4), one can look at the detail
reasons of incompatibilities by looking at
ciscoImgChkResultsTable described below.
If the status is compatible, then there is no
need to look at the ciscoImgChkResultsTable.
If the status is noStandby(6), pssErr(7),
extractFail(8), fileParseErr(9) or
getIncompatErr(10), there is some internal error
in even starting the check compatibility process,
and hence the ciscoImgChkResultsTable should not
be read for any details.
inProgress(2) - Image check is in progress
inCompatLoose(3) - Loose incompatibility
inCompatStrict(4) - Strict incompatibility
compatible(5) - images are compatible
noStandby(6) - standby supervisor is absent
pssErr(7) - internal error
extractFail(8) - Could not extract image
fileParseErr(9) - Could not parse image
getIncompatErr(10) - internal error in determining
incompatibilities.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
none(1), inProgress(2), inCompatLoose(3), inCompatStrict(4), compatible(5), noStandby(6), pssErr(7), extractFail(8), fileParseErr(9), getIncompatErr(10) |
|
| ciscoImageCheckEntryStatus |
1.3.6.1.4.1.9.9.99990.1.1.1.1.4 |
| The status of this table entry. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
RowStatus |
|
|
| ciscoImgChkResultsEntry |
1.3.6.1.4.1.9.9.99990.1.1.2.1 |
| An entry of ciscoImgChkResultsTable. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
CiscoImgChkResultsEntry |
|
|
