Multicasting – PIM Sparse Mode Test -1

We already discussed about PIM – Sparse Mode in previous posts. Let’s see one basic example for it. I hope it will help to understand PIM Sparse mode practically. For theory part , Plz refer previous post in Multicasting Tab..

In this example, I used Maipu routers. For Cisco Routers the configuration is same.

Maipu 3840 is BSR and RP

Maipu 7508 is receiver router

Multicast Source – 192.168.1.7

Multicast Receiver – 192.168.200.2

We used static Routing for connectivity,  you can use any routing protocol as per requirement. You can use any 3^rd party software or tool like VLC for multicast testing.

Topology:

Multicast PIM -Sparse Mode Setup

Configuration template –

MP 3840- Multicast Source

ip access-list standard 1

 10 permit host 224.0.1.12

 exit

ip multicast-routing

 interface gigaethernet0

 ip address 192.168.1.137 255.255.252.0

 ip pim sparse-mode

 exit

 interface gigaethernet1

 ip address 192.168.100.2 255.255.255.0

 ip pim sparse-mode

 exit       

 ip pim bsr-candidate gigaethernet1

ip pim rp-candidate gigaethernet0 192 60 group-list 1

### We are configuring this router as BSR candidate and RP candidate ###

            

ip route 192.168.200.0 255.255.255.0 192.168.100.1

  

!end

Show Outputs 

MP3840#sh ip pim bsr-router

PIMv2 Bootstrap information

PIM VRF Name: Default

This system is the Bootstrap Router (BSR)   ##Check this information ##

  BSR address: 192.168.100.2

  BSR Priority: 0

  Hash mask length: 10

  Up time: 00:26:00

  Next bootstrap message in 00:00:05

  Role: Candidate BSR

  State: Elected BSR

  Candidate RP: 192.168.1.137(gigaethernet0)

    Advertisement interval 60 secs.

    Next Cand_RP_advertisement in 00:00:53

MP3840#sh ip pim rp mapping

PIM Group-to-RP Mappings Table:

PIM VRF Name: Default

Total 1 RP set entry

Total 1 RP entry

This system is the Bootstrap Router (v2)    ### Check this information ###

  Group(s): 224.0.1.12/32

  RP count: 1

    RP: 192.168.1.137

      Info source: 192.168.100.2, via bootstrap, priority 192

      Up time: 00:25:19

      Expiry time: 00:02:11

MP3840#sh ip pim mroute

IP Multicast Routing Table:

PIM VRF Name: Default

Total 0 (*,*,RP) entry

Total 4 (*,G) entries

Total 1 (S,G) entry

Total 1 (S,G,rpt) entry

Total 0 FCR entry

Up timer/Expiry timer

(*, 224.0.1.12)

Up time: 00:12:29

RP: 192.168.1.137

RPF nbr: 0.0.0.0

RPF idx: None

Upstream State: JOINED

  Local interface list:

  Joined interface list:

    gigaethernet1  00:12:29/00:03:01

  Asserted interface list:

(192.168.1.7, 224.0.1.12)                   ### We can see Multicast S,G entry ###

Up time: 00:25:27

KAT time: 00:02:05

RPF nbr: 0.0.0.0

RPF idx: None

SPT bit: TRUE

Upstream State: JOINED

  Local interface list:

  Joined interface list:

    gigaethernet1  00:12:29/00:03:01

  Asserted interface list:

  Outgoing interface list:

    gigaethernet1

  Packet count 37735

(192.168.1.7, 224.0.1.12, rpt)

Up time: 00:12:29

RP: 192.168.1.137

Upstream State: NOT PRUNED

  Local interface list:

  Pruned interface list:

  Outgoing interface list:

    gigaethernet1

(*, 224.0.1.41)

Up time: 00:46:23

RP: 0.0.0.0 

RPF nbr: 0.0.0.0

RPF idx: None

Upstream State: JOINED

  Local interface list:

    gigaethernet0

  Joined interface list:

  Asserted interface list:

(*, 225.102.116.110)

Up time: 00:46:23

RP: 0.0.0.0

RPF nbr: 0.0.0.0

RPF idx: None

Upstream State: JOINED

  Local interface list:

    gigaethernet0

  Joined interface list:

  Asserted interface list:

(*, 239.255.255.250)

Up time: 00:46:23

RP: 0.0.0.0

RPF nbr: 0.0.0.0

RPF idx: None

Upstream State: JOINED

  Local interface list:

    gigaethernet0

  Joined interface list:

  Asserted interface list:

MP7508 Configuration – Multicast Receiver 

ip multicast-routing

interface gigaethernet0

 ip address 192.168.200.1 255.255.255.0

 ip pim sparse-mode

 exit

 interface gigaethernet1

 ip address 192.168.100.1 255.255.255.0

 ip pim sparse-mode

 exit

                                      

ip route 192.168.0.0 255.255.252.0 192.168.100.2

!end

### As BSR is configured in network, It will be advertised in Multicast network , no need to configure RP ###

