Cisco IOS Release 15.6(2)T - Release Notes for Cisco IR800 Industrial Integrated Services Routers and Cisco 1000 Series Connected Grid Routers

---

---

Ignition Power Management

Ignition Power Management prevents the router from draining the charge of the battery on automotive applications. It also keeps the IR800 up and running while the vehicle is stopped. Therefore, users won't have to wait for routers reload each time the vehicle was stopped. Details about proper wiring to the ignition are found in the Cisco IR829 Industrial Integrated Services Router Hardware Installation Guide.

When the engine is running it generates energy and recharges the battery. When the ignition is turned off, the IR829 can remain operational for a pre-determined period of time. This time period is programmable between 60 to 7200 seconds (2Hours) using the IOS ignition off-timer command.

Features of Ignition Power Management

The system software (IOS) tries to prevent the discharge of the battery with the following:

• Turning the router off if the vehicle has the ignition off for a period of time (programmable).
• Turning the router off if the battery voltage drops to a certain level (programmable).
• Attempts to protect the router by turning the router off if the battery voltage rises above a certain level (fixed amount of time).

The system software (IOS) logs the following events to the system log:

• When the user turns on or off the ignition management feature with CLI
• When the ignition is turned on or off
• When the ignition-off timer expires and the system goes off
• When the user enables or disables the feature through the CLI
• Tentatively logs the under-voltage and over-voltage events

Command Line Interface (CLI)

The Ignition Power Management feature of the IR800 series uses a command line interface.

Configuration CLI

The following commands are used to configure the feature.

Enable or Disable ignition power management:

Ignition off timer value. After the ignition is turned off the router will stay operational for this amount of time, then it shuts down if the ignition is still off:

Over-voltage threshold. If the input voltage drops to levels below this threshold, it will cause the router to shut down

Status CLI

The following command is used to show the status of the feature.

The following is the expected output:

---

Note While the default value for the IR829 is set to 9 volts, 12.2 volts is a much better value to set in order to provide better battery life to the vehicle

Troubleshooting CLI

A set of CLIs are available for debugging purposes.

---

Note To turn the debug off, prepend a no prefix to the CLI command.

The commands are:

Enable debugging error conditions in the ignition management:

Enable debugging operating events in the ignition management

Enable debugging state transitions in the ignition management software:

Enable all debugging conditions at once:

Turn off debugging:

---

Note All debugging commands are cleared through a reboot of the device.

Command Examples

The following examples illustrate the CLI commands and the associated output expected.

Default Values

The following default settings apply to Ignition Power Management:

WAN Monitoring Software (WANMon)

WANMon is a flexible solution to address the WAN link recovery requirements for the following products and interfaces:

• Physical networks: 4G LTE
• Virtual links: Non-crypto map based IPSec tunnels (either legacy or FlexVPN); that is, any IPSec tunnel you configure as an interface.

---

Note Other link types are not supported.

You enable WANMon to monitor your WAN links and initiate link recovery actions on receipt of link failure triggers.

Built-in Recovery Actions

The following are the three levels of built-in recovery processes specific to the link type:

 

Each level has two time-based thresholds based on which built-in recovery actions are taken. The following are the default settings for each level:

• threshold is the wait time in minutes after receipt of a link failure trigger to initiate the recovery action as set in the specified level.
• mintime is the frequency to perform the recovery action if the link remains down.

The built-in values are:

 

---

Note If threshold values are specified as 0, no recovery actions are taken for that level. You can use this to avoid system reload (the built-in Level 2 recovery action) on receipt of a link failure trigger where other WAN links may be operational.

Prerequisites

Ensure that the WANMon module is available. The WANMon module is included in the IOS image as the tm_wanmon.tcl policy file.

Guidelines and Limitations

• WANMon automatically performs IP address checking (no user configuration) as required for the link type:

– For cellular interfaces, WANMon performs IP address checking only for external dialer configurations, not for dial-on-demand configurations.

– For 4G LTE interfaces, WANMon always performs IP address checking.

– For all other interfaces, WANMon never performs IP address checking.

• WANMon indirectly triggers user-specified actions by generating an application event that link resetter applets monitor.
• If your network is live, ensure that you understand the potential impact of any command.

Configuring WANMon

You can enable WANMon on the router and assign WAMMon support to specific interfaces. Optionally, you can override the built-in recovery actions, define custom recovery links, and define an event manager environment policy to set the track object value and disable IP address checking. WANMon is disabled by default.

DETAILED STEPS

 

EXAMPLES

The following examples are Event Manager commands to configure cellular and Ethernet interfaces:

This example sets custom recovery thresholds:

where:

• The Level 0 threshold is set to 20 minutes after the link failure trigger. Level 0 recovery actions are performed for the cellular interface. Repeats indefinitely, no more than every 10 minutes (default).
• Level 1 threshold is set to 90 minutes. Level 1 recovery actions are performed for the cellular interface. Repeats no more frequently than every 75 minutes.
• The Level 2 threshold is set to 600 minutes (10 hours).

The following sets the track-stub-object value to 21:

Verifying WANMon Configuration

Use the following steps to verify your WANMon configuration.

DETAILED STEPS

 

EXAMPLE

WANMon Cellular Interface Configuration Example

Multiple WAN Link Monitoring Example

Related Documentation for WANMon

Configuring WAN Backhaul Redundancy

New Modem Firmware for the CGR 1000 Connected Grid 4G LTE Module running Cisco IOS

