Saturday 10 November 2012

Multicast: Sparse-Mode: Configuring Static RP:


Multicast: Sparse-Mode: Configuring Static RP:

 

·         Sparse mode is basically PULL technology

·         Explicit join

·         That means, Server and client must discover dynamically each other.

·         This is done using RP, Rendezvous Point.

·         RP can configured manually or can be discovered automatically.  

·         For source registration, PIM DR will send Unicast Registration towards RP.

·         For client registration, PIM DR will send multicast registration towards RP.

·         In this post, let me configure static RP configuration.

 

·         Let me take a basic 3-router topology:

 

R1---fa0/0-----fa0/0---R2----fa0/1--------fa0/1-----R3

 

·         R1-R2: 10.1.12.0/24

·         R2-R3: 10.1.23.0/24

 

·         OSPF is configured between these 3 routers and they are able to reach all loopback interfaces.

 

·         Let me configure R2’s loopback 2.2.2.2 as RP

 

·         We need to enable ip pim sparse-mode under loopback0 interface in R2.

·         Also, RPF check is done against RP in sparse-mode.

·         R1 is acting as multicast server and R3’s loopback0 is acting as receiver.

 

Configuration:

 

R1#show run int fa0/0

Building configuration...

 

Current configuration : 114 bytes

!

interface FastEthernet0/0

 ip address 10.1.12.1 255.255.255.0

 ip pim sparse-mode

 duplex auto

 speed auto

end

 

R1#show run | i rp-add

ip pim rp-address 2.2.2.2

R1#

 

R2#show run int fa0/0

Building configuration...

 

Current configuration : 114 bytes

!

interface FastEthernet0/0

 ip address 10.1.12.2 255.255.255.0

 ip pim sparse-mode

 duplex auto

 speed auto

end

 

R2#show run int fa0/1

Building configuration...

 

Current configuration : 114 bytes

!

interface FastEthernet0/1

 ip address 10.1.23.2 255.255.255.0

 ip pim sparse-mode

 duplex auto

 speed auto

end

 

R2#show run int loop0

Building configuration...

 

Current configuration : 83 bytes

!

interface Loopback0

 ip address 2.2.2.2 255.255.255.255

 ip pim sparse-mode

end

 

R2#

R2#show run | i rp-add

ip pim rp-address 2.2.2.2

R2#

 

R3#show run int fa0/1

Building configuration...

 

Current configuration : 114 bytes

!

interface FastEthernet0/1

 ip address 10.1.23.3 255.255.255.0

 ip pim sparse-mode

 duplex auto

 speed auto

end

 

R3#show run int loop0

Building configuration...

 

Current configuration : 151 bytes

!

interface Loopback0

 ip address 3.3.3.3 255.255.255.255

 ip pim sparse-mode

 ip igmp join-group 227.27.27.27

 ipv6 address 2002:303:303:1::3/64

end

 

R3#show run | i rp-add

ip pim rp-address 2.2.2.2

R3#

 

Verification:

 

R1#show ip pim rp mapping

PIM Group-to-RP Mappings

 

Group(s): 224.0.0.0/4, Static

    RP: 2.2.2.2 (?)

R1#

 

R2#show ip pim rp mapping

PIM Group-to-RP Mappings

 

Group(s): 224.0.0.0/4, Static

    RP: 2.2.2.2 (?)

R2#

 

R3#show ip pim rp mapping

PIM Group-to-RP Mappings

 

Group(s): 224.0.0.0/4, Static

    RP: 2.2.2.2 (?)

R3#

 

Observation:

·         2.2.2.2 is the RP for all multicast groups.

·         It is getting reflected in all the routers properly.

 

·         Now, let verify multicast functionality:

 

R1#ping 227.27.27.27

 

Type escape sequence to abort.

Sending 1, 100-byte ICMP Echos to 227.27.27.27, timeout is 2 seconds:

 

Reply to request 0 from 10.1.23.3, 120 ms

R1#

 

Observation:

·         Multicast sparse-mode is configured and working fine properly.

 

·         Now, let me see multicast routing table:

 

R1#show ip mroute

