Netgear GSM7312 FSM7326P User Manual - Page 180

hierarchical service policies not supported in a class definition

Page 180 highlights

User Manual for the NETGEAR 7300 Series Layer 3 Managed Switch Software Note that the type of class - all, any, or acl - has a bearing on the validity of match criteria specified when defining the class. A class type of 'any' processes its match rules in an ordered sequence; additional rules specified for such a class simply extend this list. A class type of 'acl' obtains its rule list by interpreting each ACL rule definition at the time the Diffserv class is created. Differences arise when specifying match criteria for a class type 'all', since only one value for each non-excluded match field is allowed within a class definition. If a field is already specified for a class, all subsequent attempts to specify the same field fail, including the cases where a field can be specified multiple ways through alternative formats. The exception to this is when the 'exclude' option is specified, in which case this restriction does not apply to the excluded fields. The only way to remove an individual match criterion from an existing class definition is to delete the class and re-create it. The following class restrictions are imposed by the 7000 Series L3 Managed Switch Software DiffServ design: • nested class support limited to: - 'any' within 'any' - 'all' within 'all' - no nested 'not' conditions - no nested 'acl' class types - each class contains at most one referenced class • hierarchical service policies not supported in a class definition • access list matched by reference only, and must be sole criterion in a class - i.e., ACL rules copied as class match criteria at time of class creation, with class type 'any' - implicit ACL 'deny all' rule also copied - no nesting of class type 'acl' Regarding nested classes, referred to here as class references, a given class definition can contain at most one reference to another class, which can be combined with other match criteria. The referenced class is truly a reference and not a copy, since additions to a referenced class affect all classes that reference it. Changes to any class definition currently referenced by any other class must result in valid class definitions for all derived classes otherwise the change is rejected. A class reference may be removed from a class definition. 9-2 Differentiated Services 202-10009-01

  • 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
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268

User Manual for the NETGEAR 7300 Series Layer 3 Managed Switch Software
9-2
Differentiated Services
202-10009-01
Note that the type of class - all, any, or acl - has a bearing on the validity of match criteria specified
when defining the class. A class type of 'any' processes its match rules in an ordered sequence;
additional rules specified for such a class simply extend this list. A class type of ‘acl’ obtains its
rule list by interpreting each ACL rule definition at the time the Diffserv class is created.
Differences arise when specifying match criteria for a class type 'all', since only one value for each
non-excluded match field is allowed within a class definition. If a field is already specified for a
class, all subsequent attempts to specify the same field fail, including the cases where a field can
be specified multiple ways through alternative formats. The exception to this is when the 'exclude'
option is specified, in which case this restriction does not apply to the excluded fields. The only
way to remove an individual match criterion from an existing class definition is to delete the class
and re-create it.
The following class restrictions are imposed by the 7000 Series L3 Managed Switch Software
DiffServ design:
nested class support limited to:
'any' within 'any'
'all' within 'all'
no nested 'not' conditions
no nested 'acl' class types
each class contains at most one referenced class
hierarchical service policies not supported in a class definition
access list matched by reference only, and must be sole criterion in a class
i.e., ACL rules copied as class match criteria at time of class creation, with class type 'any'
implicit ACL 'deny all' rule also copied
no nesting of class type 'acl'
Regarding nested classes, referred to here as class references, a given class definition can contain
at most one reference to another class, which can be combined with other match criteria. The
referenced class is truly a reference and not a copy, since additions to a referenced class affect all
classes that reference it. Changes to any class definition currently referenced by any other class
must result in valid class definitions for all derived classes otherwise the change is rejected. A
class reference may be removed from a class definition.