[Contents] [Prev] [Next] [Index] [Report an Error]

# Configuring Calling Number AVP Formats

The E-series LAC generates L2TP Calling Number AVP 22 for incoming-call request (ICRQ) packets that the LAC sends to the LNS. By default, the E-series LAC generates the Calling Number AVP 22 in descriptive format.

You can also prevent the E-series LAC from sending the Calling Number AVP in ICRQ packets.

| Note: You cannot change the L2TP Calling Number AVP on tunnel switched interfaces.

You use the aaa tunnel calling-number-format command to configure the router to generate AVP 22 in any of the following formats. Agent-circuit-id is suboption 1 of the tags supplied by the PPPoE intermediate agent from the DSLAM. Agent-remote-id is suboption 2.

- descriptive—This is the default format, and includes the following elements:

  <interface ID> <delimit> <UID> <delimit> <interface description> <delimit> <connect info> <delimit> <PPPoE description>

- descriptive include-agent-circuit-id—This format includes the following elements:

  <interface ID> <delimit> <UID> <delimit> <interface description> <delimit> <connect info> <delimit> <PPPoE description> <delimit> <agent-circuit-id>

- descriptive include-agent-circuit-id include-agent-remote-id—This format includes the following elements:

  <interface ID> <delimit> <UID> <delimit> <interface description> <delimit> <connect info> <delimit> <PPPoE description> <delimit> <agent-circuit-id> <delimit> <agent-remote-id>

- descriptive include-agent-remote-id—This format includes the following elements:

  <interface ID> <delimit> <UID> <delimit> <interface description> <delimit> <connect info> <delimit> <PPPoE description> <delimit> <agent-remote-id>

- fixed—This format is similar to the fixed format of RADIUS attribute 31 (Calling-Station-Id). If you set up the router to generate the Calling Number AVP in fixed format, the router formats the AVP to use a fixed format of up to 15 characters consisting of all ASCII fields, as follows (the maximum number of characters for each field is shown in brackets):
  - For ATM interfaces:
    <system name [4]> <slot [2]> <port [1]> <VPI [3]> <VCI [5]>
  - For Ethernet interfaces:
    <system name [4]> <slot [2]> <port [1]> <VLAN [8]>
  - Format for serial interfaces:
    <system name [4]> <slot [2]> <port [1]> <0 [8]>
  - Example—The following command configures the L2TP Calling Number AVP in fixed format:
    `
    host1(config)#aaa tunnel calling-number-format fixed
    `

    For example, when you configure this L2TP Calling Number AVP format on an E320 router for an ATM interface on system name eastern, slot 14, adapter 1, port 2, VCI 3, and VPI 4, the virtual router displays the format in ASCII as ‘14’ ‘2’ ‘003’ ‘00004’. The adapter number does not appear in this format.

- fixed-adapter-embedded—If you set up the router to generate the L2TP Calling Number AVP in fixed–adapter-embedded format, the router formats the AVP to use 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 ERX-7xx models, ERX-14xx models, and ERX-310 routers, which do not use IOAs, 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.

  - Example—The following command configures the L2TP Calling Number AVP in fixed-adapter-embedded format:
    `
    host1(config)#aaa tunnel calling-number-format fixed-adapter-embedded
    `

    For example, when you configure this L2TP Calling Number AVP format on an E320 router for an ATM interface on system name eastern, slot 14, adapter 1, port 2, VCI 3, and VPI 4, the virtual router displays the format in ASCII as ‘E’ ‘1’ ‘2’ ‘003’ ‘00004’.

- fixed-adapter-new-field—If you set up the router to generate the L2TP Calling Number AVP in fixed–adapter-embedded-new-field format, the router formats the AVP to use 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)
  - Slot numbers 0 through 16 are shown as integers in the 2-byte slot field.
  - Example—The following command configures the L2TP Calling Number AVP in fixed-adapter-new-field format:
    `
    host1(config)#aaa tunnel calling-number-format fixed-adapter-new-field
    `

    For example, when you configure this L2TP Calling Number AVP format on an E320 router for an ATM interface on system name eastern, slot 14, adapter 1, port 2, VCI 3, and VPI 4, the virtual router displays the format in ASCII as ‘14’ ‘1’ ‘02’ ‘003’ ‘00004’.

