[an error occurred while processing this directive][an error occurred while processing this directive]

Example: Configuring Selective Provider Tunnels Using Wildcards

With the (*,G) and (*,*) S-PMSI, a customer multicast join message can match more than one S-PMSI. In this case, a customer multicast join message is bound to the longest matching S-PMSI. The longest match is a (S,G) S-PMSI, followed by a (*,G) S-PMSI, and a (*,*) S-PMSI, in that order.

Consider the following configuration:

routing-instances { vpna {provider-tunnel {selective {wildcard-group-inet {wildcard-source {rsvp-te {label-switched-path-template {sptnl1;}}}}group 224.1.1.0/24 {wildcard-source {rsvp-te {label-switched-path-template {sptnl2;}}}source 10.1.1/24 {rsvp-te {label-switched-path-template {sptnl3;}}}}}}}}

For this configuration, the longest-match rule works as follows:

  • A customer multicast (10.1.1.1, 224.1.1.1) join message is bound to the sptnl3 S-PMSI autodiscovery route.
  • A customer multicast (10.2.1.1, 224.1.1.1) join message is bound to the sptnl2 S-PMSI autodiscovery route.
  • A customer multicast (10.1.1.1, 224.2.1.1) join message is bound to the sptnl1 S-PMSI autodiscovery route.

When more than one customer multicast route is bound to the same wildcard S-PMSI, only one S-PMSI autodiscovery route is created. An egress PE router always uses the same matching rules as the ingress PE router that advertises the S-PMSI autodiscovery route. This ensures consistent customer multicast mapping on the ingress and the egress PE routers.


Published: 2010-04-27

[an error occurred while processing this directive]