Migrate Subscribers from BNG to AGF

Using an Interface Tag to Migrate DHCP Subscribers from the BNG to the AGF

Before Junos OS 23.2R1, you could only map one DHCP group to a physical interface (IFD) that is supporting dynamic VLANs. This limits the interface to supporting subscribers with the same DHCP requirements. Starting in Junos OS 23.2R1, you can use interface tags to map a single dynamic VLAN or a group of dynamic VLANs to different DHCP groups. Therefore, you can support subscribers with different DHCP requirements on one IFD. The device will use the interface tag to map the incoming subscriber VLAN ID in the profile to the DHCP group. This feature allows you to easily migrate users from the BNG to the AGF.

To support multiple DHCP groups on the same physical interface:

• Configure the interface-tag in the dynamic profile on a VLAN demux interface.

  • set dynamic-profiles profile-name interfaces demux0 unit $junos-interface-unit interface-tag interface-tag-name

• Configure the dynamic VLAN demux (auto-sensed) interface and corresponding dynamic profile. Specify the VLAN range subset that will map the dynamic profile to the DHCP group.

• Map the dynamic profile to the associated DHCP group by specifying the same interface-tag name. For more information on configuring DHCP Local Server and DHCP Relay Servers, see Common DHCP Configuration for Interface Groups and Server Groups.

  DHCP Relay

  • set forwarding-options dhcp-relay group name interface-tag interface-tag-name

  • set forwarding-options dhcp-relay dhcpv6 group name interface-tag interface-tag-name

  DHCP Local Server

  • set system services dhcp-local-server group sgroup interface-tag interface-tag-name

  • set system services dhcp-local-server dhcpv6 group sgroup interface-tag interface-tag-name

Note:

Subscribers migrating from broadband to AGF will maintain their DHCP session until they terminate their session.

Subscribers who are eligible for migration remain connected in their DHCP session. Once the subscriber logs off and the DHCP session has been terminated, the router migrates the subscriber to AGF at the next successful login (DHCP renegotiation).

Use the following show DHCP binding command with the detail option to displays interface tag information:

• show dhcp relay binding detail

• show dhcpv6 relay binding detail

• show dhcp server binding detail

• show dhcpv6 server binding detail

Configure Access Support for BNG and AGF

The following example shows how to configure a physical interface (IFD) on a device to support both BNG and AGF subscribers. We configure two dynamic profiles on the demux interface (demux0—one profile for the BNG subscribers and one for AGF subscribers). The device uses the VLAN ID to map a subscriber to a dynamic profile. The device then uses the interface tag in the dynamic profile to map the subscriber to a DHCP group.

1. Configure dynamic profiles to support incoming subscribers on demux interface. Configure one dynamic profile for BNG subscribers and another profile for AGF subscribers. Use the same interface tag name in both the dynamic profile and the DHCP group. In this example, we use an interface tag that identifies the VLAN range.

   BNG

   AGF

2. Configure the interface with two dynamic profiles (BNG_DPROFILE and AGF_DPROFILE). Specify the VLAN range in the dynamic profile that maps to the DHCP group.

   BNG

   AGF

3. Configure the DHCP relay configuration for the access interface. Use the corresponding interface tag name from dynamic profile in the DHCP group. We configure the set forwarding-options dhcp-relay group DHCPv4_CLIENT_GROUP_2 interface xe-1/1/0.0 as a fallback when there are additional VLAN IDs. The router gives the interface tag precedence over the interface statement.

   BNG

   AGF