Configuring Static Routes for Multi-Subnet Environments for PGP Encryption Server

Products

• PGP Command Line
• PGP Key Management Server
• PGP Key Mgmt Client Access and CLI API
• PGP SDK
• Policy-Based Email Encryption PGP Cloud
• Desktop Email Encryption
• Drive Encryption
• Encryption Management Server
• Endpoint Encryption
• File Share Encryption
• Gateway Email Encryption

Issue/Introduction

Purpose: This article outlines the requirements for implementing custom static routes on PGP Encryption Server (Symantec Encryption Management Server) when operating in complex network environments.

Overview: The PGP Encryption Server is designed to operate primarily on Interface 1 (eth0). In environments requiring communication across multiple subnets, automatic routing may be insufficient. While simple routing adjustments can be made via standard Linux network configuration, advanced multi-interface or multi-subnet setups often require persistent custom routing scripts to maintain stability across reboots.

Resolution

Custom routing files are not included in the standard PGP Encryption Server configuration.

Ensure your virtual adapters are configured with static MAC address assignments for all PGP Encryption Server virtual network adapters to ensure they don't get changed after reboot.

If you observe network interface name shuffling (e.g., eth0 becoming eth1 after reboot, etc), reach out to PGP Encryption Support for further guidance.

Additional Information

IMSFR-1140