|
|
This chapter contains the following major sections:
IPM source routers are the routers from which you want to initiate operations for measuring network performance statistics. Each source router must contain the Cisco IOS SAA feature and an SNMP agent.
Information on working with source routers is provided in the following subsections:
To view a list of configured source routers:
Step 2 Click Sources. The Source Configuration window (Figure 4-2) is displayed which contains a list of configured source routers.
 |
Note An SNA device can be only a target, not a source. |
The Source Configuration window displays source routers that you have already configured. From this window, you can add a new source router, change the configuration of an existing source, or delete an existing source.
The Source Properties window allows you to view the properties of a defined source router.
To view source router properties:
Step 2 Select View > Properties. The Properties Viewer window (Figure 4-3) is displayed. By default, the Collector Properties window is displayed within the Properties Viewer window.
Step 3 Click Source. The Source Properties window (Figure 4-4) is displayed.
For information on these fields, refer to the "Source Properties Window" topic in the online help.
To add a new source router:
For information on configuring SNMP on the source router, see the "Configuring Your Routers to Send SAA-Related Traps" section in the "Preparing to Install" chapter of the Cisco Internetwork Performance Monitor Installation Guide.
Step 2 From the IPM Main window, select Edit > Configuration. The Configuration window (Figure 4-1) is displayed. By default, the Source Configuration window is displayed within the Configuration window.
Step 3 In the Hostname or IP Address field, enter the IP address or host name of the router on which the source resides. This host name can be from 1 to 64 characters in length.
Step 4 In the Read Community field, enter the SNMP community name for read access to the information maintained by the SNMP agent on the source router. This value can be from 1 to 32 characters in length. The default value is public.
Step 5 In the Write Community field, enter the SNMP community name for write access to the information maintained by the SNMP agent on the source router. This value can be from 1 to 32 characters in length.
Step 6 In the Name field, enter a name to assign to the source router.
Step 7 (Optional) In the Description field, enter a brief description of the source router.
Step 8 Click Add. IPM attempts to locate the router and determine whether or not it is SNMP enabled with the correct community string. If the router is successfully located, IPM adds it to the IPM database. If IPM cannot reach the router, IPM displays an error message.
|
Note If the hostname cannot be resolved by standard address resolution techniques, then IPM displays the IP address for the source router instead of a host name. |
Step 9 Click OK to close the Configuration window and return to the IPM Main window.
For information on using a seed file to add source routers to IPM, see the "Adding Source Routers Using a Seed File" section. For information on modifying or deleting source routers, see the "Working with Source Routers" section.
The following sections provide information on creating a source router seed file:
|
Note Use the same delimiter to separate all the components for a source router definition. If any component of the source router seed file contains a space in the name, then you must use either a comma or a semi colon as the delimiter between all the components for that source router. |
A sample source router seed file is shown below:
###############################################################################
#
# This file has example definitions for source routers.
#
# Comments starts with the "#" character
#
# The format of the file is as follows:
#
# <command><delim><hostname[|aliasname]><delim><read community><delim><write community>
#
# <delim> characters are " ;,\t" "space,semicolon,comma,tab"
#
# <hostname[|aliasname]> : Hostname followed by optional aliasName
# separated with a `|' ("vertical bar")
#
# The valid commands are 'a|A' for add; 'd|D' for delete; 'u|U' for update;
#
# WARNING: Please assure the permissions on these files
# do not allow read access to all users due to
# the inclusions of SNMP community names.
#
###############################################################################
#a router1 public private
#a router2 santa claus
#a router3.foobar.com open secret
Table 4-1 provides information about each of the components required for defining source routers in a source router seed file.
| Component | Description |
|---|---|
Command | Defines whether the source router is added to the IPM database, removed from the IPM database, or an existing source router entry in the IPM database is updated from the source router seed file. The following values are possible: A or a---Adds the source router to the IPM database. D or d---Removes the source router from the IPM database. U or u---Updates an existing source router entry in the IPM database from the information provided in the source router seed file. |
Host Name | IP address or host name of the router on which the source resides. The host name can be from 1 to 64 characters in length. You can also include an optional alias name for the router by adding a vertical bar (|) and the alias name after the host name. |
Read Community | SNMP community name for read access to the information maintained by the SNMP agent on the source router. This value can be from 1 to 32 characters in length. This value is usually set to public. |
Write Community | SNMP community name for write access to the information maintained by the SNMP agent on the source router. This value can be from 1 to 32 characters in length. This value is usually set to private. |
To create a source router seed file:
Step 2 Save the source router seed file as a text file in the /opt/CSCOipm/etc/source directory. A sample source router seed file named srcfile is provided.
To load source routers from a source router seed file into IPM:
Step 2 In the Seed File Type field, select Source as the type of seed file to load.
Step 3 In the Seed File Name field, type the name of the source router seed file.
Step 4 Click OK. The source routers that you defined in the source router seed file are added to the IPM database. When you access the Source Configuration window, the changes that you made to the source routers in the seed file are displayed.
 |
