Extreme Networks Px Series - Manual (Page 55)

Px Series Application Switch Installation and Configuration Guide 5-5
Configuring Virtual Services
config pattern-rule “<string>” server-group-name <name>
Pattern rules specify the URL that is being matched and the server group that
should be used to forward traffic for that URL match.
config domain default
config pattern-rule default server-group-name <name>
All layer 7 service definitions require at least a default pattern rule, to define the
“last resort” rule for URL switching. If you use any domain other than
domain* , you
must define a default domain. The default domain can only contain one pattern rule:
the default. These defaults also provide the place to configure cookie and SSL
persistence:
config pattern-rule default server-group-name <name> cookie-name <name>
cookie-type [self | hash | learned]
Cookie-name is the ASCII name of the cookie to search for, and cookie type refers to
the type of cookie-based persistence for the virtual service. Although you configure
cookies for the default domain, the cookie information applies to the entire site. See
Chapter 6 for more information on cookies.
Configuring Traffic Tagging
You can configure a service to tag traffic based on the application or transaction type.
You can then use the tag for QoS, MPLS tunneling, or bandwidth reservation, all
enforced by the L2/3 infrastructure.
You can specify tags for the 802.1p header and the DiffServ code point (DSCP) in the
TCP header. You can tag either or both of these fields. You can specify different tags for
traffic towards the server and traffic towards the network.
• For level 4 services, configure the service itself for tagging:
config service vip <addr> port <port> proto tcp L4 <tag spec>
• For level 7 services, create rules to apply the tags, so that when a session is initiated,
the flow is tagged with the specified values.
config service vip <addr> port <port> proto tcp L7 class http
config domain name <domain>
config pattern-rule [<url>|default] server-group-name <grp>
<tag spec>
Table 5-1 shows the possible tag specifications.