HP 6125G HP 6125G & 6125G/XG Blade Switches ACL and QoS Configuration - Page 65

Configuring traffic redirecting, Configuration restrictions and guidelines, Configuration procedure

Get HP 6125G PDF manuals and user guides View all HP 6125G manuals
Add to My Manuals
Save this manual to your list of manuals

Page 65 highlights

Configuring traffic redirecting Traffic redirecting is the action of redirecting the packets matching the specific match criteria to a certain location for processing. The following redirect actions are supported: • Redirecting traffic to the CPU-redirects packets that require processing by the CPU to the CPU. • Redirecting traffic to an interface-redirects packets that require processing by an interface to the interface. Note that this action applies to only Layer 2 packets, and the target interface must be a Layer 2 interface. • Redirecting traffic to the next hop-redirects packets that require processing by an interface to the interface. This action only applies to Layer 3 packets. Configuration restrictions and guidelines • The actions of redirecting traffic to the CPU, redirecting traffic to an interface, and redirecting traffic to the next hop are mutually exclusive with each other in the same traffic behavior. • A QoS policy with traffic redirecting actions can be applied to only the inbound direction of a port, VLAN, or all ports. • You can use the display traffic behavior user-defined command to view the traffic redirecting configuration. Configuration procedure To configure traffic redirecting: Step Command Remarks 1. Enter system view. system-view N/A 2. Create a class and enter class view. traffic classifier tcl-name [ operator { and | or } ] N/A 3. Configure match criteria. if-match match-criteria N/A 4. Return to system view. quit N/A 5. Create a behavior and enter behavior view. traffic behavior behavior-name N/A redirect { cpu | interface interface-type 6. Configure a traffic redirecting action. interface-number | next-hop { ipv4-add1 [ ipv4-add2 ] | ipv6-add1 [ interface-type interface-number ] [ ipv6-add2 [ interface-type interface-number ] ] } } N/A 7. Return to system view. quit N/A 8. Create a policy and enter policy view. qos policy policy-name N/A 59

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
59
Configuring traffic redirecting
Traffic redirecting is the action of redirecting the packets matching the specific match criteria to a certain
location for processing.
The following redirect actions are supported:
•
Redirecting traffic to the CPU
—redirects packets that require processing by the CPU to the CPU.
•
Redirecting traffic to an interface
—redirects packets that require processing by an interface to the
interface. Note that this action applies to only Layer 2 packets, and the target interface must be a
Layer 2 interface.
•
Redirecting traffic to the next hop
—redirects packets that require processing by an interface to the
interface. This action only applies to Layer 3 packets.
Configuration restrictions and guidelines
•
The actions of redirecting traffic to the CPU, redirecting traffic to an interface, and redirecting traffic
to the next hop are mutually exclusive with each other in the same traffic behavior.
•
A QoS policy with traffic redirecting actions can be applied to only the inbound direction of a port,
VLAN, or all ports.
•
You can use the
display traffic behavior user-defined
command to view the traffic redirecting
configuration.
Configuration procedure
To configure traffic redirecting:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Create a class and enter class
view.
traffic classifier
tcl-name
[
operator
{
and
|
or
} ]
N/A
3.
Configure match criteria.
if-match
match-criteria
N/A
4.
Return to system view.
quit
N/A
5.
Create a behavior and enter
behavior view.
traffic behavior
behavior-name
N/A
6.
Configure a traffic redirecting
action.
redirect
{
cpu
|
interface
interface-type
interface-number
|
next-hop
{
ipv4-add1
[
ipv4-add2
] |
ipv6-add1
[
interface-type
interface-number
] [
ipv6-add2
[
interface-type
interface-number
] ] } }
N/A
7.
Return to system view.
quit
N/A
8.
Create a policy and enter
policy view.
qos policy
policy-name
N/A