From: Scott Morris (smorris@internetworkexpert.com)
Date: Fri Sep 19 2008 - 13:08:42 ART
That would be correct. While I'd hope there wouldn't randomly be a MAC
change, I see your point during a regrade situation!
I would believe (hope?) that the proctors are aware of things like that and
can figure out that portion of failure. :) But on our own racks as we move
along, speed is important!
Scott
_____
From: Ed Man [mailto:networkexpert08@gmail.com]
Sent: Friday, September 19, 2008 9:36 AM
To: swm@emanon.com
Cc: Yasmin Lara; Roger RPF; Ali Mousawi; GS
Subject: Re: IPv6
Thanks Scott.
I do really agree with you that we don't memorize MAC address, and also the
router itself doesn't.
Does it mean if the router itself has its MAC address changed, hence the
link-local, then the "frame map ipv6" statement might not be still valid?
On Fri, Sep 19, 2008 at 9:28 PM, Scott Morris <swm@emanon.com> wrote:
Personally, I would recommend it wherever possible. It saves you the step
of "show ipv6 interface" to look at the address, and typing or cut/paste
ugly addresses. Worse, when looking at routing tables, nothing makes sense
because we typically don't memorize MACs.
Just my two cents. But I'd define them wherever not otherwise prohibited!
Example "ipv6 address fe80::6 link-local" is going to be R6 on every
interface. East to remember, easy to visualize!
Scott Morris, CCIE4 #4713, JNCIE-M #153, JNCIS-ER, CISSP, et al.
CCSI/JNCI-M/JNCI-ER
Senior CCIE Instructor
smorris@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987
Outside US: 775-826-4344
Knowledge is power.
Power corrupts.
Study hard and be Eeeeviiiil......
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Ed
Man
Sent: Friday, September 19, 2008 9:21 AM
To: Yasmin Lara; Roger RPF; Ali Mousawi
Cc: GS
Subject: Re: IPv6
Thanks you all.
One more question, should you explicitly configure for "ipv6 address
link-local" for the interface during practical lab?
On Fri, Sep 19, 2008 at 5:12 AM, Roger RPF <rpf@bluemail.ch> wrote:
> In Ipv6 everything is sourced from link-local address, except virtual
> links in ospf.
> I just configured your proposed setup below and it is not possible to
> ping for example R2 from R3 without the map statements to the link
> local address, as Ali said, encapsulation failed. Furthermore, if you
> use rip on the physical interface on R1, you have to disable split
> horizon in order for R3 to ping to R2
>
> regards
>
> Roger
>
> -----Urspr|ngliche Nachricht-----
> Von: nobody@groupstudy.com [mailto:nobody@groupstudy.com] Im Auftrag
> von Ali Mousawi
> Gesendet: Donnerstag, 18. September 2008 22:38
> An: Ed Man
> Cc: GS
> Betreff: Re: IPv6
>
> Hi Ed,
>
> Yeah they will learn the routes but the next hop will be the link
> local address that you cannot reach withount an L2-L3 resolution.
>
> HTH
>
> On Thu, Sep 18, 2008 at 8:42 AM, Ed Man <networkexpert08@gmail.com> wrote:
>
> > Hi Group
> >
> > When doing with RIPng over Frame Relay,
> >
> > R1
> > |
> > / \
> > / FR \
> > / \
> > | |
> > R2 R3
> >
> >
> > Is it a must to frame map their IPv6 link-local address for RIPng to
> work?
> > Why I ask this is that, without map IPv6 link-local, the routers
> > also can learn the RIPng routes from each other.
> >
> > Thanks
> > Ed.
> >
> >
> > Blogs and organic groups at http://www.ccie.net
> >
> > ____________________________________________________________________
> > ___ Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> ______________________________________________________________________
> _ Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Sat Oct 04 2008 - 09:26:18 ART