OID reference

ciscoImageLicenseMgmtMIB

1.3.6.1.4.1.9.9.640

Description

The MIB module for managing the running image level of a Cisco device. Cisco's licensing mechanism provides flexibility to run a device on a chosen image level. This mechanism is referred to as image level licensing. Image level licensing leverages the universal image based licensing solution. The image level licensin…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.9.9 (ciscoMgmt)
Node code
640
Node name
ciscoImageLicenseMgmtMIB
Numeric OID
1.3.6.1.4.1.9.9.640
URN notation
urn:oid:1.3.6.1.4.1.9.9.640
Type
OBJECT IDENTIFIER
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 9 9 640}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoImageLicenseMgmtMIB(640)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) me1200(9) ciscoMgmt(9) ciscoImageLicenseMgmtMIB(640)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoImageLicenseMgmtMIB(640)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) me1200(9) ciscoMgmt(9) ciscoImageLicenseMgmtMIB(640)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) ciscoImageLicenseMgmtMIB(640)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) me1200(9) ciscoMgmt(9) ciscoImageLicenseMgmtMIB(640)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) ciscoImageLicenseMgmtMIB(640)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) me1200(9) ciscoMgmt(9) ciscoImageLicenseMgmtMIB(640)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoImageLicenseMgmtMIB(640)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) me1200(9) ciscoMgmt(9) ciscoImageLicenseMgmtMIB(640)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoImageLicenseMgmtMIB(640)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) me1200(9) ciscoMgmt(9) ciscoImageLicenseMgmtMIB(640)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) ciscoImageLicenseMgmtMIB(640)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) me1200(9) ciscoMgmt(9) ciscoImageLicenseMgmtMIB(640)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) ciscoImageLicenseMgmtMIB(640)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) me1200(9) ciscoMgmt(9) ciscoImageLicenseMgmtMIB(640)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/9/9/640
  • /ISO/Identified-Organization/6/1/4/1/9/9/640
  • /ISO/3/6/1/4/1/9/9/640
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoImageLicenseMgmtMIB
  • /iso/identified-organization/dod/internet/private/enterprise/me1200/ciscoMgmt/ciscoImageLicenseMgmtMIB
  • /iso/identified-organization/dod/internet/private/enterprise/Cisco/ciscoMgmt/ciscoImageLicenseMgmtMIB
  • /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoImageLicenseMgmtMIB
  • /iso/identified-organization/dod/internet/private/enterprises/me1200/ciscoMgmt/ciscoImageLicenseMgmtMIB
  • /iso/identified-organization/dod/internet/private/enterprises/Cisco/ciscoMgmt/ciscoImageLicenseMgmtMIB
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/cisco/ciscoMgmt/ciscoImageLicenseMgmtMIB
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/me1200/ciscoMgmt/ciscoImageLicenseMgmtMIB
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/Cisco/ciscoMgmt/ciscoImageLicenseMgmtMIB
  • /iso/identified-organization/dod/internet/private/vendor-objects/cisco/ciscoMgmt/ciscoImageLicenseMgmtMIB
  • /iso/identified-organization/dod/internet/private/vendor-objects/me1200/ciscoMgmt/ciscoImageLicenseMgmtMIB
  • /iso/identified-organization/dod/internet/private/vendor-objects/Cisco/ciscoMgmt/ciscoImageLicenseMgmtMIB
  • /iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoImageLicenseMgmtMIB
  • /iso/org/dod/internet/private/enterprise/me1200/ciscoMgmt/ciscoImageLicenseMgmtMIB
  • /iso/org/dod/internet/private/enterprise/Cisco/ciscoMgmt/ciscoImageLicenseMgmtMIB
  • /iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoImageLicenseMgmtMIB
  • Additional combinations skipped.

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

The MIB module for managing the running image level
of a Cisco device. Cisco's licensing mechanism provides
flexibility to run a device on a chosen image level.
This mechanism is referred to as image level licensing.
Image level licensing leverages the universal image
based licensing solution.

The image level licensing mechanism works as follows -

A universal image that contains all levels of software
packages is loaded on to the device. At boot time, the
device determines the highest level of license and brings
up the appropriate software features or subsystems.
The user can configure the image level with which the
device has to boot. The system will verify whether the
appropriate license is available for the configured image
level. The image level for the next boot will be determined
based on the availability of the license. The following
scenarios explains some use-cases of image level licensing:

