Introduction

There is an old, weary joke in IT procurement that “nobody ever got fired for buying Cisco.” But for the network engineers who actually have to deploy, configure, and maintain their sanity around Cisco hardware, the reality is vastly different. Cisco’s software architectures have increasingly become a sprawling labyrinth of legacy command layers, bloated dependencies, and counter-intuitive logic filters. Nowhere is this operational friction more painful than on the WAN edge – specifically when dealing with integrated cellular pluggable modules on the ISR 1100 series platforms (such as the C1127).

The Problem: The Persistent Admin Down Deadlock

The scenario begins simply enough: a remote branch router equipped with a specialised IoT/roaming cellular SIM on interface Cellular0/2/0 shows as down. Upon investigating the status via the command line, the engineer discovers the interface is trapped in an administratively down state.

Standard operating procedure dictates a manual configuration change to force the interface up:

router(config)# interface cellular 0/2/0
router(config-if)# no shutdown

Under any rational operating system, this sequence forces the interface to transition to an active state. Instead, Cisco IOS XE completely ignores the command, refuses to bring the link up, and immediately generates this deceptive syslog error:

%CELLWAN-2-POWER_SAVE_MODE: [Cellular0/2/0]: is in Power save mode. Command ignored.

The Diagnostic Wild Goose Chase

By stating that the module is in an autonomous hardware Power save mode and that configuration commands are being actively ignored, the platform signals that an underlying hardware fault or cellular registration event loop is misbehaving. This kicks off a grueling diagnostic marathon:

• Hardware Resets: Hard-cycling the card on the physical PCIe/USB bus (hw-module subslot 0/2 reload). The module boots clean, reads the hardware telemetry perfectly, but remains deadlocked.
• SIM/Profile Edits: Querying the hardware shows the card successfully reading the SIM card’s internal IMSI and ICCID numbers. Yet, the router claims Profile 1 = INACTIVE. Manually overwriting cellular authentication tables with specific APN strings still yields the exact same “Command ignored” error loop.

The paradox is maddening: The physical router sees the card. The card sees the SIM. The configuration database holds the parameters. Yet, the software interface layer remains completely bricked.

The Discovery: A Hidden Software Lock

The true culprit behind this entire ordeal has absolutely nothing to do with power supplies, bad SIM slots, roaming carrier handshakes, or physical power-saving hardware. Instead, the problem stems from a hidden, counter-intuitive default behavior built into specific Cisco IOS XE firmware images.

On these builds, Cisco dynamically initialises an implicit default boot variable directly under the cellular controller subsystem called lte radio off.

When this hidden flag is active, it creates a severe disconnect within the router’s control plane:

1. The hardware layer is fully powered, allowing the system to query inventory, serials, and SIM information.
2. However, the logical controller plane blocks the RF radio chains from transmitting.
3. When an engineer attempts a no shutdown on the interface, the CLI parser checks the hidden controller flag, violently drops the interface, and throws a completely generic, unrelated POWER_SAVE_MODE error to the console.

Because the command path to reverse this block is tucked into an entirely separate menu layer (controller cellular) from the interface cellular prompt, standard execution paths fail completely.

The Resolution

To break the deadlock and override the fake power-save trap, the solution requires ignoring the interface menu altogether, diving straight into the controller configuration database, and explicitly purging the default hidden variable:

router# configure terminal
router(config)# controller cellular 0/2/0
router(config-controller)# no lte radio off
router(config-controller)# end
router# write memory

The moment the no lte radio off variable is negated, the internal control plane instantly drops the artificial power-save lock. The interface initialises its radio chains, parses the carrier profile, authenticates successfully over the air, and transitions to a fully functional routing state.