Wednesday, 1 January 2020

Source Specific Multicast




Today we are going to discuss about the PIM Sparse-mode.
Note all the router preconfigured with the ipv4 address and OSPF is used as the routing protocol, all routers are in area 0. PIM sparse dense mode it running.
IP ADDRESS: Fast Ethernet 155.1.XY.X/24
                       Loopback         X.X.X.X/32
Where X & Y is the router host number.(X <Y)

To enable the PIM Sparse mode we need to enable IP PIM SPARSE DEFAULT. This will enable the pim sparse mode for the group 232.0.0.0/8.

Lets this time we will do in reverse we will configure R5 the receiver first.
R5(config-if)#int lo0
R5(config-if)#ip igmp join-group 232.1.1.1 source 1.1.1.1




But R5 is sending the IGMPv2. Note for PIM SPARSE MODE we need to enable the PIM SPARSE MODE.
R5(config-if)#ip igmp version 3
We have to enable the igmp version 3 on the last hop router.
R4(config-if)#ip igmp version 3

IN SSM we don’t need the RP as receiver itself telling form which  receiver it should receive the feed.
 Note: We can also manually define the Group

Lets enable the source
R1#ping
Protocol [ip]:
Target IP address: 232.1.1.1
Repeat count [1]: 100000000
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Interface [All]: loopback0
Time to live [255]:
Source address: 1.1.1.1
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 100000000, 100-byte ICMP Echos to 224.5.5.5, timeout is 2 seconds:
Packet sent with a source address of 1.1.1.1
.............................................

Lets enable the BSR to lets populate the RP details. This we have done just to update the RP and check the state information.

R2(config)#ip pim bsr-candidate lo0

R3 will be acting as the candidate RP.
R3(config)#ip pim rp-candidate loopback 0

SSM uses the shared path tree(S,G) throughout the Path

R4#smr 232.1.1.1 | be Int
 Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 232.1.1.1), 00:00:41/stopped, RP 3.3.3.3, flags: SP
  Incoming interface: FastEthernet1/0, RPF nbr 155.1.34.3
  Outgoing interface list: Null
(1.1.1.1, 232.1.1.1), 00:00:05/00:03:26, flags: T
  Incoming interface: FastEthernet0/0, RPF nbr 155.1.24.2
  Outgoing interface list:
    FastEthernet2/0, Forward/Sparse, 00:00:05/00:03:25

R2#smr 232.1.1.1 | be Int
 Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 232.1.1.1), 00:20:43/stopped, RP 3.3.3.3, flags: SP
  Incoming interface: FastEthernet1/0, RPF nbr 155.1.23.3
  Outgoing interface list: Null
(1.1.1.1, 232.1.1.1), 00:20:43/00:03:21, flags: T
  Incoming interface: FastEthernet0/0, RPF nbr 155.1.12.1
  Outgoing interface list:
    FastEthernet2/0, Forward/Sparse, 00:20:43/00:03:29

R3#smr 232.1.1.1 | be Int
 Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 232.1.1.1), 00:16:04/00:03:21, RP 3.3.3.3, flags: S
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    FastEthernet1/0, Forward/Sparse, 00:10:48/00:03:21
(1.1.1.1, 232.1.1.1), 00:16:04/00:02:50, flags: PT
  Incoming interface: FastEthernet0/0, RPF nbr 155.1.23.2
  Outgoing interface list: Null

R5----------R4-(S,G)---------R2-(S,G)------------R1.

SSM works with both the SSM Group and also non SSM group at the same time.

No comments:

Post a Comment