Scenario 1:
- Customer selects advsecurityk9 based image.
- Manufacturing installs advsecurity license on the device.
- This device will run all features that are part of the
base advsecurity license.
- Customer upgrades to advipservicesk9 license.
- The next boot level is set to advipservicesk9.
- The device will run advsecurityk9 feature until the
next reboot. After reboot the device will run
advipservicesk9 features.

Scenario 2:
- Customer selects advipservicesk9 based image.
- Manufacturing installs advipservices and advsecurity
license on the device.
- This device will run all features that are part of the
base advipservices license.
- No upgrades available for advipservices license.

The user has to accept the End User License Agreement(EULA)
before using this MIB to configure the image level.

This MIB should be used in conjuntion with
CISCO-LICENSE-MGMT-MIB module to achieve the image level
licensing functionality.

This MIB module defines objects which provides the different
image levels supported by the device and the license required
to enable a particular image level. It also defines objects
to let the user configure the required image level. The MIB
module contains notification which will be triggered when
the user changes the image level for next boot.

The CISCO-LICENSE-MGMT-MIB module should be used to export
the EULA and to configure the required license.

This MIB module is defined generically so it can be used for
both stand-alone as well as stackable devices. The
entPhysicalIndex imported from ENTITY-MIB is used to identify
the device uniquely.
Sources for this description

Circitor

Parsed from CISCO-IMAGE-LICENSE-MGMT-MIB.mib · CISCO-IMAGE-LICENSE-MGMT-MIB

Source file: Download CISCO-IMAGE-LICENSE-MGMT-MIB.mib

Historical records

Additional source information

Information from Circitor
ciscoImageLicenseMgmtMIB MODULE-IDENTITY
    LAST-UPDATED    "200710160000Z"
    ORGANIZATION    "Cisco Systems Inc."
    CONTACT-INFO
            "Cisco Systems
            Customer Service
            Postal: 170 W Tasman Drive
            San Jose, CA  95134
            USA
            Tel: +1 800 553 -NETS
            E-mail: cs-snmp@cisco.com"
    DESCRIPTION
        "The MIB module for managing the running image level
        of a Cisco device. Cisco's licensing mechanism provides
        flexibility to run a device on a chosen image level.
        This mechanism is referred to as image level licensing.
        Image level licensing leverages the universal image
        based licensing solution.

        The image level licensing mechanism works as follows - 

        A universal image that contains all levels of software
        packages is loaded on to the device. At boot time, the
        device determines the highest level of license and brings
        up the appropriate software features or subsystems.
        The user can configure the image level with which the
        device has to boot. The system will verify whether the
        appropriate license is available for the configured image
        level. The image level for the next boot will be determined
        based on the availability of the license. The following
        scenarios explains some use-cases of image level licensing:

        Scenario 1:
        - Customer selects advsecurityk9 based image.
        - Manufacturing installs advsecurity license on the device.
        - This device will run all features that are part of the
        base advsecurity license.
        - Customer upgrades to advipservicesk9 license.
        - The next boot level is set to advipservicesk9.
        - The device will run advsecurityk9 feature until the
        next reboot. After reboot the device will run 
        advipservicesk9 features.

        Scenario 2:
        - Customer selects advipservicesk9 based image.
        - Manufacturing installs advipservices and advsecurity
        license on the device.
        - This device will run all features that are part of the
        base advipservices license.
        - No upgrades available for advipservices license.

        The user has to accept the End User License Agreement(EULA)
        before using this MIB to configure the image level. 

        This MIB should be used in conjuntion with
        CISCO-LICENSE-MGMT-MIB module to achieve the image level
        licensing functionality.

        This MIB module defines objects which provides the different
        image levels supported by the device and the license required
        to enable a particular image level. It also defines objects
        to let the user configure the required image level. The MIB 
        module contains notification which will be triggered when
        the user changes the image level for next boot. 

        The CISCO-LICENSE-MGMT-MIB module should be used to export
        the EULA and to configure the required license.

        This MIB module is defined generically so it can be used for
        both stand-alone as well as stackable devices. The
        entPhysicalIndex imported from ENTITY-MIB is used to identify
        the device uniquely."
    REVISION        "200710160000Z"
    DESCRIPTION
        "Initial version of this MIB module."
    ::= { ciscoMgmt 640 }
Information from Cisco SMIv1

Source file: Download CISCO-IMAGE-LICENSE-MGMT-MIB-V1SMI.my · Publisher's file

Source file: Download CISCO-IMAGE-LICENSE-MGMT-MIB-V1SMI.my.txt

