15.1 |
Definition |
| A HiPath 3000/5000 network can contain the following components: |
| • | HiPath 3000 systems with HiPath ComScendo Service |
| • | HiPath 5000 PCs with HiPath ComScendo Service The HiPath ComScendo Service is effectively a fully-fledged HiPath node (IP softswitch) that is configured as software on a PC. Apart from the dedicated TDM characteristics, all of the features of V5.0 are available. |
| • | HiPath 5000 Real-Time Services Manager (RSM) as the central administration unit in an IP network, with or without HiPath ComScendo Service All relevant nodes (HiPath 3000 and HiPath 5000 with HiPath ComScendo Service) can be centrally administered by creating a "single system image". |
| The HiPath ComScendo Service Resilience feature guarantees failure tolerance for the IP workpoint clients associated with a HiPath ComScendo Service or a HiPath 3000 system. In the event of a HiPath 5000 PC or HiPath 3000 system failure or an error in the HiPath 3000 ComScendo Service, the configured IP stations (resilience stations) are assigned to a standby system (resilience destination). This can be another HiPath ComScendo Service or a HiPath 3000 system. |
|
| Only default features are available to the IP stations on the standby system (see Page 15-3). |
| This feature requires a HiPath 3000/5000 network with HiPath 5000 RSM, as monitoring and control are performed by the Feature server's Resilience Service Application (RSA). If the Feature server is unable to access a node, three additional connection attempts are initiated. If these attempts also fail, HiPath ComScendo Service Resilience is activated. |
| The availability of the failed system is checked again. When the Feature server can access this node again, the resilience stations are once again assigned to their home system. |
| When configuring a standby system, remember that both the "regular" stations and the resilience stations have to be set up. The default station numbers and names of the resilience stations must be deleted. |
|
| If a node failure is detected and HiPath ComScendo Service Resilience is activated, the resilience stations are assigned to their standby system (resilience destination). The internal station numbers configured on the home system, the DID numbers, and the names of the resilience stations are transferred to the standby system. The Feature server is responsible for automatically updating the numbering tables (CAR tables) in the HiPath 3000/5000 network. |
| When the node is operational again, the resilience stations are once again assigned to their home system and the original situation is thus restored. On the standby system, the station numbers and names of the resilience stations are automatically deleted and the numbering tables (CAR tables) are updated in the HiPath 3000/5000 network. |
| HiPath 3000/5000 Manager E can be used to defined for each system client (OpenScape Personal Edition, optiPoint 410, optiPoint 420, OpenStage CorNet-IP [HFA]) whether it is a resilience station. H.323 clients are not supported. |
Model-Specific Data |
|
|||||||||||||||||||||||||||||||||||||||
Dependencies/Restrictions |
|
| HiPath 3000/5000 V9, Feature Description, Issue 7 | up ![]() |
|
![]() |
||
| Disclaimer & Copyright | ID: P31003H3590F100017618 | 2012-06-25 |