Cisco Cisco Packet Data Gateway (PDG) Ratgeber Für Administratoren
NEMOv4 with Multi-VRFs
Features and Benefits ▀
Cisco ASR 5x00 Home Agent Administration Guide ▄
245
Overlapping MNPs are allowed, if they are associated with different VRF. MNP must be different if same VRF name is
used on either one MR or across all MRs. Though per customer request, HA does not explicitly deny a request with such
misconfiguration.
used on either one MR or across all MRs. Though per customer request, HA does not explicitly deny a request with such
misconfiguration.
NEMO4G-HA processes the maximum of 16 Cisco-specific MIPv4 Extensions of type Normal Vendor/Org Specific
Extension (NVSE) that are included in the MIPv4 NEMO RRQ. The Cisco NVSE carries VRF tags as part of the
registration signaling. A GRE key associated with the VRF shall be embedded to this new NVSE, in order to provide
VRF traffic segregation between the MR ISR and the NEMO-HA ASR5K during data forwarding. Note, there may be
multiple MNPs for one GRE key, but not one MNP with multiple GREs. The Mobile Network Prefixes (MNP) will
need to be associated with these VRF tags.
Extension (NVSE) that are included in the MIPv4 NEMO RRQ. The Cisco NVSE carries VRF tags as part of the
registration signaling. A GRE key associated with the VRF shall be embedded to this new NVSE, in order to provide
VRF traffic segregation between the MR ISR and the NEMO-HA ASR5K during data forwarding. Note, there may be
multiple MNPs for one GRE key, but not one MNP with multiple GREs. The Mobile Network Prefixes (MNP) will
need to be associated with these VRF tags.
Cisco-specific NVSEs follow RFC 3025 “Mobile IP Vendor/Organization Specific Extensions.”
GRE Encapsulation
User traffic shall be encapsulated over a GRE tunnel between the MR NEMO client and NEMO4G-HA. The IP
endpoints of the GRE tunnel shall be the IPv4 assigned to the MR modem during the Enterprise PDN connection setup
and the IPv4 address of the NEMO4G-HA service on the HA/PGW/GGSN.
endpoints of the GRE tunnel shall be the IPv4 assigned to the MR modem during the Enterprise PDN connection setup
and the IPv4 address of the NEMO4G-HA service on the HA/PGW/GGSN.
NEMO4G-HA shall remove the GRE encapsulation before it forwards the outbound traffic towards the Enterprise VPN
via the associated SGi VLAN interface. Inbound traffic received through the same SGi VLAN interface shall be
encapsulated into a GRE tunnel before it's passed to the HA/PGW/GGSN service for forwarding to the MR through the
proper GTP/PMIP tunnel.
via the associated SGi VLAN interface. Inbound traffic received through the same SGi VLAN interface shall be
encapsulated into a GRE tunnel before it's passed to the HA/PGW/GGSN service for forwarding to the MR through the
proper GTP/PMIP tunnel.
Session Interactions
The following session interaction scenarios are supported between NEMO and the underlying PDN connection made
over CDMA MIP or eHRPD or LTE access.
over CDMA MIP or eHRPD or LTE access.
The mobile router on receiving a packet to from the tunnel shall use the GRE key to identify the tunnel instance. After
decap, the packet shall be forwarded towards the mobile networks, based on the route lookup in the specific VRF
context.
decap, the packet shall be forwarded towards the mobile networks, based on the route lookup in the specific VRF
context.
On receiving a packet from the mobile network, the default-route in the specific VRF context (associated with that input
interface) shall be used and the packet encap shall get the correct GRE key.
interface) shall be used and the packet encap shall get the correct GRE key.
In the following circumstances, NEMO4G-HA shall withdraw the associated prefix routes from the Enterprise VRF
routing table, update the eBGP neighbors and free up all internal resources allocated for the underlying PDN connection
and NEMO session:
routing table, update the eBGP neighbors and free up all internal resources allocated for the underlying PDN connection
and NEMO session:
When the eHRPD terminates the underlying PDN connection (PPP-VSNCP-Term-Req sent to MR and PMIP-
BU with lifetime = 0 sent to HA/PGW/GGSN).
When the MR terminates the PPP/PDN connection when accessing the network via eHRPD.
After an eUTRAN (LTE) detach procedure initiated by the MR or MME.
NEMO4G-HA shall not be able to process any NEMO MIPv4 RRQs if there's no underlying PDN connection
associated to those RRQs (PMIPv6 or GTP). In other words, NEMO MIPv4 RRQs can be accepted and processed only
if an Enterprise PDN connection has been established with HA/PGW/GGSN by the mobile router.
associated to those RRQs (PMIPv6 or GTP). In other words, NEMO MIPv4 RRQs can be accepted and processed only
if an Enterprise PDN connection has been established with HA/PGW/GGSN by the mobile router.
NEMO4G-HA shall silently ignore NEMO MIPv4 RRQs if the underlying PDN connection associated to each of those
RRQs does not have the NEMO permission indication. This applies to CDMA, eHRPD and LTE access.
RRQs does not have the NEMO permission indication. This applies to CDMA, eHRPD and LTE access.
NEMO4G-HA shall forward (not drop) user data using MIP or GRE tunneling (UDP/434 or IP Protocol/47,
respectively) to the external enterprise VRF if such data is not destined to the NEMO4G-HA IP address. This applies to
respectively) to the external enterprise VRF if such data is not destined to the NEMO4G-HA IP address. This applies to