The current version of ZoneRanger and Ranger Gateway is 5.5.
- Windows XP, 2003, 2003 Server, 2008 Server, 2008 Server R2
- RedHat Linux Enterprise 4+
- Solaris 2.8 or greater
- Centos 5.2 or greater
The RangerGateway command on Suse fails with "java: xcb_xlib.c:52: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.".
This is caused by an java issue with Suse. To correct, run the following:
Then execute the RangerGatway command.
After chaning directories to the mounted CD ROM, run the command:
./install.ksh -i console
A new ZoneRanger has a default IP address of 192.168.1.1 on NIC 1. Thus, the ZoneRanger can be connected to any ethernet hub. Another device like a laptop which can be configured on the 192.168.1 subnet can be used to telnet to the ZoneRanger to configure it.
However, applications in other zones can be configured to use the GVI (Gateway Virtual Interface) by running the “gvi add-zone” command
When I run the RangerGateway command, I get the error "Unable to locate the application's 'main' class...."
The problem is that the Unix DISPLAY variable is either not set or set to an invalid X Windows server. Set the DISPLAY variable to a valid X Windows server by running the command
where myserver is the hostname of the server running X Windows.
The main process running on the Ranger Gateway is a Java process which will use no more the 256M of server memory. The amount of disk space used by Ranger Gateway is approximately 175M.
In most circumstances, the Ranger Gateway software is installed on the same server as the management application which will use the ZoneRanger. However, it is possible to install the Ranger Gateway on a stand-alone server. In this configuration, The stand-alone server will need to have IP forwarding enabled. Each management application server will need to have static routes configured to route to the stand-alone server for those devices managed by the ZoneRanger. All of the management application servers will need to be in the same subnet as the stand-alone Ranger Gateway.
The Gateway Virtual Interface (GVI) provides a management application transparent proxy interface on the Ranger Gateway. This interface allows management applications to make SNMP, SSH, and ICMP requests directly to devices. Unknown to the application, these requests are securely proxied by the Ranger Gateway through the ZoneRanger to the managed devices. This greatly simplifies integration between the ZoneRanger and many diverse management applications.
The GVI is available on Solaris, Linux, and Windows Ranger Gateway installations.
The GVI can be configured from the Ranger Gateway Viewer or from the command line. After enabling the GVI, you can use the command (gvi status) to verify that the GVI is enabled. After adding routes using the command (gvi add-route) or the Ranger Gateway Viewer, you can use the command (gvi test) to check if a particular IP address will be proxied through the ZoneRanger. Please see the document GVI Primer for more information.
The command (gvi -enable) fails on Windows with the message "The Gateway Virtual Interface could not be started: There are no available TAP-Win32 adapters on this system."
The tunnel driver must be loaded on the Windows system before enabling the GVI. Run the following command:
In order to load additional SNMP trap definitions into the ZoneRanger, the trap definitions must be in a suitable XML format. You can view the XML format on the ZoneRanger web page Administration->Trap Definitions and click on the Question Mark link, or view the file gateway/ZRCustom/trap-definitions.xml. When the XML is ready, it can be loaded via the ZoneRanger web page or by using the command (uploadConfig) on the Ranger Gateway.