[f-nsp] What is the prefered way to add a vlan to a topo-group

[Bjørn Skovlund Rydén]

Hi all,

If you make a peer-group, you can set everything up, and then add the neighbor IP to the peer-group when all is set up.

router bgp
 neighbor foobar peer-group
 neighbor foobar remote-as 39554
 neighbor foobar route-map in foo-in
 neighbor foobar route-map out foo-out

 neighbor 12.34.56.78 peer-group foobar
exit

That should work, as far as I remember.

Cheers, Bjørn

On 1/3/08 3:01 PM, "Peter Olsen" <Peter.Olsen at globalconnect.dk> wrote:



Hi Gunther,

Yes, it have been reported long time ago. Foundry do not consider it as a bug as the code is doing was is expected from it... so, it is a feature request

br,
Peter

-----Original Message-----
From: Gunther Stammwitz [mailto:gstammw at gmx.net]
Sent: 3. januar 2008 14:58
To: Peter Olsen
Cc: foundry-nsp at puck.nether.net; goverton at nwi.net
Subject: AW: [f-nsp] What is the prefered way to add a vlan to a topo-group

Hello Peter,

did you already report this bug / feature request to foundry?

This is as annoying as the problem with new bgp neighbors:
After configuring a new bgp neighbor with "nei 1.2.3.4 remote-as 123" the mlx automatically starts to bringt the session up which is a problem because you don't have a chance to configure route-maps first.
Cisco is expecting the user to use the command "nei 1.2.3.4 activate" or "no nei
1.2.3.4 shut" once so that the router knows that the configuration has been completed.

I hope that foundry is going to implement this feature soon...

Regards,
Gunther



> -----Ursprüngliche Nachricht-----
> Von: foundry-nsp-bounces at puck.nether.net
> [mailto:foundry-nsp-bounces at puck.nether.net] Im Auftrag von Peter
> Olsen
> Gesendet: Donnerstag, 3. Januar 2008 08:15
> An: goverton at nwi.net; foundry-nsp at puck.nether.net
> Betreff: Re: [f-nsp] What is the prefered way to add a vlan to a
> topo-group
[...]
> If thats the case there is only one way to prevent a loop and that is
> to take a physical port down.
> To my opinion this is a bug, e.g. if you strictly follow the manual
> you will create a loop unless you follow the manual recommandation
> about taking a physical port down.
>


_______________________________________________
foundry-nsp mailing list
foundry-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20080103/1807b10c/attachment.html>