Calling-Station-Id (31)

31

Calling-Station-Id

String

RFC 2865

All

1–253

The attribute is used by the NAS to carry user information.

For management users, Layer 2 leased line users, Layer 3 leased line users, and network-side PPP users, the attribute is not encapsulated.

For an LAC, if the function to parse the logical line ID (LLID) information is enabled using the radius-server calling-station-id include llid user-type { ppp | lns }* command, the Calling-Station-Id attribute is obtained from the RADIUS server and encapsulated into the calling-number attribute to be sent to the LNS.

For L2TP LNS-side users, the value configured"calling-number-avp" command configured in the LAC-side L2TP group is used.

For non-L2TP LNS-side users, the attribute carries users' MAC addresses by default, in the format of 00:e0:fc:12:34:56.

To configure the generation mode of Calling-Station-Id, run the "radius-server calling-station-id include [ delimiter delimiter ] { { option82 | access-line-id } [ delimiter delimiter ] | mac [ mac-format type1 ] [ delimiter delimiter ] | interface [ delimiter delimiter ] | domain [ delimiter delimiter ] | sysname [ delimiter delimiter ] } *" or "radius-server calling-station-id include refer-option61" command.

In the format of initial delimiter + configuration item + delimiter + configuration item + delimiter, the value of a delimiter can be any of the following characters: n, b, @, #, \, &, *, -, and $, where 'n' represents null and 'b' represents a blank space.

The sysname value is obtained in ascending order of the following priorities:

nas-name configured on the RBP

nas-name configured on the interface

sysname configured for the system

The format of the interface information can be any of the following:

Three-dimensional format:

eth slot/picnum/portnum:pevlan.cevlan

trunk slot/2/Trunkid:pevlan.cevlan

atm slot/picnum/portnum:pevlan.cevlan

The MAC address format is xx:xx:xx:xx:xx:xx and can be changed to xx-xx-xx-xx-xx-xx by setting type1 in the preceding command.

When Calling-Station-Id is converted to HW-Own-Calling-Station-Id-Old using the attribute conversion command, the format is as follows:

The format of the attribute encapsulated in RADIUS packets is 00e0fc123455.

For 802.1X relay users, the attribute format is 00-e0-fc-12-34-54.

If the "radius-server calling-station-id include option82" command has been run, the Calling-Station-Id field value varies with the "option82-relay-mode" command configuration in the BAS interface view. Specifically, the Calling-Station-Id field will contain:

All Option 82 information if the "option82-relay-mode include allvalue" command is configured.

Only the circuit ID if the "option82-relay-mode include agent-circuit-id" command is configured.

Only the remote ID if the "option82-relay-mode include agent-remote-id" command is configured.

Both the circuit ID and remote ID if the "option82-relay-mode include agent-circuit-id agent-remote-id" command is configured.

After the "option82-relay-mode" command is run with any of the preceding four parameters configured, the "option82-relay-mode subopt" command can be run to configure a format (either a character string or hexadecimal notation) for the circuit ID or remote ID to be transmitted.

The value of the Calling-Station-Id attribute to be sent to the RADIUS server depends on whether the Option 61 field is carried in packets sent by access users. The "radius-server calling-station-id include refer-option61" command can be run in the RADIUS server group view to configure a device to encapsulate the user MAC address in the Calling-Station-Id attribute to be sent to the RADIUS server if user packets carry the Option 61 field. If this command is not run, the device encapsulates the user name without a domain name in the Calling-Station-Id attribute to be sent to the RADIUS server.

You can also configure a RedBack-compatible format for the Calling-Station-Id attribute.

To do so, run the "radius-server format-attribute calling-station-id vendor 2352" command in the RADIUS server group view.

Three-dimensional format:

For PPPoE and IPoE users: systemname#slot/port#PVlan:CVlan

NOTE:

The "radius-server format-attribute include sub-slot" command can be run to convert Slot/Port to Slot/Sub-Slot/Port.

