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
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.my.txt
Company: None
Module: CISCO-GSLB-HEALTH-MON-MIB
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.
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: [email protected]" 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 }
ciscoGslbHealthMonMIB OBJECT IDENTIFIER ::= { ciscoMgmt 600 }
Vendor: Cisco
Module: CISCO-GSLB-HEALTH-MON-MIB
[Automatically extracted from oidview.com]
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: [email protected]" 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 }
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: [email protected]" 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 }
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.4.1.9.9.600.0 | ciscoGslbHealthMonMIBNotifs | 1 | 1 | None |
1.3.6.1.4.1.9.9.600.1 | ciscoGslbHealthMonMIBObjects | 4 | 75 | None |
1.3.6.1.4.1.9.9.600.2 | ciscoGslbHealthMonMIBConform | 2 | 11 | None |
To many brothers! Only 100 nearest brothers are shown.
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
... | ||||
1.3.6.1.4.1.9.9.572 | ciscoRttMonIPExtMIB | 2 | 38 | 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 | ciscoQosTcMIB | 0 | 0 | This module defines the textual conventions used within Cisco Qos MIBs. |
1.3.6.1.4.1.9.9.576 | ciscoLwappMobilityMIB | 3 | 60 | 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 | ciscoLwappAclMIB | 3 | 26 | 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 | ciscoRoutePoliciesMIB | 3 | 5 | 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 | ciscoSwitchQosMIB | 3 | 295 | 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 | ciscoGslbTcMIB | 0 | 0 | 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 | ciscoEntityDiagTcMIB | 0 | 0 | This module defines the textual conventions used within Cisco Entity Diag MIB. |
1.3.6.1.4.1.9.9.585 | ciscoIpSlaEthernetMIB | 3 | 194 | 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 | ciscoNotificationControlMIB | 2 | 28 | 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 | ciscoGslbSystemMIB | 3 | 103 | 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 | ciscoCvpMIB | 3 | 255 | 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 | ciscoPrefPathMIB | 3 | 56 | 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 | ciscoFcSdvMIB | 3 | 28 | 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 | ciscoApplicationAccelerationMIB | 3 | 37 | 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 | ciscoGslbDnsMIB | 3 | 165 | 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 | ciscoContentServicesMIB | 3 | 349 | 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 | ciscoLwappAAAMIB | 3 | 73 | 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 | ciscoLwappDot11ClientMIB | 4 | 49 | 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 | ciscoResilientEthernetProtocolMIB | 3 | 77 | 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 | ciscoPacketCaptureMIB | 3 | 103 | The MIB module for the management of packet capture feature. |
1.3.6.1.4.1.9.9.603 | ciscoThreatMitigationServiceMIB | 3 | 68 | 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 | cdot1CfmMIB | 3 | 166 | Connectivity Fault Management module for managing IEEE 802.1ag |
1.3.6.1.4.1.9.9.606 | ciscoLwappMeshLinkTestMIB | 3 | 46 | ciscoLwappMeshLinkTestMIB MODULE-IDENTITY LAST-UPDATED "200702050000Z" ORGANIZATION "Cisco Systems Inc." CONTACT-INFO "Cisco Sy… |
1.3.6.1.4.1.9.9.607 | ciscoDot11HtPhyMIB | 3 | 71 | 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 | ciscoLwappRogueMIB | 3 | 78 | 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 | ciscoLwappDot11ClientCCXTextualConventions | 0 | 0 | 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 | ciscoLwappDot11MIB | 3 | 17 | 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 | ciscoEvcMIB | 3 | 156 | 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 | ciscoLwappDot11LdapMIB | 3 | 33 | 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 | ciscoLwappRrmMIB | 3 | 28 | 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.616 | ciscoLwappMeshMIB | 3 | 121 | 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 | 98 | 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 | 163 | 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 | 53 | 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 | 51 | 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 | 137 | 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… |
... |