PIM on a subscriber group interface allows for SAP-level replication over an ESM Group interface by establishing PIM adjacency to a downstream router. Figure: PIM interface on IES subscriber group interface depicts the model:
On an IES subscriber-interface, an Ethernet SAP is configured (LAG or physical port). On the SAP, a static-host is configured for connectivity to downstream Layer 3 aggregation devices (including PIM adjacency) while multiple default-hosts can be configured for subscriber traffic. Single SAP with a single static-host per group interface is supported to establish PIM adjacency on a subscriber group interface. Both IPv4 PIM ASM and SSM are supported.
Feature restrictions:
Only IPv4 PIM is supported with a single static host used to form a PIM interface under a group interface. Using multiple hosts or non-static hosts is not supported. Configuring IPv6-related parameters in config>router>pim>interface group-ift is not blocked, but takes no effect.
config>router>pim>apply-to configuration does not apply to PIM interfaces on IES subscriber group interfaces.
PIM on group interfaces is not supported in VPRN context.
Extranet is not supported.
Locally attached receivers are not supported (no IGMP/MLD and PIM mix in OIF list).
Default anti-spoofing must be configured (IP+MAC).
A subscriber profile with pim-policy enabled cannot combine with the following policies (config>subscr-mgmt>sub-prof):
- no host-tracking
- apply a host tracking policy
- no igmp-policy
- apply an IGMP policy
- no mld-policy
- apply an MLD policy
- no nat-policy
- apply a NAT policy
- no sub-mcac-policy
- apply a subscriber MCAC policy (MCAC policy can be used when configured in PIM interface context)
The feature is supported on IOM3-XP or newer line cards. When enabling the feature on older hardware, joins may be accepted and an outgoing interface may be created for the group, but traffic is not sent out on egress because no OIF is created in forwarding.