Reference record for OID 1.3.6.1.4.1.9.9.600

Parent
1.3.6.1.4.1.9.9 (ciscoMgmt)
Node code
600
Node name
ciscoGslbHealthMonMIB
Numeric OID
1.3.6.1.4.1.9.9.600
URN notation
urn:oid:1.3.6.1.4.1.9.9.600
Type
OBJECT IDENTIFIER
ASN.1 notation

{1 3 6 1 4 1 9 9 600}

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

Descriptions

Descriptions may differ between sources. The primary description is shown first.

Primary description: Circitor

The MIB defines objects related to global keepalive
properties in GSLB devices. It contains the tables
for keep alive configuration and statistics. It also
defines related notifications.

Acronyms and their description:

Keepalive : Keepalive is a method by which the GSLB
device periodically checks to see if a
resource associated with an answer is
still active. The action of checking is
known as a keepalive probe.

Shared
-keepalive : The GSLB device supports the use of shared
keepalives to minimize traffic between the
GSLB device and the SLBs(Server Load
Balancing) that it is monitoring.
A shared keepalive identifies a common IP
address or resource that provides status
for multiple answers. Shared keepalives
periodically provide state information
(online, offline) of the resources
to the GSLB device.

VIP : Virtual IP Addresses are used by SLBs to
represent content hosted on one or more
servers under their control. The use of
VIPs is to route content to the proper
requesting host without exposing the
device's internal IP address.

CAPP : Content Application Peering Protocol(CAPP) is
a protocol used for intercommunication between
content switching devices.

Answer : Refers to resources to which the GSLB device
resolves DNS requests that it receives.

There are three possible types of answers:

Virtual IP (VIP) : Addresses associated with
a SLB, a web server, a
cache, etc.

Name Server (NS) : Configured DNS name server
on the network that can
answer queries that the GSLB
device can not resolve.

Content Routing : A device which uses a
Agent (CRA) resolution process called
DNS race to send identical
and simultaneous responses
back to client D-proxy
for proximity determination.
HTTPHEAD : The HTTP HEAD keepalive type
sends a TCP format HTTP HEAD
request to a web server at
an address you specify,
returning the online status
of the device (in the form
of a 200 response) as well
as information on the web
page status and content
size.

Parsed from file CISCO-GSLB-HEALTH-MON-MIB.mib
Module: CISCO-GSLB-HEALTH-MON-MIB

Source file: Download CISCO-GSLB-HEALTH-MON-MIB.mib

Publisher path: Mibs; 41,009 bytes

Alternative description: Cisco

The MIB defines objects related to global keepalive
properties in GSLB devices. It contains the tables
for keep alive configuration and statistics. It also
defines related notifications.

Acronyms and their description:

Keepalive : Keepalive is a method by which the GSLB
device periodically checks to see if a
resource associated with an answer is
still active. The action of checking is
known as a keepalive probe.

Shared
-keepalive : The GSLB device supports the use of shared
keepalives to minimize traffic between the
GSLB device and the SLBs(Server Load
Balancing) that it is monitoring.
A shared keepalive identifies a common IP
address or resource that provides status
for multiple answers. Shared keepalives
periodically provide state information
(online, offline) of the resources
to the GSLB device.

VIP : Virtual IP Addresses are used by SLBs to
represent content hosted on one or more
servers under their control. The use of
VIPs is to route content to the proper
requesting host without exposing the
device's internal IP address.

CAPP : Content Application Peering Protocol(CAPP) is
a protocol used for intercommunication between
content switching devices.

Answer : Refers to resources to which the GSLB device
resolves DNS requests that it receives.

There are three possible types of answers:

Virtual IP (VIP) : Addresses associated with
a SLB, a web server, a
cache, etc.

Name Server (NS) : Configured DNS name server
on the network that can
answer queries that the GSLB
device can not resolve.

