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
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
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:
- Netdisco archive revision metadata (not a manufacturer release date)File: repos/netdisco/netdisco-mibs/commits/master; 15,422 bytes
- Netdisco MIB distribution at the selected archive revision38.9 MiB
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:
- Observium Community original distribution archivePublisher Last-Modified: Tue, 05 May 2026 13:47:48 GMT; 127.4 MiB
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
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
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)
Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)
Direct children (3)
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.600.0 | ciscoGslbHealthMonMIBNotifs | 1 | 1 | |
| 1.3.6.1.4.1.9.9.600.1 | ciscoGslbHealthMonMIBObjects | 4 | 75 | |
| 1.3.6.1.4.1.9.9.600.2 | ciscoGslbHealthMonMIBConform | 2 | 11 |
Siblings (706)
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.743 | ciscoCdstvCsStatsMIB | 3 | 83 | This MIB module defines objects describing the caching and streaming statistics objects that facilitate the management of the Cis… |
| 1.3.6.1.4.1.9.9.744 | ciscoIpslaVideoMIB | 3 | 73 | IP SLA is a capability which utilizes active monitoring for network performance. It can be used for network troubleshooting, net… |
| 1.3.6.1.4.1.9.9.745 | ciscoEntitySensorExtMIB | 3 | 21 | This MIB is extension to ENTITY-SENSOR-MIB(RFC 3433). This MIB also defines the notifications applicable for sensors reported in … |
| 1.3.6.1.4.1.9.9.747 | ciscoEntityStateExtMIB | 3 | 22 | |
| 1.3.6.1.4.1.9.9.748 | ciscoIpAddressPoolMIB | 3 | 96 | This MIB modules defines objects that describe common aspects of IP address pools. IP Address Pool Manager ======================= … |
| 1.3.6.1.4.1.9.9.749 | ciscoCdstvBwmgrMIB | 3 | 21 | This MIB module defines Bandwidth Manager configuration objects that facilitate the management of the Cisco Content Delivery Syst… |
| 1.3.6.1.4.1.9.9.750 | ciscoCdstvIngestTuningMIB | 3 | 18 | This MIB module defines ingest tuning configuration objects that facilitate the management of the Cisco Content Delivery System f… |
| 1.3.6.1.4.1.9.9.751 | ciscoCdstvAuthmgrMIB | 3 | 25 | This MIB module defines objects that describe the configuration of the authentication manager for the Cisco Content Delivery Syst… |
| 1.3.6.1.4.1.9.9.753 | ciscoVideoSessionMIB | 3 | 145 | This MIB module complements the CISCO-VOICE-DIAL-CONTROL-MIB, which provides voice telephony peer information, by providing manag… |
| 1.3.6.1.4.1.9.9.754 | ciscoCdstvServerMIB | 3 | 82 | This MIB module defines server configuration that faciliate the management of the Cisco Content Delivery System for TV (CDS-TV) … |
| 1.3.6.1.4.1.9.9.755 | ciscoCdstvIsaMIB | 3 | 145 | This MIB module defines ISA configuration objects that faciliate the management of the Cisco Content Delivery System for TV (CDS-… |
| 1.3.6.1.4.1.9.9.756 | ciscoEntityPerformanceMIB | 3 | 56 | This MIB module defines managed objects that facilitate to monitor performance of any physical entity, which are listed in the EN… |
| 1.3.6.1.4.1.9.9.757 | ciscoSbcStatsMIB | 3 | 106 | The main purpose of this MIB is to define the statistics information for Session Border Controller application. This MIB categori… |
| 1.3.6.1.4.1.9.9.758 | ciscoTelepresenceExchangeSystemMIB | 3 | 173 | The main purpose of this MIB is to provide product component level configuration, status, statistics, events, and alarm notificat… |
| 1.3.6.1.4.1.9.9.759 | ciscoGdoiMIB | 3 | 213 | This MIB module defines objects for managing the GDOI protocol. Copyright (c) The IETF Trust (2010). This version of this MIB mo… |
| 1.3.6.1.4.1.9.9.760 | ciscoPtpMIB | 3 | 198 | The MIB module for PTPv2 (IEEE1588 - 2008) Overview of PTPv2 (IEEE 1588-2008) This IEEE standard defines a protocol enabling prec… |
| 1.3.6.1.4.1.9.9.761 | ciscoNetsyncMIB | 3 | 104 | The Synchronous Ethernet (SyncE) MIB is defined for monitoring network synchronization based on ITU-T G.781 clock selection. Sync… |
| 1.3.6.1.4.1.9.9.762 | ciscoWanOptimizationMIB | 3 | 302 | This MIB is for managing Wide Area Network (WAN) Optimization systems. The objective of WAN optimization system is to reduce as m… |
| 1.3.6.1.4.1.9.9.763 | ciscoVideoTc | 0 | 0 | This MIB module defines a collection of common video-related textual conventions to be used in Cisco MIBS for video-capable produ… |
| 1.3.6.1.4.1.9.9.764 | ciscoUbeMIB | 2 | 12 | This MIB describes objects used for managing Cisco Unified Border Element (CUBE). The Cisco Unified Border Element (CUBE) is a Ci… |
| 1.3.6.1.4.1.9.9.765 | ciscoFlowCloneMIB | 3 | 44 | This MIB module defines objects that manages flow cloning feature. A flow cloning can be described as a hardware or software en… |
| 1.3.6.1.4.1.9.9.766 | ciscoIpslaVideoProfileMIB | 3 | 29 | IP SLA is a capability which utilizes active monitoring for network performance. It can be used for network troubleshooting, net… |
| 1.3.6.1.4.1.9.9.767 | ciscoLwappDot11ClientRmMIB | 3 | 64 | 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.768 | ciscoEntitySensorHistoryMIB | 2 | 20 | This MIB module defines objects that describe collections and measurement information for each sensor supporting historical data … |
| 1.3.6.1.4.1.9.9.769 | ciscoMediaQualityMIB | 3 | 214 | This MIB module enhances the DIAL-CONTROL-MIB (RFC2128) by providing call information and voice and video quality statistics of c… |
| 1.3.6.1.4.1.9.9.770 | ciscoTcpMetricsMIB | 4 | 22 | This MIB module defines objects that describe the quality metrics of TCP streams. GLOSSARY ============ Flow Monitor - a hardware o… |
| 1.3.6.1.4.1.9.9.771 | ciscoMediaMetricsMIB | 4 | 38 | This MIB module defines objects that describe the quality metrics of Media streams. GLOSSARY ============ Flow Monitor - a hardware… |
| 1.3.6.1.4.1.9.9.772 | ciscoPfrMIB | 3 | 303 | This MIB module defines objects that describe Performance Routing (PfR). Standard routing protocols base routing decisions on re… |
| 1.3.6.1.4.1.9.9.773 | ciscoSwitchRateLimiterMIB | 3 | 28 | This MIB module defines management objects for the Switch Rate Limiter features on Cisco Layer 2 and Layer 3 devices. Rate limits … |
| 1.3.6.1.4.1.9.9.774 | ciscoVdcMIB | 3 | 90 | CISCO-VDC-MIB |
| 1.3.6.1.4.1.9.9.775 | ciscoSelectiveVrfDownloadMIB | 3 | 41 | This MIB module defines objects describing selective VRF download. The selective VRF download feature makes a best effort to dow… |
| 1.3.6.1.4.1.9.9.776 | ciscoNetflowLiteMIB | 3 | 56 | This MIB provides a method to configure Netflow-lite feature and get information in these areas: 1. Exporter config information a… |
| 1.3.6.1.4.1.9.9.777 | ciscoDsgIfExtMIB | 3 | 15 | A MIB module for extending the DSG-IF-MIB (ITU-T J.128 10/2008) to add objects which provide additional management information ab… |
| 1.3.6.1.4.1.9.9.778 | ciscoLwappRFMIB | 3 | 143 | |
| 1.3.6.1.4.1.9.9.779 | ciscoPmonMIB | 3 | 14 | ciscoPmonMIB MODULE-IDENTITY LAST-UPDATED "201201030000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Custom… |
| 1.3.6.1.4.1.9.9.782 | ciscoSubscriberIdentityTcMIB | 0 | 0 | This MIB module defines textual conventions describing subscriber session identities. A subscriber session identity consists of … |
| 1.3.6.1.4.1.9.9.783 | ciscoDynamicTemplateTcMIB | 0 | 0 | This MIB module defines textual conventions used by the CISCO-DYNAMIC-TEMPLATE-MIB and MIB modules that use and expand on dynamic… |
| 1.3.6.1.4.1.9.9.784 | ciscoDynamicTemplateMIB | 3 | 152 | This MIB defines objects that describe dynamic templates. A dynamic template is a set of configuration attributes that a system … |
| 1.3.6.1.4.1.9.9.785 | ciscoSubscriberSessionTcMIB | 0 | 0 | This MIB module defines textual conventions describing subscriber sessions. |
| 1.3.6.1.4.1.9.9.786 | ciscoSubscriberSessionMIB | 3 | 187 | This MIB defines objects describing subscriber sessions, or more specifically, subscriber sessions terminated by a RAS. A subscr… |
| 1.3.6.1.4.1.9.9.789 | ciscoFlowMetadataMIB | 3 | 30 | The MIB module for managing Cisco medianet flow metadata. Metadata, in the simplest form, is data that qualifies other data. Flow… |
| 1.3.6.1.4.1.9.9.790 | ciscoSwitchCefMIB | 3 | 33 | This MIB module defines management objects for the CEF features on Cisco Layer 2 and Layer 3 devices. Definition of some of the t… |
| 1.3.6.1.4.1.9.9.791 | ciscoAppNavMIB | 2 | 51 | ciscoAppNavMIB MODULE-IDENTITY LAST-UPDATED "201206070000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Cust… |
| 1.3.6.1.4.1.9.9.792 | ciscoLwappDhcpMIB | 3 | 54 | |
| 1.3.6.1.4.1.9.9.793 | ciscoMspMIB | 3 | 54 | Objective of media services proxy is to provide media services to end-points and its flows identified by a set of protocols. Medi… |
| 1.3.6.1.4.1.9.9.798 | ciscoLocalAuthUserMIB | 3 | 40 | This MIB module defines objects describing users authenticated locally by a Network Access Server (NAS). + | | | … |
| 1.3.6.1.4.1.9.9.800 | ciscoMediatraceMIB | 3 | 191 | Mediatrace helps to isolate and troubleshoot network degradation problems by enabling a network administrator to discover an Inte… |
| 1.3.6.1.4.1.9.9.801 | ciscoFabricPathTopologyMIB | 3 | 40 | This MIB module defines managed objects that facilitate the management of Cisco's FabricPath Topology technology. |
| 1.3.6.1.4.1.9.9.803 | ciscoSwitchFabricMIB | 3 | 30 | This MIB module defined managed objects that facilitates the management of switching fabric information in a Cisco switch. |
| 1.3.6.1.4.1.9.9.804 | ciscoHardwareIpVerifyMIB | 3 | 13 | This MIB module defines management objects for configuration and monitoring of the Intrusion Detection System (IDS) that checks f… |