Router Access

[AbeFrohman512]

How can I gain access to my router if the CPU utilization is pegged at 100%?.  The router in question is remote and not accessible locally.

Is there a configuration that would allow me to always be able to access the mngt port?

[Joseph W. Doherty]

Disclaimer

The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.

Liability Disclaimer

In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.

Posting

I believe some routers support configuration commands (e.g. scheduler interval or scheduler allocate) that will provide additional time for management processes, which may allow remote access when CPU is pegged at 100%.

However, this doesn't help if the router is already has a pegged CPU precluding accessing it.  I.e. the commands need to be applied before you're precluded access.

[AbeFrohman512]

Joseph, thank you for your quick response.  I was looking into the scheduler interval cmd, but was left with a few questions concerning it.  This cmd states "high priority operations are allowed to use as much of the CPU as needed".  This statement seemed somewhat vague to me as I don't know what they consider "High Priority Operations" to be.  Within the description of this cmd is also states that the default is already set as the following: "High-priority operations are allowed to use as much of the CPU as needed".  I would interpret this as I should already be running at the highest possible interval (500 milliseconds).

Thoughts?

[Joseph W. Doherty]

Disclaimer

The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.

Liability Disclaimer

In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.

Posting

I agree explanation is vague.  Under scheduler interval we find:

The normal operation of the network server allows the switching operations to use as much of the central processor as is required. If the network is running unusually heavy loads that do not allow the processor the time to handle the routing protocols, give priority to the system process scheduler. High-priority operations are allowed to use as much of the CPU as needed.

In the above, it refers to insufficient time to manage routing protocols.  As those are considered rather important, perhaps the high-priority operation is packet forwarding?  Which, if correct, makes sense.  Cannot say for sure though.  It's something you might experiment with.