ciscoImageLicenseMgmtMIB OBJECT IDENTIFIER ::= { ciscoMgmt 640 }
Information from OID Repository
Vendor: Cisco
Module: CISCO-IMAGE-LICENSE-MGMT-MIB

[Automatically extracted from oidview.com]
Information from MIBdepot
ciscoImageLicenseMgmtMIB MODULE-IDENTITY
    LAST-UPDATED    "200710160000Z"
    ORGANIZATION    "Cisco Systems Inc."
    CONTACT-INFO
            "Cisco Systems
            Customer Service
            Postal: 170 W Tasman Drive
            San Jose, CA  95134
            USA
            Tel: +1 800 553 -NETS
            E-mail: cs-snmp@cisco.com"
    DESCRIPTION
        "The MIB module for managing the running image level
        of a Cisco device. Cisco's licensing mechanism provides
        flexibility to run a device on a chosen image level.
        This mechanism is referred to as image level licensing.
        Image level licensing leverages the universal image
        based licensing solution.

        The image level licensing mechanism works as follows - 

        A universal image that contains all levels of software
        packages is loaded on to the device. At boot time, the
        device determines the highest level of license and brings
        up the appropriate software features or subsystems.
        The user can configure the image level with which the
        device has to boot. The system will verify whether the
        appropriate license is available for the configured image
        level. The image level for the next boot will be determined
        based on the availability of the license. The following
        scenarios explains some use-cases of image level licensing:

        Scenario 1:
        - Customer selects advsecurityk9 based image.
        - Manufacturing installs advsecurity license on the device.
        - This device will run all features that are part of the
        base advsecurity license.
        - Customer upgrades to advipservicesk9 license.
        - The next boot level is set to advipservicesk9.
        - The device will run advsecurityk9 feature until the
        next reboot. After reboot the device will run 
        advipservicesk9 features.

        Scenario 2:
        - Customer selects advipservicesk9 based image.
        - Manufacturing installs advipservices and advsecurity
        license on the device.
        - This device will run all features that are part of the
        base advipservices license.
        - No upgrades available for advipservices license.

        The user has to accept the End User License Agreement(EULA)
        before using this MIB to configure the image level. 

        This MIB should be used in conjuntion with
        CISCO-LICENSE-MGMT-MIB module to achieve the image level
        licensing functionality.

        This MIB module defines objects which provides the different
        image levels supported by the device and the license required
        to enable a particular image level. It also defines objects
        to let the user configure the required image level. The MIB 
        module contains notification which will be triggered when
        the user changes the image level for next boot. 

        The CISCO-LICENSE-MGMT-MIB module should be used to export
        the EULA and to configure the required license.

        This MIB module is defined generically so it can be used for
        both stand-alone as well as stackable devices. The
        entPhysicalIndex imported from ENTITY-MIB is used to identify
        the device uniquely."
    REVISION        "200710160000Z"
    DESCRIPTION
        "Initial version of this MIB module."
    ::= { ciscoMgmt 640 }
Information from Cisco
ciscoImageLicenseMgmtMIB MODULE-IDENTITY
    LAST-UPDATED    "200710160000Z"
    ORGANIZATION    "Cisco Systems Inc."
    CONTACT-INFO
            "Cisco Systems
            Customer Service
            Postal: 170 W Tasman Drive
            San Jose, CA  95134
            USA
            Tel: +1 800 553 -NETS
            E-mail: cs-snmp@cisco.com"
    DESCRIPTION
        "The MIB module for managing the running image level
        of a Cisco device. Cisco's licensing mechanism provides
        flexibility to run a device on a chosen image level.
        This mechanism is referred to as image level licensing.
        Image level licensing leverages the universal image
        based licensing solution.

        The image level licensing mechanism works as follows - 

        A universal image that contains all levels of software
        packages is loaded on to the device. At boot time, the
        device determines the highest level of license and brings
        up the appropriate software features or subsystems.
        The user can configure the image level with which the
        device has to boot. The system will verify whether the
        appropriate license is available for the configured image
        level. The image level for the next boot will be determined
        based on the availability of the license. The following
        scenarios explains some use-cases of image level licensing:

        Scenario 1:
        - Customer selects advsecurityk9 based image.
        - Manufacturing installs advsecurity license on the device.
        - This device will run all features that are part of the
        base advsecurity license.
        - Customer upgrades to advipservicesk9 license.
        - The next boot level is set to advipservicesk9.
        - The device will run advsecurityk9 feature until the
        next reboot. After reboot the device will run 
        advipservicesk9 features.

        Scenario 2:
        - Customer selects advipservicesk9 based image.
        - Manufacturing installs advipservices and advsecurity
        license on the device.
        - This device will run all features that are part of the
        base advipservices license.
        - No upgrades available for advipservices license.

        The user has to accept the End User License Agreement(EULA)
        before using this MIB to configure the image level. 

        This MIB should be used in conjuntion with
        CISCO-LICENSE-MGMT-MIB module to achieve the image level
        licensing functionality.

        This MIB module defines objects which provides the different
        image levels supported by the device and the license required
        to enable a particular image level. It also defines objects
        to let the user configure the required image level. The MIB 
        module contains notification which will be triggered when
        the user changes the image level for next boot. 

        The CISCO-LICENSE-MGMT-MIB module should be used to export
        the EULA and to configure the required license.

        This MIB module is defined generically so it can be used for
        both stand-alone as well as stackable devices. The
        entPhysicalIndex imported from ENTITY-MIB is used to identify
        the device uniquely."
    REVISION        "200710160000Z"
    DESCRIPTION
        "Initial version of this MIB module."
    ::= { ciscoMgmt 640 }

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)

