9-19 MINI-LINK BAS
EN/LZB 111 0542 P2B Technical Description
9.7.9 Restart Control Processor
After all the upgradeable boards have swapped the passive and active
load modules, the CP must be restarted in order to re-establish the
complete system functionality. In this phase, all the ATs are signed-on
again, the network database is restored and the CP makes an audit
procedure on all the network.
The time needed for this operation is very much depending on the
number of ATs to be reconnected. The audit procedure time is in the
range of 1-10 minutes.
At the end of the CP restart, the system functionality and the traffic
are completely restored and the new baseline is installed.
9.7.10 Software Rollback
As each upgradeable object has two non-volatile memories, it is
always possible to swap back to the previous load module without the
need of executing again a complete SW upgrade procedure.
Note: The SW rollback procedure will be available from R1D to
R1C in the next release.
Three cases are considered here:
1. The installation of the new SW baseline is completed
successfully and all the connections have been re-established.
2. The installation of the new SW baseline implies problems in the
radio connection that prevent all the ATs to be reconnected to the
hosting radio node.
3. An intermediate situation between 1 and 2.
9.7.10.1 Case A
In this case, all the connections have been re-established and the CP
has complete control of the network.
In order to rollback the SW baseline, a procedure similar to the SW
upgrade must be executed, as shown in Figure 9-4. The difference
with respect to the previous procedure, is that no transfer of load
modules is executed, but directly an upgrade with the previous sw
baseline as a target.
Note: As already mentioned in the introduction, the upgrade
command is not related to any temporal relationship
beween two SW versions, therefore it can be executed an
upgrade command towards a previous SW baseline.
To Next Page
Loading...
Need help?
General
