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.
Parsed from file CISCO-GSLB-DNS-MIB.mib
Module: CISCO-GSLB-DNS-MIB
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.
Parsed from file CISCO-GSLB-DNS-MIB.my.txt
Company: None
Module: CISCO-GSLB-DNS-MIB
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.
ciscoGslbDnsMIB 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 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." REVISION "200704090000Z" DESCRIPTION "-Added the following objects to cgdGlobal: cgdAnsTrapRateLimit cgdDnsClauseTrapRateLimit -Added the following objects to cgdGlobalStats: cgdDroppedAnsNotifs cgdDroppedDnsClauseNotifs -Added the following groups: ciscoGslbDnsGlobalRateLimitGroup, ciscoGslbDnsGlobalNotifStatsGroup" REVISION "200611280000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 595 }
ciscoGslbDnsMIB OBJECT IDENTIFIER ::= { ciscoMgmt 595 }
Vendor: Cisco
Module: CISCO-GSLB-DNS-MIB
[Automatically extracted from oidview.com]
ciscoGslbDnsMIB 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 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." REVISION "200704090000Z" DESCRIPTION "-Added the following objects to cgdGlobal: cgdAnsTrapRateLimit cgdDnsClauseTrapRateLimit -Added the following objects to cgdGlobalStats: cgdDroppedAnsNotifs cgdDroppedDnsClauseNotifs -Added the following groups: ciscoGslbDnsGlobalRateLimitGroup, ciscoGslbDnsGlobalNotifStatsGroup" REVISION "200611280000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 595 }
ciscoGslbDnsMIB 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 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." REVISION "200704090000Z" DESCRIPTION "-Added the following objects to cgdGlobal: cgdAnsTrapRateLimit cgdDnsClauseTrapRateLimit -Added the following objects to cgdGlobalStats: cgdDroppedAnsNotifs cgdDroppedDnsClauseNotifs -Added the following groups: ciscoGslbDnsGlobalRateLimitGroup, ciscoGslbDnsGlobalNotifStatsGroup" REVISION "200611280000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 595 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.595.0 | ciscoGslbDnsMIBNotifs | 2 | 2 | None |
| 1.3.6.1.4.1.9.9.595.1 | ciscoGslbDnsMIBObjects | 8 | 146 | None |
| 1.3.6.1.4.1.9.9.595.2 | ciscoGslbDnsMIBConform | 2 | 14 | 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.548 | ciscoErrDisableMIB | 3 | 43 | This MIB module provides the ability for a Network Management Station (NMS) to configure and monitor the error-disable feature vi… |
| 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.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.600 | ciscoGslbHealthMonMIB | 3 | 90 | The MIB defines objects related to global keepalive properties in GSLB devices. It contains the tables for keep alive configurat… |
| 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… |
| ... | ||||