Release Notes for Cisco IR1101 Industrial Integrated Services Router Release 17.3.2a
Image Information and Supported Platforms
The following release notes support the Cisco IR1101 router. These release notes are updated to describe new features, limitations, troubleshooting, recommended configurations, caveats, and provide information on how to obtain support and documentation.
This publication consists of the following sections:
■ Image Information and Supported Platforms
■ Caveats
The Cisco IR1101 Industrial Integrated Services Router is a next generation modular industrial router which has a base module with additional Pluggable Modules that can be added. The Pluggable Module provides the flexibility of adding different interfaces to the IR1101 platform, for example, a cellular module.
The IR1101 ISR also has an Expansion Module that adds key capabilities such as dual LTE Pluggables, mSATA SSD FRU, SFP, and Digital GPIO connections.
Note: Complete details on the IR1101 and both Expansion Modules can be found in the IR1101 Industrial Integrated Services Router Hardware Installation Guide.
Note : The IR-1100-SP Expansion Module is the same as the IR-1100-SPMI module, without the Digital I/O and mSATA components.
Note : You must have a Cisco.com account to download the software.
Cisco IOS-XE Release 17.3.2a includes the following Cisco images:
■ir1101-universalk9.17.03.02a.SPA.bin
■ir1101-universal9_npe.17.03.02a.SPA.bin
Note : This release introduces a single image for both autonomous and SDWAN.
The latest software downloads for the IR1101 can be found at:
https://software.cisco.com/download/home/286287045
Click on the IR1101 link to take you to the specific software you are looking for.
This release has the following limitations or deviations for expected behavior:
Downgrading from 16.12.1 to 16.11.1 x
Symptoms : If an IR1101 with RJ45 Gig0/0/0 WAN is downgraded from 16.12.1 to 16.11.1 x or earlier, it will cause the Gig0/0/0 to fail to come up because its media-type is set to media-type sfp. The problem occurs because 16.12.1 or later automatically selects the correct media-type of the Gig0/0/0 interface, while 16.11.1x and earlier does not have that capability.
Workaround : Specifically set the correct media-type for the Gig0/0/0 interface (e.g. media-type rj45) prior to any downgrade.
An IR1101 operating in SDWAN Controller-mode must not downgrade to Cisco IOS XE Release 17.1.1. This is not supported for SDWAN. Instead, use Cisco IOS XE Release 16.12.1.
Note: Cisco IOS XE Release 16.12.1 supports separate Autonomous (non-SDWAN) and SDWAN Controller-mode images.
The following documentation is available:
■All of the Cisco IR1101 Industrial Integrated Services Router documentation can be found here:
https://www.cisco.com/c/en/us/support/routers/1100-series-industrial-integrated-services-routers/tsd-products-support-series-home.html
■Cisco SD-WAN Configuration Guides:
https://www.cisco.com/c/en/us/support/routers/sd-wan/products-installation-and-configuration-guides-list.html
Caveats describe unexpected behavior in Cisco IOS releases. Caveats listed as open in a prior release are carried forward to the next release as either open or resolved.
Note : You must have a Cisco.com account to log in and access the Cisco Bug Search Tool. If you do not have one, you can register for an account.
For more information about the Cisco Bug Search Tool, see the Bug Search Tool Help & FAQ.
SL Policy: Purchase information should be protected and shouldn't be able to be erased
Symptom : When performing a write erase, purchase information is lost. When purchase information is lost, the customer might required to report license usage. Customer might see in syslog that reporting is required.
Conditions : This happens when a write erase is used and the product is shipped from Cisco with Purchase Information.
Workaround : Purchase information will be restored once usage reporting is acknowledged. The customer can then use any feature which depends on the purchase information. If the usage is not reported, the customer will not have the purchase information and the router will display syslog messages to report the usage.
Issues with i p tcp adjust-mss command added automatically to cellular interface
Symptom : Issues seen with the new behavior of ip tcp adjust-mss command automatically being configured on the cellular interface based on mtu of provider:
1. If user automatically configures ip tcp adjust-mss on the cellular interface, it will get overwritten on the next interface flap. Need to allow user to specific mss manually if they would like to.
2. If user manually configures mtu on the cellular interface (lower than provider) this needs to be taken into account.
Throughput exceeds the designed default of 250MB
Symptom : Throughput traffic test on the IR1101 exceeds the designed default of 250MB even with the explicit configuration platform hardware throughput level 250MB.
Symptom : Observe the MCU is upgraded however traceback is seen.
boot env var corruption on hard reload
Symptom : Router hard reload can cause boot env var to wipe out completely. NVRAM partition corruption.
Only boot env var are affected due to which router finds itself in ROMMON mode.
IOx latency to show running state
Symptom : The show iox command takes from 5 to 7 minute to show that IOx is in a running state after starting IOx on the IR1101.
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.
Model Driven Telemetry - gRPC Dial-Out: Expands existing Model Driven Telemetry capabilities with the addition of gRPC protocol support and Dial-Out (configured) telemetry subscriptions.
YANG Data Models: For the list of Cisco IOS XE YANG models available navigate to:
https://github.com/YangModels/yang/tree/master/vendor/cisco/xe/
Revision statements embedded in the YANG files indicate if there has been a model revision. The README.md file in the same GitHub location highlights changes that have been made in the release.