Ingress P2Mp Path Management On Iom-2 - Alcatel-Lucent 7450 Manual
Ethernet service switch
Hide thumbs
Also See for 7450:
- Quality of service manual (912 pages) ,
- Configuration manual (778 pages) ,
- Basic system configuration manual (576 pages)
Table of Contents
Advertisement
MPLS and RSVP
Ingress P2MP Path Management on IOM-2
The following procedures apply at the ingress data path for packets received from or to be
forwarded to a P2MP LSP at ingress LER, LSR, branch LSR, bud LSR, and egress LER.
On ingress IOM-2, there are 3 multicast paths which are available for forwarding multicast
packets. Each path has a set of multicast queues and a multicast VoQ associated with it. Two paths
are enabled by default, a primary path and a secondary path, and represent the high-priority and
low-priority paths respectively. Each VPLS SAP, access interface, and network interface will have
a set of per forwarding class multicast and/or broadcast queues which are defined in the ingress
QoS policy associated with them. The expedited queues will be attached to the primary path while
the non-expedited queues will be attached to the secondary path.
When IMPM is disabled, packets of P2MP LSP arriving on a network interface will be queued in
that interface queue corresponding to the forwarding class of the packet.
When the user enables IMPM on the ingress MDA, a third multicast path, referred to as ancillary
path, is added on the ingress IOM-2. This path reuses unused capacity from the unicast paths. The
high-priority and low-priority paths are renamed as primary and secondary paths respectively.
A VPLS snooped packet or a PIM routed packet is managed by IMPM if it matches a <*,G> or a
<S,G> multicast record in the ingress IOM-2 forwarding table and IMPM is enabled on the ingress
MDA where the packet is received. The user enables IMPM on the ingress MDA data path using
the config>card>mda>ingress>mcast-path-management command.
A P2MP LSP packet which matches a multicast record is also managed by IMPM on ingress IOM-
2 and is thus distributed to one of the primary, ancillary, or secondary path according to the
congestion level of the paths and the preference of the packet's multicast flow as configured in the
multicast info policy 2.
7450 ESS MPLS Guide
Page 161
Advertisement
Table of Contents
