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 .

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.

Cisco 4G LTE EHWICs and Cisco 800 Series 4G LTE ISRs support the following 4G/3G modes:

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

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.

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 for more information.

Restrictions for Configuring Cisco 4G LTE

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. Latency also depends on the signal conditions and can 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.

4G GPS and NMEA

Effective with Cisco IOS Release 15.3(3)M and later releases, the Global Positioning System (GPS) feature is enabled by default on the supported Cisco 819 Series 4G LTE ISRs and Cisco 4G LTE EHWICs to provide the geographical location. GPS is also enabled by default on Cisco C880 Series and Cisco C890 Series 4G LTE ISRs.

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 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 Cisco 4G LTE EHWICs, Cisco 819 Series 4G LTE ISRs, Cisco C880 Series 4G LTE ISRs, and Cisco C890 Series 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 819 Series 4G LTE ISRs, Cisco C880 Series 4G LTE ISRs, and Cisco C890 Series 4G LTE ISRs can support either IP or serial NMEA streaming options.

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

Cisco 4G LTE EHWICs, Cisco 819 Series 4GLTE ISRs, Cisco C880 Series 4G LTE ISRs, and Cisco C890 Series 4G LTE ISRs 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. Cisco 4G LTE EHWICs, Cisco 819 Series 4GLTE ISRs, Cisco C880 Series 4G LTE ISRs, and Cisco C890 Series 4G LTE ISRs also have the capability to revert from LTE SMS to 3G and 2G SMS technology if necessary.

A sending device behind a Cisco 4G LTE ISR 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. 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 Cisco 4G LTE ISR 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

Cisco 4G LTE EHWICs, Cisco 819 Series 4GLTE ISRs, Cisco C880 Series 4G LTE ISRs, and Cisco C890 Series 4G LTE ISRs 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:

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.

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 pre-configured 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:

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 , for more information.

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 800 Series 4G LTE fixed platforms, use slot “0” for all commands.

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 800 Series 4G LTE ISRs, 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

Device# show cellular 0/0/0 network

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

Step 2

show cellular unit radio

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

Device# show cellular 0/0/0 profile

Shows information about the modem data profiles created.

Step 4

show cellular unit security

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

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 4G LTE EHWICs, Cisco 819 Series 4G LTE ISRs, Cisco C880 Series 4G LTE ISRs and Cisco C890 Series 4G LTE ISRs. The following are the default Internet profile numbers for some of the modems:

Usage Guidelines for Creating, Modifying, or Deleting Data Profiles

In most cases, you do not have to make any profile-related changes if your modem comes with a data profile, for instance, AT&T, Sprint 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 data profile. An asterisk(*) is displayed against the data profile.

The data 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 data-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 applicable for 4G LTE SKUs with MC7750 modem.

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 800 Series 4G LTE ISRs, the unit argument identifies slot “0” for all commands.

(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 data profile numbers for the various modem SKUs are given as follows:

– MC7700, MC7710, MC7304 – Profile 1

– MC7750– Profile 3

The data 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:

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

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 800 Series 4G LTE ISRs, the unit argument identifies slot “0” for all commands.

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 800 Series 4G LTE ISRs, 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

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 800 Series 4G LTE ISRs, 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

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 .

Note A SIM should be locked for SIM authentication to work. To verify the SIM’s status, use the showcellularunitsecurity 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 800 Series 4G LTE ISRs, the unit argument identifies slot “0” for all commands.

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 .

Note The slot keyword and its options are only available on Cisco 800 Series 4G LTE ISRs 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 showcellularunitsecurity 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 800 Series 4G LTE ISRs, the unit argument identifies slot “0” for all commands.

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

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

Step 5

controller cellular unit

Device(config)# controller cellular 0/0

Enters the cellular controller configuration mode.

Step 6

For Cisco 4G LTE WWAN EHWICs:

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 }

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

Authenticates the SIM CHV1 code by using the encrypted keyword 7 and the scrambled PIN from . 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 Cisco 800 Series 4G LTE ISRs which supports the dual SIM feature.

(All MC77xx modems) Applies the configured profile number to the SIM and its slot number. The default (primary) slot is 0.

The attach profile is the profile used by the modem to attach to the LTE network.

The data profile is the profile used to send and receive data over the cellular network.

Note The slot keyword and its options are available only on Cisco 800 Series 4G LTE ISRs 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.

Note Dual SIM is supported only on Cisco 819 Series 4G LTE ISRs, Cisco C880 Series 4G LTE ISRs and Cisco C890 Series 4G LTE ISRs. Dual SIM is not supported 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 data-profile command. Each SIM has an associated data profile and an attach profile.

