Re: Verification of ip multicast helper-map task

From: Narbik Kocharians <narbikk_at_gmail.com>
Date: Sun, 26 Apr 2009 09:47:54 -0700

*Sorry for the LONG post, but this is another way to configure and test the
helper-map:*
*Let me know if you guys/ladies see a problem or typos. Its the 2.0 beta
where every lab is tested:*
*Enjoy.......*

*Topology:*

* *

R1 is connected to R2 via F0/0

R2 is connected to R3 which is connected to R4 via Frame-relay P2P

R4 is connected to R5 via F0/0

*Lab Setup:*

X Configure the F0/0 interface of R1, R2 in VLAN 100.

X Configure the F0/0 interface of R4, R5 in VLAN 200.

X Configure all frame-relay connections in point-to-point manner.

X Configure the IP addressing based on the following chart.

* *

*IP addressing:*

R1s F0/0 = 10.1.12.1/24, Lo0 = 1.1.1.1 /8

R2s F0/0 = 10.1.12.2/24, S0/0.23 = 10.1.23.2/24, Lo0 = 2.2.2.2/8

R3s S0/0.32=10.1.23.3/24, S0/0.34=10.1.34.3/24

R4s S0/0.43=10.1.34.4/24, F0/0=10.1.45.4/24

R5s F0/0=10.1.45.5/24

* *

* *

*Task 1*

* *

Configure OSPF Area 0 on *all frame-relay links* and the loopback interface
of R2.

* *

*On R2*

R2(config)#router ospf 1

R2(config-router)#netw 10.1.23.2 0.0.0.0 area 0

R2(config-router)#netw 2.2.2.2 0.0.0.0 area 0

* *

*On R3*

R3(config)#router ospf 1

R3(config-router)#netw 0.0.0.0 0.0.0.0 area 0

* *

*On R4*

R4(config)#router ospf 1

R4(config-router)#netw 10.1.34.4 0.0.0.0 area 0

*To verify the configuration:*

* *

*On R2*

* *

*R2#Show ip route ospf | Inc O*

* *

O 10.1.34.0 [110/128] via 10.1.23.3, 00:00:54, Serial0/0.23

*On R4*

*R4#Show ip route ospf | Inc O*

* *

O 2.2.2.2 [110/129] via 10.1.34.3, 00:01:37, Serial0/0.43

O 10.1.23.0 [110/128] via 10.1.34.3, 00:01:37, Serial0/0.43

* *

* *

*Task 2*

Configure *RIPv2 on the F0/0 and loopback 0* interfaces of R1 and R5s F0/0.
Disable the auto-summarization on both of these routers.

* *

* *

*On R1 *

* *

R1(config)#router rip

R1(config-router)#no au

R1(config-router)#ver 2

R1(config-router)#Netw 10.0.0.0

R1(config-router)#Netw 1.0.0.0

*On R5 *

* *

R5(config)#router rip

R5(config-router)#no au

R5(config-router)#ver 2

R5(config-router)#Netw 10.0.0.0

* *

*Task 3*

Configure Multicasting on the appropriate routers such that R5 receives all
the *RIPv2* updates from R1.

R2 should be configured as the RP and BSR router, this router should use
its loopback interface as the source of all its BSR messages. You MUST use
224.1.1.1 to accomplish this task.

*This task calls for helper-map configuration, as follows:*

* *

*In the first step of this configuration, R1 is configured to send RIPv2
updates to a broadcast destination so R2 can map them to a Multicast address
of 224.1.1.1.*

R1(config)#int f0/0

R1(config-if)#*ip rip v2-broadcast*

*Step two:*

* *

*In this step IP multicast-routing should be enabled on all transit routers,
which are: R2, R3 and R4. *

*On R2, R3 and R4*

(config)#*ip multicast-routing*

* *

*Step Three:*

* *

*Pim sparse mode should be enabled on R2s F0/0, S0/0.23 and its loopback 0
interface, on R3s S0/0.32 and S0/0.34, on R4s S0/0.43 interface:*

*On R2*

R2(config)#int f0/0

R2(config-if)#*ip pim sparse-mode*

R2(config)#int s0/0.23

R2(config-subif)#*ip pim sparse-mode*

* *

R2(config)#int lo0

R2(config-if)#*ip pim sparse-mode*

*On R3*

R3(config)#int s0/0.32

R3(config-subif)#*ip pim sparse-mode*

R3(config)#int s0/0.34

R3(config-subif)#*ip pim sparse-mode*

*On R4*

R4(config)#int s0/0.43

R4(config-subif)#*ip pim sparse-mode*

*To verify the configuration:*

* *

*On R4*

*R4#Show ip pim neighbor*

PIM Neighbor Table

Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,

      S - State Refresh Capable

Neighbor Interface Uptime/Expires Ver DR

Address
Prio/Mode

10.1.34.3 Serial0/0.43 00:01:55/00:01:18 v2 1 / S

*R3#Show ip pim neighbor *

PIM Neighbor Table

Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,

      S - State Refresh Capable

Neighbor Interface Uptime/Expires Ver DR

Address
                         Prio/Mode

10.1.23.2 Serial0/0.32 00:03:43/00:01:28 v2 1 / S

10.1.34.4 Serial0/0.34 00:03:06/00:01:35 v2 1 / S

*R2#Show ip pim neighbor*

PIM Neighbor Table

Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,

      S - State Refresh Capable

Neighbor Interface Uptime/Expires Ver DR

