Fortinet black logo

Aruba Controller Redundancy Options

Aruba Controller Redundancy Options

Active/Active

Both master and local controllers are active on the network, supporting wireless traffic.

Active/Active Configuration – Mobility Master and VIPs per Controller

(Aruba OS8 )

Each controller is active and has both a virtual and physical IP address. Should one of the controllers fail, one of the other controllers take ownership of the virtual IP, along with all the wireless sessions being managed.

Although the controller is accessed using the virtual IP for session and other device queries, controllers with this configuration continue to source RADIUS authentication requests using their physical interface IP address.

Active/Passive Configuration

Only the master controller is active on the network processing wireless traffic. The passive controller operates in a standby mode ready to take over should the master fail.

In this environment, a virtual IP address is used. The virtual IP is owned by the actively running controller. Should the master fail, the local standby controller takes ownership of the virtual IP, along with all the wireless sessions being managed.

Although the controller is accessed using the virtual IP for session and other device queries, controllers with this configuration continue to source RADIUS authentication requests using their physical interface IP address.

FortiNAC will accept the request from the source but uses the NAS-IP RADIUS attribute in the packet to look up the actual controller model for FortiNAC configuration values.

Aruba Controller Redundancy Options

Active/Active

Both master and local controllers are active on the network, supporting wireless traffic.

Active/Active Configuration – Mobility Master and VIPs per Controller

(Aruba OS8 )

Each controller is active and has both a virtual and physical IP address. Should one of the controllers fail, one of the other controllers take ownership of the virtual IP, along with all the wireless sessions being managed.

Although the controller is accessed using the virtual IP for session and other device queries, controllers with this configuration continue to source RADIUS authentication requests using their physical interface IP address.

Active/Passive Configuration

Only the master controller is active on the network processing wireless traffic. The passive controller operates in a standby mode ready to take over should the master fail.

In this environment, a virtual IP address is used. The virtual IP is owned by the actively running controller. Should the master fail, the local standby controller takes ownership of the virtual IP, along with all the wireless sessions being managed.

Although the controller is accessed using the virtual IP for session and other device queries, controllers with this configuration continue to source RADIUS authentication requests using their physical interface IP address.

FortiNAC will accept the request from the source but uses the NAS-IP RADIUS attribute in the packet to look up the actual controller model for FortiNAC configuration values.