[an error occurred while processing this directive][an error occurred while processing this directive]

Configuring Access Components for the PPPoE Wholesale Network Solution

When configuring a wholesale network, you must configure several components globally. This configuration provides access to RADIUS servers (if used) that you want the wholesaler and any configured retailers to use globally. The access configuration includes the following general steps:

  1. Configuring RADIUS Server Access
  2. Configuring a PPPoE Wholesaler Access Profile
  3. Configuring PPPoE Retailer Access Profiles

Configuring RADIUS Server Access

You can globally define any RADIUS servers in your network that either the wholesale access profile or retailer access profile can use. After you define the global RADIUS servers, you can specify specific RADIUS servers within individual access profiles.

To define RADIUS servers for profile access:

  1. Access the [edit access radius-server] hierarchy level.
    [edit ]user@host# edit access radius-server
  2. Specify the address and secret for any RADIUS servers in the network.
    [edit access radius-server]user@host# set 192.168.10.1 secret $9$CzBxBBf1eWx-wM8xgaU.m345B02EcyKXLuser@host# set 10.10.10.1 secret $7$OsCsBAf1fXx-wY3xgaU.m123A02ZtyNMT

Configuring a PPPoE Wholesaler Access Profile

You must define the network and interface over which you want subscribers to initially access the network with a wholesale access profile. When a subscriber attempts to access the network, the access profile provides initial access information including authentication and accounting values that the router uses for the accessing subscriber.

To define a wholesale access profile:

  1. Create the wholesale access profile.
    [edit]user@host# edit access profile PPPoE_Wholesaler_Access
  2. Specify the authentication methods for the profile and the order in which they are used.
    [edit access profile Wholesaler1]user@host# set authentication-order radius
  3. Specify that you want to configure RADIUS support.
    [edit access profile Wholesaler1]user@host# edit radius (Access Profile)
  4. Specify the IP address of the RADIUS server used for authentication.
    [edit access profile Wholesaler1 radius] user@host# set authentication-server 192.168.10.1
  5. Specify the IP address of the RADIUS server used for accounting.
    [edit access profile Wholesaler1 radius] user@host# set accounting-server 192.168.10.1
  6. Configure any desired options for the RADIUS server.

    See Configuring RADIUS Server Options for Subscriber Access.

  7. Configure subscriber accounting (RADIUS accounting).

    See Configuring How Accounting Statistics Are Collected for Subscriber Access.

Configuring PPPoE Retailer Access Profiles

In this solution, subscribers are redirected to a networking space used by a specific retailer and defined by a unique routing instance. This method requires that you define the network and interface over which you want subscribers to access the network after being redirected by the wholesale access profile.

To define a retailer access profile:

  1. Create the retailer access profile.
    [edit]user@host# edit access profile PPPoE_Retailer_Access1
  2. Specify the authentication methods for the profile and the order in which they are used.
    [edit access profile Retailer1]user@host# set authentication-order radius
  3. Specify that you want to configure RADIUS support.
    [edit access profile Retailer1]user@host# edit radius (Access Profile)
  4. Specify the IP address of the RADIUS server used for authentication.
    [edit access profile Retailer1 radius] user@host# set authentication-server 10.10.10.1
  5. Specify the IP address of the RADIUS server used for accounting.
    [edit access profile Retailer1 radius] user@host# set accounting-server 10.10.10.1
  6. Configure any desired options for the RADIUS server.

    See Configuring RADIUS Server Options for Subscriber Access.

  7. Configure subscriber accounting (RADIUS accounting).

    See Configuring How Accounting Statistics Are Collected for Subscriber Access.


Published: 2010-04-14

[an error occurred while processing this directive]