Athena EPP (Endpoint Protection Platform)

Athena EPP (formerly Sangfor Endpoint Secure) integrates NGAV, EDR, and endpoint management into a single, powerful solution for comprehensive endpoint protection.
{{ $t('productDocDetail.guideClickSwitch') }}
{{ $t('productDocDetail.know') }}
{{ $t('productDocDetail.dontRemind') }}
6.0.4R4
Athena EPP (Endpoint Protection Platform) {{ breadTitle }} User Manual Installation and Deployment Athena EPP Manager Deployment Configuring Multiple IP Addresses for MGR
{{sendMatomoQuery("Athena EPP (Endpoint Protection Platform)","Configuring Multiple IP Addresses for MGR")}}

Configuring Multiple IP Addresses for MGR

{{ $t('productDocDetail.updateTime') }}: 2026-04-08

I. Applicable Scenarios

  • Cross-Segment/Cross-Domain Management 
    In enterprise networks segmented into isolated zones such as office networks, production networks, and DMZs, a single MGR IP address often cannot traverse firewalls to manage all endpoints. Configuring multiple MGR IP addresses to suit different network segments ensures policy deployment, log collection, and other functions for all endpoints.

  • High Availability Assurance 
    For industries requiring 24/7 uninterrupted service, such as finance and government, configuring primary/backup IPs or multiple IPs in a cluster eliminates single points of failure. This enables seamless failover without endpoint disruption, ensuring business continuity.

  • Simultaneous Internal and External Network Access 
    To manage both internal fixed endpoints and external mobile endpoints (e.g., devices used by remote or traveling employees), configure a combination of a private internal MGR IP and a public MGR IP. This meets endpoint security management requirements for remote work scenarios.

 

II. Configuration Steps

  1. Gather the MGR addresses the customer needs to configure, such as: internal IP addresses, external IP addresses, and external domain names.

  2. Log in to the EPP console, navigate to System > Network > Advanced > Manager IP Address, and enter all MGR addresses required for communication. 

  

If multiple addresses are not configured in the Console, and an agent directly connects to a multi-address MGR cluster, the agent's built-in MGR address list may be inadvertently overwritten. This can lead to connection failures to the MGR. Therefore, you must specify all MGR communication addresses on the Console page.