HP 6125XLG R2306-HP 6125XLG Blade Switch ACL and QoS Configuration Guide - Page 76

Configuring traffic redirecting, Configuration procedure

Page 76 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. Configuration procedure To configure traffic redirecting: Step 1. Enter system view. 2. Create a traffic class and enter traffic class view. 3. Configure match criteria. 4. Return to system view. 5. Create a traffic behavior and enter traffic behavior view. 6. Configure a traffic redirecting action. 7. Return to system view. Command Remarks system-view N/A traffic classifier classifier-name [ operator { and By default, no traffic class | or } ] exists. if-match match-criteria By default, no match criteria are configured for a traffic class. For more information about the match criteria, see the if-match command in ACL and QoS Command Reference. quit N/A traffic behavior behavior-name By default, no traffic behavior exists. redirect { cpu | interface interface-type interface-number } quit By default, no traffic redirecting action is configured for a traffic behavior. The actions of redirecting traffic to the CPU and redirecting traffic to an interface are mutually exclusive with each other in the same traffic behavior. The most recent redirecting action configured takes effect. N/A 70

  • 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
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109

70
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.
Configuration procedure
To configure traffic redirecting:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Create a traffic class and
enter traffic class view.
traffic classifier
classifier-name
[
operator
{
and
|
or
} ]
By default, no traffic class
exists.
3.
Configure match criteria.
if-match
match-criteria
By default, no match
criteria are configured for
a traffic class.
For more information
about the match criteria,
see the
if-match
command in
ACL and
QoS Command
Reference
.
4.
Return to system view.
quit
N/A
5.
Create a traffic behavior
and enter traffic behavior
view.
traffic behavior
behavior-name
By default, no traffic
behavior exists.
6.
Configure a traffic
redirecting action.
redirect
{
cpu
|
interface
interface-type
interface-number
}
By default, no traffic
redirecting action is
configured for a traffic
behavior.
The actions of redirecting
traffic to the CPU and
redirecting traffic to an
interface are mutually
exclusive with each other
in the same traffic
behavior. The most recent
redirecting action
configured takes effect.
7.
Return to system view.
quit
N/A