HP 6125G HP 6125G & 6125G/XG Blade Switches Network Management and Mon - Page 97

Configuring traffic mirroring, Introduction to traffic mirroring

Page 97 highlights

Configuring traffic mirroring Introduction to traffic mirroring Traffic mirroring copies the specified packets to the specified destination for packet analyzing and monitoring. It is implemented through QoS policies. In other words, you define traffic classes and configure match criteria to classify packets to be mirrored and then configure traffic behaviors to mirror packets that fit the match criteria to the specified destination. Traffic mirroring allows you to flexibly classify packets by defining match criteria and obtain accurate statistics. You can configure the traffic to be mirrored to an interface, to a CPU, or to a VLAN. • Mirroring traffic to an interface copies the matching packets to a destination interface. • Mirroring traffic to a CPU copies the matching packets to a CPU. For more information about QoS policies, traffic classes, and traffic behaviors, see ACL and QoS Configuration Guide. Traffic mirroring configuration task list Task Configuring match criteria Configuring traffic mirroring of different types Mirroring traffic to a port Mirroring traffic to the CPU Configuring a QoS policy Applying a QoS policy Apply a QoS policy to a port Apply a QoS policy to a VLAN Apply a QoS policy globally Remarks Required. Required. Perform at least one configuration. Required. Required. Perform one of these configurations. Configuring match criteria Step 1. Enter system view. 2. Create a class and enter class view. 3. Configure match criteria. Command system-view traffic classifier tcl-name [ operator { and | or } ] if-match match-criteria Remarks N/A By default, no traffic class exists. By default, no match criterion is configured in a traffic class. For more information about the traffic classifier and if-match commands, see ACL and QoS Command Reference. 90

  • 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
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157

90
Configuring traffic mirroring
Introduction to traffic mirroring
Traffic mirroring copies the specified packets to the specified destination for packet analyzing and
monitoring. It is implemented through QoS policies. In other words, you define traffic classes and
configure match criteria to classify packets to be mirrored and then configure traffic behaviors to mirror
packets that fit the match criteria to the specified destination. Traffic mirroring allows you to flexibly
classify packets by defining match criteria and obtain accurate statistics.
You can configure the traffic to be mirrored to an interface, to a CPU, or to a VLAN.
Mirroring traffic to an interface copies the matching packets to a destination interface.
Mirroring traffic to a CPU copies the matching packets to a CPU.
For more information about QoS policies, traffic classes, and traffic behaviors, see
ACL and QoS
Configuration Guide
.
Traffic mirroring configuration task list
Task
Remarks
Configuring match criteria
Required.
Configuring traffic
mirroring of different types
Mirroring traffic to a port
Required.
Perform at least one
configuration.
Mirroring traffic to the CPU
Configuring a QoS policy
Required.
Applying a QoS policy
Apply a QoS policy to a port
Required.
Perform one of these
configurations.
Apply a QoS policy to a VLAN
Apply a QoS policy globally
Configuring match criteria
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
} ]
By default, no traffic class exists.
3.
Configure match criteria.
if-match
match-criteria
By default, no match criterion is
configured in a traffic class.
For more information about the
traffic classifier
and
if-match
commands, see
ACL and QoS Command
Reference
.