CSR1000v does not start up with start-up configuration

Moderator: mike

Post Reply
mathewfer
Posts: 82
Joined: Wed May 10, 2017 12:11 pm
Contact:

CSR1000v does not start up with start-up configuration

Post by mathewfer » Mon Oct 16, 2017 3:59 am

Hi Team,

I am running about 12 CSR1000v and all are working well, except for these CSRs boot up empty configuration (prompt "router>"). I was using this EVE/UNL for few years and this is the first time I noticed LAB CSRs are blank after sevrer shutdown and power up.

I have set all the CSRs to load from exported start up configs and some CSRs does - no common pattern. Also server is not loaded - CPU at 60% and memory at 70%. Also UKSM is off.

Any thing to check on my setting?

Mathew

Uldis (UD)
Posts: 5177
Joined: Wed Mar 15, 2017 4:44 pm
Location: London
Contact:

Re: CSR1000v does not start up with start-up configuration

Post by Uldis (UD) » Mon Oct 16, 2017 8:42 am

I think you can visit our live helpdesk to explore your problem deeper..

http://www.eve-ng.net/index.php/live-helpdesk

mathewfer
Posts: 82
Joined: Wed May 10, 2017 12:11 pm
Contact:

Re: CSR1000v does not start up with start-up configuration

Post by mathewfer » Tue Oct 24, 2017 11:21 pm

Hi,

Thanks. I noticed when I run all the routers at the same time (start all), causes this issue but when I start one at a time with about 5-10min interval, all starts well with full configurations.

It could be that my server is loaded or default start interval need to more - not sure that is customization or get adjusted dynamically with the severer loading etc.

But I am currently alright with starting in batches.

Mathew

Uldis (UD)
Posts: 5177
Joined: Wed Mar 15, 2017 4:44 pm
Location: London
Contact:

Re: CSR1000v does not start up with start-up configuration

Post by Uldis (UD) » Wed Oct 25, 2017 8:55 am

Matt, it is very sensitive what server you have, as the CSR is super heavy node, mass start can be done on superb servers.

Another thing for config loading, raise the waiting timeout for loading cfg.
Left side bar, more actions/edit lab:
you will find
Config Script Timeout*

raise it to 900

and try now start your lab.

This timer is time in seconds when node is waiting until load config...

UD

Post Reply