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
accepts only subtract and audit commands from the gateway controller.
Forcing the Shutdown of a Virtual BGF
To perform a forced shutdown of the virtual BGF, enter set
service-state out-of-service-forced at the [edit services
pgcp gateway gateway-name] hierarchy level.
For example:
[edit services pgcp gateway bgf-1]
user@host#set service-state out-of-service-forced
Performing a Graceful Shutdown of a Virtual BGF
To perform a graceful shutdown of the virtual BGF, enter set service-state out-of-service-graceful at the [edit
services pgcp gateway gateway-name] hierarchy
level. For example:
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: