-
CPT supports only
local span and not remote span. Therefore, the destination port or channel
group can be any port or channel group on the same card or on different card on
the same node.
-
A port on the CPT
50 fanned out from a fabric card can be a destination span port only if the
source span port is also on the same CPT 50.
-
A span source port
on a CPT 50 fanned out from a line card and a span destination port on another
CPT 50 fanned out from another line card is not supported. If traffic is
affected due to this issue, remove the span and reload the line card that has
the fanout of the destination CPT 50 span.
-
For egress span of
the line card, only Ethernet Virtual Private LAN (EVPLAN) traffic is supported.
The operations, administration, and maintenance (OAM) control traffic is not
replicated.
-
The span
destination can only be a port or a channel group and not an EFP. The span
source can be a port, channel group, or an EFP.
-
If a channel group
is selected as a destination port, the member ports of the channel group cannot
be selected as destination ports.
-
The egress span
for the line card is supported only for point-to-multipoint traffic.
-
The EFP, Resilient
Ethernet Protocol (REP), Ethernet in the first mile (EFM) loopback, Link
Aggregation Control Protocol (LACP), and Quality of Service (QoS) cannot be
configured on the span destination port.
-
For port span, two
egress span destinations and three ingress span destinations for each card is
supported.
-
For EFP span, one
egress span destination for each card is supported.
-
For EFP span,
three ingress span destinations for each card is supported. When you add the
fourth destination port to the span, the traffic is not received on the three
destination ports.
-
The maximum egress
span bandwidth traffic is 10 Gbps for each card; the maximum egress span
bandwidth traffic for the line card is 16 Gbps for the CPT system.
-
CPT can monitor up
to 256 EFPs for each fabric card, line card (ingress), and CPT 50 panel.
-
CPT can monitor up
to 150 EFPs in the entire CPT system for line card egress span.
-
If there are
multiple source ports, the traffic sent by each source port is not equally
shared on the destination port.
-
If other services are available on a port, a service with default
encap cannot be created on that port and vice-versa
-
On MPLS-TP port, no service can be created.
-
If QoS policy is attached to a port, span destination port cannot be
configured on that.
-
If the service is tagged, MVR cannot be enabled on that.
-
If a port is MPLS-TP core port, span destination port cannot be
configured on that.
-
If a port is FOG port, span destination port cannot be configured on
that.
-
A port that has egress policy in the port-channel as a member-link
cannot be associated.