MIB Discovery
1930 modules enregistr├ęs
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 4 (private). 1 (enterprises). 9 (cisco). 9 (ciscoMgmt). 198 (ciscoRfSupMIB). 1 (ciscoRfSupMIBObjects). 2 (cRfSupCpu). 1 (cRfSupCpuTable). 1 (cRfSupCpuEntry). 2 (cRfSupCpuActiveSeverity)
OID : 1.3.6.1.4.1.9.9.198.1.2.1.1.2
TXT : iso. org. dod. internet. private. enterprises. cisco. ciscoMgmt. ciscoRfSupMIB. ciscoRfSupMIBObjects. cRfSupCpu. cRfSupCpuTable. cRfSupCpuEntry. cRfSupCpuActiveSeverity
Enfants
Pas d'enfants disponibles pour cet OID
D├ętails
OID1.3.6.1.4.1.9.9.198.1.2.1.1.2
Module CISCO-RF-SUPPLEMENTAL-MIB (CISCO)
NomcRfSupCpuActiveSeverity
Accesreadonly
Statuscurrent
DescriptionThe fault severity of a redundant unit, as calculated by software. The value zero represents a good unit with no detected faults. Higher values represent progressively more serious faults. If it's not possible to determine any current or prior severity information about a unit, the value unknown should be returned. Unlike some severity definitions, cRfSupCpuActiveSeverity should not be downgraded when it switches from being Active. The severity for a faulty Standby unit should correspond to the system impact it would have if it were made to be the Active unit, assuming the severity can be determined while Standby. The severity can be affected by either hardware or software faults with the CPU itself. It can also be affected by faults which prevent this CPU from interacting with one or more other system components (such as linecards), even when the actual faulty Field Replaceable Unit (FRU) is not the CPU itself. As a minimum, the nonFaulty and fullyTrafficAffectingFault values should be supported on any platform supporting this object. Support of the other severity values is preferred, but optional.
SyntaxeEnumeration (0-nonFaulty, 1-nonTrafficAffectingFault, 2-partialTrafficAffectingFault, 3-fullyTrafficAffectingFault, 4-unknown)