[an error occurred while processing this directive][an error occurred while processing this directive]

Shutting Down a Virtual Interface

Shutting down the virtual interface is useful when you do not want to shut down the entire virtual BGF. You can shut down the virtual interface in two ways:

  • Forced—The virtual interface immediately removes all calls and disconnects from the physical interface.
  • Graceful—The virtual interface 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, terminations associated with the virtual interface accept only subtract commands from the gateway controller.

The following topics describe how to shut down a virtual interface:

Forcing the Shutdown of a Virtual Interface

To perform a forced shutdown of a virtual interface, enter the set service-state out-of-service-forced statement at the [edit services pgcp virtual-interface interface-number] hierarchy level. For example:

[edit services pgcp virtual-interface 1]user@host# set service-state out-of-service-forced

Performing a Graceful Shutdown of a Virtual Interface

To perform a graceful shutdown of a virtual interface, enter the set service-state out-of-service-graceful statement at the [edit services pgcp virtual-interface interface-number] hierarchy level. For example:

[edit services pgcp virtual-interface 1]user@host# set service-state out-of-service-graceful

Making the Virtual Interface Operational Again

To cause the virtual interface 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 interface is in service, it is connected to the physical interface and accepts all voice calls. For example:

[edit services pgcp virtual-interface 1]user@host# set service-state in-service

Published: 2010-04-13

[an error occurred while processing this directive]