|
|
This chapter provides information on modifying IPM components. IPM components include collectors, source routers, target devices, and operations. Information is provided on viewing, updating, and deleting these components.
This chapter contains the following major sections:
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 3-1). 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:
To view detailed information about a defined collectors, follow these steps:
Step 1 From the IPM Main window, select a collector.
Step 2 Select View > Collector Properties. The Collector Properties window (Figure 3-2) is displayed.
To define a new collector, follow these steps.
Step 1 From the IPM Main window, select Edit > Add. The Add Collector window (Figure 3-3) is displayed.
Step 3 From the Target Names list, select one or more devices to designate as targets.
Step 4 From the Operation Names list, select the operation and type to use for this collector.
Step 5 Do one of the following:
Step 6 To assign a name to the collector, enter a name for the collector in the Collector Name field. If you do not specify a collector name, IPM assigns a name composed of the source router, target, and operation names.
Step 7 Click OK. The collector that you defined is displayed in the list of collectors in the IPM Main window.
The following sections provide information on creating a collector seed file:
A sample collector seed file is shown below:
#####################################!############################################## # # This file has definitions to configure collectors. # The format of the file is as follows: # # <collname><delim><source><delim><target><delim><Operation><delim><st time><delim> # <duration><delim><CollType> # # The <delim> characters are " ;,\t\n\0" "space,semicolon,comma,tab,newline,null" # The <Collector type> is M for Monitored; S for Statistical; # The <st time> is in the format MM:DD:YYYY:hh:mm:ss. # if the <st time> is 1 then it is a collector to start "now". # If <st time> and <duration> are 0 (zeros) then it is treated as preconfig collector # if the <duration> is 0 (zero) then it is a "forever" collector. # #####################################!############################################## #coll1 cwb-r18.cisco.com lindchen-ultra:::2 default-ip-echo-monitored 1 10 M #coll2 cwb-r18.cisco.com lindchen-ultra:::2 default-ip-echo-monitored 1 10 M #coll3 cwb-r18.cisco.com lindchen-ultra:::2 default-ip-echo-monitored 1 10 M #coll4 cwb-r18.cisco.com lindchen-ultra:::2 default-ip-echo-monitored 1 10 M #coll5 cwb-r18.cisco.com lindchen-ultra:::2 default-ip-echo-statistics 1 10 S #coll6 cwb-r18.cisco.com lindchen-ultra:::2 default-ip-echo-monitored 1 10 M #coll7 cwb-r18.cisco.com lindchen-ultra:::2 default-ip-echo-monitored 1 10 M #coll8 cwb-r18.cisco.com lindchen-ultra:::2 default-ip-echo-monitored 1 10 M
Table 3-1 provides information about each of the components required for defining collectors in a collector seed file.
| Component | Description |
|---|---|
Collector Name | Name of the collector. |
Source Router | 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 Device | 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. A target device is composed of the target name, application name (SNA only), mode name (SNA only), and type. |
Operation Name | 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. N Hours---Stops the collector after the specified length of time has 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 the collector is defined to collect statistics (Statistical) or to monitor data without collecting statistics (Monitored). |
To create a collector seed file, follow these steps:
Step 1 Using any text editor, create a collector seed file following the format described in the "Collector Seed File Format" section.
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, follow these steps:
Step 1 Launch the IPM Configure from Seed application using the following commands:
# cd /opt/CSCOipm/bin # ./ipm seed
To provide the name of collector seed file when you start the IPM Configure from Seed application, enter the following command:
# ipm seed filename 3
Where:
filename is the name of the collector seed file to load.
3 indicates the seed file type (1 = source router, 2 = target, 3 = collector).
Step 2 When prompted, specify the collector seed file that you have created.
The Configure from Seed application sends a request to the IPM configuration server which processes the collector seed file and creates a output file in the same directory that contains the results of the processing. The output file has the same name as the collector seed file with an extension of .out. Any errors that occurred are noted in this file.
When you start IPM, the collectors that you defined in the collector seed file are displayed in the IPM Main window.
 | Tips You can also load collectors from a collector seed file by selecting File > Open Seed File from the IPM Main window. |
