Table Of Contents
FAQs
General FAQs
Installation Questions
Server Questions
Browser Questions
Polling Questions
MIB Questions
Miscellaneous Questions
FAQs
This appendix contains Frequently Asked Questions (FAQs) on Cisco Prime Performance Manager:
General FAQs
These categories of frequently asked questions are general questions about the Cisco Prime Performance Manager:
•
Installation Questions
•Server Questions
•Browser Questions
•Polling Questions
•MIB Questions
•Miscellaneous Questions
Installation Questions
This section addresses the following installation questions:
Q. What operating systems does Prime Performance Manager support?
A. See http://www.cisco.com/en/US/products/ps11715/prod_installation_guides_list.html for more details.
Q. What client requirements do I need to have to run Prime Performance Manager?
A. See http://www.cisco.com/en/US/products/ps11715/prod_installation_guides_list.html for more details.
Q. What system requirements do I need to have to run Prime Performance Manager?
A. See http://www.cisco.com/en/US/products/ps11715/prod_installation_guides_list.html for more details.
Server Questions
This section addresses the following server questions:
•What workstation and network devices do I need to run Prime Performance Manager?
•I moved the server on which I had installed Prime Performance Manager and now I can't start Prime Performance Manager web interface or server. Why?
•Will Prime Performance Manager server processes restart automatically after a system reboot?
•Why doesn't my Prime Performance Manager server start after installing SSL?
Q. What workstation and network devices do I need to run Prime Performance Manager?
A. Prime Performance Manager comprises two distinct pieces of functionality.
•Prime Performance Manager server application runs on Solaris/Linux only.
•Prime Performance Manager web interface runs on any platform that supports the list of supported browsers. Refer Supported Browsers, page 5-1 for more details.
For further hardware and software requirements, see the "Preparing to Install Prime Performance Manager" chapter of the Quick Start Guide for the Cisco Prime Performance Manager 1.0.
Q. I moved the server on which I had installed Prime Performance Manager and now I can't start Prime Performance Manager web interface or server. Why?
A. If you change the IP address of the server on which you installed Prime Performance Manager, or if you move the server to a new network, you must reboot the server to prevent Prime Performance Manager connection problems.
To reboot the server, use this procedure:
Step 1 Log in as the root user, as described in Becoming the Root User, page 2-2.
Step 2 Enter:
If you change the server's Solaris/Linux hostname, you must reset the default hostname on Prime Performance Manager server, using this procedure:
Step 3 Log in as the root user, as described in Becoming the Root User, page 2-2.
Step 4 Enter:
Prime Performance Manager stops all Prime Performance Manager servers on the local host.
Step 5 Enter:
./ppm servername hostname
where hostname is the new default hostname. Ensure that the new name is valid and is defined in your /etc/hosts file.
Prime Performance Manager resets the default hostname for Prime Performance Manager server and automatically restarts Prime Performance Manager server. Any Units connecting to this new host should also change their default gateway server name.
Step 6 On each Unit server perform the following steps:
Step 7 Log into the Unit servers as the root user, as described in Becoming the Root User, page 2-2.
Step 8 Enter:
Prime Performance Manager stops all Prime Performance Manager servers on the local host.
Step 9 Enter:
./ppm gatewayname hostname
where hostname is the new default gateway hostname. Ensure that the new name is valid and is defined in your /etc/hosts file.
Prime Performance Manager resets the default gateway name for Prime Performance Manager unit server and automatically restarts Prime Performance Manager unit server.
Q. Will Prime Performance Manager server processes restart automatically after a system reboot?
A. Yes. When you install Prime Performance Manager server, Prime Performance Manager modifies your system startup scripts to ensure that Prime Performance Manager server processes start up again after a system reboot. To accomplish this, Prime Performance Manager adds these lines to your system startup scripts:
/etc/init.d/ppm.gw and/or /etc/init.d/ppm.unit
/etc/rc0.d/K01ppm.gw and/or /etc/rc0.d/K00ppm.unit
/etc/rc1.d/K01ppm.gw and/or /etc/rc1.d/K00ppm.unit
/etc/rc2.d/K01ppm.gw and/or /etc/rc2.d/K00ppm.unit
/etc/rc3.d/S98ppm.gw and/or /etc/rc3.d/S99ppm.unit
These lines ensure that Prime Performance Manager shutdown and startup scripts run in the correct order for each system initiation state.
Note that for Linux only, these lines are modified as well:
/etc/rc5.d/S98ppm.gw and/or /etc/rc5.d/S99ppm.unit
/etc/rc6.d/K01ppm.gw and/or /etc/rc6.d/K00ppm.unit
Q. Why doesn't my Prime Performance Manager server start after installing SSL?
A. If you have not installed the SSL key and certificate, Prime Performance Manager server will not start. For exact details on this process, see Enabling SSL Support on Gateway in Prime Performance Manager, page 3-15.
Browser Questions
This section addresses the following browser questions:
•Sometimes when browsing Prime Performance Manager web interface, a popup appears with this message: Unresponsive Script. Why does this happen and how can I prevent it from reoccurring?
•Prime Performance Manager web pages appear empty (without content). Why does this happen and how can I prevent it from reoccurring?
Q. Sometimes when browsing Prime Performance Manager web interface, a popup appears with this message: Unresponsive Script. Why does this happen and how can I prevent it from reoccurring?
A. This problem occurs when using the Firefox browser version 1.5. It is not an Prime Performance Manager bug. You can prevent the popup from occurring with this workaround:
Step 1 In the address bar of a Firefox browser window, enter about:config
Step 2 In the filter bar, enter dom.max_script_run_time.
You should now see a setting appear in the window below the filter bar. The setting's name should match what you entered previously (dom.max_script_run_time) and most likely shows a default value of 5.
Step 3 Double-click this setting. Firefox will prompt you for a new value. Enter 10.
If changing this setting still causes the Unresponsive Script popup to appear, repeat these steps but increase the number that you enter in this step.
Q. Prime Performance Manager web pages appear empty (without content). Why does this happen and how can I prevent it from reoccurring?
A. Your Internet Explorer browser settings in Prime Performance Manager client are disabling active scripting. To modify this, in Internet Explorer, change the browser settings as follows:
Step 1 Choose Tools > Internet Options.
Step 2 Select the Security tab.
Step 3 Click the Custom Level button.
Step 4 Search for Active Scripting in the Scripting section.
Step 5 Click the Enable radio button to enable Active Scripting.
Step 6 Search for Logon in the User Authentication section.
Step 7 Click the Automatic Logon with current username and password radio button.
Polling Questions
This section addresses the following polling questions:
•How does Prime Performance Manager poll nodes?
•How do I change the default status polling interval?
Q. How does Prime Performance Manager poll nodes?
A. By default, Prime Performance Manager polls the nodes in the network every 15 minutes. However, you can initiate a poll for one or more nodes at any time by selecting the nodes in the Discovery tab in the Discovery dialog box and selecting Poll.
You can also change the default poll interval for one or more nodes in the SNMP Configuration dialog box. You must be logged in as a System Administrator to access this tab.
Q. How do I change the default status polling interval?
A. Prime Performance Manager polls the node for status information (for example, interface up or down) every 15 minutes. The size of this poll depends on the number and type of interfaces that are enabled on the node.
To change the default polling interval of 15 minutes, open the SNMP Editor by selecting Administrative -> SNMP from Prime Performance Manager main window. You can enter the default polling interval to any number of minutes from 5 to 1440.
Note The status information in the GUI is only as good as the most recent poll.
MIB Questions
Q. What are the names of the MIBs used by Prime Performance Manager?
A. You can find the complete list of MIBs that Prime Performance Manager configures and queries in Appendix D, "MIB Reference."
You can obtain the latest versions of these MIBs from one of these locations:
•The Zip file mibs.zip, located at the top of Prime Performance Manager DVD Image, contains these MIBs.
•You can download these MIBs from the Cisco website:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
•The MIBs are also accessible from Prime Performance Manager web interface by selecting Home, then clicking on SNMP MIBs under the Reports Documentation section.
Miscellaneous Questions
This section addresses the following miscellaneous questions:
•Does Prime Performance Manager require any other NMS applications?
•Can I run Prime Performance Manager on my Windows PC?
•How do I increase the swap size in Solaris?
•How do I increase the swap size in Linux?
•How can I disable DNS lookups on Prime Performance Manager server host?
Q. Does Prime Performance Manager require any other NMS applications?
A. Prime Performance Manager is functionally a standalone product and does not require any other products. However, you can integrate Prime Performance Manager with other products to provide added value. Refer Prime Network Integration, page 2-3 for more details.
Q. Can I run Prime Performance Manager on my Windows PC?
A. Prime Performance Manager server must be run on a Solaris/Linux system.
Q. How do I increase the swap size in Solaris?
A. To create a new swap file on Solaris:
Step 1 Use mkfile to create a file suitable for a local swap area.
For example, to create a 1GB swap file, enter the following command:
/usr/sbin/mkfile 1024m /opt/swapfile
where /opt/swapfile is the name of the file to be used as swap space. Units for the size can be kilobytes (k), blocks (b), or megabytes (m). Choose carefully the disk location to create the swap file. Choose a disk partition with plenty of free disk space.
Step 2 Make the system use the file as swap by entering the following command:
/usr/sbin/swap -a /opt/swapfile
Step 3 Run swap -l to verify that the swap file has been activated.
Step 4 Add the following line to /etc/vfstab to assure the new swapfile is maintained across system reboots:
/opt/swapfile - - swap - no -
Q. How do I increase the swap size in Linux?
A. To create a new swap file on Linux:
Step 1 Use dd to create a file suitable for a local swap area.
For example, to create a 1GB swap file, enter the following command:
/bin/dd if=/dev/zero of=/opt/swapfile bs=1M count=1024
where /opt/swapfile is the name of the file to be used as swap space. This specifies a blocksize of 1Mb and 1024 of them for 1Gb total. Choose the disk location to create the swap file. Choose a disk partition with plenty of free disk space.
Step 2 Enter the following to make the system to start using the file as swap and activate it:
/sbin/mkswap /opt/swapfile
/sbin/swapon /opt/swapfile
Step 3 Run swap -l to verify that the swap file has been activated.
Step 4 Add the following line to /etc/fstab to assure the new swapfile is maintained across system reboots:
/opt/swapfile swap swap defaults 0 0
Q. How can I disable DNS lookups on Prime Performance Manager server host?
A. Long delays in Prime Performance Manager data processing can occur when looking up a node by its DNS name when does not have one defined or when there are latency issues in your network. Make the following operating system configuration changes to the system on which your Prime Performance Manager server runs to disable DNS lookups:
Step 1 Remove the "dns" parameter from the "hosts" and "ipnodes" lines in /etc/nsswitch.conf.
Step 2 Remove /etc/resolv.conf or comment the DNS server entries in /etc/resolv.conf.
Feedback