116 Configuring advanced security
Non-matching fabric-wide consistency policies
You may encounter one of the following two scenarios:
•
Merging a fabric with a strict policy to a fabric with an absent, tolerant, or non-matching strict policy.
The merge fails and the ports are disabled.
Table 32
shows merges that are not supported:
•
Merging fabrics with tolerant and absent policies. See
Table 33
for examples:
Table 32
Examples of strict fabric merges
Fabric-wide consistency policy setting
Expected behavior
Fabric A
Fabric B
Strict/Tolerant
SCC:S;DCC:S
SCC;DCC:S
Ports connecting switches are disabled.
SCC;DCC:S
SCC:S;DCC
Strict/Absent
SCC:S;DCC:S
SCC:S
DCC:S
Strict/Strict
SCC:S
DCC:S
Table 33
Fabric merges with tolerant/absent combinations
Fabric-wide consistency policysetting
Expected behavior
Fabric A
Fabric B
Tolerant/Absent
SCC;DCC
Error message logged.
Run
fddCfg --fabwideset
“<
policy_ID
>”
from any switch
with the desired configuration to fix
the conflict. The
secPolicyActivate
command
is blocked until conflict is resolved.
DCC
SCC;DCC
SCC
DCC
SCC
Summary of Contents for AE370A - Brocade 4Gb SAN Switch 4/12
Page 18: ...18 ...
Page 82: ...82 Managing user accounts ...
Page 102: ...102 Configuring standard security features ...
Page 126: ...126 Maintaining configurations ...
Page 198: ...198 Routing traffic ...
Page 238: ...238 Using the FC FC routing service ...
Page 260: ...260 Administering FICON fabrics ...
Page 280: ...280 Working with diagnostic features ...
Page 332: ...332 Administering Extended Fabrics ...
Page 414: ...398 Configuring the PID format ...
Page 420: ...404 Configuring interoperability mode ...
Page 426: ...410 Understanding legacy password behaviour ...
Page 442: ...426 ...
Page 444: ......
Page 447: ......