[j-nsp] Redundant REs: annoying features et al.

[Gary Tate]

Let me know if you need the NTP services.

By the way I am assuming you are using commit sync?  If you still have 
problems you can send an abridged system config to my personal mail.

Gary

On Tuesday, Oct 28, 2003, at 20:38 US/Pacific, Gary Tate wrote:

> This is the correct configuration.  It is also well to use the backup 
> router statement
>
> set system backup-router <default-gateway-for-fxp0-network>
>
> Bellow lets assume:
> set system backup-router 10.0.0.254
>
> This will allow you to communicate to the secondary RE via the fxp0 if 
> you wish without logging in from other RE
>
> Gary
>
> On Tuesday, Oct 28, 2003, at 15:56 US/Pacific, Dmitri Kalintsev wrote:
>
>> Hi David,
>>
>> groups {
>>     re0 {
>>         system {
>>             host-name router_re0;
>>         }
>>         interfaces {
>>             fxp0 {
>>                 unit 0 {
>>                     family inet {
>>                         address 10.0.0.1/24 {
>> 		    }
>> 		}
>> 	    }
>> 	}
>>     }
>>     re1 {
>>         system {
>>             host-name router_re1;
>>         }
>>         interfaces {
>>             fxp0 {
>>                 unit 0 {
>>                     family inet {
>>                         address 10.0.0.2/24 {
>>                     }
>>                 }
>>             }
>>         }
>>     }
>> }
>>
>> This config, when applied to re0 and re1, will configure their fxp0 
>> with
>> different IP addresses, so they both can talk to the network. Just 
>> note that
>> on an inactive re the routing process isn't active.
>>
>> Hope this is what you're after.
>>
>> SY,
>>
>> -- D.K.
>>
>> On Tue, Oct 28, 2003 at 11:15:06AM +0200, David Martinez CSIC RedIRIS 
>> wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> 	Hello, guys. We have a lot of Junipers deployed, every one of them 
>>> with two
>>> REs.
>>>
>>> 	I found that the backup routing engine is all the time trying to 
>>> connect to
>>> NTP servers, trying to upload its configuration, and so on. Even 
>>> more, when
>>> you switch routing engines, the backup one is out of date, due to 
>>> the fact
>>> that was unable to sync with the NTP server.
>>>
>>> 	Is there any way of solving this issue? Maybe the new statement [ 
>>> system
>>> backup-router ] will be useful? But I cannot manage to understand it 
>>> in order
>>> to set it up for fxp1/2 (internal card, whatever name it has).
>>>
>>> 	Is it possible?
>>>
>>> 	Regards,
>>>
>>>
>>> 		Ender.
>>> - --
>>> You can't even be a vegetable, because even a artichoke has heart.
>>> 		-- Am?lie (Le fabuleux destin d'Am?lie Poulain)
>>> - --
>>> Servicios de red - Network services
>>> Centro de Comunicaciones CSIC/RedIRIS
>>> Spanish Academic Network for Research and Development
>>> Madrid (Spain)
>>> Tlf (+34) 91.585.49.05
>>> -----BEGIN PGP SIGNATURE-----
>>> Version: GnuPG v1.2.3 (GNU/Linux)
>>>
>>> iD8DBQE/njOaWs/EhA1iABsRAvJqAJ9RXmsdLk+uYRtyp00tkBN0h0BhYQCgyTRB
>>> YLsSXucDmNoxMKvZV0DxZeM=
>>> =142S
>>> -----END PGP SIGNATURE-----
>>>
>>>
>>> _______________________________________________
>>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>>> http://puck.nether.net/mailman/listinfo/juniper-nsp
>> ---end quoted text---
>>
>> -- 
>> D.K.
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> http://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>