From: Brian McGahan (bmcgahan@internetworkexpert.com)
Date: Sat Oct 07 2006 - 12:45:04 ART
When you apply the process at the interface level it
automatically creates it in global config. You can create it globally
first but it's not required.
For the link-local addresses you can either have them
automatically assigned via an EUI-64 based host address or you can
statically configure it with the "ipv6 address fe80... link-local"
command. The advantage of configuring it statically is that with
multipoint NBMA interfaces you'll always know what remote link-local
address you need a static resolution statement for. Without this static
resolution you cannot perform route recursion on dynamically learned
IPv6 prefixes over the NBMA link.
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
> forwardtruth@yahoo.com
> Sent: Friday, October 06, 2006 11:52 PM
> To: ccielab@groupstudy.com
> Subject: IPv6 router rip global enabling and per interface base
>
> After enabling : "ipv6 router rip RIPng" globally , we must enable it
on
> individual router interfaces,,,Am I right ?
>
>
> First:
> In Volume1 Lab 7 Task 7.2
> Did he miss the global configuration (ipv6 router rip RIPng) in
purpose
> ?or a type ?
>
>
>
> Second :
> In Volume1 Lab 6 and 7 Task 7.2
> From where did he get the value for link-local address (FE80)? Did he
> assume values for them ?
>
> Regards
>
>
This archive was generated by hypermail 2.1.4 : Wed Nov 01 2006 - 07:29:04 ART