Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

classmap.ini File

 

The classmap.ini initialization file specifies what Steel-Belted Radius Carrier does with RADIUS attributes encoded in one or more Class attributes included in accounting requests it receives.

[AttributeName] Section

[AttributeName] Section

The [AttributeName] section (Table 66) of classmap.ini specifies whether RADIUS information encapsulated in a Class attribute is appended to an accounting request or replaces a current value in an accounting request. If one attribute is replaced by another, the original attribute can be added to the request with a different identifier.

Table 66: classmap.ini [AttributeName] Syntax

Parameter

Function

 AttributeName

Name of the attribute encoded into the Class attribute by the authenticating server.

<add | replace>

Specifies whether the attribute value is added to the accounting request (leaving all other values intact) or whether one value replaces another in the accounting request.

Attribute

Specifies the name of the attribute that is added to the accounting request that contains the original value of the attribute identified by AttributeName.

[,Attribute]

Specifies the name of the attribute in the accounting request that contains the value of the attribute displaced when the value of AttributeName replaces the existing Attribute value.

Valid only when the replace keyword is used.

Note

The RADIUS Class attribute cannot contain IPv6 attributes and structured attributes.

In the following example, the encapsulated User-Name attribute replaces the existing User-Name in the accounting request.

In the following example, the encapsulated User-Name attribute is placed in the accounting request as User-Name, and the original value for User-Name is added to the request as Funk-Full-User-Name.

In the following example, the encapsulated User-Name attribute is added to the accounting request as a new attribute, and the original User-Name attribute remains unchanged.

Upon receipt of a subsequent accounting request, SBR Carrier decapsulates and forwards the upstream server’s Class attribute. This action can result in two Class attributes being present in the proxied accounting request. In the following example, the encapsulated Class attribute replaces the existing Class attribute in the accounting request to prevent the Class attribute for SBR Carrier from being forwarded.