PE Interface acceptance test

Last Updated : Aug 24, 2023 |

Scenario

Acceptance criteria

Outcome

Verification parameters for the wanted outcome

Main server is duplicated and PE interface is not used

PE interface is not enabled (no ESS server is provided and no IP endpoints are controlled by PE interface)

Status Summary page shows:

  • PE connection is not functional on both servers

  • PE connection is not functional on both servers

  • PE Interface is set to UNUSED on the Set Identities page

  • PE Interchange Priority is set to IGNORE on the Configure Interfaces page

  • Functional Assignment for eth0 does not include PE on the Network Configuration page

  • PE Interchange Priority is set to IGNORE on the Duplication Parameters page

Main server is duplicated and PE interface is used

PE Interface is enabled on the main server and the ESS server (either ESS server is provided or IP endpoints are controlled by PE interface, or both)

Status Summary page shows:

  • PE connection is not functional on both servers

  • PE priority is set to the same value (but not IGNORE) for both servers

  • PE Interface is set to one of the Ethernet interfaces on the Set Identities page

  • PE Interchange Priority is set to the same value (but not IGNORE) on the Configure Interfaces page on both servers

  • Functional Assignment for eth0 includes Processor Ethernet on the Network Configuration page

  • PE Interchange Priority is set to the same value (but not IGNORE) on the Duplication Parameters page on both servers

Either the main server or the ESS server is duplicated

–

Current Alarms page (or running almdisplay -v on the command prompt) shows no active _PE alarms for up to 15 minutes after both servers have been running as an active or standby pair

–