Notably, unlike the base client table's row-creation behavior, the description here explicitly states a newly created login-auth server row starts out administratively disabled by default. An admin who creates a row and expects it to immediately start authenticating logins needs the extra step of explicitly setting this to active, and skipping that step is a plausible reason a newly-added backup login server never actually gets used. For example, a technician who creates a new backup login-auth server row and stops there, never setting status to active, would find it never actually receives any login authentication traffic, since it stays disabled by default.