In the lte sim data-profile command, the profile-number refers to the data profile associated with a SIM. The attach-profile-number is the attach profile associated with a SIM.

If the attach profile details are not provided by or are not relevant to the carrier, you can assign the same number as the data profile. Otherwise, create a profile with the carrier-specific attach profile parameters and assign that profile number using the lte sim data-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 data-profile number attach-profile number slot {0 | 1}

DETAILED STEPS

Command or Action

Purpose

Step 1

configure terminal

Device# configure terminal

Enters the global configuration mode.

Step 2

controller cellular unit

Device(config)# controller cellular 0/0

Enters the cellular controller configuration mode.

Step 3

lte sim primary slot

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

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

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.

Data Call Setup

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 800 Series 4G LTE ISRs, 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 EHWIC SKUs and the fixed 3G and 4G routers support these configuration changes.

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

Step 4

encapsulation slip

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

Device(config-if)# dialer in-band

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

Step 6

dialer string string

Device(config-if)# dialer string lte

Specifies the number or string to dial.

Step 7

dialer-group group-number

Device(config-if)# dialer-group 1

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

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

Step 12

line unit

Device(config)# line 0/0/0

Specifies the line configuration mode.

Step 13

script dialer regular-expression

Device(config-line)# script dialer lte

Specifies a default modem chat script.

Note If a tunnel interface is configured with ip unnumbered cellular0/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 .

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 800 Series 4G LTE ISRs, the unit argument identifies slot “0” for all commands.

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

Step 4

encapsulation slip

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

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

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

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

Device(config-if)# ip address negotiated

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

Step 9

encapsulation slip

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

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

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

Device(config-if)# dialer string lte

Specifies the number or string to dial.

Step 13

dialer-group group-number

Device(config-if)# dialer-group 1

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

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

Device(config)# access-list 1 permit any

Defines traffic of interest.

Step 17

line unit

Device(config)# line 0/0/0

Specifies the line configuration mode.

Step 18

script dialer regular-expression

Device(config-line)# script dialer lte

Specifies a default modem chat script.

Step 19

exit

Device(config-line)# exit

Exits line configuration mode.

Step 20

chat-script script-name ”” “AT!CALL” TIMEOUT timeout-value “OK”

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.

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 800 Series 4G LTE ISRs, 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 ]} or lte gps nmea

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.

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 800 Series 4G LTE ISRs, the unit argument identifies slot 0 for all commands.

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:

Device#
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: Cisco 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 4G LTE 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

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.

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.

! 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.

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:

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

Table 5 describes the Sierra Wireless modems that are supported on Cisco 4G LTE EHWICs and Cisco 800 Series 4G LTE ISRs. The firmware for the modem is upgradable using Cisco IOS commands. The firmware is a Crossword Express (cwe) file and can be downloaded from the wireless software download page on Cisco.com.

Table 5 Modem SKUs and Associated Firmware

SKU

Modem

Firmware

EHWIC-4G-LTE-A

C819G-4G-A-K9

C819HG-4G-A-K9

MC7700

FW 3.5.10.2

EHWIC-4G-LTE-G

C819G-4G-G-K9

C819HG-4G-G-K9

MC7710

FW 3.5.29.04

EHWIC-4G-LTE-V

C819G-4G-V-K9

C819HG-4G-V-K9

MC7750

FW 3.5.10.6

EHWIC-4G-LTE-AU

C819G-4G-GA-K9

C881G-4G-GA-K9

C887VAG-4G-GA-K9

C896VAG-LTE-GA-K9

C897VAG-LTE-GA-K9

C898EAG-LTE-GA-K9

C899G-LTE-GA-K9

MC7304

FW 5.5.26.02

EHWIC-4G-LTE-GB

C897VAMG-LTE-GA-K9

MC7304

FW 5.5.47.0

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:

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 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 . 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 , the firmware log file will be available on flash with the download status.

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 . Select your product in the third column and download the appropriate LTE firmware.

slot—For EHWIC, slot number, 0 to 3, where the EHWIC is plugged in. For Cisco 819, 880, and 890 4G LTE Series 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.

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:

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 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 . 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.

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 . 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

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

Device# terminal monitor

Enables the logging console in privileged EXEC mode.

Step 6

configure terminal

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:

Verifying Data Call Setup

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 >>>>>>>.

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.

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.

Feature Information for Cisco 4G LTE

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.

NoteTable 6 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.

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.