Element: controlledDeviceModel

The controlledDeviceModel element defines the device model for a controlled device object. It is used only if a device is configured that has a vendor-product matching the id attribute of this element.

The dictionary attribute must be set to the name of one of the dictionaries in the radius directory. Use the vendor and model attributes only for logging, and set them to descriptive values.

To use VSAs for a controlled device model, you must explicitly define the VSAs in the corresponding .dic file. For example, if you want to use the Juniper VSA “Unisphere-Egress-Policy-Name”, which is defined in the juniper.dct file as follows:

Then, you must define the Unisphere-Egress-Policy-Name VSA in the enterprise_juniper_4874.dic file as follows:

You must reboot the SBR Carrier server for the changes to take effect.

As shown in the schema, the controlledDeviceModel is defined in terms of a set of RADIUS ports, and a set of actions. For more information, see Element: radiusPort, and Element: actions.

XML Instance Representation

Schema Component Representation

Note

You must use a cURL command if you are sending multiple values for a VSA attribute in a single CoA message. For example, in the following XML file named “example.xml”, if you want to send the Jnpr-Cos-Scheduler-Pmt-Type attribute that is defined with two different values, you can use the cURL command “curl -s -u root:password -H \"Content-Type:text/xml\" -d @example.xml -X POST https://10.212.10.120:1814/scs/request/ -k”.