Log in
|
How to Buy
|
Contact Us
|
United States (Change)

## Choose Country

### North America

- United States

### Europe

- Deutschland - Germany
- España - Spain
- France
- Italia - Italy
- Россия - Russia
- United Kingdom

### Asia Pacific

- Asean Region (Vietnam, Indonesia, Singapore, Malaysia)
- Australia
- 中国 - China
- India
- 日本 - Japan
- 대한민국 - Korea
- 台灣 - Taiwan

Remember my choice

# Technical Documentation

Download Software
Research a Problem
Case Management
Contract & Product Management
Technical Documentation
Documentation Archive
Enterprise MIBs
File Format Help
Glossary
Portable Libraries
End-of-Life Products
Contact Support
Guidelines and Policies
Security Resources
Rate and give feedback: Feedback Received. Thank You!
Rate and give feedback:
This document helped resolve my issue. Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:
E-mail:

# radius calling-station-format

#### Syntax

radius calling-station-format { delimited | fixed-format [ stacked ] | fixed-format-adapter-embedded [ stacked ] | fixed-format-adapter-new-field [ stacked ] }

no radius calling-station-format

#### Release Information

Command introduced before JunosE Release 7.1.0.
fixed-format-adapter-embedded and fixed-format-adapter-new-field keywords added in JunosE Release 8.1.0.

stacked keyword added in JunosE Release 9.3.0.

#### Description

On a virtual router, specifies the format of RADIUS attribute 31, Calling-Station-Id, when the PPP user is terminated at the non-LNS E Series router. Depending on the keyword you use, the virtual router uses the specified format for each interface type, replacing variables in the format with their actual values for your configuration. The no version restores the default Calling-Station-Id format, delimited.

| Attribute 31, Calling-Station-Id, is used with Attribute 30, Called-Station-Id, in a standard way when the router is the LNS and the LAC is a dial-up LAC (not an E Series router). When the LNS receives the Calling-Station-Id and Called-Station-Id AVPs, the router includes the values as they are, with no format changes in the RADIUS messages. For subscribers connected over the LAG interface in DHCP standalone authenticate mode, the radius override calling-station-id remote-circuit-id command enables RADIUS to use the PPPoE remote circuit ID for the Calling-Station-Id attribute. By default, RADIUS uses a delimited format for the interface description. You cannot use this command to change the value of the Calling-Station-Id attribute.

#### Options

- delimited—Specifies that the RADIUS client uses the delimited format:
  - Format for ATM interfaces:
    delimiter systemName delimiter interfaceDescription delimiter
    VPI delimiter VCI delimiter
  - Format for Ethernet interfaces:
    delimiter systemName delimiter interfaceDescription delimiter VLAN

  Where interfaceDescription is one of the following items:

  - port name—The default setting
  - VP description—Appears if you use the atm vp-description command to assign a text description to an individual VP on an ATM interface
  - VC description—Appears if you use the atm atm1483 description command to assign a text description to VCs on an ATM 1483 subinterface and you use the atm1483 export-subinterface-description command to enable sending of VC interface descriptors to AAA
- fixed-format—Specifies that the RADIUS client uses a fixed format of up to 15 characters consisting of all ASCII fields:
  - Format for ATM interfaces:
    systemName (up to 4 bytes) slot (2 bytes) port (1 byte) VPI (3 bytes)
    VCI (5 bytes)
  - Format for Ethernet interfaces:
    systemName (up to 4 bytes) slot (2 bytes) port (1 byte) VLAN (8 bytes)
  - Format for serial interfaces:
    systemName (up to 4 bytes) slot (2 bytes) port (1 byte) 0 (8 bytes)
  - In the case of PPP terminated from LNS, the Calling-Station-Id attribute value is based on the received L2TP calling number AVP
