Redundancy deployment considerations for 5620 SAM
Overview
When deploying 5620 SAM in a redundant configuration, the following items should be
considered.
It is a best practice to keep the 5620 SAM Server, 5620 SAM Database, and 5620 SAM
Auxiliary Collectors in the same geographic site to avoid the impact of network latency.
When the 5620 SAM Database or 5620 SAM Server switches sites, the 5620 SAM
auto-align functionality will ensure the SAM Server, and 5620 SAM Auxiliary Collectors
are all aligned in the same geographic location. If the auto-align functionality is not
enabled, a manual switch of the workstations is desirable.
Redundancy with collocated 5620 SAM Server/Database
Requirements:
•
The operating systems installed on the primary and standby 5620 SAM
Server/Database must be of the same versions and at the same patch levels.
•
The layout and partitioning of the disks containing the 5620 SAM software, the
Oracle software and the database data must be identical on the active and standby
5620 SAM Server/Database.
•
The machine which will be initially used as the active 5620 SAM Server/Database
must be installed or upgraded before the machine that will initially be used as the
standby.
•
The workstations hosting the 5620 SAM software should be connected in a way to
prevent a single physical failure from isolating the two workstations from each other.
•
Workstations running the 5620 SAM Server/Database software must be configured to
perform name service database lookups on the local workstation before reverting to a
name service database located on the network such as NIS, NIS+, or DNS. A root user
must inspect and modify the /etc/nsswitch.conf file to ensure that files is the first entry
specified for each database listed in the file.
Redundancy with distributed 5620 SAM Server and 5620 SAM Database
Requirements:
•
The operating systems installed on the primary and standby 5620 SAM Server as well
as the primary and standby 5620 SAM Database must be of the same versions and at
the same patch levels.
•
The layout and partitioning of the disks containing the 5620 SAM software, the
Oracle software and the database data must be identical on the primary and standby
5620 SAM Database.
Product deployment overview
Redundancy deployment considerations for 5620 SAM
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
5620 SAM
3HE-09809-AAAG-TQZZA 13.0 R7
Issue 1
December 2015
1-15