Using Access Control Lists (ACLs)
•Specify the default
•Send the packet to the null interface (null0).
HP’s PBR routing is based on standard and extended ACLs and
Configuring PBR
To configure PBR:
•Configure ACLs that contain the source IP addresses for the IP traffic to which you want to apply PBR.
•Configure a route map that matches on the ACLs and sets route information.
•Apply the route map globally or to individual interfaces.
NOTE: All the procedures in the following sections are for the CLI.
Configure the ACLs
PBR uses route maps to change the routing attributes in IP traffic. This section shows an example of how to configure a standard ACL to identify the source
To configure a standard ACL to identify a source
HP9300(config)#
The command in this example configures a standard ACL that permits traffic from
NOTE: Do not use an access group to apply the ACL to an interface. Instead, use a route map to apply the ACL globally or to individual interfaces for PBR, as shown in the following sections.
Syntax: [no]
or
Syntax: [no]
Syntax: [no]
Syntax: [no]
The <num> parameter is the access list number and can be from 1 – 99.
The deny permit parameter indicates whether packets that match a policy in the access list are denied (dropped) or permitted (forwarded).
NOTE: If you are configuring the ACL for use in a route map, always specify permit. Otherwise, the routing switch drops the traffic instead of further processing the traffic using the route map.
The
NOTE: To specify the host name instead of the IP address, the host name must be configured using the HP device’s DNS resolver. To configure the DNS resolver name, use the ip dns
The <wildcard> parameter specifies the mask value to compare against the host address specified by the
3 - 25