IPv6 Multicasting:

Static RP:

Just like IPv4 Multicast routing is disabled and it must be enabled before we have multicasting
support on the Cisco devices.

On All Routers:
R2(config)#ipv6 multicast-routing

You should see the following console message:

%LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel0, changed state to up

Tunnel 0 comes up automatically, this is a tunnel in TX-ONLY mode and it is used to send “stop-
register” messages to the RP, but the RP is NOT known yet, so the routers think that they are the
first hop router and any minute they are going to receive the multicast traffic through one of their
interfaces and they need to send the register messages to the RP, let’s verify:

On R1
R1#Sh inter tunnel0
Tunnel0 is up, line protocol is up
Hardware is Tunnel
MTU 1514 bytes, BW 9 Kbit/sec, DLY 500000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation TUNNEL, loopback not set
Keepalive not set
Tunnel source 12::1 (FastEthernet0/0), destination UNKNOWN
 Tunnel protocol/transport PIM/IPv6

NOTE: In IPv6 when IPv6 multicast-routing is enabled, MLD and PIM will automatically be enabled on
active interfaces:

R1#Sh ipv6 pim inter

Interface PIM Nbr Hello DR
Count Intvl Prior

Tunnel0 off 0 30 1
Address: FE80::215:F9FF:FEEC:3110
DR : not elected
FastEthernet0/0 on 1 30 1
Address: FE80::1
DR : FE80::2
Loopback0 on 0 30 1
Address: FE80::1
DR : this system

R1#Show ipv6 mld int f0/0

FastEthernet0/0 is up, line protocol is up
Internet address is FE80::1/10
MLD is enabled on interface
Current MLD version is 2
MLD query interval is 125 seconds
MLD querier timeout is 255 seconds
MLD max query response time is 10 seconds
Last member query response interval is 1 seconds
MLD activity: 5 joins, 0 leaves
MLD querying router is FE80::1 (this system)

To disable MLD:

R1(config)#int f0/0
R1(config-if)#No ipv6 mld router

R1#Show ipv6 mld int f0/0

FastEthernet0/0 is up, line protocol is up
Internet address is FE80::1/10
MLD is disabled on interface

To re-enable MLD:

R1(config)#int f0/0
R1(config-if)#ipv6 mld router
R1#Show ipv6 mld int f0/0
FastEthernet0/0 is up, line protocol is up
Internet address is FE80::1/10
MLD is enabled on interface
Current MLD version is 2
MLD query interval is 125 seconds
MLD querier timeout is 255 seconds
MLD max query response time is 10 seconds
Last member query response interval is 1 seconds
MLD activity: 5 joins, 0 leaves
MLD querying router is FE80::1 (this system)

To disable PIM:

On R1
R1(config)#int f0/0
R1(config-if)#No ipv6 pim

R1#Sh ipv6 pim inter f0/0

Interface PIM Nbr Hello DR
Count Intvl Prior

FastEthernet0/0 off 0 30 1
Address: FE80::1
DR : not elected

To re-enable PIM:

R1(config)#int f0/0
R1(config-if)#ipv6 pim

R1#Sh ipv6 pim inter f0/0

Interface PIM Nbr Hello DR
Count Intvl Prior

FastEthernet0/0 on 1 30 1
Address: FE80::1
DR : FE80::2

Let’s configure R4’s Lo0 to join FF08::4444:

On R4
R4(config)#int lo0
R4(config-if)#ipv6 mld join-group FF08::4444
 R4#Show ipv6 mld group
MLD Connected Group Membership
Group Address Interface Uptime Expires
FF08::4444 Loopback0 00:00:46 never

Let’s configure R3 to be the RP:

On All Routers:

RX(config)#IPv6 pim rp-address 3::3

 
 
NOTE:  On  the  RP  you  should  see  two  tunnel  interfaces  come  up,  tunnel  1  and  tunnel  2.  
Tunnel  1  is  in  TX-­‐ONLY  mode  and  it  is  used  to  send  the  “stop-­‐Register”  messages.  
Tunnel  2  is  in  RX-­‐ONLY  mode  and  it  is  used  to  receive  the  register  messages.  
 
On  the  other  routers  you  should  see  a  single  tunnel  come  up,  tunnel  1,  this  tunnel  is  in  TX-­‐ONLY  mode  and  it  
is  used  to  send  stop-­‐register  messages  if  they  ever  become  an  RP.  

R5#Show ipv6 pim group-map ff08::4444

IP PIM Group Mapping Table
(* indicates group mappings being used)

FF00::/8*
SM, RP: 3::3
RPF: ,::
Info source: Static
Uptime: 00:05:20, Groups: 0
 
Let’s  check  the  mroute  table  of  all  routers:  

On R5
R5#Show ipv6 mroute
No mroute entries found.

