Extreme Visibility Manager (Visibility Manager), a Kubernetes-based microservices application, provides centralized device and policy management as part of the Extreme Visibility solution.
Visibility Manager supports several network packet broker devices. Although devices have different functionality and different configuration methods, Visibility Manager seamlessly interacts with all supported devices for simplified management.
You use Visibility Manager to perform much of the same traffic configuration that you might otherwise perform from the command-line interface of your network packet broker operating system. And then you use Visibility Manager to analyze the traffic for insight into issues such as network usage, load-balancing irregularities, and security threats. For more information, see "Understanding Packet Broker Functions" in Extreme Visibility Manager Administration and User Guide, 6.0.0 .
| Object | Description |
|---|---|
| Ports and port channels | The interfaces on which traffic enters and exits the packet broker device. You can associate ports and port channels with ingress groups and egress. |
| Egress | A port or port channel that you associate with an egress policy, which identifies the actions to take on egress traffic. |
| Egress group | A set of interfaces and ports on which traffic is forwarded after a policy is applied. |
| 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. |
| 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. |
| 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. |
| 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. |
| User-defined access list (UDA) | The rules and matches created for or reconciled from MLX devices. |
| Transport tunnel termination and encapsulation | The GRE or ERSPAN tunnels to associate with ingress groups or egress. |