If the "radius-server calling-station-id include vlan-description" command has been run, the format of the Calling-Station-Id attribute to be sent to the RADIUS server varies as follows:

When the three-dimensional interface format is used, the Calling-Station-Id attribute format is sysname#slot/subslot/port#Pevlan.CeVlan#vlan-description.

In this format:

The sysname has a maximum of 30 characters allowed. If the sysname is longer than 30 characters, only the first 30 characters are used.

Using the logical device name and logical interface name configured on the BAS interface as the sysname and slot/subslot/port is recommended.

If packets carry only one vla+K28n tag, the PeVlan, instead of the CeVlan, is displayed in the format.

The vlan-description is the description of the VLAN configured for the access interface. It has a maximum of 128 characters allowed.

NOTE:

For the device name and port and IP information, use their logical values configured on the BAS interfaces if they are present. If their logical values are not configured, use their actual values.

If encapsulation using the specified format fails, the device encapsulates only the user MAC address to the Calling-Station-Id attribute.

For LNS users, the calling-number attribute carried in L2TP packets sent from the LAC is preferentially encapsulated into the Calling-Station-Id attribute. If no calling-number attribute is carried in L2TP packets sent from the LAC, the LNS does not carry the Calling-Station-Id attribute in packets to be sent to the RADIUS server by default. If the radius-server calling-station-id lns-default version1 command is run in the RADIUS server group view, the Calling-Station-Id attribute carried in packets sent by the LNS is in the following format: sysname#slot/subslot/port#0#0.

The preceding formats are all Huawei-defined Calling-Station-Id formats. Besides these formats, you can configure the Calling-Station-Id to be sent according to the format defined by RedBack or Juniper. If the format defined by RedBack or Juniper is used for the Calling-Station-Id attribute, the preceding Huawei command configurations for Calling-Station-Id do not take effect.

1. To configure the RedBack-defined format, run the "radius-server format-attribute calling-station-id vendor 2352" command in the RADIUS server group view. The format is as follows:

Three-dimensional format:

PPPoE and IPoE users: systemname#slot/port#PVlan:CVlan

2. To configure the Juniper-defined format, run the "radius-server format-attribute calling-station-id vendor 2636" command in the RADIUS server group view. The format is as follows:

Format: "#sysname#DSLAM name: #vlan"

The DSLAM name is obtained from the agent-circuit-id attribute of the Option 82. The vlan field uses only one VLAN tag. If two VLAN tags are configured, only the outer VLAN tag is used.

3. version3 format: Run the radius-server format-attribute calling-station-id user-defined version3 command in the RADIUS server group. The format is as follows:

Notes:

1. Slot specifies a lost ID, Subslot specifies a sub-slot ID, and Port specifies a port number.

2. svlan specifies an outer VLAN ID, and cvlan specifies an inner VLAN ID. If no VLAN exists, the value is 0.

3. mac-address specifies a physical address, which can be separated by the semicolon (:).

4. Other fields use the fixed format.

Trunk scenario: lag-trunkid:svlan.cvlan#sysname###pppoe mac-address#

For example:

1. Double-tagged VLAN: lag-70:100.200#BNG Ouardia###pppoe 00:24:17:bd:8f:d0#

2. Single-tagged VLAN: lag-70:100.0#BNG Ouardia###pppoe 00:24:17:bd:8f:d0#

3. No VLAN: lag-70:0.0#BNG Ouardia###pppoe 00:24:17:bd:8f:d0#

Non-trunk scenario: eth slot/subslot/port:svlan.cvlan#sysname###pppoe mac-address#

For example:

1. Double-tagged VLAN: eth 70:100.200#BNG Ouardia###pppoe 00:24:17:bd:8f:d0#

2. Single-tagged VLAN: eth 70:100.0#BNG Ouardia###pppoe 00:24:17:bd:8f:d0#

3: No VLAN: eth 70:0.0#BNG Ouardia###pppoe 00:24:17:bd:8f:d0#