[alcatel-nsp] 7750 Route Reflector Server Question

[Bryan]

I don't think a route reflector is supposed to change next hop. Are
you seeing otherwise?

On Thu, Mar 3, 2011 at 5:49 PM, Ben Robinson <brobinson at lsnetworks.net> wrote:
> Thanks for the reply. That's not quite what I'm after.
>
> In this case, I want to accomplish both on the same internal sessions to
> reflector clients. I want to set next hop self on routes learned from
> external peers and propagate to internal reflector clients. In the same
> internal sessions, I want leave the original IGP next-hop on internal routes
> reflected to the reflector clients.
>
> Ben Robinson
> Systems Engineer
> LS Networks
>
> -----Original message-----
>
> From: Stefano Gridelli <sgridelli at gmail.com>
> To: Ben Robinson <brobinson at lsnetworks.net>
> Cc: "alcatel-nsp at puck.nether.net" <alcatel-nsp at puck.nether.net>
> Sent: Fri, Mar 4, 2011 01:38:04 GMT+00:00
> Subject: Re: [alcatel-nsp] 7750 Route Reflector Server Question
>
> You can implement this without a policy but by simply creating two bgp
> groups:
> group internal
>    type internal
>    neighbor 10.0.0.1
>    exit
> exit
> group external
>    peer-as 1234;
>    neighbor 4.4.4.1;
>    exit
>     next-hop-self;
> exit
> is this what you are looking for?
> On Thu, Mar 3, 2011 at 7:50 PM, Ben Robinson <brobinson at lsnetworks.net>
> wrote:
>>
>> Greetings,
>>
>>
>>
>> I’m using route reflection on 7750-SR (8.0R7) and want to set next hop
>> self for routes learned from external BGP peers, but not on routes learned
>> from internal BGP peers. The goal is to reflect routes from internal peers,
>> preserving the IGP next hop while setting next hop self on routes from
>> external peers. Perhaps this is the default behavior.
>>
>>
>>
>> I can set all routes to next hop self in the 7750 Peer/Group configuration
>> and with a policy. Since I don’t want all routes advertised internally by
>> the 7750 to have the next hop self set, I’m assuming that it is accomplished
>> in a policy.
>>
>>
>>
>> Firstly, does anyone know if this is the default behavior? Or, if
>> possible, how to accomplish this with SROS policy.
>>
>>
>>
>> The Juniper policy equivalent is:
>>
>>
>>
>> term external {
>>
>>     from route-type external;
>>
>>     then {
>>
>>         next-hop self;
>>
>>         accept;
>>
>>     }
>>
>> }
>>
>> term internal {
>>
>>     from route-type internal;
>>
>>     then accept;
>>
>> }
>>
>>
>>
>> …
>>
>>
>>
>> Policy nhs-ipv6:
>>
>>     Term external:
>>
>>         from route-type external
>>
>>         then nexthop self accept
>>
>>     Term internal:
>>
>>         from route-type internal
>>
>>         then accept
>>
>>
>>
>>
>>
>> Thanks,
>>
>>
>>
>>
>>
>> Ben Robinson
>>
>> Systems Engineer
>>
>> LS Networks, Inc.
>>
>>
>
> _______________________________________________
> alcatel-nsp mailing list
> alcatel-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/alcatel-nsp
>
>