![]() |
Using Management Center for Firewalls 1.2
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Managing Activities
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Table of ContentsManaging ActivitiesUnderstanding Activities Managing Activities With Workflow Disabled Managing Activities With Workflow Enabled Using Activity Management
Understanding Activity Error and Warning MessagesCreating an Activity Submitting an Activity for Review Approving or Rejecting an Activity (Approval Process Enabled) Opening an Existing Activity Closing an Activity Undoing An Activity Activity Error Messages
Error: No Activity Is Open
Activity Transition Warning MessagesError: <Device | Device Group> Is Locked by <Activity> Error: No Changes Can Be Made Within the Open Activity, As It Has Been Submitted for Approval Error: Invalid activity action (action). The workflow type may be changed. Please close and reopen the Firewall MC application window. Error: Operation failed. The workflow setup might be changed. Please close and reopen the browser Error: You must approve or discard all existing activities and deploy all existing jobs before you disable workflow Managing ActivitiesYou make most changes in Firewall MC using activities. Certain settings, like administrative settings, do not require an activity to modify, but firewall device settings must be changed using an activity. Activities provide an audit trail for changes, and are a convenient way to experiment with changes—you can simply discard any activities with changes you do not want to implement. Activities are implemented in three different ways, depending on the workflow mode you choose. The following workflow modes are available:
When workflow is enabled, the GUI displays the Workflow tab so you can manage activities. When workflow is disabled, the GUI displays the Deployment tab. You can use the Deployment tab to view deployment status information and to deploy saved configurations to devices. You control which of these methods to use for tracking changes. You can enable workflow with or without the formal approval process at any time; however, before you can disable workflow, you must approve or discard any open activities and deploy, cancel, or verify that all jobs are being deployed. For more information on jobs, see Managing Deployment With Workflow Enabled. Understanding ActivitiesIn Firewall MC, you use activities to control changes made to the firewall devices you are managing. Although the way activities are implemented depends on the workflow settings you choose, activities provide the following benefits in all workflow modes:
Understanding LockingThe device hierarchy is the basis for the locking-model design, which ensures the integrity of the deployed configuration files. If a group within the hierarchy is locked, subgroups and devices are implicitly locked, thereby eliminating the possibility of conflicting changes being imposed on the same devices. When you open or create an activity, the system must acquire a lock, which can be acquired only if no other activity holds a lock on the same groups or devices. Other users are locked out until the activity is approved and committed, or undone. This guarantees that when you change elements associated with a global group, no other user can read or write changes to the group that you are editing.
Imagine a device hierarchy with a group called Global at the top level containing subgroups Fruits and Nuts. Fruits contains devices Apple and Banana. Nuts contains devices Walnut and Pecan. The general rule is that when an activity makes changes to a device or device group in the hierarchy, that device or group and everything below that group is locked, and each enclosing group is marked so that no other activity can lock it. Making changes to the Global group locks everything in the hierarchy. Adding a group or device to an existing group is like making changes to the existing group. Consider the following examples:
Suppose an activity tried to make changes to the Nuts group. These changes would not be permitted, because the Nuts group has been marked, which prevents it from being locked.
Understanding Padlock IconsAfter you select the scope using the Object Selector, Firewall MC displays the scope information in the Object bar. A padlock icon is placed to the left of the device or device group that is locked. The padlock is associated with the highest point in the object hierarchy that is locked. This enables you to determine if the device or device group is available for you to make configuration changes. You can also place the mouse cursor over the lock to determine who holds the lock when workflow is disabled, or which activity holds the lock when workflow is enabled.
Managing Activities With Workflow DisabledWhen workflow is disabled (default), you do not need to define activities for tracking changes in Firewall MC. After you make configuration changes, you can deploy those configuration changes by clicking the Save and Deploy icon in the activity bar of the Devices and Configuration tabs, or you can discard the changes by clicking the Undo icon. When you click the Save and Deploy icon, new configurations are generated for any modified devices. You can then deploy the new configurations, or save them and deploy them later. For more information on deploying saved configurations, see Using the Deployment Tab. The Deployment tab is visible only when workflow is disabled. When you enable workflow, the Deployment tab is replaced by the Workflow tab, and you manage deployments by using jobs. For more information on using jobs for deployment, see Using Job Management. Important Notes about Using Firewall MC When Workflow Is Disabled
Using the Activity BarWhen workflow is disabled, you use the activity bar in the Devices and Configuration tabs to generate configurations for changed devices, undo changes, and view changes that were made since the last save. Table 4-1 shows the activity bar icons available when workflow is disabled. Table 4-1 Activity Bar Icons Used When Workflow is Disabled Managing Activities With Workflow EnabledMany organizations benefit from having a separation of responsibility when defining, implementing, and deploying corporate firewall policies. For example, a security administrator might be responsible for defining a device configuration file, another administrator for approving the configuration file, and a network operator for deploying the resulting configuration to a device. This separation of responsibility helps maintain the integrity of deployed device configurations. Firewall MC supports this separation of responsibility using activities and jobs, which define tasks that are accomplished by one or more people in succession.
Activities control policy changes. When you create a new activity, you are preparing a proposal to create or change firewall device configurations. An activity includes such information as devices or device groups to which configuration settings, access rules, and translation rules will be downloaded. To access the activities feature, select Workflow > Activity Management. See Using Activity Management.
After an activity is approved, the corresponding configuration elements can be downloaded to several devices in the form of a job. A job identifies devices to which configuration files will be deployed. To access the jobs feature, select Workflow>Job Management. See Using Job Management. To view the latest configuration file, select Configuration > View Config. See Viewing Configurations. Table 4-2 is a quick-reference to help you understand how to use activity- and job-management features. Table 4-2 Quick Reference Process Flow
Using Activity ManagementWhen you create a new activity, you are preparing a proposal to create or change firewall device configurations. An activity is a task that is accomplished by one or more people in succession. For example, a network administrator sets configuration parameters for a firewall device, and a system administrator approves the configuration settings. This separation of responsibility helps maintain the integrity of deployed device configurations. Because most users manage many firewall devices within their networks, it is common practice to manage these devices in groups. The Firewall MC design is based on a navigation hierarchy to facilitate navigation to firewall device groups and devices. As a result, a single activity could affect several devices or groups; however, only one user may open the activity at any given time. Important Notes About Activities
Understanding Activity Actions and StatesFirewall MC keeps a history of actions made with each activity, from creating an activity, to approving the activity for deployment. You also have the option of undoing all changes to an activity, which discards the activity from use. Although the Activity Management table shows only the most recent action state, you can view all actions for an activity by selecting Reports > Activity. See Viewing Administrative Activity Reports. Figure 4-1 shows an Activity Management table with activity actions and activity state information. After a new activity is defined, it advances to the Edit_Open state in the Activity Management table. The activity name is also displayed in the activity bar at the top right of your screen when viewed from the Devices or Configure tabs. You can now begin making device or configuration changes. While in the Edit_Open state, the activity and the devices and groups defined within the activity are locked to other users. Only the person who opened the activity can make changes. Figure 4-1 Activity Management Table
An activity can have the following states, which are shown in the Activity Management table State column:
Creating an ActivityCreating activities to support your organization's policies is simple. You can define your activities as a succession of actions (for example, populate network, set access rules, set passwords) based on your network topology (for example, East Coast, Corporate Office, Finance, Third-party) or by defining a change in configuration settings (for example, AAA). You then configure your network settings and submit them for review and approval (if the approval process is enabled). Ultimately, the activity takes effect through deployment jobs that download new configuration information to the selected devices. After you define your activity, it is listed in the Activity Management table, along with its current state.
Step 1 Select Workflow > Activity Management. The Activity Management page appears. Step 2 Click Add. You are prompted to enter an activity name and an optional activity comment. Step 3 Enter the information in the fields provided, then click OK. You are returned to the Activity Management table with the new activity listed. The activity state is shown as Edit_Open. Updated information is noted in the Last Action column. You are ready to begin the device setup or configuration settings for use for later deployment. Activity Management Field-Level Elements and Descriptions
Submitting an Activity for ReviewThe review and approval feature is disabled by default, but you can enable the feature if your organization requires a formal approval process. See Requiring a Formal Approval Phase. If the approval process is disabled, the submit and approval process is a single step and the activity is approved automatically when it is submitted. If the approval process is enabled, you must submit an activity to someone in your organization for review and approval. When you submit an activity for review, it must be in the Edit or Edit_Open state. After you submit an activity for approval, a person with approval authority reviews the changes.
Submitting an ActivityBefore You BeginStep 1 Select Workflow > Activity Management. The Activity Management page appears. Step 2 In the table, find the activity to submit for approval, then do one of the following: b. Enter the Activity Submit Comment (recommended). Enter a comment related to the submitted activity request (for example, includes changes to address translation pools for the Global scope). b. Enter the email address of a person with approval authority in the field provided. You can enter more than one email address. c. Enter the Activity Submit Comment (optional). Enter a comment related to the submitted activity request (for example, includes changes to address translation pools for the Global scope). The Review Device Generation List page appears. This page provides a list of devices that are changed by the activity. Step 3 Verify the devices listed are correct, then click Next. The activity summary page appears. Step 4 Verify the information is correct, then click Finish. If any devices were changed by the activity a device status popup window opens. The window refreshes automatically every 60 seconds; however, you can click Refresh to update device status manually.
Step 5 After viewing device status information, close the device status window. This is not necessary if no devices were changed by the activity.
Approving or Rejecting an Activity (Approval Process Enabled)Only a person with approval authority can approve or reject an activity. In a traditional environment, a creator and an approver work together to support changes made to policies. The creator submitting the activity for approval is prompted to enter the email address of the persons responsible for approving the activity. A person with approval authority can do one of the following:
Approving or Rejecting an ActivityBefore You BeginStep 1 Select Workflow > Activity Management. The Activity Management page appears. Step 2 In the table, find the activity to review, then click Open. The activity state changes to Submitted_Open. Step 3 Run an activity report () to view changes (recommended). See Viewing Administrative Activity Reports. Step 4 View the configuration file for each device listed in the activity (recommended). To do this, select the activity, then click Status. A popup window opens to display the generation status of all devices in the activity. Step 5 From the popup window, select a device, then click View Config. Step 6 Do one of the following: You are prompted to enter an optional activity transit comment. Step 7 Enter the optional information in the field provided, then click OK. You are returned to the Activity Management table with Approved or Rejected displayed in the State column. Updated information is shown in the Last Action column. Opening an Existing ActivityYou can open an activity to make changes only if it is unlocked or if none of the devices and device groups overlap another activity that is locked. To verify if the activity can be opened, check the Activity Management table. If the state shown is any of the following, you will not be able to open the activity:
Step 1 Select Workflow > Activity Management. The Activity Management page appears. Step 2 Find the activity in the table that you want to open, then click Open. The activity state is shown as Edit_Open in the Activity Management table. Updated information is noted in the Last Action column. You are ready to continue with device setup or configuration changes for use for later deployment. Do either of the following: Closing an ActivityAfter you complete an activity, you should close it to grant access to other users. If you have permission to do so, you may close an activity that was opened by another user. Otherwise, you may close only an activity that you opened. Step 1 Select Workflow > Activity Management. The Activity Management page appears. Step 2 Find the activity in the table that you want to close, then click Close. The activity state is shown as Edit in the State column and updated information is noted in the Last Action column.
Undoing An ActivityYou might need to discard changes to configuration settings associated with an activity. If this occurs, you can undo your changes, which returns to the previous configuration settings.
Step 1 Select Workflow > Activity Management. The Activity Management page appears. Step 2 Find the activity in the table that you want to discard, then click Undo. You are prompted for an optional activity transition comment. Step 3 Enter an optional comment in the field provided, then click OK. The activity is discarded. You are returned to the Activity Management table with the activity state shown as Discarded in the State column. Updated information is noted in the Last Action column. The activity remains listed in the table until it is purged by the system. Understanding Activity Error and Warning MessagesBefore you can make changes to a policy, you must create or open an activity. To create or open an activity, you must be an authorized user and have permission to perform this action. In addition, creating or opening an activity requires a lock. While you are making policy changes in Firewall MC, different popup windows might appear containing error or warning messages that guide you through the activity management process. These messages vary, depending upon lock availability, whether you are authorized to perform an action, whether an activity must be created or opened first, or as a transition to the next required action within the workflow process. Activity Error MessagesThe following error messages are discussed:
Error: No Activity Is OpenThis message appears if you have not created or opened an activity. You must create a new activity, or open an existing activity that can be edited to preserve the activity information in the database. Step 1 From the error popup window, select one of the following. Step 2 Click OK. a. You can use the default name or assign a new name in the field provided. b. Enter a comment in the Initial Activity Comment field. c. Click OK. The popup window closes and you are returned to the Devices or Configuration tab with the opened activity name shown in the activity bar at the top right of your screen. a. Select the activity using the respective radio button. b. Click OK. The popup window closes and you are returned to the Devices or Configuration tab with the opened activity name shown by the activity bar at the top right of your screen. You are now ready to make policy changes. Error: <Device | Device Group> Is Locked by <Activity>This message is used when no lock is available because a device or device group (7100-WestCoast-1) is already locked by another activity (Trouble ticket 37). The other activity must be approved or discarded to enable the device or device group to be assigned to a new activity. Click OK to close the popup window. Error: No Changes Can Be Made Within the Open Activity, As It Has Been Submitted for ApprovalThis message is used when an activity (Trouble ticket 37) has already been submitted for approval and is in the submitted state. The activity cannot be modified unless it is either rejected by a person with approval authority or discarded. Click OK to close the popup window.
Error: Invalid activity action (action). The workflow type may be changed. Please close and reopen the Firewall MC application window.This message is displayed when multiple users access Firewall MC. If the workflow setting is changed by a second user while you are working in an area of Firewall MC that is not available with that setting, you might receive this message. Close, then reopen, the browser. Firewall MC reopens and you can continue your task. Error: Operation failed. The workflow setup might be changed. Please close and reopen the browserThis message is displayed when multiple users access Firewall MC. If workflow is disabled and a second user enables it, you might receive this message. Close, then reopen, the browser. Firewall MC reopens with workflow enabled and you can continue your task. Error: You must approve or discard all existing activities and deploy all existing jobs before you disable workflowThis message is displayed if you have any open activities or jobs when you try to disable workflow. Approve or discard any open activities and deploy, cancel, or verify that all jobs are being deployed before you disable the workflow feature. Activity Transition Warning MessagesAn activity transition message appears when your action will result in closing the open activity (Edit_Open state), which returns it to the Edit state. While in the Edit state, the changes you made to that activity cannot be deployed— the activity remains a work in progress. This message prompts you to move the activity to a state other than Edit_Open (such as submitted, approved, or rejected) or to continue your action and close the open activity. Actions that generate this message include: The set of options appearing in this message depends on two conditions:
In the following figure, the activity (Trouble ticket 37) has been submitted for approval and is in the submitted state. No further changes can be made to the activity unless it is rejected or approved. Step 1 From the warning popup window, do one of the following:
Step 2 Click OK to perform the selected operation.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|