From: Mick Vaites (mick@pobox.net.uk)
Date: Thu Jan 17 2008 - 11:58:58 ARST
Hi Alex
got that, the question is when confronted with the senario what is the
proctor looking for ?
Regards
Mick
________________________________
From: Alexandre Ribeiro [mailto:alexandregomesribeiro@gmail.com]
Sent: 17 January 2008 11:45
To: Mick Vaites
Cc: ccielab@groupstudy.com
Subject: Re: IPv6 Frame-relay map's
Hi,
You need to place both mappings, since OSPFv3 or RIPng will use the link
local address as the source address for link local scope multicasts.
In the scenario that you presented you only need one broadcast
statement, since both IPv6 addresses map to the same DLCI. If a
multicast or broadcast packet arrives to a FR router, the router
searches for the map statements that have the broadcast keyword and
sends a packet to each circuit specified on those map statements. On the
presented scenario, if you placed two broadcast statements, the router
would send the same multicast packet twice to that DLCI.
Alex
On Jan 15, 2008 12:25 AM, Mick Vaites <mick@pobox.net.uk> wrote:
Hi all,
I am puzzling over which is correct and which is not.
It is necessary to put in L2 / L3 mappings for both the actual
IPv6
addressing as well as the lnik local addresses but which gets
the
broadcast statement?
Senario: two routers connected for IPv6, R1 and R5 over a
frame-relay
cloud, network is 2001:cc1e:5:15::x/64 and the DLCI's are 105
and 501
respectively. This are the possible snippets for R1. (apologies
for any
obvious typos).
I am wondering which is right
!R1
Interface Serial 1/0
ipv6 address 2001:cc1e:5:15::1/64
ipv6 address fe80::1 link-local
frame-relay map ipv6 fe80::5 105 broadcast <---- broadcast on
the
link-local
frame-relay map ipv6 2001:cc1e:5:15::5 105
or
!R1
Interface Serial 1/0
ipv6 address 2001:cc1e:5:15::1/64
ipv6 address fe80::1 link-local
frame-relay map ipv6 fe80::5 105
frame-relay map ipv6 2001:cc1e:5:15::5 105 broadcast <-----
broadcast
on the main IP
I have tried both of these senarios and both work okay ?
Best regards
Mick
This archive was generated by hypermail 2.1.4 : Fri Feb 01 2008 - 10:38:00 ARST