Symptom: The message, modem is not present, is seen when the modem is plugged in.
Conditions: Module is stressed with power UP/DOWN, dual SIM failovers, and modem power cycles and resets along with traffic.
Workaround: There is no workaround for this issue. Reboot the CGR.
Symptom: Modem crash memdump from the modem is not retrieved.
Conditions: Even when the modem crash tool is enabled, the memdump is not retrieved.
Workaround: There is no workaround for this issue.
Symptom: The AT Command response from the modem is very slow when bidirectional traffic is sent across the cellular interface.
Conditions: Bidirectional traffic is sent across the cellular interface.
Workaround: Stop all traffic and reload the CGR to access the AT commands.
Symptom: The following tracebacks are seen when GSM/CDMA modem crashes:
%SYS-3-BAD_RESET: Questionable reset of process 314 on tty3/1
-Process= "TTY Daemon", ipl= 0, pid= 333
-Traceback= 1845341z 1733927z 1734FA8z 22D2AA0z
Conditions: Occurs when CDMA/GSM modem crashes.
Workaround: Perform module reload by entering the command: hw-module reload slot-number.
Symptom: Fully empty battery displays high charge values.
Conditions: Occurs at high and low temperature conditions, when a battery is completely drained.
Workaround: There is no workaround for this issue.
Symptom: After booting, a cellular interface might not automatically be placed in an admin non-shut state when its 3G module is administratively powered up from a powered-down state.
Conditions: When the 3G module is powered down, its cellular interface will also be put in admin shut state. When the 3G module is powered up again, its 3G interface will be automatically put back in admin no-shut state.
However, if the 3G module is powered-down and the CGR is rebooted, the 3G interface may not be put in admin no-shut state when the 3G module is powered up again. Users may see this error "cellular_error_log: DS instance init issue". When such an error occurs, the cellular interface will not be automatically put in admin no-shut state when the 3G module is powered up.
Workaround: Try to manually bring up the cellular interface by using the no shutdown command
Symptom: Cellular 3G interface is shown in shutdown state even after the module is powered on.
Conditions: CGR (with a 3G module installed) was powered off and reloaded to ensure that the cellular interface was not in an admin down state. After the CGR boots up and the 3G module is powered on, the module remained in an admin down state.
Workaround: Shutdown and no shutdown commands need to be performed on the cellular interface after the CGR boots up.
Symptom: The dot16 interface may be set to admin shut in startup-config under some race conditions.
Conditions: Under some race condition (e.g. a copy run start operation is happening during a module power-cycle due to recovery or wan-mon), the dot16 interface configuration may be set to administrative shutdown. If the CGR is reloaded, this interface may stay in admin shut state
Workaround: Issue no shutdown in the interface configuration mode if the interface stays in the admin shut state after a reload.
Symptom: c3gModemTemperAbateNotif trap generates only after the c3gModemTemperOnsetNotif trap has already been generated once.
Conditions: c3gModemTemperAbateNotif is working like recovery trap rather than a discrete trap.
Workaround: There is no workaround.
Symptom: After an uninstall of Guest OS followed by an install of the same Guest OS package, the install may timeout.
Conditions: After an uninstall of Guest OS followed by an install of the same Guest OS package, the install may timeout.
Workaround: Do not perform an installation of the same Guest OS package after you do an uninstall. Instead, download the Guest OS package again before attempting another install on the Guest OS.
Symptom: The dot16 interface may still be shown in up state even though its module is powered down in battery power mode.
Conditions: If the dot16 module is powered down because it is configured to be automatically powered down when the system runs on battery power, its interface may still be shown in up state.
Workaround: Manually power up and then power down the dot16 module (instead of having its power-down triggered by battery power mode).
Symptom: IOx Client package or GoS applications cannot be downloaded to GoS if SSHv1 is enabled.
Conditions: By default, the GOS image that comes with the bundled image only supports SSHv2, so SSHv2 must be enabled in IOS in order to download any IOx client package or application to the GOS.
Workaround: Enable SSHv2.
Symptom: The system reset-reason may show “Thermal Trip” after a power outage.
Conditions: When a CGR is power-cycled due a power loss event, the system reset-reason may show a false “Thermal Trip” reset instead of “Power-on”. This is because the unstable voltage on the mainboard may trigger a false “Thermal Trip” reset-reason.
Workaround: After the CGR comes back up, issue show environment temperature to check the sensor temperature. If they show normal values, the Thermal Trip reset-reason can be ignored and no further action needs to be taken.
Symptom: The line protocol on the dot16 interface may not go down after restoring the interface to default configuration.
Conditions: Configure the necessary settings for the dot16 interface to come online. Restore the interface to default settings. The dot16 interface line protocol may stay up.
Workaround: Perform a shutdown on the interface.
Symptom: Malloclite memory leak occurs every 15-20 minutes.
Conditions: This issue is reproducible, but not consistently. An example is shown below:
AllocPC Address Size Parent Name
396D354 11EBC210 100 12F462CC (MallocLite)
396D354 13EFD8C4 48 13036424 (MallocLite)
396D354 13EFE484 48 13036424 (MallocLite)
396D354 13EFE504 48 13036424 (MallocLite)
Workaround: There is no workaround. Router reboot does not help.
Symptom: Incorrect timer expiration events might be sent to the WPAN CG-mesh module leading to tracebacks.
Conditions: Incorrect timer expiration events might be sent to the WPAN CG-mesh module leading to tracebacks.
*Feb 6 09:10:55.219 PDT: %SCHED-3-STUCKMTMR: Sleep with expired managed timer BD02F90, time 0x38BFFE (00:00:00 ago). -Process= "cgna main", ipl= 6, pid= 338
-Traceback= 194224Az 32B2623z 32B2B40z 32B1B63z F57485z F57039z F58AA0z F83664z 1889AECz 1888C8Bz 188764Cz FD16DCz FD0D7Fz FD0875z FD2A25z FCFA15z
*Feb 6 10:10:58.991 PDT: %SCHED-3-STUCKMTMR: Sleep with expired managed timer BD02F90, time 0x6FBD68 (00:00:00 ago). -Process= "cgna main", ipl= 6, pid= 338
Workaround: There is no workaround.
Symptom: Connected Grid Endpoints (CGEs) associated with the slave WPAN do not join RPL of the master WPAN in some instances.
Conditions: If a CGR has multiple WPAN/CG-mesh modules with at least one Dual-PHY master-slave pair, then certain following conditions or events on the router might lead to the master-slave relationship not working as expected.
The events after which the Dual-PHY Master-Slave might not work are:
– After a reload of master slot WPAN
– After a reload of slave slot WPAN
– After a reload of CGR
– After an image upgrade of CGR and subsequent mandatory reload
The CG endpoints under the Slave WPAN link-neighbor table may not join the RPL tree under the Master WPAN.
Workaround: To retain or reestablish DualPHY, after any of the above conditions occur, the CGR requires the following two actions:
1. First, reload the slave module(s) by entering:
Router(config)# hw poweroff <slave-slot>
Wait for WPAN down message plus 90 secs, and then enter:
Router(config)# no hw poweroff <slave-slot>
2. Reload the master WPAN module by entering:
Router(config)# hw poweroff <master-slot>
(Wait for WPAN down message plus 90 secs, then enter)
Router(config)# no hw poweroff <master-slot>
3. Check status of the CGR, by entering (for each CGE associated with the slave module):
show wpan <slave-slot>/1 link-neighbor table
show wpan <master-slot>/1 rpl table
When you see the CGEs join the RPL tree, the master-slave relationship is active.
Symptom : Invalid encrypted WiFi password may result in dot11 interface remaining down.
A WiFi SSID is configured and applied to the radio dot11 2/1 interface, but the interface remains down while displaying the following error on console:
*May 21 15:52:42.186 PST: %CGR1K_DOT11-3-RADIO_RESET: DOT11 radio hard reset
*May 21 15:53:55.004 PST: %CGR1K_DOT11-3-RADIO_RESET: DOT11 radio hard reset
*May 21 15:55:07.842 PST: %CGR1K_DOT11-3-RADIO_RESET: DOT11 radio hard reset
Conditions : SSID is configured with an invalid encrypted password - likely due to shorter than eight characters in length or invalid characters.
Workaround : To ensure the encrypted password used is valid:
1. Configure the dot11 SSID with a valid clear, non-encrypted password.
2. Capture the 'encrypted 7' password string (created from a valid clear password in step above) as shown in the CGR config.
3. Use that valid 'encrypted 7' type password in configs.