Home/Catalog/CISCO-GSLB-DNS-MIB

CISCO-GSLB-DNS-MIB

AI MIB Summary

The CISCO-GSLB-DNS-MIB enables monitoring of Cisco Global Server Load Balancer DNS operations, tracking query/response statistics and the operational status of answer groups, domain lists, source address lists, and proximity rules. It facilitates the observation of load balancing algorithms, proximity probing metrics, and DNS race (boomerang) configurations to manage traffic steering based on network topology and server availability.

The MIB defines objects for status and statistics information of DNS related operations of Global Server Load Balancer(GSLB). The MIB defines objects for global statistical information like DNS queries received, DNS responses sent, etc. Further it defines objects for answer, answer group, domain list, source address list, proximity rule and DNS rule statistics. It also defines related notifications. Acronyms and terminology: DNS : Domain Name System (RFC1035) D-proxy : Local DNS name server of the client. 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 server load balancer device, 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 Agent (CRA) : A device which uses a resolution process called DNS race to send identical and simultaneous responses back to a client D-proxy for proximity determination. Answer group : A logical grouping of answers. It is a set of virtual IP address (VIP), name server (NS), or content routing agent (CRA) addresses from which an individual answer is selected and used to reply to a content request. Answers are grouped together as resource pools. The GSLB device, using one of a number of available balance methods, can choose the most appropriate resource to serve each user request from the answers in an answer group. Balance method : A balance method is an algorithm for selecting the best server for replying to a DNS query. Domain list : A collection of domain names for Internet or intranet resources that have been delegated to the GSLB device for DNS query responses. Domain lists either contain complete domain names or regular expression that specifies a pattern by which the GSLB device matches incoming DNS requests. Source address list : A collection of IP addresses or address blocks meant to hold information about known D-proxies. This information is used by the GSLB device while answering DNS queries. DNS rule : A rule which controls the operation of GSLB device. It identifies the actions to be performed by the GSLB device when it receives a DNS request from a known source (a member of a source address list) for a known domain (a member of a domain list) by specifying which response (answer) is to be given to the requesting D-proxy and how that answer is chosen. Proximity : Refers to the distance or delay, in terms of network topology and not geographic distance, between the requesting client D-proxy and the resources corresponding to that request. Proximity probing : To respond to DNS requests with the most proximate answers, the GSLB device communicates with a probing device located in each proximity zone to gather round-trip time (RTT) metric information measured between the requesting client D-proxy and the zone. The GSLB device then directs client requests to an available resource with the lowest RTT value. Proximity subsystem : Component within the GSLB device responsible for proximity determination. Clause : A clause specifies that a particular answer group serve the request and a specific balance method be used to select the best resource from that answer group. Boomerang server : A method of proximity routing used by GSLB device with CRAs. It is also known as DNS race. The boomerang method is based on the concept that instantaneous proximity can be determined if a CRA within each data center sends a DNS A-record (IP address) at the exact same time to the requesting D-proxy. This gives all CRAs a chance at resolving a client request and allows for proximity to be determined without probing the client D-proxy. Whichever DNS A-record is received first by the D-proxy is, by default, considered to be the most proximate. For the GSLB device to initiate a DNS race, it needs to establish the following two pieces of information for each CRA: (a) The delay between the GSLB device and each of the CRAs in each data center. With this data, the GSLB device computes how long to delay the race from each data center, so that each CRA starts the race simultaneously. (b) The online status of the CRAs. With this data, the GSLB device knows not to forward requests to any CRA that is not responding. The boomerang server on the GSLB device gathers this information by sending keepalive messages at predetermined intervals. The boomerang server uses this data, along with the IP addresses of the CRAs, to request the exact start time of the DNS race. If the CRA response is to be accepted by the D-proxy, each CRA must spoof the IP address of the GSLB device to which the original DNS request was sent.
Main OID:
ciscoGslbDnsMIB.1.3.6.1.4.1.9.9.595
126
Objects
Active
Status
8
Dependencies