- include-agent-circuit-id format—This format includes the following element:

  <agent-circuit-id>

- include-agent-circuit-id include-agent-remote-id format—This format includes the following elements:

  <agent-circuit-id> <delimit> <agent-remote-id>

- include-agent-remote-id format—This format includes the following element:

  <agent-remote-id>

- stacked—This format includes a 4-byte stacked VLAN (S-VLAN) ID in the fixed, fixed-adapter-embedded, and fixed-adapter-new-field Calling Number AVP formats for Ethernet interfaces. The S-VLAN ID is displayed in decimal format in the range 0–4095. By default, these formats do not include the S-VLAN ID unless you specify the optional stacked keyword.

  | Note: 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 aaa tunnel calling-number-format fixed stacked, aaa tunnel calling-number-format fixed-adapter-embedded stacked, or aaa tunnel calling-number-format fixed-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.

  - Format for Ethernet interfaces that use fixed:
    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-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-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 S-VLAN ID field in the Calling Number AVP is set to 0 (zero) if you do not specify the optional stacked keyword, or if you specify the optional stacked keyword but the Ethernet interface does not have an S-VLAN ID.
  - Example—The following command configures the L2TP Calling Number AVP in fixed-adapter-new-field format for an Ethernet interface with an S-VLAN ID:
    `
    host1(config)#aaa tunnel calling-number-format fixed-adapter-new-field stacked
    `

    For example, when you configure this Calling-Station-Id format on an E320 router for an Ethernet interface on system name western, slot 4, adapter 1, port 3, S-VLAN ID 8, and VLAN ID 12, the virtual router displays the format in ASCII as ‘west’ ‘04’ ‘1’ ‘03’ ‘0008’ ‘0012’.

Tasks for configuring the L2TP Calling Number AVP 22 include:

- Calling Number AVP 22 Configuration Tasks
- Configuring the Fallback Format
- Disabling the Calling Number AVP

## Calling Number AVP 22 Configuration Tasks

To set up the router to generate Calling Number AVP 22 for an Ethernet interface in fixed format that includes both an S-VLAN ID and a VLAN ID:

1. Set the calling number format of the tunnel to fixed, and specify the optional stacked keyword to include the S-VLAN ID.
   `
   host1(config)#aaa tunnel calling-number-format fixed stacked
   `
2. Set the format of the RADIUS Calling-Station-Id to fixed-format, and specify the optional stacked keyword to include the S-VLAN ID.
   `
   host1(config)#radius calling-station-format fixed-format stacked
   `

If you use a RADIUS server to authenticate the L2TP tunnel parameters, you must configure the format for both the L2TP Calling Number AVP 22 (by using the aaa tunnel calling-number-format command) and the RADIUS Calling-Station-ID [31] attribute (by using the radius calling-station-format command).

However, if you use an AAA domain map to authenticate the L2TP tunnel parameters, you need configure only the L2TP Calling Number AVP 22 format by using the aaa tunnel calling-number-format command. You need not configure the format of the RADIUS Calling-Station-ID [31] attribute in this case.

## Configuring the Fallback Format

You can configure a fallback AVP 22 format. The E-series LAC uses the fallback format to generate the L2TP Calling Number AVP 22 in the event that the PPPoE agent ID is null or unavailable. The LAC uses the fallback format only when the configured calling number format includes either or both of the agent-circuit-id and agent-remote-id suboptions.

The calling number format determines what element triggers use of the fallback format, as shown in the following table:

Calling Number Format | Fallback Trigger
--- | ---
agent-circuit-id | agent-circuit-id is empty
agent-circuit-id include-agent-remote-id | Both agent-circuit-id and agent-remote-id are empty.
agent-remote-id | agent-remote-id is empty
descriptive include-agent-circuit-id | agent-circuit-id is empty
descriptive include-agent-circuit-id include-agent-remote-id | Both agent-circuit-id and agent-remote-id are empty.
descriptive include-agent-remote-id | agent-remote-id is empty

