Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
Page 2
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,
INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH
THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,
CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS.
CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT
LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
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.
All printed copies and duplicate soft copies of this document are considered uncontrolled. See the current online version for the latest version.
Cisco has more than 200 offices worldwide. Addresses and phone numbers are listed on the Cisco website at www.cisco.com/go/offices.
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
This preface describes the objectives, audience, organization, and conventions of this guide and describes
related documents that have additional information.
This preface describes the objectives, audience, organization, and conventions of this guide and describes
related documents that have additional information. It contains the following sections:
Objective
This guide provides an overview of the software features and explains how to perform the configuration steps
for the Cisco IR800 Integrated Services Routers.
Audience
This guide is intended for people who have a high level of technical ability, although they may not have
experience with Cisco software.
Conventions
This section describes the conventions used in this guide.
Note
Caution
Tip
Means reader take note. Notes contain helpful suggestions or references to additional information and material.
This symbol means reader be careful. In this situation, you might do something that could result in equipment
damage or loss of data.
Means the following information will help you solve a problem . The tip information might not be
troubleshooting or even an action, but could be useful information.
Searching Cisco Documents
To search an HTML document using a web browser, press Ctrl-F (Windows) or Cmd-F (Apple). In most
browsers, the option to search whole words only, invoke case sensitivity, or search forward and backward is
also available.
To search a PDF document in Adobe Reader, use the basic Find toolbar (Ctrl-F) or the Full Reader Search
window (Shift-Ctrl-F). Use the Find toolbar to find words or phrases within a specific document. Use the
Full Reader Search window to search multiple PDF files simultaneously and to change case sensitivity and
other options. Adobe Reader’s online help has more information about how to search PDF documents.
This chapter provides an overview of the features available for the Cisco IR800 Integrated Services Routers
(ISRs).
• General Description, on page 1
• Hardware Overview, on page 2
• Software Overview, on page 15
• Hardware Differences Between IR809, IR829, and C819HG, on page 16
• Antenna Recommendations, on page 18
• Features Supported in Different IOS Releases, on page 18
• Related Documentation, on page 22
General Description
The 800 Series Industrial Integrated Services Routers are compact, ruggedized, Cisco IOS Software routers.
They offer support for integrated 4G LTE wireless WAN (both 809 and 829 models) and wireless LAN
capabilities (829 model only). The IR829 offers an Internal WLAN Access Point which runs on-board the
router. The AP803 runs its own IOS software independently from the IR829 IOS, and requires configuring.
The AP803 works as a standalone access point or with a wireless controller.
CHAPTER 1
They offer:
• Easily and rapidly deployable
• Highly available, highly secure, and reliable
• Designed for machine-to-machine (M2M) communication and for mobile vehicle communication in
harsh environmental conditions
• Designed to withstand hostile environments, tolerating a wide temperature range
These industrialized routers deliver enterprise-class features, including highly secure data, voice, and video
communications to stationary and mobile network nodes across wired and wireless links. They can deliver
enterprise-grade, wireline-like functionality.
The routers also support Cisco IOx Software, providing an open, extensible environment for hosting additional
operating systems and applications directly at the network edge. They can enhance other Cisco IoT System
products across multiple industries, including transportation, manufacturing, electrical utilities, and others.
CELLULAR 0 MAIN7Cover over SIM cards, reset button and console port cover,
see Figure 6: Behind the SIM Door, on page 3
GPS SMA4
Figure 5: Cisco IR829 Back Panel Dual Modem, on page 3 shows the back panels details of the Cisco IR829
Dual Modem.
Figure 5: Cisco IR829 Back Panel Dual Modem
Denotes SIM card order, SIM0 on top and
5Cellular 1 Main1
SIM1 on bottom.
Cellular 1 AUX6WLAN ANT 1 2.4/5GHz2
3
CELLULAR 0 MAIN7Cover over SIM cards, reset button and console port cover,
see Figure 6: Behind the SIM Door, on page 3
GPS SMA4
Note
Behind the SIM Door Assembly, there is a reset switch (1), Mini USB console port (2), and Dual SIM slots
(3). See Figure 6: Behind the SIM Door, on page 3 for details
Figure 6: Behind the SIM Door
Figure 7: Cisco IR829 Top Cover, on page 3 shows the top of the Cisco IR829.
Figure 7: Cisco IR829 Top Cover
Figure 8: Cisco IR829 LED Detail, on page 3 shows the LED detail from the Dual Modem SKU. Single
See the respective Hardware Installation Guides for detailed description of the LEDs.
The reset button resets the router configuration to the default configuration set by the factory. To restore the
router configuration to the default configuration set by the factory, use a standard size #1 paper clip with wire
gauge 0.033 inch or smaller and simultaneously press the reset button while applying power to the router.
On the IR829, the rear cover must be removed to expose the reset switch.
Starting with release 15.6(1)T, the IR809 and IR829 have changed the way the reset button works. The IR800
series platforms now perform in the same manner as the C819. The high level description of the functionality
works like this:
• Press and hold the reset button while powering up the router
• During warm reboot this button has no impact on performance
• Simply pressing the button at any time does not reset the router
• The router will not react to the reset button if it is pressed after power-up because the button needs to be
pushed before turning ON/inserting power – to make sure that the condition is detected.
• The push-button cannot be used to boot a IOS image from network. The golden image has to be on flash:
only
Note
For the location of the reset button, see the appropriate IR809 or IR829 Hardware Installation Guide.
Perform the following steps to use the reset button:
Procedure
Step 1Unplug power.
Step 2Press the reset button on the router.
Step 3Power up the system while holding down the reset button.
Step 4Check the “boot system” setting configuration in the default configuration file (prior to saving it to
startup-config), and verify that it points to an existing IOS image on the flash: partition. Note: If that particular
IOS image is not present, the device will drop in rommon-2 mode and you will need to manually boot an IOS
image from there.
Step 5Copy your desired default config file to the startup-config.
Step 6Reload the router. Do NOT enter Yes if prompted whether you want to save the running-config to startup-config.
To simplify the boot process, the IR800 routers do not support the ROMMON configuration register and the
associated CLI commands. The IR800 either boots the pre-configured images, or stops at the ROMMON
prompt for user intervention. In the event of a boot failure, see Chapter 3, “Setup Command Facility” for
additional information.
Booting a Default IOS Image and Default Configuration - Method 1
The IR800 differs from traditional IOS routers when booting a default IOS image and a default configuration.
These steps apply on a device running 15.6(1)T or later.
Method 1:
Procedure
Step 1Save a copy of your IR800 IOS image with the .default extension on flash. For example: ios-image.default.
Step 2Save a copy of your IR800 Hypervisor image with the .default extension on bootstrap. For example:
hypervisor-image.default.
Step 3Save your desired default configuration file with the .cfg extension on flash. For example: config.cfg.
Step 4Reset your IR800 router by powering it down, then press and hold the RESET button while powering up the
device.
The IR800 router will automatically boot hypervisor-image.default, then ios-image.default, and load the
config.cfg.
Step 5Make sure there exists only one IOS image with a .default extension, only one configuration file with the .cfg
extension on the flash, and only one hypervisor image with the .default extension on bootstrap.
Booting a Default IOS Image and Default Configuration - Method 2
Booting a Default IOS Image and Default Configuration - Method 2
If you do not have a config.cfg on flash, it will boot with the Cisco default configuration (aka: empty)
startup-config.
Method 2:
Procedure
Step 1Check the “boot system” setting configuration in the default configuration file (prior to saving it to
startup-config), and verify that it points to an existing IOS image on the flash: partition.
Note
Step 2Copy your desired default config file to the startup-config.
Step 3Reload the router. Do NOT enter Yes if prompted whether you want to save the running-config to startup-config.
What to do next
An example of the log activity after a reboot follows:
IR800# show log
*Nov 30 19:31:04.925: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0,
changed state to down
*Nov 30 19:31:10.651: %PLATFORM-5-RESET_BUTTON: Reset Button pressed during boot up.
*Nov 30 19:31:11.527: %LINK-3-UPDOWN: Interface Async0, changed state to up
*Nov 30 19:31:11.595: %SYS-5-RESTART: System restarted -Cisco IOS Software, ir800 Software (ir800-UNIVERSALK9-M), Version 15.6(1)T, RELEASE SOFTWARE
(fc1)
Configuration Register
To configure the register:
IR800#conf t
Enter configuration commands, one per line. End with CNTL/Z.
IR800(config)#config-register 0x?
<0x0-0xFFFF>
IR800(config)#config-register 0x102
IR800(config)#
Jul 26 22:10:22.790: Bootstrap Emulator called with code 62
Jul 26 22:10:22.790: Bootstrap Emulator called with code 61
IR800(config)#
If that particular IOS image is not present, the device will drop in rommon-2 mode and you will
need to manually boot an IOS image from there.
To display the register:
IR800#sh ver
…..
…..
…..
Configuration register is 0x2101 (will be 0x102 at next reload)
The Format for the configuration registers is 0 x _ _ _ _ (4 bytes)
The Configuration Register 4th byte table shows the configuration register 4th byte values and descriptions.
Table 4: Configuration Register4th byte
Auto-recovery of Corrupt Filesystems
On rare occasions, the router could get stuck in ROMMON to flash and bootstrap file system corruption
caused by hard reloads. Hard reloads can be a consequence of fluctuating voltage or very low current. The
file system (in flash: or bootstrap:) is completely inaccessible at this point.
Starting with 15.8(3)M, on the IR8x9 platforms, software will automatically recover the router if one or more
filesystems are corrupt. This feature is enabled once the user executes bundle install, write memory, reload.
This backup partition is taken from the Guest-OS data partition on the IR809, IR829, IR829GW, IR829B
products.
The IR829M products mSATA SSD partition is unaffected.
If a previous user was already using up this extra partition in old software, the new software will NOT proceed
with creating a backup partition. This ensures the user data is always intact. If the user wants to trigger a
backup, ~300Mb needs to be cleaned up from Guest-OS /dev/sdb. In some routers, Guest-OS /dev/sdb may
appear to have ~250Mb lesser, and some ~330Mb. This is due to the two different versions of eMMC on the
IR8x9s, and there is no software cli to provide eMMC part number to distinguish.
Files Backed Up to the New Backup Partition
• IOS image
• Hypervisor image
• Guest-OS image (if IOX Recovery is enabled using conf t then iox recovery-enable)
• The entire managed folder, except managed/images
• All pnp* files (all PnP related files)
• vlan.dat
• Archive folder
• Field Network Director specific files:
• express-setup-config
• before-registration-config
• before-tunnel-config
• Sample file labeled additional_backup_file (This file is to ensure if a user wants to customize low sized
(50 kbytes or less) configuration file copy, they can save it in this name and it will be backed up.
Product Overview
Files NOT Backed Up to the New Backup Partition
• Duplicates of software images in managed/images
• User generated files, folders and configurations
• FW of 4G modems
• IOx application data
Notes:
The backup partition is limited in space and only for basic device recovery, and to load startup -config [as
SPI Flash: is intact]. In this manner, remote device reachability is back up again. Remaining files need to be
restored again by end user.
If a user running old software would like to increase their current Guest-OS disk space, it is recommended to
take a data backup, and execute the following command taking up larger disk space. Starting at IOS release
156(3)M3 and greater, the default disk space allocated to Guest-OS is Option 1 from the example below. For
previous releases default used to be Option 6 from the example below.
IR800#guest-os 1 disk-repartition ?
1 disk1: 500MB vs disk2: 1800MB
2 disk1: 700MB vs disk2: 1600MB
3 disk1: 900MB vs disk2: 1400MB
4 disk1: 1100MB vs disk2: 1200MB
5 disk1: 1300MB vs disk2: 1000MB
6 disk1: 1500MB vs disk2: 800MB
7 disk1: 1700MB vs disk2: 600MB
Note: Actual storage available for applications will be less than the value chosen for all profiles. The disk2
partition displayed in the15.8(3)M release has to account for 300MB less space. For example: option1, disk2
is 1500MB not 1800MB. In future releases, this will be corrected.
Once an auto-recovery is complete, the user will observe a small file in flash called fs_recovered.ios. It will
contain the timestamp of the last recovery. This file is indication that backup was successful, and that there
was indeed a corruption of the filesystem. This file is not persistent on soft reload of the router.
Alternatively, the user can also backup using:
IR800#hypervisor backup_images
WARNING - If you are running this command for the first time, it might delete all application
data in IOx. This operation cannot be undone. Continue? [yes/no]: y
Performing image backup......... Done
This will ensure the latest sync of vlan.dat, pnp and managed configs.
The first time the command is executed, it will forcibly create the backup. If an IOx user was using up the
300Mb required for backup partition creation from an older IOS release, then it will be carved into backup
and the user will loose data. The user can opt for 'no' and perform a manual backup of that data before
proceeding with hypervisor backup_images command.
Plug and Play Agent (PnP) support over 4G/Ethernet
Plug and Play Agent (PnP) support over 4G/Ethernet
An option was added to the bundle install command:
bundle install <bundle_image_name> rom-autoboot
When this option is specified, the IOS system image to boot will NOT be written into the running-config.
Instead, it will be set into the rommon BOOT variable (BOOT=<system_image>) ONLY.
After bundle install <bundle_image_name> rom-autoboot and write erase commands, when the device reloads
it will automatically boot up the IOS image saved in rommon BOOT. This also ensures the device does not
have any startup configuration when it boots up so it will allow PNP to start up.
PNP can be started either using Ethernet or cellular 4G. If connected to both, Ethernet will take precedence
over Cellular 4G.
PNP using Ethernet can be done in three different ways:
#conf t
#ip host pnpserver.test.com <APIC-EM address>
3. Specifying CCO’s address by configuring devicehelper.cisco.com on DHCP ROUTER
#conf t
#ip host devicehelper.cisco.com <CCO_address>
PNP using 4G cellular can be done by configuring the device information (Serial number, PID and controller
profile-APIC-EM) on CCO.
Once PNP is completed, issue a write mem command to save the configuration. PNP pushes the configuration
but does not save it. The configuration must be saved after PNP is successfully completed.
To verify if PNP is completed or not, verify with the sh run command. At the bottom of the command output,
there should be a pnp profile and the APIC EM address. This means the device was redirected to APIC-EM
and the initial PNP was successfully done. Now once the configuration file is pushed from APIC-EM, verify
this using the sh pnp task command and verify the Config-Upgrade Task should have Result: Success.
Note
The device should not be interrupted until PNP is completed. If the device is interrupted, PNP will stop. If at
any point something goes wrong, reload the router without saving the configuration and PNP will start once
again. Once PNP is completed it is necessary to save the configuration by issuing the write mem command.
IR800#sh run | b pnp
pnp profile pnp-zero-touch
transport https ipv4 172.27.122.132 port 443
end
IR800#sh pnp task
------------------ show pnp tasks --------------------Certificate-Install Task - Last Run ID:5, ST:7201, Result:Success,
LT:117562, ET:4 ms
Src:[-], Dst:[-]
Device-Auth Task - Never Run
Device-Info Task - Last Run ID:9, ST:5301, Result:Success, LT:200634, ET:1 ms Src:[udi],
Dst:[pnp-zero-touch]
Image-Install Task - Never Run
SMU Task - Never Run
Config-Upgrade Task - Last Run ID:10, ST:5202, Result:Success, LT:267420, ET:984 ms
Src:[https://192.168.1.1:443/api/v1/file/onetimedownload/1530b4e5-beb8-4db3-b4df-28dc016464fc],
Dst:[running]
CLI-Config Task - Never Run
Licensing Task - Never Run
File-Transfer Task - Never Run
Redirection Task - Never Run
CLI-Exec Task - Last Run ID:12, ST:5401, Result:Success, LT:279464, ET:1 ms
Src:[cli-exec request], Dst:[running-exec]
Script Task - Never Run
Product Overview
Additional Resources for Cisco Plug and Play can be found at the following links:
Plug and Play (PnP) Support on the IR829 LAN
Feature applies to the IR829 product series only
Starting with this release, PnP will be supported over LAN ports (G1 to G4). In previous releases, PnP was
supported only over WAN port and 4G LTE.
Similar to WAN port, PnP over LAN Interfaces can be triggered by configuring either DHCP, DNS or CCO
details on DHCP/DNS server. Since all the LAN interfaces default to Vlan1, when the router boots up in
factory default mode, it acquires an IP address from either DHCP or DNS server through Vlan1. This is how
PnP is initiated. Once the initial PnP discovery is successful and the router is discovered on the PnP Server
(for example: any Network Management System such as Field Network Director, APIC-EM, DNAC to name
a few), it will be in an unclaimed state. From here, the user can 'claim' the device and push required
configurations from the PnP server to the router.
Note: Image upgrade from the PnP server is currently not supported.
PnP using Ethernet can be done in three different ways:
ip dhcp pool IOT_DNS
network 192.168.2.0 255.255.255.0
default-router 192.168.2.1
domain-name pnp-agent-tb.cisco.com
dns-server 192.168.2.1
ip host pnpserver.pnp-agent-tb.cisco.com 172.23.165.116
ip host pnpntpserver.pnp-agent-tb.cisco.com 172.23.165.116
ip dns server
3. Specifying CCO’s address by configuring devicehelper.cisco.com on DHCP router
ip dhcp pool IOT_dhcp
network 192.168.3.0 255.255.255.0
default-router 192.168.3.1
dns-server 192.168.3.1
ip host devicehelper.cisco.com 64.101.32.10
ip host time-pnp.cisco.com 192.168.3.1
ntp master
Note: Once PnP is completed, issue a write mem command to save the configuration. PnP pushes the
configuration but does not save it. The configuration must be saved after PnP is successfully completed.
To verify if PnP is completed or not, verify with the show run command. At the bottom of the command
output, there should be a PnP profile and the PnP controller IP address. This means the device was redirected
to the PnP server and the PnP discovery was successfully done. Once the configuration file is pushed from
the PnP server, verify this using the show pnp task command and verify the Config-Upgrade Task should
show Result: Success.
You can further debug and verify the entire PnP process using the commands show pnp summary, show
pnp trace and show pnp tech-support.
Note: The device should not be interrupted until PnP is completed. If the device is interrupted, PnP will stop.
If at any point something goes wrong, reload the router without saving the configuration and PnP will start
once again. Once PnP is completed it is necessary to save the configuration by issuing the write memcommand.
IR800#show running-config | begin pnp profile
pnp profile pnp_redirection_profile
transport https ipv4 128.107.248.237 port 443
!
end
IR800#show pnp task
------------------ show pnp tasks --------------------Certificate-Install Task - Last Run ID:5, ST:7201, Result:Success,
LT:117562, ET:4 ms
Src:[-], Dst:[-]
Device-Auth Task - Never Run
Device-Info Task - Last Run ID:9, ST:5301, Result:Success, LT:200634, ET:1 ms Src:[udi],
Dst:[pnp-zero-touch]
Image-Install Task - Never Run
SMU Task - Never Run
Config-Upgrade Task - Last Run ID:10, ST:5202, Result:Success, LT:267420, ET:984 ms
Src:[https://192.168.1.1:443/api/v1/file/onetimedownload/1530b4e5-beb8-4db3-b4df-28dc016464fc],
Licensing Task - Never Run
File-Transfer Task - Never Run
Redirection Task - Never Run
CLI-Exec Task - Last Run ID:12, ST:5401, Result:Success, LT:279464, ET:1 ms
Src:[cli-exec request], Dst:[running-exec]
Script Task - Never Run
Password Recovery
Use the following procedure in the event you have lost the router password.
Procedure
Step 1Copy a ".cfg" configuration file in the router flash memory without any "username", "password", or "AAA"
In the router flash memory you must have only one ".cfg" at a time. If there are two or more the system will
be confused resulting in unexpected behavior.
Step 2Make a copy of the "startup-config" file in the router flash memory without an extension.
• Concurrent connections to two cellular networks for high reliability, enhanced
data throughputs for mission critical services.
• Dual radio 802.11n concurrent 2.4 GHz and 5.0 GHz with embedded 2X3
MIMO
• Up to 300 Mbps data rate per radio
Provides an open, extensible environment for hosting OS and applications at the
network edge.
Security
Cisco IOT Field
Network Director
Application Hosting on Guest Operation System.
Advanced security features that support:
• Access control
• Data confidentiality and data privacy
• Threat detection and mitigation
• Device and platform integrity
Available as the optional Cisco Industrial Operations Kit. This is a software
platform that manages a multiservice network and security infrastructure for IoT
applications such as transportation, smart grid, services, distribution automation
and substation automation.
Hardware Differences Between IR809, IR829, and C819HG
Product Overview
DescriptionFeature
Cisco IOS Mobile IP
Features
Cisco IOS Mobile
Network Features
QoS Features
Management and
Manageability
• Mobile IP offers transparent roaming for mobile networks, establishing a
transparent Internet connection regardless of location or movement. This
enables mission-critical applications to stay connected even when roaming
between networks.
• Assigned IP addresses to the home network are maintained in private or
public networks.
Allows an entire subnet or mobile network to maintain connectivity to the home
network while roaming.
• Provides traffic precedence to delay-sensitive or prioritized applications.
• Facilitates low-latency routing of delay-sensitive industrial applications.
• Network managers can remotely manage and monitor networks with SNMP,
Telnet, or HTTP/HTTPS/SSH, and locally through a console port.
• Support for extensive 3G and 4G LTE-based MIBs allows for centralized
management of remote devices and gives network managers visibility into
and control over the network configuration at the remote site.
• Network managers can reset to a predesignated golden image, as well as
configure an 829 through Cisco IOS Software or through an external reset
button.
• Network managers can upgrade 3G, 3.5G, 3.7G, and 4G LTE firmware and
router configurations remotely.
The tight integration with Cisco IOS Software enables router to self-monitor the
LTE WAN link and automatically recover from a radio link failure.
• Cisco IOS Software Release - 15.5(3)M, or later, and modem firmware -
5.5.58, or later. (several features require later IOS releases)
Hardware Differences Between IR809, IR829, and C819HG
The IR809s are very compact cellular (3G and 4G/LTE) industrial routers for remote deployment in various
industries. They enable reliable and secure cellular connectivity for remote asset monitoring and
machine-to-machine (M2M) solutions such as distribution automation, pipeline monitoring, and roadside
infrastructure monitoring.
The IR829s are highly ruggedized compact cellular (3G and 4G LTE with GPS and dual SIM) and WLAN
(2.4/5GHz) industrial routers supporting for scalable, reliable, and secure management of fleet vehicles and
mass transit applications.
Neither the IR809 or IR829 is shipped with antennas. These antennas must be ordered separately. The IR829
must be installed with 2 antennas (Main & Aux) to guarantee the best performance level. Using a single
antenna may impact the downlink performance by a minimum 3dB, and can be much greater (10-20dB) due
to multipath fading (destructive interference between direct and reflected radio waves).
In case of 3G UMTS, a solo antenna would not be able to switch to the diversity port.
With the IR829, it must be guaranteed >15dB isolation between the WiFi and LTE antennas at all frequencies
of 4G LTE and WiFi operation, for minimum impact to performance. This is ideally 20-25dB.
The Sierra Wireless MC73xx modem series supports MIMO on LTE. WCDMA UMTS HSPA DC-HSPA+
is diversity only, without MIMO.
Note
Poorly installed MIMO antennas, such that the two (or more in case of 3x3, 4x4 MIMO) antennas have a
strong correlation coefficient. This may cause the two streams to interfere with each other (otherwise known
as lack of diversity), since the system has trouble separating the two. The multi-element antennas (5-in-1,
3-in-1, 2-in-1) have good diversity
Product Overview
For detailed information about Cisco Antennas, please refer to the following guides:
This chapter provides instructions for initial configuration of the Cisco IR800 series Integrated Services
Routers (ISRs). To create the initial configuration, the setup command facility prompts you for basic information
about your router and network.
• IR800 Bootstrap Sequence and Troubleshooting, on page 23
• Setup Command Facility, on page 27
• Verifying the Initial Configuration, on page 30
• Auto-Negotiation Support for Gigabit-Ethernet 0 on the IR829, on page 43
• Where To Go From Here, on page 43
IR800 Bootstrap Sequence and Troubleshooting
The typical power up sequence on the IR800 is as follows:
-------------------------- END TABLE ------------------rommon-1> ping 192.0.2.1
PING 192.0.2.1 (192.0.2.1): 56 data bytes
64 bytes from 192.0.2.1: seq=0 ttl=64 time=0.242 ms
64 bytes from 192.0.2.1: seq=1 ttl=64 time=0.276 ms
64 bytes from 192.0.2.1: seq=2 ttl=64 time=0.293 ms
64 bytes from 192.0.2.1: seq=3 ttl=64 time=0.279 ms
64 bytes from 192.0.2.1: seq=4 ttl=64 time=0.280 ms
In the NVRAM status shown above, the default BOOT_IOS_SEQUNCE value is 4. Starting with IOS version
15.7(3)M2, the value has increased to 20.
Setup Command Facility
The setup command facility guides you through the configuration process by prompting you for the specific
information that is needed to configure your system. Use the setup command facility to configure a hostname
for the router, to set passwords, and to configure an interface for communication with the management network.
To use the setup command facility, you must set up a console connection with the router and enter the privileged
EXEC mode.
Setup Command Facility
To configure the initial router settings by using the setup command facility, follow these steps:
Procedure
Step 1Set up a console connection to your router, and enter privileged EXEC mode.
Step 2In privileged EXEC mode, at the prompt, enter setup.
Example:
IR800# setup
The following message is displayed:
Example:
--- System Configuration Dialog --Would you like to enter the initial configuration dialog? [yes/no]:
You are now in the setup command facility.
The prompts in the setup command facility vary, depending on your router model, on the installed interface
modules, and on the software image. The following steps and the user entries (in bold) are shown as examples
only.
Note
If you make a mistake while using the setup command facility, you can exit and run the setup
command facility again. Press Ctrl-C and enter the setup command at the privileged EXEC mode
prompt (Router#). To proceed using the setup command facility, enter yes.
Example:
Would you like to enter the initial configuration dialog? yes
Step 3When the following messages appear, enter yes to enter basic management setup.
At any point you may enter a question mark '?' for help.
Use ctrl-c to abort configuration dialog at any prompt.
Default settings are in square brackets '[]'.
Basic management setup configures only enough connectivity
for management of the system, extended setup will ask you
to configure each interface on the system
Would you like to enter basic management setup? [yes/no]: yes
Step 4Enter a hostname for the router (this example uses Router).
Example:
Configuring global parameters:
Enter host name [Router]: Router
Step 5Enter an enable secret password. This password is encrypted (more secure) and cannot be seen when viewing
the configuration.
Example:
The enable secret is a password used to protect access to
privileged EXEC and configuration modes. This password, after
entered, becomes encrypted in the configuration.
Enter enable secret: xxxxxx
Step 6Enter an enable password that is different from the enable secret password. This password is not encrypted
(less secure) and can be seen when viewing the configuration.
Example:
The enable password is used when you do not specify an
enable secret password, with some older software versions, and
some boot images.
Enter enable password: xxxxxx
Step 7Enter the virtual terminal password, which prevents unauthenticated access to the router through ports other
than the console port.
Example:
The virtual terminal password is used to protect
access to the router over a network interface.
Enter virtual terminal password: xxxxxx
Step 8Respond to the following prompts as appropriate for your network:
Example:
Configure SNMP Network Management? [yes]:
Community string [public]:
A summary of the available interfaces is displayed. The following is an example summary and may not reflect
your configuration:
Example:
Current interface summary
Any interface listed with OK? value "NO" does not have a valid configuration
Step 9Choose one of the available interfaces for connecting the router to the management network.
Example:
Enter interface name used to connect to the
management network from the above interface summary: GigabitEthernet0
Step 10Respond to the following prompts as appropriate for your network:
Example:
Configuring interface GigabitEthernet0:
Configure IP on this interface? [yes]: yes
Use the 100 Base-TX (RJ-45) connector? [yes]: yes
Operate in full-duplex mode? [no]: yes
Configure IP on this interface? [yes]: yes
IP address for this interface: 172.16.2.3
Subnet mask for this interface [255.255.0.0] : 255.255.0.0
Class B network is 172.16.0.0, 26 subnet bits; mask is /16
Setup Command Facility
The configuration is displayed:
Example:
The following configuration command script was created:
hostname Router
enable secret 5 $1$D5P6$PYx41/lQIASK.HcSbfO5q1
enable password xxxxxx
line vty 0 4
password xxxxxx
snmp-server community public
!
no ip routing
!
interface GigabitEthernet0
no shutdown
speed 100
duplex auto
ip address 172.16.2.3 255.255.0.0
!
Step 11Respond to the following prompts. Enter 2 to save the initial configuration.
Example:
[0] Go to the IOS command prompt without saving this config.
[1] Return back to the setup without saving this config.
[2] Save this configuration to nvram and exit.
Enter your selection [2]: 2
Building configuration...
Use the enabled mode 'configure' command to modify this configuration.
Press RETURN to get started! RETURN
Step 12Verify the initial configuration. See the Verifying the Initial Configuration, on page 30 for verification
procedures.
What to do next
After the initial configuration file is created, you can use the Cisco IOS CLI to perform additional configuration.
Verifying the Initial Configuration
To verify that the new interfaces are operating correctly, perform the following tests:
• To verify that the interfaces and line protocol are in the correct state—up or down—enter the showinterfaces command.
• To display a summary status of the interfaces configured for IP, enter the show ip interface brief
command.
Initial Configuration
LEDs
• To verify that you configured the correct hostname and password, enter the show configurationcommand.
After you complete and verify the initial configuration, you can configure your Cisco router for specific
functions.
Note
The QoS Input Service Policy can only be configured on the WAN interface, not on the SVI interface.
Note
To ensure product security, even though the use of Hypervisor is not discussed in this guide, a proper password
should be set. Only IOS priv15 users will be able to configure the password. The commands are shown as
follows:
Router:(config)#iox hypervisor password ?
0Specifies an UNENCRYPTED password will follow
7Specifies a HIDDEN password will follow
LINE The UNENCRYPTED (cleartext) password
The Cisco IR800 has LEDs that are discussed in the Hardware Configuration Guide for each model. There is
also a command that will show you the status of the LEDs if you are not near the device. Use the show platform
led command with options to view the different output.
Note
The following examples are from the IR829. The IR809 differs slightly.
IR829#show platform led
LED STATUS:
==================================================
GE PORTS : GE0GE1GE2GE3GE4
LINK LED : OFFGREENOFFGREENGREEN
==================================================
PoE LED: OFF
Cellular PORTS: Cellular0
RSSI LED 1 : Green
RSSI LED 2 : Green
RSSI LED 3 : Off
GPS LED: Off
SIM0 LED: Green
SIM1 LED: Off
==================================================
VPN LED: OFF
System LED: green, on
IR829#
IR829#show platform led summary
Ports LINK/ENABLE
--------+-------+------VPN LED: OFF
System LED: green, on
IR829#
IR829#show platform led system
System LED: green, on
Summary of the LED status providers:
ClientTypeStatus
------------------------------ -------- -------GigabitEthernet0critical OK
GigabitEthernet1critical OK
GigabitEthernet3critical OK
GigabitEthernet4critical OK
Cellular0critical OK
IR829#show platform led
LED STATUS:
==================================================
GE PORTS : GE0GE1GE2GE3GE4
LINK LED : OFFOFFOFFOFFOFF
==================================================
PoE LED: GREEN
Cellular PORTS: Cellular0/0
RSSI LED 1 : Green
RSSI LED 2 : Off
RSSI LED 3 : Off
GPS LED: Off
SIM LED: Off
==================================================
Cellular PORTS: Cellular1/0
RSSI LED 1 : Green
RSSI LED 2 : Green
RSSI LED 3 : Off
GPS LED: Unknown
SIM LED: Off
==================================================
VPN LED: OFF
System LED: amber, blinking
IR829#show platform led
LED STATUS:
==================================================
GE PORTS : GE0GE1GE2GE3GE4
LINK LED : OFFOFFOFFOFFOFF
==================================================
PoE LED: GREEN
Cellular PORTS: Cellular0/0
RSSI LED 1 : Green
RSSI LED 2 : Off
RSSI LED 3 : Off
GPS LED: Off
SIM LED: Off
==================================================
Cellular PORTS: Cellular1/0
RSSI LED 1 : Green
RSSI LED 2 : Green
RSSI LED 3 : Off
GPS LED: Unknown
SIM LED: Off
==================================================
VPN LED: OFF
System LED: amber, blinking
IR829#show platform led summary
Ports LINK/ENABLE
--------+-------+------VPN LED: OFF
System LED: amber, blinking
IR829#
IR829#show platform led system
System LED: amber, blinking
Summary of the LED status providers:
The system LED is physically labeled SYS on IR809 and PWR on IR829. However, the software logic for
the system LED status works in the same way for both IR809 and IR829.
Note
By definition, amber blinking means the system has an error, but has network connectivity. For most of the
time, this amber blinking condition is seen because one or more of the Ethernet ports on your IR829 is in
administrative un-shut state, but there’s no actual link (e.g. cable disconnected or peer port is down etc.)
To make the status show solid green, ensure that the link on each administrative un-shut port connects a device
that is up, or you can put all disconnected ports in administrative shut state.
IR800#show platform led system
System LED: amber, blinking
Summary of the LED status providers:
------------------------------ -------- -------GigabitEthernet5critical OK
ClientTypeStatus
Unconnected ports in an un-shut state
IR800#sh platform led system
System LED: amber, blinking
Summary of the LED status providers:
------------------------------ -------- -------GigabitEthernet5critical OK
GigabitEthernet0critical OK
GigabitEthernet1critical OK
GigabitEthernet2critical failed
GigabitEthernet3critical failed
GigabitEthernet4critical failed
ClientTypeStatus
Un-connected ports in “shutdown” state
(config)#int range gigabitEthernet 2-4
(config-if-range)#shut
IR800#sh platform led system
System LED: green, on
Summary of the LED status providers:
------------------------------ -------- -------GigabitEthernet5critical OK
GigabitEthernet0critical OK
GigabitEthernet1critical OK
Note
There may be a lag time between the LED indication on the router and what the show led commands return.
Software Bundle Installation
The Cisco IR800 ships with the latest software available with the configuration that was ordered. There should
be no reason to have to upgrade unless a failure occurs, or you wish to install a new bundle to benefit from
new features. Should the need arise, the following steps will assist in performing a bundle installation.
Note
The bundle install will fail if “ip ssh source-interface” is configured. Make sure that none of the interfaces
have ssh running on them before performing the installation.
Initial Configuration
IR829#show run | inc ip ssh source
ip ssh source-interface GigabitEthernet0
IR829#
Displaing Digital Signature and Software Authenticity
Feature is new for release 15.8(3)M1 and applies to the IR8x9
Updates have been made to CLI commands due to unsupported file format errors:
• show software authenticity file <IOS image/SRP image/bundle image/GOS image>
With this feature enhancement, users will now be able to run these CLIs to display and verify digital signature
and software authenticity information for these types of signed files present in flash: partition only (IOS image,
Hypervisor image, bundle image and Guest-OS image) supported on the IR8x9
Address or name of remote host [192.168.254.254]? your ip address here
Source filename [path to file/ir800-universalk9-bundle.SSA.156-2.10.62.GB]? <enter>
Destination filename [ir800-universalk9-bundle.SSA.156-2.10.62.GB]? <enter>
Accessing tftp://192.168.254.254/tachen/ir800-universalk9-bundle.SSA.156-2.10.62.GB...
Loading tachen/ir800-universalk9-bundle.SSA.156-2.10.62.GB from 192.168.254.254 (via Vlan1):
!
*Jun 25 18:28:45.685: %ARP-4-NULL_SRC_MAC: NULL MAC address from 172.16.0.1 on
wl0!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 161162048 bytes]
161162048 bytes copied in 466.054 secs (345801 bytes/sec)
Step 2The bundle download is complete, and now needs to be installed. Perform the bundle install flash: < bundle
Step 5Verify the boot system parameter before reloading the router.
Step 6Save the configuration and reload the router.
Example:
IR800#reload
Do you want to reload the internal AP ? [yes/no]: yes
System configuration has been modified. Save? [yes/no]: yes
Building configuration...
[OK]
Proceed with reload? [confirm] <enter>
*Jun 25 19:03:13.685: %SYS-5-RELOAD: Reload requested by console. Reload Reason: Reload
Command.
Step 7Download the 4G firmware or AP image. Instructions for uploading firmware are located here:
Used to automatically delete the bundle and free up flash: memory after installation is
complete.
rom-autoboot
Used to save autoboot information in rommon.
This configuration was exclusively introduced for PnP feature.
Setting this will ensure that even if there is 'no boot system', the router will bootup with
IOS image available in the flash: file system.
The IOS image picked will be the one that matches with the bundle, not the first or any
random IOS image in the flash: file system.
If a 'write erase' command is executed followed by reload, the router will boot back into
an IOS prompt, and not be stuck at rommon2.
The following items are important to remember when using bundle install:
• The default bundle install flash: ensures that the boot system flash: is set each time. The default will
bootup all three images - hypervisor, native IOS and guest-os alike.
• Software mix-and-match between the three images is not supported. The router can only be fully functional
if all three images are from the same bundle.
• Cellular modem firmware upgrade is not inclusive in a bundle installation.
• In IOS mode, verify show platform nvram does not have BOOT_MCU_FW_UPGRADE=NEVER and
BOOT_FPGA_FW_UPGRADE=NEVER.
• After a bundle installation, it is mandatory the router be reloaded. Prior to a reload, most operations will
be non-functional.
Power Over Ethernet (PoE)
The IR829 has an optional PoE accessory (IR800-IL-POE). When installed, it supplies a maximum of 30.8W
shared between the 4 GE LAN ports (GI1-GI4). The Power can be distributed among the ports in the following
manner:
• If one port supports PoE+ (30W), then the other ports have no PoE.
• If 2 ports support PoE (15.4 W), then the other ports have no PoE.
• All 4 ports can support 7.7 W per port.
Note
The router cannot be upgraded for PoE in the field.
IOS supports bi-directional inline power negotiations with Cisco devices through the use of CDP. Cisco Power
Devices (PDs) may signal increase or decrease in their demand for power through CDP. Decrease in demand
will result in returning unused power to the pool of available power. Increase in demand will be accommodated,
subject to the available unused power and the port power limit (and 802.3at classification where applicable).
LLDP (Link Layer Discovery Protocol) Support for 3rd party PoE devices
If the PDs do not support CDP, the inline power allocation is based on the classification if they are 802.3at
devices or 15.4W if not 802.3at compliant.
LLDP (Link Layer Discovery Protocol) Support for 3rd party PoE devices
This feature applies to the IR829 only.
Previously, the IR829 supported PoE allocation/negotiation only for the PD (Powered Devices) which
communicate using CDP (Cisco Discovery Protocol). With this release, support is added for Link Layer
Discovery Protocol.
LLDP is a vendor-neutral CDP like neighbor discovery protocol that is used by network devices to advertise
information about themselves to other devices on the network. LLDP supports a set of attributes that it uses
to discover neighbor devices. These attributes contain type, length, and value descriptions and are referred to
as TLVs. LLDP supported devices can use TLVs to receive and send information to their neighbors.
Details such as configuration information, device capabilities, and device identity can be advertised using this
protocol. LLDP for Media Endpoint Devices (LLDP-MED) is an extension to LLDP that operates between
endpoint devices such as IP phones and network devices such as switches. LLDP-MED specifically provides
support for voice over IP (VoIP) applications and provides additional TLVs for capabilities discovery, network
policy, power over Ethernet (PoE), inventory management, and location information. LLDP-MED contains
power management TLV which allows PD (power device) to request power. Power TLV defines the format
for power request.
Once power is applied to the port, LLDP-MED (Power TLV) is used to determine the actual power requirement
of PDs and the system power budget is adjusted accordingly. The router processes the request and either grants
or denies power based on the current power budget. If the request is granted, then the router simply updates
the power budget. If the request is denied, the router turns OFF power to the port, generates a syslog message,
and updates the power budget and LEDs.
If LLDP-MED is disabled or if the PD does not support the LLDP-MED power TLV, then the initial allocation
value is used throughout the duration of the connection. No new CLIs are added and the following commands
can be used to troubleshoot.
Used in interface config mode, this command configures inline power support and optionally specifies a
maximum inline power level in milliwatts.
IR800(config-if)#power inline auto
IR800(config-if)#power inline never
IR800(config-if)#power inline port max 30000
show lldp
{entry | interface | neighbors | traffic}
Used in exec mode, this command shows information for LLDP running status, specific neighbor entry,
interface status and configuration, neighbor entries, and statistics.
IR800# show lldp entry *
Capability codes:
(R) Router, (B) Bridge, (T) Telephone, (C) DOCSIS Cable Device
(W) WLAN Access Point, (P) Repeater, (S) Station, (O) Other
Total entries displayed: 0
Switch#show lldp entry *
Capability codes:
(R) Router, (B) Bridge, (T) Telephone, (C) DOCSIS Cable Device
(W) WLAN Access Point, (P) Repeater, (S) Station, (O) Other
-----------------------------------------------Chassis id: 192.168.1.11
Port id: 002584184414:P1
Port Description: SW PORT
System Name: SEP002584184414.DMSBU.com
System Description:
Cisco IP Phone 9971, V1, sip9971.9-3-0RT1-100dev
Time remaining: 154 seconds
System Capabilities: B,T
Enabled Capabilities: B,T
Management Addresses:
IP: 192.168.1.11
Auto Negotiation - supported, enabled
Physical media capabilities:
PD device, Power source: PSE, Power Priority: High, Wattage: 10.6
Location - not advertised
Total entries displayed: 1
Note: PoE port power priority (Critical, High, Low, default) and Power policing are not supported.
Serial Port Configuration
Before you begin
Serial Port configuration on the IR800 series depends on having proper cabling to start with. Before you
configure the serial port of the IR809 or IR829, make sure to read the serial port section of the IR829 Hardware
Installation Guide:https://www.cisco.com/c/en/us/td/docs/routers/access/800/829/hardware/install/guide/
829hwinst/pview.html#85723
Note
The serial port can be used either by IOS, or through an IOx application.
To specify an asynchronous serial interface and enter interface configuration mode, use one of the following
commands in global configuration mode.
IR800#sh run int async 0
Building configuration...
Current configuration : 62 bytes
!
interface Async0
no ip address
encapsulation raw-tcp
end
Configuring Accelerometer and Gyroscope
Ensure that your router is running IOS version 15.6(3)M1 or above.
Accelerometer and Gyroscope functionality tracks the speed and angular movement of the device.Two
configuration CLIs and one show CLI are available:
IR829(config)#[no] gyroscope-reading enable
Initial Configuration
Once this is enabled, gyroscope reading will start by the frequency currently set. Prior to IOS release 15.7(3)M1,
the format of the command was:
IR829 (config)#gyroscope-reading frequency ?
1/min Reading 1 times per minute
1/sec Reading 1 time per second
10/min Reading 10 times per minute
From IOS release 15.7(3)M1 going forward, the format has been modified to:
IR829 (config)#gyroscope-reading frequency ?
one/min Reading 1 times per minute
one/sec Reading 1 time per second (default value)
ten/min Reading 10 times per minute
Note
After upgrading to IOS release 15.7(3)M1, the router will have to be reconfigured.
Default frequency is 1/sec. If this is configured, it would overwrite default frequency and any later reading
would be according to the newly set frequency.
This CLI would only show data if "gyroscope-reading" is enabled. All readings since start (unless wrap-around
occurs, which means table is full), would be shown in the order from the most recent to the oldest.
Auto-Negotiation Support for Gigabit-Ethernet 0 on the IR829
Each entry shows G-X, Y, Z(3D gyroscope data) in mdps (Milli Degrees Per Second) and XL-X,Y, Z (3D
accelerator data) in unit mg (milli g forces) where g is ≈ 9.81 m/s 2 .
Note
Configurations would be in running-config and would stay over reload if saved.
A new MIB/OID is available to support the following SNMP operations:
• SNMPwalk: snmpwalk is used to fetch all values of a sub tree under the MIB table or value of particular
OID.
• SNMPget: snmpget is used to fetch the value of a particular OID.
The entity OID value is iso.3.6.1.4.1.9.12.3.1.8.230.
The show platform gyroscope command gives information about this MIB.
Auto-Negotiation Support for Gigabit-Ethernet 0 on the IR829
The IR829 product series (with a 1000Base-T SFP) only supported a fixed speed of 1000Mbps. To enable
multiple speed support Cisco introduced auto-negotiation as the default speed on Gigabit-Ethernet 0.
It is highly recommended to use auto-negotiation on both sides of the network for best performance results.
Once auto-negotiation is initiated, the device (PHY) determines whether or not the remote device has
auto-negotiation capability. If so, the device and the remote device negotiate the speed and duplex with which
to operate. If the remote device does not have auto-negotiation capability, the device uses the parallel detect
function to determine the speed of the remote device for 100BASE-TX and 10BASE T modes. If the link is
established based on the parallel detect function, then it is required to establish the link at half duplex mode
only. Refer to IEEE 802.3 clauses 28 and 40 for a full description of auto-negotiation.
Note: Auto-Negotiation is enabled by default. There is no CLI configuration.
Where To Go From Here
There are a wide variety of configuration options available on the Cisco IR800. This guide provides information
on the most common options. Use the following resources for additional information:
Cisco 800 Series Industrial Integrated Services Routers
This chapter provides configuration details for the cellular interface modules used in the IR800 series routers.
It is important to understand the architecture of the IR800 series and the relationship between Modems, SIMs,
Interface and Controller. The following table helps to illustrate these relationships.
Modem
SIMControllerRouter
Slot
*
*
*
*
Note
Check the Product Marketing Data Sheet for updated modem information.
Interface
LinePDN
3Cellular 000|10IR829
8Cellular 100|10IR829
3Cellular 0/0000IR829 (dual modem)
8Cellular 0/1000IR829 (dual modem)
9Cellular 1/0111IR829 (dual modem)
15Cellular 1/1111IR829 (dual modem)
3Cellular 000|10IR809
8Cellular 100|10IR809
With the introduction of the next generation SKUs, some functionality has changed. Refer to the following
table for details.
• Troubleshooting the Cellular Interface, on page 67
2.4 GHz and 5GHz use separate
antenna connector
Yes
Note
2.4 GHz + 5GHz coexist on the same
antenna connector
NoYesDual SIM
NoNoBand 30
cat4cat4LTE category supported
Only available from the first
LTE Modem.
Cellular Interface
The Cisco IR800 series Industrial routers use the Sierra Wireless MC73XX and MC74XX series modems
supporting MIMO on LTE. WCDMA UMTS HSPA DC-HSPA+ is diversity only, without MIMO.
Installation of the SIM card(s) and antennas is covered in the respective Hardware Installation Guides under
the Cisco 800 Series Industrial Integrated Services Routers page:
After installing the SIM card(s) and antennas, check the cellular hardware, radio, network and SIM (Unlock
SIM card if necessary).
4G LTE Dual SIM
Dual Subscriber Identity Module (SIM) provides reliability and multihoming capabilities over LTE and
HSPA-based networks. With two LTE modems, the IR829 enables concurrent connectivity to two cellular
networks for high reliability, enhanced data throughputs, load balancing and differentiated services.
Note
Dual SIM active/backup mode is supported only on single LTE models of the IR829.
The following features are provided:
4G LTE Dual SIM
• The two SIMs operate in active/backup mode on the single LTE models of the IR829, and active/active
mode with each of the two SIMs assigned to a specific cellular radio on the dual LTE models. Both
mobile provider networks must be supported by the given IR829 SKU, and it must be in an applicable
region.
• By default, SIM slot 0 is the primary, and SIM slot1 is the backup. Behavior may be changed using the
lte sim primary command.
• Profiles for each SIM are assigned by using the lte sim profile command. Each SIM has an associated
Internet profile and an IMS profile in the CLI.
• Dual-SIM behavior is managed under Cellular 0 CLI configuration.
• The fail over occurs when there is no signal from the current carrier, and generally happens depending
on the fail over timer value that is set. The default value is 5 minutes. The range is from 0-7 minutes..
• Dual active LTE radios providing Multi-carrier support for active and backup use cases. Newer cellular
modems have been added (MC74xx) with FDD/TDD LTE on LA and EA 829 models.
Note
The 7455 modems do not support dual SIM capabilities.
AutoSim and Firmware Based Switching
The advantages of the AutoSim feature are:
• Ease of Ordering Carrier Specific SKUs
• Quicker failover times in dual-sim deployments
• Ease of switchover from other service providers to Telstra network
Auto-SIM is supported in Sierra wireless firmware Version 02.20.03. A new CLI is added in the cellular
controller to enable/disable Auto-SIM. The modem in Auto-SIM mode selects the right carrier firmware after
a SIM slot switch and an automatic modem reset. Auto-SIM is supported on the MC7455, MC7430, EM7430,
Dual Radio Configuration and Single Radio Configuration
and EM7455 modems. During bootup, if the Auto-SIM configuration on the modem doesn’t match to the IOS
configuration, the corresponding Auto-SIM or manual mode is pushed to the modem.
After an Auto-SIM configuration change, the modem is automatically reset; the default is “auto-sim” enabled.
Enable Auto-SIM:
router(config)#controller cellular <slot>
router(config-controller)#lte firmware auto-sim #default is auto-sim enabled
Note
After enabling auto-sim, wait for 5 minutes until the radio comes up. Once the radio is up, issue a modem
power-cycle and wait for 3 minutes for the radio to come up again. Modem Power-Cycle is mandatory for
auto-sim configuration to take effect.
After disabling auto-sim, wait for 5 minutes until the radio comes up. Once the radio is up, issue a modem
power-cycle and wait for 3 minutes for the radio to come up again. Modem Power-Cycle is mandatory for
auto-sim configuration to take effect.
If Auto-SIM is disabled and the modem is in manual mode, select a carrier with a new exec CLI:
cellular lte firmware-activate <firmware-index>
The following CLI example shows the firmware-index of the carrier in the modem:
router#show cellular <slot> firmware
For additional information, see the following guide:https://www.cisco.com/c/en/us/td/docs/routers/access/
Dual Radio Configuration and Single Radio Configuration
shutdown
!
interface GigabitEthernet1
no ip address
!
interface GigabitEthernet2
no ip address
!
interface GigabitEthernet3
no ip address
!
interface GigabitEthernet4
no ip address
!
interface Wlan-GigabitEthernet0
no ip address
!
interface GigabitEthernet5
no ip address
shutdown
duplex auto
speed auto
!
interface Cellular0/0
#Both interfaces need to be configured in the IOS software
Cellular Interface Modules
ip address negotiated
ip virtual-reassembly in
encapsulation slip
load-interval 30
dialer in-band
dialer string lte
dialer-group 1
no peer default ip address
async mode interactive
routing dynamic
!
interface Cellular1/0
#Both interfaces need to be configured in the IOS software
ip address negotiated
ip virtual-reassembly in
encapsulation slip
load-interval 30
dialer in-band
dialer string lte
dialer-group 1
no peer default ip address
async mode interactive
routing dynamic
!
interface Cellular0/1
no ip address
encapsulation slip
!
interface Cellular1/1
no ip address
encapsulation slip
!
interface wlan-ap0
no ip address
!
interface Vlan1
no ip address
!
Dual Radio Configuration and Single Radio Configuration
interface Async0
no ip address
encapsulation scada
!
interface Async1
no ip address
encapsulation scada
!
!
ip forward-protocol nd
!
no ip http server
no ip http secure-server
!
ip route 0.0.0.0 0.0.0.0 Cellular1/0
ip route 8.8.8.8 255.255.255.255 Cellular0/0
Route values added
!
dialer-list 1 protocol ip permit
ipv6 ioam timestamp
!
access-list 1 permit any
!
control-plane
!
!
line con 0
stopbits 1
line 1 2
stopbits 1
line 3
script dialer lte
no exec
transport preferred lat pad telnet rlogin lapb-ta mop udptn v120 ssh
transport output lat pad telnet rlogin lapb-ta mop udptn v120 ssh
rxspeed 150000000
txspeed 50000000
line 4
no activation-character
no exec
transport preferred none
transport input all
transport output lat pad telnet rlogin lapb-ta mop udptn v120 ssh
l
ine 8
script dialer lte
no exec
transport preferred lat pad telnet rlogin lapb-ta mop udptn v120 ssh
transport output lat pad telnet rlogin lapb-ta mop udptn v120 ssh
rxspeed 150000000
txspeed 50000000
line 9
script dialer lte
no exec
transport preferred lat pad telnet rlogin lapb-ta mop udptn v120 ssh
transport input all
transport output lat pad telnet rlogin lapb-ta mop udptn v120 ssh
rxspeed 236800
txspeed 118000
line 15
no exec
transport preferred lat pad telnet rlogin lapb-ta mop udptn v120 ssh
transport output lat pad telnet rlogin lapb-ta mop udptn v120 ssh
rxspeed 236800
txspeed 118000
line 1/3 1/6
transport preferred none
transport output none
stopbits 1
line vty 0 4
login
transport input none
!
no scheduler max-task-time
!!
End
Test the modem configuration with a ping command:
DUAL-Modem# ping 8.8.8.8
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 8.8.8.8, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 30/88/292 ms
DUAL-Modem#
Verizon Profile
The following two examples show a Verizon profile followed by an AT&T profile.
DUAL-Modem# show cellular 0/0 profile
Profile 1 = INACTIVE **
-------PDP Type = IPv4v6
Access Point Name (APN) = vzwims
Authentication = None
Profile 2 = INACTIVE
-------PDP Type = IPv4v6
Access Point Name (APN) = vzwadmin
Authentication = None
Profile 3 = ACTIVE*
Profile 3 is used for Verizon
-------PDP Type = IPv4v6
PDP address = 166.140.43.237
Access Point Name (APN) = we01.VZWSTATIC
Authentication = None
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
Authentication = None
Profile 5 = INACTIVE
-------PDP Type = IPv4v6
Access Point Name (APN) = vzw800
Authentication = None
Profile 6 = INACTIVE
-------PDP Type = IPv4v6
Access Point Name (APN) = vzwenterprise
Authentication = None
* - Default profile
** - LTE attach profile
DUAL-Modem# show cellular 1/0 profile
Profile 1 = ACTIVE* **
Profile 1 is used for AT&T
-------PDP Type = IPv4
PDP address = 10.61.25.231
Access Point Name (APN) = m2m.com.attz
Authentication = None
Primary DNS address = 8.8.8.8
Secondary DNS address = 8.8.4.4
* - Default profile
** - LTE attach profile
DUAL-Modem# show cellular 0/0 hardware
Modem Firmware Version = SWI9X30C_02.20.03.00
Modem Firmware built = 2016/06/30 10:54:05
Hardware Version = 1.0
Device Model ID: MC7455MOBILE
International Mobile Subscriber Identity (IMSI) = 311480166946902
International Mobile Equipment Identity (IMEI) = 352009080050110
Integrated Circuit Card ID (ICCID) = 89148000001653263375
Mobile Subscriber Integrated Services
Digital Network-Number (MSISDN) = 6692200807
Modem Status = Online
Current Modem Temperature = 34 deg C
PRI SKU ID = 1103084, PRI version = 002.024, Carrier = Verizon
Carrier identified as Verizon
OEM PRI version = 000.001
Creating a Cellular Profile for Verizon.
DUAL-Modem# cellular 0/0 lte profile create 3 we01.VZWSTATIC
Warning: You are attempting to modify a currently ACTIVE data profile.
This is not recommended and may affect the connection state
PDP Type = IPv4v6
Access Point Name (APN) = we01.VZWSTATIC
Authentication = NONE
Profile 3 already exists with above parameters. Do you want to overwrite? [confirm] <return>
Profile 3 will be overwritten with the following values:
PDP type = IPv4
APN = we01.VZWSTATIC
Authentication = NONE
Are you sure? [confirm] <return>
Profile 3 written to modem
DUAL-Modem#
Enter configuration commands, one per line. End with CNTL/Z.
DUAL-Modem(config)# controller cellular 0
DUAL-Modem(config-controller)# lte sim data-profile 3 attach-profile 1
DUAL-Modem(config-controller)#
DUAL-Modem# conf t
Enter configuration commands, one per line. End with CNTL/Z.
DUAL-Modem(config)# controller cellular 0
DUAL-Modem(config-controller)# lte sim data-profile 3 attach-profile 1
DUAL-Modem(config-controller)# end
DUAL-Modem#
DUAL-Modem# show
*Oct 24 19:43:44.841: %SYS-5-CONFIG_I: Configured from console by consolecell
DUAL-Modem# show cellular 1/0 profile
Profile 1 = ACTIVE* **
-------PDP Type = IPv4
PDP address = 10.61.185.213
Access Point Name (APN) = m2m.com.attz
Authentication = None
Primary DNS address = 8.8.8.8
Secondary DNS address = 8.8.4.4
* - Default profile
** - LTE attach profile
Creating a Cellular Profile for AT&T
Cellular Interface Modules
DUAL-Modem# cellular 1/0 lte profil create 1 m2m.com.attz
Warning: You are attempting to modify a currently ACTIVE data profile.
This is not recommended and may affect the connection state
PDP Type = IPv4
Access Point Name (APN) = m2m.com.attz
Authentication = NONE
Profile 1 already exists with above parameters. Do you want to overwrite? [confirm] <return>
Profile 1 will be overwritten with the following values:
PDP type = IPv4
APN = m2m.com.attz
Authentication = NONE
Are you sure? [confirm] <return>
Profile 1 written to modem
DUAL-Modem#
DUAL-Modem# conf t
Enter configuration commands, one per line. End with CNTL/Z.
DUAL-Modem(config)# controller cellular 1
DUAL-Modem(config-controller)#
DUAL-Modem(config-controller)# lte sim data-profile 1 attach-profile 1
Note: Please issue a modem reset for the modified attach-profile to take effect.
DUAL-Modem(config-controller)# end
DUAL-Modem#
Controller Cellular 0 and NAT Configuration
Controller Cellular 0 is configured with default parameters. If a profile different from Profile 1 is set-up, it
must be attached to controller cellular 0.
If the SIM in slot #1 must be used as primary, it is done under controller cellular 0
IR800#conf term
Enter configuration commands, one per line. End with CNTL/Z.
IR800(config)#inter cellular 0
IR800(config-if)#ip nat outside
IR800(config)#inter vlan 4
IR800(config-if)#ip nat inside
IR800(config)#access-list 10 permit 10.20.20.0 0.0.0.255
!
IPv4 subnet to be NATed
IR800(config)# ip nat inside source list 10 interface Cellular0 overload
!
NAT interface association
Step 3Once the Cellular configuration is done, ping a well-known IP address to test the connectivity.
Example:
IR800#ping 8.8.8.8
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 8.8.8.8, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 340/472/740 ms
IR800#
Step 4Attached Cellular 0 profile must become “active” and “connection” shows IP address and traffic.
Data Transmitted = 700 bytes, Received = 600 bytes
IP address = 10.60.159.255
Primary DNS address = 212.27.40.240
Secondary DNS address = 212.27.40.241
Profile 2, Packet Session Status = INACTIVE
What to do next
Use the show interface cellular 0 command to display the negotiated IP address if operational.
IR800#show interfaces cellular 0
Cellular0 is up, line protocol is up
Hardware is 4G WWAN Modem - Global (Europe & Australia) Multimode LTE/DC-HSPA+/HSPA+/HSPA/U
Internet address is 10.123.161.59/32
MTU 1500 bytes, BW 384 Kbit/sec, DLY 100000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation SLIP, loopback not set
Keepalive not supported
Last input 00:22:41, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/10 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up
IR800#
If the negotiated IP address in not operational:
IR800#show interfaces cellular 0
Cellular0 is up (spoofing), line protocol is up (spoofing)
Hardware is 4G WWAN Modem - Global (Europe & Australia) Multimode LTE/DC-HSPA+/HSPA+/HSPA/U
Internet address will be assigned dynamically by the network
Other Useful Commands
IR800# show cell 0 hardware
Modem Firmware Version = SWI9X15C_05.05.58.00
Modem Firmware built = 2015/03/04 21:30:23
Hardware Version = 1.0
Device Model ID: MC7304
Package Identifier ID: 1102029_9903299_MC7304_05.05.58.00_00_Cisco_005.010_000
International Mobile Subscriber Identity (IMSI) = 208150103324395
International Mobile Equipment Identity (IMEI) = 352761060206340
Integrated Circuit Card ID (ICCID) = 8933150112100222053
Mobile Subscriber Integrated Services
Digital Network-Number (MSISDN) = 33695764790
Current Modem Temperature = 47 deg C
PRI SKU ID = 9903299, PRI version = 05.10, Carrier = 1
IR800# show cell 0 security
Active SIM = 0 !
SIM slot #0 active
SIM switchover attempts = 0
Card Holder Verification (CHV1) = Disabled
SIM Status = OK
SIM User Operation Required = None
Number of CHV1 Retries remaining = 3
IR800# cellular 0 lte sim unlock XXXX
!
XXXX = PIN code
IR800# show cell 0 radio
Radio power mode = ON
Channel Number = 3037
Current Band = Unknown
Current RSSI(RSCP) = -99 dBm
Current ECIO = -10 dBm
Radio Access Technology(RAT) Preference = AUTO
Radio Access Technology(RAT) Selected = UMTS ( UMTS/WCDMA )
IR800# show cell 0 network
Current System Time = Sat Oct 10 9:12:59 2015
Current Service Status = Normal
Current Service = Packet switched
Current Roaming Status = Home
Network Selection Mode = Automatic
Network = LTE
Mobile Country Code (MCC) = 208
Mobile Network Code (MNC) = 15
Packet switch domain(PS) state = Attached
Location Area Code (LAC) = 3910
Cell ID = 222094374
IR800# show cell 0 all
Note
The output to the show cell 0 all command is extensive, and omitted from this guide for brevity.
Accessing 4G Modem AT Commands
Note
A password must be added to the line configuration for security.
Get the line number associated to Cellular 0:
IR800#show line
Tty Line TypTx/RxA Modem Roty AccO AccI Uses Noise Overruns In
I33 TTY -----104/0Ce0
Use one of the IR800 IP address along with 2000 + line number (2003)
IR800#10.15.15.1 2003
Trying 10.15.15.1, 2003 ... Open
Execute the 4G modem AT commands, for example AT!GSTATUS?:
AT!GSTATUS?
!GSTATUS:
Current Time: 213353 Temperature: 38
Bootup Time:0 Mode:ONLINE
System mode:WCDMAPS state:Attached
WCDMA band:WCDMA 900
WCDMA channel: 3037
GMM (PS) state:REGISTEREDNORMAL SERVICE
MM (CS) state: IDLENORMAL SERVICE
WCDMA L1 state:L1M_PCH_SLEEPLAC:0F46 (3910)
RRC state:DISCONNECTEDCell ID:0D3CE428 (222094376)
RxM RSSI C0:-90 RxD RSSI C0: -106
RxM RSSI C1:-106 RxD RSSI C1: -106
Disconnect using “SHIFT+CONTROL+6+x”, then confirm:
Cellular Interface Modules
IR800#disc
Closing connection to 10.2.2.2 [confirm]enter
IR800#
Checking 4G Modem Firmware through AT Commands
To check the IR800 4G modem firmware, execute the 4G modem AT commands after connecting to the
modem. The following example is for an IR809G-LTE-GA-K9 loaded with FW-MC7304-LTE-GB Global
firmware.
Note
On the IR809, the PRI SKU ID= 9903299 is not representative of the GB firmware
at!priid?
PRI Part Number: 9903299
Revision: 05.10
Carrier PRI: 9999999_9902674_SWI9X15C_05.05.58.00_00_GENEU-4G_005.026_000
OK
This new feature allows the user to configure and lock down the modem to a specific RF band, or set of bands.
The preference can be set to be equal to, or a sub-set of the capability supported by the modem/carrier
combination.
The following examples show the controller configuration commands:
router# conf t
Enter configuration commands, one per line. End with CNTL/Z.
router(config)#controller cell interface number
router(config-controller)#lte modem ?
band-selectModem band select
dm-logModem DM logging configuration
fota-poll-timer Set poll timer for AVMS to do Firmware upgrade over the air
link-recoveryCellular Link Recovery
mtuModem mtu
nas-logModem NAS logging configuration
Radio Frequency Band Select
router(config-controller)#lte modem band-select ?
all-lte-onlyChoose all LTE bands only
all-nonlte-only Choose all non-LTE bands only
band-indicesSpecify the lte and non-lte band indices
88 - WCDMA US PCS 1900 band
90 - WCDMA US 1700 band
91 - WCDMA US 850 band
Non-LTE band Preference settings for the active sim(slot 0):
Index:
88 - WCDMA US PCS 1900 band
90 - WCDMA US 1700 band
91 - WCDMA US 850 band
IR807#show run | sec controller
controller Cellular 0
no lte gps enable
lte modem crash-action boot-and-hold
lte modem fota-poll-timer 15
lte modem mtu 1700
lte modem link-recovery disable
IR800#
Low Power Mode
This feature provides the reason for the modem going into a low power mode if the situation ever occurs. It
uses the device power control information provided by the modem. A new CLI has been implemented showcellular <interface> radio details.
router# show cellular <interface number> radio
Radio power mode = OFF, Reason = User Request
Channel Number = 0
Current Band = Unknown
Current RSSI = -128 dBm
Current ECIO = -2 dBm
Radio Access Technology(RAT) Preference = AUTO
Radio Access Technology(RAT) Selected = AUTO
router# show cellular <interface number> radio details
Radio turned off under cellular controller configuration.
router#
Note: In the above show cellular <interface number> radio output, the Radio power mode shows OFF
because the user has turned the radio off by choice. In all other cases, when the radio goes to Low Power
mode, you will see the display Radio power mode = low power.
Enhancement to Modem Crash Action
If the modem corresponding to the cellular interface crashes, the modem will reset itself and come back up.
However, in order to debug the cause of the crash, a full crash dump can be captured on the modem. The steps
to capture the crashdump are outlined in:
A new CLI has been added to set the crash action on the modem upon a crash. The CLI is lte modemcrash-action ?. The device can be set to either reset, or to boot and hold.
The following example shows the new functionality of the configuration CLI:
This CLI will show the current state the modem is set to. This is the same as AT command at!eroption=?.
IR800 Cellular Technology Selection
The cellular interface supports a seamless hand off between LTE and 3G networks when the LTE cell becomes
weak in certain spots and vice versa. But it may also be disable to lock the cellular interface in a given
technology, for example. LTE.
The cellular interface supports 3G and 2.5G technologies. The IOS CLI can be used to select a particular
technology that is most desirable in your local zone.
Use the cellular 0 lte technology command:
IR829# cellular 0 lte technology ?
!
Blue
values available on Global SKU
autoAutomatic LTE Technology Selection
cdma-1xrttCDMA 1xRTT
cdma-evdoCDMA EVDO Rev A
cdma-hybrid HYBRID CDMA
gsmGSM
lteLTE
umts UMTS
Note
The default technology type selection is auto, and it is recommended to be used at all times. Although gsm
and umts are part of the selection, the modem firmware does not support them on gsm/umts network. They
will be used as lte selection on a Verizon network.
Show the completed configuration: (output edited for brevity)
IR800#show run
Building configuration...
Current configuration : 4365 bytes
!
! Last configuration change at 09:53:09 UTC Sat Oct 10 2015 by cisco
!
version 15.5
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname IR800
!
boot-start-marker
boot system flash:/ir800-universalk9-mz.SPA.155-3.M0a
boot-end-marker
!
enable password cisco
!
aaa new-model
!
aaa session-id common
ethernet lmi ce
!
ip dhcp pool GuestOS
encapsulation scada
!
ip forward-protocol nd
!
no ip http server
no ip http secure-server
!
ip route 0.0.0.0 0.0.0.0 Cellular0
ip ssh time-out 60
!
dialer-list 1 protocol ip permit
!
control-plane
!
line con 0
stopbits 1
line 1 2
stopbits 1
line 3
script dialer LTE
modem InOut
no exec
transport preferred lat pad telnet rlogin lapb-ta mop udptn v120 ssh
transport input telnet
transport output lat pad telnet rlogin lapb-ta mop udptn v120 ssh
speed 384000
line 8
script dialer LTE
modem InOut
no exec
transport preferred lat pad telnet rlogin lapb-ta mop udptn v120 ssh
transport output lat pad telnet rlogin lapb-ta mop udptn v120 ssh
speed 384000
line 1/3 1/6
transport preferred none
transport output none
stopbits 1
line vty 0 4
password cisco
transport input telnet ssh
!
no scheduler max-task-time
!
end
IR800#
The IR800 series can be configured to enable real-time location tracking of remote assets and geo-fence when
used with IOT Field Network Director. Field Network Director receives GPS data directly from IOS, not
NMEA.
Key Points:
• GPS must be configured under controller cellular 0.
• GPS can be assigned to Cellular AUX antenna.
• GPS data can be seen locally, or data stream can be forwarded to applications, i.e. RUBAN.
Note
On the IR829 dual-LTE model, GPS can only be configured on cellular 0/0.
For information about the GPS LED indications and locations of the GPS connectors, see IR829 Product
Overview and IR809 Product Overview .
To configure GPS on the IR800 series, refer to the following examples.
IR829# conf term
IR829(config)#controller cellular 0
IR829(config-controller)#lte gps ?
enable enable GPS feature
modeselect GPS mode
nmeaenable NMEA data
IR829(config-controller)#lte gps mode standalone
IR829(config-controller)#lte gps nmea ip
IR829#show cellular 0 gps
GPS Info
------------GPS Feature: enabled
GPS Port Selected: Dedicated GPS port
GPS State: GPS enabled
GPS Mode Configured: standalone
Latitude: 48 Deg 38 Min 31.2114 Sec North
Longitude: 2 Deg 13 Min 47.3992 Sec East
Timestamp (GMT): Wed Jul 22 08:05:28 2015
You can also configure IOS so that GPS can be streamed to another destination (port or address).
For example:
IR829#conf t
Enter configuration commands, one per line. End with CNTL/Z.
IR829(config)#controller cellular 0
IR829(config-controller)#lte gps nmea ?
ipNMEA over IP interface
serial NMEA over serial interface
IR829(config-controller)#lte gps nmea ip ?
udp UDP Transport
<cr>
IR829(config-controller)#lte gps nmea ip udp ?
A.B.C.D Source address
IR829config-controller)#lte gps nmea ip udp 10.3.4.5 ?
A.B.C.D Destination address
IR829(config-controller)#lte gps nmea ip udp 10.1.1.1 10.3.4.5 ?
<0-65535> Destination port
IR829(config-controller)#lte gps nmea ip udp 10.1.1.1 10.3.4.5 3456
Cellular Modem in HWIC slot 0/0 is still in reset, we recommend to re-execute this cmd after
60 seconds
IR829(config-controller)#
The Command Line Interface for the gyroscope feature has been changed in IOS Release 15-7-3M1 in order
to be compatible with the CCP Express NMS. The old CLI format was:
IR829(config)#gyroscope-reading frequency ?
1/min Reading 1 times per minute
1/sec Reading 1 time per second (default value)
10/min Reading 10 times per minute
From this release going forward, the format has been modified to:
IR829(config)#gyroscope-reading frequency ?
one/min Reading 1 times per minute
one/sec Reading 1 time per second (default value)
ten/min Reading 10 times per minute
After upgrading to this release, the router will have to be reconfigured.
Router(config-controller)#lte gps nmea ip udp 20.20.0.1 20.20.0.10 2057 stream 1
Stream number 1 is already active.
Please remove stream number configuration before creating it with different destination ip address and port
number.
Troubleshooting the Cellular Interface
These procedures are to capture information to share with support in order to assist them in helping to
troubleshoot an issue with the cellular interface. In order to capture logs, DM logs must be enabled. Refer to
the following:https://www.cisco.com/c/en/us/td/docs/routers/access/800/819/user/guide/
3G4G-enhancements-userguide.html#pgfId-1063363
The following are steps to capture Linux logs for the cellular interface.
Procedure
Step 1Set up the fetch command.
Example:
# conf t
# service internal
# exit
# vds fetch-log
These steps will generate a directory on flash:vds-log.
24 -rw-510 Nov 16 2016 19:06:44 +00:00 4gmodem.log
25 -rw-162330 Nov 16 2016 19:06:54 +00:00 auth.log
26 -rw-262215 Nov 16 2016 19:07:04 +00:00 auth.log.1
27 -rw-11297 Nov 16 2016 19:07:16 +00:00 auth.log.2.gz
28 -rw-11296 Nov 16 2016 19:07:24 +00:00 auth.log.3.gz
29 -rw-3875716 Nov 16 2016 19:07:42 +00:00 cwan_modem0.log
30 -rw-791629 Nov 16 2016 19:07:54 +00:00 cwan_modem1.log
31 -rw-1404 Nov 16 2016 19:08:04 +00:00 daemon.log
32 -rw-13740 Nov 16 2016 19:08:14 +00:00 dmesg
33 -rw-0 Nov 16 2016 19:08:24 +00:00 dmesg.0
34 -rw-1091 Nov 16 2016 19:08:32 +00:00 ios_cs_verify.log
35 -rw-219169 Nov 16 2016 19:08:42 +00:00 ios_vds_com.log
36 -rw-262207 Nov 16 2016 19:08:54 +00:00 ios_vds_com.log.1
37 -rw-7859 Nov 16 2016 19:09:04 +00:00 ios_vds_com.log.2.gz
38 -rw-7894 Nov 16 2016 19:09:14 +00:00 ios_vds_com.log.3.gz
39 -rw-38608 Nov 16 2016 19:09:24 +00:00 kern.log
40 -rw-174064 Nov 16 2016 19:09:34 +00:00 messages
41 -rw-262364 Nov 16 2016 19:09:44 +00:00 messages.1
42 -rw-18434 Nov 16 2016 19:09:54 +00:00 messages.2.gz
43 -rw-25027 Nov 16 2016 19:10:04 +00:00 messages.3.gz
44 -rw-124266 Nov 16 2016 19:10:14 +00:00 udev
45 -rw-292 Nov 16 2016 19:10:24 +00:00 vdscli-acpid.log
46 -rw-909 Nov 16 2016 19:10:34 +00:00 vdscli-eventd.log
47 -rw-467 Nov 16 2016 19:10:44 +00:00 vdscli-vdscli-bde-gos.log
48 -rw-479 Nov 16 2016 19:10:54 +00:00 vdscli-vdscli-bde-ir800.log
49 -rw-81 Nov 16 2016 19:11:04 +00:00 vdscli-wiredd.log
50 -rw-140382 Nov 16 2016 19:11:14 +00:00 vdscli-wirelessd.log
51 -rw-1192 Nov 16 2016 19:11:24 +00:00 vdscli.log
994918400 bytes total (34735718
What to do next
Other command output that will be helpful to collect for your business unit contact:
# Show platform hypervisor
# Show platform led
# Show tech
# Show cellular 0/0 all
# Show controller 0/0
# Show interface cellular 0/0
# Show ip interface brief
# Show running-config
This chapter provides background on the Internal WLAN Access Point which runs on-board the IR829 router.
The AP803 runs its own IOS software independently from the IR829 IOS, and requires configuring. The
AP803 works as a standalone access point or with a wireless controller.
This Embedded AP supports a default Autonomous mode and a Unified mode. Both the Autonomous and
Unified images are pre-loaded from Cisco on the access point’s flash memory.
The image name describes what each image is for. w7 is Autonomous Image, while w8 is the Unified mode
This interface is internally connected to the IR829 WLAN-GigabitEthernet0 switch-port.
The Access Point GE0 interface is always up. Neither the Access Point GE0 or the IR829
WLAN-GigabitEthernet0 switch-port interfaces can be shutdown. This is in order to prevent traffic disruption
to the internal Access Point.
Note
Access Point GE0 can NOT be configured by network operators. It always operates in 1000M/full-duplex
mode.
AP803 IOS – BVI 1 (in autonomous mode only)
This is the management interface which bridges the Dot11 radio0, Dot11 radio1 and GE0 interfaces.
IR829 IOS WLAN-GigabitEthernet0
This interface connects internally to the Access Point’s GE0 interface and carries all data packets between
the Access Point and the Router.
IR829 IOS – AP803 Console Access
The default configuration for WLAN-GigabitEthernet0 is in switch-port access mode, with native VLAN 1
(Layer-3 interface). You can configure the switch-port in trunk mode as well.
IR 829 IOS wlan-ap 0
This is the interface representing the embedded Access Point on the Router. It requires an IP address and is
used only to reverse telnet into the Access Point console. This interface does not carry any data packets between
the Router and the Access Point.
IR829 IOS – AP803 Console Access
Connecting to the console of the AP803 allows for monitoring Warning and informational messages. You
can configure wlan-ap 0 so that a dedicated IP address is not needed, and wlan-ap 0 can share its IP address
with another interface. Use the following steps:
Configuring
# conf term
IR829(config)#inter wlan-ap 0
The wlan-ap 0 interface is used for managing the embedded AP.
Please use the "service-module wlan-ap 0 session" command to console into the embedded AP
IR829(config-if)# ip address 10.1.1.1 255.255.255.255
IR829#service-module wlan-ap 0 session
Trying 10.1.1.1, 2004 ... Open
User Access Verification
Username: cisco
Password: <password>
ap>ena
Password: <password>
ap#
IR829#service-module wlan-ap 0 session
Trying 10.1.1.1, 2004 ... Open
User Access Verification
Username: cisco
Password: <password>
ap>ena
Password: <password>
ap#
Monitoring
IR829#service-module wlan-ap 0 status
Service Module is Cisco wlan-ap0
Service Module supports session via TTY line 4
Service Module is in Steady state
Service Module reset on error is disabled
Service Module heartbeat-reset is enabled
Getting status from the Service Module, please wait..
The AP803 Access Point is managed by the IR829 Service Module Monitor. It communicates with the AP803
through layer-2 RBCP (Router Blade Configuration Protocol). The AP803 is managed through the
service-module wlan-ap 0 CLI.
IR829#service-module wlan-ap 0 ?
heartbeat-reset Enable/disable Heartbeat failure to reset Service Module
reloadReload service module
resetHardware reset of Service Module
The AP803 image is not included in the IR829 IOS bundle. The AP803 image must be installed separately
after obtaining the new AP803 release from Cisco.com.
1. Log onto the AP803.
2. Install the new AP803 image using the archive command. Alternately, this can be accomplished through
the embedded web interface.
• archive download-sw ! Software download.
• /overwrite ! Overwrites the software image in Flash with the downloaded image.
• /reload ! Reloads the system after downloading the image unless the configuration has been changed
and not saved.
This chapter describes the details of configuring virtual-LPWA (VLPWA) interface on the IR800 series for
the configuration of the Cisco LoRaWAN Gateway.
This chapter contains the following sections:
• Configuring Virtual-LPWA Interface on the IR800 Series, on page 77
• Configuring SNMP TRAP for Modem Notifications, on page 82
• Configuring VLPWA Interface and Associated Cisco LoRaWAN Gateway, on page 83
• Configuring Cisco LoRaWAN Gateway Password, on page 85
• Configuring Console Access, on page 85
• Configuring Clock for the Cisco LoRaWAN Gateway, on page 86
• Configuring Cisco LoRaWAN Gateway Timezone, on page 87
• Configuring IPSec on the Cisco LoRaWAN Gateway, on page 88
• Configuring SCEP on the Cisco LoRaWAN Gateway, on page 88
• Configuring Security Protection, on page 90
• Managing the Cisco LoRaWAN Gateway, on page 91
• Monitoring the LoRaWAN Gateway, on page 95
• Debugging the LoRaWAN Gateway, on page 99
Configuring Virtual-LPWA Interface on the IR800 Series
The Cisco LoRaWAN Gateway is connected to IR800 series via an Ethernet cable with PoE+ to work as a
LoRaWAN gateway. By creating a VLPWA interface on the IR800 series, you can:
• Manage hardware and software of the Cisco LoRaWAN Gateway.
• Send and receive VLPWA protocol modem message to monitor the status of the Cisco LoRaWAN
Gateway.
• Send SNMP traps to the IoT Field Network Director (IoT FND).
Note
Cisco IOS Release 15.6(3)M or later is required for the IR800 series to manage the Cisco LoRaWAN Gateway.
Configuring Ethernet Interface and Creating VLPWA Interface
Note
You need to install the Actility Thingpark LRR software as the LoRa forwarder firmware, which is loaded
through the Cisco IOS software, for the Cisco LoRaWAN Gateway to work.
You can find other documentation for the Cisco LoRaWAN Gateway at:
This chapter provides information of configuring virtual interface mode (virtual-lpwa) of the LoRaWAN
gateway. For detailed information about standalone mode configuration, see Cisco Wireless Gateway for
LoRaWAN Software Configuration Guide.
Configuring Ethernet Interface and Creating VLPWA Interface
When you configure IP address for the Ethernet interface or Vlan interface, the IP address allocated must be
aligned with the prefix configured for the DHCP pool allocated to the LoRaWAN interface.
The Cisco LoRaWAN Gateway communicates through IOS, therefore a private IPv4 address is assigned with
NAT being configured.
Configuring Virtual-LPWA
Configuring IR809 for One Cisco LoRaWAN Gateway
Beginning in privileged EXEC mode, follow these steps to configure the Ethernet interface on IR809, and
create the VLPWA interface for one Cisco LoRaWAN Gateway.
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
ip nat inside
ip virtual-reassembly in
PurposeCommand or Action
Enters global configuration mode.configure terminal
Configures the Gigabit Ethernet (GE) port.interface gigabitEthernet ID
Configures the GE interface IP address.ip address address mask
Note
The IP address should be the default
router address in its associated
DHCP pool.
Identifies the interface as the NAT inside
interface.
Enables virtual fragment reassembly (VFR) on
the interface.
Configuring IR809 for Multiple Cisco LoRaWAN Gateways
PurposeCommand or Action
Step 8
Step 9
Configuring IR809 for Multiple Cisco LoRaWAN Gateways
Beginning in privileged EXEC mode, follow these steps to configure the Ethernet interface on IR809 and
create the VLPWA interface for multiple Cisco LoRaWAN Gateways.
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
encapsulation dot1Q vlan-id native
Exits to privileged EXEC mode.end
Saves the configurations.write memory
PurposeCommand or Action
Enters global configuration mode.configure terminal
Configures the Gigabit Ethernet (GE) port.interface gigabitEthernet ID
Enables the interface.no shutdown
Exits to privileged EXEC mode.exit
Configures sub-interface on the GE port.interface gigabitEthernet ID.subID
Configures IEEE802.1Q encapsulation of
traffic on a interface.
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
ip nat inside
ip virtual-reassembly in
Configures the GE interface IP address.ip address address mask
Note
The IP address should be the default
router address in its associated
DHCP pool.
Identifies the interface as the NAT inside
interface.
Enables virtual fragment reassembly (VFR)
on the interface.
Exits to global configuration mode.exit
Creates VLPWA interface.interface Virtual-LPWA vlpwa-id
Note
The value of vlpwa-id should be the
same as the option 43 hex number
which is specified in DHCP pool.
See the DHCP section.
Exits to privileged EXEC mode.end
Saves the configurations.write memory
Each LoRaWAN gateway or virtual-lpwa must be isolated in a dedicated VLAN. If you put it in a VLAN
shared with other devices, it may cause the virtual-lpwa interface not being operational.
Beginning in privileged EXEC mode, follow these steps to configure the Ethernet interface on IR829 and
create the VLPWA interface.
Procedure
PurposeCommand or Action
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
switchport mode access
Enters global configuration mode.configure terminal
Configures the vlan interface.interface vlan vlan-id
Note
The VLAN ID can be different
from the vlpwa ID.
Configures the vlan interface IP address.ip address address mask
Note
IP address should be default router
address in its associated DHCP
pool.
Exits to global configuration mode.exit
Configures the Gigabit Ethernet port.interface gigabitEthernet ID
Sets trunking mode to ACCESS on the given
port.
Sets VLAN when interface is in access mode.switchport access vlan ID
Exits to global configuration mode.exit
Creates VLPWA interface.interface Virtual-LPWA vlpwa-id
Note
The value of vlpwa-id should be the
same as the option 43 hex number
which is specified in DHCP pool.
See the DHCP section.
Step 10
Step 11
Exits to privileged EXEC mode.end
Saves the configurations.write memory
Configuring DHCP Pool for the Cisco LoRaWAN Gateway
The Cisco LoRaWAN Gateway connects to the IR800 series through the Ethernet interface. The communication
between Cisco LoRaWAN Gateway firmware and IOS is conducted over IP. Therefore, an IP address must
be assigned to the Cisco LoRaWAN Gateway through an IOS local DHCP server pool.
If you connect multiple Cisco LoRaWAN Gateways to a single IR800 router, each interface must have its
own DHCP pool.
Configuring DHCP Pool for the Cisco LoRaWAN Gateway
On the IR800 series, beginning in privileged EXEC mode, follow these steps to configure DHCP pool.
Procedure
PurposeCommand or Action
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
ip dhcp pool pool-name
network network-number mask
default-router address
option 43 hex client-ID
Enters global configuration mode.configure terminal
Creates a DHCP server address pool and enters
DHCP pool configuration mode.
Note
If you have changed the parameters
of the DHCP server, you must
perform a refresh using the no
servicedhcpinterface-type numbercommand and service dhcp
interface-type number command.
Specifies the subnet network number and mask
of the DHCP address pool. Make sure to allow
only one dhcp address releasable to modem.
Specifies the IP address of the default router
for a DHCP client. The default router address
will be assigned to the associated VLAN
interface afterwards.
Enables vendor specific option 43 and assign
the associated Cisco LoRaWAN Gateway
client ID number as the hex value.
Defines DNS services.dns-server address
Step 7
Step 8
ip dhcp excluded-address address
Exits to global configuration mode.exit
Masks all redundant addresses including the
default router in DHCP pool.
Step 9
Step 10
Exits to privileged EXEC mode.end
Saves the configurations.write memory
Example
The following is an example of configuring DHCP pool on IR809:
On the IR800 series, beginning in privileged EXEC mode, follow these steps to enable SNMP TRAP
notifications for virtual-lpwa interface and its associated Cisco LoRaWAN Gateway.
Procedure
PurposeCommand or Action
Step 1
Step 2
snmp-server enable traps vlpwa
Enters global configuration mode.configure terminal
Enables virtual LPWA traps to monitor modem
status changing.
{ 1, 3, 6, 1, 4, 1, 9, 9, 830, 0, 12 };modem storage usage returns to normal
When the SNMP linkUp and linkDown traps are enabled, the modem device status could be monitored. The
modem device status notifications are listed below:
interface gigabitEthernet_ID linkUp/linkDownmodem power on/off
Configuring VLPWA Interface and Associated Cisco LoRaWAN
Gateway
On the IR800 series, beginning in privileged EXEC mode, follow these steps to configure one or multiple
VLPWA interfaces and associated Cisco LoRaWAN Gateways.
The following set-up refers to the Thingpark LoRa Forwarder software. When configuring the virtual-lpwa
interface with other 3rd party network server, refer to the 3rd party vendor documentation.
Specifies the timezone variables as the
configuration for the LoRaWAN modem. The
value is based on the IANA Timezone database.
Please check the /usr/share/zoneinfo/ folder in
your PC host.
timezone —Name of time zone, for example,
Asia/Shanghai.
Example:
lpwa modem timezone Asia/Shanghai
Exits to privileged EXEC mode.end
Saves the configurations.write memory
87
Page 100
Configuring IPSec on the Cisco LoRaWAN Gateway
Configuring IPSec on the Cisco LoRaWAN Gateway
In virtual-lpwa mode, IPsec is set to protect the communications between the LoRaWAN gateway and the
IR800 router.
On the IR800 series, beginning in privileged EXEC mode, follow these steps to configure IPSec for the Cisco
LoRaWAN Gateway.
Procedure
PurposeCommand or Action
Configuring Virtual-LPWA
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
What to do next
Note
Only PSK (IKEv1) and RSA (IKEv2) are supported.
interface Virtual-LPWA vlpwa-id
lpwa modem isakmp <xauth-user>
<xauth-pw> <peer-ip> group <name>
<psk-key> <lifetime>
Enters global configuration mode.configure terminal
Enters the vlpwa interface which is to be
configured.
Enables IPSec. By default, IPSec is disabled.lpwa modem ipsec enable
Specifies the XAUTH credential’s username,
password, and the IP address of the right
participant’s interface. Matches this information
to the IKEID group with group name,
pre-shared key for remote peer, and lifetime in
seconds.
Exits to privileged EXEC mode.end
Saves the configurations.write memory
Configuring SCEP on the Cisco LoRaWAN Gateway
On the IR800 series, beginning in privileged EXEC mode, use these commands to configure Simple Certificate
Enrollment Protocol (SCEP) on the Cisco LoRaWAN Gateway.