From: Gustavo Novais (gustavo.novais@novabase.pt)
Date: Wed Nov 23 2005 - 08:18:01 GMT-3
Hello Nguyen
You are right. At the moment I wrote the email I was worried about the
fact that the TCP session between neighbours didn't even come up. As you
know the route-map has nothing to do with it.
After I managed to get the peering up, I corrected the route-map and all
worked fine.
Thank you for correcting.
Gustavo Novais
________________________________
From: Nguyen Hong Son [mailto:nguyenhongsontiger@yahoo.com]
Sent: quarta-feira, 23 de Novembro de 2005 2:35
To: Gustavo Novais; West, Karl R (IT); James Matrisciano; GS
Subject: RE: BGP ipv6 peering over frame-relay using link-local
addresses
Hi Gustavo Novais.
You are wrong in configure next-hop ipv6 add.
Let say R1 as example If you use route-map out, you should use next hop
ipv6 add is the site-local of R1 (FEC0::1) if you use route-map in, you
should use next hop ipv6 add is the site-local of R3 (FEC0::3).
You can verify this in the sample Lab 1 of Doit version II preparing for
candidates after 1 Jan 2006 of Netmasterclass.
Best Regards
Gustavo Novais <gustavo.novais@novabase.pt> wrote:
Hi again!
When I do a debug ipv6 packet and deb bgp ipv6
I see that somehow the router R1 is sending packets not to the
Serial0/0 but to the FastEthernet (opposite side of R3).
Does any one know of any restriction on using link local with
fram-relay?
When I used AGUA addresses directly, all went fine.
Rack1R1#deb ipv6 packet
Rack1R1#deb ipv6 packet
IPv6 unicast packet debugging is on
Rack1R1#deb bgp ipv6
BGP debugging is on
Rack1R1#
*Mar 2 05:22:03.966: BGP: FE80::20B:46FF:FE86:3900 open active,
local address FE80::20B:FDFF:FE25:13E0
*Mar 2 05:22:03.966: IPV6: source FE80::20B:FDFF:FE25:13E0
(local)
*Mar 2 05:22:03.966: dest FE80::20B:46FF:FE86:3900
(FastEthernet0/0)
*Mar 2 05:22:03.966: traffic class 192, flow 0x0, len 64+0, prot
6, hops 64, originating
*Mar 2 05:22:03.970: IPV6: source FE80::20B:FDFF:FE25:13E0
(local)
*Mar 2 05:22:03.970: dest FF02::1:FF86:3900 (FastEthernet0/0)
*Mar 2 05:22:03.970: traffic class 224, flow 0x0, len 72+8, prot
58, hops 255, originating
*Mar 2 05:22:03.970: IPv6: Sending on FastEthernet0/0
*Mar 2 05:22:03.970: IPv6: Encapsulation failed
Rack1R1#
*Mar 2 05:22:03.970: IPv6: Resolving next hop
FE80::20B:46FF:FE86:3900 on interface FastEthernet0/0
*Mar 2 05:22:04.971: IPV6: source FE80::20B:FDFF:FE25:13E0
(local)
*Mar 2 05:22:04.971: dest FF02::1:FF86:3900 (FastEthernet0/0)
*Mar 2 05:22:04.971: traffic class 224, flow 0x0, len 72+8, prot
58, hops 255, originating
*Mar 2 05:22:04.971: IPv6: Sending on FastEthernet0/0
Gustavo Novais
-----Original Message-----
From: West, Karl R (IT) [mailto:Karl.West@morganstanley.com]
Sent: terga-feira, 22 de Novembro de 2005 22:47
To: Gustavo Novais; James Matrisciano; GS
Subject: RE: BGP ipv6 peering over frame-relay using link-local
addresses
Can we see the BGP part of your config?
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
Behalf Of
Gustavo Novais
Sent: Tuesday, November 22, 2005 5:31 PM
To: James Matrisciano; GS
Subject: RE: BGP ipv6 peering over frame-relay using link-local
addresses
Yes,
I should have shown sh ipv6 interfaces
R1
Serial0/0 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::20B:FDFF:FE25:13E0
Global unicast address(es):
FEC0::1, subnet is FEC0::/120
R3
Serial0/1 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::20B:46FF:FE86:3900
Global unicast address(es):
FEC0::3, subnet is FEC0::/120
I'm also able to ping one from the other.
Rack1R1#ping FE80::20B:46FF:FE86:3900
Output Interface: Serial0/0
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to FE80::20B:46FF:FE86:3900,
timeout is 2
seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max =
16/16/16 ms
Rack1R1#
Gustavo Novais
-----Original Message-----
From: James Matrisciano [mailto:jmatrisciano@kenttech.com]
Sent: terga-feira, 22 de Novembro de 2005 22:27
To: Gustavo Novais; GS
Subject: RE: BGP ipv6 peering over frame-relay using link-local
addresses
Is the link local address that you are mapping your frame to the
same
link-local address of that of the local interface?
Sh ipv6 interface serial 0/0
Probably so, but just have to ask.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
Behalf Of
Gustavo Novais
Sent: Tuesday, November 22, 2005 5:20 PM
To: GS
Subject: BGP ipv6 peering over frame-relay using link-local
addresses
Hello
There is an example on Ipv6 documentation on doc CD on which
they
exemplify peering between two ipv6 bgp peers using link local
addresses.
I'm trying to do it on top of a frame-relay connection.
Nevertheless,
the peering never comes up. I've checked my FR maps, I've
checked
everything but it still will no work.
I'm asking the group if there's anything wrong I'm doing.
R1 Config
Current configuration : 421 bytes
!
interface Serial0/0
ip address 162.1.13.1 255.255.255.0
ip pim sparse-dense-mode
encapsulation frame-relay
ipv6 address FEC0::1/120
no fair-queue
clock rate 256000
frame-relay traffic-shaping
frame-relay map ipv6 FEC0::3 131
frame-relay map ipv6 FE80::20B:46FF:FE86:3900 131 broadcast
frame-relay map ip 162.1.13.3 131 broadcast
frame-relay interface-dlci 131
class QoS9.1
no frame-relay inverse-arp
end
Rack1R1# sh run | b r b
router bgp 200
no synchronization
bgp router-id 150.1.1.1
bgp log-neighbor-changes
neighbor 162.1.13.3 remote-as 300
neighbor 192.10.1.6 remote-as 200
neighbor 192.10.1.254 remote-as 254
neighbor 192.10.1.254 password CISCO
neighbor FE80::20B:46FF:FE86:3900 remote-as 300
neighbor FE80::20B:46FF:FE86:3900 update-source Serial0/0
no auto-summary
!
address-family ipv6
neighbor FE80::20B:46FF:FE86:3900 activate
neighbor FE80::20B:46FF:FE86:3900 route-map NH out
network 2001:CC1E:0:162::/64
exit-address-family
!
route-map NH permit 10
set ipv6 next-hop FEC0::3
!
R3 Config
Rack1R3#sh run int ser0/1
Building configuration...
Current configuration : 330 bytes
!
interface Serial0/1
ip address 162.1.13.3 255.255.255.0
ip pim sparse-dense-mode
encapsulation frame-relay
ipv6 address FEC0::3/120
clock rate 256000
frame-relay map ipv6 FE80::20B:FDFF:FE25:13E0 311 broadcast
frame-relay map ip 162.1.13.1 311 broadcast
frame-relay map ipv6 FEC0::1 311
no frame-relay inverse-arp
end
Rack1R3#sh run | b r b
router bgp 300
no synchronization
bgp router-id 150.1.3.3
bgp log-neighbor-changes
neighbor 162.1.0.2 remote-as 300
neighbor 162.1.0.4 remote-as 100
neighbor 162.1.0.4 remove-private-AS
neighbor 162.1.13.1 remote-as 200
neighbor 162.1.13.1 remove-private-AS
neighbor 162.1.38.8 remote-as 65002
neighbor FE80::20B:FDFF:FE25:13E0 remote-as 200
neighbor FE80::20B:FDFF:FE25:13E0 update-source Serial0/1
no auto-summary
!
address-family ipv6
neighbor FE80::20B:FDFF:FE25:13E0 activate
neighbor FE80::20B:FDFF:FE25:13E0 route-map NEXTHOP out
network 2001:CC1E:0:3::/64
exit-address-family
!
route-map NEXTHOP permit 10
set ipv6 next-hop FEC0::1
Any help will be appreciated
Gustavo Novais
This archive was generated by hypermail 2.1.4 : Thu Dec 01 2005 - 09:12:07 GMT-3