[j-nsp] Software Upgrade

[Harry Reynolds]

It sounds like the pfe is rebooting at re switch, which should not happen ideally. Do you:

1. Have gres configured under chassis?
2. Have the same JUNOS software version on both the master and BU REs?

For minimal disruption you also want graceful-restart set under routing-options; set this on the local and on any neighboring routers.


[edit]
regress at foo# show routing-options 
graceful-restart;

[edit]
regress at foo# show chassis                            
redundancy {
    graceful-switchover;
}



Regards




> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net 
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of 
> lbarrios at NAVEGA.com
> Sent: Tuesday, September 18, 2007 2:14 PM
> To: juniper-nsp at puck.nether.net
> Subject: [j-nsp] Software Upgrade
> 
> Hello guys ..
> i have m10i routers, but now i need to upgrade from Rel 7.6 
> to 8.X.   And 
> i had red about the softwre-upgrade procedure. In my routers 
> i have 2 RE, 
> one working as Master and the other as Backup RE.   So i  
> don´t want to 
> interrupt the traffic so  i was thinking switch from master 
> RE to backup 
> RE and then upgrade the Master RE.   I think , i have good redundancy 
> configuration in my router but when i use the command 
> 
> request chassis routing-engine master switch
> 
> for change from Master RE to Backup RE  i have traffic 
> interrupt during 5 min aprox.  So i don´t now if  it´s normal 
> ,  but i hope interrupt traffic for 20-30 seconds.
> so 5 minutes is like  rebooting the RE so ..   I need to 
> upgrade 5 routers 
> more so  , i would like to know if i can improve the time of 
> traffic interrupt.
> 
> thanks ..
> luis 
> 
> 
> 
> Este correo electrónico puede contener información 
> confidencial y protegida legalmente bajo secreto profesional. 
> La información está dirigida solamente a la persona o entidad 
> indicada como destinatario y su acceso por cualquier otra 
> persona no está autorizado. Si usted recibió este mensaje 
> electrónico por error, infórmeselo al remitente y bórrelo. 
> Aclaramos que los conceptos y opiniones comprendidos en este 
> correo electrónico, deben atribuirse exclusivamente a su 
> autor y no deben entenderse como necesariamente coincidentes 
> con las de NAVEGA.COM, S.A. y en consecuencia, absolutamente 
> ajenos a la responsabilidad de sus directores y ejecutivos, 
> en tanto no hayan participado de su confesión y/o emisión y 
> quede esta participación expresamente consignada en el mensaje. 
> La divulgación pública de este correo electrónico, como así 
> su copia, reproducción total o parcial queda prohibida, dando 
> lugar en caso de inobservancia de esta todas las acciones 
> legales que pudiesen corresponder. Muchas Gracias.
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net 
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>