Portal Stateful Failover - HP 5500 HI Series Configuration Manual

5. After receiving the certificate request, the portal server sends an EAP authentication reply to the
authentication client, carrying the EAP-Message attribute values.
6. The authentication client sends another EAP request to continue the EAP authentication with the
RADIUS server, during which there may be several portal authentication requests. The subsequent
authentication processes are the same as that initiated by the first EAP request, except that the EAP
request types vary with the EAP authentication phases.
7. After the authentication client passes the EAP authentication, the RADIUS server sends an
authentication reply to the access device. This reply carries the EAP-Success message in the
EAP-Message attribute.
8. The access device sends an authentication reply to the portal server. This reply carries the
EAP-Success message in the EAP-Message attribute.
9. The portal server notifies the authentication client of the authentication success.
10. The portal server sends an authentication reply acknowledgment to the access device.
The remaining steps are for extended portal authentication. For more information about the steps, see the
portal authentication process with CHAP/PAP authentication.

Portal stateful failover

Overview
The stateful failover feature supports hot backup of services on two devices. It can be configured on key
devices to avoid service interruptions caused by single point failures. When working normally, the two
devices synchronize the service information of each other. If one device fails, the other device takes over
the services.
To implement stateful failover, specify a dedicated VLAN (called the "backup VLAN") on each device for
stateful failover packets. If both a failover link and a backup VLAN are configured, add the physical ports
at the two ends of the failover link to the backup VLAN. For more information about the stateful failover
feature, see High Availability Configuration Guide.
127