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.616 | ciscoLwappMeshMIB | 3 | 215 | 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.617 | ciscoLwappMeshStatsMIB | 4 | 99 | 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.618 | ciscoLwappSysMIB | 3 | 310 | 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.619 | ciscoLwappLocalAuthMIB | 3 | 54 | 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.620 | ciscoLwappMeshBatteryMIB | 3 | 34 | 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.621 | ciscoH324DialControlMIB | 2 | 34 | This MIB module enhances the IETF Dial Control MIB (RFC2128) by providing H.324 call information over a telephony network. ITU-T R… |
| 1.3.6.1.4.1.9.9.622 | ciscoLwappDot11ClientTsMIB | 3 | 34 | 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.623 | ciscoLwappCdpMIB | 3 | 56 | 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.624 | ciscoIpSlaTCMIB | 0 | 0 | This MIB contains textual conventions used by CISCO IPSLA MIBs. Acronyms: FEC: Forward Equivalence Class LPD: Label Path Discovery L… |
| 1.3.6.1.4.1.9.9.626 | ciscoDot11HtMacMIB | 3 | 40 | 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.627 | ciscoDot11RadarMIB | 3 | 25 | This MIB module is for IEEE 802.11a/h Root device, i.e. Access Point (AP) or Root Bridge. This MIB allows dynamic frequency selec… |
| 1.3.6.1.4.1.9.9.628 | ciscoServiceControlSubscribersMIB | 3 | 37 | This MIB provides global and specific information on subscribers managed by a service control entity, which is a network element … |
| 1.3.6.1.4.1.9.9.630 | ciscoTelnetServerMIB | 3 | 34 | MIB module for displaying and configuring Telnet related features in a device. Telnet is a program to log into another computer o… |
| 1.3.6.1.4.1.9.9.631 | ciscoServiceControlLinkMIB | 3 | 21 | This MIB module provides information about the status and configuration of links used by service control entities. The link on a … |
| 1.3.6.1.4.1.9.9.632 | ciscoSmeMIB | 3 | 54 | MIB module to manage Storage Media Encryption (SME) service. SME is an encryption service provided by an encryption node residing… |
| 1.3.6.1.4.1.9.9.633 | ciscoIpSlaAutoMIB | 3 | 57 | This module defines the MIB for IP SLA Automation. IP SLA Automation consists of the following: 1. Use of grouping - Group is an … |
| 1.3.6.1.4.1.9.9.634 | ciscoServiceControlTpStatsMIB | 3 | 39 | This MIB provides information and statistics on the traffic processor(s) of a service control entity, which is a network element … |
| 1.3.6.1.4.1.9.9.635 | ciscoIpSlaJitterMIB | 3 | 57 | This MIB module defines templates for IP SLA operations of UDP Jitter and ICMP Jitter. The UDP Jitter operation is designed to me… |
| 1.3.6.1.4.1.9.9.636 | ciscoIpSlaEchoMIB | 3 | 71 | This MIB module defines the templates for IP SLA operations of ICMP echo, UDP echo and TCP connect. The ICMP echo operation measu… |
| 1.3.6.1.4.1.9.9.637 | ciscoServiceControlRdrMIB | 3 | 56 | This MIB module defines objects describing statistics and configuration relating to the Raw Data Record Formatter running on a se… |
| 1.3.6.1.4.1.9.9.638 | ciscoAgwMIB | 3 | 324 | This module manages Cisco's WiMAX ASN Gateway (ASN-GW). A WiMAX network supports wireless data communication through WiMAX radio … |
| 1.3.6.1.4.1.9.9.639 | ciscoOtnIfMIB | 3 | 164 | This MIB module defines the managed objects for physical layer characteristics of DWDM optical channel interfaces and performanc… |
| 1.3.6.1.4.1.9.9.640 | ciscoImageLicenseMgmtMIB | 3 | 31 | The MIB module for managing the running image level of a Cisco device. Cisco's licensing mechanism provides flexibility to run a … |
| 1.3.6.1.4.1.9.9.642 | ciscoBridgeDomainMIB | 3 | 24 | A bridge domain is one of the means by which it is possible to define a broadcast domain on a bridging device. It is an alternati… |
| 1.3.6.1.4.1.9.9.643 | ciscoTelepresenceMIB | 3 | 119 | The MIB module defines the managed objects for a Telepresence system. Telepresence refers to a set of technologies which allow a p… |
| 1.3.6.1.4.1.9.9.644 | ciscoTelepresenceCallMIB | 3 | 178 | The MIB module defines the managed objects for Telepresence calls. Telepresence refers to a set of technologies which allow a pers… |
| 1.3.6.1.4.1.9.9.645 | ciscoEtherExtMIB | 3 | 18 | The MIB module to describe generic objects for ethernet-like network interfaces. This MIB provides ethernet-like network interfac… |
| 1.3.6.1.4.1.9.9.646 | ciscoAonStatusMIB | 3 | 80 | This MIB module defines managed objects that facilitate the management of AON node. The information available through this MIB in… |
| 1.3.6.1.4.1.9.9.647 | ciscoGgsnExtMIB | 3 | 212 | This MIB module extends the CISCO-GGSN-MIB. This MIB module manages the Gateway GPRS Support Node (GGSN) devices. A GGSN device pr… |
| 1.3.6.1.4.1.9.9.648 | ciscoVirtualInterfaceMIB | 2 | 32 | The MIB module for creation and deletion of Virtual Interfaces and Virtual Interface Groups. In addition to this MIB, interface … |
| 1.3.6.1.4.1.9.9.650 | ciscoL4L7moduleRedundancyMIB | 3 | 71 | The L4-7 SLB devices are used for scaling websites, building web enabled applications, and migrating to web services. The followin… |
| 1.3.6.1.4.1.9.9.651 | ciscoCommonRolesExtMIB | 3 | 37 | A MIB Module for managing the roles that are common between access methods like Command Line Interface (CLI), SNMP and XML interf… |
| 1.3.6.1.4.1.9.9.652 | ciscoSwitchStatsMIB | 3 | 106 | The MIB module provides management information for configuration and monitoring of traffic statistics on Cisco's switching device… |
| 1.3.6.1.4.1.9.9.653 | ciscoAdmissionPolicyMIB | 3 | 36 | This MIB module defines managed objects that facilitate the management of policies upon host(s) admission to a network. The inform… |
| 1.3.6.1.4.1.9.9.654 | ciscoMabMIB | 3 | 20 | MIB module for monitoring and configuring MAC Authentication Bypass (MAB) feature in the system. MAC Auth Bypass feature provides… |
| 1.3.6.1.4.1.9.9.655 | ciscoDigitalMediaSystemsMIB | 3 | 195 | Acronyms and Definitions The following acronyms and terms are used in this document: DMS: Digital Media Systems DAM: Digital As… |
| 1.3.6.1.4.1.9.9.656 | ciscoAuthFrameworkMIB | 3 | 117 | MIB module for Authentication Framework in the system. Authentication Framework provides generic configurations for authenticatio… |
| 1.3.6.1.4.1.9.9.657 | ciscoSbcCallStatsMIB | 3 | 201 | The main purpose of this MIB is to define the statistics information for Session Border Controller application. The statistics ar… |
| 1.3.6.1.4.1.9.9.658 | ciscoSessBorderCtrlrEventMIB | 3 | 208 | The main purpose of this MIB is to define the SNMP notifications and alarms generated by Session Border Controller application an… |
| 1.3.6.1.4.1.9.9.660 | ciscoNportVirtualizationMIB | 3 | 19 | The MIB module for the management of N_port Virtualization or NPV within the framework of Cisco's N_port virtualization (NPV) Arc… |
| 1.3.6.1.4.1.9.9.661 | ciscoWan3gMIB | 3 | 378 | This MIB module provides network management support for Cisco cellular 3G WAN products. *** ABBREVIATIONS, ACRONYMS, AND SYMBOLS … |
| 1.3.6.1.4.1.9.9.662 | ciscoCbpTcMIB | 0 | 0 | This MIB module defines textual conventions used by the CISCO-CBP-BASE-CFG-MIB, CISCO-CBP-BASE-MON-MIB, and any MIB modules exten… |
| 1.3.6.1.4.1.9.9.663 | ciscoSwitchHardwareCapacityMIB | 3 | 147 | This MIB module defines the managed objects for hardware capacity of Cisco switching devices. The hardware capacity information c… |
| 1.3.6.1.4.1.9.9.664 | ciscoMmodalContactAppsMIB | 3 | 359 | The Cisco Unified Multi-Modal Contact Applications (MMCA) platform is a highly scalable, modular, extensible, open and secure pl… |
| 1.3.6.1.4.1.9.9.667 | ciscoServiceControllerMIB | 2 | 31 | This MIB module defines objects describing traffic controllers used by a service control entity. A service control entity is a ne… |
| 1.3.6.1.4.1.9.9.668 | ciscoP2PIfMIB | 3 | 16 | The Point to Point Interface MIB module. This MIB manages the generic objects for Serial link or SONET/SDH like point to point ne… |
| 1.3.6.1.4.1.9.9.669 | ciscoCdmaPdsnExtMIB | 3 | 178 | This MIB is an extension to the CISCO-CDMA-PDSN-MIB. A CDMA network supports wireless data communication through 3G CDMA radio acc… |
| 1.3.6.1.4.1.9.9.670 | ciscoReportIntervalTcMIB | 0 | 0 | CISCO-REPORT-INTERVAL-TC-MIB |
| 1.3.6.1.4.1.9.9.672 | ciscoMobilityTapMIB | 3 | 24 | This module manages Cisco's intercept feature for Mobility Gateway Products. This MIB is used along with CISCO-TAP2-MIB MIB to int… |
| 1.3.6.1.4.1.9.9.673 | ciscoFCoEMIB | 2 | 45 | This MIB module is for configuring and monitoring Fibre Channel over Ethernet (FCoE) related entities. This MIB defines the Virtu… |