Content Routing : A device which uses a
Agent (CRA) resolution process called
DNS race to send identical
and simultaneous responses
back to client D-proxy
for proximity determination.
HTTPHEAD : The HTTP HEAD keepalive type
sends a TCP format HTTP HEAD
request to a web server at
an address you specify,
returning the online status
of the device (in the form
of a 200 response) as well
as information on the web
page status and content
size.

Source file: Download CISCO-GSLB-HEALTH-MON-MIB.my · Publisher's file

Copy from Netdisco; File: cisco/CISCO-GSLB-HEALTH-MON-MIB.my; 39,901 bytes

Vendor MIB copy from the Netdisco archive.

Related source files and packages:

Source file: Download CISCO-GSLB-HEALTH-MON-MIB · Publisher's file

Copy from Observium Community; File: cisco/CISCO-GSLB-HEALTH-MON-MIB; 39,901 bytes

Vendor MIB copy from the Observium Community archive. Cisco support.

Related source files and packages:

Source file: Download CISCO-GSLB-HEALTH-MON-MIB.my · Publisher's file

Publisher path: cisco/cisco-mibs/main/v2/CISCO-GSLB-HEALTH-MON-MIB.my; 39,901 bytes

Alternative description: MIBdepot

The MIB defines objects related to global keepalive
properties in GSLB devices. It contains the tables
for keep alive configuration and statistics. It also
defines related notifications.

Acronyms and their description:

Keepalive : Keepalive is a method by which the GSLB
device periodically checks to see if a
resource associated with an answer is
still active. The action of checking is
known as a keepalive probe.

Shared
-keepalive : The GSLB device supports the use of shared
keepalives to minimize traffic between the
GSLB device and the SLBs(Server Load
Balancing) that it is monitoring.
A shared keepalive identifies a common IP
address or resource that provides status
for multiple answers. Shared keepalives
periodically provide state information
(online, offline) of the resources
to the GSLB device.

VIP : Virtual IP Addresses are used by SLBs to
represent content hosted on one or more
servers under their control. The use of
VIPs is to route content to the proper
requesting host without exposing the
device's internal IP address.

CAPP : Content Application Peering Protocol(CAPP) is
a protocol used for intercommunication between
content switching devices.

Answer : Refers to resources to which the GSLB device
resolves DNS requests that it receives.

There are three possible types of answers:

Virtual IP (VIP) : Addresses associated with
a SLB, a web server, a
cache, etc.

Name Server (NS) : Configured DNS name server
on the network that can
answer queries that the GSLB
device can not resolve.

Content Routing : A device which uses a
Agent (CRA) resolution process called
DNS race to send identical
and simultaneous responses
back to client D-proxy
for proximity determination.
HTTPHEAD : The HTTP HEAD keepalive type
sends a TCP format HTTP HEAD
request to a web server at
an address you specify,
returning the online status
of the device (in the form
of a 200 response) as well
as information on the web
page status and content
size.

Source file: Download CISCO-GSLB-HEALTH-MON-MIB.my.txt

File: cisco/CISCO-GSLB-HEALTH-MON-MIB.my.txt; 41,009 bytes

Information from Circitor