Address
                               Prio/Mode

10.1.23.3 Serial0/0.23 00:04:02/00:01:38 v2 1 / S

*Step four:*

* *

*BSR multicast routing is configured on R2; in this step R2 is configured as
the RP and the BSR using the loopback0 interface as the source of its
packets:*

*On R2*

R2(config)#*ip pim rp-candidate lo0*

R2(config)#*ip pim bsr-candidate lo0*

*To verify the configuration:*

* *

*On R3*

*R3#Show ip pim rp map*

PIM Group-to-RP Mappings

Group(s) 224.0.0.0/4

  RP 2.2.2.2 (?), v2

    Info source: 2.2.2.2 (?), via bootstrap, priority 0, holdtime 150

         Uptime: 00:00:09, expires: 00:02:19

*On R4*

*R4#Show ip pim rp map*

PIM Group-to-RP Mappings

Group(s) 224.0.0.0/4

  RP 2.2.2.2 (?), v2

    Info source: 2.2.2.2 (?), via bootstrap, priority 0, holdtime 150

         Uptime: 00:00:32, expires: 00:02:05

*Step five:*

* *

*In the following step an access-list is configured to identify the RIP
traffic being sent from 10.1.12.1 (R1s F0/0 interface) to a broadcast IP
address destined for RIP. *

*On R2*

* *

*R2(config)#Access-list 100 permit udp host 10.1.12.1 eq rip host
255.255.255.255 eq rip*

* *

*The following command specifies the forwarding of broadcast messages
destined to UDP 520 (RIP):*

R2(config)#*ip forward-protocol udp rip*

*The following command is configured to converts the broadcast traffic
arriving at the F0/0 interface of the first hop router (The router closest
to the source) destined for UDP port 520 (RIP) to a multicast group
destination address of 224.1.1.1:*

* *

R2(config)#int F0/0

R2(config-if)#*ip multicast helper-map broadcast 224.1.1.1 100 ttl 3*

*Note the TTL keyword specifies the TTL value of multicast packets generated
by the helper-map from incoming broadcast packets. The range is 1  50 hops.
*

* *

*On R4*

*On the last hop router, the traffic is once again identified using
access-list
100 and forwarding of broadcast messages destined to UDP 520 (RIP) is
specified:*

R4(config)#*access-list 100 permit udp host 10.1.12.1 any eq rip*

R4(config)#*ip forward-protocol udp rip*

* *

*In the following command, the last hop router (Router closest to the group
members) is configured to convert the multicast traffic arriving at
S0/0.43interface back to broadcast on the outgoing interface of F0/0.
*

* *

R4(config)#Int S0/0.43

R4(config-subif)#*ip multicast helper-map 224.1.1.1 10.1.45.255 100*

*Since the traffic will be sent to the F0/0 interface of R4 as a directed
broadcast, directed broadcast is enabled:*

R4(config)#int f0/0

R4(config-if)#*ip directed-broadcast*

*To verify the configuration:*

* *

*On R5*

*Note the following command is required to disable the sanity check
performed by RIP enabled routers:*

R5(config)#router rip

R5(config-router)#*no validate-update-source*

*R5#Sh ip route rip*

* *

*R 1.0.0.0/8* [120/1] via 10.1.12.1, 00:00:05

*Note R5 receives the RIPv2 route/s advertised by R1.*

On Sun, Apr 26, 2009 at 8:07 AM, Tony Blanco <blancoj17_at_yahoo.com> wrote:

>
> NTP Multicast is a nice way to verify everything in Multicasting......and
> very easy to configure.....
>
>
>
> ----- Original Message ----
> From: Narbik Kocharians <narbikk_at_gmail.com>
> To: Vincent Tay <vtay.75_at_gmail.com>
> Cc: "Ccielab_at_groupstudy.com" <ccielab_at_groupstudy.com>
> Sent: Friday, April 24, 2009 2:51:21 AM
> Subject: Re: Verification of ip multicast helper-map task
>
> There are much better alternatives than IP SLA.
>
> On Thu, Apr 23, 2009 at 9:40 PM, Vincent Tay <vtay.75_at_gmail.com> wrote:
>
> > Hi all,
> >
> > I am working on the ip multicast helper-map task and will like to verify.
> > As
> > IP SLA does not support broadcast, i do not know whether it is a bug or
> > ...
> > ?
> >
> > Is there any workaround for it?
> >
> > R6(config-sla-monitor)#type udpEcho dest-ipaddr ?
> > Hostname or A.B.C.D IP address or hostname, broadcast disallowed
> >
> > Thanks.
> > Regards
> > /VT
> >
> >
> > Blogs and organic groups at http://www.ccie.net
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
> >
> >
> >
> >
> >
> >
> >
> >
>
>
> --
> Narbik Kocharians
> CCSI#30832, CCIE# 12410 (R&S, SP, Security)
> www.MicronicsTraining.com <http://www.micronicstraining.com/>
> www.Net-Workbooks.com <http://www.net-workbooks.com/>
> Sr. Technical Instructor
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>

--
Narbik Kocharians
CCSI#30832, CCIE# 12410 (R&S, SP, Security)
www.MicronicsTraining.com
www.Net-Workbooks.com
Sr. Technical Instructor
Blogs and organic groups at http://www.ccie.net
Received on Sun Apr 26 2009 - 09:47:54 ART

This archive was generated by hypermail 2.2.0 : Mon May 04 2009 - 07:39:13 ART