10.1.8.2. Service Information 
Conditions for switchover
The following conditions are checked before a switchover is triggered:
- The BP is active and in normal operation mode (i.e. last restart/reload is finished).
- There has not already been triggered a switchover because of this LAN monitoring feature.
- The partner BP is in state and the own DB and the DB of the partner BP are consistent. (-> necessary conditions for a successful switchover).
Note
If it happens at some point that after a second switchover caused
by LAN monitoring feature the active BP still does not have LAN connectivity
with APs then it will stay in this state until the defective LAN (on
the active BP) is back in service. Then the LAN monitoring will start
to work again.
A practical example: when both LANs are cut off simultaneously, LAN
monitoring will do two switchovers, then will stop monitoring until the
active BP's LAN is repaired.
DEP ADVISORY messages
The following DEP ADVISORY messages have been implemented for the
LAN monitoring feature:
- switchover has been triggered:
F4266 M8 N0096 SOFTREST BPA DEP ADVISORY xx-xx-xx
yy:yy:yy
ALARM CLASS:CENTRAL:005
FORMAT:42
NO AP SHELF CONNECTED
PARTNER CC AVAILABLE
SWITCHOVER INITIATED
- switchover is rejected because of AMO ZANDE switch NOLANMON:
F4266 M8 N1979 NO ACT BPA DEP ADVISORY xx-xx-xx
yy:yy:yy
ALARM CLASS:CENTRAL:023
FORMAT:42
NO AP SHELF CONNECTED,
SWITCHOVER REJECTED:
CHECK AMO ZANDE NOLANMON
- switchover is rejected because already one switchback has been triggered before:
F4266 M8 N1979 NO ACT BPA DEP ADVISORY xx-xx-xx
yy:yy:yy
ALARM CLASS:CENTRAL:023
FORMAT:42
NO AP SHELF CONNECTED,
SWITCHOVER REJECTED:
NO FURTHER SWITCHBACK
- switchover is rejected because partner BP is not :
F4266 M8 N1979 NO ACT BPA DEP ADVISORY xx-xx-xx
yy:yy:yy
ALARM CLASS:CENTRAL:023
FORMAT:42
NO AP SHELF CONNECTED,
SWITCHOVER REJECTED:
PARTNER IS NOT