ciscoGslbHealthMonMIB MODULE-IDENTITY
    LAST-UPDATED    "200704090000Z"
    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-slb@cisco.com"
    DESCRIPTION
        "The MIB defines objects related to global keepalive
        properties in GSLB devices.  It contains the tables
        for keep alive configuration and statistics.  It also
        defines related notifications.

        Acronyms and their description:

        Keepalive    : Keepalive is a method by which the GSLB
                       device periodically checks to see if a
                       resource associated with an answer is
                       still active.  The action of checking is
                       known as a keepalive probe.

        Shared
        -keepalive   : The GSLB device supports the use of shared
                       keepalives to minimize traffic between the
                       GSLB device and the SLBs(Server Load
                       Balancing) that it is monitoring.
                       A shared keepalive identifies a common IP
                       address or resource that provides status
                       for multiple answers.  Shared keepalives
                       periodically provide state information
                       (online, offline) of the resources
                       to the GSLB device.

        VIP          : Virtual IP Addresses are used by SLBs to
                       represent content hosted on one or more
                       servers under their control.  The use of
                       VIPs is to route content to the proper
                       requesting host without exposing the
                       device's internal IP address.

        CAPP         : Content Application Peering Protocol(CAPP) is
                       a protocol used for intercommunication between
                       content switching devices.

        Answer       : Refers to resources to which the GSLB device
                       resolves DNS requests that it receives.

                       There are three possible types of answers:

                       Virtual IP (VIP) : Addresses associated with
                                          a SLB, a web server, a
                                          cache, etc.

                       Name Server (NS) : Configured DNS name server
                                          on the network that can
                                          answer queries that the GSLB
                                          device can not resolve.

                       Content Routing  : A device which uses a
                       Agent (CRA)        resolution process called
                                          DNS race to send identical
                                          and simultaneous responses
                                          back to client D-proxy
                                          for proximity determination.
                       HTTPHEAD         : The HTTP HEAD keepalive type
                                          sends a TCP format HTTP HEAD
                                          request to a web server at
                                          an address you specify,
                                          returning the online status
                                          of the device (in the form 
                                          of a 200 response) as well
                                          as information on the web
                                          page status and content
                                          size."
    REVISION        "200704090000Z"
    DESCRIPTION
        "-Added the following objects to ciscoGslbGeneralConfigGroup:
        cghMonDroppedKalNotifs
        cghMonKalTrapRateLimit

        -Added a new group ciscoGslbGeneralConfigRateLimitGroup."
    REVISION        "200612040000Z"
    DESCRIPTION
        "Initial version of this MIB module."
    ::= { ciscoMgmt 600 }

Information from Cisco SMIv1

Source file: Download CISCO-GSLB-HEALTH-MON-MIB-V1SMI.my · Publisher's file

Publisher path: cisco/cisco-mibs/main/v1/CISCO-GSLB-HEALTH-MON-MIB-V1SMI.my; 38,600 bytes

Source file: Download CISCO-GSLB-HEALTH-MON-MIB-V1SMI.my.txt

File: cisco/CISCO-GSLB-HEALTH-MON-MIB-V1SMI.my.txt; 39,805 bytes

ciscoGslbHealthMonMIB OBJECT IDENTIFIER ::= { ciscoMgmt 600 }

Information from OID Repository

Vendor: Cisco
Module: CISCO-GSLB-HEALTH-MON-MIB

[Automatically extracted from oidview.com]

Information from MIBdepot

ciscoGslbHealthMonMIB MODULE-IDENTITY
    LAST-UPDATED    "200704090000Z"
    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-slb@cisco.com"
    DESCRIPTION
        "The MIB defines objects related to global keepalive
        properties in GSLB devices.  It contains the tables
        for keep alive configuration and statistics.  It also
        defines related notifications.

        Acronyms and their description:

        Keepalive    : Keepalive is a method by which the GSLB
                       device periodically checks to see if a
                       resource associated with an answer is
                       still active.  The action of checking is
                       known as a keepalive probe.

        Shared
        -keepalive   : The GSLB device supports the use of shared
                       keepalives to minimize traffic between the
                       GSLB device and the SLBs(Server Load
                       Balancing) that it is monitoring.
                       A shared keepalive identifies a common IP
                       address or resource that provides status
                       for multiple answers.  Shared keepalives
                       periodically provide state information
                       (online, offline) of the resources
                       to the GSLB device.

        VIP          : Virtual IP Addresses are used by SLBs to
                       represent content hosted on one or more
                       servers under their control.  The use of
                       VIPs is to route content to the proper
                       requesting host without exposing the
                       device's internal IP address.

        CAPP         : Content Application Peering Protocol(CAPP) is
                       a protocol used for intercommunication between
                       content switching devices.

        Answer       : Refers to resources to which the GSLB device
                       resolves DNS requests that it receives.

                       There are three possible types of answers:

                       Virtual IP (VIP) : Addresses associated with
                                          a SLB, a web server, a
                                          cache, etc.

                       Name Server (NS) : Configured DNS name server
                                          on the network that can
                                          answer queries that the GSLB
                                          device can not resolve.

                       Content Routing  : A device which uses a
                       Agent (CRA)        resolution process called
                                          DNS race to send identical
                                          and simultaneous responses
                                          back to client D-proxy
                                          for proximity determination.
                       HTTPHEAD         : The HTTP HEAD keepalive type
                                          sends a TCP format HTTP HEAD
                                          request to a web server at
                                          an address you specify,
                                          returning the online status
                                          of the device (in the form 
                                          of a 200 response) as well
                                          as information on the web
                                          page status and content
                                          size."
    REVISION        "200704090000Z"
    DESCRIPTION
        "-Added the following objects to ciscoGslbGeneralConfigGroup:
        cghMonDroppedKalNotifs
        cghMonKalTrapRateLimit

        -Added a new group ciscoGslbGeneralConfigRateLimitGroup."
    REVISION        "200612040000Z"
    DESCRIPTION
        "Initial version of this MIB module."
    ::= { ciscoMgmt 600 }

