ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Symantec Encryption Management Server clustering and replication uses network Interface 1
Article ID: 222372
Updated On:
Products
Encryption Management Server
Gateway Email Encryption
Issue/Introduction
By default, Encryption Management Server uses network Interface 1 for clustering and replication. Note that Symantec Encryption Management Server (PGP Server) refers to the first network interface - normally eth0 - as Interface 1.
If Encryption Management Server has more than one network interface, a different network interface can be used for clustering and replication. However, before making this change, please consider the following:
- If the network interface you wish to use for clustering and replication is on a different subnet to Interface 1, you will probably need to create a static routing file. For example, /etc/sysconfig/network-scripts/route-eth1.
- Static routing files are not included in the Encryption Management Server backups.
- Changing the network interface for clustering and replication cannot be done using the administration console.
- Changes to your firewall rules may need to be made in order to allow the cluster members to communicate on TCP port 444 using the different network interface.
- The network interface card is very unlikely to be a performance bottleneck. Therefore it is highly improbable that there will be any performance advantage to changing the network interface used for clustering and replication.
Environment
Symantec Encryption Management Server 10.5 and above.
Resolution
For these types of issues and for more technical clustering, please reach out to Symantec Encryption Support for further assistance.
Additional Information
Feedback
Yes
No
Powered by
