[c-nsp] dumb BGP ipv6 peer group question

[John Brown]

Yup,

Solved the problem.  Thanks Jared and Mack.

Needed a different peer-group for the IPv6 stuff.

I built a new v6 route map to go along with it.

Now I'm off to build happy little IPv6 peering packets.

Mucho thanks

On 12/27/11 5:39 PM, "Mack McBride" <mack.mcbride at viawest.com> wrote:

>You can use the same route-maps provided you don't have any statements
>that reference IP addresses (for obvious reasons).  Most people use IP
>addresses for something or other so they usually aren't compatible.
>
>Mack
>
>-----Original Message-----
>From: cisco-nsp-bounces at puck.nether.net
>[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Jared Mauch
>Sent: Tuesday, December 27, 2011 5:26 PM
>To: John Brown
>Cc: cisco-nsp
>Subject: Re: [c-nsp] dumb BGP ipv6 peer group question
>
>John,
>
>You need a second peer group, e.g.: Any2IX-v6
>
>I seem to recall (memory is fuzzy) you can't re-use the same route-maps
>either, or it may give you a warning..
>
>- Jared
>
>On Dec 27, 2011, at 6:25 PM, John Brown wrote:
>
>> I'm trying to turn up some IPv6 peers.  Most of them are already IPv4
>>peers.
>> 
>> I have a peer group defined in the IPv4 world.
>> 
>> I try to do
>> 
>> cr01.lax(config-router)#address-family ipv6 unicast
>> cr01.lax(config-router-af)#neig 2001:XXX:YY::ZZ remote AAAAA
>> cr01.lax(config-router-af)#neig 2001:XXX:YY::ZZ peer Any2IX-LAX-PEER
>> 
>> And I get the following error
>> 
>> % Members of peer-group must use the same transport
>> 
>> 
>> Here is relevant snips of my BGP config.
>> 
>> 
>> router bgp QQQQQ
>> no bgp enforce-first-as
>> bgp log-neighbor-changes
>> neighbor Any2IX-LAX-PEER peer-group
>> neighbor Any2IX-LAX-PEER description Any2IX-LAX-Base-Config neighbor
>> Any2IX-LAX-PEER update-source g6/2
>> 
>> <  NEIGHBOR STATEMENTS>
>> 
>> address-family ipv4
>> neighbor Any2IX-LAX-PEER activate
>> neighbor Any2IX-LAX-PEER next-hop-self neighbor Any2IX-LAX-PEER
>> send-community both neighbor Any2IX-LAX-PEER soft-reconfiguration
>> inbound neighbor Any2IX-LAX-PEER route-map Any2IX-LAX-ROUTE-MAP in
>> neighbor Any2IX-LAX-PEER maximum-prefix 5000 neighbor Any2IX-LAX-PEER
>> filter-list 100 out
>> 
>> <NEIGHBOR STATEMENTS REF PEER-GROUP>
>> 
>> no auto-summary
>> no synchronization
>> 
>> exit-address-family
>> !
>> address-family ipv6
>> neighbor 2001:XXX:YY::ZZ activate
>> exit-address-family
>> !
>> 
>> 
>> Mucho thanks for the help.
>> 
>> 
>> _______________________________________________
>> cisco-nsp mailing list  cisco-nsp at 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 at puck.nether.net
>https://puck.nether.net/mailman/listinfo/cisco-nsp
>archive at http://puck.nether.net/pipermail/cisco-nsp/