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.128 ciscoVlanIfTableRelationshipMIB112 ciscoVlanIftableRelationshipMIB
1.3.6.1.4.1.9.9.129 ciscoAtmVirtualIfMIB2139 The MIB module to manage ATM Virtual interface objects.
ATM virtual interfaces are configured on a physical line.
1.3.6.1.4.1.9.9.130 ciscoAdslDmtLineMIB372 This MIB module serves as an enterprise-specific extension of
the ADSL-LINE-MIB. The structure of this MIB module shadows
the st…
1.3.6.1.4.1.9.9.131 ciscoSystemMIB357 The systemGroup (see RFC 1907) provides a standard set of
basic system information. This MIB module contains
Cisco-defined exten…
1.3.6.1.4.1.9.9.132 ciscoDs3MIB2140 The MIB module to describe DS3 line objects. This is
an extension to the standard DS3 MIB(RFC 2496).
1.3.6.1.4.1.9.9.133 ciscoAtmCellLayerMIB1138 The MIB module to describe ATM cell layer objects and statistics
of a physical line.
1.3.6.1.4.1.9.9.134 ciscoClusterMIB349 The MIB module for the management of a group of
devices called a 'cluster'. A cluster comprises:

1. A command switch, which is a…
1.3.6.1.4.1.9.9.135 ciscoWirelessP2pBpiMIB366 This is the MIB Module for the Baseline Privacy Interface (BPI)
at Point to Point Wireless Radio Card.

This is a specialization o…
1.3.6.1.4.1.9.9.136 ciscoWirelessIfMIB3325 This is the MIB Module for the Cisco Wireless Radio
Point to Point interface specification.

I) Relationship of the Cisco Wireless…
1.3.6.1.4.1.9.9.137 ciscoWirelessTextualConventions00 This module defines textual conventions used
in Cisco Wireless MIBs.
1.3.6.1.4.1.9.9.138 ciscoEntityAlarmMIB366 This MIB module defines the managed objects that support the
monitoring of alarms generated by physical entities contained
by the…
1.3.6.1.4.1.9.9.139 ciscoEntityProvMIB313 This MIB module defines the objects that support provisioning
of 'container' class physical entities. Provisioning sets up
a 'co…
1.3.6.1.4.1.9.9.140 ciscoCopsClientMIB343 This MIB module is for configuration & statistic query
of Common Open Policy Service(COPS) client feature on the Cisco
device. C…
1.3.6.1.4.1.9.9.141 ciscoVSIControllerMIB221 This MIB module is used for configuring ATM Capable Switch
to be aware of VSI Controller information.

Terminolgies used:

