- play_arrow Configuring DHCP Layer 3 Wholesale Networks
- play_arrow Subscriber Management DHCP Layer 3 Wholesale Overview
- Layer 2 and Layer 3 Wholesale Overview
- Wholesale Network Configuration Options and Considerations
- DHCP Layer 3 Wholesale Configuration Interface Support
- Layer 3 Wholesale Configuration DHCP Support
- Subscriber to Logical System and Routing Instance Relationship
- RADIUS VSAs and Broadband Subscriber Management Wholesale Configuration Overview
- play_arrow Configuring DHCPv4 Layer 3 Wholesale Networks
- Broadband Subscriber Management DHCPv4 Layer 3 Wholesale Topology and Configuration Elements
- DHCPv4 Layer 3 Wholesale Network Topology Overview
- Configuring Loopback Interfaces for the DHCPv4 Layer 3 Wholesale Solution
- Configuring VLANs for the DHCPv4 Layer 3 Wholesale Network Solution
- Configuring Access Components for the DHCP Layer 3 Wholesale Network Solution
- Configuring Dynamic Profiles for the DHCPv4 Layer 3 Wholesale Network Solution
- Configuring Separate Routing Instances for DHCPv4 Service Retailers
- Configure Default Forwarding Options for the DHCPv4 Wholesale Network Solution
- Example: Wholesaler Dynamic Profile for a DHCPv4 Wholesale Network
- Example: Retailer Dynamic Profile for a DHCPv4 Wholesale Network
- Example: Default Forwarding Options Configuration for the DHCPv4 Wholesale Network
- Example: Retailer Routing Instances for a DHCPv4 Wholesale Network
- play_arrow Configuring DHCPv6 Layer 3 Wholesale Networks
- Broadband Subscriber Management DHCPv6 Layer 3 Wholesale Topology and Configuration Elements
- DHCPv6 Layer 3 Wholesale Network Topology Overview
- Configuring Loopback Interfaces for the DHCPv6 Layer 3 Wholesale Solution
- Configuring VLANs for the DHCPv6 Layer 3 Wholesale Network Solution
- Configuring Access Components for the DHCP Layer 3 Wholesale Network Solution
- Configuring Dynamic Profiles for the DHCPv6 Layer 3 Wholesale Network Solution
- Configuring Separate Routing Instances for DHCPv6 Service Retailers
- Configuring Address Server Elements for the DHCPv6 Layer 3 Wholesale Solution
- Example: Retailer Dynamic Profile for a DHCPv6 Wholesale Network
- Example: Retailer Routing Instances for a DHCPv6 Wholesale Network
- Example: DHCPv6 Address Assignment Pool That Provides Full 128-bit IPV6 Addresses for a DHCPv6 Wholesale Network
- Example: DHCPv6 Address Assignment Pool That Provides 74-bit IPV6 Prefixes for a DHCPv6 Wholesale Network
- Example: Extended DHCPv6 Local Server for a DHCPv6 Wholesale Network
-
- play_arrow Configuring PPPoE Layer 3 Wholesale Networks
- play_arrow Subscriber Management PPPoE Wholesale Overview
- play_arrow Configuring PPPoE Layer 3 Wholesale Networks
- Broadband Subscriber Management PPPoE Layer 3 Wholesale Topology and Configuration Elements
- PPPoE Layer 3 Wholesale Network Topology Overview
- Configuring Loopback Interfaces for the PPPoE Layer 3 Wholesale Solution
- Configuring Static Customer VLANs for the PPPoE Layer 3 Wholesale Network Solution
- Configuring Access Components for the PPPoE Wholesale Network Solution
- Configuring Dynamic Profiles for the PPPoE Layer 3 Wholesale Network Solution
- Configuring Separate Routing Instances for PPPoE Service Retailers
- Example: Wholesaler Dynamic Profile for a PPPoE Wholesale Network
- Example: Retailer Routing Instances for a PPPoE Wholesale Network
-
- play_arrow Configuring Layer 2 Wholesale Networks
- play_arrow Subscriber Management Layer 2 Wholesale Overview
- play_arrow Configuring Layer 2 Wholesale Networks
- Broadband Subscriber Management Layer 2 Wholesale Topology and Configuration Elements
- Layer 2 Wholesale Network Topology Overview
- Configuring a Retail Dynamic Profile for Use in the Layer 2 Wholesale Solution
- Stacking and Rewriting VLAN Tags for the Layer 2 Wholesale Solution
- Configuring VLAN Interfaces for the Layer 2 Wholesale Solution
- Configuring Encapsulation for Layer 2 Wholesale VLAN Interfaces
- Configuring NNI ISP-Facing Interfaces for the Layer 2 Wholesale Solution
- Configuring Direct ISP-Facing Interfaces for the Layer 2 Wholesale Solution
- Configuring Separate Access Routing Instances for Layer 2 Wholesale Service Retailers
- Configuring Separate NNI Routing Instances for Layer 2 Wholesale Service Retailers
- Configuring Access Components for the Layer 2 Wholesale Network Solution
- Example: Retailer Dynamic Profile for a Layer 2 Wholesale Network
- Example: Access Interface for a Layer 2 Wholesale Network
- Example: Retailer Access Routing Instances for a Layer 2 Wholesale Network
- Example: Retailer NNI ISP-Facing Interfaces for a Layer 2 Wholesale Network
- Example: Retailer Direct ISP-Facing Interface for a Layer 2 Wholesale Network
-
- play_arrow Configuration Statements and Operational Commands
Configuring a Username for Authentication of Out-of-Band Triggered Dynamic VLANs
When a subscriber logs in, the Access-Request message that is sent to the RADIUS server includes a username and optionally a password generated locally on the router to authenticate the subscriber during the VLAN authorization process. For a Layer 2 network that is wholesaled to a retailer where the dynamic VLANs are instantiated by out-of-band ANCP Port Up messages, you can configure the router to create a unique username with the value of the ANCP TLVs—Access-Loop-Circuit-ID, Access-Loop-Remote-Id, or both—as received in the ANCP Port Up message from the access node.
This configuration assumes the following:
The ANCP agent is configured to notify AAA when it receives ANCP Port Up and Port Down messages.
The dynamic profile is configured to instantiate a dynamic VLAN when notified by the ANCP agent that it has received an out-of-band ANCP Port Up message.
The RADIUS authentication server is properly configured.
To include ANCP TLVs in the authentication username
This ANCP information is not supported in stacked VLANs.
You can use any of the attributes available to the username-include
statement, except: mac-address
, option-18
, option-37
, and option-82
.
You can include other information in the username as for conventional autosensed dynamic VLANs. Alternatively, if you configure the router to convey ANCP-sourced access loop attributes as Juniper Networks VSAs—in this case Acc-Loop-Cir-Id (26-110) and Acc-Loop-Remote-Id (26-182)—the Access-Request message includes sufficient unique access line information for the RADIUS server to determine whether the access loop is wholesaled to a retailer or retained for the wholesaler.