Greg Satz

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)

Cisco Systems, Inc.

Direct children (3)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.9.9.640.0 ciscoImageLicenseMgmtMIBNotifs11
1.3.6.1.4.1.9.9.640.1 ciscoImageLicenseMgmtMIBObjects421
1.3.6.1.4.1.9.9.640.2 ciscoImageLicenseMgmtMIBConform26

Siblings (706)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.9.9.513 ciscoLwappApMIB51009 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.514 ciscoLwappTextualConventions00 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 ciscoLwappWebAuthMIB4133 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 ciscoLwappLinkTestMIB357 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 ciscoLwappReapMIB3342 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 ciscoLwappMfpMIB468 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 ciscoLwappIdsMIB328 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 ciscoLwappCcxRmMIB345 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 ciscoLwappWlanSecurityMIB377 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 ciscoLwappDot11ClientCalibMIB355 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 ciscoLwappClRoamMIB363 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 ciscoLwappQosMIB3491 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 ciscoLwappTsmMIB357 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 ciscoItpMsuRatesMIB361 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 ciscoNacTcMIB00 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 ciscoNATExtMIB313 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 ciscoCbpTargetMIB325 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 ciscoLicenseMgmtMIB3131 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 ciscoErrDisableMIB345 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 ciscoRttMonIPExtMIB257 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 ciscoQosTcMIB00 This module defines the textual conventions used within
Cisco Qos MIBs.
1.3.6.1.4.1.9.9.576 ciscoLwappMobilityMIB3106 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 ciscoLwappAclMIB347 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 ciscoRoutePoliciesMIB35 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 ciscoSwitchQosMIB3295 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 ciscoGslbTcMIB00 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 ciscoEntityDiagTcMIB00 This module defines the textual conventions used within
Cisco Entity Diag MIB.
1.3.6.1.4.1.9.9.585 ciscoIpSlaEthernetMIB3245 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 ciscoNotificationControlMIB228 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 ciscoGslbSystemMIB3103 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 ciscoCvpMIB3255 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 ciscoPrefPathMIB356 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 ciscoFcSdvMIB328 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 ciscoApplicationAccelerationMIB337 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 ciscoGslbDnsMIB3165 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 ciscoContentServicesMIB3349 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 ciscoLwappAAAMIB3150 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 ciscoLwappDot11ClientMIB4523 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 ciscoGslbHealthMonMIB390 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 ciscoResilientEthernetProtocolMIB377 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 ciscoPacketCaptureMIB3103 The MIB module for the management of packet capture
feature.
1.3.6.1.4.1.9.9.603 ciscoThreatMitigationServiceMIB368 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 cdot1CfmMIB3166 Connectivity Fault Management module for managing IEEE 802.1ag
1.3.6.1.4.1.9.9.606 ciscoLwappMeshLinkTestMIB346 ciscoLwappMeshLinkTestMIB MODULE-IDENTITY
LAST-UPDATED "200702050000Z"
ORGANIZATION "Cisco Systems Inc."
CONTACT-INFO
"Cisco Sy…
1.3.6.1.4.1.9.9.607 ciscoDot11HtPhyMIB371 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 ciscoLwappRogueMIB4134 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 ciscoLwappDot11ClientCCXTextualConventions00 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 ciscoLwappDot11MIB3158 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 ciscoEvcMIB3156 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 ciscoLwappDot11LdapMIB333 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…