New modem firmware, 3.3.4.3, is available for the CGR 1000 Connected Grid 4G LTE Module running Cisco IOS. An upgrade to this firmware is highly recommend. (CSCux47399) For upgrade details, refer to the "Upgrading the Modem Firmware" section in the Cisco Connected Grid 4G LTE Module Installation and Configuration Guide.

New PID for 4G LTE Module

A new PID, CGM-4G-LTE-MNA-AB (All bands), is supported for the Cisco Connected Grid 4G LTE Module for the CGR 1000 Series routers (CGR 1240 and CGR 1120).

New Key Lifetime Value on the WPAN Module

For the CG-mesh WPAN Module for the CGR 1000 Series routers, the key lifetime value has changed for the Interface Configuration command, mesh-security mesh-key interface lifetime value, where value is now: <60-15552000> key lifetime (in seconds). (CSCux96273)

For additional information, see the Cisco Connected Grid WPAN Module for CGR 1000 Series Installation and CG-Mesh Configuration Guide (Cisco IOS).

---

Cisco IOS Release 15.6(2)T

The following sections list caveats for Cisco IOS Release 15.6(2)T:

Open Caveats

• CSCuu49331

LED status report is inconsistent across different commands.

Workaround :

None

• CSCuy79750

After completion of a bundle installation, the Guest OS might not function.

Conditions : Perform a bundle installation with the Guest OS running. After the bundle installation is completed with Guest OS updated, the device needs to be reloaded.

Workaround:

Shutdown the Guest OS before performing a bundle installation.

• CSCut75469

IR829 is not getting GPS data after router bootup

Conditions : After router bootup, sometimes the modem is up but does not get GPS data.

Workaround: Power cycle the modem.

• CSCuu49331

LED status report is inconsistent across different commands

Conditions : PoE LED will go back and forth between yellow and green when there is a PoE device in deny power state. Typing show platform led or show platform led summary will sometimes show yellow, sometimes shows green.

Workaround : Remove the device that has been denied for power allocation

• CSCuu60617

Media-type rs485 is configurable under IR800 serial port 0 interface (async1), however the serial port 1 (async1) interface does not support media-type rs485.

Conditions : When you configure 'media-type rs485" under the async1 interface, the configuration is acceptable.

Workaround : None

• CSCux43383

On the IR829 with a 4GModem, the modem can enter into an unknown state after several modem resets.

Conditions : After 100+ modem resets and attach to BSS, the modem enters into a state where it no longer displays modem info on IOS ( show cellular 0 all). It neither attaches to the BSS or sends IP traffic. Modem seems to respond to the AT commands.

Workaround : None

• CSCux30741

Ignition functions should be disabled when the ignition is disabled.

Conditions : All functions should be disabled (including the under and over voltage protection) when the ignition feature is disabled. Currently under voltage and over voltage protection works even if the ignition management feature is disabled.

Workaround : None

• CSCuy75089

Symptom : On the CG-mesh WPAN Module, you cannot reassign the same power outage server (outage-server {WORD | X:X:X:X: :X}) after you remove it.

Conditions : User tried to reassign a previously removed power outage server configuration to the CG-mesh WPAN module.

Workaround : Assign a different value. Do not reuse a power outer server value.

For additional information, see the Cisco Connected Grid WPAN Module for CGR 1000 Series Installation and CG-Mesh Configuration Guide (Cisco IOS).

• CSCuy83574

Enabling GPS on the CGR1000 3G/4G cellular controller will lock up the console.

Conditions : The regular GPS settings for 3G or 4G cellular controller in the CGR1000 routers must not be used. Cellular modem-based GPS in CGR1000 routers is not supported.

Workaround : Only a CONFIG RESET button recovery may help to restore the CGR1000 back to working condition.

• CSCuy91636

CGR1000 GOS image version is not matching the version in the filename.

Conditions : The version in the CGR1000 GOS file name " cgr1000-ref-gos.img.1.30.gz " is 1.30, but after a bundle install and restarting the IOX VM, the GOS version being retrieved from " sh platform guest-os " is 1.29.

Workaround : None

• CSCuy91651

Inconsistent version numbering for the Ref-GOS image name in the IR800 bundle image.

Conditions : In the IR800 bundle image, the REF GOS image name is: ir800-ref-gos.img.2.3.gz.

Installing the GOS image will produce this version string:

Installation: Cisco-GOS,version-1.0.0.2

Guest OS status:

I nstallation: Cisco-GOS,version-1.0.0.2

The IR800 GOS image is properly versioned in the form: ir800-ioxvm-1.0.0.x

Workaround : None

• CSCuy88101

GOS virtual eth0 fails to get link-local IPv6 and global IPv6 addresses.

Conditions : GOS was configured to obtain global IPv6 address from DHCP server via IOS dhcp relay. At first, the GOS eth0 was able to acquire both link-local IPv6 and global IPv6 addresses. However, after about 5 days, the IPv6 addresses disappeared from the GOS eth0 interface. All attempts to restart (bring down/up) the eth0 interface and/or dhcp client did not help. It simply failed to obtain any link-local and global IPv6 address. While the IPv6 problem persisted for the GOS eth0, it still could obtain DHCP IPv4 address from IOS and communicates with it using IPv4.

Workaround : Only rebooting the GOS would help resolve the IPv6 problem for the GOS eth0 interface.

 

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.

 

© 2016 Cisco Systems, Inc. All rights reserved.

Printed in the USA on recycled paper containing 10% postconsumer waste.