Cisco Cisco ASR 5500 Guida Alla Risoluzione Dei Problemi
Troubleshoot Infrastructure Client DNS on ASR
5000/5500
5000/5500
Document ID: 119178
Contributed by Dave Damerjian, Cisco TAC Engineer.
Jul 22, 2015
Jul 22, 2015
Contents
Introduction
Configuration
UDP vs. TCP
Troubleshooting Commands
show dns−client statistics client <DNS Client Name>
show dns−client cache client <client name> [query−name <query−name>
[query−type <NAPTR | AAAA | A>] | [query−type <NAPTR | AAAA | A>]]
dns−client query client−name <client name> query−type <NAPTR | AAAA> [query−name <query name>]
Monitor Protocol (Option for DNS)
Logs
Packet Capture
Troubleshoot DNS as it Relates to Call Control
show hsgw−service statistics
Monitor Subscriber
Logs
Related Information
Configuration
UDP vs. TCP
Troubleshooting Commands
show dns−client statistics client <DNS Client Name>
show dns−client cache client <client name> [query−name <query−name>
[query−type <NAPTR | AAAA | A>] | [query−type <NAPTR | AAAA | A>]]
dns−client query client−name <client name> query−type <NAPTR | AAAA> [query−name <query name>]
Monitor Protocol (Option for DNS)
Logs
Packet Capture
Troubleshoot DNS as it Relates to Call Control
show hsgw−service statistics
Monitor Subscriber
Logs
Related Information
Introduction
This document describes how to troubleshoot issues related to Domain Name Service (DNS) infrastructure.
This includes the various command line interfaces (CLI), DNS concepts, and additional data that possibly
needs to be collected. Example output is provided as needed in order to better explain certain points.
This includes the various command line interfaces (CLI), DNS concepts, and additional data that possibly
needs to be collected. Example output is provided as needed in order to better explain certain points.
Infrastructure DNS on Cisco Aggregation Services Router (ASR) 5000 / 5500 is responsible for the resolution
of Fully Qualified Domain Names (FQDN) within the context where it is configured. This is usually in order
to support various aspects of call control in the ingress context. Examples of this include:
of Fully Qualified Domain Names (FQDN) within the context where it is configured. This is usually in order
to support various aspects of call control in the ingress context. Examples of this include:
The resolution of any Diameter endpoint peers that are in FQDN format instead of IP address
•
The resolution of Proxy Call Session Control Function (P−CSCF) FQDNs returned in Diameter S6b
responses which are needed by the User Equipment (UE) in order to register with the IP Multimedia
System (IIMS) core
responses which are needed by the User Equipment (UE) in order to register with the IP Multimedia
System (IIMS) core
•
High Rate Packet Data Serving Gateway (HSGW) needs to make DNS Named Application Naming
Authority Pointer (NAPTR) queries in order to get a list of Packet Data Network Gateways (PGW) to
connect to (either new or handoff) and then make DNS AAAA queries in order to retrieve the IP
address of the PGW Local Mobility Anchor (LMA) address in order to connect the call.
Authority Pointer (NAPTR) queries in order to get a list of Packet Data Network Gateways (PGW) to
connect to (either new or handoff) and then make DNS AAAA queries in order to retrieve the IP
address of the PGW Local Mobility Anchor (LMA) address in order to connect the call.
•
Mobility Management Entity (MME) needs to make DNS NAPTR queries in order to get a list of
Serving Gateways (SGW) / PGW pairs to which to connect with. This includes the creation of DNS
AAAA/A queries in order to retrieve the IPs of those nodes.
Serving Gateways (SGW) / PGW pairs to which to connect with. This includes the creation of DNS
AAAA/A queries in order to retrieve the IPs of those nodes.
•