I've relegated it to a maintenance window. On 2012-10-02, at 9:53 AM, "Aaron" <[email protected]> wrote:
> 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 (Capability > changed) > *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 [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
