Use this command to configure label-based application routing and the mobile router (MR) roaming interfaces. The link type label on the interfaces is passed to the home agent (HA) when the interface registers. This label is used during registration on both the MR and the HA to generate dynamic route maps from mobile map templates.
interface ethernet 1/0
ip mobile router-service roam
ip mobile router-service link-type 802.11g
You can use one or more extended named ACLs on both the MR and the HA to identify the application traffic. MR- and HA-named ACLs are used as templates at registration time to generate dynamic ACLs that are used in the dynamic route maps.
ip access-list extended WEB
permit udp any any eq port 8080
You can use one or more mobile map mobile policy templates on the MR and HA.
ip mobile mobile-map MPATH_1 10
match access-list WEB
set link-type 802.11g UMTS
set interface null0
You need to apply the mobile map to access interfaces. The mobile map is associated with a mobile network interface on the MR in the mobile network configuration. The mobile map configuration on the HA can specify up to three ingress interfaces.
ip mobile router
mobile-network e 3/0 policy mobile-map MPATH_1
ip mobile router
ip mobile home-agent policy mobile-map e 2/0 e 3/0 e 4/0
On the MR, a dynamic route map is created when each mobile map template is configured. The dynamic route map has a long name that contains the first seven characters of the mobile map tag.
Example: A mobile map with the tag “MPATH_1” creates the following dynamic route map:
The dynamic name contains the application that generated the MIP, a date and time stamp, and a sequence number.
On the HA, a single dynamic route map is created when the first mobile map is configured. It has the following name: