Reference record for OID 1.3.6.1.4.1.9.9.350
- Parent
- 1.3.6.1.4.1.9.9 (ciscoMgmt)
- Node code
- 350
- Node name
- ciscoEntityDiagMIB
- Numeric OID
- 1.3.6.1.4.1.9.9.350
- URN notation
- urn:oid:1.3.6.1.4.1.9.9.350
- Type
- OBJECT IDENTIFIER
- ASN.1 notation
-
{1 3 6 1 4 1 9 9 350}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoEntityDiagMIB(350)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) me1200(9) ciscoMgmt(9) ciscoEntityDiagMIB(350)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoEntityDiagMIB(350)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) me1200(9) ciscoMgmt(9) ciscoEntityDiagMIB(350)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) ciscoEntityDiagMIB(350)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) me1200(9) ciscoMgmt(9) ciscoEntityDiagMIB(350)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) ciscoEntityDiagMIB(350)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) me1200(9) ciscoMgmt(9) ciscoEntityDiagMIB(350)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoEntityDiagMIB(350)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) me1200(9) ciscoMgmt(9) ciscoEntityDiagMIB(350)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoEntityDiagMIB(350)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) me1200(9) ciscoMgmt(9) ciscoEntityDiagMIB(350)}
- {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) ciscoEntityDiagMIB(350)}
- {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) me1200(9) ciscoMgmt(9) ciscoEntityDiagMIB(350)}
- {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) ciscoEntityDiagMIB(350)}
- {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) me1200(9) ciscoMgmt(9) ciscoEntityDiagMIB(350)}
- Additional combinations skipped.
- OID-IRI notation
- /1/3/6/1/4/1/9/9/350
- /ISO/Identified-Organization/6/1/4/1/9/9/350
- /ISO/3/6/1/4/1/9/9/350
- Named path variants
- /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoEntityDiagMIB
- /iso/identified-organization/dod/internet/private/enterprise/me1200/ciscoMgmt/ciscoEntityDiagMIB
- /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoEntityDiagMIB
- /iso/identified-organization/dod/internet/private/enterprises/me1200/ciscoMgmt/ciscoEntityDiagMIB
- /iso/identified-organization/dod/internet/private/ldap-enterprise/cisco/ciscoMgmt/ciscoEntityDiagMIB
- /iso/identified-organization/dod/internet/private/ldap-enterprise/me1200/ciscoMgmt/ciscoEntityDiagMIB
- /iso/identified-organization/dod/internet/private/vendor-objects/cisco/ciscoMgmt/ciscoEntityDiagMIB
- /iso/identified-organization/dod/internet/private/vendor-objects/me1200/ciscoMgmt/ciscoEntityDiagMIB
- /iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoEntityDiagMIB
- /iso/org/dod/internet/private/enterprise/me1200/ciscoMgmt/ciscoEntityDiagMIB
- /iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoEntityDiagMIB
- /iso/org/dod/internet/private/enterprises/me1200/ciscoMgmt/ciscoEntityDiagMIB
- /iso/org/dod/internet/private/ldap-enterprise/cisco/ciscoMgmt/ciscoEntityDiagMIB
- /iso/org/dod/internet/private/ldap-enterprise/me1200/ciscoMgmt/ciscoEntityDiagMIB
- /iso/org/dod/internet/private/vendor-objects/cisco/ciscoMgmt/ciscoEntityDiagMIB
- /iso/org/dod/internet/private/vendor-objects/me1200/ciscoMgmt/ciscoEntityDiagMIB
- Additional combinations skipped.
Descriptions
Descriptions may differ between sources. The primary description is shown first.
Primary description: Circitor
online diagnostics capabilities supported by the
physical entities contained by the system, including chassis,
modules, ports, power supplies, fans, and sensors. In order to
manage the online diagnostic capabilities supported by
a physical entity, it must be represented by a conceptual row
in the entPhysicalTable of the ENTITY-MIB (RFC-2737).
GLOSSARY
Boot-up Diagnostic - a diagnostic consisting of tests intended
to be executed in a reasonable timeframe when a physical entity
boots.
Diagnostic - a suite of tests intended to exercise the
functional integrity of a physical entity.
Diagnostic Level - the degree of completeness that a diagnostic
will exercise a physical entity.
Field Diagnostic - a special suite of tests intended to
exercise the functional integrity of a physical entity in a
manner that is possible when a physical entity is
operational or running an operational image.
Field Diagnostic Image - an image supporting field diagnostics.
A physical entity has to be loaded with a field diagnostic
image before field diagnostics can be executed on the physical
entity.
Health Monitoring - the process of running special
non-intrusive online tests periodically on a physical entity
for the purpose of tracking the overall condition of a physical
entity.
On-Demand Diagnostic - a diagnostic intended to be executed
immediately upon request.
Offline Diagnostic - a diagnostic that consists of tests that
are disruptive in nature, and thus requires the physical entity
being evaluated to be taken offline for the duration.
Online Diagnostic - a diagnostic that consists of tests that
are not disruptive in nature, and thus can be done without
taking the physical entity offline.
Physical Entity - an identifiable physical resource, such as a
chassis, line card, power supply, or communication port. See
RFC-2737, 'Entity MIB (Version 2)', K. McCloghrie and A.
Bierman.
Scheduled Diagnostic - a diagnostic intended to execute at some
time in the future. There exist two types of scheduled
diagnostics: 1) one-shot, which execute only once; and 2)
periodic, which executes at a specific interval.
Test - an exercise intended to determine the functional
integrity of a component comprising a physical entity (e.g., a
port might support an internal loopback test).
Diagnostic Job - Consists of a diagnostic suite
(i.e., a collection of tests) to be executed by a physical
entity.
Parsed from file CISCO-ENTITY-DIAG-MIB.mib
Module: CISCO-ENTITY-DIAG-MIB
Source file: Download CISCO-ENTITY-DIAG-MIB.mib
Publisher path: Mibs; 80,519 bytes
Alternative description: Cisco
online diagnostics capabilities supported by the
physical entities contained by the system, including chassis,
modules, ports, power supplies, fans, and sensors. In order to
manage the online diagnostic capabilities supported by
a physical entity, it must be represented by a conceptual row
in the entPhysicalTable of the ENTITY-MIB (RFC-2737).
GLOSSARY
Boot-up Diagnostic - a diagnostic consisting of tests intended
to be executed in a reasonable timeframe when a physical entity
boots.
Diagnostic - a suite of tests intended to exercise the
functional integrity of a physical entity.
Diagnostic Level - the degree of completeness that a diagnostic
will exercise a physical entity.
Field Diagnostic - a special suite of tests intended to
exercise the functional integrity of a physical entity in a
manner that is possible when a physical entity is
operational or running an operational image.
Field Diagnostic Image - an image supporting field diagnostics.
A physical entity has to be loaded with a field diagnostic
image before field diagnostics can be executed on the physical
entity.
Health Monitoring - the process of running special
non-intrusive online tests periodically on a physical entity
for the purpose of tracking the overall condition of a physical
entity.
On-Demand Diagnostic - a diagnostic intended to be executed
immediately upon request.
Offline Diagnostic - a diagnostic that consists of tests that
are disruptive in nature, and thus requires the physical entity
being evaluated to be taken offline for the duration.
Online Diagnostic - a diagnostic that consists of tests that
are not disruptive in nature, and thus can be done without
taking the physical entity offline.
Physical Entity - an identifiable physical resource, such as a
chassis, line card, power supply, or communication port. See
RFC-2737, 'Entity MIB (Version 2)', K. McCloghrie and A.
Bierman.
Scheduled Diagnostic - a diagnostic intended to execute at some
time in the future. There exist two types of scheduled
diagnostics: 1) one-shot, which execute only once; and 2)
periodic, which executes at a specific interval.
Test - an exercise intended to determine the functional
integrity of a component comprising a physical entity (e.g., a
port might support an internal loopback test).
Diagnostic Job - Consists of a diagnostic suite
(i.e., a collection of tests) to be executed by a physical
entity.
Source file: Download CISCO-ENTITY-DIAG-MIB.my · Publisher's file
Publisher path: cisco/cisco-mibs/main/v2/CISCO-ENTITY-DIAG-MIB.my; 78,759 bytes
Alternative description: MIBdepot
online diagnostics capabilities supported by the
physical entities contained by the system, including chassis,
modules, ports, power supplies, fans, and sensors. In order to
manage the online diagnostic capabilities supported by
a physical entity, it must be represented by a conceptual row
in the entPhysicalTable of the ENTITY-MIB (RFC-2737).
GLOSSARY
Boot-up Diagnostic - a diagnostic consisting of tests intended
to be executed in a reasonable timeframe when a physical entity
boots.
Diagnostic - a suite of tests intended to exercise the
functional integrity of a physical entity.
Diagnostic Level - the degree of completeness that a diagnostic
will exercise a physical entity.
Field Diagnostic - a special suite of tests intended to
exercise the functional integrity of a physical entity in a
manner that is possible when a physical entity is
operational or running an operational image.
Field Diagnostic Image - an image supporting field diagnostics.
A physical entity has to be loaded with a field diagnostic
image before field diagnostics can be executed on the physical
entity.
Health Monitoring - the process of running special
non-intrusive online tests periodically on a physical entity
for the purpose of tracking the overall condition of a physical
entity.
On-Demand Diagnostic - a diagnostic intended to be executed
immediately upon request.
Offline Diagnostic - a diagnostic that consists of tests that
are disruptive in nature, and thus requires the physical entity
being evaluated to be taken offline for the duration.
Online Diagnostic - a diagnostic that consists of tests that
are not disruptive in nature, and thus can be done without
taking the physical entity offline.
Physical Entity - an identifiable physical resource, such as a
chassis, line card, power supply, or communication port. See
RFC-2737, 'Entity MIB (Version 2)', K. McCloghrie and A.
Bierman.
Scheduled Diagnostic - a diagnostic intended to execute at some
time in the future. There exist two types of scheduled
diagnostics: 1) one-shot, which execute only once; and 2)
periodic, which executes at a specific interval.
Test - an exercise intended to determine the functional
integrity of a component comprising a physical entity (e.g., a
port might support an internal loopback test).
Diagnostic Job - Consists of a diagnostic suite
(i.e., a collection of tests) to be executed by a physical
entity.
Source file: Download CISCO-ENTITY-DIAG-MIB.my.txt
File: cisco/CISCO-ENTITY-DIAG-MIB.my.txt; 80,519 bytes
Information from Circitor
ciscoEntityDiagMIB MODULE-IDENTITY
LAST-UPDATED "201005260000Z"
ORGANIZATION "Cisco Systems, Inc."
CONTACT-INFO
"Cisco Systems
Customer Service
Postal: 170 W Tasman Drive
San Jose, CA 95134
Tel: +1 800 553-NETS
E-mail: cs-snmp@cisco.com"
DESCRIPTION
"This MIB module defines the managed objects that describe the
online diagnostics capabilities supported by the
physical entities contained by the system, including chassis,
modules, ports, power supplies, fans, and sensors. In order to
manage the online diagnostic capabilities supported by
a physical entity, it must be represented by a conceptual row
in the entPhysicalTable of the ENTITY-MIB (RFC-2737).
GLOSSARY
Boot-up Diagnostic - a diagnostic consisting of tests intended
to be executed in a reasonable timeframe when a physical entity
boots.
Diagnostic - a suite of tests intended to exercise the
functional integrity of a physical entity.
Diagnostic Level - the degree of completeness that a diagnostic
will exercise a physical entity.
Field Diagnostic - a special suite of tests intended to
exercise the functional integrity of a physical entity in a
manner that is possible when a physical entity is
operational or running an operational image.
Field Diagnostic Image - an image supporting field diagnostics.
A physical entity has to be loaded with a field diagnostic
image before field diagnostics can be executed on the physical
entity.
Health Monitoring - the process of running special
non-intrusive online tests periodically on a physical entity
for the purpose of tracking the overall condition of a physical
entity.
On-Demand Diagnostic - a diagnostic intended to be executed
immediately upon request.
Offline Diagnostic - a diagnostic that consists of tests that
are disruptive in nature, and thus requires the physical entity
being evaluated to be taken offline for the duration.
Online Diagnostic - a diagnostic that consists of tests that
are not disruptive in nature, and thus can be done without
taking the physical entity offline.
Physical Entity - an identifiable physical resource, such as a
chassis, line card, power supply, or communication port. See
RFC-2737, 'Entity MIB (Version 2)', K. McCloghrie and A.
Bierman.
Scheduled Diagnostic - a diagnostic intended to execute at some
time in the future. There exist two types of scheduled
diagnostics: 1) one-shot, which execute only once; and 2)
periodic, which executes at a specific interval.
Test - an exercise intended to determine the functional
integrity of a component comprising a physical entity (e.g., a
port might support an internal loopback test).
Diagnostic Job - Consists of a diagnostic suite
(i.e., a collection of tests) to be executed by a physical
entity."
REVISION "201005260000Z"
DESCRIPTION
"Added ceDiagHMTestThreshWindowGroup."
REVISION "200906300000Z"
DESCRIPTION
"Added ceDiagTestPerfLastTestMethodGroup.
Updated Description of ceDiagTestPerfLastErrorID object."
REVISION "200803120000Z"
DESCRIPTION
"Added ceDiagNotifControlGroup, ceDiagNotifErrorMsgGroup
and ceDiagNotificationGroup."
REVISION "200701090000Z"
DESCRIPTION
"Initial version of this MIB."
::= { ciscoMgmt 350 }
Information from Cisco SMIv1
Source file: Download CISCO-ENTITY-DIAG-MIB-V1SMI.my · Publisher's file
Publisher path: cisco/cisco-mibs/main/v1/CISCO-ENTITY-DIAG-MIB-V1SMI.my; 68,007 bytes
Source file: Download CISCO-ENTITY-DIAG-MIB-V1SMI.my.txt
File: cisco/CISCO-ENTITY-DIAG-MIB-V1SMI.my.txt; 69,602 bytes
ciscoEntityDiagMIB OBJECT IDENTIFIER ::= { ciscoMgmt 350 }
Information from OID Repository
Information from MIBdepot
ciscoEntityDiagMIB MODULE-IDENTITY
LAST-UPDATED "201005260000Z"
ORGANIZATION "Cisco Systems, Inc."
CONTACT-INFO
"Cisco Systems
Customer Service
Postal: 170 W Tasman Drive
San Jose, CA 95134
Tel: +1 800 553-NETS
E-mail: cs-snmp@cisco.com"
DESCRIPTION
"This MIB module defines the managed objects that describe the
online diagnostics capabilities supported by the
physical entities contained by the system, including chassis,
modules, ports, power supplies, fans, and sensors. In order to
manage the online diagnostic capabilities supported by
a physical entity, it must be represented by a conceptual row
in the entPhysicalTable of the ENTITY-MIB (RFC-2737).
GLOSSARY
Boot-up Diagnostic - a diagnostic consisting of tests intended
to be executed in a reasonable timeframe when a physical entity
boots.
Diagnostic - a suite of tests intended to exercise the
functional integrity of a physical entity.
Diagnostic Level - the degree of completeness that a diagnostic
will exercise a physical entity.
Field Diagnostic - a special suite of tests intended to
exercise the functional integrity of a physical entity in a
manner that is possible when a physical entity is
operational or running an operational image.
Field Diagnostic Image - an image supporting field diagnostics.
A physical entity has to be loaded with a field diagnostic
image before field diagnostics can be executed on the physical
entity.
Health Monitoring - the process of running special
non-intrusive online tests periodically on a physical entity
for the purpose of tracking the overall condition of a physical
entity.
On-Demand Diagnostic - a diagnostic intended to be executed
immediately upon request.
Offline Diagnostic - a diagnostic that consists of tests that
are disruptive in nature, and thus requires the physical entity
being evaluated to be taken offline for the duration.
Online Diagnostic - a diagnostic that consists of tests that
are not disruptive in nature, and thus can be done without
taking the physical entity offline.
Physical Entity - an identifiable physical resource, such as a
chassis, line card, power supply, or communication port. See
RFC-2737, 'Entity MIB (Version 2)', K. McCloghrie and A.
Bierman.
Scheduled Diagnostic - a diagnostic intended to execute at some
time in the future. There exist two types of scheduled
diagnostics: 1) one-shot, which execute only once; and 2)
periodic, which executes at a specific interval.
Test - an exercise intended to determine the functional
integrity of a component comprising a physical entity (e.g., a
port might support an internal loopback test).
Diagnostic Job - Consists of a diagnostic suite
(i.e., a collection of tests) to be executed by a physical
entity."
REVISION "201005260000Z"
DESCRIPTION
"Added ceDiagHMTestThreshWindowGroup."
REVISION "200906300000Z"
DESCRIPTION
"Added ceDiagTestPerfLastTestMethodGroup.
Updated Description of ceDiagTestPerfLastErrorID object."
REVISION "200803120000Z"
DESCRIPTION
"Added ceDiagNotifControlGroup, ceDiagNotifErrorMsgGroup
and ceDiagNotificationGroup."
REVISION "200701090000Z"
DESCRIPTION
"Initial version of this MIB."
::= { ciscoMgmt 350 }
Information from Cisco
ciscoEntityDiagMIB MODULE-IDENTITY
LAST-UPDATED "201603110000Z"
ORGANIZATION "Cisco Systems, Inc."
CONTACT-INFO
"Cisco Systems
Customer Service
Postal: 170 W Tasman Drive
San Jose, CA 95134
Tel: +1 800 553-NETS
E-mail: cs-snmp@cisco.com"
DESCRIPTION
"This MIB module defines the managed objects that describe the
online diagnostics capabilities supported by the
physical entities contained by the system, including chassis,
modules, ports, power supplies, fans, and sensors. In order to
manage the online diagnostic capabilities supported by
a physical entity, it must be represented by a conceptual row
in the entPhysicalTable of the ENTITY-MIB (RFC-2737).
GLOSSARY
Boot-up Diagnostic - a diagnostic consisting of tests intended
to be executed in a reasonable timeframe when a physical entity
boots.
Diagnostic - a suite of tests intended to exercise the
functional integrity of a physical entity.
Diagnostic Level - the degree of completeness that a diagnostic
will exercise a physical entity.
Field Diagnostic - a special suite of tests intended to
exercise the functional integrity of a physical entity in a
manner that is possible when a physical entity is
operational or running an operational image.
Field Diagnostic Image - an image supporting field diagnostics.
A physical entity has to be loaded with a field diagnostic
image before field diagnostics can be executed on the physical
entity.
Health Monitoring - the process of running special
non-intrusive online tests periodically on a physical entity
for the purpose of tracking the overall condition of a physical
entity.
On-Demand Diagnostic - a diagnostic intended to be executed
immediately upon request.
Offline Diagnostic - a diagnostic that consists of tests that
are disruptive in nature, and thus requires the physical entity
being evaluated to be taken offline for the duration.
Online Diagnostic - a diagnostic that consists of tests that
are not disruptive in nature, and thus can be done without
taking the physical entity offline.
Physical Entity - an identifiable physical resource, such as a
chassis, line card, power supply, or communication port. See
RFC-2737, 'Entity MIB (Version 2)', K. McCloghrie and A.
Bierman.
Scheduled Diagnostic - a diagnostic intended to execute at some
time in the future. There exist two types of scheduled
diagnostics: 1) one-shot, which execute only once; and 2)
periodic, which executes at a specific interval.
Test - an exercise intended to determine the functional
integrity of a component comprising a physical entity (e.g., a
port might support an internal loopback test).
Diagnostic Job - Consists of a diagnostic suite
(i.e., a collection of tests) to be executed by a physical
entity."
REVISION "201603110000Z"
DESCRIPTION
"Added one new enumaration value disruptive(15)
to ceDiagTestAttributes"
REVISION "201005260000Z"
DESCRIPTION
"Added ceDiagHMTestThreshWindowGroup."
REVISION "200906300000Z"
DESCRIPTION
"Added ceDiagTestPerfLastTestMethodGroup.
Updated Description of ceDiagTestPerfLastErrorID object."
REVISION "200803120000Z"
DESCRIPTION
"Added ceDiagNotifControlGroup, ceDiagNotifErrorMsgGroup
and ceDiagNotificationGroup."
REVISION "200701090000Z"
DESCRIPTION
"Initial version of this MIB."
::= { ciscoMgmt 350 }
First Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)
Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)
Direct children (3)
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.350.0 | ciscoEntityDiagMIBNotifs | 4 | 4 | |
| 1.3.6.1.4.1.9.9.350.1 | ciscoEntityDiagMIBObjects | 9 | 111 | |
| 1.3.6.1.4.1.9.9.350.2 | ciscoEntityDiagMIBConform | 2 | 21 |
Siblings (702)
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.514 | ciscoLwappTextualConventions | 0 | 0 | This module defines textual conventions used throughout the Cisco enterprise MIBs designed for implementation on Central Controlle… |
| 1.3.6.1.4.1.9.9.515 | ciscoLwappWebAuthMIB | 4 | 133 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.516 | ciscoLwappLinkTestMIB | 3 | 57 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.517 | ciscoLwappReapMIB | 3 | 342 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.518 | ciscoLwappMfpMIB | 4 | 68 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.519 | ciscoLwappIdsMIB | 3 | 28 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.520 | ciscoLwappCcxRmMIB | 3 | 45 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.521 | ciscoLwappWlanSecurityMIB | 3 | 77 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.522 | ciscoLwappDot11ClientCalibMIB | 3 | 55 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.523 | ciscoLwappClRoamMIB | 3 | 63 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.524 | ciscoLwappQosMIB | 3 | 322 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.525 | ciscoLwappTsmMIB | 3 | 57 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.529 | ciscoItpMsuRatesMIB | 3 | 61 | This MIB provides information used to manage the number of MTP3 MSUs transmitted and received per processor. Many of the higher … |
| 1.3.6.1.4.1.9.9.530 | ciscoNacTcMIB | 0 | 0 | This module defines the textual conventions for Cisco Network Admission Control(NAC) system. The Cisco Network Admission Control … |
| 1.3.6.1.4.1.9.9.532 | ciscoNATExtMIB | 3 | 13 | This MIB is an extension to the NAT-MIB. This MIB module includes objects for providing the NAT related statistics. Acronyms: NAT… |
| 1.3.6.1.4.1.9.9.533 | ciscoCbpTargetMIB | 3 | 25 | This MIB module defines the managed objects for representing targets which have class-based policy mappings. A target can be any… |
| 1.3.6.1.4.1.9.9.543 | ciscoLicenseMgmtMIB | 3 | 131 | The MIB module for managing licenses on the system. The licensing mechanism provides flexibility to enforce licensing for various… |
| 1.3.6.1.4.1.9.9.548 | ciscoErrDisableMIB | 3 | 45 | This MIB module provides the ability for a Network Management Station (NMS) to configure and monitor the error-disable feature vi… |
| 1.3.6.1.4.1.9.9.572 | ciscoRttMonIPExtMIB | 2 | 57 | This MIB contains extensions to tables in CISCO-RTTMON-MIB to support IP-layer extensions, specifically IPv6 addresses and other … |
| 1.3.6.1.4.1.9.9.573 | ciscoQosTcMIB | 0 | 0 | This module defines the textual conventions used within Cisco Qos MIBs. |
| 1.3.6.1.4.1.9.9.576 | ciscoLwappMobilityMIB | 3 | 106 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.577 | ciscoLwappAclMIB | 3 | 47 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.578 | ciscoRoutePoliciesMIB | 3 | 5 | This module provides a subtree to define OIDs so that various routing 'policies' used by Cisco routers can be expressed. This mod… |
| 1.3.6.1.4.1.9.9.580 | ciscoSwitchQosMIB | 3 | 295 | This MIB module extends the CISCO-CLASS-BASED-QOS-MIB by defining configuration and statistics information specific to the qualit… |
| 1.3.6.1.4.1.9.9.583 | ciscoGslbTcMIB | 0 | 0 | This MIB module defines Textual Conventions and OBJECT-IDENTITIES for use in documents defining management information base (MIBs… |
| 1.3.6.1.4.1.9.9.584 | ciscoEntityDiagTcMIB | 0 | 0 | This module defines the textual conventions used within Cisco Entity Diag MIB. |
| 1.3.6.1.4.1.9.9.585 | ciscoIpSlaEthernetMIB | 3 | 245 | This MIB module consists of two parts. 1) Auto-Ethernet-CFM Control: | | 2) ethernetJitter Stats: | | The first part defines a mechani… |
| 1.3.6.1.4.1.9.9.586 | ciscoNotificationControlMIB | 2 | 28 | This MIB provides network management support to regulate the transmission of notifications generated by a system providing networ… |
| 1.3.6.1.4.1.9.9.589 | ciscoGslbSystemMIB | 3 | 103 | This MIB module defines objects for network and system information of Global Server Load Balancer(GSLB) as a network device. A G… |
| 1.3.6.1.4.1.9.9.590 | ciscoCvpMIB | 3 | 255 | The Cisco Unified Customer Voice Portal (CVP) application integrates with both traditional time-division multiplexing (TDM) and I… |
| 1.3.6.1.4.1.9.9.592 | ciscoPrefPathMIB | 3 | 56 | The MIB module for the management of preferred path. This MIB enables managers to configure and monitor Preferred Path parameters. … |
| 1.3.6.1.4.1.9.9.593 | ciscoFcSdvMIB | 3 | 28 | This MIB instrumentation is for managing Fibre Channel (FC) SAN Device Virtualization (SDV) solution on Cisco Fibre Channel devic… |
| 1.3.6.1.4.1.9.9.594 | ciscoApplicationAccelerationMIB | 3 | 37 | This is a MIB for managing Application Acceleration System(s). This MIB includes instrumentation for providing the performance st… |
| 1.3.6.1.4.1.9.9.595 | ciscoGslbDnsMIB | 3 | 165 | The MIB defines objects for status and statistics information of DNS related operations of Global Server Load Balancer(GSLB). Th… |
| 1.3.6.1.4.1.9.9.597 | ciscoContentServicesMIB | 3 | 349 | Content Service is a capability to examine IP/TCP/UDP headers, payload and enable billing based on the content being provided. Ab… |
| 1.3.6.1.4.1.9.9.598 | ciscoLwappAAAMIB | 3 | 150 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC), that terminate the Light Weigh… |
| 1.3.6.1.4.1.9.9.599 | ciscoLwappDot11ClientMIB | 4 | 439 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.600 | ciscoGslbHealthMonMIB | 3 | 90 | The MIB defines objects related to global keepalive properties in GSLB devices. It contains the tables for keep alive configurat… |
| 1.3.6.1.4.1.9.9.601 | ciscoResilientEthernetProtocolMIB | 3 | 77 | This MIB module defines objects required for managing Resilient Ethernet Protocol (REP). Resilient Ethernet Protocol (REP) is a C… |
| 1.3.6.1.4.1.9.9.602 | ciscoPacketCaptureMIB | 3 | 103 | The MIB module for the management of packet capture feature. |
| 1.3.6.1.4.1.9.9.603 | ciscoThreatMitigationServiceMIB | 3 | 68 | This MIB provides management information about the Threat Mitigation Service(TMS) entity named 'Consumer'. TMS is part of Cisco's… |
| 1.3.6.1.4.1.9.9.604 | cdot1CfmMIB | 3 | 166 | Connectivity Fault Management module for managing IEEE 802.1ag |
| 1.3.6.1.4.1.9.9.606 | ciscoLwappMeshLinkTestMIB | 3 | 46 | ciscoLwappMeshLinkTestMIB MODULE-IDENTITY LAST-UPDATED "200702050000Z" ORGANIZATION "Cisco Systems Inc." CONTACT-INFO "Cisco Sy… |
| 1.3.6.1.4.1.9.9.607 | ciscoDot11HtPhyMIB | 3 | 71 | This MIB is intended to be implemented on Cisco's WLAN devices that provide the wired uplink to wireless clients through the high… |
| 1.3.6.1.4.1.9.9.610 | ciscoLwappRogueMIB | 4 | 134 | This MIB is intended to be implemented on all those devices operating as Central Controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.611 | ciscoLwappDot11ClientCCXTextualConventions | 0 | 0 | This module defines the textual conventions used throughout the Cisco enterprise MIBs designed for implementation on Central Cont… |
| 1.3.6.1.4.1.9.9.612 | ciscoLwappDot11MIB | 3 | 156 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.613 | ciscoEvcMIB | 3 | 156 | Metro Ethernet services can support a wide range of applications and subscriber needs easily, efficiently and cost-effectively. … |
| 1.3.6.1.4.1.9.9.614 | ciscoLwappDot11LdapMIB | 3 | 33 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.615 | ciscoLwappRrmMIB | 3 | 175 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |