MIB Discovery
1856 modules enregistr├ęs
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 4 (private). 1 (enterprises). 9 (cisco). 9 (ciscoMgmt). 99990 (ciscoImageCheckMIB). 1 (ciscoImageCheckMIBObjects). 1 (ciscoImageCheck). 1 (ciscoImageCheckOpTable). 1 (ciscoImageCheckOpEntry). 3 (ciscoImageCheckStatus)
OID : 1.3.6.1.4.1.9.9.99990.1.1.1.1.3
TXT : iso. org. dod. internet. private. enterprises. cisco. ciscoMgmt. ciscoImageCheckMIB. ciscoImageCheckMIBObjects. ciscoImageCheck. ciscoImageCheckOpTable. ciscoImageCheckOpEntry. ciscoImageCheckStatus
Enfants
Pas d'enfants disponibles pour cet OID
D├ętails
OID1.3.6.1.4.1.9.9.99990.1.1.1.1.3
Module CISCO-IMAGE-CHECK-MIB (CISCO)
NomciscoImageCheckStatus
Accesreadonly
Statuscurrent
Description 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.
SyntaxeEnumeration (1-none, 2-inProgress, 3-inCompatLoose, 4-inCompatStrict, 5-compatible, 6-noStandby, 7-pssErr, 8-extractFail, 9-fileParseErr, 10-getIncompatErr)