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

Creating Secure Fabric OS Policies Other Than the FCS Policy, 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 58 highlights

Creating Secure Fabric OS Policies Creating Secure Fabric OS Policies Other Than the FCS Policy The FCS policy is automatically created when Secure Mode is enabled. You can create the other Secure Fabric OS policies after Secure Mode is enabled. The member list of each policy determines the devices or switches to which the policy applies. If a policy does not exist, then no Secure Fabric OS controls are in effect for that aspect of the fabric. If a policy exists but has no members, that functionality is disabled for all switches in the fabric. Once you add the first member to a policy, that functionality becomes disabled for all switches except the listed members. Note: Save policy changes frequently; changes are lost if the switch is rebooted before the changes are saved. Each supported policy is identified by a specific name, and only one policy of each type can exist except for DCC policies. The policy names are case sensitive and must be entered in all upper case. You can create multiple DCC policies using the naming convention DCC_POLICY_nnn, with nnn representing a unique string. Note: It is strongly recommended that you upload and save a copy of the Secure Fabric OS database after creating the desired Secure Fabric OS policies. The configupload command can be used to upload a copy of the configuration file, which contains all the Secure Fabric OS information. For more information about this command, refer to the HP StorageWorks Fabric OS Version 3.1.x/4.1.x Reference Guide. Policy members can be specified by device port WWN, switch WWN, Domain IDs, or switch WWN, depending on the policy. The valid methods for specifying policy members are listed in Table 3. 58 Secure Fabric OS Version 1.0 User Guide

  • 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
58
Secure Fabric OS Version 1.0 User Guide
Creating Secure Fabric OS Policies Other Than the FCS Policy
The FCS policy is automatically created when Secure Mode is enabled. You can
create the other Secure Fabric OS policies after Secure Mode is enabled. The
member list of each policy determines the devices or switches to which the policy
applies.
If a policy does not exist, then no Secure Fabric OS controls are in effect for that
aspect of the fabric. If a policy exists but has no members, that functionality is
disabled for all switches in the fabric. Once you add the first member to a policy,
that functionality becomes disabled for all switches except the listed members.
Note:
Save policy changes frequently; changes are lost if the switch is rebooted before
the changes are saved.
Each supported policy is identified by a specific name, and only one policy of
each type can exist except for DCC policies. The policy names are case sensitive
and must be entered in all upper case. You can create multiple DCC policies using
the naming convention
DCC_POLICY_
nnn
, with
nnn
representing a unique
string.
Note:
It is strongly recommended that you upload and save a copy of the Secure
Fabric OS database after creating the desired Secure Fabric OS policies. The
configupload
command can be used to upload a copy of the configuration file,
which contains all the Secure Fabric OS information. For more information about this
command, refer to the
HP StorageWorks Fabric OS Version 3.1.x/4.1.x Reference
Guide
.
Policy members can be specified by device port WWN, switch WWN, Domain
IDs, or switch WWN, depending on the policy. The valid methods for specifying
policy members are listed in
Table 3
.