Ericsson SPR1100, Руководство пользователя, Страница: 240 / 256

Home > SPR1100 Handbook > Appendices > Redundancy Modes > 1+1 Multi-Unit Redundancy > Hints and Tips
1 + 1 Redundancy Hints and Tips
This page provides a few hints and tips for using 1 + 1 redundancy.
Enable MGP
It is possible for the 1 + 1 Redundancy system to have both units Active. This can happen if
the control connection between the units fails. In this case the secondary thinks the primary
has failed, and becomes Active. This could cause duplicate multicast packets on the output
data network. To prevent this it is recommended that MGP is always enabled in a 1 + 1
Redundancy system.
To enable MGP, open the web GUI and click "Configure", then "System", then "MGP
Support". Set "MGP Mode" to "On", click "Apply Changes", then OK on the popup dialog.
Use SNTP to Synchronise Time
It is recommended that SNTP is used to ensure that the system clock on each unit reports
the same time. This can be configured from the web GUI by clicking "Configure" then
"Device Info" and setting the "SNTP Server" setting.
Beware of changing the "Device State (setmode)"
When a redundancy switch is performed (either manual or automatic), the "Device State
(setmode)" may be changed, overriding any manual change to this configuration.
If you need to manually adjust this setting it is recommended that you set the 1 + 1
Redundancy "Availability" setting to "Unavailable" on both units prior to making any change.
This will prevent the 1 + 1 Redundancy system from performing an automatic redundancy
switch.
Power down unused secondaries
If a Secondary unit is not being used, but is connected to power it will attempt to contact its
peer. After 30 seconds of not being able to, it will go Active. At this point the 30 day timed
license will start being consumed. If the unit is left in this state for 30 days, it will be
rendered useless until the license is renewed. For this reason a secondary unit that is not
being used should be disconnected from the power supply.
Resolving "Configuration Mismatch" alarm
The configuration mismatch alarm indicates that the configuration on the 2 units may not be
identical. This alarm is triggered if a configuration change is made on one unit whilst the
other unit is not contactable. It is also triggered if the pairing process is unable to work out
which unit should be Active. In this situation the user should manually decide which unit has
the most up to date configuration. The "Last Updated" value may be useful to determine
this, however since communication was lost, this may not reflect the correct value for the
other unit. You should check the Primary "Last Updated" time using the Primary web GUI