Cisco NME-16ES-1G User Guide - Page 34

Policing and Marking

Page 34 highlights

Feature Overview 16- and 36-Port Ethernet Switch Module for Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series A policy map also has these characteristics: • A policy map can contain multiple class statements. • A separate policy-map class can exist for each type of traffic received through an interface. • A policy-map configuration state supersedes any actions due to an interface trust state. For configuration information, see the "Configuring a QoS Policy" section on page 90. Policing and Marking Policing involves creating a policer that specifies the bandwidth limits for the traffic. Packets that exceed the limits are out of profile or nonconforming. Each policer specifies the action to take for packets that are in or out of profile. These actions, carried out by the marker, include dropping the packet, or marking down the packet with a new value that is user-defined. You can create this type of policer: Individual-QoS applies the bandwidth limits specified in the policer separately to each matched traffic class. You configure this type of policer within a policy map by using the policy-map configuration command. For non-IP traffic, you have these marking options: • Use the port default. If the frame does not contain a CoS value, assign the default port CoS value to the incoming frame. • Trust the CoS value in the incoming frame (configure the port to trust CoS). Layer 2 802.1Q frame headers carry the CoS value in the three most-significant bits of the Tag Control Information field. CoS values range from 0 for low priority to 7 for high priority. The trust DSCP configuration is meaningless for non-IP traffic. If you configure a port with this option and non-IP traffic is received, the switch assigns the default port CoS value and classifies traffic based on the CoS value. For IP traffic, you have these classification options: • Trust the IP DSCP in the incoming packet (configure the port to trust DSCP), and assign the same DSCP to the packet for internal use. The IETF defines the six most-significant bits of the 1-byte type of service (ToS) field as the DSCP. The priority represented by a particular DSCP value is configurable. The supported DSCP values are 0, 8, 10, 16, 18, 24, 26, 32, 34, 40, 46, 48, and 56. • Trust the CoS value (if present) in the incoming packet, and generate the DSCP by using the CoS-to-DSCP map. When configuring policing and policers, keep these items in mind: • By default, no policers are configured. • Policers can only be configured on a physical port. There is no support for policing at a VLAN or switched virtual interface (SVI) level. • Only one policer can be applied to a packet in the input direction. • Only the average rate and committed burst parameters are configurable. • Policing occurs on the ingress interfaces: - 60 policers are supported on ingress Gigabit-capable Ethernet ports. - 6 policers are supported on ingress 10/100 Ethernet ports. - Granularity for the average burst rate is 1 Mbps for 10/100 ports and 8 Mbps for Gigabit Ethernet ports. Cisco IOS Release 12.2(2)XT, 12.2(8)T, and 12.2(15)ZJ 34

  • 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
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246

16- and 36-Port Ethernet Switch Module for Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series
Feature Overview
34
Cisco IOS Release 12.2(2)XT, 12.2(8)T, and 12.2(15)ZJ
A policy map also has these characteristics:
A policy map can contain multiple class statements.
A separate policy-map class can exist for each type of traffic received through an interface.
A policy-map configuration state supersedes any actions due to an interface trust state.
For configuration information, see the
“Configuring a QoS Policy” section on page 90
.
Policing and Marking
Policing involves creating a policer that specifies the bandwidth limits for the traffic. Packets that exceed
the limits are
out of profile
or
nonconforming
. Each policer specifies the action to take for packets that
are in or out of profile. These actions, carried out by the marker, include dropping the packet, or marking
down the packet with a new value that is user-defined.
You can create this type of policer:
Individual—QoS applies the bandwidth limits specified in the policer separately to each matched
traffic class. You configure this type of policer within a policy map by using the policy-map
configuration command.
For non-IP traffic, you have these marking options:
Use the port default. If the frame does not contain a CoS value, assign the default port CoS value to
the incoming frame.
Trust the CoS value in the incoming frame (configure the port to trust CoS). Layer 2 802.1Q frame
headers carry the CoS value in the three most-significant bits of the Tag Control Information field.
CoS values range from 0 for low priority to 7 for high priority.
The trust DSCP configuration is meaningless for non-IP traffic. If you configure a port with this
option and non-IP traffic is received, the switch assigns the default port CoS value and classifies
traffic based on the CoS value.
For IP traffic, you have these classification options:
Trust the IP DSCP in the incoming packet (configure the port to trust DSCP), and assign the same DSCP
to the packet for internal use. The IETF defines the six most-significant bits of the 1-byte type of
service (ToS) field as the DSCP. The priority represented by a particular DSCP value is configurable.
The supported DSCP values are 0, 8, 10, 16, 18, 24, 26, 32, 34, 40, 46, 48, and 56.
Trust the CoS value (if present) in the incoming packet, and generate the DSCP by using the
CoS-to-DSCP map.
When configuring policing and policers, keep these items in mind:
By default, no policers are configured.
Policers can only be configured on a physical port. There is no support for policing at a VLAN or
switched virtual interface (SVI) level.
Only one policer can be applied to a packet in the input direction.
Only the average rate and committed burst parameters are configurable.
Policing occurs on the ingress interfaces:
60 policers are supported on ingress Gigabit-capable Ethernet ports.
6 policers are supported on ingress 10/100 Ethernet ports.
Granularity for the average burst rate is 1 Mbps for 10/100 ports and 8 Mbps for Gigabit
Ethernet ports.