Configuring Remote Device Management for Service Provisioning

You must also configure the back-office system that provides the external authority and management platform for remote device service management. That configuration is outside the scope of this topic. Consult the vendor documents for your back-office equipment.

You must configure both dynamic service profiles and remote devices. A dynamic service profile is identified for RDSM by configuring the profile type as remote-device-service. This profile type prevents the profile from being applied locally on the router. It is limited to application on an external device by RDSM. The external authority, such as PCRF can reference this profile to provision or deprovision services on the remote device.

The remote device configuration includes the device IP address and the dictionary path. The remote device must have an entry in an XML dictionary hosted on the MX BNG. The dictionary translates the service action instructions from the external authority to a set of vendor-specific remote procedure calls (RPCs) in the entry associated with the service. The RPCs then provision or deprovision the service.

Finally, you can configure several parameters for the provisioning method, the NETCONF XML protocol. You must configure the username and password used to access the remote device. Other parameters are optional.

Note:

Although the following procedure shows only configuration at the [edit system services] hierarchy level, and therefore the default routing instance, you can also configure RDSM at the [[edit routing-instances routing-instance-name system services] hierarchy level.

To configure remote device service management:

Configure one or more dynamic service profiles. Specify that the dynamic service profile containing this statement is not applied locally to the router. Instead, it is applied to an external device by means of the remote device services manager daemon (rdmd). It enables an external authority, PCRF to reference the dynamic service profile to provision or deprovision services (charging rules) on the remote device.

Configure one or more devices for remote services.

(Optional) Configure the Layer 2 access domain for the remote device.

Configure the address for the remote device.

Specify the absolute file path for the XML dictionary.

Specify the provisioning method (only NETCONF XML protocol is supported).

Configure the provisioning parameters for the NETCONF protocol. You must specify the username and password; all other options have default values.
1. Specify the name used to access the remote device during service management. The maximum length of the name is 64 bytes.
  Note:
  If you change the username when any active subscriber services are mapped to the device, the change takes effect only when the device reconnects.
2. Specify the password used by the NETCONF protocol to access the remote device during service management. The maximum length of the password is 64 bytes.
  Note:
  If you change the password when any active subscriber services are mapped to the device, the change takes effect only when the device reconnects.
3. (Optional) Specify the period during which multiple services are provisioned or deprovisioned based on the assigned dictionary before the configuration is committed to the service device. When the interval times out, the service actions are committed in bulk before additional actions for the device can take place.
  Note:
  You can use the bulk-interval and bulk-limit options together to optimize your service device configuration during scaled subscriber negotiation and service provisioning or subscriber termination and service deprovisioning.
4. (Optional) Specify how many services can be provisioned or deprovisioned during the bulk interval before the configuration is committed to the device.
5. (Optional) Specify how long RDSM waits between successive attempts to establish a NETCONF session with the remote device.
6. (Optional) Specify the TCP port number for the NETCONF session with the remote device.
7. (Optional) Specify how many services can be provisioned or deprovisioned as a result of a reconfiguration before the configuration is committed to the service device. When the limit is reached, the service actions are committed in bulk before additional actions for the device can take place.
8. (Optional) Specify the period during which the device must respond to an attempt to provision or deprovision a service. The timeout is a failure equivalent to an explicit failure response received from the device.
9. (Optional) Specify how many consecutive response timeouts can occur before the BNG takes action. The default action is to close and reopen the NETCONF connection.

Table 1 lists commands you can use to view information about your RDSM configuration and operation.

Table 1: show Commands for Remote Device Services Management
Command	Description
show remote-device-management service-devices	Display information about all remote service devices or a specific remote service device.
show remote-device-management services	Display information about all service sessions or a specific service session on remote service devices.
show remote-device-management statistics	Display a global summary of service statistics for all remote devices or detailed statistics for a specific remote service device.
show remote-device-management subscribers	Display information about service sessions for all subscriber sessions or about all service sessions for a specific subscriber session on remote service devices.
show remote-device-management summary	Display summary information about the remote service devices, such as session state and service state.

You can use the clear remote-device-management statistics command to clear service statistics for all remote devices globally or statistics for a specific remote service device.

Configuring Remote Device Management for Service Provisioning

Related Documentation