Known Issues

Longitude 6.3 is due to be released in a few months - it will include the following features:

• New Application:
  • NetFlow - Graphs of NetFlow metrics
• Enhanced applications:
  • Internet - support for Firefox 3.6 and Selenium IDE 1.06
  • NetworkDevice - enhanced version of the previous Cisco application
  • Oracle - additional v$sysstat metrics collected and reported on
  • VMWare - supports VSphere and ESX 4.0
  • Windows - network metrics in KB instead of packets
• Web UI Improvements:

The full Management Console installation kit has an agent installation option. Some agents installed using this option in the 64 bit installation kit may have the following problems:

• In Administration >> Component Management >> Display Status, the agent status is displayed as red
• In Manage Monitoring, a test connection to the agent is successful, but you are unable to register collections

The following steps will fix this problem:

1. Log on to the agent computer with a Local Administrator account
2. Stop the Longitude services

There is a Microsoft problem in which the SQL Server 2008 PerfMon counters on Windows Server 2003 are not accessible via WMI. When Microsoft has a fix for this problem, we will post a link to the fix. Until then, the following steps can be used to monitor default instances of SQL Server 2008 on both Windows Server 2003 and Windows Server 2008.

****Please note:

It has come to our attention that an Automatic Update of Firefox may remove Selenium. You should disable Automatic Updates on the Machine executing the internet macros so that this does not happen. You can disable the automatic updating on Firefox by performing the following.

• Go to Tools > Options > Advanced > Update.
• Uncheck the checkbox that says automatically check for updates.

We have seen some cases in Longitude 6.2 in which the CPU on a Longitude agent will spike when collecting data for Internet Macros. The Firefox instances used to collect data for the Internet Macro do not close correctly, leaving orphaned Firefox processes on the agent.

Until a patch is available, this problem can be addressed by restarting the Longitude Statistics Server component. This should kill the orphaned Firefox processes, but you may need to check the Longitude server directly and close dialog boxes for Firefox errors.

A more efficient ping was introduced for version 6.2. If you do not wish to upgrade these are the steps to implement it.

1. Grab the patch (Right Click Save Target As)
2. You will need to stop your Longitude Services from Services.msc
3. Place the files in the patch into the following directories Longitude\common\lib\firenze-common.jar
   Longitude\dc\lib\firenze-collectors.jar
4. Start the services back up
5. The ping fix is now implemented

The Upgrade Manager may fail to start during the Linux Agent install. If this occurs you will see an error in the Manage Upgrades function on the Management Station regarding connecting to the Upgrade Manager on the agent. You can start the Upgrade Manager on the agent manually by running the following command from the Longitude/bin directory:

firenze_appman start

Longitude uses the iostat command to collect the CPU_IDLE_PCT statistic. On HP-UX, this command may return inaccurate values, which can result in CPU Busy percentages over 100%, and CPU Idle percentages less than 0.

If you configure Heroix Longitude to use RSA Authentication , you will need to configure remote agents to allow connections from the Management Station by saving the Management Station's certificate file to the agents. Downloading the Management Station’s certificate using Internet Explorer will be unsuccessful if the Management Station is also configured to use HTTPS. In this case, trying to download the certificate results in an error like the following:

"Internet Explorer cannot download about.do?certificate=yes from
server.domain.net"

After adding filters to a collection it fails with an error that includes "ValueOverflow: SAP DBTech JDBC: Parameter 8: value too large." If you attempt to copy the filter to other computers, the copy will fail and the application may be removed from the target computer. The problem is that the filtering information has exceeded the size allocated for the field where it is stored in the database. To resolve the problem the size of the Parameters column must be increased in the Collections table. You can increase the size of the column as follows:

1. Start SapWWW