Tips If you do not remember the name of the source router seed file that you want to load, you can view a list of available source router seed files from the Seed File window. Select Source as the Seed File Type and click View. |
For information on listing, viewing, editing, or loading seed files from the command line, see the "IPM Command Reference" appendix.
You can delete source routers that you no longer need. You can delete more than one source router at a time.
|
Note If a source router has been configured as part of one or more collectors, then you must delete the collectors before you can delete the source router. |
Step 2 Click Delete.
Step 3 When the confirmation box appears, click Yes. The selected source routers are deleted from the IPM database.
IPM targets are destination devices for which you want to gather network performance statistics. A target can be any IP-addressable device, a Cisco router running the SAA responder, or an SNA host.
|
Note The SAA responder is only supported in Cisco IOS software release 12.0(5)T or later. |
Information on working with target devices is provided in the following subsections:
To view a list of defined targets:
Step 2 Click Targets. The Target Configuration window (Figure 4-6) is displayed which contains a list of configured target devices.
The Target Configuration window displays a list of all devices defined as IPM targets. From this window, you can define a new target, modify an existing target, or delete a target.
The Target Properties window allows you to view the properties of a defined target.
To view target properties:
Step 2 Select View > Properties. The Properties Viewer window (Figure 4-3) is displayed. By default, the Collector Properties window is displayed within the Properties Viewer window.
Step 3 Click Target. The Target Properties window (Figure 4-7) is displayed.
For information on these fields, refer to the "Target Properties Window" topic in the online help.
IPM targets are destination devices for which you want to gather data. A target can be any IP-addressable device, a Cisco SAA responder, or an SNA host.
Step 2 Click Targets. The Target Configuration window (Figure 4-6) is displayed.
Step 3 In the Target Type field, select the protocol type to be used with this target. The possible values are:
Step 4 If the target type is IP, enter the host name or IP address of the target device in the Host Name or IP Address field.
Step 5 If the target type is Cisco SAA Responder, enter the host name or IP address of the target device in the Host Name or IP Address field. In the Read Community field, enter the SNMP community name for read access to the information maintained by the SNMP agent on the target device. The default value is public.
Step 6 If the target type is SNA, enter the SNA host name of the target device in the PU Name field.
Step 7 In the Name field, enter a name to assign to the target. By default, this field matches the Hostname, IP Address, or PU Name field, but you can modify the name.
Step 8 (Optional) In the Description field, enter a brief description of the target.
Step 9 Click Add. IPM adds the newly defined target to the IPM database.
|
Note If you specify an IP address instead of a hostname and that IP address cannot be resolved by standard address resolution techniques, then IPM assumes that the IP address is valid and does not resolve to a host name. |
Step 10 Click OK to close the Configuration window and return to the IPM Main window.
For information on using a seed file to add targets to IPM, see the "Adding Targets Using a Seed File" section. For information on modifying or deleting targets, see the "Working with Target Devices" section.
The following sections provide information on creating a target seed file:
|
Note Use the same delimiter to separate all the components for a target definition. If any component of the target seed file contains a space in the name, then you must use either a comma or a semi colon as the delimiter between all the components for that target. |
A sample target seed file is shown below:
###############################################################################
#
# This file has example definitions for target devices
#
# Comments starts with the "#" character
#
# The format of the file is as follows:
#
# <command><delim><target type><delim><hostname [<aliasname.]><delim><read community>
#
# <delim> characters are " ;,\t" "space,semicolon,comma,tab"
#
# <hostname[|aliasname]> : Hostname followed by optional aliasName
# separated with a `|' ("vertical bar")
#
# The valid commands are 'a|A' for add; 'd|D' for delete; 'u|U' for update;
#
# The <target type> is 1 for IP; 2 for CISCO_SAA_RESPONDER; 3 for SNA
#
# For CISCO_SAA_RESPONDER target type, read community string is required.
# and the IOS RTR(SAA) responder must be enabled
#
# WARNING: Please assure the permissions on these files
# do not allow read access to all users due to
# the inclusions of SNMP community names.
#
###############################################################################
#a 1 www.foobar.com
#a 2 ios_router.foobar.com public
#a 3 sna_target.foobar.com
#a 1 server1
#a 2 router1 public
Table 4-2 provides information about each of the components required for defining targets in a target seed file.
| Component | Description |
|---|---|
Command | Defines whether the target is added to the IPM database, removed from the IPM database, or an existing target entry in the IPM database is updated from the target seed file. The following values are possible: A or a---Adds the target to the IPM database. D or d---Removes the target from the IPM database. U or u---Updates an existing target entry in the IPM database from the information provided in the target seed file. |
Target Type | The protocol type to be used with this target. Specify one of the following values: 1---IP. Requires an IP address or host name. 2---Cisco SAA Responder. Requires an IP address or host name and read community string. 3---SNA LU0, SNA LU2, or SNA SSCP-LU. Requires a hostname. |
Host Name | IP address or host name of the target device. The host name can be from 1 to 64 characters in length. You can also include an optional alias name for the router by adding a vertical bar (|) and the alias name after the host name. |
Read Community | For Cisco SAA Responder, include the SNMP community name for read access to the information maintained by the SNMP agent on the router. This value can be from 1 to 32 characters in length. This value is usually set to public. |
Step 2 Save the target seed file as a text file in the /opt/CSCOipm/etc/target directory. A sample target seed file named trgtfile is provided.
To load targets from a target seed file into IPM:
Step 2 In the Seed File Type field, select Target as the type of seed file to load.
Step 3 In the Seed File Name field, type the name of the target seed file.
Step 4 Click OK. The targets that you defined in the target seed file are added to the IPM database. When you access the Target Configuration window, the changes that you made to the targets in the seed file are displayed.
|
Tips If you do not remember the name of the target seed file that you want to load, you can view a list of available target seed files from the Seed File window. Select Target as the Seed File Type and click View. |
For information on listing, viewing, editing, or loading seed files from the command line, see the "IPM Command Reference" appendix.
You can delete targets that you no longer need. You can delete more than one target at a time.
|
Note Once you have associated a target with a collector, you cannot delete the target without first deleting the collector with which it is associated. |
Step 2 Click Delete.
Step 3 When the confirmation box appears, click Yes. The selected targets are deleted from the IPM database.
An IPM operation is an alias for a set of parameters used in measuring performance. Information on working with operations is provided in the following subsections:
To view a list of defined operations:
Step 2 Click Operations. The list of operations expands to show the types of operations that have been defined.
Step 3 Click an operation type. The Operation Configuration window (Figure 4-8) shows the default configuration for the selected operation type and the list of operations expands to show all defined operation of that type.
The Operation Configuration window displays a list of all defined operations. From this window, you can define a new operation, modify an existing operation, or delete an existing operation.
|
Note When you install IPM, a group of predefined operations are provided. The predefined operations cannot be modified. However, you can use them as examples for creating your own operations. For a listing and brief description of these operations, refer to the "Defining a Collector" section. |
The Operation Properties window allows you to view the properties of a defined operation.
To view operation properties:
Step 2 Select View > Properties. The Properties Viewer window (Figure 4-3) is displayed. By default, the Collector Properties window is displayed within the Properties Viewer window.
Step 3 Click Operation. The Operation Properties window (Figure 4-9) is displayed.
For information on these fields, refer to the "Operation Properties Window" topic in the online help.
An IPM operation is an alias for a set of parameters used for measuring performance between source router and a target device.
To define an operation:
Step 2 Click Operations. The list of operations expands to show the types of operations that have been defined.
Step 3 Click an operation type. The Operation Configuration window (Figure 4-8) shows the default configuration for the selected operation type and the list of operations expands to show all defined operation of that type.
Step 4 Set the options for the operation that you want to define. Detailed information on defining operations to measure performance for DHCP, DLSw, DNS, IP, SNA, TCP, UDP, and Voice over IP is provided in the "Using IPM to Measure Network Performance" chapter.
Step 5 Click OK to complete the definition of a monitoring operation. IPM redisplays the Operation window and the new operation is added to the list of defined operations.
From the Operation Configuration window, you can configure thresholds and event notifications on the source router.
To set thresholds and generate alerts using an operation:
Step 2 In the Generate Action Event field, select one of the algorithms to be used by IPM to calculate threshold violations. The following values are possible:
Step 3 In the Rising field, enter a rising threshold, in milliseconds. Valid values are between 1 and 99999 ms. The default is 5000 ms. When the latency exceeds the rising threshold, the collector uses the algorithm specified in Generate Action Event to determine if a threshold violation has occurred. If a violation occurs, the action defined in Action Event Type is taken.
Step 4 In the Falling field, enter a falling threshold, in milliseconds. Valid values are between 0 and 99999 ms. The default value is 3000 ms. When the latency falls below the falling threshold, the threshold is reset. Only one event will be generated for the time the latency is above the rising threshold.
Step 5 If you specified a Generate Action Event of Consecutive, X of Y, or Average, enter a value in the X field to be used in calculating the threshold. Valid values are 1 to 16. The default is 5.
Step 6 If you specified a Generate Action Event of X of Y, enter a value in the Y field for the Y value to be used in calculating the threshold. Valid values are 1 to 16. The default is 5.
Step 7 In the Timeout Value field, enter the amount of time, in milliseconds, for the collector to wait for a response to its echo operation. When a timeout occurs, the Timeout counter is incremented. The timeout value must be less than the specified sample interval. Valid values are between 0 and 604800 ms. The default value is 4000 ms.
Step 8 Enable the Timeout option to check for latency reporting operation timeouts based on the timeout value configured for the collector. If you enable the Timeout option, the action (specified in Action Event Type) is taken when a timeout occurs or is cleared on this collector.
Step 9 Enable the Connection Lost option to check for connection loss in connection-oriented protocols (LU0, LU2, and SSCP). If you enable the Connection Lost option, the action specified in Action Event Type is taken when a loss of connection or a reconnection after a loss occurs on this collector.
Step 10 In the Action Event Type field, select the action or combination of actions for the collector to perform when the Timeout option is enabled, the Connection Lost option is enabled, or when a threshold is violated. For the action type to occur for threshold events, the threshold type must be defined to any value other than Never. The possible actions are:
Step 11 Click OK to complete the operation definition. IPM adds the new or updated operation to the IPM database.
You can delete operations that you no longer need.You can delete more than one operation at a time.
|
Note You cannot delete the default operations provided with IPM. |
Step 2 Click Delete.
Step 3 When the confirmation box appears, click Yes. The selected operations are deleted from the IPM database.
Information on working with collectors is provided in the following subsections:
All of the collectors that you have defined are listed in the IPM Main window (Figure 4-10). Any collectors that have start dates and times earlier than the current date and time and end dates and times later than the current date and time are considered active collectors.
The following status information is displayed about each collector in the IPM Main window:
|
Tips You can sort the collector information displayed in the IPM Main window by clicking on the column titles. By default, the information is sorted based on collector name. However, you might find it useful to sort the information based on start time, target, or operation type. |
To view detailed information about a defined collectors:
Step 2 Select View > Properties. The Properties Viewer window (Figure 4-3) is displayed. By default, the Collector Properties window is displayed within the Properties Viewer window.
|
Note To display the Collector Properties window, if it is not displayed by default, click Collector. |
For information on these fields, refer to the "Collector Properties Window" topic in the online help.
|
Note After a collector starts running, you cannot change its attributes. |
To define a new collector:
Step 2 Click Collectors. The Collector Configuration window is displayed within the Configuration window.
Step 3 In the Name field, type a name to assign to the collector
Step 4 (Optional) In the Description field, enter a brief description of the collector.
Step 5 In the Collector Type field, enable the Collect Statistics option to gather data and store it in the IPM database for future analysis. If this option is not enabled, you can view data in real-time only. Network performance data is not stored in the IPM database. By default the Collector type is set to collect statistics.
Step 6 Do one of the following:
|
Note For DNS and DHCP, a target is not required. |
For a brief description of the predefined operations provided with IPM, see Table 2-1.
Step 10 Click OK. IPM adds the newly defined collector to the IPM database.
The following sections provide information on creating a collector seed file:
|
Note Use the same delimiter to separate all the components for a collector definition. If any component of the collector seed file contains a space in the name, then you must use either a comma or a semi colon as the delimiter between all the components for that collector. |
A sample collector seed file is shown below:
############################################################################### # # This file has example definitions for collectors # # Comments starts with the "#" character # # The format of the file is as follows: # # <command><delim><collName><delim><source><delim><target><delim> # <operation><delim><startTime><delim><duration><delim><collType> # # <delim> characters are " ;,\t" "space,semicolon,comma,tab" # # The valid commands are 'a|A' for add, 'd|D' for delete, 'u|U' for update; # # <collType> is M for Monitored, S for Statistical # # <startTime> is in the format MM:DD:YYYY:hh:mm:ss # # <startTime> = 1 -> start time will be now # # <duration> is in number of hours # # <duration> = 0 -> Forever # # <startTime> = zero and <duration> = zero -> ON_DEMAND collector # ############################################################################### #a coll1 router1.cisco.com target1 DefaultIpEcho 1 12 M #a coll2 router1.cisco.com target2 DefaultUDPEcho 1 0 S #a coll3 router1.cisco.com target3 DefaultJitter 1 24 M #a coll4 router1.cisco.com target4 DefaultDLSw 0 36 S #a coll5 router2.cisco.com target1 DefaultSnaLu0Echo 1 6 M #a coll6 router2.cisco.com target2 DefaultSnaLu2Echo 1 12 M #a coll7 router2.cisco.com target3 DefaultSnaRuEcho 1 24 S #a coll8 router2.cisco.com target2 DefaultIpPathEcho 10:20:1999:01:00:00 36 M
Table 4-3 provides information about each of the components required for defining collectors in a collector seed file.
| Component | Description |
|---|---|
Command | Defines whether the collector is added to the IPM database, removed from the IPM database, or an existing collector entry in the IPM database is updated from the collector seed file. The following values are possible: A or a---Adds the collector to the IPM database. D or d---Removes the collector from the IPM database. U or u---Updates an existing collector entry in the IPM database from the information provided in the collector seed file. |
Collector Name | Name of the collector. |
Source | Name of the defined source router to use for this collector. The source router must already be defined in IPM or in a source router seed file. |
Target | Name of the defined target device to use for this collector. The target device must already be defined in IPM or in a target seed file. |
Operation | Name of the defined operation to use for this collector. The operation must already be defined in IPM. |
Start Time | Date and time at which the collector will start collecting data. The following values are possible: 1---Starts the collector immediately after it is configured. Date & Time---Starts the collector at the date and time that you specify. The Start Time must be specified in the format If the Start Time and Duration both have values of 0, then the collector is treated as a collector defined to run on demand. |
Duration | Length of time, in hours, that the collector is configured to run. The following values are possible: 0---Starts the collector to run continuously until you stop it by selecting Edit > Stop from the IPM Main menu. 1-N---Stops the collector after the specified number of hours have elapsed. If the Start Time and Duration both have values of 0, then the collector is treated as a collector defined to run on demand. |
Collector Type | Defines whether or not the collector stores statistics in the IPM database. The following values are possible: S---Statistical. The collector gathers network performance statistics on an hourly basis and stores the collected data in the IPM database. M---Monitored. The collector monitors network performance in real time without storing statistics in the IPM database. |
To create a collector seed file:
Step 2 Save the collector seed file as a text in the /opt/CSCOipm/etc/collector directory. A sample collector seed file named collfile is provided.
To load collectors from a collector seed file into IPM:
Step 2 In the Seed File Type field, select Collector as the type of seed file to load.
Step 3 In the Seed File Name field, type the name of the collector seed file.
Step 4 Click OK. The collectors that you defined in the collector seed file are added to the IPM database and displayed in the IPM Main window.
|
Tips If you do not remember the name of the collector seed file that you want to load, you can view a list of available collector seed files from the Seed File window. Select Collector as the Seed File Type and click View. |
For information on listing, viewing, editing, or loading seed files from the command line, see the "IPM Command Reference" appendix.
|
Note Delete a collector also removes the SAA entry from the router. |
To delete an IPM collector:
Step 2 Select Edit > Delete.
Step 3 When the confirmation box appears, click Yes. The selected collectors are deleted from the IPM Main window.
For collectors that are using a statistical operation, IPM gathers network performance and error statistics from the source router once every hour and stores the data in the IPM database. The collected hourly data is used to calculate daily, weekly, and monthly data. By default, IPM stores the collected data for the following periods of time:
IPM provides a database preferences file that allows you to define the business hours and days. Defined business hours are used in determining the daily, weekly, and monthly averages while business days are used in determining the weekly and monthly averages. The database preferences file also allows you to set the length of time that daily data is retained in the database.
Information about viewing and changing the database preferences is provided in the following sections:
To display the values currently set in the database preferences file, enter the following commands:
# cd /opt/CSCOipm/bin # ./ipmDbPref.sh
To change the IPM database preferences:
|
Note You might want to make a back up copy of the database preferences file (ipmDbPref.conf) before modifying it. |
Step 2 To change the number of days that daily network performance statistics are stored, modify the following line:
ipm_daily_stats_life=180
Step 3 To set the business hours to be used in calculating averages, you must turn on or off the appropriate hour interval. The day is divided into one-hour increments that start at 0:00 a.m. (ipm_business_hour_0) and end at 11:59 p.m. (ipm_business_hour_23=0). For the hours that you want included in averages, set the hour interval value to 1.
For example, to store collected statistics over a business day that runs from 8:00 a.m. to 5:00 p.m., you would use the following setting:
ipm_business_hour_0=0 ipm_business_hour_1=0 ipm_business_hour_2=0 ipm_business_hour_3=0 ipm_business_hour_4=0 ipm_business_hour_5=0 ipm_business_hour_6=0 ipm_business_hour_7=0 ipm_business_hour_8=1 ipm_business_hour_9=1 ipm_business_hour_10=1 ipm_business_hour_11=1 ipm_business_hour_12=1 ipm_business_hour_13=1 ipm_business_hour_14=1 ipm_business_hour_15=1 ipm_business_hour_16=1 ipm_business_hour_17=0 ipm_business_hour_18=0 ipm_business_hour_19=0 ipm_business_hour_20=0 ipm_business_hour_21=0 ipm_business_hour_22=0 ipm_business_hour_23=0
Step 4 To set the business days used for calculating weekly and monthly averages, you must turn on or off the appropriate day. Each day of the week is represented by a number as follows:
ipm_business_day_0ipm_business_day_1ipm_business_day_2ipm_business_day_3ipm_business_day_4ipm_business_day_5ipm_business_day_6For the days that you want set as business days, set the day to a value of 1. Days with a value of 0 are not counted as business days.
For example, to set the business days to Monday through Friday, you would use the following setting (the default setting):
ipm_business_day_0=0 ipm_business_day_1=1 ipm_business_day_2=1 ipm_business_day_3=1 ipm_business_day_4=1 ipm_business_day_5=1 ipm_business_day_6=0
Step 5 Save your changes to the IPM database preferences file.
Step 6 Run the database utility program to load your preferences using the following commands:
# cd /opt/CSCOipm/bin # ./ipmDbPref.sh -s
The contents of the default IPM database preferences file (ipmDbPref.conf) are shown in the following example. This file is stored in the /opt/CSCOipm/etc directory.
# # (C) Copyright 1998 Cisco Systems, Inc. # All Rights Reserved # # IPM Database Preferences # # This file contains the IPM Database Preferences used for # data aging and reduction. # # To change these values, update the values below and run the command: # ipmDbPref.sh -s # # To display the values currently set in the database, run the command: # ipmDbPref.sh # # NOTE: Changing these parameters has no effect on daily, weekly and # monthly data that has already been calculated. Only new daily, weekly # and monthly data will use these new settings. # # The hourly data within IPM is always kept for 32 days. # The weekly and monthly data is always kept forever. # # The ipm_response_life setting determines the number of days that IPM stores # daily latency data. You can change this to any number of days. ipm_response_life=180 # # # The ipm_error_life setting determines the number of days that IPM stores # daily error data. You can change this to any number of days. ipm_error_life=180 # # # The ipm_business_hour_x settings describe which hours of the day IPM will use # when generating daily, weekly and monthly reports. Each hour of the day, # starting with 0 (midnight) and going through 23 (11 PM) may be included in # the reports. However, you will probably want to restrict the hours included # in the reports to normal business hours. # # The hours are defined as starting at 0 minutes past the hour, and going through # 59 minutes and 59 seconds past the hour. # # Set the value of each ipm_business_hour_x parameter to either 0 or 1. # A value of 1 indicates that IPM will use this hour of the day when generating # daily, weekly and monthly reports. A value of 0 indicates that IPM will ignore # this hour of the day when generating daily, weekly and monthly reports. # For example, setting 'ipm_business_hour_9=1' will cause all data collected between # 9:00AM and 9:59AM on business days to be included in reports. # ipm_business_hour_0=0 ipm_business_hour_1=0 ipm_business_hour_2=0 ipm_business_hour_3=0 ipm_business_hour_4=0 ipm_business_hour_5=0 ipm_business_hour_6=0 ipm_business_hour_7=0 ipm_business_hour_8=1 ipm_business_hour_9=1 ipm_business_hour_10=1 ipm_business_hour_11=1 ipm_business_hour_12=1 ipm_business_hour_13=1 ipm_business_hour_14=1 ipm_business_hour_15=1 ipm_business_hour_16=1 ipm_business_hour_17=1 ipm_business_hour_18=1 ipm_business_hour_19=1 ipm_business_hour_20=0 ipm_business_hour_21=0 ipm_business_hour_22=0 ipm_business_hour_23=0 # # # The ipm_business_day settings describe which days of the week IPM will use # when generating weekly and monthly reports. Each day of the week is represented # by a number: # # Sunday is 0 # Monday is 1 # Tuesday is 2 # Wednesday is 3 # Thursday is 4 # Friday is 5 # Saturday is 6 # # Set the value of each ipm_business_day_x parameter to either 0 or 1. # A value of 1 indicates that IPM will use this day of the week when generating # weekly and monthly reports. A value of 0 indicates that IPM will ignore this # day of the week when generating weekly and monthly reports. # For example, setting 'ipm_business_day_2=1' will cause all data collected on # Tuesday during business hours to be included in reports. # ipm_business_day_0=0 ipm_business_day_1=1 ipm_business_day_2=1 ipm_business_day_3=1 ipm_business_day_4=1 ipm_business_day_5=1 ipm_business_day_6=0
The IPM database is automatically backed up every morning at 1:00 a.m. If your database file is corrupted, you can restore the data in the IPM database from the previous day's backed-up data.
To restore the IPM database from a previous back up, enter the following commands:
# cd /opt/CSCOipm/bin # ./ipm dbrestore
Posted: Sun Apr 16 13:07:50 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.