From: Scott Morris (smorris@ipexpert.com)
Date: Sat Sep 15 2007 - 11:03:04 ART
But 5 is where it's coming from now, right? The "ip mroute" command is NOT
a static route. It's an "alternate path" for multicast to come in on. So
if you are receiving from R5 although that's not your unicast path, you'll
need the mroute to allow it (or it'll fail RPF).
But putting an mroute on a receiving router to R6 won't do anything to your
incoming flow of traffic! We can allow things, but not change the receive
path.
HTH,
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713, JNCIE
#153, CISSP, et al.
CCSI/JNCI-M/JNCI-J
VP - Technical Training - IPexpert, Inc.
IPexpert Sr. Technical Instructor
A Cisco Learning Partner - We Accept Learning Credits!
smorris@ipexpert.com
Telephone: +1.810.326.1444
Fax: +1.810.454.0130
http://www.ipexpert.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
robert.steeneken@getronics.com
Sent: Saturday, September 15, 2007 3:01 AM
To: ccielab@groupstudy.com
Subject: RE: RE: mroute
140.40.2.2 is the loopback of R2. When I divide the LAN in two different
vlans it works when I make a mroute for 140.40.2.2 to the ip address of R6
But shouldn,t the RPF change when I add a mroute?
*, 224.2.2.2), 00:13:55/00:02:56, RP 140.40.2.2, flags: SCL
Incoming interface: FastEthernet0.56, RPF nbr 140.40.56.5 <--
Outgoing interface list:
Loopback0, Forward/Sparse, 00:13:55/00:02:56
R7(config)#ip mroute 140.40.2.2 255.255.255.255 140.40.56.6
(*, 224.2.2.2), 00:00:02/00:02:57, RP 140.40.2.2, flags: SCL
Incoming interface: FastEthernet0.56, RPF nbr 140.40.56.5, Mroute <--
Outgoing interface list:
Loopback0, Forward/Sparse, 00:00:02/00:02:57
R1
|
R2 (RP)
|
R4
/ \
/ \
R5 R6
__|______|__
|
R7
This archive was generated by hypermail 2.1.4 : Sat Oct 06 2007 - 12:01:12 ART