Information from Cisco

ciscoGslbHealthMonMIB MODULE-IDENTITY
    LAST-UPDATED    "200704090000Z"
    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-slb@cisco.com"
    DESCRIPTION
        "The MIB defines objects related to global keepalive
        properties in GSLB devices.  It contains the tables
        for keep alive configuration and statistics.  It also
        defines related notifications.

        Acronyms and their description:

        Keepalive    : Keepalive is a method by which the GSLB
                       device periodically checks to see if a
                       resource associated with an answer is
                       still active.  The action of checking is
                       known as a keepalive probe.

        Shared
        -keepalive   : The GSLB device supports the use of shared
                       keepalives to minimize traffic between the
                       GSLB device and the SLBs(Server Load
                       Balancing) that it is monitoring.
                       A shared keepalive identifies a common IP
                       address or resource that provides status
                       for multiple answers.  Shared keepalives
                       periodically provide state information
                       (online, offline) of the resources
                       to the GSLB device.

        VIP          : Virtual IP Addresses are used by SLBs to
                       represent content hosted on one or more
                       servers under their control.  The use of
                       VIPs is to route content to the proper
                       requesting host without exposing the
                       device's internal IP address.

        CAPP         : Content Application Peering Protocol(CAPP) is
                       a protocol used for intercommunication between
                       content switching devices.

        Answer       : Refers to resources to which the GSLB device
                       resolves DNS requests that it receives.

                       There are three possible types of answers:

                       Virtual IP (VIP) : Addresses associated with
                                          a SLB, a web server, a
                                          cache, etc.

                       Name Server (NS) : Configured DNS name server
                                          on the network that can
                                          answer queries that the GSLB
                                          device can not resolve.

                       Content Routing  : A device which uses a
                       Agent (CRA)        resolution process called
                                          DNS race to send identical
                                          and simultaneous responses
                                          back to client D-proxy
                                          for proximity determination.
                       HTTPHEAD         : The HTTP HEAD keepalive type
                                          sends a TCP format HTTP HEAD
                                          request to a web server at
                                          an address you specify,
                                          returning the online status
                                          of the device (in the form 
                                          of a 200 response) as well
                                          as information on the web
                                          page status and content
                                          size."
    REVISION        "200704090000Z"
    DESCRIPTION
        "-Added the following objects to ciscoGslbGeneralConfigGroup:
        cghMonDroppedKalNotifs
        cghMonKalTrapRateLimit

        -Added a new group ciscoGslbGeneralConfigRateLimitGroup."
    REVISION        "200612040000Z"
    DESCRIPTION
        "Initial version of this MIB module."
    ::= { ciscoMgmt 600 }

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.600.0 ciscoGslbHealthMonMIBNotifs11
1.3.6.1.4.1.9.9.600.1 ciscoGslbHealthMonMIBObjects475
1.3.6.1.4.1.9.9.600.2 ciscoGslbHealthMonMIBConform211

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.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…
1.3.6.1.4.1.9.9.615 ciscoLwappRrmMIB3175 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…