To delete an IPM collector, follow these steps:
Step 1 From the IPM Main window (Figure 3-1), select the collector or collectors to delete.
Step 2 Select Edit > Delete.
Step 3 When the confirmation box appears, click Yes. The selected collectors are deleted from the IPM Main window.
IPM source routers are the routers from which you want to gather the response-time data. Each source router must contain the Cisco IOS RTR 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, select Configure > Source Router from the IPM Main window. The Source Router window (Figure 3-4) is displayed.
The Source Router 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.
Step 1 Do one of the following:
Step 2 Select View > Source Properties. The Source Properties window (Figure 3-5) is displayed.
For information on these fields, refer to the "Source Properties Window" topic in the online help or see the "Source Properties Window" section in the "IPM Windows Reference" appendix of this guide.
Step 1 Verify that the SNMP read community and write community strings are configured properly on the router and verify that the router is configured to send RTR-generated traps to your NMS host. For information on configuring SNMP on the source router, see the "Configuring Your Routers to Send RTR-Related Traps" section in "Preparing to Install" chapter of the Internetwork Performance Monitor User Guide.
Step 2 From the Source Router window (Figure 3-4), select Edit > Add. The Add Source Router window (Figure 3-6) is displayed.
Step 3 On the Add Source Router window, enter the appropriate data in the following fields:
Step 4 Click OK to configure this source. 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 Source Router window. If IPM cannot reach the router, IPM displays an error message and redisplays the Add Source Router window.
The following sections provide information on creating a source router seed file:
A sample source router seed file is shown below:
#####################################!############################################## # # This file has definitions for source routers. # # The comments starts with "#" character # The format of the file is as follows: # # <hostname><delimiter><rd community name><delimiter><wr community name> # # The <delimiter> characters are " ;,\t\n\0" "space,semicolon,comma,tab,newline,null" # #####################################!############################################## #cwb-r18.cisco.com public private #cwb-r17 public private #cwb-r01.cisco.com public private #cwb-r02 public private
Table 3-2 provides information about each of the components required for defining source routers in a source router seed file.
| Component | Description |
|---|---|
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. |
Read Community | Community name (or password) for read access to the information maintained by the SNMP agent. This value can be from 1 to 32 characters. The default value is public. |
Write Community | Community name (or password) for write access to the information maintained by the SNMP agent. This value can be from 1 to 32 characters. |
To create a source router seed file, follow these steps:
Step 1 Using any text editor, create a source router seed file following the format described in the "Source Router Seed File Format" section.
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, follow these steps:
Step 1 Launch the IPM Configure from Seed application using the following commands:
# cd /opt/CSCOipm/bin # ./ipm seed
1 indicates the seed file type (1 = source router, 2 = target, 3 = collector).
Step 2 When prompted, specify the source router seed file that you have created.
The Configure from Seed application sends a request to the IPM configuration server which processes the source router seed file and creates a output file in the same directory that contains the results of the processing. The output file has the same name as the source router seed file with an extension of .out. Any errors that occurred are noted in this file.
When you start IPM, the source routers that you defined in the source router seed file are displayed in the Source Router window.
| Tips You can also load source routers from a source router seed file by selecting File > Open Seed File from the Source Router window. |
To change the configuration of a source router, follow these steps:
Step 1 From the Source Router window (Figure 3-4), select the source router to update.
Step 2 Select Edit > Update. The Update Source Router window (Figure 3-7) is displayed. The window title bar displays the name of the source router that you have selected (in this case, cwb-c9).
Step 3 You can change the following source attributes:
Step 4 Click OK to implement the change.
You can delete source routers that you no longer need. You can delete more than one source router at a time.
To delete a source, perform the following steps:
Step 1 From the Source Router window (Figure 3-4), select the source router or source routers that you want to delete.
Step 2 Select Edit > Delete.
Step 3 When the confirmation box appears, click Yes. The selected source routers are deleted from the Source Router window.
IPM targets are destination devices for which you want to gather response-time data. A target can be an SNA host or an IP-addressable device.
Information on working with target devices is provided in the following subsections:
To view a list of defined targets, select Configure > Target from the IPM Main window. The Target window (Figure 3-8) is displayed.
The Target 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.
To add a new target, follow these steps:
Step 1 From the Target window (Figure 3-8), select Edit > Add. The Add Target window (Figure 3-9) is displayed.
Step 2 On the Add Target window, enter data in the following fields:
Step 3 Click OK.
The following sections provide information on creating a target seed file:
A sample source router seed file is shown below:
#####################################!############################################## # # This file has definitions for target addresses # The format of the file is as follows: # # <target type><delimiter><hostname><delimiter><mode name> # # The <delimiter> characters are " ;,\t\n\0" "space,semicolon,comma,tab,newline,null" # The <target type> is 2 for IP; 4 for SNA_SSCP; 5 for SNA_LU0; 6 for SNA_LU2 # #####################################!############################################## #2,lindchen-ultra, #2,kschombu-ss20,
Table 3-3 provides information about each of the components required for defining targets in a target seed file.
| Component | Description |
|---|---|
Target Type | The protocol type to be used with this target. Specify one of the following values: 2---IP/ICMP Echo. Requires a destination IP address or host name. 4---SNA SSCP-LU Native Echo. Requires the host name defined for the SNA PU connection to VTAM. 5---SNA LU type 0 connection to Cisco's NSPECHO host application. Requires the host name defined for the SNA PU connection to VTAM. 6---SNA LU type 2 connection to Cisco's NSPECHO host application. Requires the host name defined for the SNA PU connection to VTAM. |
Host Name | For IP, enter the IP address or host name of the target device. This is the name that appears in the Target field when you define a collector. |
Mode Name | Eight-character SNA logon mode name used to access the SNA echo host application. If you omit the Mode Name value, default session parameters are used when in session with the host application. The Mode Name field is for SNA Echo LU0 only. The default value for LU0 is INTERACT and the default value for LU2 is D4A32782. The SNA host uses this name to find the logon mode table entry that defines session parameters. If you omit this name, the SNMP agent sends a name of all blanks to the SNA host, which then uses a set of default session parameters for the echo session. |
To create a target seed file, follow these steps:
Step 1 Using any text editor, create a target seed file following the format described in the "Target Seed File Format" section.
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, follow these steps:
Step 1 Launch the IPM Configure from Seed application using the following commands:
# cd /opt/CSCOipm/bin # ./ipm seed
To provide the name of target seed file when you start the IPM Configure from Seed application, enter the following command:
# ipm seed filename 2
Where:
filename is the name of the target seed file to load.
2 indicates the seed file type (1 = source router, 2 = target, 3 = collector).
Step 2 When prompted, specify the target seed file that you have created.
The Configure from Seed application sends a request to the IPM configuration server which processes the target seed file and creates a output file in the same directory that contains the results of the processing. The output file has the same name as the target seed file with an extension of .out. Any errors that occurred are noted in this file.
When you start IPM, the target that you defined in the target seed file are displayed in the Target window.
| Tips You can also load targets from a target seed file by selecting File > Open Seed File from the Target window. |
You can delete targets that you no longer need. You can delete more than one target at a time.
To delete a target, perform the following steps:
Step 1 From the Target window (Figure 3-8), select the target or targets that you want to delete.
Step 2 Select Edit > Delete.
Step 3 When the confirmation box appears, click Yes. The selected targets are deleted from the Target window.
An IPM operation is an alias for a set of parameters used in measuring response time. You configure an operation by associating an operation name with a network protocol, such as IP Echo or PathEcho, that you want to use to measure response times from the source router to the target device.
Information on working with operations is provided in the following subsections:
To view a list of defined operations, select Configure > Operation from the IPM Main window. The Operation window (Figure 3-10) is displayed.
The Operation window displays a list of the defined operations. From this window, you can add a new operation, modify an existing operation, or delete an existing operation.
Step 1 Do one of the following:
Step 2 Select View > Operation Properties. The Operation Properties window (Figure 3-11) is displayed. By default, the Protocol tab is displayed.
Step 3 Click Stats, the Statistics tab (Figure 3-12) is displayed.
Step 4 Click Threshold, the Threshold tab (Figure 3-13) is displayed.
For information on these fields, refer to the "Operation Properties Window" topic in the online help or see the "Source Properties Window" section in the "IPM Windows Reference" appendix of this guide.
An IPM operation is an alias for a set of parameters used to measuring response time. You configure an operation by associating an operation name with a network protocol, such as IP Echo or PathEcho, that you want to use to measure response times from a source router to a target device.
To define an operation, follow these steps:
Step 1 Select Configure > Operation from the IPM Main window. The Operation window (Figure 3-10) is displayed.
Step 2 From the Operation window, select Edit > Add. The Add Operation window (Figure 3-14) is displayed. By default, the Protocol tab is displayed when you access this window.
Step 3 In the Name field, enter a symbolic name that you want to assign to this operation. A name will appear in the Operation Name field when you configure a collector. This name can be from 1 to 32 characters. Do not include special characters such as ! @ # $ % ^ & * ' '' or | in the name.
Step 4 In the Description field, enter text to describe the operation for your own use. This description can be from 1 to 255 characters. Do not include special characters such as ! @ # $ % ^ & * ' '' or | in the description.
Step 5 In the Sample Interval field, enter a value, in seconds, for how often you want the collector at the source router to execute the operation to measure response time to and from the target. The default is every 60 seconds. The valid range is from 10 to 3600 seconds (1 hour).
For normal operation, do not set the interval value to fewer than 60 seconds. A more frequent interval is not needed when keeping statistics (the default) and can slow down the network.
If the collector takes longer to execute the operation than the specified sample interval value allows, the busy statistical counter in the output display is incremented instead of starting another operation.
Step 6 In the Type field, select one of the following options:
Step 7 From the Protocol list, select one of the following protocols to be used by the collector:
Step 8 In the Request Size field, enter the size of the protocol data, in bytes, in the payload of the collector's request packet. The valid range is from 1 to 16384 (the protocol's maximum allowable size). The default is 1 byte. This option is valid only for LU0 and LU2. For IP, the request size is set to 64 bytes.
Step 9 In the Response Size field, enter the size, in bytes, of the protocol data in the payload in the collector's response packet. For SNA echo protocols, the default is 1 byte. For IP echo protocols, the default is the same value as the request size. The valid range is from 0 to 16384 bytes. This option is valid only for LU0 and LU2 protocols.
Step 10 Enable the Verify Data option to have the source router check the echo response for unexpected data. When the response contains unexpected data, the Verify Data counter is incremented in the displayed results. This option is valid only for SNA protocols.
Step 11 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.
The options available on the Statistics tab of the Add Operation window allow you to gather response time, error, and threshold statistics for the paths that you are monitoring. For information on using these options, see the "Gathering Statistics" section.
The options available on the Threshold tab of the Add Operation window allow you to set thresholds and have IPM alert you when these thresholds have been violated. For information on setting thresholds, see the "Setting Thresholds and Generating Alerts" section.
From the Statistics tab of the Add Operation window, you can configure an operation to collect statistics at the source router. The collected statistics include response time, errors, and threshold violations that occur during the time that the collector is active.
To define an operation to gather statistics, follow these steps:
Step 1 Define a new operation by following the steps in the "Adding a New Operation" section, but do not click OK to complete the definition.
Step 2 Click the Statistics tab to access the Statistics tab (Figure 3-15).
Step 3 Enable the Collect Statistics option to collect statistics on an hourly basis from the source router. The statistics are stored in the IPM database and used later for trend analysis. If the Collect Statistics option is not enabled, IPM runs in monitor mode only. In monitor mode, you view response-time data in real time or set thresholds for notification of violations as they occur.
Step 4 In the Number of Paths field, enter the maximum number of paths for which you want IPM to collect statistics. To ensure that you do not miss collecting statistics for relevant paths, set this value to a number slightly higher than the expected number of paths. The default value is 5.
Step 5 In the Number of Hops field, enter the maximum number of hops for which to collect statistics. To ensure that you do not miss collecting statistics for relevant hops, set this value to a number slightly higher than the expected number of hops. The default value is 15.
Step 6 Click OK to complete the definition of the statistical operation. IPM redisplays the Operation window and the new operation is added to the list of defined operations.
From the Threshold tab of the Add Operation window, you can configure thresholds and event notifications on the source router.
To set thresholds and generate alerts using an operation, follow these steps:
Step 1 Define a new operation by following the steps in the "Adding a New Operation" section, but do not click OK to complete the definition.
Step 2 Click the Threshold tab to access the Threshold tab (Figure 3-16).
Step 3 In the Threshold Type field, select one of the algorithms to be used by IPM to calculate threshold violations. The following values are possible:
Step 4 In the Rising field, enter a rising threshold, in milliseconds. Valid values are between 1 and 2147483647. The default is 5000 ms. When the response time exceeds the rising threshold, the collector uses the algorithm specified in Threshold Type to determine if a threshold violation has occurred. If a violation occurs, the action defined in Event Type is taken.
Step 5 In the Falling field, enter a falling threshold, in milliseconds. Valid values are between 0 and 2147483647. The default value is 3000 ms. When the response time falls below the falling threshold, the threshold is reset.
Step 6 If you specified a Threshold Type of Consecutive, X of Y, or Average, enter a value in the Count1 field to be used in calculating the threshold. Valid values are 1 to 16. The default is 5.
Step 7 If you specified a Threshold Type of X of Y, enter a value in the Count2 field for the Y value to be used in calculating the threshold. Valid values are 1 to 16. The default is 5.
Step 8 In the Response Timeout 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 interval. Valid values are between 0 and 60480000. The default value is 4000 ms.
Step 9 Enable the Timeout option to check for response-time reporting operation timeouts based on the timeout value configured for the collector. If you enable the Timeout option, the action (specified in Event Type) is taken when a timeout occurs or is cleared on this collector.
Step 10 Enable the Connection Lost option to check for IPM connection loss in connection-oriented protocols (LU0, LU2, and SSCP). If you enable the Connection Lost option, the action specified in Event Type is taken when a loss of connection or a reconnection after a loss occurs on this collector.
Step 11 In the 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 12 Click OK to complete the operation definition. IPM redisplays the Operation window and the new operation is added to the list of defined operations.
To change the configuration of an operation, follow these steps:
Step 1 From the Operation window (Figure 3-10), select the operation that you want to update.
Step 2 Select Edit > Update. The Update Operation window (Figure 3-17) is displayed. By default, the Protocol tab is displayed when you access this window.
Step 3 You can change any of the following operation protocol attributes:
Step 4 Click the Statistics tab to display the Statistics tab (Figure 3-18) and change any of the following statistics collection attributes defined for this operation:
Step 5 Click the Threshold tab to display the Threshold tab (Figure 3-19) and change any of the following threshold or event notification values defined for this operation:
Step 6 Click OK to implement the changes.
You can delete operations that you no longer need.You can delete more than one operation at a time.
To delete an operation, perform the following steps:
Step 1 From the Operation window (Figure 3-10), select the operation or operations that you want to delete.
Step 2 Select Edit > Delete.
Step 3 When the confirmation box appears, click Yes. The selected operations are deleted from the Operation window.
For collectors that are using a statistical operation, IPM gathers response-time 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 statistics while business days are used in determining the weekly and monthly statistics. 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, follow these steps:
Step 1 Edit the IPM database preferences file (/opt/CSCOipm/etc/ipmDbPref.conf) using a text editor.
Step 2 To change the number of days that response time statistics are stored, modify the following line:
ipm_response_life=180
Step 3 To change the number of days that error statistics are stored, modify the following line:
ipm_error_life=180
Step 4 To set the business hours for which you want collected statistics stored, 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 collected statistics stored, set the hour interval value to 1. Statistics are not stored for intervals with a value of 0.
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 5 To set the business days used for calculating weekly and monthly data, you must turn on or off the appropriate day. Each day of the week is represented by a number as follows:
ipm_business_day_0
ipm_business_day_1
ipm_business_day_2
ipm_business_day_3
ipm_business_day_4
ipm_business_day_5
ipm_business_day_6
For 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 6 Save your changes to the IPM database preferences file.
Step 7 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 response time 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
Use device data that is already known to CiscoWorks2000 Resource Manager Essentials (Essentials) or CiscoWorks2000 CWSI Campus (Campus) to define source routers or targets for IPM. To use this data with IPM, you must complete the following tasks:
The process for exporting the device data is different depending on whether you are using Essentials or Campus. Follow the appropriate steps below to export the device data.
To export device data from Essentials, complete the following steps:
Step 1 While Essentials is running, select Admin > Inventory > Export to File.
Step 2 In the Output Format field, select Comma Separated Value Format as the file format.
Step 3 In the File Name field, enter the filename for the file to contain the exported device data.
By default, the exported data file is stored in the /opt/CSCOpx directory on the server where you are running Essentials. To select a different directory for the file, select Browse.
Step 4 Click Next. A message confirming that the data has been exported is displayed.
Step 5 Click OK.
Step 6 If you are running Essentials and IPM on the same server, you can proceed to the "Convert the Exported Data to IPM Seed File Format" section.
Step 7 If you are not running Essentials and IPM on the same server, you need to transfer the exported device file from the Essentials server to the IPM server. Proceed to the "Convert the Exported Data to IPM Seed File Format"section.
To export device data from Campus, complete the following steps:
Step 1 If Campus and IPM are not running on the same server, Telnet to the server where Campus is running.
Step 2 Export the device data by entering the following commands:
# cd /opt/CSCOcwsi/bin cwsiexp <AniServername> Vlad:db_getAllDevicesCommunity > <filename>
Where:
AniServername is the name assigned to the AniServer during Campus installation.
filename is the name for the file to contain the exported device data.
Step 3 If you are running Campus and IPM on the same server, proceed to the "Convert the Exported Data to IPM Seed File Format" section.
Step 4 If you are not running Campus and IPM on the same server, transfer the exported device file from the Campus server to the IPM server. Proceed to the "Convert the Exported Data to IPM Seed File Format" section.
After exporting the device data from either Essentials or Campus, you must run a conversion utility on the file to convert the data into the seed file format expected by IPM. The exported device data file might contain some devices that cannot be used as sources. If a device does not support RTR, the IPM will not add the device to the source router list. However, any device with an IP address can be used as a target. The exported device data can be used to create either a source router seed file or a target seed file.
To convert the exported device data to a source router seed file, enter the following commands:
# cd /opt/CSCOipm/bin ./ipmConvertCW2KtoSeed.sh -s <input filename> <output filename>
Where:
-s indicates that the resulting seed file is a source router seed file.
input filename is the filename for the exported device data file.
output filename is the filename where you want to store the converted data in a source router seed file.
To convert the exported device data to a target seed file, enter the following commands:
# cd /opt/CSCOipm/bin ./ipmConvertCW2KtoSeed.sh -t <input filename> <output filename>
Where:
-t indicates that the resulting seed file is a target seed file.
input filename is the filename for the exported device data file.
output filename is the filename where you want to store the converted data in a target seed file.
To load source routers from a source router seed file into IPM, follow these steps:
Step 1 Copy the source router seed file into the /opt/CSCOipm/etc/source directory on the server where you are running the IPM server.
Step 2 From the Source Router window, select File > Open Seed File. The Seed File window is displayed.
Step 3 In the Enter Seed File Name field, enter 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 displayed in the Source Router window and in the Source Router list in the Add Collector window.
To load targets from a target seed file into IPM, follow these steps:
Step 1 Copy the target seed file into the /opt/CSCOipm/etc/source directory on the server where you are running the IPM server.
Step 2 From the Target window, select File > Open Seed File. The Seed File window is displayed.
Step 3 In the Enter Seed File Name field, enter the name of the target seed file.
Step 4 Click OK.
The targets that you defined in the target seed file are displayed in the Target window and in the Target list in the Add Collector window.
Posted: Fri Mar 12 08:31:46 PST 1999
Copyright 1989-1999©Cisco Systems Inc.