Cisco 4G LTE Software Installation Guide

Table Of Contents

Cisco 4G LTE Software Configuration Guide

Finding Feature Information

Contents

Overview of Cisco 4G LTE

Prerequisites for Configuring Cisco 4G LTE

Restrictions for Configuring Cisco 4G LTE

Cisco 4G LTE Features

4G GPS and NMEA

Example: Connecting to a Server Hosting a GPS Application

Short Message Service (SMS) Capabilities

Using a SIM Card

Data Account Provisioning

IP Multimedia Subsystem Profiles

4G LTE LEDs

How to Configure Cisco 4G LTE

Verifying Modem Signal Strength and Service Availability

Creating, Modifying, or Deleting Modem Data Profiles

Usage Guidelines for Creating, Modifying, or Deleting Data Profiles

Configuration Examples

Configuring a SIM for Data Calls

Locking and Unlocking a SIM Card Using a PIN Code

Changing the PIN Code

Verifying the Security Information of a Modem

Configuring Automatic Authentication for a Locked SIM

Configuring an Encrypted PIN for a SIM

Applying a Modem Profile in a SIM Configuration

Configuring a Dual SIM

Data Call Setup

Configuring the Cellular Interface

Configuring DDR

Configuring DDR Backup

Enabling 4G GPS and NMEA Data Streaming

Configuring 4G SMS Messaging

Configuration Examples for 4G LTE

Example: Basic Cellular Interface Configuration: EHWIC-4G-LTE

Example: Basic Cellular Interface Configuration: Cisco 819 ISR

Cellular Interface Configuration for Always-On Connection

Dialer-Watch Configuration without External Dialer Interface

Dialer-Persistent Configuration with External Dialer Interface

Example: GRE Tunnel over Cellular Interface Configuration

4G-LTE Wireless WAN as Backup with NAT and IPSec

SIM Configuration: Examples

Locking the SIM Card: Example

Unlocking the SIM Card: Example

Automatic SIM Authentication: Example

Changing the PIN Code: Example

Configuring an Encrypted PIN: Example

SMS Initiated Call Back Configuration: Example

Dialer-Watch Configuration without External Dialer Interface: Example

Dialer-Persistent Configuration with External Dialer Interface: Example

Upgrading the Modem Firmware

Upgrading the Modem Firmware Manually

MC7700 Manual Modem Firmware Upgrade: Example

MC7710 Manual Modem Firmware Upgrade: Example

MC7750 Manual Modem Firmware Upgrade: Example

Upgrading the Modem Firmware Using the EEM Scripts

Downloading the Modem Firmware and Installing the EEM Scripts

Running the EEM Scripts on the Router to Upgrade the Modem

Removing EEM Scripts from the Router once the Modem Upgrades Successfully

SNMP MIBs

SNMP 4G LTE Configuration: Example

Troubleshooting

Verifying Data Call Setup

Checking Signal Strength

Verifying Service Availability

Successful Call Setup

Modem Troubleshooting Using Integrated Modem DM Logging

Modem Settings for North America and Carriers Operating on 700 MHz Band

Changing Modem Settings

Electronic Serial Number (ESN)

Additional References

Related Documents

MIBs

RFCs

Technical Assistance

Feature Information for Cisco 4G LTE

Cisco 4G LTE Software Configuration Guide

First Published: March 16, 2012

Last Updated: December 17, 2013, OL-25146-06

This document provides an overview of the software features and configuration information for Cisco Fourth-Generation (4G) Long-Term Evolution (LTE) Wireless WAN (WWAN) Enhanced High-Speed WAN Interface Cards ( EHWIC-4G-LTEs) and also Cisco 819HG-4G and Cisco 819G-4G LTE ISRs that support 4G LTE cellular and 3G cellular networks.

Cisco EHWIC-4G-LTEs are single-wide 4G Wireless WAN (WWAN) EHWICs supported on Cisco Integrated Services Router Generation 2 (ISR G2).For Cisco EHWIC-4G-LTE SKUs, faceplate, and LED descriptions, see the Cisco 4G LTE Hardware Installation Guide.

Finding Feature Information

Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module and to see a list of the releases in which each feature is supported, see the "Feature Information for Cisco 4G LTE" section.

Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Contents

•Overview of Cisco 4G LTE

•Prerequisites for Configuring Cisco 4G LTE

•Restrictions for Configuring Cisco 4G LTE

•Cisco 4G LTE Features

•How to Configure Cisco 4G LTE

•Configuration Examples for 4G LTE

•Upgrading the Modem Firmware

•SNMP MIBs

•Troubleshooting

•Additional References

•Feature Information for Cisco 4G LTE

Overview of Cisco 4G LTE

Cisco EHWIC-4G-LTEs are single-wide Wireless WAN (WWAN) EHWICs supported on Cisco 1900 Series, 2900 Series, and 3900 Series Integrated Services Router Generation 2 (ISR G2) routers. Cisco EHWIC-4G-LTEs operate over Fourth-Generation Long-Term Evolution (4G LTE) cellular networks and Third-Generation (3G) cellular networks. The Cisco 4G LTE WWAN EHWIC offers a highly secure, simplified, and cost-effective WAN alternative to DSL or Frame Relay. In areas where terrestrial broadband services (cable, DSL, or T1) are not available or are expensive, 4G LTE WWAN connectivity can be a viable alternative. Using the integrated services available on the Cisco ISR G2 routers, Cisco 4G LTE Wireless WAN EHWICs can provide instant and mobile communications during disasters and service outages.

Cisco 819 series ISR routers also support integrated 4G LTE wireless WAN.

The Cisco EHWIC-4G-LTEs and Cisco 819 series ISRs (Cisco 819HG-4G and Cisco 819G-4G LTE) supports the following modes:

•3G Evolution-Data Optimized (EVDO or DOrA) Mode—EVDO is a 3G telecommunications standard for the wireless transmission of data through radio signals, typically for broadband Internet access. DOrA refers to EVDO Rev-A. EVDO uses multiplexing techniques including Code Division Multiple Access (CDMA), as well as Time Division Multiple Access (TDMA), to maximize both individual users' throughput and the overall system throughput.

•3G Evolution High-Speed Packet Access (HSPA/HSPA+)—HSPA is a UMTS-based 3G network. It supports High-Speed Downlink Packet Access (HSDPA) and High-Speed Uplink Packet Access (HSUPA) data for improved download and upload speeds. Evolution High-Speed Packet Access (HSPA+) supports Multiple Input/Multiple Output (MIMO) antenna capability.

•4G LTE—4G LTE mobile specification provides multi-megabit bandwidth, more efficient radio network, latency reduction, and improved mobility. LTE solutions target new cellular networks. These networks initially support up to 100 Mb/s peak rates in the downlink and up to 50 Mb/s peak rates in the uplink. The throughput of these networks is higher than the existing 3G networks.

Table 1 describes the Cisco 4G WWAN EHWIC product SKUs.

Table 1 Cisco 4G EHWICs by Mode, Operating Region, and Frequencies

Cisco 4G EHWIC

Description

Mode

Operating Regions

Frequency Band

EHWIC-4G-LTE-V

EHWIC-4G-LTE-V is a dedicated Multimode LTE for Verizon Wireless networks and it is backwards compatible with these technologies :

•Evolved High-Rate Packet Data (EHRPD)

•Single Carrier Evolution Data Optimized (1x EVDO) Revision A

•Single Carrier Radio Transmission Technology (1xRTT)

LTE—EVDO Revison A (DOrA)

North America

•For LTE: 700 MHz (band 13)

•For CDMA 1xRTT and 1xEVDO Revision A

–800 MHz

–1900 MHz

EHWIC-4G-LTE-A

EHWIC-4G-LTE-A is a dedicated Multimode LTE for AT&T Wireless networks and it is backwards compatible with these technologies :

•Universal Mobile Telecommunications System (UMTS)

•High Speed Packet Access + (HSPA+)

•HSPA

•Global System for Mobile communications (GSM)

•Exchanged Data rates for GSM Evolution (EDGE)

•General Packet Radio Services (GPRS)

LTE—HSPA+/HSPA/UMTS/EDGE/GPRS

North America

For LTE:

•700 MHz (band 17)

•AWS (band 4)

•2100 MHz (band 1)

For UMTS, HSPA+ and HSPA:

•800 MHz

•850 MHz

•1900 MHz

•2100 MHz

For GSM , EDGE and GPRS:

•850 MHz

•900 MHz

•1800 MHz

•1900 MHz

EHWIC-4G-LTE-G

EHWIC-4G-LTE-G is a Dedicated Multimode LTE for global wireless networks and it is backwards compatible with these technologies :

•UMTS

•HSPA+

•HSPA

•GSM

•EDGE

•GPRS

LTE—HSPA+/HSPA/UMTS/EDGE/GPRS

Global

For LTE:

•800 MHz (band 20)

•900 MHz (band 8)

•1800 MHz (band 3)

•2100 MHz (band 1)

•2600 MHz (band 7)

For UMTS/HSPA+/HSPA:

•900 MHz

•2100 MHz

For GSM/EDGE/GPRS:

•900 MHz

•1800 MHz

•1900 MHz

EHWIC-4G-LTE-JP

EHWIC-4G-LTE-JP is a dedicated multimode 4G LTE for NTT Docomo Japan, and is based on the Sierra Wireless MC7700 modem. EHWIC-4G-LTE-JP is backward compatible with these technologies:

•UMTS

•HSPA+

LTE—UMTS/HSPA+

Japan

For LTE: 2100 MHz (band 1)

For UMTS/HSPA+:

•2100 MHz (band 1)

•1900 MHz (band 2)

•850 MHz (band 5)

EHWIC-4G-LTE-BE

EHWIC-4G-LTE-BE is a dedicated multimode LTE for Canada, and is based on the Sierra Wireless MC7700 modem. EHWIC-4G-LTE-BE is backward compatible with these technologies:

•UMTS

•HSPA+

LTE—UMTS/HSPA+

Canada

For LTE: AWS band 4

For UMTS/HSPA+:

•2100 MHz (band 1)

•1900 MHz (band 2)

•850 MHz (band 5)

Figure 1 4G LTE Packet Core Network Architecture

Gateways

The Serving Gateway (SGW) routes and forwards user data packets, while also acting as the mobility anchor for the user plane, and is the anchor for mobility between LTE and other 3GPP technologies. The Packet Data Network (PDN) Gateway (PGW) provides connectivity from the User Equipment (UE) to external packet data networks by being the point of exit and entry of traffic for the UE.

A UE may have simultaneous connectivity with more than one PGW for accessing multiple PDNs. The PGW performs policy enforcement, packet filtering for each user, charging support, lawful interception, and packet screening. Another key role of the PGW is to act as the anchor for mobility between 3GPP and non-3GPP technologies such as WiMAX and 3GPP2 (CDMA 1X and EvDO).

The System Architecture Evolution GW (SAE GW) is the entity that covers the PGW and SGW functionality in the Evolved Packet Core (EPC).

RNC

The Radio Network Controller (RNC) is responsible for controlling the Radio Access Network (RAN) that are connected to it. The RNC carries out radio resource management and some of the mobility management functions and is the point where encryption is done before user data is sent to and from the mobile. The RNC connects to the Circuit-Switched Core Network through the Media Gateway (MGW).

BTS

Base Transceiver Station.

BSC

Base Station Controller.

SGSN

Service GPRS Support Node.

Prerequisites for Configuring Cisco 4G LTE

•You must have 4G LTE network coverage where your router is physically placed. For a complete list of supported carriers, see the product data sheet.

•You must subscribe to a service plan with a wireless service provider and obtain a Subscriber Identity Module (SIM) card.

•You must install the SIM card before configuring the 4G LTE Wireless WAN EHWIC or Cisco 819 router. For instructions on how to install the SIM card, see the Configuring a SIM for Data Calls for more information.

•The standalone antenna that supports GPS capabilities must be installed for the GPS feature to work. See the Cisco 4G Indoor/Outdoor Active GPS Antenna (GPS-ACT-ANTM-SMA) document for installation information.

•Both GPS and NMEA features must be configured for GPS coordinates to be obtained.

Restrictions for Configuring Cisco 4G LTE

Follow these restrictions and usage guideline while configuring Cisco 4G LTE :

•Currently, cellular networks support only outgoing calls.

•Due to the shared nature of wireless communications, the experienced throughput varies depending on the number of active users or congestion in a given network.

•Cellular networks have higher latency compared to wired networks. Latency rates depend on the technology and carrier. Latency may be higher because of network congestion.

•Public Land Mobile Network (PLMN) feature is not supported.

•Any restrictions that are part of the terms of service from your carrier.

•SMS—Only one text message up to 160 characters to one recipient at a time is supported. Larger texts are automatically truncated to the proper size before being sent.

•For the router that runs the SNMP agent, you must configure appropriate access control (for example, SNMP-server community) using the Cisco IOS CLI for the NMS and agent to work properly.

•It is strongly recommended that you configure SNMP V3 with authentication/privacy when implementing SNMP SET operation.

Cisco 4G LTE Features

Cisco 4G LTE WWAN EHWICs and Cisco 819HG-4G and Cisco 819G-4G LTE ISRs support the following major functionality:

•Global Positioning System (GPS) and National Marine Electronics Association (NMEA) streaming.

•4G SMS

•IPv4 bearer

•Mobile Internet Protocol Version 4 (MIPv4) , IPv4 Network Mobility (NEMOv4), RFC 3025

•IPv4 subnet behind LTE UE interface

•Evolved High-Rate Packet Data (EHRPD) protocol, which allows seamless transition between LTE and 3G services (EHWIC-4G-LTE-V only)

•Seamless handoff between LTE and the EHRPD network (EHWIC-4G-LTE-V only)

•Support for the UMTS service as a fallback option from the LTE service (EHWIC-4G-LTE-A, EHWIC-4G-LTE-G, EHWIC-4G-LTE-JP, and EHWIC-4G-LTE-BE only)

•Seamless handoff between LTE and UMTS service (EHWIC-4G-LTE-A, EHWIC-4G-LTE-G, EHWIC-4G-LTE-JP, and EHWIC-4G-LTE-BE only)Seamless transition between LTE and UMTS service (EHWIC-4G-LTE-A and EHWIC-4G-LTE-G only)

•Remote access to Qualcomm Diagnostic Monitor (DM) port

•OTA-DM including wireless configuration FOTA (EHWIC-4G-LTE-V only)

•Mini USB type 2 connector for modem provisioning

•Single Universal Integrated Chip Card (UICC) or Universal Subscriber Identity Module (USIM)

•3G/4G Simple Network Management Protocol (SNMP) MIB.

4G GPS and NMEA

With the introduction of Cisco IOS Release 15.3(3)M, the Global Positioning System (GPS) feature is enabled by default on the supported Cisco 819 ISRs and Cisco 4G LTE EHWICs to provide the geographical location.

Active GPS is supported on the SubMiniature version A (SMA) port. Active GPS antenna is supported only in the standalone mode. An Active GPS antenna includes a built-in Low-Noise Amplifier that provides sufficient gain to overcome coaxial cable losses while providing the proper signal level to the GPS receiver. Active GPS antennae require power from the GPS receiver SMA port to operate. See the "Example: Connecting to a Server Hosting a GPS Application" section for more information.

National Marine Electronics Association (NMEA) streams GPS data either from a 4G EHWIC or a Cisco 819 ISR through a virtual COM port and a TCP/IP Ethernet connection to any marine device (such as a Windows-based PC) that runs a commercially available GPS-based application.

The following GPS and NMEA features are supported on the EHWIC-4G-LTE-V, EHWIC-4G-LTE-A, and EHWIC-4G-LTE-G4G SKUs and the Cisco 819HG-4G and Cisco 819G-4G LTE ISRs:

•GPS standalone mode (satellite-based GPS).

•Cisco IOS CLI display coordinates.

•Virtual and physical serial ports can export NMEA-formatted GPS data.

•External application displays router map location.

•Objects in the CISCO-WAN-3G-MIB supports GPS and NMEA features.

•The Cisco 4G LTE EHWIC supports only the IP NMEA streaming option.

•The Cisco 819HG-4G and Cisco 819G-4G LTE ISRs can support either IP or serial NMEA streaming options.

Note Assisted GPS mode is not supported.

For instructions on setting up the GPS antenna, see the Cisco 4G Indoor/Outdoor Active GPS Antenna (GPS-ACT-ANTM-SMA) document.

