INM 4.1 New Feature Description 55 of 202INM Release 4.1 Planning Guide PG OC 98-13 Issue 1.2In order for the bump request to be successful, the following conditions mustbe 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 bumprequest (bumper) on its server access list.• Both the bumper and the bumpee must be running INM BroadbandRelease 4.1 or higher. If the bumpee is running INM Broadband Release3.1, the bump request will be ignored.Figure 15 on page 55 illustrates the bump request scenario which provides aself-healing property to the server client relationship.Figure 15. Scalability Bump RequestOPCGNE/GNBXDR-MOACLIENTSERVER 1SERVER 2SERVER 3SERVER 44 SLOTS1 - Server 1 is down, the connection is lost2 - The Client promotes itself3 - Server 1 is restarted, but the Controller is busy4 - Server 1 sends a Bump Request5 - The promotes client demotes itself6 - Server 1 wins the slot back
