The running-config always shows the
gyroscope-reading enable setting even if the feature is disabled. The default setting for the gyroscope-reading feature is disabled, and the setting is supposed to be
no gyroscope-reading enable in the running-config.
Issue the EXEC command show platform gyroscope-data to check whether the feature is actually enabled or disabled.
On the 800 series routers, configured with Dialer Watch configurations, if the interface cellular is up and device is reloaded, the dial-out does not happen and IP does not appear on cellular interface.
Perform a shut then noshut on the cellular interface.
On the CGR1K series, SSH enabling/disabling for IOX does not work consistently.
When SSH server is enabled or disabled in GOS VM using the i
ox host exec disablessh/enablessh xxxx command, the operation may randomly fail or succeed.
Repeat the command several times until it succeeds.
On the CGR1K series, an ungraceful IOX shutdown may cause previously running apps to get stuck in deployed or failed state after booting.
If an app is deployed and running and the device is power-cycled or the GOS VM is ungracefully restarted, the app may be stuck in deployed or failed state after booting.
Uninstall the app prior to power-cycling the router or ungracefully restart the GOS VM. Re-install the app after booting.
Cgroups error message may occasionally show up during apps operations, such as install/uninstall.
When an app is installed or uninstalled, this error message may show up in the GOS VM console:
software/apps/work/repo-proc# cgroup: cgcreate (762) created nested cgroup for controller "memory"
which has incomplete hierarchy support. Nested cgroups may change behavior in the future. cgroup: "memory" requires setting
use_hierarchy to 1 on the root.
Bundle install redundant lengthy time-out right after reload.
On the IR800 series, right after router reboot, the IOS-VDS hb failure syslog message comes in quite late. Because of this, if the user erroneously tries a bundle install, the following is observed:
Expected - Bundle install should immediately timeout/fail stating vds not up
Observation - Bundle install continues for next 15 minutes and then times out.
Expected - VDS eventually comes up within a minute or two, and can be reached
Observation - Even though VDS is now accessible, bundle install continues to timeout. So no value add in letting it run.
Ping the IP address 127.1.3.1. Proceed with bundle install only if the ping to VDS succeeds.
On repeated reload, MCU reattempts to upgrade application firmware.
This problem occurs very rarely on the IR800 series. Observed syslog:
%NOTICE: The system booted with MCU in bootloader mode, which triggers the MCU upgrade.For MCU upgrade, MCU must be in bootloader mode. MCU is going to bootloader mode This might cause System reload.
Device eventually comes back up in a couple of reboots.
BVI host list detail only shows IPv6, not IPv4 address.
On the IR800 series, IPv4 address does not show up in host list detail. Functionally no impact to Guest-OS, user can ping, ssh IOx v4 interface. It is just TPM issue.
Reboot router. No functional impact of defect.
SFP-GE-T in IR829 throws traceback as unrecognized device.
Sometimes on system reload it recovers as well.
On the IR800 series, GOS restart times out with multiple applications running.
With the new graceful shutdown of applications implementation, CAF takes longer to shutdown the apps. GOS restart times out.
Wait for 5 minutes. Applications should come up by themselves.
On the CGR1K, firmware upgrade fails with an error code 105. Seen on both the MC7430 and MC7455 modems.
Workaround : Reload the router.
On the CGR1K, Third-party modules may show power sequence error when powering up.
Conditions : Starting with Cisco IOS version 15.6(3)M1b, whenever a third-party module is powered up, the following power sequence error log message may be generated.
CGR1000_JAF1626BLCM(config)#no hw-module poweroff 5
Sep 11 11:50:45.317 PDT: %CGR1K_SYS-3-MODULE_POWER_SEQ: Module power sequence error, slot 5 error 5 data 1101
This is due to an enhancement for power sequence error reporting to ensure that Cisco modules are properly powered up. However, for third-party modules, such power sequence error may be safely ignored as long as the module does not have any temperature sensor.
Workaround : None
Problem Description :
Bundle install failure/timeout, IOx failure
1. ping to VDS fails:
2. bundle install times out
3. iox applications are not accessible anymore
Typically, when the router is left idle for many weeks and months, there is a possibility to observe this when upgrading to the next software image.
Root cause was that dual modem logs in VDS were not rotating and size increased in time. Due to lack of memory, bundle install attempts failed. Reload the router before reattempting bundle install and image upgrade.
Issue is seen in all software images supporting dual modem [15.6(3)M and beyond]
Reload IOS and system will recover.
Problem Description :
On IR829 and IR809 platform, there is a Wpan2 interface shown by default in 15.6(3)M2 and beyond software images.
The show run command will by default show an additional interface, regardless of whether LoRa modem is attached or not.
router#show run int wpan 2
Current configuration : 78 bytes
The following caveats are fixed with this release:
On the IR829, a rare condition occurred where the device may shut down due to the ignition timer turning on.
Symptoms : Happens with MCU Firmware 28, Application 30. show ignition shows timer has started countdown to shut-down. Since it is unpredictable, difficult to monitor at all times.
Workaround : Power device back on. Or upgrade to 15.6(3)M2 with fix as part of MCU Application version 31.
Application Hosting from IOx may not work even if the software is upgraded to the latest working software [15.6(3)M2 and beyond] with the fix. Once the user hits this issue with older versions, following the manual workaround is mandatory.
– No access to local manager
– Cannot access device from fog director
– unable to manually start applications
– CAF does not start
– The product ID value in CAF is 'default', when it should update with the product ID sent by IOS.
4. Login to IOx. The simplest method is to reverse telnet to the g0 interface on an IR809, or the g5 interface on an IR829 using port 2070. For Example:
5. Ensure Line1/4 has '
transport input/output all ' on it.
6. Ensure IPv6 is enabled in the IOx interface.
7. Once logged in, check the following:
The most likely status is that CAF will be stopped.
8. To resolve the problem:
Manually delete 'default'
Manually edit the Product_ID of the device to reflect your product ID
For example: IR829GW-LTE-NA-AK9
9. Restart CAF again.
10. Verify that CAF is up.
CAF should be in a RUNNING state.
Memory leaks on the CGR 1000.
Symptoms : There is no specific condition for the leak to be seen. The leak happens in the background.
Workaround : Resolved