Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
[+] Expand All
[-] Collapse All

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:

ATTRIBUTE Unisphere-Egress-Policy-Name             ERX-VSA(11, string)    c

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

<attribute id="Unisphere-Egress-Policy-Name" type="11" format="string" vendor ="JUNIPER_4874"/> 

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

dictionary=" xs:NCName [0..1]"
id="anySimpleType [1]"
model="anySimpleType [1]"
vendor="anySimpleType [1]"> 
    <radiusPorts> ... </radiusPorts> [1] 
    <actions> ... </actions> [1]

Schema Component Representation

<xs:element name="controlledDeviceModel"> 
            <xs:element ref=" radiusPorts "/> 
            <xs:element ref=" actions "/>
        <xs:attribute name="dictionary" type=" xs:NCName "/> 
        <xs:attribute name="id" use="required"/> 
        <xs:attribute name="model" use="required"/> 
        <xs:attribute name="vendor" use="required"/>

Modified: 2017-09-27