Technical data

Brocade ServerIron ADX Advanced Server Load Balancing Guide 75

53-1003441-01

Policy-based caching

Policy-based caching allows configuration of a separate set of filters for each cache group. Users

can use access lists to define a set of filters and apply these to different cache groups.

Creating a set of filters using access lists

You first must create a set of filters using the access-list command at the CLI. You can use regular

or extended access lists.

Applying access lists to cache group

Apply the access list to the desired cache group as follows. In the example, the filters defined in

access list 1 are used for cache-group 1.

ServerIronADX(config)#server cache-group 1

ServerIronADX(config-tc-1)#filter-acl 1

ServerIronADX(config-tc-1)#exit

In the previous example, the filters defined in access list 2 are used for cache-group 2.

ServerIronADX(config)#server cache-group 2

ServerIronADX(config-tc-2)#filter-acl 2

ServerIronADX(config-tc-2)#exit

Syntax: filter-acl { Access-List-ID | Access-List-Name }

NOTE

Although IPv4 and IPv6 ACLs are supported, an IPv4 ACL can only be bound to an IPv4 cache group

and an IPv6 ACL can only be bound to an IPv6 cache group.

Configuring default cache groups

You can configure a default cache group. If the traffic does not match the ACL IDs for any of the

cache groups, then it is sent to the default cache group. You do not need to explicitly associate an

ACL ID with the default cache group; the behavior of the default cache group is "permit any any".

ServerIronADX(config)#server cache-group 3

ServerIronADX(config-tc-1)#cache-name Cache-Server1

ServerIronADX(config-tc-1)#cache-name Cache-Server2

ServerIronADX(config-tc-1)#default-group

ServerIronADX(config-tc-1)#exit

Syntax: default-group

NOTE

If default cache group is not configured or if no cache servers are associated with the default cache

group, then the traffic is sent to the Internet if the traffic does not match any of the group ACLs.