© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco/Verizon Public Information.
Page 3 of 14
3.
ISR 1900, 2900, 3900 and 4000 series require an IOS Software data license for MPN/DMNR (NeMo support).
This is included by default with 800 series. The data license is acquired by ordering the AppX license. A 60
day temporary data license can be immediately generated using an IOS configuration mode command
(requires an IOS reload to take effect). Below are examples for ISR G2 and 4K series.
license boot module c1900 technology-package datak9
. The keyword following "module" varies based on
ISR model c1900, c2900, c3900. For ISR 4000 series, the configuration mode command is as follows:
license boot level appxk9
the command is the same for all ISR 4K models.
4.
To connect a Network Mobility (NEMO) session to the Verizon Wireless Enterprise GateWay (EXGW), the
enterprise MPN must be provisioned for 4G, and the subscriber mobile line (subscriber identity module [SIM])
used by the mobile router enhanced high-speed WAN interface card (eHWIC, NIM or GRWIC or embedded in
an 819 or 899) must have NEMO permission provisioned by Verizon Wireless.
The enterprise Access Point Name (APN) must be correctly provisioned in the Verizon Wireless network in
order to make a successful private network connection. In addition, the APN must be appropriately set on the
modem for LTE and eHRPD profiles, either automatically through Over-The-Air Device Management (OTA-
DM) or locally on the ISR. If OTA-DM does not update the APN, it can be set manually on the ISR. The
method of manually setting the APN is via a single enable-mode IOS command. An example is shown below:
cellular 0/
0
/0 lte profile create 3
ne01.VZWSTATIC
(Note that the Data APN is profile 3). The middle “
0
” can be 0, 1, 2 or 3 depending on which ISR slot the LTE
module is installed. For 819 and 899, use “cellular 0”. The value “
ne01.VZWSTATIC
” is a sample APN. The
appropriate APN must be provided by Verizon Wireless.
5.
To connect a NEMO session to the EXGW, the mobile router must be configured with the correct Security
Parameter Index (SPI) and key. For DMNR, the correct values are provided in this guide.
6.
To connect a NEMO session to the EXGW, the mobile router must be configured with the correct IP address of
the NEMO High Availability (NEMO-HA) service. The address depends on the location of the EXGW. For the
appropriate address, please contact your Verizon representative.
7.
At least one ISR interface must be registered by the mobile router when the NEMO call is made to the EXGW.
The interface must be in UP/UP state (loopback interface is recommended).
8.
Directly connected and non-connected mobile network prefixes may be configured for registration by the
mobile router. The mobile networks are registered by specifying the connected interface name or by using the
“non-connected-network” command. If non-connected subnets are required, please refer to the guide “DMNR
with Secondary IP and Nonconnected Subnets” available here: www.cisco.com/c/en/us/support/interfac
es-
modules/high-speed-wan-interface-cards/products-installation-and-configuration-guides-list.html
9.
It is not recommended to configure secondary IP addresses on the interfaces that are registered by the mobile
router unless it is intended by design. In Cisco IOS Software a secondary IP address is listed first under the
interface configuration, and its subnet will be the only one that is inserted into the NEMO prefix list from that
interface. If secondary IP addresses are required, please refer to configuration guide “DMNR with Secondary
IP and Nonconnected Subnets” mentioned above.
10. The EXGW will accept up to 8 subnets in the NEMO registration prefix list. Subnets in excess of 8 will be
silently ignored. Registering a summary address using “non-connected-network” stated above may assist.
11. After a successful NEMO registration, the mobile router will automatically bring up a generic-routing-
encapsulation (GRE) tunnel interface (Tunnel0) and will install a dynamic Mobile Default route to that interface.
12. Ensure that no static routes pointing to interface
Cellular 0/x/0
(Cellular 0 for 819 or 899) exist in the mobile
router configuration.
