If you need to make extensive changes to the system, or if you are
importing a new system version, the following requirements could arise:
- Larger configuration changes should be distributed to all CC-APs as
quickly as possible
- After completing the changes, you should initiate an “unscheduled“
backup. However, make sure that you verify that there is sufficient transmission
bandwidth available in the network at this time to complete the backup
and the subsequent restore operations of the CC-APs. Remember that you
cannot cancel backup and restore procedures that are active. It may be
useful to deactivate the backup process before making the changes. ->
See the second point. In the OpenScape 4000 Assistant Backup & Restore,
go to the schedule for the backup type “AP Emergency“ and click Start
now. It is not advisable to use “Backup“ for this. If you do,
you must remember to run an EXEC-UPDAT beforehand.
- You should verify new SW (regardless of whether it is a pre-revision bug
fix of an LW or a new system version) on the host system first, before
distributing it to all CC-APs.
- Before importing new SW: In the OpenScape 4000 Assistant Backup
& Restore, go to the schedule for the backup type “AP Emergency“
and change the status from “activated“ to “deactivated“.
If there are several entries in the schedule for the backup type “AP
Emergency“, you must deactivate all entries that could apply during
the planned interval.
- After successful verification of the SW: In the OpenScape
4000 Assistant Backup & Restore, go to the schedule for the backup
type “AP Emergency“ and change the status from “deactivated“
back to “activated“. If there are several entries in the schedule
for the backup type “AP Emergency“, you must activate all entries
that you previously deactivated. If the network allows it, it may be
useful to initiate an unscheduled backup. -> See the first point.