Configuring a RADIUS Packet Template (SRC CLI)

You can define RADIUS packets for flexible RADIUS accounting and authentication plug-ins in two ways.

• Define attributes in a template, and then apply the template to flexible RADIUS accounting and authentication plug-ins.
• Define attributes in the packet definition configuration of a flexible plug-in instance. These definitions override definitions in packet templates.

Use the following configuration statements to configure a RADIUS packet template:

To configure a template:

1. From configuration mode, access the RADIUS packet template configuration. In this sample procedure, the stdAcct template is configured in the west-region service activation engine (SAE) group.
   user@host# edit shared sae group west-region configuration radius-packet-template stdAcct
2. Create an attribute instance using the names in Flexible RADIUS Plug-Ins Overview, and enter the configuration for the RADIUS attribute instance.
   [edit shared sae group west-region configuration radius-packet-template stdAcct] user@host# edit radius-attributes name
3. Add RADIUS attribute definitions to the attribute instance. Repeat this step for each attribute.
   [edit shared sae group west-region configuration radius-packet-template stdAcct radius-attributes svcstop]user@host# set attributes name value

   For example:

   [edit shared sae group west-region configuration radius-packet-template stdAcct radius-attributes svcstop]user@host# set attributes Acct-Session-ID sessionId
4. (Optional) Verify the configuration of your attribute instance.

   [edit shared sae group west-region configuration radius-packet-template stdAcct radius-attributes svcstop]
   user@host# show 
   attributes {
    Acct-Input-Octets lowWord(inOctets);
     Acct-Output-Octets lowWord(outOctets);
     Acct-Input-Packets lowWord(inPackets);
     Acct-Output-Packets lowWord(outPackets);
     Acct-Input-Gigawords highWord(inOctets);
     Acct-Output-Gigawords highWord(outOctets);
   }

5. (Optional) Verify the configuration of the RADIUS packet template.

   [edit shared sae group west-region configuration radius-packet-template stdAcct radius-attributes svcstop]
   user@host# up 
   [edit shared sae group west-region configuration radius-packet-template stdAcct]
   user@host# show 
   radius-attributes svcstop {
     attributes {
       Acct-Input-Octets lowWord(inOctets);
       Acct-Output-Octets lowWord(outOctets);
       Acct-Input-Packets lowWord(inPackets);
       Acct-Output-Packets lowWord(outPackets);
       Acct-Input-Gigawords highWord(inOctets);
       Acct-Output-Gigawords highWord(outOctets);
     }
   }
   radius-attributes stop {
     attributes {
       Acct-Session-Time sessionTime;
       Acct-Terminate-Cause terminateCause;
     }
   }
   radius-attributes svcacct {
     attributes {
       Chargeable-User-Identity userSessionProperties.CUI;
       Class radiusClass;
     }
   }
   radius-attributes acct {
     attributes {
       Acct-Session-Id sessionId;
       NAS-Identifier localNasId;
       NAS-IP-Address localNasIp;
       Event-Time eventTime;
     }
   }
   radius-attributes startstop {
     attributes {
       Acct-Multi-Session-Id ifSessionId;
       NAS-Port-Id "\"%s %s\" %(routerName, portId or interfaceName)";
       NAS-Port "nasPort or None";
     }
   }

   Note: You must configure any one of the following values to set the Chargeable-User-Identity attribute value in the accounting-request packet. userSessionProperties.CUI getUserSessionProperties().CUI getUserSessionProperties().get(“CUI”) getUserSessionProperties()[CUI] userSessionProperties().CUI