Configuring Bridged Ethernet Dynamic Interfaces

A bridged Ethernet interface is IP over bridged Ethernet over ATM 1483 over ATM AAL5 over ATM.

When bridged Ethernet packets are received over ATM circuits, the bridged Ethernet and IP interfaces are dynamically constructed over the corresponding ATM 1483 interfaces and use the configuration data received from the RADIUS server, a profile, or both.

Figure 55 shows the protocol layers that represent the bridged Ethernet interface columns, and the layers within the interface columns that are static and dynamic.

Figure 55: Dynamic Bridged Ethernet over Static ATM 1483 Interface Columns

Configuring a Dynamic Bridged Ethernet Interface

When you configure dynamic bridged Ethernet interfaces, you must assign a profile. You may optionally assign a subscriber identification.

To configure dynamic bridged Ethernet interfaces:

1. Configure a physical interface.
   host1(config)#interface atm 5/0
2. Configure an ATM subinterface.
   host1(config-if)#interface atm 2/0.1
3. Configure a PVC by specifying the VCD, the VPI, the VCI, and the encapsulation type.

   If you want the router to autodetect the encapsulation type, use the aal5autoconfig option.

   host1(config-subif)#atm pvc 10 100 22 aal5snap host1(config-subif)#atm pvc 10 100 22 aal5autoconfig
4. Do either of the following:
   • Configure the subinterface to detect and accept the dynamic bridged Ethernet encapsulation type with the default lockout time range, 1–300 seconds.
     host1(config-subif)#auto-configure bridgedEthernet
   • Configure the subinterface to detect and accept the dynamic bridged Ethernet encapsulation type with a nondefault lockout time range. For example, the following command configures 3600 seconds (1 hour) as the minimum lockout time and 7200 seconds (2 hours) as the maximum lockout time.
     host1(config-subif)#auto-configure bridgedEthernet lockout-time 3600 7200
5. Assign a profile to match the encapsulation type of bridged Ethernet.
   host1(config-subif)#profile bridgedEthernet foo
6. (Optional) Assign subscriber identification.
   host1(config-subif)#subscriber bridgedEthernet user charlie domain myisp password lucy
7. (Optional) Verify your configuration.
   host1#show atm subinterface atm 2/0.1

Configuring Subscriber Management for IP Subscribers on Dynamic Bridged Ethernet Interfaces

You can use the JunosE subscriber management application to configure and manage IP subscribers associated with a dynamic bridged Ethernet over static ATM 1483 interface column, as described in Authenticating Subscribers on Dynamic Bridged Ethernet over Static ATM Interfaces.

To use the subscriber management application to configure IP subscribers on a dynamic bridged Ethernet interface for RADIUS authentication:

1. Define an IP service profile that contains the subscriber’s RADIUS authentication parameters including the username, domain, and password.
2. Configure the interface profile from which the router creates a dynamic bridged Ethernet interface column.
   1. Include the desired characteristics for the upper-layer encapsulation types.
   2. (Optional) Specify the name of the route map used to configure the IP subscriber interface.
   3. Use the bridge1483 service-profile command to assign the specified IP service profile to the interface profile. The IP service profile contains the RADIUS authentication parameters for subscribers on the dynamic bridged Ethernet interface.
3. Define the underlying static or dynamic ATM 1483 subinterface on which the dynamic bridged Ethernet interface column is built.
   1. Assign the specified interface profile to the ATM 1483 subinterface.
   2. Enable autodetection (autoconfiguration) of the bridged Ethernet upper-layer encapsulation type.
   3. Define the ATM PVC over which data is transmitted.
4. (Optional) Use the show profile command to verify assignment of the IP service profile to the interface profile.

   For information, see show profile.

Configuration Example Using subscriber Command

The following configuration example illustrates the preceding procedure. The example has two parts:

• The first part of the example shows how to use the subscriber command to configure RADIUS authentication for IP subscribers on a dynamic bridged Ethernet interface. This configuration method does not support running stateful SRP switchover on the router.
• The second part of the example shows the commands required to re-create this configuration using the IP subscriber management application. This configuration method uses the bridge1483 service-profile command to assign the specified IP service profile to the interface profile, and does support running stateful SRP switchover on the router.

Assume that you have issued the following commands to configure IP subscribers on a dynamic bridged Ethernet interface for RADIUS authentication. In this configuration, the subscriber command provides the subscriber’s authentication parameters, and the static ATM 1483 subinterface is the authenticating layer. Keep in mind that the subscriber command does not support running stateful SRP switchover on the router.

Equivalent Configuration Example Using IP Subscriber Management

To achieve the same functionality without adversely affecting stateful SRP switchover if it is running on the router, you can issue the following commands to use the subscriber management feature to configure IP subscribers on a dynamic bridged Ethernet interface using RADIUS. In this configuration, the IP service profile provides the subscriber’s authentication parameters, and the subscriber management application is the authenticating layer. To assign the IP service profile to the interface profile, use the bridge1483 service-profile command.

For more information about using the subscriber management application, see JunosE Broadband Access Configuration Guide.