Radware_2011_技术培训汇.ppt

A configuration where farms associated with the same Layer 4 Policy VIP are associated with different segments is not supported. It is your responsibility to ensure that such configuration conflicts are avoided. Similarly, configurations where servers and the Virtual IP do not belong to the same segment are not supported. You can also assign a NHR to each segment, similar to the way Next Hop Routers can be associated with Virtual IPs. Segmentation is a global AppDirector feature and therefore can only be configured globally. All the segments must be of the same type: either port segments or VLAN Tag segments. AppDirector default gateway can only belong to the default segment. Device management can only be performed via a port/VLAN tag that belongs to the default segment. A configuration where farms associated with the same Layer 4 Policy VIP are associated with different segments is not supported. You need to ensure that these configuration conflicts are avoided. Similarly, configurations where servers and the Virtual IP do not belong to the same segment are not supported. Segmentation by physical ports cannot be used when the same physical port belongs to multiple segments and is used with Delayed Binding (Layer 7 policies, Session ID Persistency, SYN Flood Protection, etc). Each host or router handling a packet examines the Destination Address in the IP header, computes the next hop that will bring the packet one step closer to its destination, and delivers the packet to the next hop, where the process is repeated. A Next Hop Router (NHR) is a network element used for outbound traffic in AppDirector Multi Homing configurations. NAT addresses can be associated with Next Hop Routers (NHRs), similar to the way VIPs are associated with NHRs. The NHR Table window enables you to list the devices next hop routers. All Next-Hop Routers connected to the AppDirector are defined in the NHR table. NHRs are associated with the Virtual IP addresses of the device using th