Rule and Functionality Mapping

Extreme Visibility Manager supports multiple devices, which have different functions and configurations related to traffic direction.

The following tables describe how Visibility Manager configuration, policies, and header modification tasks map to the same features on supported devices.

Key for the abbreviations in the following tables:

MLX to Visibility Manager mapping

Table 1. Rule mapping
Rule MLX path XVM path
Policies per device
Create a policy structure for every route-map name. Index to the policy structure is the route-map name Device[]/route-map[name] /Policy[name]
Create a rule structure under policy for every rm-instance indexed by seq-num Device[]/route-map[name]/rm-instance[seqNum) /Policy[name]<ingress>/Rule (SeqNum)
For every route-map stanza, a set operation can be mapped to a rule action Device[]/route-map[name]/rm-instance[seqNum)/action /Policy[name]<ingress>/Rule (SeqNum)/action
Each route-map can have multiple match criteria on an ACL level related to Layer 2 and Layer 3 headers Device[]/route-map[name]/rm-instance[seqNum)/'X'acl /Policy[name]<ingress>/Rule(SeqNum)/X(l2/ipv4/ipv6)
Device[]/route-map[name]/rm-instance[seqNum)/'X'acl/match /Policy[name]/Rule (SeqNum)/X/match
Device[]/route-map[name]/rm-instance[seqNum)/'X'acl/action /Policy[name]<ingress>/Rule (SeqNum)/X/action
Interfaces per device
Bind policies to interfaces Device[]/Slots[]/Device-id[]/Ports[]/Policy /ingress/Policy bind[name]
Port channels per device
Members of VLANS that are part of a route-map's nexthop are scanned. If port channels are present with load-balancing, apply the same to port channels in the Visibility Manager model. Device[]/vlans[]/vlan/<load-balancing> /egress/Port-channel[]
Table 2. Advanced rule mapping for global features
MLX I MLX E XVM I XVM E Rule MLX path XVM path
802.1BR header stripping: Strip the 802.1BR header from ingress traffic and send it for processing
Supported Not supported Supported Supported Add the decap traffic type for 802.1BR on the ingress port Device[]/Slots[]/Device-id[]/Ports[]/<802.1bR strip> /ingress[]/Traffic/TrafficDecap<802.1BR>
802.1BR header bypass: Bypass the 802.1BR header and perform inner header lookup
Supported Not supported Supported Supported Add the bypass traffic type for 802.1BR on the ingress port Device[]/Slots[]/Device-id[]/Ports[]/<802.1bR bypass> /ingress[]/Traffic/TrafficBypass<802.1BR>
VN-tag header stripping: Strip the VN-tag from ingress traffic and send it for processing
Supported Not supported Supported Supported Add the decap traffic type for the VN-tag on the ingress port Device[]/Slots[]/Device-id[]/Ports[]/<vn-tag strip> /ingress[]/Traffic/TrafficDecap<vn-tag>
VN-tag header bypass: Bypass the VN-tag header and perform inner header lookup
Supported Not supported Supported Supported Add the bypass traffic type for the VN-tag on the ingress port Device[]/Slots[]/Device-id[]/Ports[]/<vn-tag bypass> /ingress[]/Traffic/TrafficBypass<VN-tag>
VN-tag and 802.1BR preservation: TBD
Supported Not supported Supported Supported
VxLAN header stripping: Strip VxLAN from ingress traffic and send it for processing
Supported Not supported Supported Supported Add the decap traffic type for the VxLAN on the ingress port Device[]/Slots[]/Device-id[]/Ports[]/vxlan strip> /ingress[]/Traffic/TrafficDecap<vxlan>
NVGRE header stripping: Strip NVGRE from ingress traffic and send for processing
Supported Not supported Supported Supported Add the decap traffic type for NVGRE on the ingress port Device[]/Slots[]/Device-id[]/Ports[]/<nvgre strip> /ingress[]/Traffic/TrafficDecap<nvgre>
GTP de-encapsulation: Remove the outer IP, the outer UDP header, and the GTP header from GTP-U packets
Supported Not supported Supported Supported Add the decap traffic type for GTP on the ingress port Device[]/Slots[]/Device-id[]/Ports[]/<gtp decap> /ingress[]/Traffic/TrafficDecap<gtpDecap>
Packet slicing (packet truncation)
Not supported Supported Supported Supported Add packet slicing for traffic on the egress port Device[]/Slots[]/Device-id[]/Ports[]<egress>/<gtp decap> /egress[]/Traffic/<packetSlicing>

