HP StorageWorks XP48 Disk Array - Manual (Page 52)

Using Provisioning Manager 52
CAUTION:
• A user with guest or local guest access permission cannot edit an allocation plan.
• Even for an allocation plan whose security level is public, if the login user’s access permission is Local Administrator
or Local Storage Administrator, the user cannot delete the following plans:
• An allocation plan that is owned by a user group positioned above the user group to which the login user belongs
• An allocation plan that is owned by a user group positioned in a different hierarchy from the user group to which
the login user belongs
To delete an allocation plan:
1. From the navigation frame, click Provisioning Plans.
2. Click Allocation Plans, located in the navigation frame immediately below Provisioning Plans. The method
frame displays the Allocation Plans subwindow. The information frame displays the List Objects -
Allocation Plans subwindow.
3. In the List Objects - Allocation Plans subwindow, click the plan name. The method frame displays the
PlanName subwindow.
4. In the PlanName subwindow, click Delete Allocation Plan. The Delete Allocation Plan - PlanName dialog
box is displayed (see
Figure 3-14 ).
5. Click the OK button. A dialog box for confirming that you wish to delete the allocation plan is displayed.
6. If you still wish to delete the allocation plan, click the OK button.
7. Make sure that the target allocation plan is deleted in the Delete Allocation Plan - Result dialog box.
8. Click the Close button. The dialog box closes. This action completes deletion of the allocation plan.
Figure 3-14 Delete Allocation Plan - PlanName Dialog Box
3-7 Managing Transaction Logs
A transaction log is a recording of the state and result of each operation performed by the user on a host and
the states and results of the sequence of configuration steps requested by Provisioning Manager to the host
(Device Manager agent) that is generated by these operations.
The following paragraphs explain some uses of a transaction log.
• Isolating an error
Because the state and result of each step are recorded, you can use the transaction log to isolate errors,
regardless of whether or not the operation executed successfully. Provisioning Manager expands a single
configuration operation specified by a user into multiple steps. This is helpful for isolating an error
because, in addition to the step at which the error occurred, you might also have to check the states and
results of the steps immediately preceding the step at which the error occurred.
• Checking the progress of a configuration operation
Because the state and result of each configuration step included in a configuration operation are
immediately recorded, you can use them to check the progress of an operation. Provisioning Manager
expands a single configuration operation specified by a user into multiple steps. This is helpful for
checking the progress of an operation, because an operation may take some time to complete,
depending on the environment.
• Restarting a configuration operation
Because the intermediate states of the configuration steps in a configuration operation are recorded, a
transaction log can be used to restart the configuration operation after user intervention has ended. This
is helpful because, although Provisioning Manager can be used to perform many configuration operations
centrally from a management client, in some environments you may not be able to avoid user
intervention, such as restarting of the host.