PGW and SGW Selection by MME Mechanism on the ASR
|
|
- Judith Baldwin
- 7 years ago
- Views:
Transcription
1 PGW and SGW Selection by MME Mechanism on the ASR Document ID: Contributed by Krishna Kishore DV, Cisco TAC Engineer. Jun 18, 2015 Contents Introduction Resource Records A and AAAA NAPTR SRV PGW Selection APN FQDN APN Lookup for Simple LTE (PGW Candidate List) SGW Selection TAI FQDN TAI Lookup for Simple LTE (SGW Candidate List) ASR5x00 Configurations S5/S8 Protocol DNS CC Profile MME Service Sample DNS Client Configuration GW Selection Criteria Additional Configurations Useful Troubleshooting Commands Related Information Introduction This document describes the way in which the Mobility Management Entity (MME) mechanism is used in order to select Packet Gateways (PGWs) and Serving Gateway (SGWs), and how it is implemented on the Cisco 5x00 Series Aggregated Service Router (ASR5x00). Resource Records This section describes the various resource records that are used by the MME. A and AAAA The A resource record is used in order to define the Internet Protocol Version 4 (IPv4) host addresses that correspond to the Fully Qualified Domain Name (FQDN) of the host. The AAAA resource record is used in order to define the Internet Protocol Version 6 (IPv6) host addresses that correspond to the FQDN of the host. Here is an example:
2 example.example.com 1500 IN A NAPTR The Name Authority Pointer (NAPTR) resource record and is a powerful tool that allows Domain Name System (DNS) to be used in order to look up services for a wide variety of resource names that are not in the Domain Name (DN) syntax. The Straightforward NAPTR (S NAPTR) procedure is used for the resolution of a DN, application service name, or application protocol dynamically in order to target the server and port via both NAPTR and Service (SRV). Here is an example: starent.apn.epc.mnc012.mcc345.3gpp.org order pref flags 2000 IN NAPTR "s" "SGW:PMIP" ( ; service "" ; regexp pmip.example.com. ; replacement ) SRV The SRV resource record uses a pool of servers for a single domain with static load balancing to each server in order to move services from host to host and in order to designate some hosts as primary servers for a service from a pool of hosts. Here is an example: pmip.example.com Pref Weight Port Target 1500 IN SRV example.example.com. PGW Selection This image illustrates the PGW selection by the MME for the initial Attach message and the additional Public Data Network (PDN) connection:
3 During the initial Attach and PDN connection creation with 3rd Generation Partnership Project (3GPP) access, both a PGW and an SGW must be selected by the MME. The service parameter that is used in the S NAPTR procedure for the PGW is either x 3gpp pgw:x s5 gtp or x 3gpp pgw:x s5 pmip. You must provision the authoritative DNS server that is responsible for the apn.epc.mnc<mnc>.mcc<mcc>.3gppnetwork.org domain with NAPTR records for each Access Point Name FQDN (APN FQDN) value in the network. The NAPTR records are formed from these service parameters and all of the S5/S8 interfaces: x 3gpp pgw:x s8 gtp x 3gpp pgw:x s8 pmip x 3gpp pgw:x s5 gtp x 3gpp pgw:x s5 pmip The APN FQDN is used in DNS queries by the MME and is derived from an APN. The DNS and S NAPTR procedures logically output a list of host names that are each coupled with a service, a protocol, a port, and a list of IPv4 and/or IPv6 addresses. This is the candidate list of the PGWs for a specific APN. This candidate list is passed through the selection logic in order to choose a specific PGW. The selection logic can use parameters such as: Load (locally deduced) Order, preference, and weight (DNS provided) Collocation with the SGW (learned from DNS responses) Topological closeness Note: Once the PGW has successfully been contacted, the selected PGW host name, the used PGW IP address, the port number, and the selected protocol type is stored in the MME per PDN. APN FQDN The APN is received by the Evolved Packet Core (EPC) node discovery function for 3GPP accesses and has two parts: the APN Network Identifier (NI) and the APN Operator Identifier (OI).
4 Here is an example: APN NI <APN NI> APN OI mnc<mnc>.mcc<mcc> The APN FQDN is obtained from the APN via insertion of the label apn.epc. between the APN NI and the default APN OI, and via a replacement of the label.gprs at the end of the default APN OI with the labels.3gppnetwork.org. For example, with an APN of internet.mnc015.mcc234.gprs, the derived APN FQDN is internet.apn.epc.mnc015.mcc234.3gppnetwork.org. This format is used by the MME in DNS queries to networks with DNS provisioned to Release 8. The DNS records that are provisioned at this location are NAPTR records and include all of the S5/S8 interfaces for PGW and the collocated PGWs/SGWs that are intended to be used for that APN. There are exactly three labels, and the last label is gprs. The APN is transformed to the APN FQDN format, as described in the sub clause of the 3GPP Technical Specifications (TS) [2]: If the APN has the last three labels matching the pattern "mnc<mnc>.mcc<mcc>.gprs", where <MNC> and <MNC> are each composed of 3 decimal digits, then the last 3 labels of the APN shall be replaced by "apn.epc.mnc<mnc>.mcc<mcc>.3gppnetwork.org" to form the APN FQDN. Else if the User Equipment(UE)/Mobile Station(MS) is in the home network and the APN string has as last label "gprs", then last label "gprs" in the APN string shall be replaced by "apn.epc.mnc<mnc>.mcc<mcc>.3gppnetwork.org" to form the APN FQDN where the Mobile Network Code(MNC) and Mobile Country Code(MCC) values are the values of the home network. This use case occurs if the Home Public Land Mobile Network(HPLMN) OI 1 (derived from the APN OI Replacement field in the subscriber's profile) does not conform to the pattern "mnc<mnc>.mcc<mcc>.gprs". Otherwise the APN is invalid and cannot be used for a Release 8 APN usage. APN Lookup for Simple LTE (PGW Candidate List) Here is an example of an APN lookup for a simple Long Term Evolution (LTE) scenario from TS : Assume a non roaming LTE UE indicates it want to use APN NI string "imstv2" to the MME in our example network at initial attach. NOTE 1: Reminder $ORIGIN is epc.mnc990.mcc311.3gppnetwork.org. and is employed here simply to keep the length of the example text manageable The MME starts the S NAPTR procedure with Application Unique String = imstv2.apn.$origin and desired services x 3gpp pgw:x s5 gtp and x 3gpp pgw:x s5 pmip. MME starts with Application Unique String = imstv2.apn.$origin and the desired services x 3gpp pgw:x s5 gtp and x 3gpp pgw:x s5 pmip Command to DNS server ## +tcp NAPTR imstv2.apn.$origin
5 Start Response from DNS server ;; QUESTION SECTION: ;imstv2.apn.$origin. IN NAPTR ;; ANSWER SECTION: imstv2.apn.$origin IN NAPTR "a" "x 3gpp pgw:x s8 pmip" "" topoff.vip2.gw01.node.$origin. imstv2.apn.$origin IN NAPTR "a" "x 3gpp pgw:x s5 gtp:x s8 gtp" "" topoff.vip1.gw21.node.$origin. imstv2.apn.$origin IN NAPTR "a" "x 3gpp pgw:x s5 gtp:x s8 gtp" "" topoff.vip1.gw01.node.$origin. imstv2.apn.$origin IN NAPTR "a" "x 3gpp pgw:x s8 pmip" "" topoff.vip2.gw21.node.$origin. End Response from DNS server MME retains only NAPTR records with matching services x 3gpp pgw:x s5 gtp and x 3gpp pgw:x s5 pmip yielding: NAPTR record set replacement service flag order preference topoff.vip1.gw21.node.$origin x 3gpp pgw:x s5 gtp:x s8 gtp "a" topoff.vip1.gw01.node.$origin x 3gpp pgw:x s5 gtp:x s8 gtp "a" MME node sorts NAPTR by RFC 3958 yielding NAPTR record set replacement service flag order preference topoff.vip1.gw21.node.$origin x 3gpp pgw:x s5 gtp:x s8 gtp "a" topoff.vip1.gw01.node.$origin x 3gpp pgw:x s5 gtp:x s8 gtp "a" MME Stores records since they are flag "a" topoff.vip1.gw21.node.$origin services of x 3gpp pgw:x s5 gtp topoff.vip1.gw01.node.$origin services of x 3gpp pgw:x s5 gtp MME now has final candidate list (A and AAAA lookup is deferred for our hand example) topoff.vip1.gw21.node.$origin services of x 3gpp pgw:x s5 gtp topoff.vip1.gw01.node.$origin services of x 3gpp pgw:x s5 gtp The needed A/AAAA records were included with additional records. I.e. topoff.vip1.gw21.node.$origin IN A topoff.vip1.gw21.node.$origin IN A topoff.vip1.gw21.node.$origin IN AAAA 2001:db8:0:e::
6 topoff.vip1.gw21.node.$origin IN AAAA 2001:db8:0:f:: and topoff.vip1.gw01.node.$origin IN A topoff.vip1.gw01.node.$origin IN A topoff.vip1.gw01.node.$origin IN AAAA 2001:db8:0:c:: topoff.vip1.gw01.node.$origin IN AAAA 2001:db8:0:d:: IF the A and AAAA records were not available in the Additional Record section (or a DNS cache) the MME would do the A/AAAA lookups. Which emulating with manual commands would look like: +tcp A topoff.vip1.gw21.node.$origin +tcp AAAA topoff.vip1.gw21.node.$origin +tcp A topoff.vip1.gw01.node.$origin +tcp AAAA topoff.vip1.gw01.node.$origin We can form the full candidate list now (after random shuffling the A and AAAA records) to get (topoff.vip1.gw21.node.$origin,services of x 3gpp pgw:x s5 gtp, { , }, { 2001:db8:0:e::,2001:db8:0:f::} ) (topoff.vip1.gw01.node.$origin,services of x 3gpp pgw:x s5 gtp, { , }, { 2001:db8:0:c::, 2001:db8:0:d::) SGW Selection The SGW selection function selects an available SGW to serve a UE. The selection is based on the network topology. The selected SGW serves the UE location, and when there are SGW service areas that overlap, the selection might prefer the SGWs with service areas that reduce the probability of an SGW change. The SGW selection uses the Tracking Area Identity (TAI), which provides information about the location of the UE attachment to the Radio Access Network (RAN). You should provision the authoritative DNS server that is responsible for the NAPTR records under the Tracking Area Identity FQDN (TAI FQDN) for each TAI value in the network. The NAPTR records are formed from these service parameters and all of the S5/S8 interfaces: x 3gpp sgw:x s8 gtp x 3gpp sgw:x s8 pmip x 3gpp sgw:x s5 gtp x 3gpp sgw:x s5 pmip The TAI FQDN is used in DNS queries by the MME. The S NAPTR procedures, described in later sections, logically outputs a list of host names, each of which are coupled with a service, a protocol, a port, and a list of IPv4 and/or IPv6 addresses. This is the candidate list of SGWs for a specific APN. This candidate list is passed through the selection logic in order to choose a specific SGW. The selection logic can use parameters
7 such as: TAI coverage Load (locally deduced) Order, preference, and weight (DNS provided) Collocation with PGW (learned from DNS responses) Topology (PGW Node name) TAI FQDN The MME constructs the TAI FQDN as defined in sub clause of the 3GPP TS The TAI FQDN is constructed in this format: tac lb<tac low byte>.tac hb<tac high byte>.tac.epc.mnc<mnc>.mcc<mcc>. 3gppnetwork.org The Tracking Area Code (TAC) is a 16 bit integer. The <TAC high byte> is the hexadecimal string of the most significant byte in the TAC, and the <TAC low byte> is the hexadecimal string of the least significant byte. TAI Lookup for Simple LTE (SGW Candidate List) Here is an example of the TAI lookup for a Simple LTE scenario from TS : Assume a non roaming LTE UE performs and initial attach and indicates it want to use a APN NI (an APN in this operator's network). The MME knows it does not need to use S8 since it is a non roaming UE and must be local APN so S5 is used. NOTE 1: Reminder $ORIGIN is epc.mnc990.mcc311.3gppnetwork.org. and is employed here simply to keep the length of the example text manageable. The MME has the TAI value where the UE has attached. We assume the low byte of the TAC is hex 11 and the high byte is hex 40. The MME starts the S NAPTR procedure with Application Unique String = tac lb11.tac hb40.tac.$origin and desired services x 3gpp sgw:x s11,x 3gpp sgw:x s5 gtp, x 3gpp sgw:x s5 pmip. NOTE 2: This particular MME vendor looks for the x s11 values, which is only an optional optimization. This will not have any benefit in this example since the operator chose not to provision them. Here we emulate the same action the MME would do manually with the "dig" command. Command to DNS server ## +tcp NAPTR tac lb11.tac hb40.tac.$origin Start Response from DNS server ;; QUESTION SECTION:
8 ;tac lb11.tac hb40.tac.$origin. IN NAPTR ;; ANSWER SECTION: tac lb11.tac hb40.tac.$origin IN NAPTR "a" "x 3gpp sgw:x s8 pmip" "" topoff.eth9.gw01.node.$origin. tac lb11.tac hb40.tac.$origin IN NAPTR "a" "x 3gpp mme:x s10" "" topoff.eth1.mmec02.mmegi8001.mme.$origin. tac lb11.tac hb40.tac.$origin IN NAPTR "a" "x 3gpp mme:x s10" "" topoff.eth1.mmec01.mmegi8001.mme.$origin. tac lb11.tac hb40.tac.$origin IN NAPTR "a" "x 3gpp sgw:x s5 gtp:x s8 gtp" "" topoff.eth4.gw21.node.$origin. tac lb11.tac hb40.tac.$origin IN NAPTR "a" "x 3gpp sgw:x s5 gtp:x s8 gtp" "" topoff.eth4.gw01.node.$origin. tac lb11.tac hb40.tac.$origin IN NAPTR "a" "x 3gpp sgw:x s8 pmip" "" topoff.eth9.gw21.node.$origin. End Response from DNS server MME retains only the NAPTR with matching services x 3gpp sgw:x s11,x 3gpp sgw:x s5 gtp, and x 3gpp sgw:x s5 pmip yielding NAPTR record set replacement service flag order preference topoff.eth4.gw01.node.$origin x 3gpp sgw:x s5 gtp:x s8 gtp "a" topoff.eth4.gw21.node.$origin x 3gpp sgw:x s5 gtp:x s8 gtp "a" Note the x s8 gtp are not really included but are kept here to allow the reader to see which NAPTR record was kept from the DNS response. MME node sorts the NAPTR records by RFC 3958 yielding NAPTR record set replacement service flag order preference topoff.eth4.gw21.node.$origin x 3gpp sgw:x s5 gtp:x s8 gtp "a" topoff.eth4.gw01.node.$origin x 3gpp sgw:x s5 gtp:x s8 gtp "a" MME Stores topoff.eth4.gw21.node.$origin services of x 3gpp sgw:x s5 gtp topoff.eth4.gw01.node.$origin services of x 3gpp sgw:x s5 gtp MME now has candidate list topoff.eth4.gw21.node.$origin services of x 3gpp sgw:x s5 gtp topoff.eth4.gw01.node.$origin services of x 3gpp sgw:x s5 gtp Again the A/AAAA records were available in the additional record section.
9 topoff.eth4.gw21.node.$origin IN A topoff.eth4.gw21.node.$origin IN A topoff.eth4.gw21.node.$origin IN AAAA 2001:db8:0:26:: topoff.eth4.gw21.node.$origin IN AAAA 2001:db8:0:27:: and topoff.eth4.gw01.node.$origin IN A topoff.eth4.gw01.node.$origin IN A topoff.eth4.gw01.node.$origin IN AAAA 2001:db8:0:1e:: topoff.eth4.gw01.node.$origin IN AAAA 2001:db8:0:1f:: From the candidate list that results, an SGW is chosen based on a combination of these criteria: Maximum TA coverage Geographic proximity Load balancing Combined PGW/SGW functionality Protocols that are supported ASR5x00 Configurations This section describes the relevant configurations for the ASR5x00. S5/S8 Protocol The S5 and S8 protocols should be configurable for the MME on a per HPLMN basis. This is used in order to shortlist the resource records that are returned by the DNS server. Only the PGWs that support the configured protocol are considered in the Gateway (GW) selection. The configuration is placed under the Call Control (CC) profile that is associated with the operator policy. Here is an example: [ingress]asr5000(config call control profile lmn)# plmn protocol plmnid mcc <> mnc <> { [s5 protocol <[pmip gtp] >] [s8 protocol <[pmip gtp]>] } DNS The system allows one DNS client service to be configured per context. The DNS client service to be used for the FQDN resolution is named under the CC profile and/or the MME service separately for the PGW and the SGW. In the CC profile, the context name is mandatory, as the CC profile is not attached to any context. In the MME service, the context name is optional. If no name is specified, the context of the MME service is used for the DNS service.
10 CC Profile Here is the relevant configuration for the CC profile: [ctxt]asr5000(config call control profile lmn)# dns pgw context <name> [ctxt]asr5000(config call control profile lmn)# dns sgw context <name> MME Service Here is the relevant configuration for the MME service: [ctxt]asr5000(config mme service)#dns pgw [context <name>] [ctxt]asr5000(config mme service)#dns sgw [context <name>] Sample DNS Client Configuration Here is a sample DNS client configuration on the ASR5x00: #(config ctx)# ip name servers #(config ctx)# dns client xyz bind address port 6011 resolver retransmission interval 3 resolver number of retries 2 cache ttl positive cache ttl negative 60 cache size central cache size local 1000 cache algorithm central FIFO cache algorithm local LRU no round robin answers The DNS resolution procedure for the S/P GW is invoked only when the CLI information that is shown in the previous example is enabled. Otherwise, the static address that is configured in the MME service is used. Additionally, if the DNS resolution fails, then the static address that is configured in the MME service is used. GW Selection Criteria This configuration is placed under the CC profile that is associated with the operator policy. It decides the selection algorithms that are used in order to eventually select a PGW/SGW from the resource records that are returned by the DNS. Only one of the criteria can be configured at a time. Here is an example: [ctxt]asr5000(config call control profile lmn)# gw selection [ topology collocation pgw < weight > sgw <weight> ]
11 Here are some important considerations when collocation is the selection criterion: Collocation should be configured for both the PGW and the SGW selection in order for collocation to function properly. Collocation is given the highest priority. In other words, even if the degree of labels that match between a non collocated PGW/SGW pair might be higher than a collocated pair, the collocated pair is selected. Host names with both topon and topoff labels are considered in collocation. Collocation implicitly means topology match. If a collocated PGW/SGW node cannot be found, then the topologically closest nodes are chosen next. Note: Dependent upon the operator requirements, this approach might change in the future in order to separate the collocation and topology match criteria. Additional Configurations Here are some additional configurations that you must implement on the ASR5x00: context ingress ip domain lookup ip name servers <ip address of the Linux machine (it should be running bind)> dns client dns bind address round robin answers exit mme service <mmesvc> dns pgw dns service dns context ingress dns sgw dns service dns context ingress exit Useful Troubleshooting Commands You can use these commands in order to troubleshoot the MME mechanism: #dns client query client name dns query type NAPTR query name <starent.com.apn.epc.mncxxx.mccxxx.3gppnetwork.org> #show dns client <dns1> statistics #show dns client cache client <> Related Information TS
12 Technical Support & Documentation Cisco Systems Updated: Jun 18, 2015 Document ID:
3GPP TS 29.303 V8.0.0 (2008-12)
TS 29.303 V8.0.0 (2008-12) Technical Specification 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Domain Name System Procedures; Stage 3 (Release 8) The present
More informationETSI TS 129 303 V8.0.0 (2009-01) Technical Specification
TS 129 303 V8.0.0 (2009-01) Technical Specification Universal Mobile Telecommunications System (UMTS); LTE; Domain Name System Procedures (3GPP TS 29.303 version 8.0.0 Release 8) 1 TS 129 303 V8.0.0 (2009-01)
More informationLTE Attach and Default Bearer Setup Messaging
LTE Attach and Default Bearer Setup Messaging 2012 Inc. All Rights Reserved LTE Attach Message Sequence Chart enodeb MME SGW HSS Initial UE Message Update Location Update Location Answer Create Session
More informationDNS Conformance Test Specification For Client
DNS Conformance Test Specification For Client Revision 1.0 Yokogawa Electric Corporation References This test specification focus on following DNS related RFCs. RFC 1034 DOMAIN NAMES - CONCEPTS AND FACILITIES
More informationDomain Name System 2015-04-28 17:49:44 UTC. 2015 Citrix Systems, Inc. All rights reserved. Terms of Use Trademarks Privacy Statement
Domain Name System 2015-04-28 17:49:44 UTC 2015 Citrix Systems, Inc. All rights reserved. Terms of Use Trademarks Privacy Statement Contents Domain Name System... 4 Domain Name System... 5 How DNS Works
More informationConfiguring a Load-Balancing Scheme
Configuring a Load-Balancing Scheme Finding Feature Information Configuring a Load-Balancing Scheme Last Updated: August 15, 2011 This module contains information about Cisco Express Forwarding and describes
More informationDNS SRV Usage June 22, 2011
DNS SRV Usage June 22, 2011 Proprietary 2011 Media5 Corporation Table of Contents Scope of this Document... 3 DNS SRV (RFC 2782)... 3 Deployment Scenario... 4 Mediatrix Unit Configuration... 5 Scenario
More information464XLAT: Breaking Free of IPv4. Cameron.Byrne@T-Mobile.com APRICOT 2014
464XLAT: Breaking Free of IPv4 Cameron.Byrne@T-Mobile.com APRICOT 2014 1 Background T-Mobile US is a GSM / UMTS / LTE provider in the USA with 45+ Million subscribers In 2008, T-Mobile launched the first
More informationNTT DOCOMO Technical Journal. Core Network Infrastructure and Congestion Control Technology for M2M Communications
M2M 3GPP Standardization Further Development of LTE/LTE-Advanced LTE Release 10/11 Standardization Trends Core Network Infrastructure and Congestion Control Technology for M2M Communications The number
More informationUse Domain Name System and IP Version 6
Use Domain Name System and IP Version 6 What You Will Learn The introduction of IP Version 6 (IPv6) into an enterprise environment requires some changes both in the provisioned Domain Name System (DNS)
More informationProcedure: You can find the problem sheet on Drive D: of the lab PCs. 1. IP address for this host computer 2. Subnet mask 3. Default gateway address
Objectives University of Jordan Faculty of Engineering & Technology Computer Engineering Department Computer Networks Laboratory 907528 Lab.4 Basic Network Operation and Troubleshooting 1. To become familiar
More informationKAREL UCAP DNS AND DHCP CONCEPTS MANUAL MADE BY: KAREL ELEKTRONIK SANAYI ve TICARET A.S. Organize Sanayi Gazneliler Caddesi 10
KAREL UCAP DNS AND DHCP CONCEPTS MANUAL MADE BY: KAREL ELEKTRONIK SANAYI ve TICARET A.S. Organize Sanayi Gazneliler Caddesi 10 Sincan 06935 Ankara, Turkey Version Table Manual Version/Date AAA/22.03.2011
More informationImplementing LTE International Data Roaming
Implementing International Data Roaming Data Roaming Standardization Implementing International Data Roaming On completion of EPC standardization at 3GPP, specifications for international roaming between
More informationCisco DNS-AS Troubleshooting
First Published: May 11, 2016 Last Updated: May 17, 2016 Contents Introduction... 3 DNS-AS Troubleshooting Tools... 4 Diagnostic Tool: Verify Customization Interval... 4 Diagnostic Tool: Verify that Traffic
More informationThis guide provides detailed information on how to configure and use server redundancy on Yealink IP phones.
This guide provides detailed information on how to configure and use server redundancy on Yealink IP phones. The information applies to Yealink IP phones running firmware version 71 or later. Server redundancy
More informationHow To - Configure Virtual Host using FQDN How To Configure Virtual Host using FQDN
How To - Configure Virtual Host using FQDN How To Configure Virtual Host using FQDN Applicable Version: 10.6.2 onwards Overview Virtual host implementation is based on the Destination NAT concept. Virtual
More informationSERVICE DISCOVERY AND MOBILITY MANAGEMENT
Objectives: 1) Understanding some popular service discovery protocols 2) Understanding mobility management in WLAN and cellular networks Readings: 1. Fundamentals of Mobile and Pervasive Computing (chapt7)
More informationIntroduction to Network Operating Systems
As mentioned earlier, different layers of the protocol stack use different kinds of addresses. We can now see that the Transport Layer (TCP) uses port addresses to route data to the correct process, the
More informationJoe Davies. Principal Writer Windows Server Information Experience. Presented at: Seattle Windows Networking User Group June 1, 2011
Joe Davies Principal Writer Windows Server Information Experience Presented at: Seattle Windows Networking User Group June 1, 2011 2011 Microsoft Corporation IPv6 addressing and DNS review IPv6 subnetting
More informationTeldat Router. DNS Client
Teldat Router DNS Client Doc. DM723-I Rev. 10.00 March, 2003 INDEX Chapter 1 Domain Name System...1 1. Introduction...2 2. Resolution of domains...3 2.1. Domain names resolver functionality...4 2.2. Functionality
More informationVirtual Evolved Packet Core
Virtual Evolved Packet Core User Manual Note 1: The IP address for the APN interface must to be from the same subnet as the IP pool of the APN. Default GW of the OS should be on the APN subnet (ex. 10.0.31.1).
More information464XLAT: Breaking Free of IPv4. Cameron.Byrne @ T-Mobile.com NANOG 61 June 2014
464XLAT: Breaking Free of IPv4 Cameron.Byrne @ T-Mobile.com NANOG 61 June 2014 1 Goals of Talk 1. Declare victory for IPv6 2. Explain IPv6-only approach at T-Mobile US 3. Discuss risks related to IPv4-only
More informationThis guide provides detailed information on how to configure and use server redundancy on Yealink IP phones.
This guide provides detailed information on how to configure and use server redundancy on Yealink IP phones. The information applies to Yealink SIP-T28P, SIP-T26P, SIP-T22P, SIP-T20P, SIP-T21P, SIP-T19P,
More informationASR 5x00 Series SGSN Authentication and PTMSI Reallocation Best Practices
ASR 5x00 Series SGSN Authentication and PTMSI Reallocation Best Practices Document ID: 119148 Contributed by Krishna Kishore DV, Sujin Anagani, and Parthasarathy M, Cisco TAC Engineers. Jun 12, 2015 Contents
More informationDeploying IPv6 in 3GPP Networks. Evolving Mobile Broadband from 2G to LTE and Beyond. NSN/Nokia Series
Brochure More information from http://www.researchandmarkets.com/reports/2379605/ Deploying IPv6 in 3GPP Networks. Evolving Mobile Broadband from 2G to LTE and Beyond. NSN/Nokia Series Description: Deploying
More informationDiameter in the Evolved Packet Core
Diameter in the Evolved Packet Core A Whitepaper November 2009 Page 2 DIAMETER in the Evolved Packet Core Mobile broadband is becoming a reality, as the Internet generation grows accustomed to having broadband
More informationMobility Management for All-IP Core Network
Mobility Management for All-IP Core Network Mobility Management All-IP Core Network Standardization Special Articles on SAE Standardization Technology Mobility Management for All-IP Core Network PMIPv6
More informationUMTS/GPRS system overview from an IP addressing perspective. David Kessens Jonne Soininen
UMTS/GPRS system overview from an IP addressing perspective David Kessens Jonne Soininen Introduction 1) Introduction to 3GPP networks (GPRS, UMTS) Technical overview and concepts for 3GPP networks Mobility
More informationDNS zone transfers from FreeIPA to non-freeipa slave servers
FreeIPA Training Series DNS zone transfers from FreeIPA to non-freeipa slave servers FreeIPA 3.0 and bind-dyndb-ldap 2.3 Petr Špaček 01-03-2013 Text file based
More informationConfiguration Notes 0215
Mediatrix Digital and Analog VoIP Gateways DNS SRV Configuration for a Redundant Server Solution (SIP) Introduction... 2 Deployment Scenario... 2 DNS SRV (RFC 2782)... 3 Microsoft Server Configuration...
More informationLab - Observing DNS Resolution
Objectives Part 1: Observe the DNS Conversion of a URL to an IP Address Part 2: Observe DNS Lookup Using the nslookup Command on a Web Site Part 3: Observe DNS Lookup Using the nslookup Command on Mail
More informationBehavioral Differences Regarding DNS Queries and Domain Name Resolution in Different OSs
Behavioral Differences Regarding DNS Queries and Domain Name Resolution in Different OSs Document ID: 116016 Contributed by Cisco TAC Engineers. Jan 28, 2014 Contents Introduction Split Versus Standard
More informationDNS Commands ip dns spoofing
DNS Commands ip dns spoofing ip dns spoofing To enable Domain Name System (DNS) spoofing, use the ip dns spoofing command in global configuration mode. To disable DNS spoofing, use the no form of this
More informationDNS (Domain Name System) is the system & protocol that translates domain names to IP addresses.
Lab Exercise DNS Objective DNS (Domain Name System) is the system & protocol that translates domain names to IP addresses. Step 1: Analyse the supplied DNS Trace Here we examine the supplied trace of a
More informationETSI TS 124 303 V8.9.0 (2012-07)
TS 124 303 V8.9.0 (2012-07) Technical Specification Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Mobility management based on Dual-Stack
More informationVoice over IP over LTE (VoLTE) Impacts on LTE access. EFORT http://www.efort.com
1 Introduction Voice over IP over LTE (VoLTE) Impacts on LTE access EFORT http://www.efort.com IMS (IP Multimedia Subsystems) has been around for some time, and many infrastructure vendors have invested
More informationForouzan: Chapter 17. Domain Name System (DNS)
Forouzan: Chapter 17 Domain Name System (DNS) Domain Name System (DNS) Need System to map name to an IP address and vice versa We have used a host file in our Linux laboratory. Not feasible for the entire
More information1 SIP Carriers. 1.1 Tele2. 1.1.1 Warnings. 1.1.2 Vendor Contact. 1.1.3 Versions Verified SIP Carrier status as of Jan 1, 2011. 1.1.
1 SIP Carriers 1.1 Tele2 1.1.1 Warnings Check the SIP 3 rd Party SIP Carrier Matrix for certification status, and supported features. More info about the SIP 3 rd Party SIP Carrier Matrix can be found
More informationLong Term Evolution - LTE. A short overview
Long Term Evolution - LTE A short overview LTE Architecture 2 Conformance Test Suite Specification 3 GPP and ETSI product 3GPP TS 32.523-3 Evolved Universal Terrestrial Radio Access (E-UTRA) User Equipment
More informationMotivation. Domain Name System (DNS) Flat Namespace. Hierarchical Namespace
Motivation Domain Name System (DNS) IP addresses hard to remember Meaningful names easier to use Assign names to IP addresses Name resolution map names to IP addresses when needed Namespace set of all
More informationConfiguring DNS. Finding Feature Information
The Domain Name System (DNS) is a distributed database in which you can map hostnames to IP addresses through the DNS protocol from a DNS server. Each unique IP address can have an associated hostname.
More informationehrpd Mike Keeley Market Segment Director
ehrpd Mike Keeley Market Segment Director Agenda ehrpd What, Why, and When? ehrpd s Impact on the Core Network ehrpd s Impact on the Mobile Device Verifying ehrpd works 2 Acronyms AAA AN BSC EAP- AKA ehrpd
More informationDomain Name System. CS 571 Fall 2006. 2006, Kenneth L. Calvert University of Kentucky, USA All rights reserved
Domain Name System CS 571 Fall 2006 2006, Kenneth L. Calvert University of Kentucky, USA All rights reserved DNS Specifications Domain Names Concepts and Facilities RFC 1034, November 1987 Introduction
More informationNetwork Protocol Configuration
Table of Contents Table of Contents Chapter 1 Configuring IP Addressing... 1 1.1 IP Introduction... 1 1.1.1 IP... 1 1.1.2 IP Routing Protocol... 1 1.2 Configuring IP Address Task List... 2 1.3 Configuring
More informationPort Use and Contention in PlanetLab
Port Use and Contention in PlanetLab Jeff Sedayao Intel Corporation David Mazières Department of Computer Science, NYU PDN 03 016 December 2003 Status: Ongoing Draft. Port Use and Contention in PlanetLab
More informationUSING TRANSACTION SIGNATURES (TSIG) FOR SECURE DNS SERVER COMMUNICATION
USING TRANSACTION SIGNATURES (TSIG) FOR SECURE DNS SERVER COMMUNICATION Transaction Signatures (TSIG) provide a secure method for communicating in the Domain Name System (DNS) from a primary to a secondary
More informationGlobal Server Load Balancing (GSLB) Concepts
Global Server Load Balancing (GSLB) Concepts Section Section Objectives GSLB Overview GSLB Configuration Options GSLB Components Server Mode Configuration 2 Global Server Load Balancing (GSLB) Key ACOS
More informationProtocol Signaling Procedures in LTE
White Paper Protocol Signaling Procedures in LTE By: V. Srinivasa Rao, Senior Architect & Rambabu Gajula, Lead Engineer Overview The exploding growth of the internet and associated services has fueled
More informationCopyright 2013 http://itfreetraining.com
This video will look at two DNS features, DNS round robin and netmask ordering. These features allow for simple load balancing and also provide a method for directing a user to local resources rather than
More informationChapter 3 Configuring Basic IPv6 Connectivity
Chapter 3 Configuring Basic IPv6 Connectivity This chapter explains how to get a ProCurve Routing Switch that supports IPv6 up and running. To configure basic IPv6 connectivity, you must do the following:
More informationAPI of DNS hosting. For DNS-master and Secondary services Table of contents
API of DNS hosting. For DNS-master and Secondary services Table of contents API of DNS hosting. For DNS-master and Secondary services... 1 1. Introduction... 3 2. Setting access area of application for
More informationLTE Control Plane on Intel Architecture
White Paper Soo Jin Tan Platform Solution Architect Siew See Ang Performance Benchmark Engineer Intel Corporation LTE Control Plane on Intel Architecture Using EEMBC CoreMark* to optimize control plane
More informationDomain Name Resolver (DNR) Configuration
CHAPTER 7 Domain Name Resolver (DNR) Configuration This chapter provides an overview of the information required to customize Cisco IOS for S/390. It includes these sections: Introducing the Domain Name
More informationPractical Network Forensics
BCS-ISSG Practical Network Forensics Day BCS, London Practical Network Forensics Alan Woodroffe issg@securesystemssupport.co.uk www.securesystemssupport.co.uk Copyright Secure Systems Support Limited.
More informationNationwide Interoperability Framework
Nationwide Interoperability Framework Emergency Response Interoperability Center (ERIC) Public Safety Homeland Security Bureau Federal Communications Commission PSCR, Boulder, CO Dec 2, 2010 7/9/101 1
More informationPublic Safety Communications Research. LTE Demonstration Network Test Plan. Phase 3 Part 1: Network Interoperability & Drive Test. Version 2.
Public Safety Communications Research LTE Demonstration Network Test Plan Phase 3 Part 1: Network Interoperability & Drive Test Version 2.4 May 7, 2013 1 1 Contents 2 List of Tables... 5 3 List of Figures...
More information100-101: Interconnecting Cisco Networking Devices Part 1 v2.0 (ICND1)
100-101: Interconnecting Cisco Networking Devices Part 1 v2.0 (ICND1) Course Overview This course provides students with the knowledge and skills to implement and support a small switched and routed network.
More informationDynamic DNS Support for Cisco IOS Software
Dynamic DNS Support for Cisco IOS Software First Published: 12.3(8)YA Last Updated: February 28, 2006 The Dynamic DNS Support for Cisco IOS Software feature enables Cisco IOS software devices to perform
More informationNetIQ Advanced Authentication Framework - MacOS Client
NetIQ Advanced Authentication Framework - MacOS Client Installation Guide Version 5.2.0 1 Table of Contents 1 Table of Contents 2 Introduction 3 About This Document 3 About MacOS Client 4 System Requirements
More informationMobile IPv6 deployment opportunities in next generation 3GPP networks. I. Guardini E. Demaria M. La Monaca
Mobile IPv6 deployment opportunities in next generation 3GPP networks I. Guardini E. Demaria M. La Monaca Overview of SAE/LTE Terminology SAE (System Architecture Evolution): core network/system aspects
More informationCisco TelePresence Authenticating Cisco VCS Accounts Using LDAP
Cisco TelePresence Authenticating Cisco VCS Accounts Using LDAP Deployment Guide Cisco VCS X8.1 D14465.06 December 2013 Contents Introduction 3 Process summary 3 LDAP accessible authentication server configuration
More informationIPv6.marceln.org. marcel.nijenhof@proxy.nl
IPv6.marceln.org marcel.nijenhof@proxy.nl RFC 1606 RFC 1606 A Historical Perspective On The Usage Of IP Version 9 1 April 1994, J. Onions Introduction The take-up of the network protocol TCP/IPv9 has been
More informationDHCP and DNS Services
CHAPTER 9 A DHCP server provides network configuration parameters, such as IP addresses, to DHCP clients. The security appliance can provide DHCP server or DHCP relay services to DHCP clients attached
More informationHow to Install and Configure the DHCP Service in Windows Server 2008 R2
How to Install and Configure the DHCP Service in Windows Server 2008 R2 I am not responsible for your actions or their outcomes, in any way, while reading and/or implementing this tutorial. I will not
More informationCourse Overview: Learn the essential skills needed to set up, configure, support, and troubleshoot your TCP/IP-based network.
Course Name: TCP/IP Networking Course Overview: Learn the essential skills needed to set up, configure, support, and troubleshoot your TCP/IP-based network. TCP/IP is the globally accepted group of protocols
More informationThe Domain Name System
Internet Engineering 241-461 Robert Elz kre@munnari.oz.au kre@coe.psu.ac.th http://fivedots.coe.psu.ac.th/~kre DNS The Domain Name System Kurose & Ross: Computer Networking Chapter 2 (2.5) James F. Kurose
More informationSAE and Evolved Packet Core
SAE and Evolved Packet Core Farooq Bari Seattle Communications (COM-19) Society Chapter Nov. 13, 2008 1 SAE/EPS Background Around 2005, 3GPP RAN groups initiated the LTE work and in parallel the SAE work
More informationnetkit lab dns Università degli Studi Roma Tre Dipartimento di Informatica e Automazione Computer Networks Research Group Version Author(s)
Università degli Studi Roma Tre Dipartimento di Informatica e Automazione Computer Networks Research Group netkit lab dns Version Author(s) E-mail Web Description 2.2 G. Di Battista, M. Patrignani, M.
More information7750 SR OS System Management Guide
7750 SR OS System Management Guide Software Version: 7750 SR OS 10.0 R4 July 2012 Document Part Number: 93-0071-09-02 *93-0071-09-02* This document is protected by copyright. Except as specifically permitted
More informationEmerald. Network Collector Version 4.0. Emerald Management Suite IEA Software, Inc.
Emerald Network Collector Version 4.0 Emerald Management Suite IEA Software, Inc. Table Of Contents Purpose... 3 Overview... 3 Modules... 3 Installation... 3 Configuration... 3 Filter Definitions... 4
More informationManaging Users and Identity Stores
CHAPTER 8 Overview ACS manages your network devices and other ACS clients by using the ACS network resource repositories and identity stores. When a host connects to the network through ACS requesting
More informationYou can specify IPv4 and IPv6 addresses while performing various tasks in this feature. The resource
The feature enables the configuration of a Virtual Private Network (VPN) routing and forwarding instance (VRF) table so that the domain name system (DNS) can forward queries to name servers using the VRF
More informationDNS ActiveX Control for Microsoft Windows. Copyright Magneto Software All rights reserved
DNS ActiveX Control for Microsoft Windows Copyright Magneto Software All rights reserved 1 DNS Overview... 3 1.1 Introduction... 3 1.2 Usage... 3 1.3 Property... 4 1.4 Event... 4 1.5 Method... 4 1.6 Error
More informationI. What is VPN? II. Types of VPN connection. There are two types of VPN connection:
Table of Content I. What is VPN?... 2 II. Types of VPN connection... 2 III. Types of VPN Protocol... 3 IV. Remote Access VPN configuration... 4 a. PPTP protocol configuration... 4 Network Topology... 4
More informationDNS ROUND ROBIN HIGH-AVAILABILITY LOAD SHARING
PolyServe High-Availability Server Clustering for E-Business 918 Parker Street Berkeley, California 94710 (510) 665-2929 wwwpolyservecom Number 990903 WHITE PAPER DNS ROUND ROBIN HIGH-AVAILABILITY LOAD
More informationThe Use of DNS Resource Records
International Journal of Advances in Electrical and Electronics Engineering 230 Available online at www.ijaeee.com & www.sestindia.org/volume-ijaeee/ ISSN: 2319-1112 Simar Preet Singh Systems Engineer,
More informationTopic 7 DHCP and NAT. Networking BAsics.
Topic 7 DHCP and NAT Networking BAsics. 1 Dynamic Host Configuration Protocol (DHCP) IP address assignment Default Gateway assignment Network services discovery I just booted. What network is this? What
More informationDNS Resolving using nslookup
DNS Resolving using nslookup Oliver Hohlfeld & Andre Schröder January 8, 2007 Abstract This report belongs to a talk given at the networking course (Institue Eurecom, France) in January 2007. It is based
More informationArchitecture and Data Flow Overview. BlackBerry Enterprise Service 10 721-08877-123 Version: 10.2. Quick Reference
Architecture and Data Flow Overview BlackBerry Enterprise Service 10 721-08877-123 Version: Quick Reference Published: 2013-11-28 SWD-20131128130321045 Contents Key components of BlackBerry Enterprise
More informationConfiguring a Load-Balancing Scheme
This module contains information about Cisco Express Forwarding and describes the tasks for configuring a load-balancing scheme for Cisco Express Forwarding traffic. Load-balancing allows you to optimize
More informationImplementing Intercluster Lookup Service
Appendix 11 Implementing Intercluster Lookup Service Overview When using the Session Initiation Protocol (SIP), it is possible to use the Uniform Resource Identifier (URI) format for addressing an end
More informationReverse DNS considerations for IPv6
Reverse DNS considerations for IPv6 Kostas Zorbadelos OTE David Freedman - ClaraNet Reverse DNS in IPv4 Every Internet-reachable host should have a name Make sure your PTR and A records match. For every
More information7 TRANSMISSION CONTROL PROTOCOL/ INTERNET PROTOCOL (TCP/IP)
7 TRANSMISSION CONTROL PROTOCOL/ INTERNET PROTOCOL (TCP/IP) PROJECTS Project 7.1 Project 7.2 Project 7.3 Project 7.4 Project 7.5 Understanding Key Concepts Configuring TCP/IP Properties Comparing Name
More informationSUBNETTING SCENARIO S
SUBNETTING SCENARIO S This white paper provides several in-depth scenario s dealing with a very confusing topic, subnetting. Many networking engineers need extra practice to completely understand the intricacies
More informationConfiguring NetFlow-lite
CHAPTER 55 Note NetFlow-lite is only supported on Catalyst 4948E Ethernet Switch. This chapter describes how to configure NetFlow-lite on the Catalyst 4948E switch. NetFlow-lite provides traffic monitoring
More informationSample Configuration Using the ip nat outside source list C
Sample Configuration Using the ip nat outside source list C Table of Contents Sample Configuration Using the ip nat outside source list Command...1 Introduction...1 Before You Begin...1 Conventions...1
More informationDeployment Guide A10 Networks/Infoblox Joint DNS64 and NAT64 Solution
Deployment Guide A10 Networks/Infoblox Joint DNS64 and NAT64 Solution DG_ACC_062011.1 TABLE OF CONTENTS 1 Introduction... 3 2 Deployment Guide Overview... 3 3 Lab Setup Requirements... 3 4 Architecture
More informationAccelerating 4G Network Performance
WHITE PAPER Accelerating 4G Network Performance OFFLOADING VIRTUALIZED EPC TRAFFIC ON AN OVS-ENABLED NETRONOME INTELLIGENT SERVER ADAPTER NETRONOME AGILIO INTELLIGENT SERVER ADAPTERS PROVIDE A 5X INCREASE
More informationWeb Application Hosting Cloud Architecture
Web Application Hosting Cloud Architecture Executive Overview This paper describes vendor neutral best practices for hosting web applications using cloud computing. The architectural elements described
More informationQuick Start for Network Agent. 5-Step Quick Start. What is Network Agent?
What is Network Agent? Websense Network Agent software monitors all internet traffic on the machines that you assign to it. Network Agent filters HTTP traffic and more than 70 other popular internet protocols,
More informationIP Addressing and Subnetting. 2002, Cisco Systems, Inc. All rights reserved.
IP Addressing and Subnetting 2002, Cisco Systems, Inc. All rights reserved. 1 Objectives Upon completion, you will be able to: Discuss the Types of Network Addressing Explain the Form of an IP Address
More informationINTRODUCTION OF VOIP AND SIP SECURITY 2
INTRODUCTION OF VOIP AND SIP SECURITY 2 Ge Zhang, Karlstad University May, 2009 Outline Review SIP vulnerabilities by external infrastructures DNS server as an example Confidentiality Integrity Availability
More informationCase Study 2 SPR500 Fall 2009
Case Study 2 SPR500 Fall 2009 6 th November 2009 Due Date: 9 th December 2009 Securing Sotnec's web site using Linux Firewall technology Sotnec corporation, an Open Source Company, consists of a small
More informationNAT TCP SIP ALG Support
The feature allows embedded messages of the Session Initiation Protocol (SIP) passing through a device that is configured with Network Address Translation (NAT) to be translated and encoded back to the
More informationExamPDF. Higher Quality,Better service!
ExamPDF Higher Quality,Better service! Q&A Exam : 1Y0-A21 Title : Basic Administration for Citrix NetScaler 9.2 Version : Demo 1 / 5 1.Scenario: An administrator is working with a Citrix consultant to
More informationTelecommunication Services Engineering (TSE) Lab. Chapter III 4G Long Term Evolution (LTE) and Evolved Packet Core (EPC)
Chapter III 4G Long Term Evolution (LTE) and Evolved Packet Core (EPC) http://users.encs.concordia.ca/~glitho/ Outline 1. LTE 2. EPC architectures (Basic and advanced) 3. Mobility management in EPC 4.
More information3GPP TSG CN Plenary Meeting #16 5 th - 7 th June 2002. Marco Island, USA. 3GPP TSG-CN1 Meeting #24 Tdoc N1-021455 Budapest, Hungary, 13. 17.
3GPP TSG CN Plenary Meeting #16 5 th - 7 th June 2002. Marco Island, USA. NP-020155 Title: Liaison Statement on 3GPP Network Domain Name usage for IMS Source: CN1 Agenda item: 5.1 Document for: INFORMATION
More informationChapter 25 Domain Name System. 25.1 Copyright The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
Chapter 25 Domain Name System 25.1 Copyright The McGraw-Hill Companies, Inc. Permission required for reproduction or display. 25.2 Figure 25.1 Example of using the DNS service 25-1 NAME SPACE To be unambiguous,
More informationInstallation Guide Advanced Authentication - Linux PAM Client. Version 5.3
Installation Guide Advanced Authentication - Linux PAM Client Version 5.3 Legal Notices For information about legal notices, trademarks, disclaimers, warranties, export and other use restrictions, U.S.
More informationDevelopment of the Domain Name System. Joey Brown David Margolies
Development of the Domain Name System Joey Brown David Margolies Introduction DNS provides name service for the Internet 1982 - HOSTS.TXT Centrally maintained Too large Too costly to distribute Organizations
More information