Mirror services

Note:

SR tunnels for mirror services are not supported on 7210 SAS platforms.

The user can configure a spoke-SDP bound to an SR tunnel to forward mirrored packets from a mirror source to a remote mirror destination. In the configuration of the mirror destination service at the destination node, the remote-source command must use a spoke-SDP with a VC-ID that matches the VC-ID configured in the mirror destination service at the mirror source node. The far-end option is not supported with an SR tunnel.

Use the following syntax to configure a mirror source node.

config mirror mirror-dest service-id
        no spoke-sdp <sdp-id:vc-id> 
        spoke-sdp <sdp-id:vc-id> [create]
            egress
                vc-label <egress-vc-label>

Note:

sdp-id matches an SDP that uses an SR tunnel.
For vc-label, both static and T-LDP egress VC labels are supported.

Use the following syntax to configure a mirror destination node.

configure mirror mirror-dest service-id remote-source
        spoke-sdp <SDP-ID>:<VC-ID> create <-- VC-ID matching that of spoke-sdp configured in mirror destination context at mirror source node.
            ingress
                vc-label <ingress-vc-label> <--- optional: both static and t-ldp ingress vc label are supported.
            exit
            no shutdown
        exit
    exit

Note:

The far-end command in the config>mirror>mirror-dest>remote-source context is not supported with SR tunnels at a mirror destination node; the user must reference a spoke-SDP using a segment routing SDP coming from a mirror source node.
For vc-label, both static and T-LDP ingress VC labels are supported.