You use the aaa tunnel calling-number-format-fallback command to configure the router to generate any of the following fallback AVP 22 formats:

- descriptive—This is the default fallback AVP 22 format, and includes the following elements:

  <interface ID> <delimit> <UID> <delimit> <interface description> <delimit> <connect info> <delimit> <PPPoE description>

- fixed—This format is similar to the fixed format of RADIUS attribute 31 (Calling-Station-Id). If you set up the router to generate the fallback AVP 22 in fixed format, the router formats the AVP to use a fixed format of up to 15 characters consisting of all ASCII fields, as follows (the maximum number of characters for each field is shown in brackets):
  - Fallback format for ATM interfaces:
    <system name [4]> <slot [2]> <port [1]> <VPI [3]> <VCI [5]>
  - Fallback format for Ethernet interfaces:
    <system name [4]> <slot [2]> <port [1]> <VLAN [8]>
  - Fallback format for serial interfaces:
    <system name [4]> <slot [2]> <port [1]> <0 [8]>
  - Example—The following command configures the fallback AVP 22 in fixed format:
    `
    host1(config)#aaa tunnel calling-number-format-fallback fixed
    `

    For example, when you configure this fallback format on an E320 router for an ATM interface on system name eastern, slot 14, adapter 1, port 2, VCI 3, and VPI 4, the virtual router displays the format in ASCII as ‘14’ ‘2’ ‘003’ ‘00004’. The adapter number does not appear in this format.

- fixed-adapter-embedded—If you set up the router to generate the fallback AVP 22 in fixed–adapter-embedded format, the router formats the AVP to use 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:
  - Fallback format for ATM interfaces:
    systemName (up to 4 bytes) slot (1 byte) adapter (1 byte)
    port (1 byte) VPI (3 bytes) VCI (5 bytes)
  - Fallback format for Ethernet interfaces:
    systemName (up to 4 bytes) slot (1 byte) adapter (1 byte)
    port (1 byte) VLAN (8 bytes)
  - Fallback 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 ERX-7xx models, ERX-14xx models, and ERX-310 routers, which do not use IOAs, 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.

  - Example—The following command configures the fallback AVP 22 in fixed-adapter-embedded format:
    `
    host1(config)#aaa tunnel calling-number-format-fallback fixed-adapter-embedded
    `

    For example, when you configure this fallback format on an E320 router for an ATM interface on system name eastern, slot 14, adapter 1, port 2, VCI 3, and VPI 4, the virtual router displays the format in ASCII as ‘E’ ‘1’ ‘2’ ‘003’ ‘00004’.

- fixed-adapter-new-field—If you set up the router to generate the fallback AVP 22 in fixed–adapter-embedded-new-field format, the router formats the AVP to use 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:
  - Fallback format for ATM interfaces:
    systemName (up to 4 bytes) slot (2 bytes) adapter (1 byte)
    port (2 bytes) VPI (3 bytes) VCI (5 bytes)
  - Fallback format for Ethernet interfaces:
    systemName (up to 4 bytes) slot (2 bytes) adapter (1 byte)
    port (2 bytes) VLAN (8 bytes)
  - Fallback format for serial interfaces:
    systemName (up to 4 bytes) slot (2 bytes) adapter (1 byte)
    port (2 bytes) 0 (8 bytes)
  - Slot numbers 0 through 16 are shown as integers in the 2-byte slot field.
  - Example—The following command configures the fallback AVP 22 in fixed-adapter-new-field format:
    `
    host1(config)#aaa tunnel calling-number-format-fallback fixed-adapter-new-field
    `

    For example, when you configure this fallback format on an E320 router for an ATM interface on system name eastern, slot 14, adapter 1, port 2, VCI 3, and VPI 4, the virtual router displays the format in ASCII as ‘14’ ‘1’ ‘02’ ‘003’ ‘00004’.

