Facebook

Fill out this form to subscribe to news, tips and information about updates.

Read more
Search known errors
From date:
To date:

Follow us
Facebook    Twitter    LinkedIn

G&R » Support » Known Errors  

Known Errors

These are the known errors in our products, logged as reported with versions and platforms affected as well as corrections and work-arounds.

This list is largely historical, since it records all problems that have been reported throughout G&R history. Only the most recently reported problems still exist, unless you are using a very old copy of the product, in which case you should update the product to the most recent version.


E1211: Ggate, enabling TNVIP/Telnet could cause load sharing to fail

Product: Ggate
Platform: Windows and UNI
Status: Fixed for 6.5, fix available for 6.4
Last updated: 2009-11-05 11:52:28

When Ggate/DSA is used in a load sharing environment for Glink clients,
Gproxy takes over the Ggate port, accepts connections from Glink
clients and redirects them to the least loaded Ggate system it finds in
the local load-balancing community. Ggate must be allocated 'some other'
port using the -gga parameter. Gproxy locates the Ggate port it should
use when redirecting Glink clients by looking at the port from which
Ggate load-balancing information is broadcast.

When Ggate/TNVIP-server functionality is enabled using the -tnv
parameter it allocates a port for TNVIP clients (default 7323 or given
in the -tnv parameter).

If the -tnv parameter occured on the Ggate command line before the -gga
parameter The -tnv port was used as the broadcast port for load
balancing information. This caused Gproxy to redirect Glink/DSA clients
to the TNVIP port, and load balancing failed.

The same problem can occur when enabling Telnet or TN3270 functionality.

The work-around is to place the -gga parameter before -tnv, -tel
or -tn3270 in the Ggate command line.
(c) Copyright 1982-2017 Gallagher & Robertson AS. Webmaster: webmaster@gar.no

URL: http://www.gar.no/support/errors
 
PARTNERS