[Contents] [Prev] [Next] [Index] [Report an Error]

Example: Basic IPv4 Multicast over a Layer 3 VPN Configuration

Figure 63: Basic IPv4 Multicast over a Layer 3 VPN Topology Diagram

Image g017220.gif

In Figure 63, the multicast source sends to group 229.1.1.1, and the receiver listens to the same group address. The VPN C-RP is located at Router CE1, whereas the SP-RP is located at Router P0. The routing instances are named VPN-A on both routers PE0 and PE1.

Router CE0



[edit]
protocols {


pim {


rp {


dense-groups {
229.0.0.0/8;
}




static {
address 10.254.245.91;
}


}




interface all {
mode sparse-dense;
version 2;
}




interface fxp0.0 {
disable;
}


}


}

In this example, the interface all statement is configured. If the topology requires only a few interfaces to be configured for PIM, then loopback interface lo0 must also be one of the configured interfaces.

Router PE0



[edit]
protocols {


pim {


rp {


static {
address 10.254.71.47;
}


}




interface all {
mode sparse;
version 2;
}




interface fxp0.0 {
disable;
}


}


}

Router PE0 also requires a standard VPN configuration, along with the PIM instance configuration. The vpn-group-address command is the only new PIM statement with PIM used exclusively with a routing instance multicast configuration.



[edit]
routing-instances {


VPN-A {
instance-type vrf;
interface t1-0/3/0:0.0;
                 
interface lo0.1               

route-distinguisher 10.254.71.46:100;
vrf-import VPNA-import;
vrf-export VPNA-export;


protocols {


ospf {
export bgp-to-ospf;


area 0.0.0.0 {
interface t1-0/3/0:0.0;
interface lo0.1;
}


}




                     
pim { 
                 



dense-groups {
229.0.0.0/8;
}


                     
vpn-group-address 239.1.1.1;                   



rp {


static {
address 10.254.245.91;
}


}




interface t1-0/3/0:0.0 {
mode sparse-dense;
version 2;
}




                       
interface lo0.1 {                     

mode sparse-dense;
version 2;
}


}


}


}


}

Router P0



[edit]
protocols {


pim {


rp {


local {
                     
address 10.254.71.47;
}


}




interface all {
mode sparse;
version 2;
}




interface fxp0.0 {
disable;
}


}


}

Again, if the configuration calls for specific interfaces to be configured for PIM, loopback interface lo0 must be included as one of the interfaces running PIM.

Router PE1



[edit]
protocols {


pim {


rp {


static {
address 10.254.71.47;
}


}




interface all {
mode sparse;
version 2;
}




interface fxp0.0 {
disable;
}


}


}
routing-instances {


VPN-A {
instance-type vrf;
interface t1-1/0/0:0.0;
                 
interface lo0.1;               

route-distinguisher 10.254.71.51:100;
vrf-import VPNA-import;
vrf-export VPNA-export;


protocols {


ospf {
export bgp-to-ospf;


area 0.0.0.0 {
interface t1-1/0/0:0.0;
interface lo0.1;
}


}




                     
pim { 
                 



dense-groups {
229.0.0.0/8;
}


                     
vpn-group-address 239.1.1.1;                   



rp {


static {
address 10.254.245.91;
}


}




interface t1-1/0/0:0.0 {
mode sparse-dense;
version 2;
}




                       
interface lo0.1 {                     

mode sparse-dense;
version 2;
}


}


}


}


}

Router CE1



[edit]
protocols {


pim {


dense-groups {
229.0.0.0/8;
}




                   
rp {    
            



local {
address 10.254.245.91;
}


}




interface all {
mode sparse-dense;
version 2;
}




interface fxp0.0 {
disable;
}


}


}

[Contents] [Prev] [Next] [Index] [Report an Error]