Nortel INM 4.1, Руководство по планированию

Страница: 55 / 202

INM 4.1 New Feature Description 55 of 202
INM Release 4.1 Planning Guide PG OC 98-13 Issue 1.2
In order for the bump request to be successful, the following conditions must
be met:
• The INM that is being bumped (bumpee) must be a promoted client
(directly connected, configured indirect).
• The promoted client must have the server which is sending the bump
request (bumper) on its server access list.
• Both the bumper and the bumpee must be running INM Broadband
Release 4.1 or higher. If the bumpee is running INM Broadband Release
3.1, the bump request will be ignored.
Figure 15 on page 55 illustrates the bump request scenario which provides a
self-healing property to the server client relationship.
Figure 15. Scalability Bump Request
OPC
GNE/GNB
XDR-MOA
CLIENT SERVER 1
SERVER 2
SERVER 3
SERVER 4
4 SLOTS
1 - Server 1 is down, the connection is lost
2 - The Client promotes itself
3 - Server 1 is restarted, but the Controller is busy
4 - Server 1 sends a Bump Request
5 - The promotes client demotes itself
6 - Server 1 wins the slot back