# Basic Interdomain Multicast w/o MSDP

Load **inter-as.multicast.msdp.init.cfg**

```
#IOS-XE
config replace flash:inter-as.multicast.msdp.init.cfg
 
#IOS-XR
configure
load bootflash:inter-as.multicast.msdp.init.cfg
commit replace
y
```

<figure><img src="/files/MVPaBwUdQBPAO8UUraRU" alt=""><figcaption></figcaption></figure>

On R2, enable multicast, PIM, and join the group (\*, 239.1.1.1). On R4, send traffic to to 239.1.1.1. R4 should receive a reply from R2. Do not use MSDP to achieve this.

## Answer <a href="#d46dc562-58cc-453b-bfe5-e36805695f41" id="d46dc562-58cc-453b-bfe5-e36805695f41"></a>

```
#R2
ip multicast-routing distributed
!
int Gi2.525
 ip pim sparse-mode
 ip igmp join-group 239.1.1.1

#R9
int GigabitEthernet2.569
 ip igmp static-group 239.1.1.1

#R6
int gi2.569
 ip pim dense-mode proxy-register list 100
!
ip access-list ext 100
 permit ip any any
```

## Explanation <a href="#a8934c35-9abd-41a8-a924-623cc6eb90a1" id="a8934c35-9abd-41a8-a924-623cc6eb90a1"></a>

Inter-domain multicast for ASM generally requires MSDP. However, this lab demonstrates an alternative to MSDP. By using the IGMP **static-group** command, the sending domain can forward the traffic out the interface to the receiving domain.

First, R2 joins group (\*, 239.1.1.1). R10 is the RP for this domain, so the RP tree is only built from R2 to R10.

Next, R4 starts sending, but R9 does not notify R10 of active sources, because they are not running MSDP. As a workaround, R9 can use **static-group** on the interface connecting to R6 to unconditionally forward the traffic out that interface.

```
#R9
int GigabitEthernet2.569
 ip igmp static-group 239.1.1.1
```

R9 adds this interface to the OIL for (\*, 239.1.1.1):

<div align="left"><figure><img src="/files/EcorH3NgtQKLL6BKdVMX" alt=""><figcaption></figcaption></figure></div>

Next, R4 starts sending and R9 forwards the traffic to R6. However, R6 realizes that the traffic is not sourced from the directly connected subnet, so it does not Register the traffic with R10. Instead, we can run dense-mode on R6 and configure R6 to proxy a PIM Register for received traffic. This was originally a way to bridge together a dense-mode and sparse-mode domain, but this tool can also be used in this context to achieve basic inter-domain multicasting.

```
#R6
int gi2.569
 ip pim dense-mode proxy-register list 100
!
ip access-list ext 100
 permit ip any any
```

Now when R4 sends, R6 registers this with R10. R10 can now join the SPT (11.4.13.4, 239.1.1.1):

<div align="left"><figure><img src="/files/SRLugkqj3rItMcG26Sig" alt=""><figcaption></figcaption></figure></div>

Traffic is now working:

<div align="left"><figure><img src="/files/szmI8SYnIbGLkKWDZJmP" alt=""><figcaption></figcaption></figure></div>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ccie-sp.gitbook.io/ccie-spv5.1-labs/labs/multicast/basic-interdomain-multicast-w-o-msdp.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.