MP7508# sh ip pim bsr-router

PIMv2 Bootstrap information

PIM VRF Name: Default

  BSR address: 192.168.100.2                 ### BSR router Information ###

  BSR Priority: 0

  Hash mask length: 10

  Up time: 00:26:57

  Expiry time: 00:01:14

  Role: Non-candidate BSR

  State: Accept Preferred

MP7508#sh ip pim rp mapping

PIM Group-to-RP Mappings Table:

PIM VRF Name: Default

Total 1 RP set entry

Total 1 RP entry

  Group(s): 224.0.1.12/32

  RP count: 1

    RP: 192.168.1.137                                         ### RP information ###

      Info source: 192.168.100.2, via bootstrap, priority 192

      Up time: 00:26:02

      Expiry time: 00:02:29

MP7508#sh ip pim mroute

IP Multicast Routing Table:

PIM VRF Name: Default

Total 0 (*,*,RP) entry

Total 1 (*,G) entry

Total 1 (S,G) entry

Total 1 (S,G,rpt) entry

Total 0 FCR entry

Up timer/Expiry timer

(*, 224.0.1.12)

Up time: 00:13:22

RP: 192.168.1.137

RPF nbr: 192.168.100.2

RPF idx: gigaethernet1

Upstream State: JOINED

  Local interface list:

    gigaethernet0

  Joined interface list:

  Asserted interface list:

(192.168.1.7, 224.0.1.12)                 ### We can see multicast S,G entry , Multicast receiver is active##

Up time: 00:13:22

KAT time: 00:02:22

RPF nbr: 192.168.100.2

RPF idx: gigaethernet1

SPT bit: TRUE

Upstream State: JOINED

  Local interface list:

  Joined interface list:

  Asserted interface list:

  Outgoing interface list:

    gigaethernet0

  Packet count 41562

(192.168.1.7, 224.0.1.12, rpt)

Up time: 00:13:22

RP: 192.168.1.137

Upstream State: NOT PRUNED

  Local interface list:

  Pruned interface list:

  Outgoing interface list:

In this testing I included all outputs; it will help you in practice to compare it.

As I already mentioned above Cisco configuration will be same. If anyone is facing any issue, Plz put comments.

Hope this example will help you in configuring PIM Sparse mode..

For likes and any queries, Plz put comments with your mail id...

GVRP - GARP VLAN Registration protocol

Many times we see VTP protocol, Many of engineers would know that GVRP is same like VTP in Cisco. In this section we will discuss about GVRP.

GVRP(GARP VLAN Registration protocol) is one application protocol defined by GARP. It is the GARP-based protocol mechanism, maintaining the VLAN information in the switch dynamically.

All switches that support GVRP can receive the VLAN registration information from other switches and updates the local VLAN registration information dynamically, including the current VLAN on the router And ports contained in the VLANs. Moreover, all switches that support GVRP can spread the local VLAN registration information to other switches, so as to make the VLAN configurations of all devices that support GVRP in one switching network consistent. 

The VLAN registration information spread by GVRP includes the static VLAN information configured manually at the local and the dynamic VLAN information from other switches. Note that the Leave message of GVRP cannot delete the VLAN configured manually at the local, that is to say, the priority of the VLAN configured manually is higher than the GVRP operation.

GVRP realizes the dynamic registration, maintenance and de-registration of the port member information in the VLAN. If VLAN does not exist, create the VLAN dynamically. If the number of the port members in the VLAN is 0, delete the VLAN dynamically, that is, add the port dynamically to VLAN or delete the port from the VLAN. In this way, the dynamic configuration of VLAN on the VLAN is realized.

GVRP can dynamically configure the VLAN, so there is no need to configure all VLANs of all devices, but only need to configure some devices especially edge devices, and some special VLANs. The other devices can be automatically configured by GVRP. Currently, the enterprise network is large and there are many VLANs. 

The GVRP function greatly reduces the configuration work of the administrator and the possibility of the manual mistakes. Moreover, when the network topology changes, the GVRP function can help to configure the VLAN automatically, so as to ensure the connectivity between VLANs.

Some Basics:

• Generic Attribute Registration Protocol (GARP) VLAN Registration Protocol(GVRP) is an application defined in the IEEE 802.1Q standard that allows for the control of VLANs.
• GVRP runs only on 802.1Q trunk links.
• GVRP prunes trunk links so that only active VLANs will be sent across trunk connections.
• GVRP expects to hear join messages from the switches before it will add a VLAN to the trunk.
• GVRP updates and hold timers can be altered.
• GVRP ports run in various modes to control how they will prune VLANs.
• GVRP can be configured to dynamically add and manage VLANS to the VLAN database for trunking purposes.

Hope you got understanding about GVRP. Its similar like VTP in Cisco. In coming post I will let you know how to configure it on Maipu switches. 

Will try to share some more information also regrading commands details. 

Hope this post is informative for you..

For feedback and queries, Plz comment with your mail id.