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

Table 3-12, Policy State, Characteristics, portEnable

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 72 highlights

3 DCC policies must follow the naming convention "DCC_POLICY_nnn," where nnn represents a unique string. To save memory and improve performance, one DCC policy per switch or group of switches is recommended. Device ports must be specified by port WWN. Switch ports can be identified by the switch WWN, domain ID, or switch name followed by the port or area number. To specify an allowed connection, enter the device port WWN, a semicolon, and the switch port identification. Following are the possible methods of specifying an allowed connection: • deviceportWWN;switchWWN (port or area number) • deviceportWWN;domainID (port or area number) • deviceportWWN;switchname (port or area number) How to create a DCC policy is described after Table 3-12, which shows the possible DCC policy states. Table 3-12 DCC Policy States Policy State Characteristics No policy Any device can connect to any switch port in the fabric. Policy with no entries Any device can connect to any switch port in the fabric. An empty policy is the same as no policy. Policy with entries If a device WWN is specified in a DCC policy, that device is only allowed access to the fabric if connected to a switch port listed in the same policy. If a switch port is specified in a DCC policy, it only permits connections from devices that are listed in the policy. Devices with WWNs that are not specified in a DCC policy are allowed to connect to the fabric at any switch ports that are not specified in a DCC policy. Switch ports and device WWNs may exist in multiple DCC policies. Proxy devices are always granted full access and can connect to any switch port in the fabric. Note When a DCC violation occurs, the related port is automatically disabled and must be re-enabled using the portEnable command. Proxy device access cannot be managed using a DCC policy in a secure fabric. Proxy devices are always granted full access, even if the DCC policy has an entry that restricts or limits access of a proxy device. 3-22 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-22
Secure Fabric OS Administrator’s Guide
Publication Number: 53-1000244-01
3
DCC policies must follow the naming convention “DCC_POLICY_
nnn,
” where
nnn
represents a
unique string. To save memory and improve performance, one DCC policy per switch or group of
switches is recommended.
Device ports must be specified by port WWN. Switch ports can be identified by the switch WWN,
domain ID, or switch name followed by the port or area number. To specify an allowed connection,
enter the device port WWN, a semicolon, and the switch port identification. Following are the possible
methods of specifying an allowed connection:
•
deviceportWWN
;
switchWWN
(port or area number)
•
deviceportWWN
;
domainID
(port or area number)
•
deviceportWWN
;
switchname
(port or area number)
How to create a DCC policy is described after
Table 3-12
, which shows the possible DCC policy states.
Table 3-12
DCC Policy States
Policy State
Characteristics
No policy
Any device can connect to any switch port in the fabric.
Policy with no entries
Any device can connect to any switch port in the fabric. An empty
policy is the same as no policy.
Policy with entries
If a device WWN is specified in a DCC policy, that device is only
allowed access to the fabric if connected to a switch port listed in the
same policy.
If a switch port is specified in a DCC policy, it only permits connections
from devices that are listed in the policy.
Devices with WWNs that are not specified in a DCC policy are allowed
to connect to the fabric at any switch ports that are not specified in a
DCC policy.
Switch ports and device WWNs may exist in multiple DCC policies.
Proxy devices are always granted full access and can connect to any
switch port in the fabric.
Note
When a DCC violation occurs, the related port is automatically disabled and must be re-enabled using
the
portEnable
command.
Proxy device access cannot be managed using a DCC policy in a secure fabric. Proxy devices are always
granted full access, even if the DCC policy has an entry that restricts or limits access of a proxy device.