Before configuring EDSG, familiarize yourself with the usage scenario, complete the pre-configuration tasks, and obtain the data required for the configuration.
In some regions, small local carriers need to rent backbone carriers' lines to provide Internet access services to users. The local carriers also need to pay the backbone carriers for traffic over the backbone networks. Low fees are charged for traffic over a local network, whereas high fees are charged for traffic over a backbone network. To increase revenues, local carriers need a solution that can distinguish the two types of traffic and perform accounting based on network types. EDSG meets this requirement. Two EDSG services can be configured for the local and backbone networks based on destination addresses to implement differentiated accounting on traffic over both the local and backbone networks.
When campus users access a campus network, the carrier does not charge any fees or charges low fees, and the access rate is unlimited. However, when campus users access an external network, the carrier charges high fees and limits their access rates. To increase the carrier's revenues, configure two EDSG services for the campus and external networks based on destination addresses to implement differentiated accounting and rate limit on traffic over both the campus and external networks.
Many Internet services, such as gaming, File Transfer Protocol (FTP), video on demand (VOD), and news services, have different costs and bandwidth requirements. To implement differentiated accounting and rate limit on various services, configure these services as different EDSG services.
As shown in Figure 1, Point-to-Point Protocol over Ethernet (PPPoE) users access networks 1 and 2. Different fees need to be charged for traffic over networks 1 and 2. The users have different bandwidth requirements for networks 1 and 2. To meet these requirements, configure two EDSG services on the broadband remote access server (BRAS) to perform differentiated accounting and rate limit on traffic over networks 1 and 2. EDSG allows carriers to provide flexible service and accounting policies for different user requirements.
AAA server: provides user authentication, authorization, and accounting. Generally, a RADIUS server is used as a AAA server.
Policy server: delivers EDSG service policies. Only a RADIUS server can be used as a policy server.
Portal server: provides user interfaces. Users can log in to a portal server and select EDSG services as required. A portal server is generally integrated into a AAA or policy server.
Before configuring EDSG, complete the following tasks:
Load the BRAS license and the EDSG license.
Configure an authentication scheme, an accounting scheme, and a RADIUS server group for an EDSG service policy (for details, see AAA and User Management Configuration (Access Users)).
Configure an address pool (for details, see Configuring an IPv4 Address Pool and an Address Pool Group).
Configure a domain and bind the authentication scheme, accounting scheme, address pool, and RADIUS server group to the domain (for details, see Configuring a Domain).
Configure a BAS interface (for details, see IPoE Access Configuration and PPPoE Access Configuration).