Atlas 500 AI edge station
Figure 2-1 shows the typical networking of the Atlas 500 AI edge station. IEF is short for Intelligent EdgeFabric, and FD is short for FusionDirector.
Device |
Port |
IP Address |
Description |
|---|---|---|---|
Atlas 500 AI edge station (active) |
ETH0 |
Floating IP address (active) |
Used for the Atlas 500 AI edge station to communicate with external devices, such as IP cameras (IPCs). If the active node is faulty, the floating IP address of the active node is migrated to the standby node, and the standby node uses this IP address to communicate with external devices. If the user service does not need to connect to external devices, you do not need to set the floating IP address. |
Arbitration IP address (active) |
Used to assist the dual backup function in active/standby arbitration. This IP address is optional. The system periodically checks whether the arbitration IP address can be pinged to determine the network connectivity. Generally, this parameter is set to the IP address of the gateway. |
||
Management IP address (active) |
|
||
ETH1 |
Heartbeat IP address (active) |
Used for information exchange and file synchronization between the active and standby nodes. |
|
Atlas 500 AI edge station (standby) |
ETH0 |
Floating IP address (standby) |
To detect the floating IP address status of the active node, you need to configure an IP address that is in the same network segment as the floating IP address of the active node for the standby node to ensure that the floating IP address of the active node can be pinged from the standby node. |
Arbitration IP address (standby) |
Used to assist the dual backup function in active/standby arbitration. This IP address is optional. The system periodically checks whether the arbitration IP address can be pinged to determine the network connectivity. Generally, this parameter is set to the IP address of the gateway. |
||
Management IP address (standby) |
|
||
ETH1 |
Heartbeat IP address (standby) |
Used for information exchange and file synchronization between the active and standby nodes. |
The port and IP address planning in the preceding table is only for reference. You need to configure the IP addresses of each network port according to the actual planning. It is recommended that the heartbeat IP address be configured on an independent network port (for example, ETH1 in the preceding table) to improve the reliability of the HA system.
