13.07.2015 Views

Next Generation ESNet Arch Requirements - ATIS

Next Generation ESNet Arch Requirements - ATIS

Next Generation ESNet Arch Requirements - ATIS

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

CESERGApplication Session1. Logout Message (includes CESEID and Application Session ID)2.ACKFigure 7-2 CESE Logout7.1.1.3 RG ShutdownThe RG issues a Shutdown message when it determines that it must shut down the currentconnection. It will make a best effort to send an Acquiesce request (see 7.2.2) before itsends a Shutdown. Steps 1 and 2 of Figure 7-3 can be used to illustrate this scenario.Examples of when an RG will issue a shutdown message include: 1) the RG hasencountered a critical abnormal processing condition and must restart or 2) the RGmaintenance personnel are forcing the RG to take itself out of service for maintenancereasons.CESE Receives: Shutdown MessageCESE Sends: Shutdown ACKErrors: NoneNotes:1. The CESE should immediately acknowledge the shutdown message and enter theacquiesce sequence as discussed in Section 7.2.2 if it has not already done so. Itshould expect the current connection to close soon after receiving this message.2. Open Emergency Events, if not completed before the connection physicallyterminates, will have to be re-established when the CESE re-establishes theconnection with a new RG instance.3. The difference between shutdown and acquiesce is that shutdown means that theRG will shut down whether the CESE has created a new connection or not. Theacquiesce request from the RG asks that the CESE create a new connection andclose the old one but will not force the request if the CESE ignores it.4. Shutdown is intended to be a rare event signaling an urgent condition on the RGside. If the CESE acknowledges and performs the acquiesce protocol5 Version 1 9/23/04

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!