IR829 COnfig Guide
IR829 COnfig Guide
• 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.
• 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.
EHWIC-4G-LTE-V EHWIC-4G-LTE-V is a dedicated • LTE North • For LTE: 700 MHz (band 13)
Multimode LTE SKU for Verizon • EVDO America • For CDMA 1xRTT and 1xEVDO
Wireless networks and it is Revision Revision A
backwards compatible with these A (DOrA)
technologies: • 800 MHz
• 1900 MHz
• Evolved High-Rate Packet
Data (EHRPD)
• Single Carrier Evolution
Data Optimized (1x EVDO)
Revision A
• Single Carrier Radio
Transmission Technology
(1xRTT)
EHWIC-4G-LTE-JP EHWIC-4G-LTE-JP is a dedicated • LTE Japan For LTE: 2100 MHz (band 1)
Multimode LTE SKU for NTT • UMTS For UMTS/HSPA+:
Docomo Japan, and is based on • HSPA+
the Sierra Wireless MC7700 • 2100 MHz (band 1)
modem. EHWIC-4G-LTE-JP is • 1900 MHz (band 2)
backward compatible with these • 850 MHz (band 5)
technologies:
• UMTS
• HSPA+
EHWIC-LTE-LA Dedicated Multimode LTE SKU • LTE Latin For FDD LTE:
for Latin American Wireless • HSPA+ America
• 700 MHz (band 28)
networks. This comes with a • HSPA
Sierra Wireless MC7430 modem. • 850 MHz (band 5)
• UMTS • 800 MHz (band 19)
• 800 MHz (band 18)
• 900 MHz (band 8)
• 1800 MHz (band 3)
• 2100 MHz (band 1)
• 2600 MHz (band 7)
For TDD LTE:
• 1900 MHz (Band 39)
• 2300 MHz (Band 40)
• 2500 MHz (Band 41)
• 2600 MHz (Band 38)
For UMTS, HSPA+, HSPA:
• 800 MHz (band 6)
• 800 MHz (band 19)
• 850 MHz (band 5)
• 900 MHz (band 8)
• 1700 MHz (band 9)
• 2100 MHz (band 1)
EHWIC-LTE-CI Dedicated Multimode LTE SKU • LTE India and For FDD LTE:
for Wireless networks in India and • HSPA+ China
• 700 MHz (band 28)
China. This comes with a Sierra • HSPA
Wireless MC7430 modem. • 850 MHz (band 5)
• UMTS • 800 MHz (band 19)
• 800 MHz (band 18)
• 900 MHz (band 8)
• 1800 MHz (band 3)
• 2100 MHz (band 1)
• 2600 MHz (band 7)
For TDD LTE:
• 1900 MHz (Band 39)
• 2300 MHz (Band 40)
• 2500 MHz (Band 41)
• 2600 MHz (Band 38)
For UMTS, HSPA+, HSPA:
• 800 MHz (band 6)
• 800 MHz (band 19)
• 850 MHz (band 5)
• 900 MHz (band 8)
• 1700 MHz (band 9)
• 2100 MHz (band 1)
EHWIC-LTE-JN Dedicated Multimode LTE SKU • LTE Japan For FDD LTE:
for Wireless networks in Japan. • HSPA+ • 700 MHz (band 28)
This comes with a Sierra Wireless • HSPA
MC7430 modem. • 850 MHz (band 5)
• UMTS • 800 MHz (band 19)
• 800 MHz (band 18)
• 900 MHz (band 8)
• 1800 MHz (band 3)
• 2100 MHz (band 1)
• 2600 MHz (band 7)
For TDD LTE:
• 1900 MHz (Band 39)
• 2300 MHz (Band 40)
• 2500 MHz (Band 41)
• 2600 MHz (Band 38)
For UMTS, HSPA+, HSPA:
• 800 MHz (band 6)
• 800 MHz (band 19)
• 850 MHz (band 5)
• 900 MHz (band 8)
• 1700 MHz (band 9)
• 2100 MHz (band 1)
The following table lists the different 4G LTE SKUs available for the Cisco 1110 series routers:
C819HG-4G-V-K9 C819HG-4G-V-K9 is a LTE—DOrA North America For LTE: 700 MHz (band 13)
dedicated Multimode LTE
For CDMA 1xRTT, 1xEVDO Rev A:
SKU for Verizon Wireless
networks and comes with a • 800 MHz
Sierra Wireless MC7750 • 1900 MHz
modem. C819HG-4G-V-K9
is a hardened Cisco 819
Series Router.
C819G-4G-V-K9 C819G-4G-V-K9 is a LTE—DOrA North America For LTE: 700 MHz (band 13)
dedicated Multimode LTE
For CDMA 1xRTT, 1xEVDO Rev A:
SKU for Verizon Wireless
networks and comes with a • 800 MHz
Sierra Wireless MC7750 • 1900 MHz
modem. C819G-4G-V-K9
is a non-hardened Cisco 819
Series Router.
The following table lists the different 4G LTE SKUs available for the Cisco 880 and Cisco 890 series ISRs.
Table 3: Supported 4G LTE SKUs for the Cisco 880 and Cisco 890 Series ISRs
C899G-LTE-JP-K9 • LTE Global (Japan) LTE: Cisco 890 series ISR with
• HSPA+ Multimode LTE feature for
• 800 MHz (band 20)
• HSPA global wireless networks.
• 850 MHz (band 19) C899G-LTE-JP-K9 comes with
• UMTS • 900 MHz (band 8) a Sierra Wireless MC7330
• EDGE • 1500 MHz (band 21) modem.
• GPRS • 1800 MHz (band 3)
• 2100 MHz (band 1)
• 2600 MHz (band 7)
3G (UMTS, HSPA+, HSPA):
• 800 MHz (band 6)
• 850 MHz (band 5)
• 900 MHz (band 8)
• 1900 MHz (band 2)
• 2100 MHz (band 1)
2G (GSM, EDGE, GPRS):
• 850 MHz
• 900 MHz
• 1800 MHz
• 1900 MHz
C899G-LTE-LA-K9 C899G-LTE-LA-K9 is • LTE Latin America and APAC For FDD LTE:
a dedicated Multimode • HSPA+ • 700 MHz (band 28)
LTE SKU for Latin • HSPA
American wireless • 850 MHz (band 5)
• UMTS • 800 MHz (band 19)
networks and comes
with a Sierra Wireless • 800 MHz (band 18)
MC7430 modem. • 900 MHz (band 8)
• 1800 MHz (band 3)
• 2100 MHz (band 1)
• 2600 MHz (band 7)
For TDD LTE:
• 1900 MHz (Band 39)
• 2300 MHz (Band 40)
• 2500 MHz (Band 41)
• 2600 MHz (Band 38)
The following figure explains the 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).
For instructions on setting up the GPS antenna, see the Cisco 4G Indoor/Outdoor Active GPS Antenna
(GPS-ACT-ANTM-SMA) document.
For information on Customer Advisory on GPS rollover, see the Mandatory firmware upgrade for all MC73xx
Modems document.
Note Microsoft Streets & Trips is a licensed software that you can download from the Microsoft website.
To connect a Cisco 1110 series router through IP to a PC running Microsoft Streets & Trips, perform the
following steps:
1. Connect the PC to the router using an Ethernet cable.
2. Ensure that the PC and router can ping.
3. Launch the serial port redirector on the PC.
4. Use the show line command in the privileged EXEC mode to locate the NMEA port on the router.
5. Create a virtual serial port that connects to the NMEA port on the router.
6. Launch Microsoft Streets & Trips on your PC.
7. Select the GPS Menu.
8. Click Start Tracking.
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.
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.
Note 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.
• MC7354—Up to 16 profiles
• MC7430—Up to 16 profiles
The default data profile numbers for the various modem SKUs are given as follows:
• • MC7700, MC7710, MC7354, MC7304 – Profile 1
• MC7750, MC7350– Profile 3
• MC7430–Profile 1
The data profile is displayed by using the show cellular unit profile command with an asterisk(*).
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 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 and MC7350 modems.
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 1110 Series 4G LTE routers, the unit argument identifies slot “0” for all commands.
4G LTE LEDs
The following table describes 4G LTE EHWIC and Cisco 1110 series LED behavior:
Green (four blinks during bootup) Reset button has been pushed during the bootup.
WWAN Green Solid —On Module is powered on and connected, but is not
transmitting or receiving.
Green (slow blinking) —On 5sec, Off Module is powered on and searching for connection.
200ms
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
SIM Green / Yellow (one green blink followed SIM in slot 0 is active, SIM in slot 1 is not.
by two yellow blinks)
Yellow / Green (one yellow blink SIM in slot 1 is active, SIM in slot 0 is not.
followed by two green blinks)
Off / Green (two green blinks and then a No SIM in slot 0, SIM present in slot 1.
pause)
Green / Off (slow single green blink and SIM present in slot 0, no SIM in slot 1.
then a pause)
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.
Off No service.
These interfaces can be viewed as two logical interfaces using the same radio resources.
Note This feature is supported on Global, Australia, Canada, and AT&T SKUs. This feature is not supported on
Sprint and Verizon SKUs.
Note Here onwards, the interface cellular 0/x/0 on EHWIC and cellular 0 on C8xx are referred as the first PDN,
and cellular 0/x/1 on EHWIC and cellular 1 on C8xx as the second PDN.
The first step, in bringing up the two PDNs, is applying the configuration on both the cellular interfaces and
their corresponding lines, in order to make two simultaneous data calls.
The next step is associating the data-bearer profile with its corresponding cellular interface or PDN. It is
sufficient to associate the profile for just the first PDN under the controller cellular configuration. Note that
the second PDN assumes a profile that is just one above the profile used for the first PDN. For example, if
the first PDN uses profile 1, the second PDN uses profile 2 automatically when the call is initiated for the
second one.
After the interesting traffic is routed through these cellular interfaces, data calls are initiated and each interface
is assigned its own IP and DNS addresses provided by the cellular network. Note that both PDNs share radio
resources. Therefore, any throughput measurement needs to take into account the aggregate throughput on
both PDNs, instead of just one.
Call History
Call history maintains the history of the last three calls. The following details are recorded in the call history:
• Tx/Rx bytes
• Reason for disconnecting the call
• Duration of the call
• Who disconnected the call; User, Modem, or Network
Use the show cellular unit connection history command to display the call history. Note that this feature
has dependency on modem firmware and SDK used.
The following example shows the output of the command when the call connection is up:
The following example shows the output of the command when the call connection is down:
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.
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.
Quality of Service
Quality of Service (QoS) ensures priority treatment for certain services during times of congestion in the
network. In an LTE network, the QoS is implemented between a User Equipment (UE) and a Packet Data
Network (PDN) gateway. QoS treatment is applied to a set of associated data bearers. A bearer is a virtual
data path between the UE and the PDN gateway that carries a particular type of service, such as VoIP. A
bearer is identified by a set of parameters, known as Traffic Flow Template (TFT) parameters. Both the
network the and IOS configurations apply bandwidth related parameters to these bearers, so as to achieve an
end-to-end bearer-level QoS. For example, VoIP traffic is carried by a particular bearer which is assigned a
guaranteed bandwidth, and is prioritized over the web browser traffic which is carried over by another bearer.
Cisco 4G-LTE interface on ISRG2 routers supports only network-initiated QoS. If the QoS is subscribed by
a given UE, the network establishes the bearers between the UE and the core network after the UE has attached
to the network. Otherwise, only a default data-bearer is created between the UE and the network. No user
intervention is needed for the purposes of establishing these dedicated bearers.
Cisco 4G-LTE interface on ISRG2 routers support a maximum of 8 bearers. These bearers are created based
on the Traffic Flow Template (TFT) parameters that are downloaded to the UE after it attaches to the core
network. The host router must be configured to shape the overall traffic, as well as the IOS QoS configured
parameters on the router must match the subscribed LTE QoS parameters. When the service falls back to 3G,
the UE sets up a primary PDP context and the dedicated bearers are removed, with all the traffic flowing via
a single PDP context.
The following restrictions apply for QoS:
• UE-initiated QoS is not supported.
• The QoS parameters are determined by the carrier's service contract with the user.
• IOS QoS configuration should match with the subscribed QoS of the service provider network. If there
are any changes in the subscribed LTE QoS parameters, this must be correspondingly reflected in the
IOS QoS configuration.
Note LTE QoS is supported in Cisco IOS 15.5(1)T and later releases.
The following figure shows the Egress Class-Based Traffic Control Policy configuration:
Figure 5: Egress Class-based Traffic Control Policy Configuration
For more information about configuring QoS features, see Quality of Service Solutions Configuration Guide
Library, Cisco IOS Release 15M&T.
Troubleshooting QoS
The cellular interface notifies a user with a syslog message when QoS is enabled during the router boot-up,
or when the modem attaches to the network. It also sends a message when a TFT profile is added, deleted, or
modified by the core network. Users need to change the configuration on their side to match TFT profile. The
following table lists the syslog messages generated for various events.
The dedicated bearer has been added. Check the TFT rules of
DEDICATED_BEARER_UP: Dedicated bearer
the dedicated bearer by using the show cellular command, and
(bearer_id=%d) in HWIC slot %d/%d is
now UP add QoS configuration accordingly.
Parameter Description
rssi This parameter defines the RSSI value below which the link recovery feature triggers
onset-threshold additional scrutiny to look for potential issues and take action if needed. The range of
this parameter can be set from -90 dBm to -125 dBm. The recommended and default
value is -110 dBm.
monitor-timer This parameter determines how often link recovery looks for potential issues. The default
value for this parameter is 20 seconds which means, link recovery feature will be
triggered every 20 seconds and look at certain parameters to determine if there is a
potential issue. You can configure the monitor-timer range between 20 to 60 seconds.
Increasing the monitor timer value above 20 seconds will increase the response time of
the feature.
wait-timer and The wait-timer parameter is used in conjunction with the debounce-count parameter to
debounce-count perform more frequent, additional checks, once the link recovery feature has identified
a potential issue that needs to be recovered from, with a modem power-cycle. The default
value for wait-timer is 10 seconds and the default value for debounce- count is 6. With
this setting, once link recovery has identified an inoperative modem state, it performs
additional checks every 10 seconds, up to 6 times, to determine if the issue has been
resolved without a modem reset. Reducing the debounce-count and the wait-timer makes
faster link recovery, while reducing them may increase the time for recovery. The
configurable range for wait-timer is 5-60 seconds. The configurable range for
debounce-count is 6-20 seconds.
SIM 0 is present
SIM 1 is present
SIM 0 is active SIM
Restrictions
The following restrictions apply for PLMN search and selection:
• Support in Cisco LTE 2.0 and MC73xx modem series and above.
• You have to verify whether your cellular service supports roaming or not.
• You have to use a SIM card that supports roaming.
• This feature is not supported on 4G+WiFi platforms.
• Supported firmware version is 5.5.58.x or later.
• Supported IOS release is Cisco IOS Release 15.5(3)M1 or later.
Commands
Use the following commands on fixed platforms:
• cellular x lte plmn search
• show cellular x network
• cellular x lte plmn select mode mcc mnc rat duration
Use the following commands on EHWICs:
• cellular x/x/x lte plmn search
• show cellular x/x/x network
• cellular x/x/x lte plmn select mode mcc mnc rat duration
After the search, use the show cellular 0 network command to see the available networks:
11 234 10 lte O2 - UK
12 234 15 lte voda UK
2 234 10 gsm O2 - UK
3 234 20 umts 3 UK
4 234 30 umts EE
5 234 15 gsm voda UK
6 234 33 gsm EE
7 234 20 lte 3 UK
8 234 30 gsm EE
9 234 15 umts voda UK
10 234 30 lte EE
11 234 10 lte O2 - UK
12 234 15 lte voda UK
router#show cellular 0 radio
Radio power mode = ON
Channel Number = 122
Current Band = GSM 900 Extended
Current RSSI = -48 dBm
Current ECIO = -127 dBm
Radio Access Technology(RAT) Preference = GSM
Radio Access Technology(RAT) Selected = EDGE
Note Some networks may not allow the router to connect. In such cases, you have to choose a different network.
Note Restart your modem if the router is not able to connect to any network.
SNMP MIBs
The following Simple Management Network Protocol (SNMP) MIBs are supported on Cisco 4G LTE WWAN
EHWICs, Cisco 819 Series 4G LTE ISRs and Cisco C880 Series 4G LTE ISRs and Cisco C890 Series 4G
LTE Series 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.
Procedure
Step 2 show cellular unit radio Shows the radio signal strength.
Example: Note The RSSI should be better than –90
dBm for steady and reliable
Device# show cellular 0/0/0 radio connection.
Step 3 show cellular unit profile Shows information about the modem data
profiles created.
Example:
Step 4 show cellular unit security Shows the security information for the modem,
such as SIM and modem lock status.
Example:
Step 5 show cellular unit all Shows consolidated information about the
modem, profiles created, radio signal strength,
Example:
network security, and so on.
Device# show cellular 0/0/0 all
Procedure
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.
Procedure
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.
Procedure
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.
Procedure
Procedure
Step 3 Do one of the following: lte sim authenticate Authenticates the SIM CHV1 code by using an
0 pin lte sim authenticate 0 pin slot {0 | 1} unencrypted (0) keyword and PIN. This PIN is
sent to the modem for authentication with each
Example:
subsequent LTE connection. If authentication
passes based on the configured PIN, the data
Device(config-controller)# lte sim
authenticate 0 1111 call is allowed. If authentication fails, the
modem does not initiate the data call.
• For the Cisco 4G EHWICs that do not
support dual SIM feature, use the first
command.
• For the Cisco 800 Series 4G LTE ISRs
with dual SIM feature, use the second
command.
Procedure
Device(config)# service
password-encryption
Step 3 username name privilege 0 password pin Creates username and password.
Example: • name—Specifies the username.
• pin—Specifies the four- to eight-digit PIN
Device(config)# username SIM privilege code.
0 password 1111
Step 6 Do one of the following: Authenticates the SIM CHV1 code by using the
encrypted keyword 7 and the scrambled PIN
• lte sim authenticate {0 | 7} pin
from Step 4. The PIN is sent to the modem for
• lte sim authenticate {0 | 7} pin slot {0 | authentication with each subsequent LTE
1} connection. If authentication passes based on
Example: the configured PIN, the data call is allowed. If
authentication fails, the modem does not initiate
Device(config-controller)# lte sim the data call.
authenticate 7 055A575E70
For Cisco 4G LTE WWAN EHWICs, use the
first command.
For the Cisco 819(H)G-4G-G ISR that supports
dual SIM feature, use the second command.
Note The slot keyword and its options are
available only on Cisco 800 Series
4G LTE ISRs which supports the
dual SIM feature.
Device(config-controller)# exit
Device(config)# no service
password-encryption
Procedure
Step 3 Do one of the following: (All MC77xx modems) Applies the configured
profile number to the SIM and its slot number.
• lte sim data-profile number
The default (primary) slot is 0.
• attach-profile number lte sim profile
number attach-profile number slot {0 | 1} • For the Cisco 4G EHWICs that do not
support dual SIM feature, use the first
Example: command.
• For the Cisco 800 Series 4G LTE ISRs
Device(config-controller)# lte sim
data-profile 2 attach-profile 1 slot 0
with dual SIM feature, use the second
command.
Example: • attach profile—profile used by the
modem to attach to the LTE network.
Device(config-controller)# lte sim
• data profile—profile used to send and
data-profile 3 attach-profile 1 slot 1
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.
Note You can manually activate a SIM using the cellular 0 lte sim activate slot 0 or 1 command.
Procedure
Step 3 lte sim primary slot (Optional) Enters either slot number 0 or 1 of
the primary SIM.
Example:
Device(config-controller)# lte sim
primary 1
Step 4 lte sim max-retry number (Optional) Specifies the maximum number of
failover retries from 1 to 65535. The default
Example:
value is 10.
Device(config-controller)# lte sim
max-retry 20
Step 5 lte failovertimer timeout-period (Optional) By default, the failover time period
is 2 minutes before the primary SIM switches
Example:
over to the secondary SIM if service becomes
Device(config-controller)# lte unavailable.
failovertimer 6
Specify a failover timeout value between 1 and
7 minutes before a switchover occurs.
Step 6 lte sim data-profile number attach-profile Applies the configured profile number to the
number slot {0 | 1} SIM and its slot number. The default (primary)
slot is 0.
Example:
Device(config-controller)# lte sim You must also identify the primary and
data-profile 2 attach-profile 1 slot 0 secondary SIM for the configured profile when
two SIMs are presented.
Example:
Device(config-controller)# lte sim
data-profile 2 attach-profile 1 slot 1
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.
Procedure
Step 7 dialer-group group-number Specifies the number of the dialer access group
to which the specific interface belongs.
Example:
Device(config-if)# dialer-group 1
Device(config-if)# exit
Step 9 chat-script script-name ”” “AT!CALL” Defines the ATDT commands when the dialer
TIMEOUT timeout-value “OK” is initiated.
Example:
Step 10 ip route network-number network-mask Establishes a floating static route with the
{ip-address | interface} [administrative configured administrative distance through the
distance] [name name] specified interface.
Example: Note A higher administrative distance
should be configured for the route
Device(config)# ip route 209.165.200.225 through the backup interface so that
255.255.255.224 cellular 0/0/0 it is used only when the primary
interface is down.
Step 11 dialer-list dialer-group protocol Creates a dialer list for traffic of interest and
protocol-name {permit | deny | list permits access to an entire protocol.
access-list-number | access-group}
Example:
What to do next
Note 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.
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.
Procedure
Example:
Step 7 interface dialer number Specifies the number of a dialer rotary group
to which the specific interface belongs.
Example:
Step 10 dialer pool number Specifies the number of a dialing pool that the
dialer interface can use to connect to a specific
Example:
destination subnetwork.
Device(config-if)# dialer pool 1
Step 11 dialer idle-timeout seconds Specifies the duration of idle time, in seconds,
after which a line will be disconnected.
Example:
Step 13 dialer-group group-number Specifies the number of the dialer access group
to which the specific interface belongs.
Example:
Device(config-if)# dialer-group 1
Device(config-if)# exit
Device(config-line)# exit
Step 20 chat-script script-name ”” “AT!CALL” Defines the ATDT commands when the dialer
TIMEOUT timeout-value “OK” is initiated.
Example:
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.
Procedure
Step 2 backup interface cellular number Specifies the cellular interface as backup.
Example:
Step 3 backup delay enable-delay-period Specifies delay between the physical interface
disable-delay-period going down and the backup interface being
enabled and between the physical interface
Example:
coming back up and the backup being disabled.
Device(config-if)# backup delay 0 10
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.
Procedure
(Optional) GPS is enabled by default. Use this command to enable the GPS feature if GPS has been disabled
for any reason.
Enables NMEA streaming. Cisco 4G LTE EHWICs support only IP NMEA streaming. Therefore, IP interface
and serial interface options are unavailable. Cisco 819 4G LTE ISRs, Cisco C880 Series 4G LTE ISRs, and
Cisco C890 Series 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).
Note Effective with Cisco IOS release 15.4(3)T, the lte gps nmea serial ip command is available on
Cisco 800 series routers with serial interfaces only.
Step 6 end
Example:
Device(config-controller)# end
Exits the controller configuration mode and returns to the privileged EXEC mode.
GPS Info
-------------
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
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
!
controller Cellular 0
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 -
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.
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 1110 Series 4G LTE routers, the unit argument identifies slot 0 for all
commands.
Procedure
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 5 end
Example:
Device(config)# end
Exits the configuration mode and returns to the privileged EXEC mode.
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.
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.
(Optional) Deletes one message ID or all of the stored messages from memory.
Procedure
Step 3 Do one of the following: Disables or enables the cellular modem link
recovery feature.
• lte modem link-recovery disable
• no lte modem link-recovery
link-recovery disable
Example:
Device(config-controller)# lte modem
link-recovery disable
Example:
Device(config-controller)# no lte modem
link-recovery disable
Note The firmware upgrade procedure explained here is applicable only to MC77xx modems. The procedure for
MC73xx modem is explained here:
http://www.cisco.com/c/en/us/td/docs/routers/access/interfaces/firmware/Firmware_Upgrade.html
Use only Cisco certified firmware. Using a firmware version not certified by Cisco may impact the wireless
service provider network adversely.
Note Do not disconnect power or switch the router off during the firmware upgrade process. This may result in
permanent modem failure.
Note The 3.5.x firmware must have a 15.2(4)M3 or later software image.
Procedure
Step 1 Go to Cisco web page http://software.cisco.com/download/navigator.html and select firmware for Cisco 4G
to download the latest certified firmware for your carrier.
Note This website is only available to registered Cisco.com users. For remote download, you can transfer
this using the 4G wireless link from Cisco.com onto flash. You configure external dialer and dialer
persistent to bring the interface and the dialer up again.
Step 2 On this page, navigate as follows: Products -> Cisco Interfaces and Modules -> Cisco High-Speed WAN
Interface Cards
A list of available cards displays in the third column as shown in the following figure. Select your product in
the third column and download the appropriate LTE firmware. After clicking on the Cisco High-Speed WAN
interface Cards selection, a list of available cards displays in the third column as shown in the following
figure ().
Step 3 Select your product in the third column and download the appropriate LTE firmware to the flash memory on
the router.
Step 4 Enable the logging console.
Step 5 Initiate the firmware upgrade process.
Note For remote downloads, if wireless is your primary link, you lose connectivity. Connectivity is
restored after the download. If you have opted for logging in Step 5, the firmware log file is available
on flash with the download status.
Procedure
Step 2 microcode reload cellular pa-bay slot Initiates the firmware upgrade process.
modem-provision flash:filename
• pa-bay—Use 0 for EHWIC and Cisco 819,
Example: 880 and 890 Series ISR.
• slot—For EHWIC, slot number, 0 to 3,
Device# microcode reload cellular 0 1 where the EHWIC is plugged in. For Cisco
modem-provision flash:filename.cwe
819, 880, and 890 4G LTE Series ISR, use
Example: 0.
Note For remote download, you can
Example: transfer this using the wireless link
from Cisco.com onto flash. You
F/W Upgrade: Complete Successfully must configure external dialer and
dialer persistent to bring the interface
and the dialer up again prior to the
upgrade.
Step 3 show cellular unit show cellular 0 hardware Verifies the firmware upgrade process. The first
command pertains to Cisco 4G LTE EHWIC
Example:
and the second command pertains to Cisco
819 Series 4G LTE ISRs, Cisco C880 Series
Device# show cellular 0 hardware
4G LTE ISRs, and Cisco C890 Series 4G LTE
Example: ISRs.
Example:
Procedure
Step 2 On this page, select from the following After the Cisco High-Speed WAN interface
options:Products -> Cisco Interfaces and Cards is selected, a list of available cards
Modules -> Cisco High-Speed WAN Interface displays in the third column. Select your product
Cards 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 Deletes any boot system flash: commands from
the running configuration in global
Example:
configuration mode.
Device(config)# no boot system
flash:cxxx-universalk9-mz.SPA.152-4.M2
Step 7 Copy EEM Script 1 and EEM Script 2 for your Installs the EEM scripts on the router.
modem (see the following this section) and
Note The EEM script is written assuming
paste this text into the router's running
that the ISR is initially running the
configuration.
IOS interim image for LTE. If the
router is running IOS 15.2(4)M2,
replace the following line in the
script before executing:
with:
Step 8 show event manager policy registered Verifies that the policy is registered.
Example: Note Ensure that every line of the script
has registered properly.
Device# show event manager policy
registered
Procedure
Step 2 show cellular slot hardware Verifies that the upgrade was successful. If the
upgrade was successful, a message similar to
Example:
the one shown in the example should appear.
Device# show cellular 0 hardware
Example:
Example:
Removing EEM Scripts from the Router once the Modem Upgrades Successfully
Procedure
Step 2 no event manager applet applet-name Deregisters the applet with the Embedded Event
Manager (EEM) and enters applet configuration
Example:
mode for this applet.
Device(config)# no event manager
applet FW
Example:
no event manager
Device(config)#
applet router_reload
Device(config)# end
for the specific firmware upgrade procedure. For example, if you are upgrading only the carrier provisioning
file, the directory should only contain the carrier provisioning file.
Note You should always execute the firmware upgrade command from flash. If you execute the firmware upgrade
command inside a directory or folder the firmware upgrade may fail.
Note You should reload the router after the modem firmware upgrade.
Note When you create a directory in the flash for firmware upgrade, you shouldn’t create any subdirectories under
the directory.
Procedure
Step 1 Go to the Cisco web page http://software.cisco.com/download/navigator.html to download the latest certified
firmware for your carrier which can be found under the path: Products -> Cisco Interfaces and Modules ->
LTE Wireless WAN Interfaces
Step 2 Download the firmware files to the router flash over Ethernet or cellular or any other WAN interface. This
can be done by hosting the firmware files on a FTP or TFTP server and reaching to that server via any WAN
interface on the router.
Step 3 Create a directory in the flash.
Example:
Step 4 Copy the firmware files to the created directory in the flash. Before you copy the firmware, make sure that
the files are available in a TFTP server.
Example:
Step 5 Ensure that the firmware file (CWE) and carrier PRI file (NVU) have the same version and both files are
available under the same directory.
Example:
7430_02.14.03.00
_Telstra_002.013_000.nvu
26 -rw- 64316979 Apr 22 2016 18:15:52 +00:00 74XX_02.14.03.00
.cwe
Step 6 Initiate the firmware upgrade process using the microcode reload cellular command. When you use this
command, provide the directory name instead of firmware file name.
For EHWIC-LTE-LA, EHWIC-LTE-JN, and EHWIC-LTE-CI
Example:
Step 7 Once the firmware upgrade begins, wait for a few minutes. The firmware upgrade may take upto 7 minutes.
The following message will be displayed if the firmware upgrade is successful.
For EHWIC-LTE-LA, EHWIC-LTE-JN, EHWIC-LTE-CI, C898EAG-LTE-LA-K9, and
C897VAG-LTE-LA-K9, C899G-LTE-LA-K9, C819G-LTE-LA-K9
Example:
Step 8 Once the message indicates a successful upgrade, wait for 2 minutes till modem comes up.
Step 9 After the firmware upgrade, reload the router and verify that you have the latest firmware.
Example:
Note You should reload the router after the modem firmware upgrade, regardless of the upgrade is a
success or failure.
Step 10 After the firmware upgrade as well as after the router reload, the modem status should be online. Check
whether the modem status is online.
Example:
Procedure
Step 1 Perform the steps from 1 to 4 in Upgrading Firmware File and Carrier PRI file , on page 75.
Step 2 Ensure that the currently running firmware version in the modem has the same version as the carrier PRI file
going to be upgraded.
Example:
Step 3 Initiate the firmware upgrade process using the microcode reload cellular command. When you use this
command, provide the directory name instead of firmware file name.
For EHWIC-LTE-LA, EHWIC-LTE-JN, and EHWIC-LTE-CI
Example:
Step 4 Once the firmware upgrade begins, wait for a few minutes. The firmware upgrade may take upto 7 minutes.
The following message will be displayed if the firmware upgrade is successful.
For EHWIC-LTE-LA, EHWIC-LTE-JN, EHWIC-LTE-CI, C898EAG-LTE-LA-K9, C897VAG-LTE-LA-K9,
C899G-LTE-LA-K9 and C819G-LTE-LA-K9
Example:
Step 5 Once the message indicates a successful upgrade, wait for 2 minutes till the modem comes up.
Step 6 After the firmware upgrade, reload the router to verify that you have the latest firmware.
Example:
Note You should reload the router after the modem firmware upgrade, regardless of the upgrade is a
success or failure.
Step 7 After the firmware upgrade, as well as after the modem reload, the modem status should be online. Check
whether the modem status is online.
Example:
Procedure
Step 1 Perform the steps from 1 to 4 in Upgrading Firmware File and Carrier PRI file , on page 75.
Step 2 Check the versions of old OEM PRI and the new OEM PRI and ensure that the old PRI is available. Use the
show cell slot hardware command to check the OEM PRI version.
Example:
Step 3 Initiate the firmware upgrade process using the microcode reload cellular command. When you use this
command, provide the directory name instead of firmware file name.
For EHWIC-LTE-LA, EHWIC-LTE-JN, and EHWIC-LTE-CI
Example:
Step 4 Once the firmware upgrade begins, wait for a few minutes. The firmware upgrade may take upto 7 minutes.
The following message will be displayed if the firmware upgrade is successful.
For EHWIC-LTE-LA, EHWIC-LTE-JN, EHWIC-LTE-CI, C898EAG-LTE-LA-K9, C897VAG-LTE-LA-K9,
C899G-LTE-LA-K9, and C819G-LTE-LA-K9
Example:
Step 5 Once the message indicates a successful upgrade, wait for 2 minutes till the modem comes up.
Step 6 After the firmware upgrade, reload the router and verify that you have the latest firmware.
Example:
Note You should reload the router after the modem firmware upgrade, regardless of the upgrade is a
success or failure.
Step 7 After the firmware upgrade, as well as after the reload, the modem status should be online. Check whether
the modem status is online.
Example:
Note Image upgrade on Cisco IR800 and Cisco CGR1000 is not supported. Only configuration upgrade is supported.
Note Ensure that the configuration pushed through the Cisco Network PnP server contains a route to the Cisco
Network PnP server over the 4G interface. This route can be a default route and should retain the Cisco
Network PnP agent and server communication to continue to work over the 4G interface, after the provisioning
is completed.
Steps Process
Step 1 4G modem attaches to the base station and obtains a DHCP IP address.
Step 2 DHCP allocates an IP address to the cellular interface. After that, the PnP
discovery process starts.
Step 3 The router connects to Cisco Plug and Play Connect portal at
devicehelper.cisco.com over a secure HTTPS channel. The portal redirects the
device to its appropriate PnP Server or Controller.
Step 4 The APIC-EM server securely provisions the configuration and image.
Troubleshooting
You do not need to manually enable PnP. PnP is enabled automatically when the router boots up.
Note PnP is not invoked if the startup configuration is present in the router.
The following log file shows a successful scenario of the PnP boot-up:
The following log file shows a failure scenario when the startup configuration is present in the router:
The following log file shows a failure scenario when a user interrupts the PnP discovery process:
Enabling Serviceability
Serviceability or Non-Access Stratum (NAS) is a set of protocols in the Evolved Packet System. The NAS is
used to convey non-radio signaling between the User Equipment (UE) and the Mobility Management Entity
(MME). The serviceability feature collects the NAS messages during a network outage and helps you to
narrow down the issues on the network or UE side.
Restrictions
Follow these restrictions and usage guideline while configuring serviceability .
• This feature is not supported on the C819GW router and 4G CGM module.
Enabling Serviceability
The following example shows how to enable serviceability:
Router#config terminal
Router(config)#controller cellular 0/0/0
Router(config-controller)#lte modem svb-log enable
Router(config-controller)#end
The following example shows how to specify the log size and the file size of the log file:
Router#config terminal
Router(config)#controller cellular 0/0/0
Router(config-controller)#lte modem svb-log size 0
Router(config-controller)#lte modem svb-log filesize 1
Router(config-controller)#lte modem svb-log enable
Router(config-controller)#end
Directory of bootflash:/
Note You can set a MTU of 2K on the cellular interface if your service provider's network can support it.
Restrictions
Follow these restrictions and usage guideline while configuring MTU.
• This feature (MTU of 2K) is supported only on the EM7455, MC7304, and MC7354MNA modems.
Configuring MTU
The supported MTU value is determined only after a call is established between the modem and the network.
The cellular interface can accept an MTU value up to 2000 bytes.
The following example shows how to set the MTU value to 2000:
Router#config terminal
Router(config)#interface cellular 0/0/0
Router(config-if)#mtu 2000
Router(config-if)#end
The following example shows the output of the command after a call:
Note For 73XX modems, the below output always shows negotiated network MTU value as 2000.
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 .
Procedure
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.
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.
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 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:
Hardware Information
====================
Electronic Serial Number (ESN) = 0x603c9854 [09603971156]
Electronic Serial Number (ESN) = <specific ESN in hexadecimal> [specific ESN in decimal]
The following example shows the output of the show cellular command:
The following example shows the output of the show cellular command before you enable the debug command:
The following example shows the output of the show cellular command after you enable the debug command:
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
The following example shows how to display the status of a dual SIM:
The following example shows how to display the status of a dual SIM:
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
Note The receive and transmit speeds cannot be configured. The actual throughput depends on the cellular network
service.
!
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 [email protected]
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...).
Device(config)# end
May 14 20:20:52.603: %SYS-5-CONFIG_I: Configured from console by console
Note The “14001234567” phone number in the example below is the incoming caller’s number.
!
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
interface Cellular0
ip address negotiated
encapsulation slip
dialer in-band
dialer pool-member 1
dialer in-band
dialer idle-timeout 0
dialer string lte
dialer-group 1
!
ip route 141.141.141.141 255.255.255.255 Cellular1
ip route 192.169.187.254 255.255.255.255 Cellular0
!
line 3
exec-timeout 0 0 script dialer lte
modem InOut
no exec
transport input all
transport output all
rxspeed 100000000
txspeed 50000000
!
line 8
script dialer lte
modem InOut
no exec
transport input all
transport output all
rxspeed 100000000
txspeed 50000000
The following show commands can be used to verify the status of the multiple PDN calls:
Domain name-servers:
171.70.168.183
173.36.131.10
DNS Server settings:
Forwarding of queries is disabled
Forwarder timeout: 3 seconds
Forwarder retries: 2
Forwarder addresses:
Forwarder addresses:
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
Example: Upgrading MC7430 Modem Firmware File and Carrier PRI file
This example shows the firmware and carrier file upgrade of MC7430 modem the using the microcode reload
cellular command. In this example, firmware files are downloaded to the
Package_02.14.03.00_Telstra_002.013_000 directory.
UA_2951#
*Jan 28 09:51:06.577 PST: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0/0,
changed state to up
*Jan 28 09:51:07.561 PST: %LINK-5-CHANGED: Interface Cellular0/0/0, changed state to
administratively down
*Jan 28 09:51:07.565 PST: %LINK-5-CHANGED: Interface Cellular0/0/1, changed state to
administratively down
*Jan 28 09:51:07.565 PST: %LINK-5-CHANGED: Interface Cellular0/0/3, changed state to
administratively down
Router_2951#
The current modem F/W App Version: SWI9X30C_02.05.07.00
The current modem F/W Boot Version: SWI9X30C_02.05.07.00
The current modem Carrier String: 1
The current modem Device ID: MC7430
The current modem Package Identifier:
The current modem SKU ID: 1102644
Router_2951#
Firmware Upgrade is in Progress...
Router_2951#
*Jan 28 09:51:27.105 PST: %CELLWAN-2-MODEM_DOWN: Modem in HWIC slot 0/0 is DOWN
Router_2951#
F/W Upgrade: Firmware Upgrade has Completed Successfully
The following example describes how to configure an external host device to communicate with the router
through SNMP:
Additional References
Related Documents
Cisco IOS commands • Cisco IOS Master Commands List, All Releases
• Configuring Cisco EHWIC and 880G for 3G (EV-DO Rev A)
• Configuring 3G Wireless WAN on Modular and Fixed ISRs
(HWIC-3G-CDMA, HWIC-3G-CDMA-x, and PCEX-3G-CDMA-x)
4G LTE EHWIC and Cisco Cisco IOS Dial Technologies Command Reference
1110 series commands
Supported Cisco antennas and • Installing Cisco Interface Cards in Cisco Access Routers
cables
• Cisco 4G/3G Omnidirectional Dipole Antenna (4G-LTE-ANTM-D)
• Cisco 4G Indoor Ceiling-Mount Omnidirectional Antenna
(4G-ANTM-OM-CM)
• Cisco Outdoor Omnidirectional Antenna for 2G/3G/4G Cellular
(ANT-4G-OMNI-OUT-N)
• Cisco Integrated 4G Low-Profile Outdoor Saucer Antenna
(ANT-4G-SR-OUT-TNC)
• Cisco Single-Port Antenna Stand for Multiband TNC Male-Terminated
Portable Antenna (Cisco 4G-AE015-R, Cisco 4G-AE010-R)
• Cisco 4G Lightning Arrestor (4G-ACC-OUT-LA)
• Lightning Arrestor for the Cisco 1240 Connected Grid Router
• Cisco 4G Indoor/Outdoor Active GPS Antenna
(GPS-ACT-ANTM-SMA)
MIBs
RFCs
RFC Title
Technical Assistance
Description Link
Dual-mode Cisco IOS Cisco 4G LTE WWAN EHWICs (EHWIC-4G-LTE-V for Verizon Wireless
LTE Release networks) support 4G-LTE cellular and 3G cellular networks. 4G-LTE mobile
Support for 16.5.1 specification provides multi-megabit bandwidth, more efficient use of the radio
Cisco network, latency reduction, and improved mobility.
1110?
The following commands were introduced or modified: cellular, controller cellular,
default lte, lte event,lte radio, lte sim, lte.
Enhancements Cisco IOS Bug Fixes. See Release Notes for Cisco 4G LTE Wireless WAN EHWIC 1.0 at:
for Release
http://www.cisco.com/en/US/docs/routers/access/interfaces/Release/Notes/RN_
Dual-mode 16.5.1
MM4G3GWAN.pdf
LTE
http://www.cisco.com/en/US/docs/routers/access/interfaces/Release/Notes/RN_MM4G3GWAN.pdf
Support
forCisco
1110
Multimode Cisco IOS This feature is supported on the Cisco 1110 series routers.
4G LTE Release
The following 4G LTE WWAN EHWICs were released:
Support for 16.5.1
Cisco • EHWIC-4G-LTE-A—Dedicated multimode LTE for AT&T Wireless networks
1110?
• EHWIC-4G-LTE-G—Dedicated multimode LTE for global wireless networks
4G LTE Cisco IOS The Cisco 1110 series and 4G LTE EHWIC MC77xx modems support the following
GPS Release features:
NMEA, 16.5.1
• Active and passive antenna-based Global Positioning System (GPS)
SMS, and
Dual SIM • 4G Short Message Service (SMS) feature for the receiving, transmitting,
support archiving, and deleting of SMS messages
• Dual SIM support
The following commands were introduced or modified: cellular lte profile, cellular
lte sms, debug cellular messages, lte failovertimer, lte gps, lte sim, lte sms
archive path, show cellular.