Question: When the central system breaks down, an OpenScape 4000
system with IPDA and AP Emergency is divided into 5 islands. Each island
is controlled by a survivability unit. Can islands communicate via IP
insofar as this is permitted by the IP network?
Answer: No. Each island represents an individual system in emergency
mode. These systems only communicate via CO or tie trunks.
Follow-up question: If I configure IP trunking between the
islands, will it work then?
Answer: In principle yes, however, you cannot only configure IP trunking
for emergencies. It must be configured in the central system and is then
also available during normal operation. You must pay particular attention
here that you are dealing with tie trunks in normal operation within
a system, something that is very difficult to manage in terms of LCR.
Therefore, we would strongly advise against such scenarios.
Question: Is the Survivable OpenScape 4000 SoftGate (OpenScape
Access/Branch 500 a/i/) able to take over the control (survival mode)
for the local OpenScape 4000 SoftGate machine in case of a local LAN
failure (L1/eth0 down)?
Answer: Yes. On a OpenScape Access/Branch 500 hardware the signaling
routing (HSR) can be handled on internal path (backplane), i.e. no external
LAN needed. If there are OpenScape Access modules connected over Xlink
they will continue to work also.
Question: Can Minor/Fixed Release upgrades be made via hard disk
exchange with APEs and Survivable OpenScape 4000 SoftGates?
Answer: Please note when upgrading a system in the main system
via hard disk exchange, the OpenScape 4000 Platform Administration (Portal),
OpenScape 4000 CSTA and OpenScape 4000 Assistant(1)
on APEs and Survivable OpenScape 4000 SoftGates will not be automatically
upgraded.
Under such circumstances there are two possible courses of action
to ensure the APEs and Survivable OpenScape 4000 SoftGates receive the
correct software afterwards:
The new host system hard disk for the customer upgrade should be prepared
in the lab with the identical version as the existing customer software
level and then upgraded to the version the customer requires via SWA/SWT.
In this way the upgrade history exists on the new hard disk and with
the next HBR for the APE/Survivable OpenScape 4000 SoftGate the correct
packages will be transferred and an automatic update performed to the
correct OpenScape 4000 Platform Administration (Portal), OpenScape 4000
CSTA and OpenScape 4000 Assistant(1) versions.
After installation of the new hard disk with a newer version made with
First Installation, RMX would only upgrade on the APEs/Survivable OpenScape
4000 SoftGates, but OpenScape 4000 Platform Administration (Portal),
OpenScape 4000 CSTA and OpenScape 4000 Assistant
1 versions will not be updated due to the missing upgrade history.
Once the Fix Release/Maintenance Release is transferred and activated
individually on each APE/Survivable OpenScape 4000 SoftGate via SWT/SWA,
any subsequent Hot Fixes will be activated automatically with the next
HBR.
IMPORTANT:
Linux host OpenScape 4000 Platform Administration
(Portal) (PLT) and OpenScape 4000 CSTA are not included in this backup.
Therefore if host system is updated by replacing system hard disk, then
each connected APE/Survivable OpenScape 4000 SoftGate has to be either
installed anew or updated with RLC of the same version as the new host
hard disk.
IMPORTANT:
This handling of course does not apply for upgrades
where a new installation is needed. After installing the central host
with OpenScape 4000 software, only RMX would replicate to APEs/Survivable
OpenScape 4000 SoftGates, but OpenScape 4000 Platform Administration
(Portal), OpenScape 4000 Assistant and OpenScape 4000 CSTA will not be
updated. Therefore the APEs/Survivable OpenScape 4000 SoftGates must
be newly installed and then synchronized with the central host.
Question: Should Activation of Hot Fixes on APEs and Survivable
OpenScape 4000 SoftGates be made?
Answer: As per SWA graphical user interface activation hints:
ATTENTION: Activation of Hotfixes and FR/MR should not be made directly
on APE Nodes !!!
Software updates should be activated directly on the Host system and
will be mirrored to the APE nodes during the next APE restore process.
Direct activation on APE should only be used in rare instances of
first installation or manual upgrade.
(1)
Note: OpenScape 4000
Assistant Upgrade can be forced via Option I in HBR, however this is
not recommend as standard and would not upgrade the OpenScape 4000 Platform
Administration (Portal) or OpenScape 4000 CSTA as already commented in
the Service Manual.
