Table Of Contents
Administering Campus Manager
Network Discrepancies
Types of Network Discrepancies
Viewing Discrepancy Reports
Customizing Discrepancy Reports
Topology Groups
Topology Groups Concepts
Concept of a Group
Membership Update
Rules Editor
Access Controls
Managing Topology Groups
Using Topology Groups
Getting Started with Topology Groups
System Defined Groups
User Defined Groups
Configuring Job Schedules
Configuring Path Analysis Jobs Scheduling
Using the Configuring Path Analysis Jobs Scheduling Main Window
Configuring Path Analysis Jobs Scheduling
Scheduling Jobs for Exporting User Tracking Data
Using the Scheduling Jobs for Exporting User Tracking Data Main Window
Configuring and Scheduling Jobs for Exporting User Tracking Data
Administering Campus Manager
Network administrators can perform administrative tasks on Campus Manager applications. These include the tasks available under the Administration tab in Campus.
Use the administrative functions of Campus to:
•
Configure the network discrepancies that you would like reported, see Network Discrepancies
•
Create, and manage rule-based custom views, see Topology Groups.
•
Configure scheduling of Path Analysis traces, and archiving of User Tracking data, see Configuring Job Schedules.
Note
You must be assigned the CiscoWorks user role of network administrator or system administrator to perform the tasks described in this chapter.
Network Discrepancies
This feature offers reports on network inconsistencies, anomalies or misconfiguration in the physical and logical layout in the discovered network making it easy to identify configuration errors such as line-speed mismatches on either end of a connection.
Types of Network Discrepancies
Campus can automatically identify two types of discrepancies on network devices:
•
Physical discrepancies
Physical discrepancies include mismatches in line speed, trunk configuration, or duplex mode on two ends of a link; for example, full duplex configured on one side of a link and half duplex configured on the other side.
•
Logical discrepancies
Logical discrepancies include inconsistent or incorrect settings in VTP domains, VLANS, and ATM LANE components; for example, an ATM VLAN that has no entry in the LECS or if there is a VTP client and no VTP server. (if the network uses only transparent nodes in the domain, a VTP server is not required.)
Viewing Discrepancy Reports
Discrepancy reports can be viewed using either of the following methods:
From the Campus drawer on the CiscoWorks desktop,
•
Select Campus Manager > Discrepancy Reports > Physical Discrepancy Report
•
Select Campus Manager > Discrepancy Reports > Logical Discrepancy Report
From a network topology view, (for more information on viewing a network topology, see Open a network topology view., page 2-26).
•
To view physical discrepancies for the entire network, from the LAN Edge or Layer 2 Network View window select Reports > Discrepancies. This report is also available only in the LAN edge and Layer 2 network views. It will show any link-setting mismatches that might need to be corrected on devices. You can also display physical discrepancies for a specific ATM or VTFI domain by selecting the discrepancy filters within the Network View window for that domain.
•
To view logical discrepancies, from the Topology Services main window select Report > Discrepancies. This will detail any errors in VLAN or ATM LANE configuration that might need to be corrected.
Customizing Discrepancy Reports
You can customize the Discrepancy Report to display only those discrepancies about which you want to be notified.
To customize the reports:
Step 1
Select Campus Manager > Administration > Network Discrepancies.
The Configuring Network Discrepancies windows is displayed. You can
Step 2
To include a discrepancy in the Discrepancy Reports, check the box next to it.
Checking all the boxes results in a report displaying all discrepancies in the network.
Step 3
To exclude a discrepancy from the Discrepancy Reports, uncheck the box.
Step 4
Click Apply.
You can use the filters to display discrepancy reports for specific devices, link or network types. This makes it easy to find a particular discrepancy for a particular type. See Figure 7-1 for the list of dicrepancy filters.
Figure 7-1 Network Discrepancy Filters
You can use more than one filter at the same time, but results will vary. When more than one filter in the same top-level category is selected, Boolean OR is used. For example, if you select Duplex, Speed under Link, any link or port that fulfils at least one filter criteria will be displayed in the report. When more than one filter is selected from different top-level categories, Boolean AND is used. For example, if you select both a Link type and a Port type filter from the Physical discrepancy filter, any link that fulfils both filter criteria will be displayed in the report.
Topology Groups
The Topology Groups feature in Campus allows you to create customized views, of the network, in which devices are grouped according to various criteria. A view may be considered as a group of devices or device elements. You can define the criteria (called a rule) which will determine the settings of your custom view. The rule will determine the group of devices to be displayed in the view.
These groups are subsets of Layer 2 maps, the members being defined by a set of rule expressions. In a network with a large number of devices, a Topology Group helps you to perform operations in a subset of the large network.
You can use Topology Groups Administration to manage the Topology Groups in your system.
The following topics provide you with information about:
•
Topology Groups Concepts
•
Managing Topology Groups
•
Using Topology Groups
•
Getting Started with Topology Groups
Topology Groups Concepts
A Topology Group can be thought of as a convenience view that allows you to view a subset of the entire network based on the group rule defined while creating the view.
These views, which are subsets of the Layer 2 views, can be accessed by a user or a set of users. These custom views are generated using a Campus Manager feature called Object Grouping Services (OGS), which helps manage groups of devices. OGS determines the membership of a group by interpreting and applying the rule associated with the group.
Hence, Topology Groups provides multiple benefits:
•
Provides a channel to identify, and view a set of objects corresponding to a view.
•
Facilitates the creation and management of views.
•
Provides you with a way to define convenience views which are a subset of the Layer2 map.
Refer to the following sections for a better understanding of Topology Groups concepts:
•
Concept of a Group
•
Membership Update
•
Rules Editor
Concept of a Group
A group is a named set of devices. The group is characterized by a set of properties such as a name, description, type, access permission, etc., but, most importantly an associated rule. The rule determines the membership of a group, which may change whenever the rule is evaluated.
Topology Groups manages groups in a hierarchical organization and supports subgrouping. Two predefined top level parent groups are available:
•
System Defined Groups
•
User Defined Groups
By default, only the admin user will have necessary privileges to create groups under System Defined Groups. However, the admin user can edit the group to provide write access to other users. Note that access permissions are maintained on a username basis, not a role basis.
If you possess appropriate permissions, you can create subgroups under groups. Hence, each child group is a subgroup of a parent group.
Note the following:
•
The membership of a child group will be a subset of its immediate parent group.
•
Changes in the properties of a parent group, viz., Name, Rule, Evaluation Type, Access Permissions, impacts all child groups under it.
•
When you remove a group, all child groups under it are also removed.
•
When a user is removed from the Campus list of users, the groups created by the user are not removed.
Membership Update
The membership of a group is governed by the rule associated with a group. The changes in the membership is reflected in the network topology view of the group. To view a topology view, select Campus Manager > Topology Views. For more information, see Open a network topology view., page 2-26.
Morevover, while groups with evaluation type Automatic have membership that is current, groups with evaluation type Only Upon User Request retain the membership at creation time or on subsequent re-evaluation.
Two modes of membership updates are available:
•
Automatic
The membership of a group is recomputed automatically on a periodic basis.
Note
If the node or view has been displayed, you must close all of Topology Services and re-open it to display the revised group membership.
•
Only Upon User Request
The membership of the group is recomputed only when an explicit request is made, using the Refresh option. For more information on the refresh option, see Recomputing group membership..
Rules Editor
Every group is defined by a set of rules. You may select an item from the drop down menus, enter a rule in the free-form Rule Text area, or use a combination of the two.
A rule set contains a Boolean combination of individual rule expressions. A rule expression is made of the following components:
Object type
The type of devices which form the group. Rules are evaluated on the list of devices discovered. Campus supports only one object type:
Variable
Any of the attributes of a device. The following variables are available:
•
DeviceLabel
•
DiscoveryStatus
•
HostName
•
ImageVersion
•
IP Subnet
•
IP Address
•
SysObjectID
•
SystemContact
•
SystemLocation
Operator
The operator used in forming a rule. The following operators are available:
•
equals
•
contains
When the variable DiscoveryStatus is used, only one operator is available:
•
= (equals sign)
Value
A free flow operand forming the last part of the rule.
When the variable DiscoveryStatus is used, only the following values are available:
•
Never_Reachable
•
Reachable
•
Currently_Unreachable
Example of a rule
Let us consider a scenario where you need to define a rule for a set of devices in the State Street Campus. The Campus has devices at two locations: Bldg 1 Devices and Bldg 2 Devices.
In this scenario, we will create rules for the System Defined Groups and the User Defined Groups.
Rule for a System Defined Group
•
To create a System Defined Group whose member devices are located in Bldg. 1 Devices, the group rule would be:
:Campus:OGS:Device.SystemLocation equals "Bldg 1 Devices"
where
Variable is SystemLocation
Operator is equals
Value is Bldg 1 Devices
•
Similarly, to create a System Defined Group whose member device IP addresses is 172.20.121.10, the group rule would be:
:Campus:OGS:Device.IpAddress equals "172.20.121.10"
In addition you can use the contains operator to match a value anywhere in the attribute:
:Campus:OGS:Device.IpAddress contains "10"
The above rule, will match devices with IP address like 172.20.10.3, 172.25.3.101 etc.
Rule for a User Defined Group
•
To create an User Defined group whose member devices are labelled Lab Test Setup, the group rule would be:
:Campus:OGS:Device.DeviceLabel equals "Lab Test Setup"
where
Variable is DeviceLabel
Operator is equals
Value is Lab Test Setup
•
Similarly, to create an User Defined group whose member devices have a common system contact person, J Smith Devices, the group rule would be:
:Campus:OGS:Device.DeviceLabel equals "J Smith Devices"
A Composite Rule
A Boolean set of such rules form a composite rule. In the example, to create a group whose member devices are labelled Lab Test Setup, have a common system contact person, J Smith Devices, the composite rule will be:
:Campus:OGS:Device.DeviceLabel equals "Lab Test Setup" AND
:Campus:OGS:Device.SystemContact equals "J Smith Devices"
Access Controls
You are required to explicitly set access permissions for the group you create. You can set permissions for the list of all Campus users. The list displays the default permissions assigned to each of them. As a convenience, you can automatically assign username access to the group based on role.
Campus does not maintain role-based access control, rather it is immediately translated into username-based access control. For example, if while creating a group you set allow read and write access to Network Operators, then at that time all users with Network Operator role are determined and those users given read and write access. If a user is added to the Network Operator list, the new user will not be automatically given access to the group. You would need to edit the group access list to explicitly add the new user to the list.
Managing Topology Groups
From the CiscoWorks desktop, select Campus Manager > Administration > Topology Groups. The Campus Manager Topology Groups Administration page appears (see Figure 7-2).
When you start Topology Groups, the Topology Groups Administration page appears. You can access the Topology Groups Administration wizard, you can choose to:
•
Create a group—define group properties.
•
Edit a previously defined group—update group properties.
•
View group property and membership details.
•
Refresh group membership which recomputes devices in the group.
•
View group details.
•
Delete a view.
Access control to groups is controlled on a username basis.
By default, read permission will be granted to System Defined Groups and read and write permissions will be granted to User Defined Groups. It is expected that the admin user will create groups that are to be generally shared among users under the System Defined Groups folder. For example, the admin may wish to create device groupings based on IP address, subnet, location or contact. The User Defined Groups folder is meant to hold a users private group and/or groups that are more transient in nature.
By default, read permission will be granted to System Defined Groups and read, write, and evaluate permissions will be granted to User Defined Groups.
Figure 7-2 Campus Manager Topology Groups Administration
See Table 7-1 for a description of the elements in the Topology Groups Administration wizard.
Table 7-1 Topology Groups Administration Elements
Item
|
Description
|
Group Selector
|
Displays a hierarchical group selector tree for convenient selection of objects.
|
Content Area
|
Displays attributes of the currently selected group.
|
Wizard Navigation Area
|
Provides quick access to frequently used administration options, like Next, Back, Finish.
|
Using Topology Groups
Table 7-2 lists the main tasks that you can perform using Topology Groups administration. All actions begin from the Topology Groups administration page, unless otherwise specified. For more information about each task, see the Topology Groups online help.
Table 7-2 Topology Groups Administration Tasks
Task
|
Purpose
|
Action
|
Creating a group.
|
For creating groups under System Defined Groups and User Defined Groups.
Access to group creation is based on permission levels. You can create groups under User Defined Groups. By default, only the CiscoWorks admin user can create under System Defined Groups; however, the admin user can modify the access permission to the System Defined Group to enable edit privilege (i.e., create permission) to other Campus usernames.
|
Step 1 of 5: Creating Group Properties
1. Click Create.
2. Enter a unique name in the Group Name field.
3. To copy attributes from a previously selected defined group, click Select Group.
4. To change the parent group under which you want to define the group, click Change Parent.
5. Enter a description for the group in the Description box.
6. Select a membership update mode.
7. Click Next.
|
| |
Creating the group's rule, either using the parameters specified, or manually entering the rule text.
|
Step 2 of 5: Creating Group Rules
You can create groups using either of the following methods:
1. Select desired parameters for Object Type, Variable, and Operator.
2. Enter or select the desired Value for the variable you have selected.
3. Click Add Rule Expression. The rule is added to the Rules Text field.
Or
Enter the rules directly in the Rule Text field.
Note When a rule is entered into the Rule Text field, using either of the above methods, the screen auto-refreshes, and displays a Boolean operator field in the Rule Expression area. You can use the Boolean operators to create composite rules.
• To validate the rules syntax entered, click Check Syntax.
• To view rules defined for the all parent group, click View Parent Rules.
• Click Next.
|
| |
To Specify the devices available to the group. The devices appear in Available Objects or Objects in Group, based on the properties and rules you specified in the previous steps.
Available Objects is the set of objects in the parent group not selected by the child group's rule.
|
Step 3 of 5: Creating Memberships
1. To add the selected devices from the Available Objects list to the Objects in Group list, click Add.
The devices appear in Available Objects or Objects in Group, based on the properties and rules you specified in the previous steps.
2. To remove the selected devices from the Objects in Group list click Remove.
3. Click Next.
|
| |
You can set access permissions for the group from the list of all Campus users. The list displays the default permissions assigned to each of them.
|
Step 4 of 5: Creating Access Controls
1. Click, and select the access permissions for each user from the Permission drop-down list.
2. As a convenience, you can quickly set username permission to the group based on user role by clicking Set Default Permissions.
3. Click Next.
|
| |
You can view a summary of the group attributes.
|
Step 5 of 5: Viewing Create Summary
To create the group according to the properties and rules you specified, click Finish.
|
Modifying a group.
|
You can modify most attributes of a group in the edit mode; an exception being the parent group.
|
1. Select a group, and click Edit.
You can modify the Group Name, Description, and Membership Update Type.
2. Click Next.
3. To modify group rule, edit the rule either using the Rule Expression fields or edit the rule in the Rule Text field.
4. Click Next.
5. To add or remove devices from the Objects in Group, click the Add or Remove buttons, as appropriate.
6. Click Next.
7. To modify access permissions, select the access levels in the Permission field.
8. Click Next.
9. To save modified group attributes, click Finish.
|
Viewing group details.
|
You can view attributes of a group.
|
1. Select Campus Manager > Administration > Topology Groups.
2. Select a group.
Group information is displayed in the right window.
3. To view detailed attributes for the group, click Details.
4. To view the rules attributes of the parent group, click View Parent Rules.
5. To view the list of devices in the group, click Membership Details.
|
Recomputing group membership.
|
This option will recompute the membership of groups by re-evaluating and re-applying the group's rule
|
1. Select Campus Manager > Administration > Topology Groups.
2. Select a group.
3. To recompute the membership of the group, select Refresh.
4. Click Yes to confirm.
|
Removing a group.
|
You can remove a topology group and all child groups under it from the Campus desktop.
|
1. Select Campus Manager > Topology Groups.
2. Select a group.
3. To remove the group, click Delete.
4. Click Yes to confirm.
|
Getting Started with Topology Groups
When Campus is installed, two folders are automatically created under Topology Groups:
•
System Defined Groups
•
User Defined Groups
These groups are provided as a way to categorize groups at your site, and each of these contains a list of all the devices in the ANI Database.
System Defined Groups
System Defined Groups is a top-level container for standard groups that are accessible to and used by most Campus users. By Default, only the Campus admin user has necessary privilege to create groups under the System Defined Groups folder.
Note
A user must have write permission to a group in order to create a child group under it. Although by default, only the Campus admin user has write permission to System Defined Groups, the admin user can grant write privilege to other users by editing the access permission to System Defined Groups.
A system administrator will typically define and configure their own System Defined Groups based on the partitioning requirements of the network. The admin may choose to partition views based on any of the attributes that can be grouped; however, IP address, hostname, sysLocation, and subnet will be common selections.
Notional examples of groups that might appear under System Defined Groups are:
•
Create groups based on system location
•
Create groups based on IP address
•
Create a groups based on DNS name
•
Create a groups based on subnet
Predefined System Defined Groups
The Table 7-3 lists sets of predefined groups available under the System Defined Groups. You can use these predefined groups to categorize devices in your network. For example, you can select Catalyst 6000 Switches to view all such switches in your network.
Table 7-3 Predefined Groups
Device Type
|
Predefined Groups
|
Routers
|
All Access Points All RSMs Cisco 700 Series Routers Cisco 800 Series Routers Cisco 1000 Series Routers Cisco 1400 Series Routers Cisco 1600 Series Routers Cisco 1700 Series Routers Cisco 2500 Series Routers Cisco 2600 Series Routers Cisco 3200 Series Routers Cisco 3600 Series Routers Cisco 3700 Series Routers Cisco 4000 Series Routers Cisco 4500 Series Routers Cisco 4700 Series Routers Cisco 7000 Series Routers Cisco 7500 Series Routers Cisco 10000 Series Routers Cisco 12000 Series Routers Cisco UBR900 Series Routers
|
Switches
|
All ATM Switches Catalyst 1200 Switches Catalyst 1900 Switches Catalyst 2200 Switches Catalyst 2820 Switches Catalyst 2900 Switches Catalyst 2900XL Switches Catalyst 2948G-2980G Switches Catalyst 2950 Switches Catalyst 3000 Switches Catalyst 3500XL Switches Catalyst 3550 Switches Catalyst 3900 Switches Catalyst 4000 Switches Catalyst 4500 Switches Catalyst 5000 Switches Catalyst 5500 Switches Catalyst 6000 Switches All Catalyst L2L3 Switches All DPA 7600 Switches All FastHub Devices All IGX-PBX Switches All LS1010 Switches
|
Other devices
|
All CCM Hosts All Unreachable Devices All Voice Gateways
|
Create groups based on system location
Let us assume that we want to create views which partition our network based on the geography/location of our facilities, as follows:
•
Facility A-1200 Main Street
–
Floor 1 Lab
–
Floor 2 Lab
•
Facility B-510 State Street
–
Test Lab
–
Production Lab
The following rules might be used to create a hierarchy of groups based on sysLocation:
•
Facility A - 1200 Main Street
:Campus:OGS:Device.SystemLocation contains "FacilityA_"
–
Floor 1 Lab
:Campus:OGS:Device.SystemLocation contains "FacilityA_Floor1"
–
Floor 2 Lab
:Campus:OGS:Device.SystemLocation contains "FacilityA_Floor2"
•
Facility B - 510 State Street
:Campus:OGS:Device.SystemLocation contains "FacilityB_"
–
Test Lab
:Campus:OGS:Device.SystemLocation contains "FacilityB_TestLab"
–
Production Lab
:Campus:OGS:Device.SystemLocation contains "FacilityB_ProdLab"
Create groups based on IP address
For example, the following rules might be used to create two groups based on IP address:
:Campus:OGS:Device.IpAddress contains "172.29.252."
:Campus:OGS:Device.IpAddress contains "172.29.253."
Create a groups based on DNS name
For example, the following rules might be used to create two groups based on DNS name:
:Campus:OGS:Device.HostName contains "FacA1-"
:Campus:OGS:Device.HostName contains "FacA2-"
Create a groups based on subnet
For example, the following rules might be used to create two groups based on the IP address subnet:
:Campus:OGS:Device.IP.Subnet equals "172.29.252.32"
:Campus:OGS:Device.IP.Subnet equals "172.29.252.64"
The examples provided here are simple; however the Object Grouping Service allows arbitrarily complex rules to be formed by combining rule expressions with AND, OR or the EXCLUDE operators. This gives the administrator the power and flexibility to create view partitions tailored to the needs of their site.
User Defined Groups
User Defined Groups is a top-level container where individual Campus users can create their own groups. Typically, the groups under User Defined Groups would be used and accessible to the user who created the group, and perhaps a small group of additional users, or these groups may be transient in nature. A notional example would be that Joe Smith wants create a group that contains all devices where he is the System Contact, and he uses the following rule to form this group:
:Campus:OGS:Device.SystemContact equals "Joe Smith" OR
:Campus:OGS:Device.SystemContact equals "jsmith"
Configuring Job Schedules
From the CiscoWorks desktop, select Campus Manager > Administration > Job Schedule. The Configure Path Analysis User Tracking Scheduling window appears.
The window provides tabs for performing two tasks:
•
Configuring Path Analysis Jobs Scheduling
•
Scheduling Jobs for Exporting User Tracking Data
Configuring Path Analysis Jobs Scheduling
This feature provides you with the option of scheduling and archiving Path Analysis traces.
Using the Configuring Path Analysis Jobs Scheduling Main Window
The Configuring Path Analysis Jobs Scheduling Main Window displays the jobs scheduled for Path Analysis. This Main Window is divided into three components: Scheduled Jobs Table, Task Bar, and Scheduled Jobs Details Area. (see Figure 7-3).
Tip
Clicking on a column header in a table sorts the data by that column, and an arrow indicates whether the order is ascending (up arrow) or descending. Clicking again reverses the order. To rearrange the order of the columns click on the column title and drag it to a new position.
Figure 7-3 Configuring Path Analysis Jobs Scheduling Main Window
The Scheduling Jobs window provides several options for working with scheduled jobs, as shown in Table 7-4.
Table 7-4 Configuring Path Analysis Jobs Scheduling Main Window Components
Item
|
Description
|
Usage Notes
|
Scheduled Jobs Table
|
Contains fields providing details about each scheduled job.
|
Click and drag column headings to change the order in which they appear.
|
Task Bar
|
Provides quick access to the following scheduling task options:
• Edit Job
• Delete Job
• Refresh
|
Select a job, and click the desired action in the Task Bar.
|
Scheduled Jobs Details area
|
Contains fields for viewing details of the selected job. In the Edit mode, you can modify the details.
|
None.
|
Schedule Job Type area.
|
Contains fields for scheduling the job.
|
None.
|
Configuring Path Analysis Jobs Scheduling
Table 7-5 describes the main tasks you can perform with Topology Services. For more information about each task, see Path Analysis online help.
Table 7-5 Configuring Path Analysis Jobs Scheduling Tasks
Task
|
Purpose
|
Action
|
Creating a new scheduled job.
|
Allows you to create a new scheduled Path Analysis job.
|
1. From the CiscoWorks desktop, select Campus Manager > Job Schedule > Path Analysis.
2. Click New Job.
3. Enter the name of the job in the Job Name field.
4. Enter the name or IP address of the source of the path in the Source field.
5. Enter the name or IP address of the destination of the path in the Destination field.
6. To specify a time, in minutes, after which the path trace should timeout, enter a value in the Timeout field.
7. To specify the number of archives of the path trace to maintained, enter a value in the No. of Archives field.
8. To start a job immediately, select Start Immediate.
9. To schedule a job to start at a later time, select Start At. Then select Starting Time and Starting Date.
10. To specify that the job be periodically run at a specified time or day, enter a value in the Periodic Schedule field, and select a Time or Day from the drop-down list.
11. Click Apply to schedule the job.
|
Modifying a scheduled job.
|
Allows you to modify the settings for a scheduled Path Analysis job.
|
1. From the CiscoWorks desktop, select Campus Manager > Job Schedule > Path Analysis.
2. To modify the settings of a job, select the job in the Scheduled Jobs Table.
3. Click Edit Job.
4. Modify the settings you would like to change.
5. Click Apply to reschedule the job.
|
Removing a scheduled job.
|
Allows you to remove a scheduled Path Analysis job.
Note If you delete a running job, all subsequent occurrences of the job will be deleted.
|
1. From the CiscoWorks desktop, select Campus Manager > Job Schedule > Path Analysis.
2. To remove a job, select the job in the Scheduled Jobs Table.
3. Click Delete Job.
4. Click Yes to confirm.
|
Updating job details table.
|
Allows you to get the latest updates in the Job Details Table.
|
1. From the CiscoWorks desktop, select Campus Manager > Job Schedule > Path Analysis.
2. Click Refresh.
|
Scheduling Jobs for Exporting User Tracking Data
This feature provides you with the option of scheduling the exporting and archiving User Tracking end-user hosts data and User Tracking IP phone data. Hence, this feature allows you to:
•
Archive data collected from scheduled tasks.
•
View details about the archived data.
The data collected from the scheduled tasks are archived and the users are provided with an interface for viewing the information required from the archives.
Using the Scheduling Jobs for Exporting User Tracking Data Main Window
The Scheduling Jobs for Exporting User Tracking Data Window displays the export jobs scheduled for User Tracking. This Scheduling Jobs window is divided into four components: Scheduled Jobs Table, Task Bar, and Scheduled Jobs Details Area. (see Figure 7-4).
Tip
Clicking on a column header in a table sorts the data by that column, and an arrow indicates whether the order is ascending (up arrow) or descending. Clicking again reverses the order. To rearrange the order of the columns click on the column title and drag it to a new position.
Figure 7-4 Scheduling Jobs for Exporting User Tracking Data Main Window
The Scheduling Jobs window provides several options for working with scheduled jobs, as shown in Table 7-6.
Table 7-6 Scheduling Jobs for Exporting User Tracking Data Main Window Components
Item
|
Description
|
Usage Notes
|
Scheduled Jobs Table.
|
Contains fields providing details about each scheduled job.
|
Click and drag column headings to change the order in which they appear.
|
Task Bar.
|
Provides quick access to the following scheduling task options:
• Edit Job
• Delete Job
• Refresh
|
Select a job, and click the desired action in the Task Bar.
|
Scheduled Jobs Details area.
|
Contains fields for viewing details of the selected job. In the Edit mode, you can modify the details.
|
None.
|
Schedule Job Type area.
|
Contains fields for scheduling the job.
|
None.
|
Configuring and Scheduling Jobs for Exporting User Tracking Data
Table 7-7 describes the main tasks you can perform with the Configuring and Scheduling Jobs. For more information about each task, see Path Analysis online help.
Table 7-7 Configuring and Scheduling Jobs for Exporting User Tracking Data Tasks
Task
|
Purpose
|
Action
|
Creating a new scheduled job.
|
Allows you to create a new scheduled Path Analysis job.
|
1. From the CiscoWorks desktop, select Campus Manager > Job Schedule > User Tracking.
2. Click New Job.
3. Enter the name of the job in the Job Name field.
4. Enter the desired number of export archives to be maintained in the No. of Export Archives field.
|
Creating a new scheduled job.
(continued)
|
|
5. Select the query name to be used from the Query Name drop down list while exporting the User Tracking data.
Note The Query Name drop down list displays all and user defined custom queries.
6. Select the layout name to be used from the Layout Name drop down list while exporting the User Tracking data.
Note The Layout Name drop down list displays all, default, and user defined custom layouts.
7. Enter the directory where you want to export the User Tracking data in the Export Directory on Server field.
8. To specify whether to export the User Tracking end-user host data or the User Tracking IP phone data, select Host Export or Phone Export.
9. To start a job immediately, select Start Immediate.
10. To schedule a job to start at a later time, select Start At. Then select Starting Time and Starting Date.
11. To specify that the job be periodically run at a specified time or day, enter a value in the Periodic Schedule field, and select a Time or Day from the drop-down list.
12. Click Apply to schedule the job.
|
Modifying a scheduled job.
|
Allows you to modify the settings for a scheduled Path Analysis job.
|
1. From the CiscoWorks desktop, select Campus Manager > Job Schedule > User Tracking.
2. To modify the settings of a job, select the job in the Scheduled Jobs Table.
3. Click Edit Job.
4. Modify the settings you would like to change.
5. Click Apply to reschedule the job.
|
Removing a scheduled job.
|
Allows you to remove a scheduled Path Analysis job.
Note If you delete a running job, every subsequent occurrence of the job will be deleted.
|
1. From the CiscoWorks desktop, select Campus Manager > Job Schedule > User Tracking.
2. To remove a job, select the job in the Scheduled Jobs Table.
3. Click Delete Job.
4. Click Yes to confirm.
|
Updating job details table.
|
Allows you to get the latest updates in the Job Details Table.
|
1. From the CiscoWorks desktop, select Campus Manager > Job Schedule > User Tracking.
2. Click Refresh.
|