Vision Edge 50 (E50)
Case Studies
This case study looks at one example of how to use Custom Offset Filtering feature on the Vision Edge 50 (E50). To learn the many other ways to use this feature, see the Custom Dynamic / Offset Filtering chapter in the Vision E50 User Guide. The E50 has some limitations, but it also has some advantages that the other Vision Network Packet Brokers (NPBs) do not have.
COF works a little differently on the Vision Edge 50 (E50) platform than it does on other NPBs. On other NPBs, you can match on two IPv6 addresses for MPLS, one for each of the two field sets. That’s because they have 16 bytes available for each field set, for 32 bytes total. The E50 has just 16 bytes available in Field Set 2. Field Set 1 only has 14 bytes available, not enough for a full IPv6 address. So you are limited to one IPv6 address.
On the other hand, the E50 has the advantage of having byte pools available for GTP and VxLAN that are independent of MPLS. So you can use Field Set 1 for GTP and VxLAN filtering and use Field Set 2 for MPLS filtering on IPv6 addresses. That is the purpose of this case study, to show how to do that. It also clarifies what you cannot do with the E50.