Imported Objects

Objects

126 total
Object Name
ciscoGslbDnsMIB
MODULE-IDENTITY
.1.3.6.1.4.1.9.9.595
ciscoGslbDnsMIBNotifs
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.595.0
ciscoGslbDnsEventClause
NOTIFICATION-TYPE
.1.3.6.1.4.1.9.9.595.0.1
ciscoGslbAnswerEventStatusChange
NOTIFICATION-TYPE
.1.3.6.1.4.1.9.9.595.0.2
ciscoGslbDnsMIBObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.595.1
cgdNotifControl
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.595.1.1
cgdDnsClauseNotifEnablerw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.9.9.595.1.1.1
cgdDnsAnswerNotifEnablerw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.9.9.595.1.1.2
cgdNotifObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.595.1.2
cgdAnswerPrevStatusro
CiscoGslbAnswerStatus (CISCO-GSLB-TC-MIB)
.1.3.6.1.4.1.9.9.595.1.2.1
cgdGlobal
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.595.1.3
cgdTotalDomainsro
Unsigned32
.1.3.6.1.4.1.9.9.595.1.3.1
cgdTotalDomainListsro
Unsigned32
.1.3.6.1.4.1.9.9.595.1.3.2
cgdTotalSourceAddressesro
Unsigned32
.1.3.6.1.4.1.9.9.595.1.3.3
cgdTotalSourceAddressListsro
Unsigned32
.1.3.6.1.4.1.9.9.595.1.3.4
cgdTotalAnswersro
Unsigned32
.1.3.6.1.4.1.9.9.595.1.3.5
cgdTotalAnswerGroupsro
Unsigned32
.1.3.6.1.4.1.9.9.595.1.3.6
cgdTotalRulesro
Unsigned32
.1.3.6.1.4.1.9.9.595.1.3.7
cgdAnsTrapRateLimitro
Unsigned32
.1.3.6.1.4.1.9.9.595.1.3.8
cgdDnsClauseTrapRateLimitro
Unsigned32
.1.3.6.1.4.1.9.9.595.1.3.9
cgdGlobalStats
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.595.1.4
cgdDnsRcvdQueriesro
Counter32 UNITS "queries"
.1.3.6.1.4.1.9.9.595.1.4.1
cgdDnsRcvdHostAddrQueriesro
Counter32 UNITS "queries"
.1.3.6.1.4.1.9.9.595.1.4.2
cgdDnsUnmatchedQueriesro
Counter32 UNITS "queries"
.1.3.6.1.4.1.9.9.595.1.4.3
cgdDnsDroppedQueriesro
Counter32 UNITS "queries"
.1.3.6.1.4.1.9.9.595.1.4.4
cgdNSFwdSentQueriesro
Counter32 UNITS "queries"
.1.3.6.1.4.1.9.9.595.1.4.5
cgdNSFwdRcvdRespsro
Counter32 UNITS "responses"
.1.3.6.1.4.1.9.9.595.1.4.6
cgdBoomServSentReqsro
Counter32 UNITS "requests"
.1.3.6.1.4.1.9.9.595.1.4.7
cgdProxLkupSentReqsro
Counter32 UNITS "requests"
.1.3.6.1.4.1.9.9.595.1.4.8
cgdProxLkupRcvdRespsro
Counter32 UNITS "responses"
.1.3.6.1.4.1.9.9.595.1.4.9
cgdDnsQueryRateCurrentro
Gauge32 UNITS "requests per second"
.1.3.6.1.4.1.9.9.595.1.4.10
cgdDnsQueryRatePeakro
Unsigned32 UNITS "requests per second"
.1.3.6.1.4.1.9.9.595.1.4.11
cgdDnsUdpSrcPortErrsro
Counter32 UNITS "errors"
.1.3.6.1.4.1.9.9.595.1.4.12
cgdDnsTcpSrcPortErrsro
Counter32 UNITS "errors"
.1.3.6.1.4.1.9.9.595.1.4.13
cgdDnsPollSockErrsro
Counter32 UNITS "errors"
.1.3.6.1.4.1.9.9.595.1.4.14
cgdDroppedAnsNotifsro
Unsigned32 UNITS "traps"
.1.3.6.1.4.1.9.9.595.1.4.15
cgdDroppedDnsClauseNotifsro
Unsigned32 UNITS "traps"
.1.3.6.1.4.1.9.9.595.1.4.16
cgdAnswer
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.595.1.5
cgdAnswerGroupTable
SEQUENCE OF CgdAnswerGroupEntry
.1.3.6.1.4.1.9.9.595.1.5.1
cgdAnswerGroupEntry
CgdAnswerGroupEntry
.1.3.6.1.4.1.9.9.595.1.5.1.1
cgdAnswerGroupName
SnmpAdminString
.1.3.6.1.4.1.9.9.595.1.5.1.1.1
cgdAnswerGroupTyperw
CiscoGslbAnswerType (CISCO-GSLB-TC-MIB)
.1.3.6.1.4.1.9.9.595.1.5.1.1.2
cgdAnswerGroupHitsro
Counter32 UNITS "number of hits"
.1.3.6.1.4.1.9.9.595.1.5.1.1.3
cgdAnswerGroupStorageTyperw
StorageType (SNMPv2-TC)
.1.3.6.1.4.1.9.9.595.1.5.1.1.4
cgdAnswerGroupRowStatusrw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.9.9.595.1.5.1.1.5
cgdAnswerTable
SEQUENCE OF CgdAnswerEntry
.1.3.6.1.4.1.9.9.595.1.5.2
cgdAnswerEntry
CgdAnswerEntry
.1.3.6.1.4.1.9.9.595.1.5.2.1
cgdAnswerId
Unsigned32 (1..4294967295 )
.1.3.6.1.4.1.9.9.595.1.5.2.1.1
cgdAnswerTyperw
CiscoGslbAnswerType (CISCO-GSLB-TC-MIB)
.1.3.6.1.4.1.9.9.595.1.5.2.1.2
cgdAnswerAddressTyperw
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.595.1.5.2.1.3
cgdAnswerAddressrw
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.595.1.5.2.1.4
cgdAnswerNamerw
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.595.1.5.2.1.5
cgdAnswerGrpNamerw
SnmpAdminString
.1.3.6.1.4.1.9.9.595.1.5.2.1.6
cgdAnswerAdminStaterw
CiscoGslbAnswerAdminState (CISCO-GSLB-TC-MIB)
.1.3.6.1.4.1.9.9.595.1.5.2.1.7
cgdAnswerStatusro
CiscoGslbAnswerStatus (CISCO-GSLB-TC-MIB)
.1.3.6.1.4.1.9.9.595.1.5.2.1.8
cgdAnswerHitsro
Counter32 UNITS "number of hits"
.1.3.6.1.4.1.9.9.595.1.5.2.1.9
cgdAnswerRate1Minro
Gauge32 UNITS "hits per second"
.1.3.6.1.4.1.9.9.595.1.5.2.1.10
cgdAnswerRate5Minro
Gauge32 UNITS "hits per second"
.1.3.6.1.4.1.9.9.595.1.5.2.1.11
cgdAnswerRate30Minro
Gauge32 UNITS "hits per second"
.1.3.6.1.4.1.9.9.595.1.5.2.1.12
cgdAnswerRate4Hrro
Gauge32 UNITS "hits per second"
.1.3.6.1.4.1.9.9.595.1.5.2.1.13
cgdAnswerStorageTyperw
StorageType (SNMPv2-TC)
.1.3.6.1.4.1.9.9.595.1.5.2.1.14
cgdAnswerRowStatusrw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.9.9.595.1.5.2.1.15
cgdDomain
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.595.1.6
cgdDomainListTable
SEQUENCE OF CgdDomainListEntry
.1.3.6.1.4.1.9.9.595.1.6.1
cgdDomainListEntry
CgdDomainListEntry
.1.3.6.1.4.1.9.9.595.1.6.1.1
cgdDomainListName
SnmpAdminString
.1.3.6.1.4.1.9.9.595.1.6.1.1.1
cgdDomainListHitsro
Counter32 UNITS "number of hits"
.1.3.6.1.4.1.9.9.595.1.6.1.1.2
cgdDomainListStorageTyperw
StorageType (SNMPv2-TC)
.1.3.6.1.4.1.9.9.595.1.6.1.1.3
cgdDomainListRowStatusrw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.9.9.595.1.6.1.1.4
cgdDomainTable
SEQUENCE OF CgdDomainEntry
.1.3.6.1.4.1.9.9.595.1.6.2
cgdDomainEntry
CgdDomainEntry
.1.3.6.1.4.1.9.9.595.1.6.2.1
cgdDomainId
Unsigned32 (1..4294967295 )
.1.3.6.1.4.1.9.9.595.1.6.2.1.1
cgdDomainNamerw
InetAddressDNS (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.595.1.6.2.1.2
cgdDomainListrw
SnmpAdminString
.1.3.6.1.4.1.9.9.595.1.6.2.1.3
cgdDomainHitsro
Counter32 UNITS "number of hits"
.1.3.6.1.4.1.9.9.595.1.6.2.1.4
cgdDomainRate1Minro
Gauge32 UNITS "hits per second"
.1.3.6.1.4.1.9.9.595.1.6.2.1.5
cgdDomainRate5Minro
Gauge32 UNITS "hits per second"
.1.3.6.1.4.1.9.9.595.1.6.2.1.6
cgdDomainRate30Minro
Gauge32 UNITS "hits per second"
.1.3.6.1.4.1.9.9.595.1.6.2.1.7
cgdDomainRate4Hrro
Gauge32 UNITS "hits per second"
.1.3.6.1.4.1.9.9.595.1.6.2.1.8
cgdDomainStorageTyperw
StorageType (SNMPv2-TC)
.1.3.6.1.4.1.9.9.595.1.6.2.1.9
cgdDomainRowStatusrw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.9.9.595.1.6.2.1.10
cgdSourceAdd
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.595.1.7
cgdSourceAddressListTable
SEQUENCE OF CgdSourceAddressListEntry
.1.3.6.1.4.1.9.9.595.1.7.1
cgdSourceAddressListEntry
CgdSourceAddressListEntry
.1.3.6.1.4.1.9.9.595.1.7.1.1
cgdSourceAddressListName
SnmpAdminString
.1.3.6.1.4.1.9.9.595.1.7.1.1.1
cgdSourceAddressListHitsro
Counter32 UNITS "number of hits"
.1.3.6.1.4.1.9.9.595.1.7.1.1.2
cgdSourceAddressListStorageTyperw
StorageType (SNMPv2-TC)
.1.3.6.1.4.1.9.9.595.1.7.1.1.3
cgdSourceAddressListRowStatusrw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.9.9.595.1.7.1.1.4
cgdSourceAddressTable
SEQUENCE OF CgdSourceAddressEntry
.1.3.6.1.4.1.9.9.595.1.7.2
cgdSourceAddressEntry
CgdSourceAddressEntry
.1.3.6.1.4.1.9.9.595.1.7.2.1
cgdSourceAddressId
Unsigned32 (1..4294967295 )
.1.3.6.1.4.1.9.9.595.1.7.2.1.1
cgdSourceAddressAddressTypero
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.595.1.7.2.1.2
cgdSourceAddressAddressro
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.595.1.7.2.1.3
cgdSourceAddressPrefixLengthro
InetAddressPrefixLength (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.595.1.7.2.1.4
cgdSourceAddressListrw
SnmpAdminString
.1.3.6.1.4.1.9.9.595.1.7.2.1.5
cgdSourceAddressHitsro
Counter32 UNITS "number of hits"
.1.3.6.1.4.1.9.9.595.1.7.2.1.6
cgdSourceAddressRate1Minro
Gauge32 UNITS "hits per second"
.1.3.6.1.4.1.9.9.595.1.7.2.1.7
cgdSourceAddressRate5Minro
Gauge32 UNITS "hits per second"
.1.3.6.1.4.1.9.9.595.1.7.2.1.8
cgdSourceAddressRate30Minro
Gauge32 UNITS "hits per second"
.1.3.6.1.4.1.9.9.595.1.7.2.1.9
cgdSourceAddressRate4Hrro
Gauge32 UNITS "hits per second"
.1.3.6.1.4.1.9.9.595.1.7.2.1.10
Showing 100 of 126 OID objects

CISCO-GSLB-DNS-MIB Technical Reference Overview

The CISCO-GSLB-DNS-MIB SNMP MIB module published by Cisco defines 126 managed OID objects, including 94 scalar/column metrics, 8 SNMP tables, and 2 trap/notification events anchored at base OID .1.3.6.1.4.1.9.9.595. Key tabular structures include cgdAnswerGroupTable, cgdAnswerTable, cgdDomainListTable, cgdDomainTable, cgdSourceAddressListTable, cgdSourceAddressTable. Monitored SNMP traps/notifications include ciscoGslbDnsEventClause, ciscoGslbAnswerEventStatusChange.

Key OID Definitions in CISCO-GSLB-DNS-MIB

ciscoGslbDnsMIBMODULE-IDENTITYnot-accessible
.1.3.6.1.4.1.9.9.595

The MIB defines objects for status and statistics information of DNS related operations of Global Server Load Balancer(GSLB). The MIB defines objects for global statistical information like DNS queries received, DNS responses sent, etc. Further it defines objects for answer, answer group, domain list, source address list, proximity rule and DNS rule statistics. It also defines related notifications. Acronyms and terminology: DNS : Domain Name System (RFC1035) D-proxy : Local DNS name server of the client. 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 server load balancer device, 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 Agent (CRA) : A device which uses a resolution process called DNS race to send identical and simultaneous responses back to a client D-proxy for proximity determination. Answer group : A logical grouping of answers. It is a set of virtual IP address (VIP), name server (NS), or content routing agent (CRA) addresses from which an individual answer is selected and used to reply to a content request. Answers are grouped together as resource pools. The GSLB device, using one of a number of available balance methods, can choose the most appropriate resource to serve each user request from the answers in an answer group. Balance method : A balance method is an algorithm for selecting the best server for replying to a DNS query. Domain list : A collection of domain names for Internet or intranet resources that have been delegated to the GSLB device for DNS query responses. Domain lists either contain complete domain names or regular expression that specifies a pattern by which the GSLB device matches incoming DNS requests. Source address list : A collection of IP addresses or address blocks meant to hold information about known D-proxies. This information is used by the GSLB device while answering DNS queries. DNS rule : A rule which controls the operation of GSLB device. It identifies the actions to be performed by the GSLB device when it receives a DNS request from a known source (a member of a source address list) for a known domain (a member of a domain list) by specifying which response (answer) is to be given to the requesting D-proxy and how that answer is chosen. Proximity : Refers to the distance or delay, in terms of network topology and not geographic distance, between the requesting client D-proxy and the resources corresponding to that request. Proximity probing : To respond to DNS requests with the most proximate answers, the GSLB device communicates with a probing device located in each proximity zone to gather round-trip time (RTT) metric information measured between the requesting client D-proxy and the zone. The GSLB device then directs client requests to an available resource with the lowest RTT value. Proximity subsystem : Component within the GSLB device responsible for proximity determination. Clause : A clause specifies that a particular answer group serve the request and a specific balance method be used to select the best resource from that answer group. Boomerang server : A method of proximity routing used by GSLB device with CRAs. It is also known as DNS race. The boomerang method is based on the concept that instantaneous proximity can be determined if a CRA within each data center sends a DNS A-record (IP address) at the exact same time to the requesting D-proxy. This gives all CRAs a chance at resolving a client request and allows for proximity to be determined without probing the client D-proxy. Whichever DNS A-record is received first by the D-proxy is, by default, considered to be the most proximate. For the GSLB device to initiate a DNS race, it needs to establish the following two pieces of information for each CRA: (a) The delay between the GSLB device and each of the CRAs in each data center. With this data, the GSLB device computes how long to delay the race from each data center, so that each CRA starts the race simultaneously. (b) The online status of the CRAs. With this data, the GSLB device knows not to forward requests to any CRA that is not responding. The boomerang server on the GSLB device gathers this information by sending keepalive messages at predetermined intervals. The boomerang server uses this data, along with the IP addresses of the CRAs, to request the exact start time of the DNS race. If the CRA response is to be accepted by the D-proxy, each CRA must spoof the IP address of the GSLB device to which the original DNS request was sent.

cgdAnswerGroupTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.595.1.5.1

This table is used to configure answer groups. This table consists a list of answer groups that are configured and the number of hits on that answer.

cgdAnswerTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.595.1.5.2

This table is used to configure the answers. This table contains the configurable parameters for an answer as well as the statistics for each answer.

cgdDomainListTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.595.1.6.1

This table is used to create domain lists. This table consists the domain lists configured and its associated hits.

cgdDomainTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.595.1.6.2

This table is used to configure domain entries. This table consists the domain names and its association to the domain lists.

cgdSourceAddressListTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.595.1.7.1

This table is used to configure source address lists. This table consists the source address lists configured and their statistics.

cgdSourceAddressTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.595.1.7.2

This table is used to configure source addresses on the GSLB device. It consists of the source addresses configured and its statistics.

cgdClauseTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.595.1.8.1

This table is used to configure the clauses. This table contains entries for each clause configured and their statistics.

cgdDnsRuleTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.595.1.8.2

This table is used to configure DNS rule. This table consists the DNS rules configured and also the statistics for each rule.

ciscoGslbDnsEventClauseNOTIFICATION-TYPEnot-accessible
.1.3.6.1.4.1.9.9.595.0.1

This notification is sent when transition occurs from use of one clause to another for selecting an answer on a DNS rule match. For example a transition is said to have occured, when a DNS rule uses a clause identified by cgdSecondClauseId instead of cgdFirstClauseId. -cgdFirstClauseId contains the clause number used for selecting the most recent answer for a DNS rule. -cgdSecondClauseId contains the clause number that was previously used to select an answer for the DNS rule.

ciscoGslbAnswerEventStatusChangeNOTIFICATION-TYPEnot-accessible
.1.3.6.1.4.1.9.9.595.0.2

This notification is sent when the value of cgdAnswerStatus changes from one state to another.

cgdTotalDomainsUnsigned32read-only
.1.3.6.1.4.1.9.9.595.1.3.1

This object specifies the total number of domains configured. The value of this object corresponds to the number of entries in the cgdDomainTable.

cgdTotalDomainListsUnsigned32read-only
.1.3.6.1.4.1.9.9.595.1.3.2

This object specifies the total number of domain lists configured. The value of this object corresponds to the number of entries in the cgdDomainListTable.

cgdTotalSourceAddressesUnsigned32read-only
.1.3.6.1.4.1.9.9.595.1.3.3

This object specifies the total number of source addresses configured. The value of this object corresponds to the number of entries in the cgdSourceAddressTable.

cgdTotalSourceAddressListsUnsigned32read-only
.1.3.6.1.4.1.9.9.595.1.3.4

This object specifies the total number of source address lists configured. The value of this object corresponds to the number of entries in the cgdSourceAddressListTable.

cgdTotalAnswersUnsigned32read-only
.1.3.6.1.4.1.9.9.595.1.3.5

This object specifies the total number of answers configured. The value of this object corresponds to the number of entries in the cgdAnswerTable.

cgdTotalAnswerGroupsUnsigned32read-only
.1.3.6.1.4.1.9.9.595.1.3.6

This object specifies the total number of answer groups configured. The value of this object corresponds to the number of entries in the cgdAnswerGroupTable.

cgdTotalRulesUnsigned32read-only
.1.3.6.1.4.1.9.9.595.1.3.7

This object specifies the total number of DNS rules configured. The value of this object corresponds to the number of entries in the cgdDnsRuleTable.

cgdAnsTrapRateLimitUnsigned32read-only
.1.3.6.1.4.1.9.9.595.1.3.8

This object specifies the maximum rate at which the ciscoGslbAnswerEventStatusChange notifications can be sent.

cgdDnsClauseTrapRateLimitUnsigned32read-only
.1.3.6.1.4.1.9.9.595.1.3.9

This object specifies the maximum rate at which the ciscoGslbDnsEventClause notifications can be sent.

cgdDnsRcvdQueriesCounter32read-only
.1.3.6.1.4.1.9.9.595.1.4.1

This object specifies the number of DNS queries received.

cgdDnsRcvdHostAddrQueriesCounter32read-only
.1.3.6.1.4.1.9.9.595.1.4.2

This object specifies the number of DNS queries with QTYPE value 1(A) or 255(*) received.

cgdDnsUnmatchedQueriesCounter32read-only
.1.3.6.1.4.1.9.9.595.1.4.3

This object specifies the number of DNS queries received for which no answer could be found.

cgdDnsDroppedQueriesCounter32read-only
.1.3.6.1.4.1.9.9.595.1.4.4

This object specifies the number of DNS queries dropped.

More MIBs from Cisco

Browse all CiscoMIBs →
CISCO-UNIFIED-COMPUTING-COMPUTE-MIB

The CISCO-UNIFIED-COMPUTING-COMPUTE-MIB provides SNMP-based monitoring and management of Cisco UCS compute blades, servers, and chassis components, exposing critical metrics such as CPU utilization, memory usage, thermal sensor readings, power supply status, and interface operational states. This module enables granular visibility into the health and performance of the Cisco Unified Computing System's compute subsystems for capacity planning and fault isolation.

1401 objects→
CISCO-UNIFIED-COMPUTING-STORAGE-MIB

The CISCO-UNIFIED-COMPUTING-STORAGE-MIB facilitates SNMP-based monitoring and management of storage subsystems, including Fibre Channel and iSCSI interfaces, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers. It exposes critical operational metrics such as port status, error counters, throughput statistics, and storage controller health states to enable granular visibility into the storage infrastructure.

1295 objects→
CISCO-UNIFIED-COMPUTING-VNIC-MIB

The CISCO-UNIFIED-COMPUTING-VNIC-MIB enables SNMP-based monitoring and management of Virtual Network Interface Card (vNIC) attributes, including operational status, traffic counters, and binding configurations, within the Cisco Unified Computing System (UCS) fabric interconnects and server blades.

1161 objects→
CERENT-GENERIC-MIB

SNMP MIB module

984 objects→
CISCO-UNIFIED-COMPUTING-BIOS-MIB

The CISCO-UNIFIED-COMPUTING-BIOS-MIB enables SNMP-based monitoring and configuration of BIOS-level parameters, firmware versions, and hardware initialization states within Cisco Unified Computing System (UCS) servers. It provides visibility into critical server boot diagnostics, BIOS settings, and hardware readiness indicators to facilitate low-level infrastructure management and troubleshooting.

937 objects→
CISCO-UNIFIED-COMPUTING-ETHER-MIB

The CISCO-UNIFIED-COMPUTING-ETHER-MIB provides SNMP management interfaces for monitoring Ethernet interface statistics, link states, and error counters on Cisco Unified Computing System (UCS) fabric interconnects and blade server line cards. This module enables the tracking of physical layer connectivity, port throughput, and packet error rates within the UCS Ethernet switching infrastructure.

920 objects→