HP StorageWorks 2/16V Brocade Secure Fabric OS Administrator's Guide (53-10002 - Page 74

Creating an SCC Policy

Get HP StorageWorks 2/16V - SAN Switch PDF manuals and user guides View all HP StorageWorks 2/16V manuals
Add to My Manuals
Save this manual to your list of manuals

Page 74 highlights

3 To create a DCC policy "DCC_POLICY_example" that includes devices 44:55:66:77:22:33:44:dd and 33:44:55:66:77:11:22:cc, ports 1 through 4 of switch domain 4, and all devices currently connected to ports 1 through 4 of switch domain 4: primaryfcs:admin> secpolicycreate "DCC_POLICY_example", "44:55:66:77:22:33:44:dd;33:44:55:66:77:11:22:cc;4[1-4]" DCC_POLICY_xxx has been created Creating an SCC Policy Note Fabric OS v5.2.0 supports local SCC policies; however the local SCC polices created in non-secure mode cannot be used while in secure mode. Policies created in non-secure mode are deleted when secure mode is enabled. Back up SCC policies before enabling secure mode. The SCC policy is used to restrict which switches can join the fabric. Switches are checked against the policy each time secure mode is enabled, the fabric is initialized with secure mode enabled, or an E_Port-to-E_Port connection is made. The policy is named SCC_POLICY and accepts members listed as WWNs, domain IDs, or switch names. Only one SCC policy may be created. By default, any switch is allowed to join the fabric; the SCC policy does not exist until it is created by the administrator. Note When an SCC policy is activated, any non-FCS switches in the fabric not included in the policy member list, will be segmented from the fabric. A SCC policy is required if FICON is enabled. When connecting fibre channel router to secure Fabric that has an active SCC policy, the front domain of fibre channel router must be included in the SCC policy. The possible SCC policy states are shown in Table 3-13. 3-24 Secure Fabric OS Administrator's Guide Publication Number: 53-1000244-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
3-24
Secure Fabric OS Administrator’s Guide
Publication Number: 53-1000244-01
3
To create a DCC policy “DCC_POLICY_example” that includes devices 44:55:66:77:22:33:44:dd
and 33:44:55:66:77:11:22:cc, ports 1 through 4 of switch domain 4, and all devices currently
connected to ports 1 through 4 of switch domain 4:
Creating an SCC Policy
The SCC policy is used to restrict which switches can join the fabric. Switches are checked against the
policy each time secure mode is enabled, the fabric is initialized with secure mode enabled, or an
E_Port-to-E_Port connection is made.
The policy is named SCC_POLICY and accepts members listed as WWNs, domain IDs, or switch
names. Only one SCC policy may be created.
By default, any switch is allowed to join the fabric; the SCC policy does not exist until it is created by
the administrator.
The possible SCC policy states are shown in
Table 3-13
.
primaryfcs:admin>
secpolicycreate “DCC_POLICY_example”,
“44:55:66:77:22:33:44:dd;33:44:55:66:77:11:22:cc;4[1-4]”
DCC_POLICY_
xxx
has been created
Note
Fabric OS v5.2.0 supports local SCC policies; however the local SCC polices created in non-secure
mode cannot be used while in secure mode. Policies created in non-secure mode are deleted when secure
mode is enabled. Back up SCC policies before enabling secure mode.
Note
When an SCC policy is activated, any non-FCS switches in the fabric not included in the policy member
list, will be segmented from the fabric.
A SCC policy is required if FICON is enabled.
When connecting fibre channel router to secure Fabric that has an active SCC policy, the front domain
of fibre channel router must be included in the SCC policy.