- 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 the ANCP Agent to Dampen the Effects of Short-Term Adjacency Losses
By default, the ANCP agent treats a loss of adjacency as if it has received a Port Down message for every access loop that is represented by the adjacency. All Layer 2 wholesale sessions are logged out and cleaned up. If the associated physical interface is in the Down state, then pending sessions cannot be reestablished when the interface transitions back to the Up state.
You can configure the ANCP agent to maintain the corresponding ANCP-triggered Layer 2 wholesale sessions for a configurable period in the event that an ANCP adjacency is lost. If the adjacency is restored before the timer expires, the session continues. If the timer expires before the adjacency is restored, then the session is logged out and cleaned up. This behavior dampens the effect of unstable ANCP connections. The hold timer can also detect when an access line is unconfigured on a neighbor and trigger logout and cleanup of the related sessions.
The default value of the timer is 0, which means that the loss of neighbor adjacency immediately triggers a logout of all corresponding Layer 2 wholesale sessions.
To configure how long the ANCP agent maintains sessions in the event of an adjacency loss for any neighbor:
Specify the hold timer duration in seconds.
content_copy zoom_out_map[edit protocols ancp] user@host# set adjacency-loss-hold-time seconds
To configure how long the ANCP agent maintains sessions in the event of an adjacency loss for a specific neighbor:
Specify the hold timer duration in seconds.
content_copy zoom_out_map[edit protocols ancp neighbor ip-address] user@host# set adjacency-loss-hold-time seconds