[j-nsp] Routing Engine for M10i
Anton Delport
adelport at juniper.net
Thu Sep 18 17:31:09 EDT 2008
Hi Luis
This should not be a problem. Mixing different REs as you are doing will
be supported during an upgrade procedure. I would just wait a few
minutes after the RE0 is booted before making the switch.
On 18-9-2008 23:14, lbarrios at NAVEGA.com wrote:
> Hello ..
>
> I have a router m10i with two routing engines.The router Engine in the
> slot 0 is as a Backup . The RE in Slot 1 is the Master.
>
> Routing Engine status:
> Slot 0:
> Current state Backup
> Election priority Master
> Temperature 29 degrees C / 84 degrees F
> CPU temperature 26 degrees C / 78 degrees F
> DRAM 768 MB
> Memory utilization 25 percent
> CPU utilization:
> User 0 percent
> Background 0 percent
> Kernel 1 percent
> Interrupt 0 percent
> Idle 99 percent
> Model RE-5.0
> Serial ID 1000482755
> Start time 2007-10-15 08:47:13 CST
> Uptime 339 days, 5 hours, 43 minutes, 15
> seconds
>
>
> lbarrios at Juniper-re1# run show chassis hardware | match Routing
> Routing Engine 0 REV 09 740-009459 1000482755 RE-5.0
> Routing Engine 1 REV 09 740-009459 1000482737 RE-5.0
>
>
>
> Now i want to change the REs for other routing engine with more capacity
> for Memoria RAM.
>
>
> My new RE is :
>
> Routing Engine 0 REV 06 740-011202 1000687885 RE-850
>
> This RE has 1.5GB of capacity for RAM .
>
> I want to make the next procedure :
> - Remove from the slot 0 the old RE-5.0 ( my backup RE)
> - Insert in the slot 0 the new RE-850
> - make a commit synchronize
> - make a request chassis routing-engine master switch
>
> I hope interrupt the traffic only for a 2 or 3 minutes. ( with the switch
> between the REs)
>
> my question is if you know .. could i have a problem with incompatibility
> with between the REs .. when i execute the commnads .. "commit
> synchronize" or "request chassis routing-engine master switch" ... both
> REs are for M10 i routers . I have the new RE with the same Junos
> version ( JUNOS 8.2R2.4) than the old REs.
>
> thanks so much for your comments.
>
> 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. =
>
--
Anton
More information about the juniper-nsp
mailing list