Visibility Solution (Visibility Skill)

XCO supports several network packet broker devices as part of the visibility solution to provide centralized device and policy management.

Although devices have different functionality and different configuration methods, XCO seamlessly interacts with all supported devices for simplified management.

XCO managed objects work together to accomplish packet broker functions. You can configure these objects from the user interface. For more information, see Packet Broker Functions.
Table 1. Managed objects
Object Description
Ports and port channels The interfaces on which traffic enters and exits a device. You can associate ports and port channels with ingress groups and egress.

For more information, see Ports and Port Channels.

Egress A port or port channel that you associate with an egress policy, which identifies the actions to take on egress traffic.

For more information, see Create an Egress for Devices.

Egress group A set of interfaces and ports on which traffic is forwarded after a policy is applied.

For more information, see Create an Egress Group.

Ingress group A collection of ports, port channels, and tunnels on which monitored traffic is received. You can select several actions to perform on the incoming traffic and you can associate the ingress group with an ingress policy.

For more information, see Ingress Groups.

Policy rule matches The parts of a packet header that a rule targets, such as the source port or the payload length. One or more rules constitute a match. You associate matches with ingress or egress policies.

For more information, see Policy Rule Matches.

Ingress policy (or route map) The actions to apply to inbound packets. You can associate policy rule matches and egress groups, and select other actions such as packet slicing and scope shift.

For more information, see Create an Ingress Policy for a Device.

Egress policy (or listener policy) The actions to apply to outbound packets. You can associate policy rule matches and select other actions such as packet slicing and header stripping.

For more information, see Create an Egress Policy for a Device.

Note: Applies to 9920 devices only.
User-defined access list (UDA) The UDA profiles for SLX and MLX devices.

For more information, see UDA Profiles.

Transport tunnel termination and encapsulation The GRE or ERSPAN tunnels to associate with ingress groups or egress.

For more information, see Tunnels.

Note: Applies to 9920 devices only.
Quality of Service (QoS) The QoS configuration is used on 9920 devices to manage traffic delivery.

For more information, see Quality of Service.

Mirrors A copy of the egress port traffic on 9920 is forwarded to the configured mirror destination port.

For more information, see Mirrors.