Re: BGP peering IPv6 over unnumbered

Thanks Rob!

The IPv6 address on R5 was just a typo in the email (my bad)
2001:2::5:1/128 would be the correct entry,
You're right though. I had the peer address wrong on R1.

There I am jumping to conclusions but once I fixed the logic error, the
peers came right up.

Thanks again!

On 2/12/2011 9:29 PM, Rob Routt wrote:
> Looks like your IPv6 address on R5 is messed up. You are missing a
> colon in the lo0 address and it appears you are trying to peer with
> 2001:1::5:1 instead of 2001:2::5:1. On R1 you have:
>
> neighbor 2001:1::5:1 activate
>
> on R5
> Lo0: 2001:2:5:1/128==missing colon and should be 2001:1::5:1/128 right?
>
> unless those are typos.
>
> -R
>
>
>
> On Sat, 2011-02-12 at 20:20 -0500, Chris Proctor wrote:
>> All,
>>
>> Does anyone know if this is possible?
>>
>> My lab configuration:
>> ----------------------------------
>> R1
>> Lo0: 2001:1::1:1/128
>> S1/0: ipv6 unnumbered lo0
>> frame-relay map ipv6 2001:2::5:1 100
>> ipv6 route 2001:2::5:1 s1/0
>>
>> R5
>> Lo0: 2001:2:5:1/128
>> S1/0: ipv6 unnumbered lo0
>> frame-relay map ipv6 2001:1::1:1 100
>> ipv6 route 2001:1::1:1 s 1/0
>>
>> R1: BGP config
>> router bgp 100
>> bgp router-id 192.0.0.1
>> no bgp default ipv4-unicast
>> bgp log-neighbor-changes
>> neighbor as200 peer-group
>> neighbor as200 remote-as 200
>> neighbor 2001:1::5:1 peer-group as200
>> !
>> address-family ipv6
>> neighbor as200 send-community both
>> neighbor as200 soft-reconfiguration inbound
>> neighbor 2001:1::5:1 activate
>> exit-address-family
>>
>> R5: BGP config
>> router bgp 200
>> bgp router-id 192.0.0.5
>> no bgp default ipv4-unicast
>> bgp log-neighbor-changes
>> neighbor as100 peer-group
>> neighbor as100 remote-as 100
>> neighbor 2001:1::1:1 peer-group as100
>> !
>> address-family ipv6
>> neighbor as100 send-community both
>> neighbor as100 soft-reconfiguration inbound
>> neighbor 2001:1::1:1 activate
>> exit-address-family
>> ---------------------
>> Verification:
>> ---------------------
>> Ping works:
>> Ping from R5 Loop to R1 Loop
>> R5#ping 2001:1::1:1 so lo0
>>
>>
>> Type escape sequence to abort.
>> Sending 5, 100-byte ICMP Echos to 2001:1::1:1, timeout is 2 seconds:
>> Packet sent with a source address of 2001:2::5:1
>> !!!!!
>> Success rate is 100 percent (5/5), round-trip min/avg/max = 24/39/72 ms
>>
>> Telnet works:
>> R5#telnet 2001:1::1:1 /so lo0
>> Trying 2001:1::1:1 ... Open
>>
>>
>> Password required, but none set
>>
>> [Connection to 2001:1::1:1 closed by foreign host]
>>
>> Error messages indicate peer not listenign:
>> *Feb 12 20:14:46.363: BGP: 2001:1::1:1 open active, local address
>> 2001:2::5:1
>> *Feb 12 20:14:46.443: BGP: 2001:1::1:1 read request no-op
>> *Feb 12 20:14:46.447: BGP: 2001:1::1:1 open failed: Connection refused
>> by remote host, open active delayed 17180ms (35000ms max, 60% jitter)
>>
>> BGP not listening:
>> telnet 2001:1::1:1 bgp /so lo0
>> Trying 2001:1::1:1, 179 ...
>> % Connection refused by remote host
>>
>> R1 says it is listening (and even has an existing BGP peering to another
>> peer):
>> R1# show control-plane host open-ports
>> Active internet connections (servers and established)
>> Prot Local Address Foreign
>> Address Service State
>> tcp *:23
>> *:0 Telnet LISTEN
>> tcp *:56860 2001:1::1:1:179
>> IOS host service ESTABLIS
>> tcp *:179
>> *:0 BGP LISTEN
>> tcp *:179
>> *:0 BGP LISTEN
>>
>> --------------
>>
>> I've tried ebgp multi-hop and update-source but I can't think of any way
>> around the not listening part.
>>
>
>
> --
> This message was scanned by ESVA and is believed to be clean.
> Click here to report this message as spam.
> <https://mail-relay.cwproctor.net/cgi-bin/learn-msg.cgi?id=F0E1928635.A16FA>

-- 
Chris Proctor
--
This message was scanned by ESVA and is believed to be clean.
Blogs and organic groups at http://www.ccie.net