HP StorageWorks 2/16V HP StorageWorks Fabric OS 5.3.x administrator guide (569 - Page 139

Deleting IP Filter policy rules, Aborting a switch session transaction, IP Filter policy distributions

Page 139 highlights

Deleting IP Filter policy rules Deleting a rule in the specified IP Filter policy causes the rules following the deleted rule to shift up in rule order. The change to the specified IP Filter policy is not saved to persistent configuration until a save or activate sub-command is run. To delete a rule to an IP Filter policy: 1. Log in to the switch as admin. 2. Type in the following command: ipfilter --delrule -rule Aborting a switch session transaction A transaction is associated with a command line or manageability session. It is opened implicitly when the --create, --addrule, --delrule, --clone and --delete subcommands are run. This subcommand will explicitly end the transaction owned by the current command line or manageability session. If a transaction is not ended, other command line or manageability sessions are blocked on the sub-commands that would open a new transaction. To abort a transaction associated with IP Filter 1. Log in to the switch as admin. 2. Type in the following command: ipfilter --transabort IP Filter policy distributions The IP Filter policy is manually distributed, using the distribute --p "IPFILTER" command. The distribution includes both active and defined IP Filter policies. All policies are combined as a single entity to be distributed and cannot be selectively distributed. However, you may choose the time at which to implement the policy for optimization purposes. If a distribution includes an active IP Filter policy, the receiving switches will activate the same IP Filter policy automatically. When a switch receives IP Filter policies, all uncommitted changes left in its local transaction buffer will be lost, and the transaction will be aborted. When firmware is upgraded for the first time from pre-5.3.0 to 5.3.0, the default IPv4 and IPv6 filter policies are active. If non-default IP Filter policies are created, and then saved but not activated, and firmware is downgraded to pre-5.3.0, the non-default IP Filter policies are preserved. Subsequently, if the firmware is upgraded again to 5.3.0, the saved IP Filter policies remains present and become visible again. If, however, the default IP Filter policy is not active, a firmware downgrade to pre-5.3.0 is blocked. Switches with Fabric OS 5.3.0 will have the ability to accept or deny IP Filter policy distribution, through the commands fddCfg --localaccept or fddcfg --localreject. However, automatic distribution of IP Filter policy through Fabric Wide Consistent Policy is not supported in Fabric OS 5.3.0release. See "Distributing ACL policies to other switches" on page 141 for more information on distributing the IP Filter policy. IP Filter policy restrictions On a chassis system with dual switch domains, IP Filter policies can only be configured through switch instance 0 (zero). IP Filter policies created on switch instance 0 will apply to both switch instances. Attempting to configure IP Filter policy on switch instance 1 will generate error messages. In a mixed fabric with Fabric OS 5.3.0 and pre-5.3.0 switches, IP Filter policies cannot be distributed from a Fabric OS 5.3.0 switch to a pre-5.3.0 switch. This means that the sending switch will fail distribute --p "IPFILTER" operation, if the specified receiving domain list contains switches with Fabric OS 5.2.0 and earlier. When the asterisk (*) is used as the receiving domain, the sending switch will distribute the IP Filter policies only to switches with Fabric OS 5.3.0. Fabric OS 5.3.0 administrator guide 141

  • 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
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412
  • 413
  • 414
  • 415
  • 416
  • 417
  • 418
  • 419
  • 420
  • 421
  • 422
  • 423
  • 424
  • 425
  • 426
  • 427
  • 428
  • 429
  • 430
  • 431
  • 432
  • 433
  • 434
  • 435
  • 436
  • 437
  • 438
  • 439
  • 440
  • 441
  • 442
  • 443
  • 444
  • 445
  • 446
  • 447
  • 448
  • 449
  • 450
  • 451
  • 452
  • 453
  • 454
  • 455
  • 456
  • 457
  • 458
  • 459
  • 460
  • 461
  • 462
  • 463
  • 464
  • 465

Fabric OS 5.3.0 administrator guide
141
Deleting IP Filter policy rules
Deleting a rule in the specified IP Filter policy causes the rules following the deleted rule to shift up in rule
order. The change to the specified IP Filter policy is not saved to persistent configuration until a save or
activate sub-command is run.
To delete a rule to an IP Filter policy:
1.
Log in to the switch as admin.
2.
Type in the following command:
ipfilter –-delrule <policyname> -rule <rule number>
Aborting a switch session transaction
A transaction is associated with a command line or manageability session. It is opened implicitly when the
--
create
,
--
addrule
,
--
delrule
,
--
clone
and
--
delete
subcommands are run. This
subcommand will explicitly end the transaction owned by the current command line or manageability
session. If a transaction is not ended, other command line or manageability sessions are blocked on the
sub-commands that would open a new transaction.
To abort a transaction associated with IP Filter
1.
Log in to the switch as admin.
2.
Type in the following command:
ipfilter –-transabort
IP Filter policy distributions
The IP Filter policy is manually distributed, using the
distribute --p “IPFILTER”
command. The
distribution includes both active and defined IP Filter policies. All policies are combined as a single entity
to be distributed and cannot be selectively distributed. However, you may choose the time at which to
implement the policy for optimization purposes. If a distribution includes an active IP Filter policy, the
receiving switches will activate the same IP Filter policy automatically. When a switch receives IP Filter
policies, all uncommitted changes left in its local transaction buffer will be lost, and the transaction will be
aborted.
When firmware is upgraded for the first time from pre-5.3.0 to 5.3.0, the default IPv4 and IPv6 filter
policies are active. If non-default IP Filter policies are created, and then saved but not activated, and
firmware is downgraded to pre-5.3.0, the non-default IP Filter policies are preserved. Subsequently, if the
firmware is upgraded again to 5.3.0, the saved IP Filter policies remains present and become visible
again. If, however, the default IP Filter policy is not active, a firmware downgrade to pre-5.3.0 is blocked.
Switches with Fabric OS 5.3.0 will have the ability to accept or deny IP Filter policy distribution, through
the commands
fddCfg --localaccept
or
fddcfg --localreject
.
However, automatic
distribution of IP Filter policy through Fabric Wide Consistent Policy is not supported in Fabric OS
5.3.0release. See ”
Distributing ACL policies to other switches
” on page 141 for more information on
distributing the IP Filter policy.
IP Filter policy restrictions
On a chassis system with dual switch domains, IP Filter policies can only be configured through switch
instance 0 (zero). IP Filter policies created on switch instance 0 will apply to both switch instances.
Attempting to configure IP Filter policy on switch instance 1 will generate error messages.
In a mixed fabric with Fabric OS 5.3.0 and pre-5.3.0 switches, IP Filter policies cannot be distributed from
a Fabric OS 5.3.0 switch to a pre-5.3.0 switch. This means that the sending switch will fail
distribute
--p “IPFILTER”
operation, if the specified receiving domain list contains switches with Fabric OS 5.2.0
and earlier. When the asterisk (
*
) is used as the receiving domain, the sending switch will distribute the IP
Filter policies only to switches with Fabric OS 5.3.0.