Best Practicies Cisco reboot

[douglas767]

Dear friends,

I like to know about Cisco policy to reboot switches and routers every 15 months. Any help or indications of Cisco documentation is welcome.

thanks in advance

Douglas Saraiva

 

[AJ1982]

Not aware of any policy, having had switches/routers with uptimes in excess of 2-3 years.

===

Fatman Superstar (Andrew James)

CCNA

 

[AJ1982]

Less of course youve replaced IOS with a Microsoft product, but then you would be rebooting every 20 seconds, sorry, bad dig

===

Fatman Superstar (Andrew James)

CCNA

 

[jneiberger]

It's possible that you'd need to do this if the IOS you were running had a memory leak or some other related problem. If you see an issue like being low on memory, then reboot. Otherwise, I don't think I'd reboot it just for the fun of it.

 

[burtsbees]

Fatman Superstar, I don't think you should post inaccurate info about Microsoft...you said reboot every 20 seconds. It's more like every 10. Ha ha ha.

Burt

 

[AJ1982]

LOL Sorry yes 10 seconds, being serious now if youve got issues you should look into a an upgrade IOS. Never rebooted a cisco device out of routine at all.

===

Fatman Superstar (Andrew James)

CCNA

 

[douglas767]

Dear friends,

I agree about microsoft, but a sales representative tell me about some policy or best practice impositionig by Cisco. I tell this to my boss and we (he and I) want to get some documentation about this to justify a project to reboot 500 routers and 2400 switches.

Please help me to elucidate this.

Thank so much,

Douglas Saraiva

 

[AJ1982]

Never seen anything to this liking Doug. Cisco stuff is generally very reliable and if you have a specific issue I would look into upgrade of IOS. I would not see a reason to reboot all devices. Except in the event of a datacentre power down.

===

Fatman Superstar (Andrew James)

CCNA

 

[jneiberger]

Douglas,

Don't waste your time with this project. The devices don't need to be rebooted unless they're behaving strangely, in which case you should probably also upgrade to a more stable IOS release.

As far as I know, there is no such thing as a defined policy from Cisco regarding how often you should reboot their products. I've doing this for a while and I know lots of people at Cisco. I've never heard of anything like this.

Regards,
John

 

[BuckWeet]

I wouldn't dog on Microsoft bugs soo much.. Cisco IOS is just as bad!

 

[jneiberger]

Cisco IOS is often fairly buggy, especially early releases within a train. There's a reason you try to avoid ED and LD releases.

 

[kbing]

The cisco tech that I talked to recommended to always use the T train for the IOS releases.

I manage a fairly large site and we never reload routers or switches. I had one instance where a router keep crashing due to a memory leak but we since upgraded the IOS a newer version that fixed the bug.

Maintenance plans for cisco gear generally never require periodic reboots. They just run...........

Microsoft - ya...reboot those ;-)

 

[jneiberger]

I would only recommend the T train if you really need what it offers. The T trains are always ED or LD, and will never become GD. The T trains add new features that don't exist in the mainline release, and they also tend to be much buggier. Those new features are rolled into the next mainline release.

If you want stability, stick to the latest mainline GD release that has the features you require.

 

[kbing]

Hmmm...it's a thought. sometimes a tech can give bad advice however if it's a vendor recommendation...ya know... If anyone else get's a different recommendation direct from Cisco I'd be interested if they give different recommendations.

anyway

 

[jneiberger]

I've been told many times by Cisco not to run T train software unless you need it. Like I said before, there's a reason that it is classified as ED (Early Deployment) or LD (Limited Deployment). "T" train releases are not--and never will be--GD (General Deployment). They are built from the mainline release but they have new technology features added. This gives you more things to play with, but it adds a lot of bugs.

If you don't need the features in a T release then there's no reason to run it. It is always safest to run the latest mainline release that has the features you need, especially once the mainline release has been declared GD.