Extreme 9920 to Visibility Manager mapping

Table 3. Rule mapping
Rule 9920 path XVM path
Ingress port bind
Device traffic parameters are mapped to the Visibility Manager model Device[]/ingress-group/Traffic /ingress/Traffic
Copy all ingress direction policies per interface Device[]/ingress-group/rm-bind /ingress/Policy-bind
Ingress policies
Create a route-map and subsidiaries, and copy all ingress policies Device[]/route-map[name]/rm-instance[seqNum) /Policy[name]<ingress>/Rule[SeqNum]
Device[]/route-map[name]/rm-instance[seqNum)/action /Policy[name]<ingress>/Rule[SeqNum]/action
Device[]/route-map[name]/rm-instance[seqNum)/'X'acl /Policy[name]<ingress>/Rule[SeqNum]/X(l2/ipv4/ipv6)
Device[]/route-map[name]/rm-instance[seqNum)/L2acl/ipv4acl/'X'acl/match /Policy[name]<ingress>/Rule[SeqNum]/X/match
Device[]/route-map[name]/rm-instance[seqNum)/L2acl/ipv4acl/'X'acl/action /Policy[name]<ingress>/Rule[SeqNum]/X/action
Egress policies
Create a route-map and subsidiaries, and copy all listener policies Device[]/Listener-policy[name]/lp-instance[seqNum) /Policy[name]<Egress>/Rule[SeqNum]
Device[]/Listener-policy[name]/lp-instance[seqNum)/action /Policy[name]<Egress>/Rule[SeqNum]/action
Device[]/Listener-policy[name]/lp-instance[seqNum)/'X'acl /Policy[name]<Egress>/Rule[SeqNum]/X(l2/ipv4/ipv6)
Device[]/Listener-policy[name]/lp-instance[seqNum)/L2acl/ipv4acl/'X'acl/match /Policy[name]<Egress>/Rule[SeqNum]/X/match
Device[]/Listener-policy[name]/lp-instance[seqNum)/L2acl/ipv4acl/'X'acl/action /Policy[name]<Egress>/Rule[SeqNum]/X/action
Copy all egress direction policies per interface device/egress-group/egress/Listener-Policy[] /egress[]/Policy<egress>-bind[]
Egress encapsulation
For the egress direction, copy encap to all egress port policies device/egress-group/egress/TrafficEncap /egress/Traffic<encap>
Table 4. Advanced rule mapping for global features
9920 I 9920 E XVM I XVM E Rule 9920 path
802.1 BR header stripping
Not supported Supported Supported Supported Map the listener-policy action to the egress policy rule action of the XVM model Device[]/Slots[]/Device-id[]/Ports[]/<802.1bR strip>
VN-tag header stripping
Not supported Supported Supported Supported Map the listener-policy action to the egress policy rule action of the XVM model Device[]/Listener-policy[name]/lp-instance[seqNum)/action<vn-tag strip>
VxLAN header stripping
Supported Not supported Supported Supported Map the ingress-group VxLAN strip to the ingress traffic decap of the XVM model Device[]/ingress-group/Ports[]/Traffic/TrafficDecap<vxlan>
NVGRE header stripping
Supported Not supported Supported Supported Map the ingress-group VxLAN strip to the ingress traffic decap of the XVM model Device[]/ingress-group/Ports[]/Traffic/TrafficDecap<nvgre>
GTP decapsulation
Supported Not supported Supported Supported Map the ingress-group VxLAN strip to the ingress traffic decap of the XVM model Device[]/ingress-group/Ports[]/Traffic/TrafficDecap<gtp>
Packet slicing
Supported Supported Supported Supported Truncation is supported in ingress or egress depending on configuration. Map to the XVM model Device[]/route-map[name]/rm-instance[seqNum)/action<truncate>

