Shutting Down a Virtual BGF
You can shut down the virtual BGF in two ways—forced or graceful:
- Forced—The virtual BGF immediately removes all gates and disconnects from the gateway controller. The virtual BGF does not attempt to establish a new connection.
- Graceful—The virtual BGF goes out of service by entering a draining mode and waiting for all terminations to be subtracted before going out of service. During the draining, the virtual BGF by default accepts only subtract and audit commands from the gateway controller. However, you can specify that add commands for emergency calls are to be accepted during the draining.
This topic consists of the following:
Forcing the Shutdown of a Virtual BGF
To perform a forced shutdown of the virtual BGF, enter the set service-state out-of-service-forced statement at the [edit services pgcp gateway gateway-name] hierarchy level. For example:
Performing a Graceful Shutdown of a Virtual BGF
To perform a graceful shutdown of the virtual BGF, enter the set service-state out-of-service-graceful statement at the [edit services pgcp gateway gateway-name] hierarchy level. For example:
Allowing Emergency Calls While the BGF Is Draining
To allow the BGF to accept new emergency calls during draining due to a graceful shutdown:
- Access the h248-options hierarchy level.user@host# edit services pgcp gateway bgf-1 h248–options
- Set the option to accept emergency calls
while draining.[edit services pgcp gateway bgf-1 ]user@host# set accept-emergency-calls-while-graceful
Making the Virtual BGF Operational Again
To cause the virtual BGF to be operational again and available for traffic, set the service state to in-service with the set service-state in-service statement. When the virtual BGF is in service, it attempts to connect to the gateway controller and accepts all PGCP commands from the gateway controller. For example:
