From: Haas, Brad (bhaas@netinfosys.com)
Date: Mon Mar 12 2007 - 08:50:22 ART
If it's of any consequence... When doing the ASET lab's, the
auto-verify grading tool marked it as wrong if I only put the broadcast
statement on the link-local and not the global. I did verify it as a
working config without the broadcast on my global frame map, but the
grading tool didn't agree.
-Brad
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
ian
Sent: Monday, March 12, 2007 6:45 AM
To: mmmmmmmmmmmm mmmmmmmmmmmm; ccielabdude@gmail.com;
anthony.sequeira@thomson.com
Cc: ccielab@groupstudy.com
Subject: Re: Re: IPv6 Link local addressing and FR maps
I have the same question about IPv6 over FR. When creating FR ipv6
mapping statement, do we need to put the keyword "broadcast" on both
global address mapping and link-local mapping? What the difference
between these two methods?
e.g.
frame-relay map ipv6 2002:1001:1020::6/48 102 broadcast
frame-relay map ipv6 fe80::6 102 broadcast
======= 2007-03-12 21:19:24 What you've mentioned in your
letter#:=======
>Hi, All
>I feel it's best practise to use your own link-local addresses for fram
maps
>for another reason also.
>The link-local addresses that are generated include the mac address on
one
>of your interfaces in the host portion. If you configure a fram map
using
>this your config won't work on other equipment.
>As most labs these days are zipped up and marked by another theatre
your
>configs will most likely be on differnt kit when they are marked.
>
>HTH
>C
>
>
>>From: "Lab Dude" <ccielabdude@gmail.co
>>Reply-To: "Lab Dude" <ccielabdude@gmail.com>
>>To: "anthony.sequeira@thomson.com" <anthony.sequeira@thomson.com>
>>CC: ccielab@groupstudy.com
>>Subject: Re: IPv6 Link local addressing and FR maps
>>Date: Sun, 11 Mar 2007 12:57:36 +0000
>>
>>Hi Anthony
>>Thanks for the response. It makes it clear. Appreciate your help.
>>
>>Some questions for you regarding FR maps:
>>
>>1. According to (4) below, it is my understanding that we need
link-local
>>maps for routing protocols. Would we need to have maps only for remote
>>link-local address on FR? Or would we need to have FR maps for both
>>'link-local' AND 'global' IPv6 addresses in the event that we are
running
>>OSPFover FR? How about a scenario when we have RIP running over FR?
>>
>>Basically, what I am trying to get to is, when do we need global IPv6
>>address FR maps and when do we need link-local FR maps, and when do we
need
>>both link-local and global IPv6 address FR maps.
>>
>>2. Consider a following scenario, where we need to have IPv6 as
follows:
>>
>>BB1-R1-R2-R5
>>
>>R1 and R2 are connected over FR. R1 is point-to-point sub, and R2 is
main
>>interface with FR enabled. R2-R5 is a Ethernet broadcast segment. R1
is
>>connected to BB2 over Ethernet. All these links need to have IPv6
enabled
>>on
>>them. We have been given Global IPv6 addresses for all.
>>
>>a. Do I need to configure both Link local and Global FR maps on R2?
>>
>>b. When I configure FR maps using neighbors IPv6 Global address, OSPF
>>adjacency does come up. So why do I need to have link-local map on R2?
>>
>>Thanks for your help.
>>
>>Lab Dude
>>On 3/10/07, anthony.sequeira@thomson.com
<anthony.sequeira@thomson.com>
>>wrote:
>>
>> > Hey - Lab Dude - great name!
>> >
>> >
>> > 1. When you enable IPv6 on an interface - using the ipv6 enable
command
>> > or the ipv6 address command - you immediately get a link local
address
>> > there! IPv6 requires it and uses it for a variety of purposes. Lots
of
>> > candidates like to manually configure an IPv6 link-local address
>> > replacing the difficult to remember one that gets created by
default.
>> > They do this so it is easier to reference it in later
configurations -
>> > such as frame maps!
>> >
>> > 2. You always have a link local address - it is required. Check
this by
>> > configuring a global address and the run show ipv6 address.
>> >
>> > 3. Routing protocols use the link local address - so your maps need
to
>> > reference the link local address. This is an example of when
students
>> > like to override the link local address with one that is easy to
>> > remember.
>> >
>> > 4. The routing protocols use link local as next hop - this
necessitates
>> > the link local frame maps.
>> >
>> > I think you should start with this set of documents in your studies
-
>> > especially considering you will have access in the lab:
>> >
>> >
http://www.cisco.com/univercd/cc/td/doc/product/software/ios124/124cg/hi
>> > pv6_c/index.htm
>> >
>> > The Brians at InternetworkExpert recommended this book which I
really
>> > enjoyed:
>> >
>> >
http://www.amazon.com/IPv6-Second-Protocol-Practice-Networking/dp/155860
>> >
8109/ref=pd_bbs_sr_8/103-7726709-8680640?ie=UTF8&s=books&qid=1173569643&
>> > sr=8-8
>> >
>> > Also, I assisted NetMasterClass in creating the following product -
it
>> > covers everything you might see in the lab and then some:
>> >
>> >
>> > http://wwww.netmasterclass.com/site/cod_ipv6.php
>> >
>> > -----Original Message-----
>> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
Behalf Of
>> > Lab Dude
>> > Sent: Saturday, March 10, 2007 6:02 PM
>> > To: ccielab@groupstudy.com
>> > Subject: IPv6 Link local addressing and FR maps
>> >
>> > Hi
>> >
>> > I am a bit confused about Link local addressing on IPV6. A couple
of
>> > questions:
>> >
>> > 1. In what scenarios do I need to configure IPv6 Link-local address
on a
>> > particular interface?
>> >
>> > 2. Can I just do with a global address on an interface? Or do I
need to
>> > have
>> > a link-local interface on an interface as well?
>> >
>> > 3. When configuring FR maps, do I need to have link local FR maps
in
>> > addition to Global IPv6 address maps? Or can I just do it with
Global
>> > address map to the spoke/hub?
>> >
>> > 4. What routing protocols (OSPF, RIP) over FR require for me to
>> > configure
>> > Link-local ip addresses/FR maps in addition to Global addresses?
>> >
>> > Your help in this regard or some good documentation that explains
the
>> > differences between Global and Link-local IP addresses and their
usage
>> > for
>> > IPv6 would be highly appreciated.
>> >
>> > Thanks
>> >
>> >
This archive was generated by hypermail 2.1.4 : Sun Apr 01 2007 - 06:35:51 ART