or

Device[]/Listener-policy[name]/lp-instance[seqNum)/action<truncate>

SLX to Visibility Manager mapping

Table 5. Rule mapping
Rule SLX path XVM path
Policies per device
Create a policy structure for every route-map name. Index to the policy structure is the route-map name Device[]/route-map[name] /Policy[name]
Create a rule structure under policy for every rm-instance indexed by seq-num Device[]/route-map[name]/rm-instance[seqNum) /Policy[name]<ingress>/Rule (SeqNum)
For every route-map stanza, a set operation can be mapped to a rule action Device[]/route-map[name]/rm-instance[seqNum)/action /Policy[name]<ingress>/Rule (SeqNum)/action
Each route-map can have multiple match criteria on an ACL level related to Layer 2 and Layer 3 headers Device[]/route-map[name]/rm-instance[seqNum)/'X'acl /Policy[name]<ingress>/Rule(SeqNum)/X(l2/ipv4/ipv6)
Device[]/route-map[name]/rm-instance[seqNum)/'X'acl/match /Policy[name]/Rule (SeqNum)/X/match
Device[]/route-map[name]/rm-instance[seqNum)/'X'acl/action /Policy[name]<ingress>/Rule (SeqNum)/X/action
Interfaces per device
Bind policies to interfaces Device[]/Ports[]/npb_bind /ingress/Policy bind[name]
Table 6. Advanced rule mapping for global features
SLX I SLX E XVM I XVM E Rule SLX path XVM path
802.1BR header stripping: Strip the 802.1BR header from ingress traffic and send it for processing
Supported Not supported Supported Supported Add the decap traffic type for 802.1BR on the ingress port Device[]/Ports[]<ingress>/<802.1bR strip> /ingress[]/Traffic/TrafficDecap<802.1BR>
VN-tag header stripping: Strip the VN-tag from ingress traffic and send it for processing
Supported Not supported Supported Supported Add the decap traffic type for the VN-tag on the ingress port Device[]/Slots[]/Device-id[]/Ports[]/<vn-tag strip> /ingress[]/Traffic/TrafficDecap<vn-tag>
VxLAN header stripping: Strip VxLAN from ingress traffic and send it for processing
Supported Not supported Supported Supported Add the decap traffic type for the VxLAN on the ingress port Device[]/Slots[]/Device-id[]/Ports[]/vxlan strip> /ingress[]/Traffic/TrafficDecap<vxlan>
NVGRE header stripping: Strip NVGRE from ingress traffic and send for processing
Supported Not supported Supported Supported Add the decap traffic type for NVGRE on the ingress port Device[]/Slots[]/Device-id[]/Ports[]/<nvgre strip> /ingress[]/Traffic/TrafficDecap<nvgre>
GTP de-encapsulation: Remove the outer IP, the outer UDP header, and the GTP header from GTP-U packets
Supported Not supported Supported Supported Add the decap traffic type for GTP on the ingress port Device[]/Slots[]/Device-id[]/Ports[]/<gtp decap> /ingress[]/Traffic/TrafficDecap<gtpDecap>
MPLS stripping: Strip the outer headers (MPLS labels, outer L2, and the pseudo-wire control word) to prepare the inner headers and frame payload for forwarding and processing
Supported Not supported Supported Supported Add the decap traffic type for MPLS on the ingress port Device[]/Slots[]/Device-id[]/Ports[]/<mpls strip> /ingress[]/Traffic/TrafficDecap<mpls strip>