Table Of Contents
Administration
System Preferences
Set Log Levels
Purge Jobs
Set Report Publish Location
Purge Data
View Purge Details
Schedule Quick Reports
Poll Settings
Load MIB Files
View Audit Trail Log Report
Understanding Audit Trail Log Report
Trap Receiver Groups
Creating a Trap Receiver Group
Editing a Trap Receiver Group
Deleting a Trap Receiver Group
Filtering Trap Receiver Groups
Syslog Receiver Groups
Creating a Syslog Receiver Group
Editing a Syslog Receiver Group
Deleting a Syslog Receiver Group
Filtering Syslog Receiver Groups
Administration
This chapter explains how to perform maintenance and administrative tasks in CiscoWorks HUM. The System Preferences section provides a list of tasks to perform maintenance and administration.
System Preferences
The System Preferences page allow you to perform the following maintenance and administrative tasks in HUM:
•
Set Log Levels
•Purge Jobs
•Set Report Publish Location
•Purge Data
•View Purge Details
•Schedule Quick Reports
•Poll Settings
•Load MIB Files
•View Audit Trail Log Report
•Trap Receiver Groups
•Syslog Receiver Groups
To access the System Preferences page go to LMS Portal and select Health and Utilization Monitor > Admin > System Preferences.
The Current Admin Settings table appears, displaying the administrative settings currently applied.
Table 9-1 describes the fields in the Current Admin Settings table.
Table 9-1 Current Admin Settings Fields
Field
|
Description
|
Job Purge Settings
|
Date and time of next job purge schedule.
For example, 09 Jun 2007, 08 Hrs 10 Mins
|
Report Publish Path
|
Directory path configured to publish HUM reports.
|
Data Purge Settings
|
Displays the schedule of next purge.
For example, 09 Jun 2007, 10 Hrs 10 Mins
|
Quick Report Schedule
|
Enable or Disable any Quick Report generation and configure the frequency for each Quick Report generation.
For example,
•CPU Utilization: Every 1 hour
•Interface Availability: Every 4 hours
•Memory Utilization: Every 30 mins
|
Poll Settings
|
Displays the Poll Settings details.
For example,
•SNMP Timeout: 3 sec
•SNMP Retry: 1
•Failure Notification Interval: 24 hours
•E-Mail ID
|
Set Log Levels
You can use this option to configure and manage log level settings in HUM. You can set log level modes (such as Fatal, Error, Warn, Info, Debug) either for all HUM application modules or at a module level.
HUM application module log files are stored at these locations:
•On Windows: $NMSROOT\log\, where $NMSROOT is the CiscoWorks HUM installation directory.
•On Solaris: /var/adm/CSCOpx/log/
When a log file reaches its maximum file size of 10000 KB, the module backs up the file and starts writing to a new log file. The maximum number of backup log files stored for each application is two.
To set log levels:
Step 1 Go to LMS Portal and select Health and Utilization Monitor > Admin > System Preferences.
Step 2 Select Log Level Settings.
The Set Application Logging Levels dialog box appears.
Step 3 Select the application module from the drop-down list.
The sub-module for the selected application module appear in the Module field.
Step 4 Select an appropriate log level from the Logging Level drop-down list. Changes to HUM modules are logged with appropriate log level message. The logging levels are:
•Fatal
•Error
•Warn
•Info
•Debug
The logging level is set as Info, by default.
Table 9-2 describes the fields in the Set Application Logging Levels dialog box and also provides information on the files to which these logs are stored.
Table 9-2 Set Application Logging Levels Fields
Application Module
|
Sub-module
|
Log File
|
Description
|
All
|
—
|
—
|
Set logging level for the entire system
|
UI
|
Poller Management
|
upm_ui.log
|
Set logging level for User Interface modules
|
Template Management
|
Threshold Setup
|
TrendWatch Setup
|
Report Management
|
Report Job Browser
|
Admin Pages
|
Trap Group Management
|
Syslog Group Management
|
Live Graph
|
HUMLiveGraph.log
|
HUM Portlets
|
HUMPortal.log
|
Device Center
|
upm_ui.log
|
UPMProcess
|
Polling Engine
|
upm_process.log
|
Set logging level for UPMProcess modules
|
Instance Querying
|
Threshold Monitor
|
Device Access Layer
|
Device Management
|
UPMProcess
|
UPMProcess.log
|
PollerUPMProcess
|
upm_process.log
|
TemplateUPMProcess
|
ThresholdUPMProcess
|
IfAdmin Status
|
IfAdminStatus.log
|
JOBS
|
Report Jobs
|
HumReportJob_<JobId>_<InstanceId>.log
For example, HumReportJob_1003_479.log
|
Set logging level for Job modules
|
Summarization Job
|
upm_summarizer.log
|
Purge Job
|
upm_purge.log
|
Failure Tracker Job
|
HumReportJob_<JobId>_<InstanceId>.log
For example, HumReportJob_1003_479.log
|
UPMCTMOperations
|
UPM CTM Operations
|
upm_ctm.log
|
Set logging level for UPMCTMOperations modules
|
Step 5 Click Apply to set the logging level or Reset to apply the default logging level.
A message appears confirming that the logging levels are successfully updated.
Purge Jobs
You can configure HUM to periodically purge job data that you no longer need. This is done using Job Purge.
Job Purge provides a centralized location for you to schedule purging for the following HUM jobs:
•Quick Report Jobs—Purge all Quick Report jobs older than the specified number of days.
•Custom Report Jobs—Purge all Custom Report jobs older than the specified number of days.
•Threshold Report Jobs—Purge all Threshold Report jobs older than the specified number of days.
•Poller Report Jobs—Purge all Poller Report jobs older than the specified number of days.
•Failure Tracker Jobs—Purge all Failure Tracker jobs older than the specified number of days.
•TrendWatch jobs—Purge all TrendWatch jobs older than the specified number of days.
•TrendWatch Summary jobs—Purge all TrendWatch summary jobs older than the specified number of days.
•Summarizer Jobs—Purge all Summarizer jobs older than the specified number of days.
•Data Purge jobs—Purge all Data Purge jobs older than the specified number of days.
•Job Purge jobs—Purge all Job Purge jobs older than the specified number of days.
•Maintenance jobs—Purge all Maintenance jobs older than the specified number of days.
To schedule Job Purge:
Step 1 Go to LMS Portal and select Health and Utilization Monitor > Admin > System Preferences.
Step 2 Select Job Purge.
The Job Purge Settings page appears, displaying Job Purge Schedule dialog box.
Table 9-3 describes the fields in the Job Purge Schedule dialog box.
Table 9-3 Job Purge Schedule Fields
Field/Button
|
Description
|
Scheduling
|
Run Type
|
Specify the type of schedule for job purge:
•Daily—Runs daily at the specified time.
•Weekly—Runs weekly on the day of the week and at the specified time.
•Monthly—Runs monthly on the day of the month and at the specified time. (A month comprises 30 days).
For Daily jobs, the subsequent instances of jobs will run only after the earlier instance of the job is complete.
For example, if you have scheduled a daily job at 10:00 a.m. on November 1, the next instance of this job will run at 10:00 a.m. on November 2, only if the earlier instance of the November 1 job has completed. If the 10.00 a.m. November 1 job has not completed before 10:00 a.m. November 2, then the next job will start only at 10:00 a.m. on November 3.
|
Date
|
Specify the date and time that the job purge is scheduled for.
Select the date by clicking the calendar icon and time from the drop-down list.
|
Purge Policy
|
Days
|
The default setting for purging archived job data is 30 days. That is, job data older than 30 days will be deleted. You can change this value as required. This is a mandatory field.
You can enter only full day value. You cannot enter fractions of days.
|
Apply
(button)
|
Job purge is scheduled at the specified Run Type and Date for the job data older than the days specified in the Days field.
|
Purge Now
(button)
|
Job purge is done immediately for the job data older than the days specified in the Days field.
|
Step 3 Update the necessary fields in the following panes:
•Scheduling
•Purge Policy
See Table 9-3 for the description of fields that appear in the Job Purge Schedule dialog box.
Step 4 Click Apply to schedule job purge or Purge Now to immediately perform job purge.
•If you click Apply, a message appears confirming that the purge settings are applied successfully.
•If you click Purge Now, a message appears confirming that purge is done successfully and the Job ID appears.
You can see the job details in the CiscoWorks Common Services Job Browser at LMS Portal > CiscoWorks Common Services > Server > Admin > Job Browser.
Note We recommend that you wait for any activity currently running in the system to stop before purging jobs.
By default, all Job Purge jobs older than seven days are purged by CiscoWorks HUM.
Set Report Publish Location
CiscoWorks HUM allows you to publish the PDF, HTML and CSV format of all the reports to a directory location of your choice. This is done by setting a default directory path.
Ensure that the casuser is assigned the required write permission privileges to publish the PDF format of the report to the directory path. For more information, see User Guide for CiscoWorks Common Services.
Note The HTML format of the report published in the Report Publish directory will not show graphs. However, you can use the PDF format of the report to view the graphs.
To set a report publish location:
Step 1 Go to LMS Portal and select Health and Utilization Monitor > Admin > System Preferences.
Step 2 Select Report Location.
The Default Report Publish Location page appears, displaying Default Location Settings dialog box.
Table 9-4 describes the field in the Default Location Settings dialog box.
Table 9-4 Default Location Settings Fields
Field/Button
|
Description
|
Report Location
|
Directory path where the PDF, HTML and CSV format of the reports are published.
Use the Browse button to select a directory path.
The Server Side File Browser dialog box is launched. You can select the directory path in this dialog box.
|
Step 3 Click Browse.
The Server Side File Browser dialog box appears.
Step 4 Select the directory path from the Server Side File Browser dialog box.
Step 5 Click OK.
The directory path is displayed in the Report Location field.
Step 6 Click Apply to save the default directory path settings or Cancel to reset the directory path.
Purge Data
You can configure HUM to periodically purge polled data that you no longer need in the database. You can purge data records such as summarization records, Poller failure records, threshold violation records, audit trail records.
CiscoWorks HUM polls the device and stores the polled data in the database. Over a period of time, the polled data occupies a large amount of space in the database.
To prevent this, HUM stores only the last 24 hours data in the database. Background tasks in HUM summarizes this polled data and categorizes the data as 5-minute summarization record, 30-minute summarization record, 3-hour summarization record and 12-hour summarization record.
The summarization of polled data happens every one hour. The summarized data can be purged at regular intervals using the Data Purge option.
Data Purge allows you to schedule purging for the following HUM data records:
•5 Minute Summarization records—Purge all 5-minute summarization data records older than the specified number of days.
•30 Minute Summarization records—Purge all 30-minute summarization data records older than the specified number of days.
•3 Hour Summarization records—Purge all 3-hour summarization data records older than the specified number of days.
•12 Hour Summarization records—Purge all 12-hour summarization data records older than the specified number of days.
•Poller failure records—Purge all failure data records older than the specified number of days.
•Threshold violation records—Purge all threshold violation data records older than the specified number of days.
•Audit trail records—Purge all audit trail data records older than the specified number of days.
•TrendWatch violation records—Purge all trendWatch violation data records older than the specified number of days.
•Status change details records—Purge all status change details data records older than the specified number of days.
Note It is recommended to keep the HUM view in LMS Portal closed, when the data purge job is running.
To schedule Data Purge:
Step 1 Go to LMS Portal and select Health and Utilization Monitor > Admin > System Preferences.
Step 2 Select Data Purge.
The Data Purge Settings page appears, displaying the Data Purge Schedule dialog box.
Table 9-5 describes the fields in the Data Purge Schedule dialog box.
Table 9-5 Data Purge Schedule Fields
Field/Button
|
Description
|
Purge Schedule
|
Run Type
|
Specify the type of schedule to perform Data Purge:
•Hourly—Runs hourly.
•Daily—Runs daily at the specified time.
•Weekly—Runs weekly on the day of the week and at the specified time.
•Monthly—Runs monthly on the day of the month and at the specified time. (A month comprises 30 days).
By default, Daily is set as the default Run Type schedule for Data Purge.
For example, if you have scheduled Run Type as Daily for Data Purge job at 10:00 a.m. on November 1, the next instance of this Data Purge job will run at 10:00 a.m. on November 2, only if the earlier instance of the November 1 job has completed.
If the 10.00 a.m. November 1 Data Purge job has not completed before 10:00 a.m. November 2, then the next Data Purge job will start only at 10:00 a.m. on November 3.
|
Date
|
Specify the date and time that the Data Purge job is scheduled for.
Select the date by clicking the calendar icon and time from the drop-down list.
|
Purge Policy
|
Days
|
The following are the default settings for purging the following data:
•5 Minute's Summarization records—3 days
•30 Minute's Summarization records—15 days
•3 Hour Summarization records—90 days
•12 Hour Summarization records—365 days
•Poller failure records—1 day
•Threshold violation records—180 days
•Audit trail records—90 days
•TrendWatch violation records—180 days
•Status change details records—15 days
The default data purge settings provides optimal performance of CiscoWorks HUM. You can also change the default purge settings as required. However, the performance of CiscoWorks HUM may not be as expected.
You can enter only full days. You cannot enter fractions of days.
This is a mandatory field.
|
Apply
(button)
|
Data purge is scheduled at the specified Run Type and Date for the data older than the days specified in the Days field.
|
Purge Now
(button)
|
Data purge is done immediately for the data older than the days specified in the Days field.
|
Step 3 Update the necessary fields in the following panes:
•Purge Schedule
•Purge Policy
See Table 9-5 for the description of fields that appear in the Data Purge Schedule dialog box.
Step 4 Click Apply to schedule the data purge or Purge Now to immediately perform the data purge.
•If you click Apply, a message appears confirming that data purge settings are applied successfully.
•If you click Purge Now, a message appears confirming that purge is done successfully and the Job ID appears.
You can see the job details in the CiscoWorks Common Services Job Browser at LMS Portal > CiscoWorks Common Services > Server > Admin > Job Browser.
Note By default, all Summarization jobs older than seven days are purged by CiscoWorks HUM.
View Purge Details
CiscoWorks HUM allows you to view the details of the data purged using the option Purge Details.
To view Data Purge details:
Step 1 Go to LMS Portal and select Health and Utilization Monitor > Admin > System Preferences.
Step 2 Select Purge Details.
The Purge Details page appears, displaying Show Purge Details dialog box.
Table 9-6 describes the fields in the Show Purge Details dialog box.
Table 9-6 Show Purge Details Fields
Field
|
Description
|
Details
|
Displays the purge details of the Data Purge job.
The following purge information is displayed:
•Next Data Purge Job scheduled at
•No. of Poll Failure records purged
•No. of Audit Trail records purged
•No. of Threshold Violation records purged
•No. of Polled records purged
•Last Job Purge completed at
•No. of TrendWatch violation records purged
|
Value
|
Details the number of records purged and purge schedule.
|
Schedule Quick Reports
The Quick Report Schedule allows you to enable or disable generation of any of the pre-defined Quick Reports. It also lets you configure the frequency of generating each of the Quick Report. By default, all the pre-defined Quick Reports are enabled and are generated every hour.
By default, the time taken to generate all reports is extended over a specific period of time. If you try to configure the Quick Report to generate more than two Quick Reports at the same time, a message appears, prompting you to change the schedule time of the reports.
It is recommended to stagger the schedule time of the Quick Reports to avoid clash at the time of generation of the reports.
For example, assume that you schedule CPU Utilization and Interface Utilization reports at a frequency of half an hour and the start time of the reports is 9 hrs 30 mins. So in one hour, two reports will be generated for each type of report.
Now if you schedule another report for example, Interface Availability report to start at 10 hrs 00 mins, then this time will clash with the second report generation of the earlier two reports. In this case, an error appears, prompting you to change the schedule time of Interface Availability report.
To schedule Quick Reports.
Step 1 Go to LMS Portal and select Health and Utilization Monitor > Admin > System Preferences.
Step 2 Select Quick Report Schedule.
The Quick Report Schedule dialog box appears.
Step 3 Select Frequency and Start Time for each of the pre-defined Quick reports.
For example, Frequency as 1 hour and Start Time as 04 Hrs 10 Mins.
Table 9-7 describes the fields in the Quick Report Schedule dialog box.
Table 9-7 Quick Report Schedule Fields
Field
|
Description
|
Quick Report Name
|
Name of the Quick Report.
|
Enable
|
Uncheck this check box to disable generation of any Quick Report.
|
Frequency
|
Specify the frequency from the drop-down list.
You can select any of these predefined values. The default option is one hour.
•30 Minutes—Quick Report generated every 30 minutes
•1 Hour—Quick Report generated every 1 hour.
•4 Hours—Quick Report generated every 4 hours.
•8 Hours—Quick report generated every 8 hours.
•12 Hours—Quick Report generated every 12 hours.
•24 Hours—Quick Report generated every 24 Hours.
|
Start Time
|
Specify the time the Quick Report job is scheduled for.
|
Step 4 Click any of the folowing:
•Apply to set the frequency level
•Cancel to cancel the operation.
A message appears confirming that the default time for generating Quick Report is updated successfully.
Poll Settings
CiscoWorks HUM allows you to configure the SNMP timeout and SNMP retries using the Poll Settings option. The SNMP timeout and SNMP retries are based on the device and network response time.
•SNMP timeout is the duration of time that HUM waits for the device to respond before it retries to query the device again.
•SNMP retry is the maximum number of times HUM retries to query the device.
You can also set the notification interval time in case of poller faliures and the e-mail ID to which the notification should be sent.
You can also configure Poll Settings to send the polling failure report as an e-mail.
To configure Poll Settings:
Step 1 Go to LMS Portal and select Health and Utilization Monitor > Admin > System Preferences.
Step 2 Select Poll Settings.
The Poll Settings dialog box appears.
Table 9-8 describes the fields in the Poll Settings dialog box.
Table 9-8 Poll Settings Fields
Field
|
Description
|
Poll Details
|
SNMP Timeout
|
Specify the SNMP timeout interval in seconds.
The default SNMP timeout value is 3 seconds. You can change the default SNMP timeout value to a value between 1 to 15 seconds.
|
SNMP Retries
|
Specify the SNMP retries count.
The default SNMP retry count value is 1. You can set the default SNMP retry count to a value between 1 to 3.
|
Polling Failure
|
Notification Interval
|
Specify the polling failure notification interval.
You can select any of these predefined values. The default option is 6 hours.
•01 - Hour—Polling failures notified every 1 hour.
•06 - Hours—Polling failures notified every 6 hours.
•24 - Hours—Polling failures notified every 24 hours.
•48 - Hours—Polling failures notified every 48 hours.
•Weekly—Polling failures notified every week.
Polling failure notification report is generated periodically based on notification interval. This report contains information on the SNMP polling failures with device details.
|
E-mail ID
|
Enter the e-mail address.
The E-mail address must be in the format: user@domain.com.
The poll failure report is send to the E-mail address based on the Notification Interval.
|
Step 3 Update the necessary fields in the following panes:
•Poll Details
•Polling Failure
See Table 9-8 for the description of fields that appear in the Poll Settings dialog box.
Step 4 Click Apply to update the poll settings or Reset to cancel the poll settings.
A message appears confirming that poll settings are updated successfully.
Load MIB Files
You can load a new MIB file into HUM using the Load MIB option. The new MIB file is compiled and stored in HUM. You can use the new MIB file to create new templates by grouping MIB variables. For more information, see Creating a Template.
You can load MIB files with the file extension .my.
To load a MIB file:
Step 1 Go to LMS Portal and select Health and Utilization Monitor > Admin > System Preferences.
Step 2 Select Load MIB.
The Load MIB dialog box appears.
Table 9-9 describes the field in the Load MIB dialog box.
Table 9-9 Load MIB Fields
Field
|
Description
|
MIB file
|
Use the Browse button to load a MIB file from a directory location.
For example, RFC1213-MIB.my
You are allowed to load a MIB file only from the following directory path:
•In Windows, $NMSROOT\hum\mibmanager\mibcompiler\mibs
•In Solaris, $NMSROOT/hum/mibmanager/mibcompiler/mibs
$NMSROOT is the default CiscoWorks HUM installation directory.
|
Step 3 Click Browse to select the MIB file from a directory location.
The Server Side File Browser dialog box appears.
Step 4 Double-click the MIB file from the directory location.
Step 5 Click Apply to load the MIB file into HUM or Cancel to cancel the operation.
You will be able to load and compile a new MIB file into HUM only when its dependent MIB files are available in the directory location.
For example,
To load and compile RFC1213-MIB, the dependent MIB files for RFC1213-MIB (RFC1155-SMI and RFC-1212) must also be available at the same directory location. If the dependent MIB files are not available, an appropriate error message is displayed and RFC1213-MIB does not compile.
The dependent MIB files are case sensitive, the names of these dependent MIB files should be the same as the MIB files names present in the definition files. Load only version2 MIB.
The following is the list of basic dependent MIBs that will be required for loading other MIBs in HUM:
•RMON2-MIB.my
•BRIDGE-MIB.my
•RFC-1215.my
•INET-ADDRESS-MIB.my
•P-BRIDGE-MIB.my
•Q-BRIDGE-MIB.my
•CISCO-NETFLOW-MIB.my
•CISCO-STACK-MIB.my
•TOKEN-RING-RMON-MIB.my
•RFC-1212.my
•RMOM-MIB.my
•RFC1155-SMI.my
•RFC1213-MIB.my
•SNMP-FRAMEWORK-MIB.my
•CISCO-SMI.my
•ENTITY-MIB.my
•FDDI-SMT73-MIB.my
•CISCO-VTP-MIB.my
•SNMPv2-TC.my
•SNMPv2-SMI.my
•SNMPv2-MIB.my
•SNMPv2-CONF.my
•IF-MIB.my
•IANAifType-MIB.my
To view the list of more dependent MIBs go to:
http://tools.cisco.com/Support/SNMP/do/BrowseMIB.do?local=en&step=2
The compiled MIB file appears in the Show MIB drop-down list in Select MIB Variables page. For more information, see Creating a Template.
View Audit Trail Log Report
CiscoWorks HUM logs all the changes made to the individual HUM modules as Audit Trail messages. These Audit Trail messages are logged and stored in the HUM database.
You can use the Audit Trail Logging option to view the Audit Trail Logging report for all modules, categories and users.
To generate the Audit Trail Logging report:
Step 1 Go to LMS Portal and select Health and Utilization Monitor > Admin > System Preferences.
Step 2 Select Audit Trail Logging.
The Audit Trail Logging dialog box appears.
Table 9-10 describes the fields in the Audit Trail Logging dialog box.
Table 9-10 Audit Trail Logging Fields
Field
|
Description
|
Date Range
|
24 Hours
|
Check the 24 Hours checkbox to generate Audit Trail Logging report for last 24 hours.
|
From
|
Specify the start date and time of your Audit Trail Logging report.
Select the date by clicking the calendar icon and time from the drop-down list.
The From date must be earlier than the current date.
This field is disabled if you have selected the 24 Hours checkbox.
|
To
|
Specify the end date and time of your Audit Trail Logging report.
Select the date by clicking the calendar icon and time from the drop-down list.
The To date must be later than the From date and earlier than the current date.
This field is disabled if you have selected the 24 Hours checkbox.
|
Options
|
Module
|
Select one of the following modules from the drop-down list to generate the Audit Trail Logging report:
•All—The report is generated for all HUM modules.
•Poller Management—The report is generated for the Poller Management module.
•Template Management—The report is generated for the Template Management module.
•Polling Engine—The report is generated for the Polling Engine module.
•Threshold Manager—The report is generated for the Threshold module.
•Job Manager—The report is generated for the Job Manager module.
•Summarization—The report is generated for the Summarization operation module.
•Purge—The report is generated for the Purge operations module.
•Admin—The report is generated for the Admin module.
The drop-down list displays All, by default.
|
Category
|
View the Audit Trail Logging report for each Module category.
See Table 9-11 for the list of categories under each HUM module.
This field is disabled if you have selected All in the Module option.
|
User
|
Select one of the following users from the drop-down list to generate the Audit Trail Logging report:
•All—The report is generated for changes done by All users.
•Admin—The report is generated for changes done by the Admin user.
•System—The report is generated for changes done by the System user.
The drop-down list displays all users, by default.
|
Step 3 Update the necessary fields in the following panes:
•Date Range
•Options
See Table 9-10 for the description of fields that appear in the Audit Trail Logging dialog box.
Step 4 Click OK to launch the Audit Trail Logging report or Cancel to cancel report generation.
The Audit Trail Log Report page appears, displaying the report details. For more information, see Understanding Audit Trail Log Report.
Table 9-11 lists the categories available in each HUM module
Table 9-11 HUM Modules and Categories
Module
|
Category
|
Description
|
Poller Management
|
•All
•Poller Creation
•Poller Modification
•Poller Deletion
•Poller State Change
•Delete Devices From Poller
•Delete Failures from Poller
•Clear Missed Cycles
|
The report is generated for the category selected in the Poller Management module.
If you have selected All, the report generated for all the categories in the Poller Management module.
|
Template Management
|
•Template Creation
•Template Modification
•Template Deletion
•Template Import
•Template Export
|
The report is generated for the category selected in the Template Management module.
If you have selected All, the report generated for all the categories in the Template Management module.
|
Polling Engine
|
Polling Cycle Missed
|
The report is generated for the category selected in the Polling Engine module.
If you have selected All, the report generated for all the categories in the Polling Engine module.
|
Threshold Manager
|
•Threshold Creation
•Threshold Modification
•Threshold Deletion
|
The report is generated for the category selected in the Threshold Manager module.
If you have selected All, the report generated for all the categories in the Threshold Manager module.
|
Job Manager
|
•Job Creation
•Job Updation
•Job Deletion
|
The report is generated for the category selected in the Job Manager module.
If you have selected All, the report generated for all the categories in the Job Manager module.
|
Summarization
|
•Summarization Start
•Summarization End
•Summarization Ended with Failure
|
The report is generated for the category selected in the Summarization module.
If you have selected All, the report generated for all the categories in the Summarization module.
|
Purge
|
•Purge Start
•Purge End
•Purge Ended with Failure
|
The report is generated for the category selected in the Purge module.
If you have selected All, the report generated for all the categories in the Purge module.
|
Admin
|
•Report Location Modification
•Report Location Creation
•Data Purge Policy Modification
•Quick Report Time Modified
•Poll Settings Updated
•Job Purge Job updated
•Job Purge Job Created
•Data Purge Job Updated
•Data Purge Job Created
•Failure Tracker Job Updated
•New MIB Loaded
•Log Level Modified
•Trap Receiver Groups
•Syslog Receiver Groups
|
The report is generated for the category selected in the Admin module.
If you have selected All, the report generated for all the categories in the Admin module.
|
Understanding Audit Trail Log Report
This section describes the fields available in the Audit Trail Log report. The Audit Trail Log report provides information on the changes that occurred in each HUM module.
Table 9-12 describes the fields in the Audit Trail Log report.
Table 9-12 Audit Trail Log Report Fields
Field
|
Description
|
Module
|
Name of the HUM module.
For example, Job Manager
|
Category
|
Name of the module category.
For example, Job Creation
|
Time Stamp
|
Displays the date and time at which the change was made to the HUM module.
For example, Mon, Apr 21 2008, 12:44:08
|
User
|
User who made the change in the HUM module.
For example, admin or system
|
Description
|
Change that occurred in the HUM module.
For example, Poller XYZ Created at Mon, Apr 21 2008, 12:44:08
|
Trap Receiver Groups
CiscoWorks HUM allows you to create SNMP Trap Receiver Groups using the Trap Receiver Groups option.This is group of hosts that receives specified trap notifications, when any TrendWatch or Threshold violation occurs in HUM.
The Trap destination is defined by the IP address or it can be a host name. From the Trap Receiver Groups page, you can create a Trap Receiver Group, modify the configuration of a Trap Receiver Group, and delete a Trap Receiver Group.
To access the Trap Receiver Group page go to LMS Portal and select Health and Utilization Monitor> Admin > System Preferences > Trap Receiver Groups. The Trap Receiver Groups page appears.
Table 9-13 describes the fields in the Trap Receiver Groups.
Table 9-13 Trap Receiver Groups Fields
Field
|
Description
|
Trap Group Name
|
Name of the Trap Receiver Group.
Click on the Name hyperlink to view the details of the Trap Receiver Group created.
|
Number of Receivers
|
Number of Trap Receivers added to the Trap Receiver Group.
|
Create
(button)
|
Creates a Trap Receiver Group. See Creating a Trap Receiver Group.
|
Edit
(button)
|
Modifies an existing Trap Receiver group. See Editing a Trap Receiver Group.
|
Delete
(button)
|
Deletes an existing Trap Receiver Group. See Deleting a Trap Receiver Group.
|
Filter
(button)
|
Filters information based on the criteria that you select from the drop-down
list. The drop-down list contains the following criteria:
· All
· Group Name
See Filtering Trap Receiver Groups
|
You can perform the following tasks from the Trap Receiver Groups dialog box:
•Creating a Trap Receiver Group
•Editing a Trap Receiver Group
•Deleting a Trap Receiver Group
•Filtering Trap Receiver Groups
Creating a Trap Receiver Group
To create a Trap Receiver group
Step 1 Go to the LMS Portal and select Health and Utilization Monitor > Admin > System Preferences > Trap Receiver Groups.
The Trap Receiver Groups page appears.
Step 2 Click Create.
The Create Trap Receiver Group page appears, displaying the Trap Group Configuration dialog box.
Table 9-14 describes the fields in the Trap Group Configuration dialog box.
Table 9-14 Trap Group Configuration
Field
|
Description
|
Group Name
|
Enter the name of the Trap Receiver Group. For example, Trap Receiver Group 1.
The name can contain a mix of alphabets, numerals, and some special characters (such as - _ . # @ $ &).
|
Receiver Details
|
Host
|
Enter the host name or IP address. For example 10.77.201.52
Enter the IP address or hostname of the destination to which the trap message should be delivered.
|
Port
|
Enter the Port Number on which Trap Receiver is listening for traps.
The default port value is 162. This field is optional.
|
Community
|
Enter the community string that appears in the trap message.
The default community string is public. This field is optional.
|
Create
(button)
|
Creates the Trap Receiver Group.
|
Add More
(button)
|
Adds more hosts to the present Group.
|
Cancel
(Button)
|
Cancels the creation of Trap Receiver Group.
|
Step 3 Enter a descriptive name for the Trap Group name in the GroupName field.
Step 4 Enter the IP address or hostname of the destination to which the trap should be delivered in the Host field.
Step 5 Enter the Port Number on which Trap Receiver is listening for traps in the Port field.
Step 6 Enter the community string that appears in the trap message in Community field.
The community string will be displayed as asterisks.
Note You can add as many as five hosts or devices to the Trap Group by default.
To add more than five hosts to the Trap Group,
Step 1 Click Add More to add another host information to the Trap Group. Go to Step 4 to continue.
Step 2 Click Create to create the Trap Group.
Or
Click Cancel to cancel the operation.
The Trap Receiver Group dialog box appears, displaying the Trap Groups.
Related Topics
•Editing a Trap Receiver Group
•Deleting a Trap Receiver Group
•Filtering Trap Receiver Groups
Editing a Trap Receiver Group
You can edit a Trap Receiver Group to update or change the hosts, ports and community string of the selected Trap Receiver Group using the Edit button in the List of Trap Receiver Groups.
You can edit only one Trap Receiver Group at a time. If you select multiple Trap Receiver Groups using the checkbox, the Edit button is disabled. You cannot edit the Trap Receiver Group Name field.
To edit a Trap Receiver Group:
Step 1 Go to LMS Portal and select Health and Utilization Monitor > Admin > System Preferences > Trap Receiver Groups.
The Trap Receiver Groups dialog box appears.
Step 2 Select the Trap Receiver Group by checking the corresponding checkbox against the Trap Receiver Group Name.
Step 3 Click Edit.
The Edit Trap Receiver Group dialog box appears, displaying the earlier settings.
Table 9-15 describes the fields in the Trap Group Configuration dialog box.
Table 9-15 Trap Group Configuration
Field
|
Description
|
Group Name
|
Name of the Trap Receiver Group.
For example, Trap Receiver
|
Receiver Details
|
Host
|
Enter the host name or IP address. For example 10.77.201.52
Enter the IP address or hostname of the destination to which the trap message should be delivered.
|
Port
|
Enter the Port Number on which Trap Receiver is listening for traps.
For example, 162
|
Community
|
Enter the community string that appears in the trap message.
The default community string is public.
|
Update
(button)
|
Updates the Trap Receiver Group.
|
Add More
(button)
|
Adds more hosts to the present Group.
|
Cancel
(Button)
|
Cancels the modification of the Trap Receiver Group.
|
Step 4 Make the necessary changes to the Receiver Details.
To add more receivers to the present configuration,
Step 1 Click AddMore in the Trap Group Configuration dialog box.
Step 2 Make necessary changes to the Receiver Details.
Step 3 Click Update in the Trap Group Configuration dialog box to complete updating the Trap Receiver Group.
Or
Click Cancel to cancel the operation.
The Trap Receiver Group dialog box appears, displaying the Trap Groups.
Deleting a Trap Receiver Group
You can delete one or more Trap Receiver Groups using the Delete button on the List of Trap Receiver Groups dialog box.
You cannot delete a Trap Receiver Group that is associated with any Threshold or TrendWatch. If you want to delete such Trap Receiver Groups, first remove the Trap Receiever Group from the associated Threshold or TrendWatch.
Before a Trap Receiver Group is deleted, you are prompted to confirm the deletion because you cannot restore a Trap Receiver Group that you have deleted from the database.
To delete a Trap Receiver Group:
Step 1 Go to LMS Portal and select Health and Utilization Monitor > Admin > System Preferences > Trap Receiver Group.
The List of Trap Receiver Groups dialog box appears.
Step 2 Select the Trap Group Name by checking the appropriate checkbox.
You can select multiple Trap Receiver Groups by checking their respective checkboxes.
Step 3 Click Delete.
A message appears, prompting you to confirm the deletion,
Step 4 Click OK to delete the Trap Receiver Groups.
Or
Click Cancel to cancel the operation.
If you choose to click OK, a message appears that the Trap Receiver Group is deleted successfully.
The Trap Receiver Groups dialog box appears.
Filtering Trap Receiver Groups
This section describes how you can use the filter option to display the Trap Receiver Group information based on a specific criteria.
To filter a Trap Receiver Groups:
Step 1 Go to LMS Portal and select Health and Utilization Monitor > Admin > System Preferences > Trap Receiver Group.
The List of Trap Receiver Group dialog box appears.
Step 2 Select a criteria for filtering from the drop-down list.
Step 3 Enter the data to be filtered.
Step 4 Click Show.
The List of Trap Receiver Groups dialog box appears, displaying the Trap Receiver Group information based on the filter criteria.
Table 9-16 describes the criteria to filter.
Table 9-16 Trap Receiver Groups Field Description
Filter Criteria
|
Description
|
Group Name
|
Select Group Name and enter the data. You can use either of the following methods to filter by entering:
•Complete Group name
•Any wildcard characters of the Trap Receiver Group name (such as *trap, trap*)
|
Syslog Receiver Groups
CiscoWorks HUM allows you to create Syslog Receiver Groups using the Syslog Receiver Groups option. Syslog Receiver Groups is a group of hosts that receives Syslog messages when any TrendWatch or Threshold violation occurs in HUM.
From the Syslog Receiver Groups page you can create a Syslog Receiver Group, modify the configuration of a Syslog Receiver Group, and delete a Syslog Receiver Group.
To access the Syslog Receiver Group page go to LMS Portal and select Health and Utilization Monitor >Admin > System Preferences > Syslog Receiver Groups. The List of Syslog Receiver Groups dialog appears.
Table 9-17 describes the fields in the Syslog Receiver Groups.
Table 9-17 Syslog Receiver Groups Fields
Field
|
Description
|
Syslog Group Name
|
Name of the Syslog Receiver Group.
For example, Syslog Group
|
Number of Receivers
|
Number of Syslog Receivers added to the Syslog Receiver Group.
|
Create
(button)
|
Creates a Syslog Receiver Group. See Creating a Syslog Receiver Group.
|
Edit
(button)
|
Modifies an existing Syslog Receiver group. See Editing a Syslog Receiver Group.
|
Delete
(button)
|
Deletes an existing Syslog Receiver Group. See Deleting a Syslog Receiver Group.
|
Filter
(button)
|
Filters information based on the criteria that you select from the drop-down
list. The drop-down list contains the following criteria:
· All
· Group Name
See Filtering Trap Receiver Groups
|
Update Facility
(button)
|
Sends the Syslog message to the receiver, based on the facility level selected in the drop-down list. The drop-down list contains the folowing criteria:
•local 0
•local 1
•local 2
•local 3
•local 4
•local 5
•local 6
•local 7
|
You can perform the following tasks from the Syslog Receiver Groups dialog box:
•Creating a Syslog Receiver Group
•Editing a Syslog Receiver Group
•Deleting a Syslog Receiver Group
•Filtering Syslog Receiver Groups
Creating a Syslog Receiver Group
To create a Syslog Receiver group
Step 1 Go to the LMS Portal and select Health and Utilization Monitor > Admin > System Preferences > Syslog Receiver Groups.
The Syslog Receiver Groups dialog appears.
Step 2 Click Create.
The Create Syslog Receiver Group page appears, displaying the Syslog Group Configuration dialog box.
Table 9-18 describes the fields in the Syslog Group Configuration dialog box.
Table 9-18 Syslog Groups Configuration
Field
|
Description
|
Group Name
|
Enter the name of the Syslog Group name. For example, Syslog Group.
The name can contain a mix of alphabets, numerals, and some special characters (such as - _ . # @ $ &).
|
Receiver Details
|
Host
|
Enter the host name or IP address. For example 10.77.201.52
Enter the IP address or hostname of the destination to which the syslog message should be delivered. This IP address should be DNS resolvable.
|
Port
|
Enter the Port Number on which Syslog Receiver is listening for syslog messages.
The default port value is 514. This field is optional.
|
Create
(button)
|
Creates the Syslog Receiver Group
|
Add More
(button)
|
Adds more hosts to the present Group
|
Cancel
(Button)
|
Cancels the creation of Syslog Receiver Group
|
Step 3 Enter a descriptive name for the Syslog Group name in the GroupName field.
Step 4 Enter the IP address or hostname of the destination to which the Syslog messages should be delivered in the Host field.
Step 5 Enter the Port Number on which Syslog Receiver is listening for Syslog Messages in the Port field.
Note You can add as many as five hosts or devices to the Syslog Group by default.
To add more than five hosts to the Syslog Group,
Step 1 Click AddMore to add another host information to the Syslog Group. Go to Step 4 to continue.
Step 2 Click Create to create the Syslog Group.
Or
Click Cancel to cancel the operation.
The Syslog Receiver Group dialog box appears, displaying the Syslog Groups.
Editing a Syslog Receiver Group
You can edit a Syslog Receiver Group to update or change the hosts and ports of the selected Syslog Receiver Group using the Edit button in the List of Syslog Receiver Groups.
You can edit only one Syslog Receiver Group at a time. If you select multiple Syslog Receiver Groups using the checkbox, the Edit button is disabled. You cannot edit the Syslog Receiver Group Name field.
To edit a Syslog Receiver Group:
Step 1 Go to LMS Portal and select Health and Utilization Monitor > Admin>System Preferences > Syslog Receiver Groups.
The Syslog Receiver Groups dialog box appears.
Step 2 Select the Syslog Receiver Group by checking the corresponding checkbox against the Syslog Receiver Group Name.
Step 3 Click Edit.
The Edit Syslog Receiver Group dialog box appears, displaying the earlier settings.
Table 9-18 describes the fields in the Syslog Group Configuration dialog box.
Table 9-19 Syslog Groups Configuration
Field
|
Description
|
Group Name
|
Name of the Syslog Group name.
For example, Syslog Group.
|
Receiver Details
|
Host
|
Enter the host name or IP address. for example 10.77.201.52
Enter the IP address or hostname of the destination to which the Syslog message should be delivered.
|
Port
|
Enter the Port Number on which Syslog Receiver is listening for Syslog messages.
The default port number is 512.
|
Update
(button)
|
Updates the Syslog Receiver Group.
|
Add More
(button)
|
Adds more hosts to the present Group.
|
Cancel
(Button)
|
Cancels the modification of the Syslog Receiver Group.
|
Step 4 Make the necessary changes to the Receiver Details.
To add more receivers to the current configuration:
Step 1 Click AddMore in the Syslog Group Configuration dialog box.
Step 2 Make the necessary changes to the Receiver Details.
Step 3 Click Update in the Syslog Group Configuration dialog box to complete updating the Syslog Receiver Group.
Or
Click Cancel to cancel the operation.
The Syslog Receiver Group dialog box appears, displaying the Syslog Groups.
Deleting a Syslog Receiver Group
You can delete one or more Syslog Receiver Groups using the Delete button on the List of Syslog Receiver Groups dialog box.
You cannot delete a Syslog Receiver Group which is associated with any Threshold or TrendWatch. If you want to delete such Syslog Receiver Groups, first remove the Syslog Receiever Group from the associated Threshold or TrendWatch.
Before a Syslog Receiver Group is deleted, you are prompted to confirm the deletion because you cannot restore a Syslog Receiver Group that you have deleted from the database.
To delete a Syslog Receiver Group:
Step 1 Go to LMS Portal and select Health and Utilization Monitor > Admin > Preferences > Syslog Receiver Group.
The Syslog Receiver Groups dialog box appears.
Step 2 Select the Syslog Group Name by checking the appropriate checkbox.
You can select multiple Syslog Receiver Groups by checking their respective checkboxes.
Step 3 Click Delete.
A message appears, prompting you to confirm the deletion.
Step 4 Click OK to delete the Syslog Receiver Groups.
Or
Click Cancel to cancel the operation.
If you choose to click OK, a message appears that the Syslog Receiver Group is deleted successfully.
The Syslog Receiver Groups dialog box appears.
Filtering Syslog Receiver Groups
You can use the Filter option to display the Syslog Receiver Group information based on a specific criteria.
To filter a Syslog Receiver Groups:
Step 1 Go to LMS Portal and select Health and Utilization Monitor > Admin > System Preferences > Syslog Receiver Group.
The List of Syslog Receiver Group dialog box appears.
Step 2 Select a criteria for filtering from the drop-down list.
Step 3 Enter the data to be filtered.
Step 4 Click Show.
The Syslog Receiver Groups dialog box appears, displaying the Syslog Receiver Group information based on the filter criteria.
Table 9-20 describes the criteria to filter.
Table 9-20 Syslog Receiver Groups Field Description
Filter Criteria
|
Description
|
Group Name
|
Select Group Name and enter the data. You can use any of the following methods to filter by entering:
•Complete Group name
•Any wildcard characters of the Syslog Receiver Group name (such as *Syslog, Syslog*)
|
