Alcatel-Lucent 5620, Planning Manual

Page: 132 / 144

Deploying the 5620 SAM with multiple network interfaces/IP
addresses
Deploying the 5620 SAM with multiple network interfaces/IP addresses
The 5620 SAM Server and 5620 SAM Auxiliary Collector components of the application
communicate with very different entities: a managed network, a collection of Clients
(GUIs and OSS), and between each other. Since these entities usually exist in very
different spaces, Alcatel-Lucent recognizes the importance of separating these different
types of traffic. Alcatel-Lucent therefore supports configuring the 5620 SAM Server and
5620 SAM Auxiliary such that it uses different network interfaces (IP addresses) to
manage the network and to service the requirements of the 5620 SAM Clients.
5620 SAM Server uses an internal communications system (JGroups/JMS) to handle
bi-directional access to the 5620 SAM Server for the 5620 SAM Clients and the 5620
SAM Auxiliary Collectors. In 5620 SAM, this communication system can be configured
to allow the 5620 SAM Clients and 5620 SAM Auxiliary Collectors to communicate
using different network interfaces on the 5620 SAM Server. This adds significant
flexibility when isolating the different types of traffic to the 5620 SAM Server. If using
this mode, special attention must be paid to the firewall rules on the network interfaces on
the 5620 SAM Server and 5620 SAM Auxiliary Collector (NICs 1 and NICs 3 on
Figure
8-2, “Distributed 5620 SAM Server/Database deployment with multiple network
interfaces” (p. 8-4)
).
It is a security requirement that all IP communications from a 5620 SAM Auxiliary
Collector to the 5620 SAM Main server use only one IP address. This IP Address must be
the same IP address as the Auxiliary Collector IP address configured when installing the
Main Server. Any other IP communications originating from a different IP address on the
Auxiliary Collector will be rejected by the 5620 SAM Main Server.
When installing 5620 SAM components on workstations with multiple interfaces, each
interface must reside on a separate subnet, with the exception of interfaces that are to be
used in IP Bonding.
Figure 8-1, “Collocated 5620 SAM Server/Database deployment with multiple network
interfaces” (p. 8-3)
illustrates a collocated 5620 SAM Server/Database deployment where
the 5620 SAM is configured to actively use more than one network interface.
It is not necessary to use the first network interface on the 5620 SAM Server workstation
(i.e. ce0, bge0) to communicate with the 5620 SAM GUI Clients.
Deploying the 5620 SAM with multiple network
interfaces/IP addresses Deploying the 5620 SAM with multiple network
interfaces/IP addresses
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
8-2 5620 SAM
3HE-09809-AAAG-TQZZA 13.0 R7
Issue 1 December 2015