IP Multicast Routing Table

Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,

       L - Local, P - Pruned, R - RP-bit set, F - Register flag,

       T - SPT-bit set, J - Join SPT, M - MSDP created entry,

       X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,

       U - URD, I - Received Source Specific Host Report,

       Z - Multicast Tunnel, z - MDT-data group sender,

       Y - Joined MDT-data group, y - Sending to MDT-data group

Outgoing interface flags: H - Hardware switched, A - Assert winner

 Timers: Uptime/Expires

 Interface state: Interface, Next-Hop or VCD, State/Mode

 

(*, 227.27.27.27), 00:00:21/stopped, RP 2.2.2.2, flags: SP

  Incoming interface: FastEthernet0/0, RPF nbr 10.1.12.2

  Outgoing interface list: Null

 

(1.1.1.1, 227.27.27.27), 00:00:21/00:03:08, flags: T

  Incoming interface: Null, RPF nbr 0.0.0.0

  Outgoing interface list:

    FastEthernet0/0, Forward/Sparse, 00:00:21/00:03:08

 

(*, 224.0.1.40), 00:10:32/00:02:23, RP 2.2.2.2, flags: SJPCL

  Incoming interface: FastEthernet0/0, RPF nbr 10.1.12.2

  Outgoing interface list: Null

 

R1#

 

R2#show ip mroute

IP Multicast Routing Table

Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,

       L - Local, P - Pruned, R - RP-bit set, F - Register flag,

       T - SPT-bit set, J - Join SPT, M - MSDP created entry,

       X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,

       U - URD, I - Received Source Specific Host Report,

       Z - Multicast Tunnel, z - MDT-data group sender,

       Y - Joined MDT-data group, y - Sending to MDT-data group

Outgoing interface flags: H - Hardware switched, A - Assert winner

 Timers: Uptime/Expires

 Interface state: Interface, Next-Hop or VCD, State/Mode

 

(*, 227.27.27.27), 00:09:03/00:03:21, RP 2.2.2.2, flags: S

  Incoming interface: Null, RPF nbr 0.0.0.0

  Outgoing interface list:

    FastEthernet0/1, Forward/Sparse, 00:09:03/00:03:21

 

(1.1.1.1, 227.27.27.27), 00:00:27/00:03:05, flags: T

  Incoming interface: FastEthernet0/0, RPF nbr 10.1.12.1

  Outgoing interface list:

    FastEthernet0/1, Forward/Sparse, 00:00:27/00:03:21

 

(*, 224.0.1.40), 07:07:55/00:03:21, RP 2.2.2.2, flags: SJCL

  Incoming interface: Null, RPF nbr 0.0.0.0

  Outgoing interface list:

    FastEthernet0/1, Forward/Sparse, 00:09:03/00:03:21

    FastEthernet0/0, Forward/Sparse, 00:10:20/00:02:18

 

R2#

 

R3#show ip mroute

IP Multicast Routing Table

Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,

       L - Local, P - Pruned, R - RP-bit set, F - Register flag,

       T - SPT-bit set, J - Join SPT, M - MSDP created entry,

       X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,

       U - URD, I - Received Source Specific Host Report,

       Z - Multicast Tunnel, z - MDT-data group sender,

       Y - Joined MDT-data group, y - Sending to MDT-data group

Outgoing interface flags: H - Hardware switched, A - Assert winner

 Timers: Uptime/Expires

 Interface state: Interface, Next-Hop or VCD, State/Mode

 

(*, 227.27.27.27), 00:09:44/stopped, RP 2.2.2.2, flags: SJCL

  Incoming interface: FastEthernet0/1, RPF nbr 10.1.23.2

  Outgoing interface list:

    Loopback0, Forward/Sparse, 00:09:45/00:02:51

 

(1.1.1.1, 227.27.27.27), 00:00:28/00:02:36, flags: LJT

  Incoming interface: FastEthernet0/1, RPF nbr 10.1.23.2

  Outgoing interface list:

    Loopback0, Forward/Sparse, 00:00:28/00:02:51

 

(*, 224.0.1.40), 07:04:15/00:02:11, RP 2.2.2.2, flags: SJPCL

  Incoming interface: FastEthernet0/1, RPF nbr 10.1.23.2

  Outgoing interface list: Null

 

R3#

No comments:

Post a Comment