Ip Address Aliasing - Tavve zoneranger User Manual

D. IP Address Aliasing
IP address aliasing is one of a number of alternative mechanisms (e.g. GVI, SOCKS) that can be used to
enable the Ranger Gateway to intercept management protocol traffic originated by management
applications and destined for managed devices.
Most operating systems provide a means to associate multiple IP addresses with each network interface
(i.e. a primary address, and one or more "aliases"). If IP address aliases, corresponding to managed
devices located in firewall-partitioned networks, are defined on the management application server, and
the Ranger Gateway is configured to listen on a variety of ports for TCP or UDP traffic destined for any
of these IP addresses, all traffic generated by the management application and destined for these devices
on the configured ports will be received by the Ranger Gateway.
If the management application and the Ranger Gateway software have been installed on the same server,
the IP address aliases can usually be added to the server's loopback interface.
For example consider the network shown in the following figure:
Figure D-1. IP Address Aliasing
In this network, the management application is managing devices in two DMZs via a Ranger Gateway
and a set of three ZoneRangers. There are five devices to be managed in all: 10.2.1.1, 10.2.1.2, 10.4.1.1,
10.4.1.2, and 10.4.1.3. In order to enable the Ranger Gateway to intercept traffic destined for these
devices, five IP address aliases are defined on the management application server. The addresses in this
case are identical to the actual IP addresses of the managed devices.
If the management application and the Ranger Gateway software have been installed on different
servers, the IP address aliases must be added to an appropriate network interface on the Ranger Gateway
server, and static routes will need to be defined on the management application server to ensure that
SNMP requests are routed to the Ranger Gateway server.
For example consider the network shown in the following figure:
ZoneRanger 5.5 User's Guide 367