VSI …
1.3.6.1.4.1.9.9.144 ciscoTransactionConnectionMIB266 The MIB module for retrieving Cisco Transaction
Connection configuration and status. Cisco Transaction
Connection routes transac…
1.3.6.1.4.1.9.9.145 ciscoWanModuleMIB332 The MIB to configure Connection Specific parameters and
statistics related information in a Service Module.
The Service Module(SM…
1.3.6.1.4.1.9.9.146 ciscoCallApplicationMIB2548 This MIB allows management of call applications on a
network device. A 'call application' is a software module
that processes cal…
1.3.6.1.4.1.9.9.147 ciscoFirewallMIB377 MIB module for monitoring Cisco Firewalls.
1.3.6.1.4.1.9.9.148 ciscoBgpPolAcctMIB215 BGP policy based accounting information
1.3.6.1.4.1.9.9.149 ciscoAdslLineCapMIB346 This MIB module serves as an enterprise-specific extension of
the ADSL-LINE-MIB. The structure of this MIB module shadows
the st…
1.3.6.1.4.1.9.9.150 ciscoAAASessionMIB331 This MIB module provides data for accounting sessions
based on Authentication, Authorization, Accounting
(AAA) protocols.


Referenc…
1.3.6.1.4.1.9.9.151 ciscoL2L3IfConfigMIB211 Interface switchport mode configuration management MIB.

This MIB is used to monitor and control
configuration of interface switch…
1.3.6.1.4.1.9.9.152 ciscoSipUaMIB4557 Cisco User Agent Session Initiation Protocol (SIP)
MIB module. SIP is an application-layer signalling
protocol for creating, mod…
1.3.6.1.4.1.9.9.154 ciscoIdslLineMIB3148 This MIB module describes IDSL (ISDN Digital Line Subscriber)
line interfaces. The structure of this module resembles that
of th…
1.3.6.1.4.1.9.9.155 ciscoSdslLineMIB3170 This MIB module describes all variations of the symmetric
DSL line interfaces. The structure of this module resembles
and mainta…
1.3.6.1.4.1.9.9.156 ciscoCcmMIB3487 The MIB Module for the management of a Cisco Unified
Communications Manager (CUCM) application running with a Cisco
Communication…
1.3.6.1.4.1.9.9.157 ciscoCdmaPdsnMIB3984 This MIB is to support the CDMA PDSN (Packet Data Serving
Node) feature. A CDMA2000 network supports wireless data
communication…
1.3.6.1.4.1.9.9.158 ciscoAAAClientMIB325 This MIB module provides data for authentication method
priority based on Authentication, Authorization,
Accounting (AAA) protoco…
1.3.6.1.4.1.9.9.159 ciscoQosPolicyConfigMIB335 This MIB module defines managed objects that support the
policy source configuration of Quality of Service (QoS) on
the device.

T…
1.3.6.1.4.1.9.9.160 ciscoCircuitInterfaceMIB211 The MIB module to configure the circuit description
for an interface.
The circuit description can be used to describe and
identify…
1.3.6.1.4.1.9.9.161 ciscoSlbMIB3279 The MIB for managing Server Load Balancing Manager(s),
such as the Cisco IOS SLB product.

This MIB includes instrumentation for t…
1.3.6.1.4.1.9.9.162 ciscoVsiMasterMIB3109 This MIB module contains objects related to the master side of the
the Virtual Switch Interface protocol used for control of ATM
…
1.3.6.1.4.1.9.9.163 ciscoCallTrackerMIB3104 CISCO-CALL-TRACKER-MIB
1.3.6.1.4.1.9.9.164 ciscoCallTrackerTCPMIB325 This MIB module provides TCP service connection
related data for tracking the progress and status of
a call.

This module extends t…
1.3.6.1.4.1.9.9.165 ciscoCallTrackerModemMIB397 This MIB module provides modem call related data for
tracking the progress and status of a call.

This module extends tables defin…
1.3.6.1.4.1.9.9.166 ciscoCBQosMIB2562 Cisco Class-Based QoS MIB

**********************************
Overview
**********************************
This MIB provides read acc…
1.3.6.1.4.1.9.9.167 ciscoWirelessDocsIfMib3140 This is the MIB Module for MCNS compliant Radio Frequency
(RF) interfaces in wireless point-to-multipoint subscriber
units (SU) a…
1.3.6.1.4.1.9.9.168 ciscoNtpMIB387 This MIB module defines a MIB which provides
mechanisms to monitor an NTP server.

The MIB is derived from the Technical Report
#Ma…
1.3.6.1.4.1.9.9.169 ciscoWirelessDocsExtMIB399 This MIB module defines Cisco-specific objects that
add to the functionality defined in
CISCO-WIRELESS-DOCS-IF-MIB.
These objects …
1.3.6.1.4.1.9.9.170 ciscoWirelessPhyMIB2112 This is the MIB Module for the Cisco Wireless Radio
Point to MultiPoint interface.
1.3.6.1.4.1.9.9.171 ciscoIpSecFlowMonitorMIB3507 This is a MIB Module for monitoring the
structures in IPSec-based Virtual Private Networks.
The MIB has been designed to be adopt…
1.3.6.1.4.1.9.9.172 ciscoIpSecPolMapMIB321 The MIB module maps the IPSec
entities created dynamically to the policy entities
that caused them. This is an appendix to the
IPS…
1.3.6.1.4.1.9.9.173 ciscoPrivateVlanMIB256 The MIB module to support Private VLAN feature on
Cisco's switching devices.
1.3.6.1.4.1.9.9.174 ciscoMobileIpMIB3533 An extension to the IETF MIB module defined in
RFC-2006 for managing Mobile IP implementations.

Mobile IP introduces the followin…
1.3.6.1.4.1.9.9.175 ciscoIfLinkConfigMIB215 The MIB module for configuration of bulk distribution
(de-multiplexing of traffic from higher-bandwidth to
lower-bandwidth interf…
1.3.6.1.4.1.9.9.176 ciscoRFMIB3117 This MIB provides configuration control and status for the
Redundancy Framework (RF) subsystem. RF provides a mechanism
for logic…
1.3.6.1.4.1.9.9.177 ciscoSaaApmMIB338 Acronyms and Terms:
SAA - Service Assurance Agent
APM - Application Performance Monitoring

A MIB for controlling SAA APM.
APM provi…
1.3.6.1.4.1.9.9.178 ciscoContentEngineMIB3263 The MIB module for the Cisco Content Engine from
Cisco Systems, Inc.
1.3.6.1.4.1.9.9.179 ciscoCatOSAclQosMIB3470 This MIB module is for Access Control Lists(ACLs) configuration
of Quality of Service (QoS) as well as Security feature on the
Ci…
1.3.6.1.4.1.9.9.180 ciscoWirelessRfMetricsMIB599 This is the MIB Module for the Cisco Wireless Radio
Point to MultiPoint interface specification.