MPLS and RSVP
7450 ESS MPLS Guide Page 51
RSVP LSP Statistics
This feature provides the following counters:
• Per forwarding class forwarded in-profile packet count
• Per forwarding class forwarded in-profile byte count
• Per forwarding class forwarded out of profile packet count
• Per forwarding class forwarded out of profile byte count
The counters are available for an RSVP LSP at the egress datapath of an ingress LER and at the
ingress datapath of an egress LER. No LSR statistics are provided.
This feature is supported on IOM-3 and requires chassis mode D.
P2MP RSVP-TE LSP Statistics
This feature provides the following counters for a RSVP P2MP LSP instance:
• Per forwarding class forwarded in-profile packet count.
• Per forwarding class forwarded in-profile byte count.
• Per forwarding class forwarded out of profile packet count.
• Per forwarding class forwarded out of profile byte count.
The above counters are provided for the following LSR roles:
1. At ingress LER, a set of per P2MP LSP instance counters for packets forwarded to the
P2MP LSP instance without counting the replications is provided. In other words, a
packet replicated over multiple branches of the same P2MP LSP instance will count once
as long as at least one LSP branch forwarded it.
2. At BUD LSR and egress LER, per ILM statistics are provided. These counters will
include all packets received on the ILM, whether they match a L2/L3 MFIB record or not.
ILM stats will work the same way as for a P2P LSP. In other words, they will count all
packets received on the primary ILM, including packets received over the bypass LSP.
When MBB is occurring for an S2L path of an RSVP P2MP LSP, paths of the new and old
S2L will both receive packets on the egress LER. Both packets are forwarded to the fabric
and outgoing PIM/IGMP interfaces until the older path is torn down by the ingress LER.
In this case, packet duplication should be counted.
3. No branch LSR statistics are provided.
To Next Page
Loading...
