Managing subnet side rules
You configure subnet side rules in the Editing Appliance Configuration: <hostname>, Subnet Side Rules page.
You need to configure subnet side rules to support VSP and Flow Export on a virtual in-path deployment.
Subnet side rules enable you to configure subnets as LAN-side subnets or WAN-side subnets for a virtual in-path SteelHead appliance. The subnet side rules determine whether traffic originated from the LAN or the WAN-side of the SteelHead appliance based on the source subnet. You must configure subnets on each SteelHead appliance in a virtual in-path configuration, as the subnets for each will likely be unique.
With subnet side rules in place, RiOS can send incoming packets to the correct VSP VNIs for VVSP, and, a virtual in-path SteelHead can use flow export collectors such as NetFlow to analyze nonoptimized or passed through traffic correctly. Otherwise, the SteelHead appliance can’t discern whether the traffic is traveling from the LAN to the WAN or in the opposite direction. This can result in over-reporting traffic in a particular direction or for a particular interface.
FakeIndex is necessary for correct optimized traffic reporting. For details, see the SteelHead Deployment Guide.
You can’t delete the default rule, Default, which optimizes all remaining WAN-side traffic that hasn’t been selected by another rule. This rule is always listed last.
This page applies to SteelHead.