[j-nsp] vrrp on fxp0

[joe lin]

the approach we took is we will try the re0's ip address, if it fails, we will try the re1's ip address in auto-configuration things.

if re1 works, make re1 the primary ip.  if both fails, send alarms

-joe

  ----- Original Message ----- 
  From: Hangu Jeong 
  To: Ben Buxton ; juniper-nsp at puck.nether.net 
  Sent: Wednesday, January 22, 2003 11:37 PM
  Subject: Re: RE: [j-nsp] vrrp on fxp0


  That's true.
  But If we are running scheduled auto-configuration generator on 
  management station ,that is a big issue. 

  Regards,
  Han
  --- Original Message ---
  From: "Ben Buxton" B.Buxton at Planettechnologies.nl
  To: juniper-nsp at puck.nether.net
  Date: Wed, 22 Jan 2003 12:30:09 +0100
  Subject: RE: [j-nsp] vrrp on fxp0

  >
  >In this situation I would say that if you lose a RE, telnetting to a
  >different IP address from the management station is the least of
  >your concerns.
  >
  >BB
  >
  >>
   We use a management network via fxp0 with other devices.
  >>
   I know what you mean, 
  >>
   But we don't want to change the router ip address on 
  >>
   management server  to telnet when RE changed case.
  >>
   If we run vrrp on fxp0 with interface tracking, we can access 
  >>
   always router without ip address change.
  >>
   Of course we have to use predefined group re0 and re1 at that case.
  >>
   
  >>
   Thanks
  >>
   
  >>
   Han
  >>
   
  >>
   -----Original Message-----
  >>
   From: Guy Davies [mailto:Guy.Davies at telindus.co.uk]
  >>
   Sent: Wednesday, January 22, 2003 7:39 PM
  >>
   To: 'Hangu Jeong'; juniper-nsp at puck.nether.net
  >>
   Subject: RE: [j-nsp] vrrp on fxp0
  >>
   
  >>
   
  >>
    
  >>
   -----BEGIN PGP SIGNED MESSAGE-----
  >>
   Hash: SHA1
  >>
   
  >>
   Why would you want to run vrrp on fxp0?  VRRP gives you a degree of
  >>
   resilience to a default route.  Since you can't route traffic 
  >>
   via fxp0,
  >>
   this makes no sense at all.
  >>
   
  >>
   The thing to do for the 2 REs is to have an IP address for 
  >>
   each.  Both REs
  >>
   are live even though one is master and the other slave so you 
  >>
   can log into
  >>
   both of them independently.  If you use the predefined groups 
  >>
   re0 and re1,
  >>
   you can have an identical config on both REs which configures the IP
  >>
   address of fxp0 depending upon which RE slot the config is 
  >>
   being installed
  >>
   on.
  >>
   
  >>
   Regards,
  >>
   
  >>
   Guy
  >>
   
  >>
   >
   -----Original Message-----
  >>
   >
   From: Hangu Jeong [mailto:hgjeong at icraft21.com]
  >>
   >
   Sent: Wednesday, January 22, 2003 10:32 AM
  >>
   >
   To: juniper-nsp at puck.nether.net
  >>
   >
   Subject: [j-nsp] vrrp on fxp0
  >>
   >
   
  >>
   >
   
  >>
   >
   Hi all,
  >>
   >
   
  >>
   >
   We have a M20 with 2 RE. 
  >>
   >
   Anybody tried to run vrrp on fxp0 for router management ?
  >>
   >
   Pls let me know, if anyabody have experience for that. 
  >>
   >
   
  >>
   >
   Thaniks in advance
  >>
   >
   
  >>
   >
   Han
  >>
   >
   
  >>
   >
   
  >>
   >
   
  >>
   >
   
  >>
   >
   _______________________________________________
  >>
   >
   juniper-nsp mailing list juniper-nsp at puck.nether.net
  >>
   >
   http://puck.nether.net/mailman/listinfo/juniper-nsp
  >>
   >
   
  >>
   
  >>
   -----BEGIN PGP SIGNATURE-----
  >>
   Version: PGP 8.0
  >>
   
  >>
   iQA/AwUBPi501Y3dwu/Ss2PCEQKD6QCdEy20aYHGz26fiwu0MI61o+60ccIAnRTn
  >>
   WKY/cYap3Mic5JT1rruXyRaT
  >>
   =OJaz
  >>
   -----END PGP SIGNATURE-----
  >>
   
  >>
   
  >>
   This e-mail is private and may be confidential and is for the intended
  >>
   recipient only.  If misdirected, please notify us by 
  >>
   telephone and confirm
  >>
   that it has been deleted from your system and any copies 
  >>
   destroyed.  If you
  >>
   are not the intended recipient you are strictly prohibited from using,
  >>
   printing, copying, distributing or disseminating this e-mail or any
  >>
   information contained in it.  We use reasonable endeavors to 
  >>
   virus scan all
  >>
   e-mails leaving the Company but no warranty is given that 
  >>
   this e-mail and
  >>
   any attachments are virus free.  You should undertake your own virus
  >>
   checking.  The right to monitor e-mail communications through 
  >>
   our network
  >>
   is reserved by us. 
  >>
   
  >>
   
  >>
   
  >>
   
  >>
   
  >>
   
  >>
   _______________________________________________
  >>
   juniper-nsp mailing list juniper-nsp at puck.nether.net
  >>
   http://puck.nether.net/mailman/listinfo/juniper-nsp
  >>
   
  >
  >_______________________________________________
  >juniper-nsp mailing list juniper-nsp at puck.nether.net
  >http://puck.nether.net/mailman/listinfo/juniper-nsp




------------------------------------------------------------------------------


  _______________________________________________
  juniper-nsp mailing list juniper-nsp at puck.nether.net
  http://puck.nether.net/mailman/listinfo/juniper-nsp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://puck.nether.net/pipermail/juniper-nsp/attachments/20030123/c707b4ab/attachment.htm