Thanks all. Also, since ipv6 seems inevitable, it would seem like a nice way to future proof your network by simply enabling v6 af in the vrf definition (also on me's create vrf using the definition mode for v6), the vpnv6 af under bgp and the v6 af within the vrf specific bgp context....that way, it's done. Saying this since we seem to be looking for ipv6 capabilities to be supported in must things we do these days....so would seem logical to setup router configs to be v6-ready then...
Aaron -----Original Message----- From: Nick Hilliard [mailto:n...@inex.ie] Sent: Tuesday, October 02, 2012 10:00 AM To: Adam Vitkovsky Cc: Aaron; <cisco-nsp@puck.nether.net> Subject: Re: [c-nsp] 6vpe - me3600x In general you don't want to enable multisession bgp unless you know why you need it and you understand all the consequences of doing so. I really wouldn't recommend this as a means of avoiding session flaps due to capabilities renegotiation. Nick Sent from my iWotsit. On 2 Oct 2012, at 15:22, Adam Vitkovsky <adam.vitkov...@swan.sk> wrote: > I thought this is on by default but apparently it's not > > Try > neighbor x.x.x.x transport multi-session > > > adam > -----Original Message----- > From: cisco-nsp-boun...@puck.nether.net > [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Aaron > Sent: Tuesday, October 02, 2012 4:02 PM > To: cisco-nsp@puck.nether.net > Subject: Re: [c-nsp] 6vpe - me3600x > > (resending due to ugly formatting) > > When I enabled vpnv6 on my pre-existing vpnv4 neighbor session I saw > it bounce....Is there any way around this ? ...i'm concerned about > the interruption (for operational environment) on the underlying vpnv4 l3vpn. > Would be only momentary though right?... looks like 10 seconds from > "nbr_reset" to "Up" > > If no way to avoid this, how do y'all do it ? maint window? > > Aaron > > noc-3600(config)#router bgp 64512 > > noc-3600(config-router)#address-family vpnv6 unicast > > % IPv6 routing not enabled > > noc-3600(config)#ipv unicast-routing > > noc-3600(config)#router bgp 64512 > > noc-3600(config-router)#address-family vpnv6 unicast > > noc-3600(config-router-af)#neighbor 10.101.0.254 activate > > *Oct 1 21:01:46: %BGP-5-NBR_RESET: Neighbor 10.101.0.254 reset > (Capabilitychanged) > > *Oct 1 21:01:46: %BGP-5-ADJCHANGE: neighbor 10.101.0.254 Down > Capability changed > > *Oct 1 21:01:46: %BGP_SESSION-5-ADJCHANGE: neighbor 10.101.0.254 > VPNv4 Unicast topology base removed from session Capability changed > > *Oct 1 21:01:47: %BGP-5-NBR_RESET: Neighbor 10.101.0.254 active reset > (Peer closed the session) > > *Oct 1 21:01:47: %BGP_SESSION-5-ADJCHANGE: neighbor 10.101.0.254 > VPNv6 Unicast topology base removed from session Peer closed the > session > > *Oct 1 21:01:47: %BGP_SESSION-5-ADJCHANGE: neighbor 10.101.0.254 > VPNv4 Unicast topology base removed from session Peer closed the > session > > *Oct 1 21:01:56: %BGP-5-ADJCHANGE: neighbor 10.101.0.254 Up > > > > _______________________________________________ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > > _______________________________________________ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
