This post was originally published on ZPE Systems
Image: Traditional ISP management access is cut off when the main network goes down, forcing technicians to go on site.
Most ISP devices are managed over the same network they help provide. Because there’s no independent access path (like dedicated out-of-band management), when the network fails, so does access to the device itself. Recovery is only possible by restoring the very network that’s broken, and since the underlying infrastructure can’t be accessed remotely, someone has to physically connect to the devices that are causing issues.
Watch our quick presentation from Cisco Live 2025 for a closer look.
Limited or Missing Serial Console Access
Many failure states can only be resolved via the console:
Bootloader recovery Rollback after a failed OS upgrade Network lockouts caused by ACL or routing errors
Again, traditional approaches leave serial access dependent on the production network. When the network goes down, the only way to access the console is by physically connecting.
Here’s how one of ZPE’s IT & System Administrators addressed this exact scenario, but used out-of-band to recover remotely instead of going on site.
No Remote Power Control
When devices freeze or become unresponsive, a power cycle typically fixes the problem.
— Read the rest of this post, which was originally published on ZPE Systems.
