Brocade Communications Systems ServerIron ADX 12.4.00 Service Manual Page 186

  • Download
  • Add to my manuals
  • Print
  • Page
    / 188
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 185
ServerIron ADX Firewall Load Balancing Guide 175
53-1002436-01
Denying FWLB for specific applications
A
DRAFT: BROCADE CONFIDENTIAL
ServerIron ADX A has an extended ACL at the firewall group configuration level that denies
FWLB for packets addressed to destination TCP port 80.
ServerIron ADX B has an extended ACL at the firewall group configuration level that denies
FWLB for packets from source TCP port 80.
Notice that the routers use default routes to send traffic to a specific firewall. However, the default
routes do not necessarily determine the firewall to which the ServerIron ADX sends the traffic.
When the ServerIron ADX performs load balancing for a packet and selects a firewall for the traffic,
the ServerIron ADX also changes the destination MAC address of the packet to the MAC address of
the firewall selected by the ServerIron ADX. For example, in
Figure 25, if ServerIron ADX A selects
firewall FW2 for a packet, the ServerIron ADX changes the destination MAC address of the packet
to abcd.4321.34e1, the MAC address of firewall FW2’s interface with ServerIron ADX
A. As a result,
even if the WAN access router addresses a packet to the MAC address for firewall FW1, the
ServerIron ADX does not send the packet to firewall FW1 unless the load balancing mechanism
selects that firewall. In either case, the ServerIron ADX changes the destination MAC address of the
packet.
If you want to ensure that all packets for an application go to a specific firewall (as specified in the
default route on the router), you must deny FWLB service for that application. For example, if you
have configured firewall FW1 to collect statistics on HTTP traffic and you therefore want to send all
the HTTP traffic to firewall FW1, you must disable FWLB for HTTP traffic. To disable FWLB for an
application, configure an extended ACL at the firewall group configuration level.
NOTE
When you configure an ACL at the firewall group configuration level, a deny action does not cause
the ServerIron ADX to drop the denied packet. In this type of configuration, a deny action denies
FWLB service for the packet, so that the ServerIron ADX leaves the destination MAC address of the
packet unchanged.
NOTE
This section focuses on using extended ACLs to deny FWLB based on TCP or UDP port. However, you
also can use standard ACLs at the firewall group configuration level to deny FWLB based on IP
address.
Configuration guidelines
Consider the following:
Configure extended ACLs at the firewall group configuration level to deny FWLB for specific
applications.
Configure a permit ACL to allow all applications. Once you configure an ACL, the default action
changes from permit to deny. As a result, if you do not configure the permit ACL for all traffic
types, FWLB is denied for all traffic. Make sure the permit ACL for all traffic is the last ACL, after
all the deny ACLs.
Configure the deny ACLs for each direction of traffic for which you want to deny FWLB. In
Figure 25, configure a deny ACL on ServerIron ADX A to deny FWLB for packets addressed to
destination TCP port 80 (HTTP). To deny FWLB for the return traffic, configure a deny ACL on
ServerIron ADX
B to deny packets from source TCP port 80.
Page view 185
1 2 ... 181 182 183 184 185 186 187 188

Comments to this Manuals

No comments