HP StorageWorks MSA 2/8 HP StorageWorks Secure Fabric OS V1.0 User Guide (AA-R - Page 71

Creating a DCC Policy

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

Page 71 highlights

Creating Secure Fabric OS Policies Example: primaryfcs:admin> secPolicyCreate "OPTIONS_POLICY", "NoNodeWWNZoning" OPTIONS_POLICY has been created. primaryfcs:admin> Creating a DCC Policy You can create DCC policies to manage which device ports are allowed to connect to which switch ports. The devices can be initiators, targets, or intermediate devices such as SCSI routers and loop hubs. The same device port can be bound to one or more switch ports, and the same device and switch ports may be listed in multiple DCC policies. If a device port is specified in a DCC policy, that port is allowed access to the fabric only if it is connected to one of the designated switch ports. Similarly, if a switch port is specified in a DCC policy, it permits connections only from the specified devices. Device ports that are not specified in a DCC policy are allowed to connect only to switch ports that are not specified in a DCC policy. You can create multiple DCC policies, using the naming convention DCC_POLICY_nnn, where nnn represents a unique string. One DCC policy per switch or group of switches is recommended instead of a separate DCC policy for each port. This saves memory and improves performance. You can specify device ports by device WWN and switch ports by either switch WWN, Domain ID, or switch name followed by the port or area number. For example: ■ deviceWWN;switchWWN(port or area number) ■ deviceWWN;domainID(port or area number) ■ deviceWWN;switchname(port or area number) By default, all device ports are allowed to connect to all switch ports; no DCC policies exist until they are created by the administrator. The possible DCC policy states are shown in Table 12. Secure Fabric OS Version 1.0 User Guide 71

  • 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
Creating Secure Fabric OS Policies
71
Secure Fabric OS Version 1.0 User Guide
Example:
Creating a DCC Policy
You can create DCC policies to manage which device ports are allowed to connect
to which switch ports. The devices can be initiators, targets, or intermediate
devices such as SCSI routers and loop hubs.
The same device port can be bound to one or more switch ports, and the same
device and switch ports may be listed in multiple DCC policies. If a device port is
specified in a DCC policy, that port is allowed access to the fabric only if it is
connected to one of the designated switch ports. Similarly, if a switch port is
specified in a DCC policy, it permits connections only from the specified devices.
Device ports that are not specified in a DCC policy are allowed to connect only to
switch ports that are not specified in a DCC policy.
You can create multiple DCC policies, using the naming convention
DCC_POLICY_
nnn
, where
nnn
represents a unique string. One DCC policy per
switch or group of switches is recommended instead of a separate DCC policy for
each port. This saves memory and improves performance.
You can specify device ports by device WWN and switch ports by either switch
WWN, Domain ID, or switch name followed by the port or area number. For
example:
■
deviceWWN;switchWWN(port or area number)
■
deviceWWN;domainID(port or area number)
■
deviceWWN;switchname(port or area number)
By default, all device ports are allowed to connect to all switch ports; no DCC
policies exist until they are created by the administrator.
The possible DCC policy states are shown in
Table 12
.
primaryfcs:admin> secPolicyCreate “OPTIONS_POLICY”, “NoNodeWWNZoning”
OPTIONS_POLICY has been created.
primaryfcs:admin>