[j-nsp] BGP multihop question

[Derick Winkworth]

Their HSRP address is what I'd assume....

Campbell, Alex wrote:
> Thanks, that's great.  They're not running RIP or OSPF to customers.
>
> The only other thing is that I'm not sure about is whether to point the
> static route to the ISP router's HSRP address or their individual
> addresses?
>
>
> -----Original Message-----
> From: Derick Winkworth [mailto:dwinkworth at att.net] 
> Sent: Friday, 31 October 2008 11:03 PM
> To: Campbell, Alex
> Cc: juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] BGP multihop question
>
> That is the correct approach, unless they are also running RIP or OSPF
> inbetween...
>
> Which I doubt.  But hey... you never know.
>
>
>
> Campbell, Alex wrote:
>   
>> Hi all,
>>
>> We are in the process of bringing up an additional upstream provider
>>     
> to
>   
>> our J4350s. They have given us two switchports on a /29, and told us
>>     
> to
>   
>> establish multihop BGP sessions to their routers (which are on a
>> completely different subnet).  Each switchport will come back to a
>> different J4350 on our end.
>>
>> My problem is that I don't get how our routers will know where to send
>> the BGP packets to the ISPs routers, as they won't have a route for
>>     
> them
>   
>> (we are running defaultless).
>>
>> I think I need to add a static route out to their BGP routers - is
>>     
> this
>   
>> the correct approach here? Or am I missing something?
>>
>> Any help would be most appreciated.
>>
>> Regards,
>>
>> Alex
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>>     
> ------------------------------------------------------------------------
>   
>> No virus found in this incoming message.
>> Checked by AVG - http://www.avg.com 
>> Version: 8.0.175 / Virus Database: 270.8.5/1756 - Release Date:
>>     
> 10/30/2008 7:59 AM
>   
>>   
>> ------------------------------------------------------------------------
>>
>>
>> No virus found in this incoming message.
>> Checked by AVG - http://www.avg.com 
>> Version: 8.0.175 / Virus Database: 270.8.5/1756 - Release Date: 10/30/2008 7:59 AM
>>
>>