Example: Connecting to a Server Hosting a GPS Application

You can feed the NMEA data to a remote server that hosts the GPS application. The server can be connected to the router either directly using an Ethernet cable or through a LAN or WAN network. If the application supports serial port, run a serial port emulation program to create a virtual serial port over the LAN or WAN connection.

Note Microsoft Streets & Trips is a licensed software that you can download from the Microsoft website.

To connect a Cisco 819 ISR through IP to a PC running Microsoft Streets & Trips, perform the following steps:

Step 1 Connect the PC to the router using an Ethernet cable.

Step 2 Ensure that the PC and router can ping.

Step 3 Launch the serial port redirector on the PC.

Step 4 Use the show line command in the privileged EXEC mode to locate the NMEA port on the router.

Step 5 Create a virtual serial port that connects to the NMEA port on the router.

Step 6 Launch Microsoft Streets & Trips on your PC.

Step 7 Select the GPS Menu.

Step 8 Click Start Tracking.

Step 9 If you have acquired a location fix from the show cellular gps command output on the router, the current location is plotted on the graph, and a reddish brown dotted cursor with a circle around it is seen on the map.

Note If you have not acquired a location fix, the Microsoft application times out and disconnects.

Short Message Service (SMS) Capabilities

The 4G EHWIC MC77xx modems support receiving, transmitting, archiving, and deleting of SMS messages. This support includes the ability to view up to 25 received texts, and archive more messages in a custom file location. SMS is supported on multiple carriers. MC77xx modems also have the capability to revert from LTE SMS to 3G and 2G SMS technology if necessary.

A sending device behind an MC77xx modem and router transmits an SMS text message over the 4G cellular link through cellular towers until it the message reaches the recipient's router, which then notifies the recipient device, such as a cell phone. The receiving device uses the same process to return a reply to the sending device. Figure 2 describes the flow from a mobile device to a sending device. For SMS transmission to work, end users must have a text-capable device, and optionally, a text plan. If end users do not have a text plan, standard SMS rates apply to their text transmissions.

The SMS-initiated Data Callback feature allows customers to set up a data connection by sending a text message to the 4G EHWIC MC77xx modem and includes the message screening functionality using the originating number to improve feature security and eliminate unauthorized callback requests.

Figure 2 SMS Network

Using a SIM Card

The 4G LTE EHWIC needs an active SIM card provided by a service provider. The SIM cards are usually provided in an unlocked state so that it can be used without a Personal Identification Number (PIN). If the SIM is unlocked, it can be inserted into an EHWIC and used without an authorization code.

The SIM can be initially locked with a PIN code (4 to 8 digits s long) defined by the service provider. Contact your service provider for the PIN code.

The SIM-Lock feature allows a SIM to be locked or unlocked with a PIN code so that it is used only in an authorized device. Perform the SIM lock and unlock procedures using the Cisco IOS CLI through a console or Telnet/SSH to the ISR.

After the SIM is locked, it cannot initiate a call unless authentication is done using the same PIN. Authentication is done automatically by Cisco IOS through configuration of the PIN. This mandatory configuration for automatic SIM authentication is done using the Cisco IOS CLI as part of the router startup configuration.

After the Cisco IOS configuration is in place, the ISR can initiate an LTE connection. The ISR uses the configured PIN to authenticate prior to the LTE connection. If the Cisco IOS PIN configuration is missing or if the PIN is incorrect, the SIM authentication will fail and the connection will not be initiated.

If the locked SIM is moved to a different ISR or to another device, or if the EHWIC in which the locked SIM resides is moved to a different EHWIC slot in the same ISR, the ISR configuration should be changed. The configuration is associated with the cellular controller that is specific to an ISR EHWIC slot number. This will ensure that the SIM card will not be used in any unauthorized device, or, if there are multiple LTE EHWICs in a single ISR, that the appropriate PIN is applied to each LTE EHWIC/SIM. An authentication command (with the same PIN used to lock the SIM) must be defined on the new device or on the new cellular controller slot to successfully initiate the LTE connection.

The following procedures are used to configure a SIM:

•Locking and Unlocking a SIM Card Using a PIN Code

•Applying a Modem Profile in a SIM Configuration

Caution It is very important to use the correct PIN after it is configured. The SIM card will be blocked if the wrong PIN is entered three consecutive times on a locked SIM during authentication or when trying to unlock a locked SIM.

You can unblock a blocked SIM card using the PUK code. Contact your service provider for the PUK code.

Use the cellular <slot> lte sim unblock <PUK code> <new PIN code> command to unblock the SIM.

Data Account Provisioning

One or more modem data profiles can be created to provision a modem on a 3G or 4G EHWIC. An active wireless account with a service provider with one or more (dual) SIM cards must be installed. The modem data profile is preconfigured on the modem.

The following tasks are used to verify the signal strength and service availability of the modem and to create, modify, and delete modem data profiles:

•Verifying Modem Signal Strength and Service Availability

•Creating, Modifying, or Deleting Modem Data Profiles

IP Multimedia Subsystem Profiles

IP Multimedia Subsystem (IMS) profiles establish a session, and are a part of the modem configuration and are stored in the modem's NVRAM. An IMS network is an access-independent and standard-based IP connectivity service that enables different types of multimedia services to end users using common Internet-based protocols. See "Creating, Modifying, or Deleting Modem Data Profiles" section, for more information.

4G LTE LEDs

Table 2 describes 4G LTE EHWIC and 819 ISR LED behavior:

Table 2 4G LTE LED Descriptions

LED

Color

Description

SYS

Yellow

FPGA download is complete.

Green (blinking)

ROMMON is operational.

Green (solid)

Cisco IOS is operational.

Green (four blinks during bootup)

Reset button has been pushed during the bootup.

Off

After powering up, when FPGA is being downloaded (in ROMMON).

ACT

Green

Network activity on FE switch ports, GE WAN port, 3G cellular interface, and serial interfaces.

Off

No network connectivity.

WWAN

Green

Module is powered on and connected, but is not transmitting or receiving.

Green (slow blinking)

Module is powered on and searching for connection.

Green (fast blinking)

Module is transmitting or receiving.

Off

Module is not powered.

GPS - EHWIC

Green (solid)

GPS coordinates are obtained.

Off

GPS is disabled, GPS is enabled without GPS mode and NMEA configuration, or GPS is acquiring.

GPS - 819 ISR

Green (solid)

GPS coordinates are obtained.

Green (blinking)

GPS is acquiring.

Off

GPS is disabled or GPS is enabled without GPS mode and NMEA configuration.

RSSI

Green (solid)

Signal > -60 dBm

Very strong signal

Green (three blinks and then a long pause)

Signal <= -60 to 74 dBm

Strong signal

Green (two blinks and then a long pause)

Signal <= -75 to 89 dBm

Fair signal

Green (one blink and then a long pause)

Signal <= -90 to 109 dBm

Marginal signal

Off

Signal <= -110 dBm

Unusable signal

SIM

Green / Yellow (one green blink followed by two yellow blinks)

SIM in slot 0 is active, SIM in slot 1 is not.

Yellow / Green (one yellow blink followed by two green blinks)

SIM in slot 1 is active, SIM in slot 0 is not.

Off / Green (two green blinks and then a pause)

No SIM in slot 0, SIM present in slot 1.

Green / Off (slow single green blink and then a pause)

SIM present in slot 0, no SIM in slot 1.

Off / Off

No SIM present in either slots.

3G/4G

Green (one blink and then a pause)

For 1xRTT, EGPRS, or GPRS service.

Green (two blinks and then a pause)

For EVDO, EVDO/1xRTT, or UMTS service.

Green (three blinks and then a pause)

For EVDO/1xRTT RevA, HSPA, or HSUPA/HSDPA service.

Green (four blinks and then a pause)

For HSPA+ service.

Green (Solid)

For 4G/LTE service.

Off

No service.

How to Configure Cisco 4G LTE

Note For 4G-LTE EHWICs, the numbering for slot 0, wic 0, and port 0 is 0/0/0 for all commands. For Cisco 819 4G LTE fixed platforms, use slot "0" for all commands.

•Verifying Modem Signal Strength and Service Availability

•Creating, Modifying, or Deleting Modem Data Profiles

•Configuring a SIM for Data Calls

•Data Call Setup

•Enabling 4G GPS and NMEA Data Streaming

•Configuring 4G SMS Messaging

Verifying Modem Signal Strength and Service Availability

Note For the EHWIC, the unit argument identifies the router slot, WIC slot, and port separated by slashes (0/0/0). For the Cisco 819 ISR fixed platform, the unit argument identifies slot "0" for all commands.

SUMMARY STEPS

1. show cellular unit network

2. show cellular unit radio

3. show cellular unit profile

4. show cellular unit security

5. show cellular unit all

DETAILED STEPS

Command or Action

Purpose

Step 1

show cellular unit network
Example:

Device# show cellular 0/0/0 network

Displays information about the carrier network, cell site, and available service.

Step 2

show cellular unit radio
Example:

Device# show cellular 0/0/0 radio

Shows the radio signal strength.

Note The RSSI should be better than -90 dBm for steady and reliable connection.

Step 3

show cellular unit profile
Example:

Device# show cellular 0/0/0 profile

Shows information about the modem data profiles created.

Step 4

show cellular unit security
Example:

Device# show cellular 0/0/0 security

Shows the security information for the modem, such as SIM and modem lock status.

Step 5

show cellular unit all
Example:

Device# show cellular 0/0/0 all

Shows consolidated information about the modem, profiles created, radio signal strength, network security, and so on.

Creating, Modifying, or Deleting Modem Data Profiles

You can create multiple profiles on Cisco 819 ISRs and EHWICs. The following are the default internet profile numbers for some of the modem SKUs:

•Profile 1— MC7700: (EHWIC-LTE-4G-G and C819-LTE-4G-G)

•Profile 1— MC7710: (EHWIC-LTE-4G-A and C819-LTE-4G-A)

•Profile 3— MC7750: (EHWIC-LTE-4G-V and C819-LTE-4G-V)

Usage Guidelines for Creating, Modifying, or Deleting Data Profiles

Follow these guidelines while you configure a data profile:

•In most cases, you do not have to make any profile-related changes if your modem comes with a default profile, for instance, AT&T and Verizon.

•If any profile parameter changes are required for a connection type, the changes will most likely be carried out in the default profiles.

•To configure different profile types and use them for a different connection, you can create separate profiles with different parameters (for instance, APN names). Note that only one profile is active at a given time.

•Use the show cellular <> profile command to view the default profile. An asterisk(*) is displayed against the default profile.

•The default profile is used to set up a data call. If you want to use a different profile, that profile needs to be made the default one. Use the lte sim profile <number> command to change the default profile.

•To verify the completed sets of 3GPP and 3GPP2 profiles, enable the debug cellular <0/x/0> message profile command and then enter the show cellular 0 profile command. This debug command is applied to the MC7750 modem for EHWIC-LTE-4G-V and C819-LTE-4G-V SKUs.

Note If you are using the MC7750(EHWIC-LTE-4G-V and C819-LTE-4G-V), avoid modifying the ims profile (Profile 1 displayed in the show command with a ** against it). Typically, you have to modify Profile 3 for an APN update.

Note For the EHWIC, the unit argument identifies the router slot, WIC slot, and port separated by slashes (0/0/0). For the Cisco 819 ISR fixed platform, the unit argument identifies slot "0" for all commands.

SUMMARY STEPS

1. cellular unit lte profile [create | delete] profile-number [apn [authentication [username password [bearer-type]]]]

DETAILED STEPS

Command or Action

Purpose

Step 1

cellular unit lte profile [create | delete] profile-number [apn [authentication [username password [bearer-type]]]]
Example:

Device# cellular 0/0/0 lte profile create 2 apn.com pap username pwd ipv4

Creates, modifies, or deletes a modem data profile in the privileged EXEC mode.

•The profile-number argument specifies the profile number created for the modem. Up to 16 profiles can be created for the MC7700 and MC7710 modems. Up to six profiles can be created for the MC7750 modem.

•(Optional) The apn argument specifies an Access Point Name (APN) in the profile. An APN is provided by your service provider. Only a single APN can be specified in a single profile.

•(Optional) The authentication parameter specifies the authentication type used. Acceptable parameters are chap, none (no authentication), pap, and pap_chap (PAP or CHAP authentication).

•(Optional) The username and password arguments are given by a service provider.

•(Optional) The bearer-type parameter specifies the type of data payload exchanged over the air link when the packet data session is established with this profile. Acceptable data type parameters are: ipv4, ipv6, and ipv4v6 (IPv4 and IPv6).

Note Entering this command results in the creation or modification of both the 3GPP and 3GPP2 profiles with the same parameters for the MC7750 modem.

Note The default internet profile numbers for the various modem SKUs are: MC7700 - Profile 1, MC7710 - Profile 1, MC7750 - Profile 3. The default profile is displayed by using the show cellular unit profile command with an asterisk(*).

Configuration Examples

The following example shows how to change a default profile on EHWIC-4G-LTE-A:
router(config-controller)#lte sim profile 2
router(config-controller)#end
router#
router#sh run
Building configuration...
controller Cellular 0/1
 lte sim profile 2
router#ping 8.8.4.4 rep 10
Type escape sequence to abort.
Sending 10, 100-byte ICMP Echos to 8.8.4.4, timeout is 2 seconds:
!!!!!!!!!!
Success rate is 100 percent (10/10), round-trip min/avg/max = 284/364/600 ms
router#
The following example shows the output of the show cellular command:
router#show cellular 0/1/0 profile
Profile 1 = INACTIVE **
--------
PDP Type = IPv4
Access Point Name (APN) = Broadband
Profile 2 = ACTIVE*
--------
PDP Type = IPv4
PDP address = 10.176.207.8
Access Point Name (APN) = Broadband
        Primary DNS address = 172.26.38.1
        Secondary DNS address = 172.26.38.2
  * - Default profile 
 ** - LTE attach profile
The following example shows the output of the show cellular command before you enable the debug command:
router#show cellular 0/0/0 profile
Profile 1 = INACTIVE **
--------
PDP Type = IPv6
Access Point Name (APN) = vzwims
Profile 2 = INACTIVE
--------
PDP Type = IPv4v6
Access Point Name (APN) = vzwadmin
Profile 3 = ACTIVE*
--------
PDP Type = IPv4v6
PDP address = 10.187.130.3
Access Point Name (APN) = VZWINTERNET
        Primary DNS address = 198.224.173.135
        Secondary DNS address = 198.224.174.135