- stacked—This format includes a 4-byte stacked VLAN (S-VLAN) ID in the fixed, fixed-adapter-embedded, and fixed-adapter-new-field fallback AVP 22 formats for Ethernet interfaces. The S-VLAN ID is displayed in decimal format in the range 0–4095. By default, these formats do not include the S-VLAN ID unless you specify the optional stacked keyword.

  | Note: 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 aaa tunnel calling-number-format-fallback fixed stacked, aaa tunnel calling-number-format-fallback fixed-adapter-embedded stacked, or aaa tunnel calling-number-format-fallback fixed-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.

  - Fallback format for Ethernet interfaces that use fixed:
    systemName (up to 4 bytes) slot (2 bytes) port (1 byte) S-VLAN (4 bytes) VLAN (4 bytes)
  - Fallback format for Ethernet interfaces that use fixed-adapter-embedded:
    systemName (up to 4 bytes) slot (1 byte) adapter (1 byte) port (1 byte) S-VLAN (4 bytes) VLAN (4 bytes)
  - Fallback format for Ethernet interfaces that use fixed-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 S-VLAN ID field in the fallback AVP 22 is set to 0 (zero) if you do not specify the optional stacked keyword, or if you specify the optional stacked keyword but the Ethernet interface does not have an S-VLAN ID.
  - Example—The following command configures the fallback AVP 22 in fixed-adapter-new-field format for an Ethernet interface with an S-VLAN ID:
    `
    host1(config)#aaa tunnel calling-number-format-fallback fixed-adapter-new-field stacked
    `

    For example, when you configure this fallback format on an E320 router for an Ethernet interface on system name western, slot 4, adapter 1, port 3, S-VLAN ID 8, and VLAN ID 12, the virtual router displays the format in ASCII as ‘west’ ‘04’ ‘1’ ‘03’ ‘0008’ ‘0012’.

## Disabling the Calling Number AVP

You can use the l2tp disable calling-number-avp command to prevent the E-series LAC from sending the Calling Number AVP in ICRQ packets. You use this command in special situations where you do not want the LAC to send this AVP.

- To prevent the LAC from sending the Calling Number AVP:
  `
  host1(config)#l2tp disable calling-number-avp
  `

For more information about setting up the router to generate Calling Number AVP 22 in a format that includes either or both of the agent-circuit-id and agent-remote-id suboptions of the tags supplied by the PPPoE intermediate agent, see Configuring PPPoE Remote Circuit ID Capture in the JUNOSe Link Layer Configuration Guide .

Calling Number AVP 22 Configuration Examples

The following examples show how you can synchronize the contents of RADIUS Calling-Station-Id (Attribute 31) and L2TP Calling-Number (AVP 22).

To send the PPPoE agent-circuit-id in RADIUS Attribute 31 and L2TP AVP 22 and specify that the fixed format is used when the PPPoE agent-circuit-id is unavailable, issue the following commands:

`

host1(config)#radius calling-station-format fixed-format
host1(config)#radius remote-circuit-id-delimiter #
host1(config)#radius override calling-station-id remote-circuit-id
host1(config)#radius remote-circuit-id-format agent-circuit-id
host1(config)#aaa tunnel calling-number-format include-agent-circuit-id
host1(config)#aaa tunnel calling-number-format-fallback fixed

`

To send the PPPoE agent-circuit-id and agent-remote-id in RADIUS Attribute 31 and L2TP AVP 22 and specify that the fixed format is used when both PPPoE agent-circuit-id and agent-remote-id are unavailable, issue the following commands:

`

host1(config)#radius calling-station-format fixed-format
host1(config)#radius remote-circuit-id-delimiter #
host1(config)#radius override calling-station-id remote-circuit-id
host1(config)#radius remote-circuit-id-format agent-circuit-id agent-remote-id
host1(config)#aaa tunnel calling-number-format include-agent-circuit-id include-agent-remote-id
host1(config)#aaa tunnel calling-number-format-fallback fixed

`

[Contents] [Prev] [Next] [Index] [Report an Error]