Fallback Mechanism for N26 Connected Mode - 5G to 4G
AMF supports retrying up to three MMEs if the MMEs are not reachable. These MMEs can come from DNS-resolved MME IPs, static configuration, or both.
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Supported scenarios:
DNS-based MME discovery is available for both idle mode (registration with 4G GUTI) and connected mode (handover to EPC) mobility procedures.
Both IPv4 and IPv6 MMEs can be selected, depending on the AMF’s local endpoint configuration.
If DNS resolution fails, AMF falls back to static peer MME configuration.
When multiple IPs are received in a DNS response, AMF selects one IP address.
If the DNS discovery feature is enabled, the AMF prefers the IP addresses resolved from the DNS server.
AMF supports retrying up to three MMEs if the MMEs are not reachable. These MMEs can come from DNS-resolved MME IPs, static configuration, or both.
Enable and manage dynamic peer MME selection for the AMF using DNS queries.
Use this configuration to allow AMF to discover peer MMEs dynamically via DNS, or to revert to static configuration as needed.
Follow these steps to configure DNS-based MME discovery:
|
Step 1 |
Enter the AMF service configuration mode. amf-services amf_service_name |
|
Step 2 |
Enable DNS-based peer MME discovery. peer-mme dns-discovery enabled |
|
Step 3 |
Save and commit the configuration. |