Cisco Cisco Packet Data Interworking Function (PDIF) Guía De Administador
NEMOv4 with Multi-VRFs
▀ Features and Benefits
▄ Cisco ASR 5x00 Home Agent Administration Guide
244
Multi-VRF takes effect only if:
MR sends in RRQ with the new NVSE format.
The specific VRF name is authorized with the ip-pool config. (the default VRF is always
authorized, so vrf-list is NOT required to support multi-vrf, all the old config could support
multi-vrf without any change. If an IP Pool or vrf-list is changed, it takes effect only for
future new calls.
multi-vrf without any change. If an IP Pool or vrf-list is changed, it takes effect only for
future new calls.
Important:
Next-hop forwarding is not supported by Multi-VRF with 15.0. Only
MPLS is supported.
Home Agent on receiving the Mobile IP Registration Request from the mobile router with the above
NVSE, and after a successful authentication learns about the dynamic mobile networks associated
with the mobile router from the Dynamic Network extension in the Registration Request. If the
request is authorized, a Registration Reply with the Mobile Router Multi-VRF NVSE extension is
sent.
with the mobile router from the Dynamic Network extension in the Registration Request. If the
request is authorized, a Registration Reply with the Mobile Router Multi-VRF NVSE extension is
sent.
The Home Agent supports the following:
Dynamic Mobile Network Prefix (MNP) updates for an authorized VRF.
VRF addition/deletion of VRF's from the authorization list without requiring mobile pool
reconfiguration.
MNP's of any length, including /32.
Geo-redundancy (ICSR) for NEMO Multi-VRF.
Mapping of a mobile pool to a list of authorized VRF's.
Multiple VRF authorization lists for 1 APN or Subscriber Profile.
The Home Agent on receiving a packet from the tunnel shall use the GRE key for VRF forwarding the
packet towards the enterprise.
On receiving a packet from the enterprise towards the MR, the VRF key associated with the interface
IDB shall be used as the GRE key.
NEMO MR Authorization
NEMO4G-HA authorizes a NEMO MIPv4 session only if a NEMO permission has been assigned to the underlying
PDN connection. NEMO permission should be assigned to the underlying PDN connection through either local
configuration (APN parameter) or for CDMA via subscriber profile or based on a NEMO permission AVP assigned by
the 3GPP AAA during the PDN authorization. For local configuration, a new APN parameter or for CDMA via
subscriber profile is supported to enable NEMO permission at the APN/PDN level within the HA/PGW/GGSN service.
VRF authorization is needed. The multi-vrf authorization is done by comparing RRQ's each VRF name with the ip-
pool's Default VRF or names defined by the vrf-list.
PDN connection. NEMO permission should be assigned to the underlying PDN connection through either local
configuration (APN parameter) or for CDMA via subscriber profile or based on a NEMO permission AVP assigned by
the 3GPP AAA during the PDN authorization. For local configuration, a new APN parameter or for CDMA via
subscriber profile is supported to enable NEMO permission at the APN/PDN level within the HA/PGW/GGSN service.
VRF authorization is needed. The multi-vrf authorization is done by comparing RRQ's each VRF name with the ip-
pool's Default VRF or names defined by the vrf-list.
MIPv4 NEMO Protocol
NEMO4G-HA processes a Mobile IPv4 NEMO Registration Request (RRQ) received from the MR NEMO client. The
RRQ shall carry multiple NVSEs to reflect the multiple VRFs and multi-tenant Prefixes per MR.
RRQ shall carry multiple NVSEs to reflect the multiple VRFs and multi-tenant Prefixes per MR.