Packet forwarding and filtering are core features of Extreme 9920 software. To properly configure and use the Extreme 9920 effectively, you need a good understanding of the various components that configure the packet workflow to monitor your network.
Before you configure any settings, you must create components that monitor and modify packets flowing into and out of the Extreme 9920.
Note
For the purpose of configuration, it is recommended that you adhere to the following configuration order when you create these building blocks. When you have a basic packet workflow in place, modifications to that workflow follow the same order as outlined here.It is important to note the terminology used when discussing packet flow through the 9920. Interfaces that are connected to the network being monitored are termed tap interfaces. Interfaces connected toward the visibility tools are called tool ports. Because tap ports often receive the same traffic types, you create and configure an ingress-group to group the tap interfaces to the same desired route-map.
Likewise, tool ports are configured in an egress, which combines interfaces and any post-processing directives (such as dropping specific packets, removing tunnel or specific headers, adding a VLAN tag, or truncating packet length) by using a listener-policy. In-between the 'ingress-group' and the 'egress' is abstraction layer that connects the two together, the 'egress-group'.
You can configure various actions at each level, and some ould depend on a prior entity existing in the configuration. The examples that are provided are not exhaustive for all possible configurations or parameters. For additional information, see Extreme 9920 Software Command Reference, 21.1.1.0 .