Filter
Top Products
14-4
Cisco Broadband Access Center 3.8 Administrator Guide
OL-27172-01
Chapter 14 CWMP Device Operations
Connection Modes for Device Operations
Figure 14-2 illustrates the high-level flow for on-connect operations.
Figure 14-2 On-connect Operation Mode Workflow
The API client constructs an IPDeviceOperation specifying an on-connect execution. It registers the
appropriate AsyncOperationEvent listeners, then invokes the performOperation() API method. The RDU
then constructs and sends corresponding operation instructions to all DPEs in the device’s provisioning
group. The DPEs save the operation in their internal database. The RDU batch completes, and the
BatchStatus is returned to the API client.
The DPE does not initiate a connection request notification to the device, as it does while running an
immediate operation.
When the device connects to the DPE the next time, the DPE creates a new session with the device and
runs the operation upon the device. When the session is closed, the operation result is sent to the RDU,
and the RDU sends an AsyncOperationEvent to any registered API client listeners.
Immediate operations are always run before on-connect operations. While you can use Cisco BAC to
mix modes of operations along with the built-in instructions, you must ensure that the instructions do
not override one other.
For example, if the device's configuration template specifies False for
InternetGatewayDevice.ManagementServer.PeriodicInformEnable and a device operation changes that
to True, the configuration template, which runs only after the device operation, overrides it to False.
API RDU DPE Device
Submit Operation
Operation Pending
Establish Session
On Connect Operation
Operation Result
Execute Operation
Remove On Connect Operation
Operation Result
Operation Result
158274