From: mani poopal (mani_ccie@yahoo.com)
Date: Wed Apr 20 2005 - 09:15:18 GMT-3
thanks guys. I will have to play around with the technology.
Mani
"George Cassels (gcassels)" <gcassels@cisco.com> wrote:
Mani,
See below the mroute command is supposed to be used with the source
of the multicast not a multicast address. The source for a multicast
stream is always a unicast address. Basically what you are doing is
over-riding the RPF check. You should not have to use a tunnel and a
mroute.
ip mroute
To configure a multicast static route (mroute), use the ip mroute
command in global configuration mode. To remove the route, use the no
form of this command.
ip mroute source-address mask [protocol as-number] {rpf-address | type
number} [distance]
no ip mroute source mask [protocol as-number] {rpf-address | type
number} [distance]
Syntax Description
source-address
IP address of the multicast source.
mask
Mask on the IP address of the multicast source.
protocol
(Optional) Unicast routing protocol that you are using.
as-number
(Optional) Autonomous system number of the routing protocol you are
using, if applicable.
rpf-address
Incoming interface for the mroute. If the Reverse Path Forwarding (RPF)
address rpf-address is a Protocol Independent Multicast (PIM) neighbor,
PIM join, graft, and prune messages are sent to it. The rpf-address
argument can be a host IP address of a directly connected system or a
network/subnet number. When it is a route, a recursive lookup is done
from the unicast routing table to find a directly connected system. If
the rpf-address argument is not specified, the interface type number
value is used as the incoming interface.
type number
Interface type and number for the mroute.
distance
(Optional) Determines whether a unicast route, a Distance Vector
Multicast Routing Protocol (DVMRP) route, or a static mroute should be
used for the RPF lookup. The lower distances have better preference. If
the static mroute has the same distance as the other two RPF sources,
the static mroute will take precedence. The default is 0.
Defaults
distance: 0
Command Modes
Global configuration
Command History
Release
Modification
11.0
This command was introduced.
Usage Guidelines
This command allows you to statically configure where multicast sources
are located (even though the unicast routing table shows something
different).
When a source range is specified, the rpf-address argument applies only
to those sources.
Examples
The following example configures all sources via a single interface (in
this case, a tunnel):
ip mroute 0.0.0.0 0.0.0.0 tunnel0
The following example configures all specific sources within a network
number to be reachable through 172.30.10.13:
ip mroute 172.16.0.0 255.255.0.0 172.30.10.13
The following example causes this multicast static route to take effect
if the unicast routes for any given destination go away:
ip mroute 0.0.0.0 0.0.0.0 serial0 200
________________________________
From: Lee Donald [mailto:Lee.Donald@t-systems.co.uk]
Sent: Wednesday, April 20, 2005 8:01 AM
To: mani poopal; Lee Donald; George Cassels (gcassels);
ccielab@groupstudy.com
Subject: RE: multicast doubt of frame-relay hub and spoke
Come to think of it, you would have to use a tunnel, or static mroutes
and p2p ints.
________________________________
From: mani poopal [mailto:mani_ccie@yahoo.com]
Sent: 20 April 2005 12:53
To: Lee Donald; George Cassels (gcassels); ccielab@groupstudy.com
Subject: RE: multicast doubt of frame-relay hub and spoke
Lee,
I thought you have to use tunnel as well as static mroute. Do you have
any sample configs.
=============================================
eg:
on RC:
int tu 0
ip unnumbered s 0
tu source s 0
tu destination 133.13.13.1
ip pim sparse-dense-mode
ip mroute 225.25.25.25 255.255.255.255 tu 0
==================================
thanks
Mani
Lee Donald wrote:
Mani,
Ip pim nbma-mode only functions with sparse, although you can
configure it
with sparse-dense.
Both spokes have a direct connection with the mapping agent, so
I suppose
you have a split horizon problem in force. You could either use
static
mroutes or a tunnel.
Regards
Lee.
-----Original Message-----
From: George Cassels (gcassels) [mailto:gcassels@cisco.com]
Sent: 20 April 2005 12:09
To: mani poopal; ccielab@groupstudy.com
Subject: RE: multicast doubt of frame-relay hub and spoke
Mani,
You can announce any multicast enabled interface as the RP,
although I would normally enable it on a centrally located
router it
does not have to be. I will assume you are using sparse-dense
mode
since you are using auto-RP. The hub router will not send
packets out
of ports it received the traffic on so you could do a static
mroute
since your configuration is all on the same subnet and will not
allow
for separate P2P sub interfaces. My question would be do you
need the
ip pim nbma-mode with running in sparse-dense mode. I know you
need it
with sparse mode to track individual join and leaves, but not
sure if
you need it if you are running sparse dense.
Regards,
George
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
Behalf Of
mani poopal
Sent: Wednesday, April 20, 2005 6:24 AM
To: ccielab@groupstudy.com
Subject: multicast doubt of frame-relay hub and spoke
Guys please look at the scenario below any help is appreciated.
Frame relay hub and spoke: RB hub and RA/RC spokes
e0(RA)s0--------------------s0(RB)HUB-----------s0(RC)e0 spoke
s0 =133.13.13.1 s0 133.13.13.2 s0=133.13.13.3
e0 =133.13.10.1 e0 133.13.20.1 e0=133.13.30.1
lo0 =133.13.1.1 lo0 133.13.2.2 lo0=133.13.3.3
scenario:
make RB mapping agent
make RA e0 Join mcast group 225.25.25.25 make RA announce it as
RP.for
multicast group 225.25.25.25
questions:
-If not asked to enable mcast on lo 0, is it ok to put lo 0 in
pim and
announce RA lo 0(ip pim send-rp-announce lo 0) or should we
announce e0
-once this is configured, unable to ping the mcast 225.25.25.25
group
from FR other spoke router(RC), so how we solve, even if a
question
doesnt asks for static mcast routes and introduction of tunnel
interfaces, can we use it, how
thanks
Mani
B.ENG,A+,CCNA,CCNP,CCNP-VOICE, CSS1,CNA,MCSE
(416)431 9929
MANI_CCIE@YAHOO.COM
This archive was generated by hypermail 2.1.4 : Tue May 03 2005 - 07:55:03 GMT-3