Profile 4 = INACTIVE
--------
PDP Type = IPv4v6
Access Point Name (APN) = vzwapp
  * - Default profile    /* Note
 ** - LTE attach profile  /* note
The following example shows the output of the show cellular command after you enable the debug command:
router#debug cellular 0/0/0 messages profile
PROFILE_3GPP2 debugging is on
router#
router #show cellular 0/0/0 profile            
Profile 1 = INACTIVE **
--------
PDP Type = IPv6
Access Point Name (APN) = vzwims
Profile 2 = INACTIVE
--------
PDP Type = IPv4v6
Access Point Name (APN) = vzwadmin
Profile 3 = ACTIVE*
--------
PDP Type = IPv4v6
PDP address = 10.187.130.3
Access Point Name (APN) = VZWINTERNET
        Primary DNS address = 198.224.173.135
        Secondary DNS address = 198.224.174.135
Profile 4 = INACTIVE
--------
PDP Type = IPv4v6
Access Point Name (APN) = vzwapp
3GPP2 Profiles:
==============
Profile 1 = INACTIVE
--------
PDN Type = IPv6
Access Point Name (APN) = vzwims
Profile 2 = INACTIVE
--------
PDN Type = IPv4v6
Access Point Name (APN) = vzwadmin
Profile 3 = INACTIVE*
--------
PDN Type = IPv4v6
Access Point Name (APN) = VZWINTERNET
Profile 4 = INACTIVE
--------
PDN Type = IPv4v6
Access Point Name (APN) = vzwapp
Profile 5 = INACTIVE
--------
PDN Type = IPv4v6
Access Point Name (APN) = 
Profile 6 = INACTIVE
--------
PDN Type = IPv4v6
Access Point Name (APN) = 
  * - Default profile 
 ** - LTE attach profile
Configuring a SIM for Data Calls

•Locking and Unlocking a SIM Card Using a PIN Code

•Changing the PIN Code

•Verifying the Security Information of a Modem

•Configuring an Encrypted PIN for a SIM

•Applying a Modem Profile in a SIM Configuration

•Applying a Modem Profile in a SIM Configuration

•Configuring a Dual SIM

Locking and Unlocking a SIM Card Using a PIN Code

Perform this task to lock or unlock a SIM card given by your service provider.

Caution The SIM card gets blocked if the wrong PIN is entered three consecutive times. Make sure you enter the correct PIN the SIM is configured with. If your SIM card gets blocked, contact your service provider for a PUK code. Using the PUK code, you can unblock the SIM card.

Note For the EHWIC, the unit argument identifies the router slot, WIC slot, and port separated by slashes (0/0/0). For the Cisco 819 ISR fixed platform, the unit argument identifies slot "0" for all commands.

SUMMARY STEPS

1. cellular unit lte sim {lock | unlock} pin

DETAILED STEPS

Command or Action

Purpose

Step 1

cellular unit lte sim {lock | unlock} pin
Example:

Device# cellular 0/0/0 lte sim lock 1111

Locks or unlocks the SIM card using a PIN code.

•pin—A code (4 to 8 digits long) provided by your carrier to lock or unlock the SIM card.

Changing the PIN Code

Perform this task to change the PIN code of a SIM.

Note For the EHWIC, the unit argument identifies the router slot, WIC slot, and port separated by slashes (0/0/0). For the Cisco 819 ISR fixed platform, the unit argument identifies slot "0" for all commands.

SUMMARY STEPS

1. cellular unit lte sim change-pin pin new-pin

DETAILED STEPS

Command or Action

Purpose

Step 1

cellular unit lte sim change-pin pin new-pin
Example:

Device# cellular 0/0/0 lte sim change-pin 1111 1234

Changes the assigned PIN code. SIM should be in locked state when the PIN is being changed.

Verifying the Security Information of a Modem

Perform this task to verify the security information of a modem.

Note For the EHWIC, the unit argument identifies the router slot, WIC slot, and port separated by slashes (0/0/0). For the Cisco 819 ISR fixed platform, the unit argument identifies slot "0" for all commands.

SUMMARY STEPS

1. show cellular unit security

DETAILED STEPS

Command or Action

Purpose

Step 1

show cellular unit security
Example:

Device# show cellular 0/0/0 security

Shows the security information of the modem, including the SIM lock status.

Configuring Automatic Authentication for a Locked SIM

An unencrypted PIN can be configured to activate the Card Holder Verification (CHV1) code that authenticates a modem.

Caution The SIM card gets blocked if the wrong PIN is entered three consecutive times. Make sure you enter the correct PIN the SIM is configured with. If your SIM card gets blocked, contact your service provider for a PUK code.

Note Follow these procedures when using an unencrypted Level 0 PIN to configure CHV1. For instructions on how to configure CHV1 using an encrypted Level 7 PIN, see the "Configuring an Encrypted PIN for a SIM" section.

Note A SIM should be locked for SIM authentication to work. To verify the SIM's status, use the show cellular unit security command.

Note For the EHWIC, the unit argument identifies the router slot, WIC slot, and port separated by slashes (0/0/0). For the Cisco 819 ISR fixed platform, the unit argument identifies slot "0" for all commands.

SUMMARY STEPS

1. configure terminal

2. controller cellular unit

3. lte sim authenticate 0 pin
or
lte sim authenticate 0 pin slot {0 | 1} (Cisco 819(H)G-4G-G ISR only)

DETAILED STEPS

Command or Action

Purpose

Step 1

configure terminal
Example:

Device# configure terminal

Enters global configuration mode.

Step 2

controller cellular unit
Example:

Device(config)# controller cellular 0/0

Enters the cellular controller configuration mode.

Step 3

For Cisco 819 ISRs and 4G EHWICs that do not have dual SIM feature:

lte sim authenticate 0 pin

For the Cisco 819(H)G-4G-G ISR that supports dual SIM feature:

lte sim authenticate 0 pin slot {0 | 1}
Example:

Device(config-controller)# lte sim authenticate 0 1111

Authenticates the SIM CHV1 code by using an unencrypted (0) keyword and PIN. This PIN is sent to the modem for authentication with each subsequent LTE connection. If authentication passes based on the configured PIN, the data call is allowed. If authentication fails, the modem does not initiate the data call.

Note This command is valid only when an unencrypted PIN is used. To configure CHV1 code using an encrypted PIN, see the "Configuring an Encrypted PIN for a SIM" section.

Note The slot keyword and its options are only available on the Cisco 819(H)G-4G-G ISR, which supports the dual SIM feature.

Configuring an Encrypted PIN for a SIM

To configure an encrypted PIN, the scrambled value of the PIN must be obtained. To get the scrambled Level 7 PIN and to configure the SIM CHV1 code for verification using this encrypted PIN, enter the following commands in the EXEC mode.

Note When obtaining the encrypted PIN for a SIM, a username and password are created by configuring password encryption, defining the username and associated password, copying the resulting scrambled password, and using this scrambled password in the SIM authentication command. After the scrambled PIN has been obtained and used in SIM authentication, the username created can be deleted from the Cisco IOS configuration.

Note A SIM should be locked for SIM authentication to work. To verify the SIM's status, use the show cellular unit security command.

Note For the EHWIC, the unit argument identifies the router slot, WIC slot, and port separated by slashes (0/0/0). For the Cisco 819 ISR fixed platform, the unit argument identifies slot "0" for all commands.

SUMMARY STEPS

1. configure terminal

2. service password-encryption

3. username name privilege 0 password pin

4. do show run | i name

5. controller cellular unit

6. lte sim authenticate {0 | 7} pin
or
lte sim authenticate {0 | 7} pin slot {0 | 1} (Cisco 819(H)G-4G-G ISR only)

7. exit

8. no username name

9. no service password-encryption

DETAILED STEPS

Command or Action

Purpose

Step 1

configure terminal
Example:

Device# configure terminal

Enters global configuration mode.

Step 2

service password-encryption
Example:

Device(config)# service password-encryption

Enables password encryption.

Step 3

username name privilege 0 password pin
Example:

Device(config)# username SIM privilege 0 password 1111

Creates username and password.

•name—Specifies the username.

•pin—Specifies the four- to eight-digit PIN code.

Step 4

do show run | i name
Example:

Device(config)# do show run | i SIM

Shows the username configuration line with the encrypted level 7 PIN for the username created in Step 3 (user "SIM" in the example shown).

Copy the scrambled password for use in Step 6 (as the PIN).

Step 5

controller cellular unit
Example:

Device(config)# controller cellular 0/0

Enters the cellular controller configuration mode.

Step 6

For the Cisco 4G LTE WWAN EHWICs and Cisco 819(H)G-4G LTE ISRs:

lte sim authenticate {0 | 7} pin

For the Cisco 819(H)G-4G-G ISR that supports dual SIM feature:

lte sim authenticate {0 | 7} pin slot {0 | 1}
Example:

Device(config-controller)# lte sim authenticate 7 055A575E70

Authenticates the SIM CHV1 code by using the encrypted keyword 7 and the scrambled PIN from Step 4. The PIN is sent to the modem for authentication with each subsequent LTE connection. If authentication passes based on the configured PIN, the data call is allowed. If authentication fails, the modem does not initiate the data call.

Note The slot keyword and its options are available only on the Cisco 819(H)G-4G-G ISR, which supports the dual SIM feature.

Step 7

exit
Example:

Device(config-controller)# exit

(Optional) Exits the cellular controller configuration mode.

Step 8

no username name
Example:

Device(config)# no username SIM

(Optional) Removes the username and password created in Step 3.

Step 9

no service password-encryption
Example:

Device(config)# no service password-encryption

(Optional) Disables password encryption.

Applying a Modem Profile in a SIM Configuration

Note For the EHWIC, the unit argument identifies the router slot, WIC slot, and port separated by slashes (0/0/0). For the Cisco 819 ISR fixed platform, the unit argument identifies slot "0" for all commands.

SUMMARY STEPS

1. configure terminal

2. controller cellular unit

3. lte sim profile number [ims number]
or
lte sim profile number [ims number] slot {0 | 1} (Cisco 819(H)G-4G-G ISR only)

DETAILED STEPS
Command or Action

Purpose

Step 1

configure terminal
Example:

Device# configure terminal

Enters the global configuration mode.

Step 2

controller cellular unit
Example:

Device(config)# controller cellular 0/0

Enters the cellular controller configuration mode.
Step 3
For Cisco 819 ISRs and 4G EHWICs that do not have dual SIM feature:

lte sim profile number [ims number]

For the Cisco 819(H)G-4G-G ISR that supports dual SIM feature:
lte sim profile number [ims number] slot {0 | 1}
Example:

Device(config-controller)# lte sim profile 1 ims 2 slot 0
Device(config-controller)# lte sim profile 3 ims 4 slot 1
(All MC77xx modems) Applies the configured profile number to the SIM and its slot number. The default (primary) slot is 0.

An IMS profile number is configured for each SIM from 1 to 6 if you have a MC7750 modem, and 1 to 16 if you have an MC7710 or MC7700 modem.

Note The slot keyword and its options are available only on the Cisco 819(H)G-4G-G ISR, which supports the Dual SIM feature.
Configuring a Dual SIM

The Dual SIM feature provides a failover mechanism in case the active SIM loses connectivity to the network. The Dual SIM feature is supported only on C819(H)G-4G-G-K9.

Note Dual SIM is supported only on C819 platforms and not on EHWICs although modular ISRs can have multiple 4G EHWICs.

Usage Guidelines for Configuring a Dual SIM

Follow these guidelines while you configure a dual SIM:

•By default, SIM slot 0 is the primary slot, and slot 1 is the backup.

•To change the primary SIM slot, use the lte sim primary command in the cellular controller configuration mode.

•Assign profiles for each SIM using the lte sim profile command. Each SIM has an associated internet profile and an ims profile.

•In the lte sim profile command, the profile number refers to the internet profile associated with a SIM. The ims number is the attach profile associated with a SIM.

•If the ims profile details are not provided by or are not relevant to the carrier, you can assign the same number as the internet profile. Otherwise, create a profile with the carrier-specific ims parameters and assign that profile number using the lte sim profile command.

SUMMARY STEPS

1. configure terminal

2. controller cellular unit

3. lte sim primary slot

4. lte sim max-retry number

5. lte sim authenticate [0 | 7] pin slot {0 | 1}

6. lte failover timeout-period

7. lte sim profile number [ims number] slot {0 | 1}

DETAILED STEPS
Command or Action

Purpose

Step 1

configure terminal
Example:

Device# configure terminal

Enters the global configuration mode.

Step 2

controller cellular unit
Example:

Device(config)# controller cellular 0/0

Enters the cellular controller configuration mode.

Step 3

lte sim primary slot
Example:

Device(config-controller)# lte sim primary 1

(Optional) Enters either slot number 0 or 1 of the primary SIM.

Step 4

lte sim max-retry number
Example:

Device(config-controller)# lte sim max-retry 20

(Optional) Specifies the maximum number of failover retries from 1 to 65535. The default value is 10.

Step 5

lte failovertimer timeout-period
Example:

Device(config-controller)# lte failovertimer 6

(Optional) By default, the failover time period is 2 minutes before the primary SIM switches over to the secondary SIM if service becomes unavailable.

Specify a failover timeout value between 1 and 7 minutes before a switchover occurs.
Step 6
lte sim profile number [ims number] slot {0 | 1}
Example:

Device(config-controller)# lte sim profile 1 ims 2 slot 0
Device(config-controller)# lte sim profile 3 ims 4 slot 1
Applies the configured profile number to the SIM and its slot number. The default (primary) slot is 0.

You must also identify the primary and secondary SIM for the configured profile when two SIMs are presented.
Note You can manually activate a SIM using the cellular 0 lte sim activate slot <0 or 1> command.

Configuration Examples

The following example shows how to configure a dual SIM:
router# configure terminal
router(config)# controller Cellular 0
router(config-controller)# lte sim profile 1 ims 1 slot 0
router(config-controller)# lte sim profile 2 ims 2 slot 1
router(config-controller)# lte sim primary slot 1
router(config-controller)# lte sim max-retry 20
router(config-controller)# lte sim failovertimer 5
The following example shows how to display an active profile on a SIM:
router#show cellular 0 profile
Profile Information
====================
Profile 1 = INACTIVE
--------
PDP Type = IPv4
Access Point Name (APN) = internet.telenor.se
Profile 2 = ACTIVE* **
--------
PDP Type = IPv4
PDP address = 78.78.16.214
Access Point Name (APN) = telia.online.se
        Primary DNS address = 195.67.199.18
        Secondary DNS address = 195.67.199.19
  * - Default profile
 ** - LTE attach profile
Configured default profile for active SIM 1 is profile 2.
The following example shows how to display the status of a dual SIM:
router#show cellular 0 security
Active SIM = 0
SIM switchover attempts = 0
Card Holder Verification (CHV1) = Disabled
SIM Status = OK
SIM User Operation Required = None
Number of CHV1 Retries remaining = 3
router#
The following example shows how to display the status of a dual SIM:
router#show controller cellular 0
Interface Cellular0
4G WWAN Modem - Global Multimode LTE/DC-HSPA+/HSPA+/HSPA/UMTS/EDGE/GPRS 
Cellular modem configuration
======================================
Modem is recognized as valid
manufacture id:  0x00001199     product id: 0x000068A2
Power status: Active
Sierra Wireless Direct IP MC7710 modem
:
:
Cellular Dual SIM details:
---------------------------
SIM 0 is present
SIM 1 is present
SIM 0 is active SIM
Data Call Setup

To set up a data call, use the following procedures:

•Configuring the Cellular Interface

•Configuring DDR

•Configuring DDR Backup

Figure 3 shows a typical data call setup.

Figure 3 Data Call Setup with EHWIC-4G-LTE

Configuring the Cellular Interface

To configure the cellular interface, enter the following commands starting in EXEC mode.

Note For the EHWIC, the unit argument identifies the router slot, WIC slot, and port separated by slashes (0/0/0). For the Cisco 819 ISR fixed platform, the unit argument identifies slot "0" for all commands.

Note Starting from Cisco IOS Release 15.3(3)M and 15.3(1)T, the chat-script configuration, including dialer in-band, dialer string, and script dialer, is auto-generated based on the modem type plugged in. The 3G and 4G HWIC SKUs and the fixed 3G and 4G routers support these configuration changes.

SUMMARY STEPS

1. configure terminal

2. interface cellular unit

3. ip address negotiated

or

ip address ip-address mask

4. encapsulation slip

5. dialer in-band

6. dialer string string

7. dialer-group group-number

8. exit

9. chat-script script-name "" "AT!CALL" TIMEOUT timeout-value "OK"

10. ip route network-number network-mask {ip-address | interface} [administrative distance] [name name]

11. dialer-list dialer-group protocol protocol-name {permit | deny | list access-list-number | access-group}

12. line unit

13. script dialer regular-expression

DETAILED STEPS

Command or Action

Purpose

Step 1

configure terminal
Example:

Device# configure terminal

Enters global configuration mode.

Step 2

interface cellular unit
Example:

Device(config)# interface cellular 0/0/0

Specifies the cellular interface.

Step 3

ip address negotiated
or

ip address ip-address mask
Example:

Device(config-if)# ip address negotiated
or

Example:

Device(config-if)# ip address 10.4.0.254 255.255.0.0

Specifies that the IP address for a particular interface is dynamically obtained.

Step 4

encapsulation slip
Example:

Device(config-if)# encapsulation slip

Specifies Serial Line Internet Protocol (SLIP) encapsulation for an interface configured for dedicated asynchronous mode or dial-on-demand routing (DDR). This is the default for asynchronous interfaces.

Step 5

dialer in-band
Example:

Device(config-if)# dialer in-band

Enables DDR and configures the specified serial interface to use in-band dialing.

Step 6

dialer string string
Example:

Device(config-if)# dialer string lte

Specifies the number or string to dial.

Step 7

dialer-group group-number
Example:

Device(config-if)# dialer-group 1

Specifies the number of the dialer access group to which the specific interface belongs.

Step 8

exit
Example:

Device(config-if)# exit

Enters the global configuration mode.

Step 9

chat-script script-name "" "AT!CALL" TIMEOUT timeout-value "OK"
Example:

Device(config)# chat-script lte"" "AT!CALL" TIMEOUT 60 "OK"

Defines the ATDT commands when the dialer is initiated.

Step 10

ip route network-number network-mask {ip-address | interface} [administrative distance] [name name]
Example:

Device(config)# ip route 209.165.200.225 255.255.255.224 cellular 0/0/0

Establishes a floating static route with the configured administrative distance through the specified interface.

Note A higher administrative distance should be configured for the route through the backup interface so that it is used only when the primary interface is down.

Step 11

dialer-list dialer-group protocol protocol-name {permit | deny | list access-list-number | access-group}
Example:

Device(config)# dialer-list 1 protocol ip list 1

Creates a dialer list for traffic of interest and permits access to an entire protocol.

Step 12

line unit
Example:

Device(config)# line 0/0/0

Specifies the line configuration mode.

Step 13

script dialer regular-expression
Example:

Device(config-line)# script dialer lte

Specifies a default modem chat script.

Note When a static IP address is required for the cellular interface, the address may be configured as ip address negotiated. The network ensures that the correct static IP address is allocated to the device. If a tunnel interface is configured with ip unnumbered cellular 0/0/0, it is necessary to configure the actual static IP address under the cellular interface, in place of ip address negotiated. For a sample cellular interface configuration, see the "Example: Basic Cellular Interface Configuration: EHWIC-4G-LTE" section.

Configuring DDR

To configure DDR for the cellular interface, enter the following commands starting in EXEC mode.

Note For the EHWIC, the unit argument identifies the router slot, WIC slot, and port separated by slashes (0/0/0). For the Cisco 819 ISR fixed platform, the unit argument identifies slot "0" for all commands.

SUMMARY STEPS

1. configure terminal

2. interface cellular unit

3. ip address negotiated

or

ip address ip-address mask

4. encapsulation slip

5. dialer in-band

6. dialer pool-member number

7. interface dialer number

8. ip address negotiated

9. encapsulation slip

10. dialer pool number

11. dialer idle-timeout seconds

12. dialer string string

13. dialer-group group-number

14. exit

15. dialer-list dialer-group protocol protocol-name {permit | deny | list access-list-number | access-group}

16. access-list access-list-number permit ip-source-address

17. line unit

18. script dialer regular-expression

19. exit

20. chat-script script-name "" "AT!CALL" TIMEOUT timeout-value "OK"

DETAILED STEPS

Command or Action

Purpose

Step 1

configure terminal
Example:

Device# configure terminal

Enters global configuration mode.

Step 2

interface cellular unit
Example:

Device(config)# interface cellular 0/0/0

Specifies the cellular interface.

Step 3

ip address negotiated
or

ip address ip-address mask
Example:

Device(config-if)# ip address negotiated
or

Example:

Device(config-if)# ip address 10.4.0.254 255.255.0.0

Specifies that the IP address for a particular interface is dynamically obtained.

Step 4

encapsulation slip
Example:

Device(config-if)# encapsulation slip

Specifies Serial Line Internet Protocol (SLIP) encapsulation for an interface configured for dedicated asynchronous mode or dial-on-demand routing (DDR). This is the default for asynchronous interfaces.

Step 5

dialer in-band
Example:

Device(config-if)# dialer in-band

Enables DDR and configures the specified serial interface to use in-band dialing.

Step 6

dialer pool-member number
Example:

Device(config-if)# dialer pool-member 1

Specifies the number of a dialer profile's dialing pool to which the specific interface belongs.

Step 7

interface dialer number
Example:

Device(config-if)# interface dialer 1

Specifies the number of a dialer rotary group to which the specific interface belongs.

Step 8

ip address negotiated
Example:

Device(config-if)# ip address negotiated

Specifies that the IP address for a particular interface is dynamically obtained.

Step 9

encapsulation slip
Example:

Device(config-if)# encapsulation slip

Specifies Serial Line Internet Protocol (SLIP) encapsulation for an interface configured for dedicated asynchronous mode or dial-on-demand routing (DDR). This is the default for asynchronous interfaces.

Step 10

dialer pool number
Example:

Device(config-if)# dialer pool 1

Specifies the number of a dialing pool that the dialer interface can use to connect to a specific destination subnetwork.

Step 11

dialer idle-timeout seconds
Example:

Device(config-if)# dialer idle-timeout 30

Specifies the duration of idle time, in seconds, after which a line will be disconnected.

Step 12

dialer string string
Example:

Device(config-if)# dialer string lte

Specifies the number or string to dial.

Step 13

dialer-group group-number
Example:

Device(config-if)# dialer-group 1

Specifies the number of the dialer access group to which the specific interface belongs.

Step 14

exit
Example:

Device(config-if)# exit

Enters the global configuration mode.

Step 15

dialer-list dialer-group protocol protocol-name {permit | deny | list access-list-number | access-group}
Example:

Device(config)# dialer-list 1 protocol ip list 1

Creates a dialer list for traffic of interest and permits access to an entire protocol.

Step 16

access-list access-list-number permit ip-source-address
Example:

Device(config)# access-list 1 permit any

Defines traffic of interest.

Step 17

line unit
Example:

Device(config)# line 0/0/0

Specifies the line configuration mode.

Step 18

script dialer regular-expression
Example:

Device(config-line)# script dialer lte

Specifies a default modem chat script.

Step 19

exit
Example:

Device(config-line)# exit

Exits line configuration mode.

Step 20

chat-script script-name "" "AT!CALL" TIMEOUT timeout-value "OK"
Example:

Device(config)# chat-script lte"" "AT!CALL" TIMEOUT 60 "OK"

Defines the ATDT commands when the dialer is initiated.

Configuring DDR Backup

To monitor the primary connection and initiate the backup connection when needed, the router can use one of the following methods:

•Backup Interface—The backup interface that stays in standby mode until the primary interface line protocol is detected as down and then is brought up.

•Floating Static Route—The route through the backup interface has an administrative distance that is greater than the administrative distance of the primary connection route and therefore would not be in the routing table until the primary interface goes down.

•Dialer Watch—Dialer watch is a backup feature that integrates dial backup with routing capabilities.

Configuring Interfaces to Use a Backup Interface

Note You cannot configure a backup interface for the cellular interface and any other asynchronous serial interface.

To configure one or more interfaces to use a backup interface, use the following commands, beginning in global configuration mode.

SUMMARY STEPS

1. interface type number

2. backup interface cellular number

3. backup delay enable-delay-period disable-delay-period

DETAILED STEPS

Command or Action

Purpose

Step 1

interface type number
Example:

Device(config)# interface atm 0/0/0

Specifies the interface to be backed up and begins interface configuration mode.

Step 2

backup interface cellular number
Example:

Device(config-if)# backup interface cellular 0/0/0

Specifies the cellular interface as backup.

Step 3

backup delay enable-delay-period disable-delay-period
Example:

Device(config-if)# backup delay 0 10

Specifies delay between the physical interface going down and the backup interface being enabled and between the physical interface coming back up and the backup being disabled.

Enabling 4G GPS and NMEA Data Streaming

GPS NMEA data streaming to external NMEA 2.0-compliant GPS plotter applications can be enabled on 4G EHWIC modems and Cisco 819HG-4G and Cisco 819(H)G-4G LTE ISRs.

Note For an EHWIC, the unit argument identifies the router slot, WIC slot, and the port, and is separated by slashes (0/0/0). For the Cisco 819 ISR fixed platform, the unit argument identifies slot 0 for all commands.

SUMMARY STEPS

1. configure terminal

2. controller cellular unit

3. (Optional) lte gps enable

4. lte gps mode standalone

5. lte gps nmea {ip | serial [streaming]} (Cisco 819 ISR)
or
lte gps nmea (4G EHWIC)

6. end

7. show cellular unit gps

8. show cellular unit gps detail

9. show running

10. show line

11. telnet ip address port

DETAILED STEPS
Command

Description

Step 1

configure terminal
Example:

Device# configure terminal

Enters the configuration mode.

Step 2

controller cellular unit
Example:

Device(config)# controller cellular 0

Enters the controller cellular configuration mode.

Step 3

lte gps enable
Example:

Device(config-controller)# lte gps enable

(Optional) GPS is enabled by default. Use this command to enable the GPS feature if GPS has been disabled for any reason.

Step 4

lte gps mode standalone
Example:

Device(config-controller)# lte gps mode standalone

Enables the standalone GPS mode.
Step 5
lte gps nmea {ip | serial [streaming]} (Cisco 819 ISR)
or
lte gps nmea (4G EHWIC)
Example:

Device(config-controller)# lte gps nmea ip
Enables NMEA streaming.

The Cisco 4G LTE EHWIC supports only IP NMEA streaming. Therefore, the IP interface and serial interface options are unavailable.

The Cisco 819HG-4G and Cisco 819G-4G LTE ISRs support the following NMEA streaming options:

• ip—NMEA over IP interface.

•serial—NMEA over serial interface.

•streaming—Parameters are: 38400 (bps baud rate), 4800 (bps baud rate, which is the default) line-config (use tty line configuration).
Step 6

end
Example:

Device(config-controller)# end

Exits the controller configuration mode and returns to the privileged EXEC mode.

Step 7

show cellular unit gps
Example:

Device# show cellular 0/0/0 gps

GPS Info
-------------
GPS Feature: enabled
GPS Port Selected: DIV port
GPS State: GPS enabled
GPS Mode Configured: standalone
Last Location Fix Error: Offline [0x0]
GPS Error Count: 13
Latitude: 37 Deg 24 Min 58 Sec North
Longitude: 121 Deg 55 Min 7 Sec West
Timestamp (GMT): Thu Aug 15 14:23:35 2013

Fix type index: 0, Height: 15 m

Displays a summary of the following GPS data:

•GPS state information (GPS disabled, GPS acquiring, GPS enabled)

•GPS mode configured (standalone)

•GPS location and timestamp information

•GPS satellite information

•GPS feature (enabled or disabled)

•GPS port selected (Dedicated GPS and GPS port with voltage-no-bias)
Step 8
show cellular unit gps detail
Example:
Device# show cellular 0 gps detail
GPS Info
-------------
GPS Feature: enabled
GPS Port Selected: DIV port
GPS State: GPS enabled
GPS Mode Configured: standalone
Last Location Fix Error: Offline [0x0]
GPS Error Count: 71
Latitude: 37 Deg 24 Min 58 Sec North
Longitude: 121 Deg 55 Min 7 Sec West
Timestamp (GMT): Fri Aug 16 10:46:25 2013

Fix type index: 0, Height: 20 m
HDOP: 0.8, GPS Mode Used: standalone

Satellite Info
----------------
Satellite #1, elevation 18, azimuth 52, SNR 30 *
Satellite #4, elevation 13, azimuth 165, SNR 29 *
Satellite #7, elevation 3, azimuth 133, SNR 22
Satellite #8, elevation 33, azimuth 126, SNR 29 *
Satellite #9, elevation 33, azimuth 133, SNR 0 *
Satellite #11, elevation 4, azimuth 39, SNR 0
Satellite #15, elevation 29, azimuth 284, SNR 0 *
Satellite #17, elevation 84, azimuth 118, SNR 0 *
Satellite #26, elevation 38, azimuth 224, SNR 0
Displays detailed GPS data.
Step 9

show running config
Example:

Device# show running config

!
controller Cellular 0
lte gps mode standalone
lte gps nmea ip
!

Shows the output of the configuration.

Step 10

show line
Example:

Device# show line
Tty Typ Tx/Rx A Modem Roty AccO AccI Uses Noise Overruns Int
* 0 CTY - - - - - 0 0 0/0 -
1 AUX 0/0 - - - - - 0 0 0/0 -
2 TTY 9600/9600 - - - - - 0 0 0/0 -
I 3 TTY - inout - - - 0 0 0/0 Ce0
I 6 TTY - inout - - - 0 24101 0/0 NM0/0/5
10 VTY - - - - - 0 0 0/0 -
11 VTY - - - - - 0 0 0/0 -
12 VTY - - - - - 0 0 0/0 -
13 VTY - - - - - 0 0 0/0 -
14 VTY - - - - - 0 0 0/0 -

Line(s) not in async mode -or- with no hardware support:
4-5, 7-9

Shows the async port number.

After NMEA is configured, Cisco IOS creates a n NMEA async port. The port number is platform dependent. In this example, the async port number is line 6.

Step 11

telnet ip address port
Example:

Device#telnet 10.1.1.1 2006
Trying 10.1.1.1, 2006 ... Open
$GPRMC,,V,,,,,,,,,,N*53
$GPGSV,3,1,11,01,17,049,34,04,16,164,30,08,29,129,32 ,09,29,136,38*70
$GPGSV,3,2,11,15,29,281,37,17,83,073,36,28,,,41,07,0 0,135,*4B
$GPGSV,3,3,11,11,01,037,,12,00,272,,24,18,313,*46
$GLGSV,2,1,08,78,23,323,27,86,25,030,27,77,67,014,25 ,76,37,112,32*6D
$GLGSV,2,2,08,88,39,203,32,87,81,070,31,68,01,292,34 ,69,,,*5A
$GPGGA,185555.0,3724.984762,N,12155.122163,W,1,04,13 .3,23.2,M,-27.0,M,,*6A
$PQXFI,185555.0,3724.984762,N,12155.122163,W,23.2,26 4.53,176.14,9.08*46
$GNGNS,185555.0,3724.984762,N,12155.122163,W,AN,04,1 3.3,23.2,-27.0,,*51
$GPVTG,,T,,M,,N,,K,N*2C
$GPRMC,185555.0,A,3724.984762,N,12155.122163,W,,,160 813,,,A*7B
$GPGSA,A,3,08,09,15,17,,,,,,,,,16.2,13.3,9.2*3E
$GNGSA,A,3,08,09,15,17,,,,,,,,,16.2,13.3,9.2*20
$GNGSA,A,3,,,,,,,,,,,,,16.2,13.3,9.2*23

After NMEA streaming is enabled, the modem starts to stream NMEA data over the NMEA port regardless of whether the GPS fix is acquired or not. You can reverse Telnet to the NMEA port to check the NMEA data.
Configuring 4G SMS Messaging

Note In the context of an EHWIC, the unit argument identifies the router slot, WIC slot, and the port, and is separated by slashes (0/0/0). For the Cisco 819 ISR fixed platform, the unit argument identifies slot 0 for all commands.

SUMMARY STEPS

1. configure terminal

2. controller cellular unit

3. lte sms archive path FTP-URL

4. cellular unit lte sms view {all | ID | summary}

5. end

6. show cellular unit sms

7. cellular unit lte sms send number

8. cellular unit lte sms delete [all | id]

DETAILED STEPS
Command

Description

Step 1

configure terminal
Example:

Device# configure terminal

Enters the configuration mode.

Step 2

controller cellular unit
Example:

Device(config)# controller cellular 0/1/0

Enters the controller cellular configuration mode.

Step 3

lte sms archive path FTP-URL
Example:

Device(config-controller)# lte sms archive path ftp://username:password@172.25.211.175/SMS-LTE

Specifies an FTP server folder path to send all the incoming and outgoing SMS messages. After the folder path is identified, it is appended automatically with outbox and inbox folders for the path to which SMS messages are sent and received, for example:

ftp://172.25.211.175/SMS-LTE/outbox
ftp://172.25.211.175/SMS-LTE/inbox
Step 4
cellular unit lte sms view {all | ID | summary}
Example:
evice# cellular 0/0/0 lte sms view summary
ID   FROM                  YY/MM/DD HR:MN:SC  SIZE  
CONTENT
0	 4442235525            12/05/29 10:50:13  137   
Your entry last month has...
2    5553337777            13/08/01 10:24:56  5     
First                       
3    5553337777            13/08/01 10:25:02  6     
Second 
Displays the message contents of incoming texts received by a modem.

•all—Displays the message contents of up to 255 incoming text messages received by the modem.

•ID—Displays the message contents for a specified ID (0-255) of an incoming text message.

•summary—Displays a summary of the incoming text messages received by the modem.
Step 5

end
Example:

Device(config)# end

Exits the configuration mode and returns to the privileged EXEC mode.

Step 6

show cellular unit sms
Example:

Device#show cellular 0/0/0 sms
Incoming Message Information
----------------------------
SMS stored in modem = 20
SMS archived since booting up = 0
Total SMS deleted since booting up = 0
Storage records allocated = 25
Storage records used = 20
Number of callbacks triggered by SMS = 0
Number of successful archive since booting up = 0
Number of failed archive since booting up = 0

Outgoing Message Information
----------------------------
Total SMS sent successfully = 0
Total SMS send failure = 0
Number of outgoing SMS pending = 0
Number of successful archive since booting up = 0
Number of failed archive since booting up = 0
Last Outgoing SMS Status = SUCCESS
Copy-to-SIM Status = 0x0
Send-to-Network Status = 0x0
Report-Outgoing-Message-Number:
Reference Number = 0
Result Code = 0x0
Diag Code = 0x0 0x0 0x0 0x0 0x0

SMS Archive URL = ftp://lab:lab@1.3.150.1/outbox

Displays all the information in the text messages sent and received. Message information includes text messages sent successfully, received, archived, and messages pending to be sent. LTE-specific information on errors in case of a FAILED attempt may also be displayed.

Step 1

cellular unit lte sms send number
Example:

Device# cellular 0/1/0 lte sms send 15554443333

Enables a user to send a 4G LTE band SMS message to other valid recipients, provided they have a text message plan. The number argument is the telephone number of the SMS message recipient.

Note 10-digit or 11-digit (phone) numbers are the proper numerical format for sending a text. For example, ########## or 1##########. Seven digits are not supported.

Step 2

cellular unit lte sms delete [all | id]
Example:

Device# cellular 0/1/0 lte sms delete all

(Optional) Deletes one message ID or all of the stored messages from memory.
Configuration Examples for 4G LTE

•Example: Basic Cellular Interface Configuration: EHWIC-4G-LTE

•Example: Basic Cellular Interface Configuration: Cisco 819 ISR

•Cellular Interface Configuration for Always-On Connection

•Example: GRE Tunnel over Cellular Interface Configuration

•4G-LTE Wireless WAN as Backup with NAT and IPSec

•SIM Configuration: Examples

•SMS Initiated Call Back Configuration: Example

•Dialer-Watch Configuration without External Dialer Interface: Example

•Dialer-Persistent Configuration with External Dialer Interface: Example

Example: Basic Cellular Interface Configuration: EHWIC-4G-LTE

The following example shows how to configure the cellular interface to be used as a primary and is configured as the default route:
Device# show running-config
chat-script lte "" "AT!CALL" TIMEOUT 20 "OK"
interface Cellular0/0/0
ip address negotiated
encapsulation slip
dialer in-band
dialer string lte
dialer-group 1
async mode interactive
ip route 172.22.1.10 255.255.255.255 cellular 0/0/0
dialer-list 1 protocol ip permit
line 0/0/0
script dialer lte
modem InOut
Example: Basic Cellular Interface Configuration: Cisco 819 ISR

The following example shows how to configure the cellular interface to be used as primary and is configured as the default route:
chat-script lte "" "AT!CALL1" TIMEOUT 20 "OK"
!
!
controller Cellular 0
!         
!
interface Cellular0
 ip address negotiated
 encapsulation slip
 load-interval 30
 dialer in-band
 dialer idle-timeout 0
 dialer string lte
 dialer-group 1
 no peer default ip address
 async mode interactive
 routing dynamic
!
ip route 172.22.1.10 255.255.255.255 cellular 0/0/0
!
dialer-list 1 protocol ip permit
!
line 3
 script dialer lte
 modem InOut
 no exec
 transport input all
 transport output all
!
Cellular Interface Configuration for Always-On Connection

This section provides the following configuration examples:

•Dialer-Watch Configuration without External Dialer Interface

•Dialer-Persistent Configuration with External Dialer Interface

Dialer-Watch Configuration without External Dialer Interface

The following example shows how to configure dialer-watch without external dialer interface. The bold text is used to indicate important commands that are specific to dialer-watch.
chat-script lte "" "AT!CALL" TIMEOUT 20 "OK" 
interface Cellular0/0/0
 ip address negotiated
 encapsulation slip
 dialer in-band
 dialer string LTE
 dialer watch-group 1
 async mode interactive
!
dialer watch-list 1 ip 5.6.7.8 0.0.0.0
dialer watch-list 1 delay route-check initial 60
dialer watch-list 1 delay connect 1
!
ip route 0.0.0.0 0.0.0.0 cellular 0/0/0
line 0/0/0
 script dialer LTE
 modem InOut
 no exec
 transport input all
 transport output all
Dialer-Persistent Configuration with External Dialer Interface

The following example shows how to configure dialer-persistent with external dialer interface. The bold text is used to indicate important commands that are specific to dialer-persistent.
chat-script lte "" "AT!CALL" TIMEOUT 20 "OK"
interface Cellular0/0/0
 ip address negotiated
  encapsulation slip
 dialer in-band
 dialer pool-member 1
 async mode interactive
 routing dynamic
interface Dialer1
ip address negotiated
encapsulation slip
 dialer pool 1
 dialer idle-timeout 0
 dialer string lte
 dialer persistent
 dialer-group 1
!
dialer-list 1 protocol ip permit
ip route 0.0.0.0 0.0.0.0 dialer 1
line 0/0/0
 script dialer lte
 modem InOut
 no exec
 transport input all
 transport output all
Example: GRE Tunnel over Cellular Interface Configuration

The following example shows how to configure the static IP address when a GRE tunnel interface is configured with ip address unnumbered cellular interface:

Note The GRE tunnel configuration is supported only if the service providers provide a public IP address on the LTE interface.

Note For service providers using a private IP address, the point-to-point static GRE tunnel cannot be set up with a private IP address at one end and a public IP address on the other end.
interface Tunnel2 
ip unnumbered <internal LAN interface GE0/0 etc.> 
tunnel source Cellular0
tunnel destination a.b.c.d 
interface Cellular0 
ip address negotiated 
encapsulation slip 
no ip mroute-cache 
dialer in-band 
dialer string lte 
dialer-group 1 
async mode interactive
4G-LTE Wireless WAN as Backup with NAT and IPSec

The following example shows how to configure the 4G-LTE wireless WAN on the router as backup with NAT and IPSec:

Note The receive and transmit speeds cannot be configured. The actual throughput depends on the cellular network service.
ip dhcp excluded-address 10.4.0.254
!
ip dhcp pool lan-pool
   network 10.4.0.0 255.255.0.0
   dns-server 10.4.0.254 
   default-router 10.4.0.254 
!
!
chat-script lte "" "AT!CALL" TIMEOUT 20 "OK"
crypto isakmp policy 1
 encr 3des
 authentication pre-share
crypto isakmp key  address a.b.c.d
!
!
crypto ipsec transform-set  ah-sha-hmac esp-3des 
!
crypto map gsm1 10 ipsec-isakmp 
 set peer a.b.c.d
 set transform-set  
 match address 103
!
!
interface ATM0/0/0
 no ip address
 ip virtual-reassembly
 load-interval 30
 no atm ilmi-keepalive
 dsl operating-mode auto 
!
interface ATM0/0/0.1 point-to-point
 backup interface Cellular0/3/0
 ip nat outside
 ip virtual-reassembly
 no snmp trap link-status
 pvc 0/35 
  pppoe-client dial-pool-number 2
 !
!
interface Cellular0/3/0
 ip address negotiated
 ip nat outside
 ip virtual-reassembly
 encapsulation slip
 no ip mroute-cache
 dialer in-band
 dialer idle-timeout 0
 dialer string lte
 dialer-group 1
 async mode interactive
 crypto map gsm1
!
interface Vlan104
 description used as default gateway address for DHCP clients
 ip address 10.4.0.254 255.255.0.0
 ip nat inside
 ip virtual-reassembly
!
interface Dialer2
 ip address negotiated
 ip mtu 1492
 ip nat outside
 ip virtual-reassembly
 encapsulation ppp
 load-interval 30
 dialer pool 2
 dialer-group 2
 ppp authentication chap callin
 ppp chap hostname cisco@dsl.com
 ppp chap password 0 cisco
 ppp ipcp dns request
 crypto map gsm1
!
ip local policy route-map track-primary-if
ip route 0.0.0.0 0.0.0.0 Dialer2 track 234
ip route 0.0.0.0 0.0.0.0 Cellular0/3/0 254
!
!
ip nat inside source route-map nat2cell interface Cellular0/3/0 overload
ip nat inside source route-map nat2dsl interface Dialer2 overload
!
ip sla 1
 icmp-echo 2.2.2.2 source-interface Dialer2
 timeout 1000
 frequency 2
ip sla schedule 1 life forever start-time now
access-list 1 permit any
access-list 101 deny ip 10.4.0.0 0.0.255.255 10.0.0.0 0.255.255.255
access-list 101 permit ip 10.4.0.0 0.0.255.255 any
access-list 102 permit icmp any host 2.2.2.2
access-list 103 permit ip 10.4.0.0 0.0.255.255 10.0.0.0 0.255.255.255
dialer-list 1 protocol ip list 1
dialer-list 2 protocol ip permit
!
!
route-map track-primary-if permit 10
 match ip address 102
 set interface Dialer2
!
route-map nat2dsl permit 10
 match ip address 101
 match interface Dialer2
!
route-map nat2cell permit 10
 match ip address 101
 match interface Cellular0/3/0
!
line 0/3/0
 exec-timeout 0 0
 script dialer lte 
 login
 modem InOut
Note For service providers using a private IP address, use the crypto ipsec transform-set esp command (that is, esp-aes esp-sha256-hmac...).

SIM Configuration: Examples

•Locking the SIM Card: Example

•Unlocking the SIM Card: Example

•Automatic SIM Authentication: Example

•Changing the PIN Code: Example

•Configuring an Encrypted PIN: Example

Locking the SIM Card: Example

The following example shows how to lock the SIM. The italicized text in this configuration example is used to indicate comments and are not be seen when a normal console output is viewed.
Device# sh cellular 0/0/0 security 
Card Holder Verification (CHV1) = Disabled
SIM Status = OK
SIM User Operation Required = None
Number of CHV1 Retries remaining = 3
Device#
!
!	SIM is in unlocked state.
!
Device# cellular 0/0/0 lte sim lock 1111
!!!WARNING: SIM will be locked with pin=1111(4). 
Do not enter new PIN to lock SIM. Enter PIN that the SIM is configured with.
Call will be disconnected!!!
Are you sure you want to proceed?[confirm]
Device#
Apr 26 19:35:28.339: %CELLWAN-2-MODEM_DOWN: Modem in HWIC slot 0/0 is DOWN
Apr 26 19:35:59.967: %CELLWAN-2-MODEM_UP: Modem in HWIC slot 0/0 is now UP
Device#
Device# sh cellular 0/0/0 security 
Card Holder Verification (CHV1) = Enabled
SIM Status = Locked
SIM User Operation Required = Enter CHV1
Number of CHV1 Retries remaining = 3
Device#
!
!	SIM is in locked state.
!
Unlocking the SIM Card: Example

The following example shows how to unlock the SIM. The italicized text throughout this configuration example is used to indicate comments and will not be seen when a normal console output is viewed.
Device# sh cellular 0/0/0 security 
Card Holder Verification (CHV1) = Enabled
SIM Status = Locked
SIM User Operation Required = Enter CHV1
Number of CHV1 Retries remaining = 3
Device#
!
!	SIM is in locked state.
!
Device# cellular 0/0/0 lte sim unlock 1111
!!!WARNING: SIM will be unlocked with pin=1111(4). 
Do not enter new PIN to unlock SIM. Enter PIN that the SIM is configured with.
Call will be disconnected!!!
Are you sure you want to proceed?[confirm]
Device#
Device# sh cellular 0/0/0 security 
Card Holder Verification (CHV1) = Disabled
SIM Status = OK
SIM User Operation Required = None
Number of CHV1 Retries remaining = 3
Device#
!
!	SIM is in unlocked state.
!
Automatic SIM Authentication: Example

The following example shows how to configure automatic SIM authentication. The italicized text throughout this configuration example is used to indicate comments and will not be seen when a normal console output is viewed.
Device# show cellular 0/0/0 security 
Card Holder Verification (CHV1) = Disabled
SIM Status = OK
SIM User Operation Required = None
Number of CHV1 Retries remaining = 3
Device#
!
!	SIM is in unlocked state.
!
Device# cellular 0/0/0 lte sim lock 1111
!!!WARNING: SIM will be locked with pin=1111(4). 
Do not enter new PIN to lock SIM. Enter PIN that the SIM is configured with.
Call will be disconnected!!!
Are you sure you want to proceed?[confirm]
Device#
Apr 26 21:22:34.555: %CELLWAN-2-MODEM_DOWN: Modem in HWIC slot 0/0 is DOWN
Apr 26 21:23:06.495: %CELLWAN-2-MODEM_UP: Modem in HWIC slot 0/0 is now UP
Device#
Device# sh cellular 0/0/0 security 
Card Holder Verification (CHV1) = Enabled
SIM Status = Locked
SIM User Operation Required = Enter CHV1
Number of CHV1 Retries remaining = 3
Device#
!
!	SIM is in locked state. SIM needs to be in locked state for SIM authentication to 
!	work.
!
Device#
Device# conf term
Enter configuration commands, one per line.  End with CNTL/Z.
Device(config)# controller cellular 0/0
Device(config-controller)# lte sim authenticate 0 1111 
CHV1 configured and sent to modem for verification
Device(config-controller)# end
Device#
Apr 26 21:23:50.571: %SYS-5-CONFIG_I: Configured from console by console
Device#
Device# sh cellular 0/0/0 security 
Card Holder Verification (CHV1) = Enabled
SIM Status = OK
SIM User Operation Required = None
Number of CHV1 Retries remaining = 3
Device#
!
!	SIM is now in locked state but it can be used for connectivity since authentication is 
!	good. Authentication can be saved in the router configuration so that when you boot up 
!	the router with the same locked SIM, connection can be established with the correct 
!	Cisco IOS configuration.
!
Changing the PIN Code: Example

The following example shows how to change the assigned PIN code. The italicized text throughout this configuration example is used to indicate comments and will not be seen when a normal console output is viewed.
Device# sh cellular 0/0/0 security 
Card Holder Verification (CHV1) = Disabled
SIM Status = OK
SIM User Operation Required = None
Number of CHV1 Retries remaining = 3
Device#
!
!	SIM is in unlocked state.
!
Device#
Device# cellular 0/0/0 lte sim lock 1111
!!!WARNING: SIM will be locked with pin=1111(4). 
Do not enter new PIN to lock SIM. Enter PIN that the SIM is configured with.
Call will be disconnected!!!
Are you sure you want to proceed?[confirm]
Device#
Apr 26 21:58:11.903: %CELLWAN-2-MODEM_DOWN: Modem in HWIC slot 0/0 is DOWN
Apr 26 21:58:43.775: %CELLWAN-2-MODEM_UP: Modem in HWIC slot 0/0 is now UP
Device#
Device# sh cellular 0/0/0 security 
Card Holder Verification (CHV1) = Enabled
SIM Status = Locked
SIM User Operation Required = Enter CHV1
Number of CHV1 Retries remaining = 3
Device#
!
!	SIM is in locked state. SIM needs to be in locked state to change its PIN.
!
Device#
Device# cellular 0/0/0 lte sim change-pin 1111 0000
!!!WARNING: SIM PIN will be changed from:1111(4) to:0000(4)
Call will be disconnected. If old PIN is entered incorrectly in 3 attempt(s), SIM will be 
blocked!!!
Are you sure you want to proceed?[confirm]
Resetting modem, please wait...
CHV1 code change has been completed. Please enter the new PIN in controller configuration 
for verfication
Device#
Apr 26 21:59:16.735: %CELLWAN-2-MODEM_DOWN: Modem in HWIC slot 0/0 is DOWN
Apr 26 21:59:48.387: %CELLWAN-2-MODEM_UP: Modem in HWIC slot 0/0 is now UP
Device#
Device#
Device# sh cellular 0/0/0 security 
Card Holder Verification (CHV1) = Enabled
SIM Status = Locked
SIM User Operation Required = Enter CHV1
Number of CHV1 Retries remaining = 3
Device#
!
!	SIM stays in locked state, as expected, but with new PIN.
!
Device# cellular 0/0/0 lte sim unlock 0000
!!!WARNING: SIM will be unlocked with pin=0000(4). 
Do not enter new PIN to unlock SIM. Enter PIN that the SIM is configured with.
Call will be disconnected!!!
Are you sure you want to proceed?[confirm]
Device#
Device# show cellular 0/0/0 security 
Card Holder Verification (CHV1) = Disabled
SIM Status = OK
SIM User Operation Required = None
Number of CHV1 Retries remaining = 3
Device#
!
!	Unlock with new PIN is successful. Hence, changing PIN was successful.
!
Configuring an Encrypted PIN: Example

The following example shows how to configure automatic SIM authentication using an encrypted PIN. The italicized text throughout this configuration example is used to indicate comments and will not be seen when a normal console output is viewed.
Device# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Device(config)# service password-encryption
Device(config)# username SIM privilege 0 password 1111
Device(config)# do sh run | i SIM
username SIM privilege 0 password 7 055A575E70.
!
!	Copy the encrypted level 7 PIN. Use this scrambled PIN in the SIM authentication 
!	command.
!
Device(config)#
Device(config)# controller cellular 0/0
Device(config-controller)# lte sim authenticate 7 055A575E70
CHV1 configured and sent to modem for verification
Device(config-controller)# exit
Device(config)# no username SIM
Device(config)# end
May 14 20:20:52.603: %SYS-5-CONFIG_I: Configured from console by console
SMS Initiated Call Back Configuration: Example

The following example shows how to configure SMS initiated data callback feature on a dialer interface to set up a data connection by sending a text message to the modem and securing the data connection by using the originating (caller's) number to eliminate unauthorized callback requests.

Note The "14001234567" phone number in the example below is the incoming caller's number.
chat-script lte "" "AT!CALL" TIMEOUT 20 "OK"
interface Cellular0/0/0 
ip address negotiated 
encapsulation slip 
dialer in-band 
dialer pool-member 1 
async mode interactive 
routing dynamic
!
interface Dialer1
ip address negotiated
encapsulation slip 
dialer pool 1 
dialer idle-timeout 0 
dialer string lte 
dialer caller 14001234567 callback
dialer-group 1
!
ip route 172.22.1.10 255.255.255.255 Cellular0/0/0
dialer-list 1 protocol ip permit
!
       line 0/0/0 
       script dialer LTE 
       modem InOut 
       no exec 
       transport input all 
       transport output all
Dialer-Watch Configuration without External Dialer Interface: Example

The following example shows how to configure the dialer-watch without external dialer interface. The bold text is used to indicate important commands that are specific to the dialer-watch:
chat-script lte "" "AT!CALL1" TIMEOUT 20 "OK" 
interface Cellular0
ip address negotiated 
encapsulation slip 
dialer in-band 
dialer string LTE 
dialer watch-group 1 
async mode interactive
!
dialer watch-list 1 ip 5.6.7.8 0.0.0.0
dialer watch-list 1 delay route-check initial 60
dialer watch-list 1 delay connect 1
!
ip route 0.0.0.0 0.0.0.0 cellular 0
line 3
script dialer LTE 
modem InOut 
no exec 
transport input all 
transport output all
Dialer-Persistent Configuration with External Dialer Interface: Example

The following example shows how to configure the dialer-persistent with external dialer interface. The bold text is used to indicate important commands that are specific to the dialer-persistent:
interface Cellular0
ip address negotiated 
encapsulation slip 
dialer in-band 
dialer pool-member 1 
async mode interactive 
routing dynamic
interface Dialer1
ip address negotiated
encapsulation slip 
dialer pool 1 
dialer idle-timeout 0 
dialer string lte 
dialer persistent 
dialer-group 1
!
dialer-list 1 protocol ip permit
ip route 0.0.0.0 0.0.0.0 dialer 1
line 3
script dialer lte 
modem InOut 
no exec 
transport input all 
transport output all
Upgrading the Modem Firmware

The modems described in Table 3 from Sierra Wireless can use the Cisco 4G-LTE EHWICs and Cisco WWAN 4G ISR model G2. The firmware for the modem is upgradable using Cisco IOS commands. The firmware is a Crossword Express file (cwe) and can be downloaded from the wireless software download page on Cisco.com.

Table 3 Modem SKUs and Associated Firmware

SKU

Modem

Firmware

EHWIC-4G-LTE-A, C819G-4G-A-K9 and C819HG-4G-A-K9

MC7700

FW 3.5.10.2

EHWIC-4G-LTE-G, C819G-4G-G-K9 and C819HG-4G-G-K9

MC7710

FW 3.5.19.4

EHWIC-4G-LTE-V, C819G-4G-V-K9 and C819HG-4G-V-K9

MC7750

FW 3.5.10.6

Caution Use only Cisco certified firmware. Using a firmware version not certified by Cisco may impact the wireless service provider network adversely.

Caution Do not disconnect power or switch the router off during the firmware upgrade process. This may result in permanent modem failure.

Note Firmware downgrade is not supported.

Note The 3.5.x firmware must have a 15.2(4)M3 or later software image.

Upgrading the Modem Firmware Manually

Cisco recommends the manual upgrade process for the LTE modem firmware and IOS software image for all new deployments and the following existing deployments:

•LTE is not the primary ISR WAN interface.

•LTE is not the only ISR WAN interface.

•The network administrator has out-of-band or local access to the ISR.

Note You can also remotely download firmware over the air by following the same steps listed below.

SUMMARY STEPS

Step 1 Go to the following Cisco web page to download the latest certified firmware for your carrier:

http://software.cisco.com/download/navigator.html

Note For remote download, you can transfer this using the 4G wireless link from Cisco.com onto flash. You must configure external dialer and dialer persistent to bring the interface and the dialer up again.

Step 2 On this page, select from the following options.
Products -> Cisco Interfaces and Modules -> Cisco High-Speed WAN Interface Cards

Step 3 After clicking on the Cisco High-Speed WAN interface Cards selection, a list of available cards displays in the third column as shown in Figure 4. Select your product in the third column and download the appropriate LTE firmware.

Figure 4 Cisco Download Software Web Page

Step 4 Enable the logging console.

Step 5 Initiate the firmware upgrade process.

Note For remote downloads, if wireless is your primary link, you will lose connectivity. Connectivity is restored after the download. If you have opted for logging in Step 5, the firmware log file will be available on flash with the download status.

Step 6 Verify the upgrade process.

Step 7 Reload the ISR to complete the upgrade process.

DETAILED STEPS
Command or Action

Purpose

Step 1

Go to the Cisco Wireless WAN software download website at:

http://software.cisco.com/download/navigator.html

Provides access to Cisco Wireless WAN software downloads. Select firmware for Cisco 4G.

Note This website is only available to registered Cisco.com users.

Step 2

On this page, select from the following options:
Products -> Cisco Interfaces and Modules -> Cisco High-Speed WAN Interface Cards

After the Cisco High-Speed WAN interface Cards is selected, a list of available cards displays in the third column as shown in Figure 4. Select your product in the third column and download the appropriate LTE firmware.

Step 3

Download the selected LTE firmware release.

Download the modem firmware file to flash memory on the router.

Step 4

terminal monitor
Example:

Device# terminal monitor

Enables the logging console in privileged EXEC mode.
Step 5
microcode reload cellular pa-bay slot 
modem-provision flash:filename
Example:

Device# microcode reload cellular 0 1 modem-provision flash:<filename>.cwe

F/W Upgrade: Complete Successfully
Initiates the firmware upgrade process.

•pa-bay—Use 0 for EHWIC and 819 ISR.

•slot—Slot number, 0 to 3, where the EHWIC is plugged in. For the 819 ISR, use 0.

Note For remote download, you can transfer this using the wireless link from Cisco.com onto flash. You must configure external dialer and dialer persistent to bring the interface and the dialer up again prior to the upgrade.
Step 6

For the LTE 4G EHWIC:

show cellular unit

For the 819 with embedded AT&T LTE:

show cellular 0 hardware
Example:

Device# show cellular 0 hardware

Modem Firmware Version = SWI9200X_03.05.10.02
Modem Firmware built = 2012/02/25 11:58:38

Verifies the firmware upgrade process.

Step 7

reload

Reloads the IOS application software image to complete the firmware upgrade.

Note Ensure that you are reloading an IOS software image that is 15.2(4)M3 or later.
MC7700 Manual Modem Firmware Upgrade: Example
Device#microcode reload cellular 0 0 modem-provision flash:MC7700_ATT_03.05.10.02_00.cwe  
Reload microcode? [confirm] <hit enter key>
Log status of firmware download in router flash?[confirm] <hit enter key>
Firmware download status will be logged in flash:fwlogfile
Microcode Reload Process launched for Cellular 37946756; hw type = 0x6F3
Device#
*****************************************************
 The interface will be Shut Down for Firmware Upgrade
 This will terminate any active data connections.
*****************************************************
Modem radio has been turned off
*****************************************************
 Modem will be upgraded!
 Upgrade process will take up to 15 minutes. During
 this time the modem will be unusable.
 Please do not remove power or reload the router during
 the upgrade process.
*****************************************************
Sending F/W[MC7700_ATT_03.05.10.02_00.cwe] to the card [41569157 bytes]:
Firmware file: MC7700_ATT_03.05.10.02_00.cwe sent to the card
The current modem F/W App Version: SWI9200X_01.00.03.01AP R2492 CARMD-EN-10526 2011/07/01 
19:31:09
The current modem F/W Boot Version: SWI9200X_01.00.03.01BT R2492 CARMD-EN-10526 2011/07/01 
19:28:52
The current modem Carrier String: 5
The current modem Device ID: MC7700
The current modem Package Identifier: MC7700_01.00.03.01_00_vzw_020.006_001
The current modem SKU ID: 1584083
FW UPgrade: In the progress.
*Feb 21 23:39:35.407: %CISCO800-2-MODEM_DOWN: Cellular0 modem is now DOWN.
F/W Upgrade: Complete Successfully
*Feb 21 23:42:00.475: %CISCO800-2-MODEM_UP: Cellular0 modem is now UP.
*Feb 21 23:42:00.475: %CISCO800-2-MODEM_DOWN: Cellular0 modem is now DOWN.
*Feb 21 23:42:05.475: %CISCO800-2-MODEM_UP: Cellular0 modem is now UP.
Modem radio has been turned on
Device#show cellular 0 hardware | incl Modem Firmware Version
Modem Firmware Version = SWI9200X_03.05.10.02
MC7710 Manual Modem Firmware Upgrade: Example
Device#microcode reload cellular 0 0 modem-provision  
flash:MC7710_Global_03.05.19.04_00.cwe
Reload microcode? [confirm] <hit enter key>
Log status of firmware download in router flash?[confirm] <hit enter key>
Firmware download status will be logged in flash:fwlogfile
Microcode Reload Process launched for Cellular 37946756; hw type = 0x6F3
Device#
*****************************************************
 The interface will be Shut Down for Firmware Upgrade
 This will terminate any active data connections.
*****************************************************
Modem radio has been turned off
*****************************************************
 Modem will be upgraded!
 Upgrade process will take up to 15 minutes. During
 this time the modem will be unusable.
 Please do not remove power or reload the router during
 the upgrade process.
*****************************************************
Sending F/W[MC7710_Global_03.05.19.04_00.cwe] to the card [41569157 bytes]:
Firmware file: MC7710_Global_03.05.19.04_00.cwe sent to the card
The current modem F/W App Version: SWI9200X_03.00.11.00AP R2492 CARMD-EN-10526 2011/07/01 
19:31:09
The current modem F/W Boot Version: SWI9200X_03.00.11.00BT R2492 CARMD-EN-10526 2011/07/01 
19:28:52
The current modem Carrier String: 5
The current modem Device ID: MC7710
The current modem Package Identifier: MC7710_03.00.11.00_00_vzw_020.006_001
The current modem SKU ID: 1584083
FW UPgrade: In the progress.
*Feb 21 23:39:35.407: %CISCO800-2-MODEM_DOWN: Cellular0 modem is now DOWN.
F/W Upgrade: Complete Successfully
*Feb 21 23:42:00.475: %CISCO800-2-MODEM_UP: Cellular0 modem is now UP.
*Feb 21 23:42:00.475: %CISCO800-2-MODEM_DOWN: Cellular0 modem is now DOWN.
*Feb 21 23:42:05.475: %CISCO800-2-MODEM_UP: Cellular0 modem is now UP.
Modem radio has been turned on
Device#show cellular 0 hardware | incl Modem Firmware Version
Modem Firmware Version = SWI9200X_03.05.19.04
MC7750 Manual Modem Firmware Upgrade: Example
Device#microcode reload cellular 0 0 modem-provision  flash:MC7750_VZW_03.05.10.06_00.cwe  
Reload microcode? [confirm] <hit enter key>
Log status of firmware download in router flash?[confirm] <hit enter key>
Firmware download status will be logged in flash:fwlogfile
Microcode Reload Process launched for Cellular 37946756; hw type = 0x6F3
Device#
*****************************************************
 The interface will be Shut Down for Firmware Upgrade
 This will terminate any active data connections.
*****************************************************
Modem radio has been turned off
*****************************************************
 Modem will be upgraded!
 Upgrade process will take up to 15 minutes. During
 this time the modem will be unusable.
 Please do not remove power or reload the router during
 the upgrade process.
*****************************************************
Sending F/W[MC7750_VZW_03.05.10.06_00.cwe] to the card [41569157 bytes]:
Firmware file: MC7750_VZW_03.05.10.06_00.cwe sent to the card
The current modem F/W App Version: SWI9600M_01.00.09.03AP R2492 CARMD-EN-10526 2011/07/01 
19:31:09
The current modem F/W Boot Version: SWI9600M_01.00.09.03BT R2492 CARMD-EN-10526 2011/07/01 
19:28:52
The current modem Carrier String: 5
The current modem Device ID: MC7750
The current modem Package Identifier: MC7750_01.00.09.03_00_vzw_020.006_001
The current modem SKU ID: 1584083
FW UPgrade: In the progress.
*Feb 21 23:39:35.407: %CISCO800-2-MODEM_DOWN: Cellular0 modem is now DOWN.
F/W Upgrade: Complete Successfully
*Feb 21 23:42:00.475: %CISCO800-2-MODEM_UP: Cellular0 modem is now UP.
*Feb 21 23:42:00.475: %CISCO800-2-MODEM_DOWN: Cellular0 modem is now DOWN.
*Feb 21 23:42:05.475: %CISCO800-2-MODEM_UP: Cellular0 modem is now UP.
Modem radio has been turned on
Device#show cellular 0 hardware | incl Modem Firmware Version
Modem Firmware Version = SWI9600M_03.05.10.06
Upgrading the Modem Firmware Using the EEM Scripts

For existing field deployments where LTE is the only WAN interface, and there is no local or out-of-band administrative access to the ISR, an automated upgrade method using a Cisco IOS Embedded Event Manager (EEM) script is recommended. The EEM script upgrades the modem firmware and reloads the ISR with the IOS software image that is compatible with the new firmware release.

Downloading the Modem Firmware and Installing the EEM Scripts

SUMMARY STEPS

Step 1 Go to the following Cisco web page to download the latest certified firmware for your carrier:

http://software.cisco.com/download/navigator.html

Note For remote download, you can transfer this using the 4G wireless link from Cisco.com onto flash. You must configure external dialer and dialer persistent to bring the interface and the dialer up again.

Step 2 On this page, select from the following options.
Products -> Cisco Interfaces and Modules -> Cisco High-Speed WAN Interface Cards

Step 3 After clicking on the Cisco High-Speed WAN interface Cards selection, a list of available cards displays in the third column as shown in Figure 4. Select your product in the third column and download the appropriate LTE firmware.

Step 4 Select your product in the third column and download the appropriate LTE firmware to flash memory on your router.

Step 5 Delete any boot system flash: commands from the running configuration.

Step 6 Enable the logging console.

Step 7 configure terminal

Step 8 Install the EEM scripts on the router.

Step 9 Verify that the policy is registered.

DETAILED STEPS
Command or Action

Purpose

Step 1

Go to the Cisco Wireless WAN software download website at:

http://software.cisco.com/download/navigator.html

Provides access to Cisco Wireless WAN software downloads. Select firmware for Cisco 4G.

Note This website is only available to registered Cisco.com users.

Step 2

On this page, select from the following options:
Products -> Cisco Interfaces and Modules -> Cisco High-Speed WAN Interface Cards

After the Cisco High-Speed WAN interface Cards is selected, a list of available cards displays in the third column as shown in Figure 4. Select your product in the third column and download the appropriate LTE firmware.

Step 3

Download the selected LTE firmware release.

Download the modem firmware file to flash memory on the router.

Step 4

no boot system flash:filename
Example:

Device(config)# no boot system flash:cxxx-universalk9-mz.SPA.152-4.M2

Deletes any boot system flash: commands from the running configuration in global configuration mode.

Step 5

terminal monitor
Example:

Device# terminal monitor

Enables the logging console in privileged EXEC mode.

Step 6

configure terminal
Example:

Device# configure terminal

Enters global configuration mode.
Step 7

Copy EEM Script 1 and EEM Script 2 for your modem (see the following this section) and paste this text into the router's running configuration.
Installs the EEM scripts on the router.

Note The EEM script is written assuming that the ISR is initially running the IOS interim image for LTE. If the router is running IOS 15.2(4)M2, replace the following line in the script before executing:
action 1.3.4 set old_IOS 
"c$platform-universalk9-mz.SSA.V152_4_M_LT
E"
with:
action 1.3.4 set old_IOS 
"c$platform-universalk9-mz.SPA.152-4.M2"
Step 8

show event manager policy registered
Example:

Device# show event manager policy registered

Verifies that the policy is registered.

Note Ensure that every line of the script has registered properly.
EEM Script 1 for MC7700 Modem
event manager applet FW authorization bypass
event none maxrun 1200
action 1.0 if $_none_argc ne "1"
action 1.0.1  syslog msg "Incorrect number of arguments passed. Please check and try 
again"
action 1.0.2 exit
action 1.0.3 end
action 1.1 cli command "enable"
action 1.2 set slot_number "$_none_arg1"
action 1.3 cli command "show version | incl System image file"
action 1.3.1 regexp "(.*)c(.*)-universalk9-(.*)\"" "$_cli_result" _match _sub1 _sub2 _sub3
action 1.3.2 set platform "$_sub2"
action 1.3.3 set current_IOS "c$_sub2-universalk9-$_sub3"
action 1.3.4 set old_IOS "c$platform-universalk9-mz.SPA.152-4.M2"
action 1.3.5 set new_IOS "c$platform-universalk9-mz.SPA.152-4.M3"
action 1.3.6 set firmware "MC7700_ATT_03.05.10.02_00.cwe"
action 1.3.7 set old_firmware "SWI9200X_01.00.03.01"
action 1.3.8 set new_firmware "SWI9200X_03.05.10.02"
action 1.4 if $platform eq "800"
action 1.4.1 set cellular_interface 0
action 1.5 else
action 1.5.1 set cellular_interface "0/$slot_number/0"
action 1.5.2 end
action 1.6 cli command "show cellular $cellular_interface hardware | incl Modem Firmware 
Version"
action 1.7 string first "$new_firmware" "$_cli_result"
action 1.8 if $_string_result ge 0
action 1.8.1 syslog msg "Modem is already on new firmware $new_firmware. Exiting 
upgrade!!"
action 1.8.2 exit
action 1.8.3 end
action 2.1 if $current_IOS ne $old_IOS
action 2.1.1 syslog msg "Current IOS version is incorrect. Please run $old_IOS before 
starting upgrade. Exiting upgrade!!"
action 2.1.2 exit
action 2.2 end
action 2.3 cli command "show flash: | incl $new_IOS"
action 3.0 string first "$new_IOS" "$_cli_result"
action 3.1 if $_string_result lt 0
action 3.1.1 syslog msg "$new_IOS is not present in flash. Exiting upgrade!!"
action 3.1.2 exit
action 3.2 end
action 3.3 cli command "show flash: | incl $firmware"
action 5.0  string first "$firmware" "$_cli_result"
action 5.1 if $_string_result lt 0
action 5.1.1 syslog msg "$firmware is not present in flash. Exiting upgrade!!"
action 5.1.2 exit
action 5.2 end
action 5.3 cli command "configure terminal"
action 5.4 cli command "no boot system"
action 5.5 cli command "end"
action 6.1 cli command "microcode reload cellular 0 $slot_number modem-provision 
flash:$firmware" pattern "confirm"
action 6.2 cli command "y"
action 6.3 wait 400
action 6.4 cli command "event manager run router_reload $old_IOS $new_IOS $old_firmware 
$cellular_interface"
action 6.5 wait 120
action 6.6 exit
EEM Script 2 for MC7700 Modem
event manager applet router_reload authorization bypass
event none maxrun 120
action 1.0 set old_IOS "$_none_arg1"
action 1.1 set new_IOS "$_none_arg2"
action 1.2 set old_firmware "$_none_arg3"
action 1.3 set cellular_interface "$_none_arg4"
action 1.4 cli command "enable"
action 2.0 cli command "show cellular $cellular_interface hardware | inc Modem Firmware 
Version"
action 2.1 set _string_result "0"
action 2.2 string first "$old_firmware" "$_cli_result"
action 2.3 if $_string_result ge "0"
action 2.3.1 set boot_IOS "$old_IOS"
action 2.3.2 syslog msg "Firmware did not Upgrade successfully. Please try again after 
reload"
action 2.4 else
action 2.4.1 set boot_IOS "$new_IOS"
action 2.4.2 syslog msg "Firmware upgraded successfully. value= $_string_result"
action 2.4.3 end
action 2.5 cli command "configure terminal"
action 2.5.1 cli command "boot system flash:$boot_IOS"
action 2.5.2 cli command "config-register 0x2102"
action 2.5.3 cli command "interface cellular $cellular_interface"
action 2.5.4 cli command "no shut"
action 2.5.5 cli command "end"
action 2.5.6 cli command "write memory"
action 2.5.7 reload
EEM Script 1 for MC7710 Modem
event manager applet FW authorization bypass
event none maxrun 1200
action 1.0 if $_none_argc ne "1"
action 1.0.1  syslog msg "Incorrect number of arguments passed. Please check and try 
again"
action 1.0.2 exit
action 1.0.3 end
action 1.1 cli command "enable"
action 1.2 set slot_number "$_none_arg1"
action 1.3 cli command "show version | incl System image file"
action 1.3.1 regexp "(.*)c(.*)-universalk9-(.*)\"" "$_cli_result" _match _sub1 _sub2 _sub3
action 1.3.2 set platform "$_sub2"
action 1.3.3 set current_IOS "c$_sub2-universalk9-$_sub3"
action 1.3.4 set old_IOS "c$platform-universalk9-mz.SPA.152-4.M2"
action 1.3.5 set new_IOS "c$platform-universalk9-mz.SPA.152-4.M3"
action 1.3.6 set firmware "MC7710_Global_03.05.19.04_00.cwe"
action 1.3.7 set old_firmware "SWI9200X_03.00.11.00"
action 1.3.8 set new_firmware "SWI9200X_03.05.19.04"
action 1.4 if $platform eq "800"
action 1.4.1 set cellular_interface 0
action 1.5 else
action 1.5.1 set cellular_interface "0/$slot_number/0"
action 1.5.2 end
action 1.6 cli command "show cellular $cellular_interface hardware | incl Modem Firmware 
Version"
action 1.7 string first "$new_firmware" "$_cli_result"
action 1.8 if $_string_result ge 0
action 1.8.1 syslog msg "Modem is already on new firmware $new_firmware. Exiting 
upgrade!!"
action 1.8.2 exit
action 1.8.3 end
action 2.1 if $current_IOS ne $old_IOS
action 2.1.1 syslog msg "Current IOS version is incorrect. Please run $old_IOS before 
starting upgrade. Exiting upgrade!!"
action 2.1.2 exit
action 2.2 end
action 2.3 cli command "show flash: | incl $new_IOS"
action 3.0 string first "$new_IOS" "$_cli_result"
action 3.1 if $_string_result lt 0
action 3.1.1 syslog msg "$new_IOS is not present in flash. Exiting upgrade!!"
action 3.1.2 exit
action 3.2 end
action 3.3 cli command "show flash: | incl $firmware"
action 5.0  string first "$firmware" "$_cli_result"
action 5.1 if $_string_result lt 0
action 5.1.1 syslog msg "$firmware is not present in flash. Exiting upgrade!!"
action 5.1.2 exit
action 5.2 end
action 5.3 cli command "configure terminal"
action 5.4 cli command "no boot system"
action 5.5 cli command "end"
action 6.1 cli command "microcode reload cellular 0 $slot_number modem-provision 
flash:$firmware" pattern "confirm"
action 6.2 cli command "y"
action 6.3 wait 400
action 6.4 cli command "event manager run router_reload $old_IOS $new_IOS $old_firmware 
$cellular_interface"
action 6.5 wait 120
action 6.6 exit
EEM Script 2 for MC7710 Modem
event manager applet router_reload authorization bypass
event none maxrun 120
action 1.0 set old_IOS "$_none_arg1"
action 1.1 set new_IOS "$_none_arg2"
action 1.2 set old_firmware "$_none_arg3"
action 1.3 set cellular_interface "$_none_arg4"
action 1.4 cli command "enable"
action 2.0 cli command "show cellular $cellular_interface hardware | inc Modem Firmware 
Version"
action 2.1 set _string_result "0"
action 2.2 string first "$old_firmware" "$_cli_result"
action 2.3 if $_string_result ge "0"
action 2.3.1 set boot_IOS "$old_IOS"
action 2.3.2 syslog msg "Firmware did not Upgrade successfully. Please try again after 
reload"
action 2.4 else
action 2.4.1 set boot_IOS "$new_IOS"
action 2.4.2 syslog msg "Firmware upgraded successfully. value= $_string_result"
action 2.4.3 end
action 2.5 cli command "configure terminal"
action 2.5.1 cli command "boot system flash:$boot_IOS"
action 2.5.2 cli command "config-register 0x2102"
action 2.5.3 cli command "interface cellular $cellular_interface"
action 2.5.4 cli command "no shut"
action 2.5.5 cli command "end"
action 2.5.6 cli command "write memory"
action 2.5.7 reload
EEM Script 1 for MC7750 Modem
event manager applet FW authorization bypass
event none maxrun 1200
action 1.0 if $_none_argc ne "1"
action 1.0.1  syslog msg "Incorrect number of arguments passed. Please check and try 
again"
action 1.0.2 exit
action 1.0.3 end
action 1.1 cli command "enable"
action 1.2 set slot_number "$_none_arg1"
action 1.3 cli command "show version | incl System image file"
action 1.3.1 regexp "(.*)c(.*)-universalk9-(.*)\"" "$_cli_result" _match _sub1 _sub2 _sub3
action 1.3.2 set platform "$_sub2"
action 1.3.3 set current_IOS "c$_sub2-universalk9-$_sub3"
action 1.3.4 set old_IOS "c$platform-universalk9-mz.SSA.V152_4_M_LTE"
action 1.3.5 set new_IOS "c$platform-universalk9-mz.SPA.152-4.M3"
action 1.3.6 set firmware "MC7750_VZW_03.05.10.06_00.cwe"
action 1.3.7 set old_firmware "SWI9600M_01.00.09.03"
action 1.3.8 set new_firmware "SWI9600M_03.05.10.06"
action 1.4 if $platform eq "800"
action 1.4.1 set cellular_interface 0
action 1.5 else
action 1.5.1 set cellular_interface "0/$slot_number/0"
action 1.5.2 end
action 1.6 cli command "show cellular $cellular_interface hardware | incl Modem Firmware 
Version"
action 1.7 string first "$new_firmware" "$_cli_result"
action 1.8 if $_string_result ge 0
action 1.8.1 syslog msg "Modem is already on new firmware $new_firmware. Exiting 
upgrade!!"
action 1.8.2 exit
action 1.8.3 end
action 2.1 if $current_IOS ne $old_IOS
action 2.1.1 syslog msg "Current IOS version is incorrect. Please run $old_IOS before 
starting upgrade. Exiting upgrade!!"
action 2.1.2 exit
action 2.2 end
action 2.3 cli command "show flash: | incl $new_IOS"
action 3.0 string first "$new_IOS" "$_cli_result"
action 3.1 if $_string_result lt 0
action 3.1.1 syslog msg "$new_IOS is not present in flash. Exiting upgrade!!"
action 3.1.2 exit
action 3.2 end
action 3.3 cli command "show flash: | incl $firmware"
action 5.0  string first "$firmware" "$_cli_result"
action 5.1 if $_string_result lt 0
action 5.1.1 syslog msg "$firmware is not present in flash. Exiting upgrade!!"
action 5.1.2 exit
action 5.2 end
action 5.3 cli command "configure terminal"
action 5.4 cli command "no boot system"
action 5.5 cli command "end"
action 6.1 cli command "microcode reload cellular 0 $slot_number modem-provision 
flash:$firmware" pattern "confirm"
action 6.2 cli command "y"
action 6.3 wait 400
action 6.4 cli command "event manager run router_reload $old_IOS $new_IOS $old_firmware 
$cellular_interface"
action 6.5 wait 120
action 6.6 exit
EEM Script 2 for MC7750 Modem
event manager applet router_reload authorization bypass
event none maxrun 120
action 1.0 set old_IOS "$_none_arg1"
action 1.1 set new_IOS "$_none_arg2"
action 1.2 set old_firmware "$_none_arg3"
action 1.3 set cellular_interface "$_none_arg4"
action 1.4 cli command "enable"
action 2.0 cli command "show cellular $cellular_interface hardware | inc Modem Firmware 
Version"
action 2.1 set _string_result "0"
action 2.2 string first "$old_firmware" "$_cli_result"
action 2.3 if $_string_result ge "0"
action 2.3.1 set boot_IOS "$old_IOS"
action 2.3.2 syslog msg "Firmware did not Upgrade successfully. Please try again after 
reload" 
action 2.4 else
action 2.4.1 set boot_IOS "$new_IOS"
action 2.4.2 syslog msg "Firmware upgraded successfully. value= $_string_result"
action 2.4.3 end
action 2.5 cli command "configure terminal"
action 2.5.1 cli command "boot system flash:$boot_IOS"
action 2.5.2 cli command "config-register 0x2102"
action 2.5.3 cli command "interface cellular $cellular_interface"
action 2.5.4 cli command "no shut"
action 2.5.5 cli command "end"
action 2.5.6 cli command "write memory"
action 2.5.7 reload
Running the EEM Scripts on the Router to Upgrade the Modem

SUMMARY STEPS

Step 1 event manager run fw slot-number

Step 2 show cellular slot hardware

DETAILED STEPS

Command or Action

Purpose

Step 1

event manager run fw slot-number
Example:

Device# event manager run fw 1

Identifies the EHWIC-4G-LTE slot number.

Note For 819 ISR platforms, the slot number is 0. For the 1900, 2900, or 3900 platforms with EHWICs, the slot number identifies the ISR slot where EHWIC-4G-LTE is inserted.

Step 2

show cellular slot hardware
Example:

Device# show cellular 0 hardware

Modem Firmware Version = SWI9200X_03.05.10.02
Modem Firmware built = 2012/02/25 11:58:38

Verifies that the upgrade was successful. If the upgrade was successful, a message similar to the one shown in the example should appear.

Removing EEM Scripts from the Router once the Modem Upgrades Successfully

SUMMARY STEPS

Step 1 configure terminal

Step 2 no event manager applet FW

Step 3 no event manager applet router_reload

Step 4 end

Step 5 write memory

DETAILED STEPS
Command or Action

Purpose
Step 1
configure terminal 
Example:

Device# configure terminal
Enters global configuration mode.
Step 2

no event manager applet applet-name
Example:

Device(config)# no event manager applet FW
Device(config)# no event manager applet router_reload

Deregisters the applet with the Embedded Event Manager (EEM) and enters applet configuration mode for this applet.

Step 3

end
Example:

Device(config)# end

Exits global configuration mode and enters privileged EXEC mode.

Step 4

write memory
Example:

Device# write memory

Saves the running configuration to NVRAM on the ISR.
SNMP MIBs

The following Simple Management Network Protocol (SNMP) MIBs are supported on certain Cisco 4G LTE WWAN EHWICs and 819 ISRs:

•IF-MIB

•ENTITY-MIB

•CISCO-WAN-3G-MIB

For the CISCO-WAN-3G-MIB, the following tables and sub-tables are supported for 3G and LTE technologies:

•ciscoWan3gMIB(661)

•ciscoWan3gMIBNotifs(0)

•ciscoWan3gMIBObjects(1)

•c3gWanCommonTable(1)

•c3gWanGsm(3)

•c3gGsmIdentityTable(1)

•c3gGsmNetworkTable(2)

•c3gGsmPdpProfile(3)

•c3gGsmPdpProfileTable(1)

•c3gGsmPacketSessionTable(2)

•c3gGsmRadio(4)

•c3gGsmRadioTable(1)

•c3gGsmSecurity(5)

•c3gGsmSecurityTable(1)

You can download the MIBs from the Cisco MIB Locator at http://www.cisco.com/go/mibs.

SNMP 4G LTE Configuration: Example

The following example describes how to configure SNMP capability on the router:
snmp-server group neomobilityTeam v3 auth notify 3gView 
snmp-server view 3gView ciscoWan3gMIB included
snmp-server community neomobility-test RW
snmp-server community public RW
snmp-server enable traps c3g	
snmp-server host 172.19.153.53 neomobility  c3g
snmp-server host 172.19.152.77 public  c3g
snmp-server host 172.19.152.77 public udp-port 6059 
The following example describes how to configure an external host device to communicate with the router through SNMP:
setenv SR_MGR_CONF_DIR /users/<userid>/mibtest
setenv SR_UTIL_COMMUNITY neomobility-test
setenv SR_UTIL_SNMP_VERSION -v2c
setenv SR_TRAP_TEST_PORT 6059	
Troubleshooting

This section provides the necessary background information and resources available for troubleshooting the Cisco 4G-LTE Wireless WAN EHWIC.

For LED descriptions, see Cisco 4G LTE Wireless WAN EHWIC.

•Verifying Data Call Setup

•Checking Signal Strength

•Verifying Service Availability

•Successful Call Setup

•Modem Troubleshooting Using Integrated Modem DM Logging

•Modem Settings for North America and Carriers Operating on 700 MHz Band

Verifying Data Call Setup

To verify the data call setup, follow these steps:

Step 1 After you create a modem data profile using the cellular profile create command and configuring DDR on the cellular interface, send a ping from the router to a host across the wireless network.

Step 2 If the ping fails, debug the failure by using the following debug and show commands:

•debug chat

•debug modem

•debug dialer

•show cellular all

•show interface cellular

•show running-config

•show ip route

Step 3 Save the output from these commands and contact your system administrator.

Checking Signal Strength

If the Received Signal Strength Indication (RSSI) level is very low (for example, if it is less than
-110 dBm), follow these steps:

Step 1 Check the antenna connection. Make sure the TNC connector is correctly threaded and tightened.

Step 2 If you are using a remote antenna, move the antenna cradle and check if the RSSI has improved.

Step 3 Contact your wireless service provider to verify if there is service availability in your area.

Verifying Service Availability

The following is a sample output for the show cellular all command for a scenario where the antenna is disconnected and a modem data profile has not been created. The errors in this case have been highlighted with >>>>>>>.
Device# show cellular 0/0/0 all
Hardware Information
====================
Modem Firmware Version = SWI9600M_01.00.09.03
Modem Firmware built = 2011/07/01 19:31:09
Hardware Version = 20460000
International Mobile Subscriber Identity (IMSI) = <specific sim number>
International Mobile Equipment Identity (IMEI) = <specific modem number>
Electronic Serial Number (ESN) = <specific ESN in Hex> [specific ESN in Dec]
Integrated Circuit Card ID (ICCID) = <specific ICCID number>
Mobile Subscriber International Subscriber
IDentity Number (MSISDN) = <specific phone number>
Profile Information
====================
 * - Default profile >>>>>>>> no profile here.
Data Connection Information
===========================
Profile 1, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 2, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 3, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 4, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 5, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 6, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 7, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 8, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 9, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 10, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 11, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 12, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 13, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 14, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 15, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 16, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Network Information
===================
Current Service Status = No service, Service Error = None    >>>>>>> no service means not 
connected to the network.
Current Service = Packet Switched
Current Roaming Status = Home
Network Selection Mode = Automatic
Country = , Network = 
Mobile Country Code (MCC) = 0
Mobile Network Code (MNC) = 0
Radio Information
=================
Radio power mode = Online
Current RSSI = -125 dBm        >>>>>>> either no antenna, or bad antenna or out of 
network.
Radio power mode = Online
LTE Technology Selected = LTE
Modem Security Information
==========================
Card Holder Verification (CHV1) = Disabled
SIM Status = OK
SIM User Operation Required = None
Number of CHV1 Retries remaining = 3
Successful Call Setup

The following is a sample output when a call is set up using a chat script. It shows a received IP address from the network. Call setup is successful and data path is open.
debugs
debug modem
debup chat
Device#
Aug 25 18:46:59.604: CHAT0/0/0: Attempting async line dialer script
Aug 25 18:46:59.604: CHAT0/0/0: Dialing using Modem script: lte & System script: none
Aug 25 18:46:59.604: CHAT0/0/0: process started
Aug 25 18:46:59.604: CHAT0/0/0: Asserting DTR
Aug 25 18:46:59.604: CHAT0/0/0: Chat script lte started
Aug 25 18:46:59.604: CHAT0/0/0: Sending string: AT!CALL
Aug 25 18:46:59.604: CHAT0/0/0: Expecting string: OK
Aug 25 18:47:00.641: CHAT0/0/0: Completed match for expect: OK
Aug 25 18:47:00.641: CHAT0/0/0: Chat script lte finished, status = Success
Aug 25 18:47:00.641: TTY0/0/0: no timer type 1 to destroy
Aug 25 18:47:00.641: TTY0/0/0: no timer type 0 to destroy
Aug 25 18:47:00.641: TTY0/0/0: no timer type 2 to destroy
Aug 25 18:47:02.642: %LINK-3-UPDOWN: Interface Cellular0/0/0, changed state to up
Aug 25 18:47:02.642: %DIALER-6-BIND: Interface Ce0/0/0 bound to profile Di1
Aug 25 18:47:03.642: %LINEPROTO-5-UPDOWN: Line protocol on Interface Cellular0/0/0, 
changed state to up (69.78.96.14) [OK]
Modem Troubleshooting Using Integrated Modem DM Logging

As part of the 3G and 4G serviceability enhancement in Cisco IOS Release 15.2(4)M2 and Cisco IOS Release 15.3(1)T, DM log collection has been integrated into Cisco IOS, eliminating the need for an external PC and simplifying the DM log collection process. The lte modem dm-log command can be used in controller cellular configuration mode to configure integrated DM logging to monitor traffic on the modem. See the Cisco 3G and 4G Serviceability Enhancement User Guide for more information on configuring Integrated DM Logging parameters.

Modem Settings for North America and Carriers Operating on 700 MHz Band

For HWIC-3G deployments in North America and for carriers operating in the 700 MHz band, the following changes to the modem settings are required to prevent long network attach times.

The output of show cellular x/x/x all command shows the following:

•Current RSSI is -125 dBM

•LTE Technology Preference = No preference specified (AUTO)

Changing Modem Settings

To change the modem settings to force the modem to scan different technologies, use the following Cisco IOS command:
Device# cellular 0/0/0 lte technology ?
auto         Automatic LTE Technology Selection
cdma-1xrtt   CDMA 1xRTT
cdma-evdo    CDMA EVDO Rev A
cdma-hybrid  HYBRID CDMA
gsm          GSM
lte          LTE
umts         UMTS
Electronic Serial Number (ESN)

The ESN number is located directly on the modem label in hexadecimal notation. It can also be retrieved using the Cisco IOS CLI using the show cellular slot/port/hwic hardware command.

The sample output below shows the ESN number:
Hardware Information
====================
Electronic Serial Number (ESN) = 0x603c9854 [09603971156]
Electronic Serial Number (ESN) = <specific ESN in hexadecimal> [specific ESN in decimal]
Additional References

Related Documents

Related Topic

Document Title

Cisco IOS commands

•Cisco IOS Master Commands List, All Releases

http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html

•Configuring Cisco EHWIC and 880G for 3G (EV-DO Rev A)

http://www.cisco.com/en/US/docs/routers/access/1800/1861/software/feature/guide/mrwls_evdo.html

•Configuring 3G Wireless WAN on Modular and Fixed ISRs (HWIC-3G-CDMA, HWIC-3G-CDMA-x, and PCEX-3G-CDMA-x)

http://www.cisco.com/en/US/docs/routers/access/1800/1861/software/feature/guide/mrwlcdma.html

4G LTE EHWIC and Cisco 819 ISR commands

Cisco IOS Dial Technologies Command Reference

Hardware Overview and Installation

•Cisco 4G-LTE Wireless WAN EHWIC

http://www.cisco.com/en/US/docs/routers/access/interfaces/ic/hardware/installation/guide/EHWIC-4G-LTEHW.html

Supported Cisco antennas and cables

•Installing Cisco Interface Cards in Cisco Access Routers

http://www.cisco.com/en/US/docs/routers/access/interfaces/ic/
hardware/installation/guide/inst_ic.html

•Cisco 4G/3G Omnidirectional Dipole Antenna (4G-LTE-ANTM-D)

http://www.cisco.com/en/US/docs/routers/access/wireless/hardware/notes/4G3G_ant.html

•Cisco 4G Indoor Ceiling-Mount Omnidirectional Antenna (4G-ANTM-OM-CM)

http://www.cisco.com/en/US/docs/routers/access/wireless/hardware/
notes/antcm4gin.html

•Cisco Outdoor Omnidirectional Antenna for 2G/3G/4G Cellular (ANT-4G-OMNI-OUT-N)

http://www.cisco.com/en/US/docs/routers/connectedgrid/antennas/installing/Outdoor_Omni_for_2G_3G_4G_Cellular.html

•Cisco Integrated 4G Low-Profile Outdoor Saucer Antenna (ANT-4G-SR-OUT-TNC)

http://www.cisco.com/en/US/docs/routers/connectedgrid/antennas/installing/4G_LowProfile_Outdoor_Saucer.html

•Cisco Single-Port Antenna Stand for Multiband TNC Male-Terminated Portable Antenna (Cisco 4G-AE015-R, Cisco 4G-AE010-R)

http://www.cisco.com/en/US/docs/routers/access/wireless/hardware/notes/4Gantex15-10r.html

•Cisco 4G Lightning Arrestor (4G-ACC-OUT-LA)

http://www.cisco.com/en/US/docs/routers/access/wireless/hardware/notes/4Glar.html

•Lightning Arrestor for the Cisco 1240 Connected Grid Router

http://www.cisco.com/en/US/docs/routers/connectedgrid/lightning_arrestor/Lightning_Arrestor_for_the_Cisco_1240_Connected_Grid_Router.html

•Cisco 4G Indoor/Outdoor Active GPS Antenna (GPS-ACT-ANTM-SMA)

MIBs

MIB

MIBs Link

•IF-MIB

•CISCO-ENTITY-VENDORTYPE-OID-MIB

•CISCO-WAN-3G-MIB

To locate and download MIBs for selected platforms, Cisco software releases, and feature sets, use Cisco MIB Locator found at the following URL:

http://www.cisco.com/go/mibs

RFCs

RFC

Title

RFC 3025

Mobile IP Vendor/Organization-Specific Extensions

Technical Assistance

Description

Link

The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password.

http://www.cisco.com/cisco/web/support/index.html

Feature Information for Cisco 4G LTE

Table 4 lists the release history for this feature.

Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Note Table 4 lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.

Table 4 Feature Information for Cisco 4G LTE

Feature Name

Releases

Feature Information

Dual-mode LTE Support for ISR G2

Cisco IOS Release 15.1(4)M2

Cisco 4G LTE WWAN EHWICs (EHWIC-4G-LTE-V for Verizon Wireless networks) support 4G-LTE cellular and 3G cellular networks. 4G-LTE mobile specification provides multi-megabit bandwidth, more efficient use of the radio network, latency reduction, and improved mobility.

This feature was introduced for the Cisco ISR G2 modular platform.

The following commands were introduced or modified:

•cellular slot lte

•Under controller cellular unit: default lte, lte event, lte radio, lte sim, no lte

Enhancements for Dual-mode LTE Support for ISR G2

Cisco IOS Release 15.1(4)M4, 15.2(4)M, or later releases

Bug Fixes. See Release Notes for Cisco 4G LTE Wireless WAN EHWIC 1.0 at:

http://www.cisco.com/en/US/docs/routers/access/interfaces/Release/Notes/RN_MM4G3GWAN.pdf

Multimode 4G LTE Support for ISR G2

Cisco IOS Release 15.2(4)M1

This feature is supported on the Cisco 819HG-4G and Cisco 819G-4G LTE ISRs.

The following 4G LTE WWAN EHWICs were released:

•EHWIC-4G-LTE-A—Dedicated multimode LTE for AT&T Wireless networks.

•EHWIC-4G-LTE-G—Dedicated multimode LTE for global wireless networks.

Multimode LTE EHWIC is backwards compatible with HSPA+, HSPA, UMTS, EDGE, and GPRS. This feature was introduced for the Cisco ISR G2 modular platforms.

4G LTE GPS NMEA, SMS, and Dual SIM support

Cisco IOS Release 15.3(3)M

The Cisco 819HG-4G and Cisco 819G-4G LTE ISRs and 4G LTE EHWIC MC77xx modems support the following features:

•Active and passive antenna-based Global Positioning System (GPS).

•4G Short Message Service (SMS) feature for the receiving, transmitting, archiving, and deleting of SMS messages

•Dual SIM support

The following commands were introduced or modified: cellular lte profile, cellular lte sms delete, cellular lte sms send, cellular lte sms view, debug cellular messages, debug cellular messages sms, lte failovertimer, lte gps enable, lte gps mode standalone, lte gps nmea, lte sim authenticate, lte sim max-retry, lte sim primary, lte sim profile, lte sms archive path, show cellular gps, show cellular sms.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

© 2013 Cisco Systems, Inc. All rights reserved.

Cisco High-Speed WAN Interface Cards

Cisco 4G LTE Software Installation Guide

Hierarchical Navigation

Downloads

Table Of Contents

Cisco 4G LTE Software Configuration Guide

Finding Feature Information

Contents

Overview of Cisco 4G LTE

Prerequisites for Configuring Cisco 4G LTE

Restrictions for Configuring Cisco 4G LTE

Cisco 4G LTE Features

4G GPS and NMEA

Example: Connecting to a Server Hosting a GPS Application

Short Message Service (SMS) Capabilities

Using a SIM Card

Data Account Provisioning

IP Multimedia Subsystem Profiles

4G LTE LEDs

How to Configure Cisco 4G LTE

Verifying Modem Signal Strength and Service Availability

SUMMARY STEPS

DETAILED STEPS

Creating, Modifying, or Deleting Modem Data Profiles

Usage Guidelines for Creating, Modifying, or Deleting Data Profiles

SUMMARY STEPS

DETAILED STEPS

Configuration Examples

Configuring a SIM for Data Calls

Locking and Unlocking a SIM Card Using a PIN Code

DETAILED STEPS

Changing the PIN Code

DETAILED STEPS

Verifying the Security Information of a Modem

DETAILED STEPS

Configuring Automatic Authentication for a Locked SIM

SUMMARY STEPS

DETAILED STEPS

Configuring an Encrypted PIN for a SIM

SUMMARY STEPS

DETAILED STEPS

Applying a Modem Profile in a SIM Configuration

SUMMARY STEPS

DETAILED STEPS

Configuring a Dual SIM

Usage Guidelines for Configuring a Dual SIM

SUMMARY STEPS

DETAILED STEPS

Configuration Examples

Data Call Setup

Configuring the Cellular Interface

SUMMARY STEPS

DETAILED STEPS

Configuring DDR

SUMMARY STEPS

DETAILED STEPS

Configuring DDR Backup

Configuring Interfaces to Use a Backup Interface

SUMMARY STEPS

DETAILED STEPS

Enabling 4G GPS and NMEA Data Streaming

SUMMARY STEPS

DETAILED STEPS

Configuring 4G SMS Messaging

SUMMARY STEPS

DETAILED STEPS

Configuration Examples for 4G LTE

Example: Basic Cellular Interface Configuration: EHWIC-4G-LTE

Example: Basic Cellular Interface Configuration: Cisco 819 ISR

Cellular Interface Configuration for Always-On Connection

Dialer-Watch Configuration without External Dialer Interface

Dialer-Persistent Configuration with External Dialer Interface

Example: GRE Tunnel over Cellular Interface Configuration

4G-LTE Wireless WAN as Backup with NAT and IPSec

SIM Configuration: Examples

Locking the SIM Card: Example

Unlocking the SIM Card: Example

Automatic SIM Authentication: Example

Changing the PIN Code: Example

Configuring an Encrypted PIN: Example