From: Brian McGahan (bmcgahan@internetworkexpert.com)
Date: Tue Aug 23 2005 - 18:19:33 GMT-3
f the link is just point-to-point transit you technically don't
need a global unicast address. If you are peering via IPv6 BGP you can
introduce some problems, but there are various workarounds. Using
global unicast address on transit links is more for administrative
purposes than anything else.
HTH,
Brian McGahan, CCIE #8593
bmcgahan@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987 x 705
Outside US: 775-826-4344 x 705
24/7 Support: http://forum.internetworkexpert.com
Live Chat: http://www.internetworkexpert.com/chat/
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> gladston@br.ibm.com
> Sent: Tuesday, August 23, 2005 3:44 PM
> To: ccielab@groupstudy.com
> Subject: ATM IPv6 Mapping
>
> Some books show examples mapping the remote link-local IPv6 and
Site-local
> (or Aggregatable Global) IPv6 address on ATM/Frame-Relay.
>
> Tests shows mapping only the remote link-local address is enough when
IGP
> advertises the IPv6 configured on the remote interface.
>
> Any comments appreciated.
>
> Rack2R11#sh run int ATM1/0.1311
> interface ATM1/0.1311 multipoint
> description PVC
> ip address 148.5.100.11 255.255.255.0
> pvc 0/200
> protocol ip 148.5.100.3 broadcast
> protocol ipv6 FE80:148:100::3 broadcast
> !
> ipv6 address 148:5:100:311::11/64
> ipv6 address FE80:148:100::11 link-local
> ipv6 ospf network point-to-multipoint
> ipv6 ospf 10 area 0
> end
>
>
> Rack2R11#sh ipv6 rou ospf
> O 148:5:100:311::3/128 [110/1]
> via FE80:148:100::3, ATM1/0.1311
>
> Rack2R11#pi 148:5:100:311::3
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 148:5:100:311::3, timeout is 2
seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
>
>
This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:01:20 GMT-3