Guest

Cisco Remote Monitoring Suite Option

Backwards Compatibility Considerations (Release 4.6)

  • Viewing Options

  • PDF (109.3 KB)
  • Feedback
Backwards Compatibility Considerations

Table Of Contents

Backwards Compatibility Considerations

Listener and Grid

LGMapper Server

AlarmTracker Clients


Backwards Compatibility Considerations


Listener and Grid

If you are upgrading from an existing Listener/Grid solution, there are some compatibility issues that you should be aware of.

The new Listener can be used with old Grid clients provided the following criteria are met:

The Listener's Exclude Node feature is disabled (Enabling the Exclude Node Feature)

Update every Grid client's GridPipe.dll with the new GridPipe.dll found in the Listener executable directory (typically ICR\bin). If this dll file is not updated, the Grid client fails to connect and an Alarm is raised in the AALSTN customer node.

When upgrading from an existing Listener/Grid solution, you may want to preserve compatibility during an initial acceptance period.

Once you enable the Exclude Node feature, you can no longer use the Grid clients to monitor Alarm data. The Grid client can connect to Listener, but receives no data other than Listener heartbeats. An Alarm is also raised in the AALSTN customer node.

Version 2 of the LGMapper and LGArchiver are designed to work with a 4.6 Listener server. This version of Listener now supports multiple products. If you choose not to upgrade Listener to a 4.6 Listener, you can still use the Version 2 LGMapper and LGArchiver by setting a registry key. This key is used by LGMapper and LGArchiver to request an older feed from Listener that does not support multiple products. In this case, only the ICM product can be supported.

To use a 4.5 Listener with the LGMapper, create the following registry value:

Key: HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems\LGMapper2
DWORD Value: ListenerClientVersion = 4

Similarly, to use a 4.5 Listener with the LGArchiver, create the following registry value:

Key: HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems\LGArchiver
DWORD Value: ListenerClientVersion = 4

If you fail to set the registry keys and inadvertently connect to a 4.5 Listener, the initialization will abort. An error message (with an error code of 0x8007000b) is then written to the log file. The error text:

An attempt was made to load a program with an incorrect format.

may be seen for an AlarmTracker Client.

LGMapper Server

Version 2 of LGMapper has changed considerably from the initial Version 1 release. The biggest change is the migration to SQL Server 7.0 from Microsoft Access as the database repository for the configuration information and Alarms data. Because of this major design change, it was decided to rename all the Server components and add a '2' to each COM object and interface to distinguish it from its Version 1 counterpart.

It is therefore possible to install the Version 2 LGMapper Server on the same machine as the Version 1 LGMapper Server. However, it is strongly recommended that the Version 2 LGMapper Server be installed in a different directory than the Version 1 LGMapper Server since there can be some overlap in file names and log file output.


Note If you are upgrading the LGMapper, ensure no LGMapper Server is currently run ning.


AlarmTracker Clients

The Version 2 AlarmTracker Client is specifically designed to connect to the Version 2 LGMapper Server. It is not backward compatible with the Version 1 AlarmTracker client. Therefore, you cannot use the Version 2 AlarmTracker client to connect to a Version 1 LGMapper Server.

Since the name of the AlarmTracker executable file is still AlarmTracker.exe, to maintain both a Version 1 installation and a Version 2 installation on the same machine, ensure Version 2 AlarmTracker Client is installed in a different directory than the Version 1 AlarmTracker Client. That way, both versions can run side by side to perform validation checks.