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

Saving Changes to Secure Fabric OS Policies, Aborting a Secure Fabric OS Transaction

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

Creating Secure Fabric OS Policies ■ Aborting a Secure Fabric OS Transaction, page 81 From any switch in the fabric, abort a Secure Fabric OS-related transaction that has become frozen (such as due to a failed host) and is preventing other Secure Fabric OS transactions. Saving Changes to Secure Fabric OS Policies You can save changes to Secure Fabric OS policies without activating them by entering the secpolicysave command. This saves the changes to the Defined Policy Set. Note: Until the secpolicysave or secpolicyactivate command is issued, all policy changes are in volatile memory only, and are lost if the switch reboots or the current session is logged out. To save changes to the Secure Fabric OS policies without activating the changes: 1. From a sectelnet or SSH session, log into the Primary FCS switch as Admin. 2. Enter the secpolicysave command. Example: primaryfcs:admin> secPolicySave Committing configuration...done. Saving Define FMPS ... done primaryfcs:admin> Activating Changes to Secure Fabric OS Policies In order to implement any changes to the Secure Fabric OS policies, you must enter the secpolicyactivate command. This saves the changes to the Active Policy Set and activates all policy changes since the last time the command was issued. You cannot activate an individual policy; all changes to the entire policy set are activated by the command. Note: Until a secpolicysave or secpolicyactivate command is issued, all policy changes are in volatile memory only, and are lost upon rebooting. Secure Fabric OS Version 1.0 User Guide 77

  • 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
77
Secure Fabric OS Version 1.0 User Guide
■
Aborting a Secure Fabric OS Transaction
, page 81
From any switch in the fabric, abort a Secure Fabric OS-related transaction
that has become frozen (such as due to a failed host) and is preventing other
Secure Fabric OS transactions.
Saving Changes to Secure Fabric OS Policies
You can save changes to Secure Fabric OS policies without activating them by
entering the
secpolicysave
command. This saves the changes to the
Defined Policy Set.
Note:
Until the
secpolicysave
or
secpolicyactivate
command is issued,
all policy changes are in volatile memory only, and are lost if the switch reboots or the
current session is logged out.
To save changes to the Secure Fabric OS policies without activating the changes:
1.
From a sectelnet or SSH session, log into the Primary FCS switch as Admin.
2.
Enter the
secpolicysave
command.
Example:
Activating Changes to Secure Fabric OS Policies
In order to implement any changes to the Secure Fabric OS policies, you must
enter the
secpolicyactivate
command. This saves the changes to the
Active Policy Set and activates all policy changes since the last time the command
was issued. You cannot activate an individual policy; all changes to the entire
policy set are activated by the command.
Note:
Until a
secpolicysave
or
secpolicyactivate
command is issued,
all policy changes are in volatile memory only, and are lost upon rebooting.
primaryfcs:admin> secPolicySave
Committing configuration...done.
Saving Define FMPS ...
done
primaryfcs:admin>