Você está na página 1de 4

Blog Home | INE Home | Members | Contact Us | Subscribe

Free Resources

View Archives

All Access Pass

CCIE Bloggers

Featured Posts
Share your Expertise Become
an INE Instructor! Read Post

Using Cisco VIRL for CCIE


Preparation Read Post

INEs CCIE RSv5 Expanded


Blueprint Read Post

Search

Posts Tagged policy-map


Sep

15

QoS on the PIX/ASA Part 2:The Modular Policy Framework


Posted by INE Instructor in Advanced Security,CCIE Security,PIX/ASA Firewall

0 Comments

How do you apply most of your QoS mechanisms on a Cisco router? You use the Modular Quality of Service
Command Line Interface (MQC). The approach is similar on the PIX/ASA, but the tool does feature some
important differences. Also, Cisco has renamed the tool to the Modular Policy Framework. One reason for
this is the fact that it is used for more than just QoS. For example, the MPF is also used for application
inspection and Intrusion Prevention configurations on the ASA.
The three steps used by MPF are pretty famous at this point. Here they are:
Step 1: Define the traffic flows that you want to manipulate using what is called a Class Map. Do not confuse
this with a Map Class that you might remember from Frame Relay configurations. A nice analogy for the
Class Map is a bucket that you are pouring the traffic into that you want to manipulate.
Web page converted to PDF with the PDFmyURL PDF creation API!

Search
Submit

Categories
Select Category

CCIE Bloggers
Brian Dennis, CCIEx5 #2210
Routing & Switching
Voice
Security
Service Provider
ISP Dial
Brian McGahan, CCIEx4 #8593,

Step 2: Take those buckets of traffic from Step 1 and define the particular policy that will apply. The structure
used for this is called a Policy Map. An example might be to police Web traffic (defined in a Class Map) to a
particular rate.
Step 3: Assign the Policy Map to an interface or all interfaces on the system using what is called a Service
Policy.
Lets examine the syntax for these various commands.

pixfirewall(config)# class-map ?
configure mode commands/options:
WORD < 41 char

class-map name

type

Specifies the type of class-map

Notice the Class Map syntax includes a type option on the security appliance, the possible types include
inspect, management, and regex and represent the variety of configurations the Modular Policy Framework
can carry out.

CCDE #2013::13
Design
Data Center
Routing & Switching
Security
Service Provider
Mark Snow, CCIEx4 #14073
Data Center
Collaboration
Security
Voice
Petr Lapukhov, CCIEx4 #16379,
CCDE #2010::7
Design
Routing & Switching
Security
Service Provider
Voice

Popular Posts
CCIE Security v5 Blueprint

Something else interesting about the Class Map on the security appliance is the fact that there is no options
for match-any or match-all. This is because on the security appliance you can only have one match
statement. There are exceptions to this, and that is after using either the match tunnel-group or match
default-inspection-traffic commands.
Here you can see the match options on the security appliance to fill these buckets of traffic:

pixfirewall(config-cmap)# match ?
mpf-class-map mode commands/options:
access-list

Match an Access List

any

Match any packet

default-inspection-traffic

Match default inspection traffic:

dscp

Match IP DSCP (DiffServ CodePoints)

flow

Flow based Policy

port

Match TCP/UDP port(s)

precedence
Match IP precedence
Web page converted to PDF with the PDFmyURL PDF creation API!

Update Announced

rtp

Match RTP port numbers

tunnel-group

Match a Tunnel Group

Obviously, a powerful option is the ability to match on an access list, since this allows matching on very
specific criteria, such as well Web traffic requests from a source to a specific destination. Here is an example:

pixfirewall(config)# access-list AL-EXAMPLE permit tcp any host 10.10.10.200 eq www


pixfirewall(config)# class-map CM-EXAMPLE
pixfirewall(config-cmap)# match access-list AL-EXAMPLE

For step 2, we use the Policy Map. There are also types of these components that can be created. Notice
that you are not in Policy Map configuration mode long, you switch immediately to Policy Map Class
configuration mode to get your configuration complete.

pixfirewall(config)# policy-map PM-EXAMPLE


pixfirewall(config-pmap)# class CM-EXAMPLE
pixfirewall(config-pmap-c)# police output 56000 10500

Here you can see the third strep. The Service Policy applies the Policy Map. You can assign the Policy Map
to an interface or all interfaces with the following syntax:

pixfirewall(config)# service-policy PM-EXAMPLE global

Here is a single interface example:

service-policy PM-EXAMPLE interface inside

Notice that a direction is not specified as you would on a router. Notice the direction of policing was actually
specified in the Policy Map.
What happens if there is a global policy and an interface policy? Well the interface policy wins out and
controls the interface.
Web page converted to PDF with the PDFmyURL PDF creation API!

The next blog entry on this subject will focus on the priority queuing tool available on the security appliance.

Tags: asa, classification, mpf, mqc, pix, policy-map

twitter.com/ine

2011 INE, Inc., All Rights Reserved

Web page converted to PDF with the PDFmyURL PDF creation API!

Você também pode gostar