On Dec 14, 2012, at 2:15 PM, Tauseef Khan <tasneemjan_at_googlemail.com> wrote:
> Thanks All for the explanation. If we have an auto ipv6 address on an
> interface with <ipv6 address autoconfig> I presume we wouldn't need ip6
> enable on that interface.
That is correct. Any <ipv6 address > command implicitly does what ipv6
enable does, which is ensure generation of a link local address for
that interface.
> On 14 December 2012 02:29, Brian McGahan <bmcgahan_at_ine.com> wrote:
>
>> This is a legacy command that's not needed anymore. It used to be that
>> you needed "ipv6 enable" and an ipv6 address in order to run IPv6. Now you
>> only need to say "ipv6 enable" if you want to run IPv6 with only a
>> link-local address, for example for like an EBGP peering.
Not that using link local addresses for ebgp peers is a good thing.
Apart from being a ling & complicated address, it will also
automatically change if you changed the interface hardware, thus
bringing down ur BGP session.
One place where <ipv6 enable> is useful is where in ipv4 u needed <IP
address unnumbered>. It could also be used on the CPEs to provision
the WAN interface.
Regards
Blogs and organic groups at http://www.ccie.net
Received on Sun Dec 16 2012 - 08:41:11 ART
This archive was generated by hypermail 2.2.0 : Tue Jan 01 2013 - 09:36:53 ART