- fixed-format-adapter-embedded—Specifies that the RADIUS client uses a fixed format of up to 15 characters consisting of all ASCII fields with a 1-byte slot field, 1-byte adapter field, and 1-byte port field:
  - Format for ATM interfaces:
    systemName (up to 4 bytes) slot (1 byte) adapter (1 byte) port (1 byte)
    VPI (3 bytes) VCI (5 bytes)
  - Format for Ethernet interfaces:
    systemName (up to 4 bytes) slot (1 byte) adapter (1 byte) port (1 byte)
    VLAN (8 bytes)
  - Format for serial interfaces:
    systemName (up to 4 bytes) slot (1 byte) adapter (1 byte) port (1 byte)
    0 (8 bytes)
  - For E120 routers and E320 routers, adapter is the number of the bay in which the I/O adapter (IOA) resides, either 0 (representing the right IOA bay on the E120 router and the upper IOA bay on the E320 router) or 1 (representing the left IOA bay on the E120 router or the lower IOA bay on the E320 router). For ERX7xx models, ERX14xx models, and ERX310 routers, adapter is always shown as 0.
  - Slot numbers 0 through 16 are shown as ASCII characters in the 1-byte slot field according to the following translation:

    Slot Number | ASCII Character | Slot Number | ASCII Character
    --- | --- | --- | ---
    0 | 0 | 9 | 9
    1 | 1 | 10 | A
    2 | 2 | 11 | B
    3 | 3 | 12 | C
    4 | 4 | 13 | D
    5 | 5 | 14 | E
    6 | 6 | 15 | F
    7 | 7 | 16 | G
    8 | 8 | – | –

    For example, slot 16 is shown as the ASCII character uppercase G.

- fixed-format-adapter-new-field—Specifies that the RADIUS client uses a fixed format of up to 17 characters consisting of all ASCII fields with a 2-byte slot field, 1-byte adapter field, and 2-byte port field:
  - Format for ATM interfaces:
    systemName (up to 4 bytes) slot (2 bytes) adapter (1 byte) port (2 bytes)
    VPI (3 bytes) VCI (5 bytes)
  - Format for Ethernet interfaces:
    systemName (up to 4 bytes) slot (2 bytes) adapter (1 byte) port (2 bytes) VLAN (8 bytes)
  - Format for serial interfaces:
    systemName (up to 4 bytes) slot (2 bytes) adapter (1 byte) port (2 bytes)
    0 (8 bytes)
  - For E120 routers and E320 routers, adapter is the number of the bay in which the IOA resides, either 0 or 1. For ERX7xx models, ERX14xx models, and ERX310 routers, adapter is always shown as 0.
  - Slot numbers 0 through 16 are shown as integers in the 2-byte slot field.

  | Note: You must use this field when you configure the format of the Calling-Station-ID attribute on routers that have line modules that support more than seven physical ports.

- stacked—Includes a 4-byte stacked VLAN (S-VLAN ID) for Ethernet interfaces when the RADIUS client uses the fixed-format, fixed-format-adapter-embedded, or fixed-format-adapter-new-field format; by default, these formats do not include the S-VLAN ID unless you specify the optional stacked keyword; If you include the stacked keyword, the S-VLAN ID is displayed in decimal format in the range 0–4095
  - Format for Ethernet interfaces that use fixed-format:
    systemName (up to 4 bytes) slot (2 bytes) port (1 byte) S-VLAN (4 bytes) VLAN (4 bytes)
  - Format for Ethernet interfaces that use fixed-format-adapter-embedded:
    systemName (up to 4 bytes) slot (1 byte) adapter (1 byte) port (1 byte) S-VLAN (4 bytes) VLAN (4 bytes)
  - Format for Ethernet interfaces that use fixed-format-adapter-new-field:
    systemName (up to 4 bytes) slot (2 bytes) adapter (1 byte) port (2 bytes) S-VLAN (4 bytes) VLAN (4 bytes)

  | The use of the stacked keyword is not supported for VLAN subinterfaces based on agent-circuit-identifier information, otherwise known as ACI VLANs. When you issue the radius calling-station-format fixed-format stacked, radius calling-station-format fixed-format-adapter-embedded stacked, or radius calling-station-format fixed-format-adapter-new-field stacked command for an ACI VLAN, the values that appear in the 4-byte S-VLAN ID and 4-byte VLAN ID fields are incorrect. The S-VLAN ID field in the Calling-Station-Id [31] attribute is set to 0 (zero) under the following conditions: You do not specify the optional stacked keyword. You specify the optional stacked keyword but the Ethernet interface does not have an S-VLAN ID.

#### Mode

Global Configuration

#### Published: 2011-10-04

Site Map / RSS Feeds / Careers / Accessibility / Feedback / Privacy & Policy / Legal Notices
Copyright© 1999-2011 Juniper Networks, Inc. All rights reserved.
Help
|
My Account
|
Log Out