On R4
R4#Show ipv mroute | b Incoming
Incoming interface: Serial0/0.43
RPF nbr: FE80::3
Immediate Outgoing interface list:
Loopback0, Forward, 00:21:40/never
On R3
R3#Show ipv mroute | b Incoming
Incoming interface: Tunnel2
RPF nbr: 3::3
Immediate Outgoing interface list:
Serial0/0.34, Forward, 00:03:44/00:02:42

On R2 and R1
R2#Show ipv mroute | b Incoming

R1,  R2  and  R5  are  not  in  the  path  so  they  should  not  see  any  state,  let’s  test  the  connectivity:  

On R1
R1#Ping ff08::4444
Output Interface: loopback0
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to FF08::4444, timeout is 2 seconds:
Packet sent with a source address of 1::1

Reply to request 0 received from 4::4, 164 ms

Reply to request 1 received from 4::4, 128 ms
Reply to request 2 received from 4::4, 108 ms
Reply to request 3 received from 4::4, 108 ms
Reply to request 4 received from 4::4, 108 ms
Success rate is 100 percent (5/5), round-trip min/avg/max = 108/123/164 ms
5 multicast replies and 0 errors.

All routers should see the RPF, incoming interface and outgoing interface/s. EXCEPT R5:

R5#Ping ff08::4444
Output Interface: loopback0
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to FF08::4444, timeout is 2 seconds:
Packet sent with a source address of 5::5

Reply to request 0 received from 4::4, 88 ms

Reply to request 1 received from 4::4, 8 ms
Reply to request 2 received from 4::4, 0 ms
Reply to request 3 received from 4::4, 0 ms
Reply to request 4 received from 4::4, 0 ms
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/19/88 ms
5 multicast replies and 0 errors.

R5#Sh ipv6 mroute

 Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group,
C - Connected, L - Local, I - Received Source Specific Host Report,
P - Pruned, R - RP-bit set, F - Register flag, T - SPT-bit set,
J - Join SPT
Timers: Uptime/Expires
Interface state: Interface, State

(5::5, FF08::4444), 00:00:15/00:03:14, flags: SFT

Incoming interface: Loopback0
RPF nbr: FE80::5
Immediate Outgoing interface list:
FastEthernet0/0, Forward, 00:00:15/00:03:14

BSR:

Let’s remove the commands from the previous lab and configure R4 to be the candidate BSR and
3 to be the RP:

On All Routers:
Rx(config)#No ipv6 pim rp-address 3::3

To configure R4 as the BSR:

R4(config)#IPv6 pim bsr candidate bsr 4::4

On R3

To configure R3 as the RP:

R3(config)#IPv6 pim bsr candidate rp 3::3

On All Routers:
R4#Sh ipv6 pim group-map ff08::4444
IP PIM Group Mapping Table
(* indicates group mappings being used)

FF00::/8*
SM, RP: 3::3
 RPF: Se0/0.43,FE80::3
Info source: BSR From: 4::4(00:01:43), Priority: 192
Uptime: 00:02:46, Groups: 1

Embedded RP:

Let’s remove the configuration from the previous lab:

On R4
R4(config)#int lo0
R4(config-if)#No ipv6 mld join-group ff08::4444

R4(config)#No IPv6 pim bsr candidate bsr 4::4

On R3
R3(config)#No IPv6 pim bsr candidate rp 3::3

Let’s configure Embedded RP:

In Embedded RP there is no need to configure RP’s IPv6 address on all routers because when they
ng the group address, it includes the IPv6 address of the RP.

Let’s configure R3 to be the RP:

On R3
R3(config)#IPv6 pim rp-address 3::3

NOTE: Only the RP is configured as the RP.

Let’s configure the Lo0 interface of R5 to join group 5555:5555:

On R5
R5(config)#Int Lo0
R5(config-if)#IPv6 mld join-group FF78:0340:3::5555:5555

To verify and test:

On All Routers:

R5#Ping FF78:0340:3::5555:5555
Output Interface: loopback0
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to FF78:340:3::5555:5555, timeout is 2 seconds:
Packet sent with a source address of 5::5

Reply to request 0 received from 5::5, 16 ms

Reply to request 1 received from 5::5, 0 ms
Reply to request 2 received from 5::5, 0 ms
Reply to request 3 received from 5::5, 0 ms
Reply to request 4 received from 5::5, 0 ms
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/3/16 ms
5 multicast replies and 0 errors.

FF ! It means Multicast
FF7 ! The added 7 means embedded RP
FF78 ! 5 means site wide, 8 means org wide and E means global wide
FF78:0 ! After the first section, bits 17, 18, 19 and 20 must all be zeros
FF78:03 ! The “3” is the last character of RP’s IPv6 address; Since the IPv6
address of the RP is 3::3, and it ends with 3. The last character “3” is the one
added to the embedded RP address
FF78:0340 ! the next two characters “40” is the prefix length, since
the Prefix-length is 64, 64 is converted to hex which is 40
FF78:0340:3:: ! 3:: is the network portion of the RP’s IPv6 address
FF78:0340:3::5555:5555 ! 5555:5555 is the group address