There are several instances in which GAB will intentionally panic a system. For example, GAB panics a system if it detects an internal protocol error or discovers an LLT node-ID conflict. Other instances are as follows:

• Client process failure

  See About GAB client process failure.

• Registration monitoring

  See About GAB client registration monitoring.

• Network failure

  See About network failure and GAB IOFENCE message.

• Quick reopen

  See About quick reopen.