cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1186
Views
5
Helpful
4
Replies

Dynamic bandwidth selection for PPPoE over Ethernet/VLAN

hiepnguyenho
Level 1
Level 1

Hello all, hope you are doing great.

I'm planning to deploy PPPoE Server (Cisco Router 7609) for a ISP. This ISP will provide Internet connection for customer over Ethernet.

I have to provide a solution to assign bandwidth to each customer by RADIUS and I find some clues that Dynamic Bandwidth Selection (DBS) should be the answer. Unfortunately, DBS only support PPPoA or PPPoE over ATM.

If you have any experience with equivalent function, please help me. Thank you very much.

Regards,

Hiep Nguyen.

4 Replies 4

Stephen Teusch
Level 1
Level 1

Hiep Nguyen,

I was looking into this too.

The only thing I could think of so far would be to use radius to assign the IP, and build a large policy map so the bandwidth could be changed by choosing an IP from a given level of service.

Did you come up with a solution?

Stephen Teusch
Level 1
Level 1

Hiep,

 

I think I have figured this out.  Here is the test config on my PPPoE server:

 

int lo1
  ip address 172.25.25.25 255.255.255.255


ip radius source-interface Loopback1

aaa new-model

radius-server host 172.16.1.55 auth-port 1812 acct-port 1813 key cisco$$$

aaa group server radius RADIUS-ACT
 server 172.16.1.55 auth-port 1812 acct-port 1813  

aaa authentication login default group RADIUS-ACT local
aaa authorization exec default group RADIUS-ACT local
aaa accounting exec default start-stop group RADIUS-ACT

aaa accounting delay-start
aaa authentication ppp default if-needed group RADIUS-ACT local
aaa authorization network default group RADIUS-ACT local
aaa accounting network default start-stop group RADIUS-ACT
aaa accounting update periodic 5

bba-group pppoe global
 virtual-template 1

interface fa0/1
 pppoe enable group global
 ip address 172.30.0.1 255.255.0.0
 no shut

interface Virtual-Template1
 mtu 1492
 ip unnumbered FastEthernet0/1
 peer default ip address pool GLOBALPOOL
 ppp authentication chap

ip local pool GLOBALPOOL 172.30.0.2 172.30.127.255

policy-map POLICE-128K
 class class-default
    police 128000
policy-map POLICE-512K
 class class-default
    police 512000

 

Here are the attributes on the radius server, for a group the PPPoE customer belonged to:

Service-Type = Framed

Framed-Protocol = PPP

cisco-avpair="ip:sub-policy-In=POLICE-128K"

cisco-avpair+="ip:sub-policy-Out=POLICE-512K"

 

Here is the show policy-map on the virtual-access interface the client connected on:

sho policy-map int virtual-a 3
 Virtual-Access3

  Service-policy input: POLICE-128K

    Class-map: class-default (match-any)
      1000 packets, 1402000 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match: any
      police:
          cir 128000 bps, bc 4000 bytes
        conformed 799 packets, 1120198 bytes; actions:
          transmit
        exceeded 201 packets, 281802 bytes; actions:
          drop
        conformed 0 bps, exceed 0 bps

  Service-policy output: POLICE-512K

    Class-map: class-default (match-any)
      911 packets, 1137746 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match: any
      police:
          cir 512000 bps, bc 16000 bytes
        conformed 799 packets, 1136178 bytes; actions:
          transmit
        exceeded 0 packets, 0 bytes; actions:
          drop
        conformed 0 bps, exceed 0 bps

I was able to generate enough traffic with ping to meet the exceed action in and have it drop packets.

 

Hi Steven,

I got some troubles with your lab about defining ip:sub-policy-In on DaloRarius, could you please help?

Pedro,

It displays a SQL error.  This means that daloRadius is able to parse the request but your SQL server is not reading the SQL statement is creating for backend storage.  There is probably some versioning or SQL setting in dalo so the correct or supported SQL statements are used.  I cannot help you find it but I did a build guide for when I created my daloRadius server:

http://ephemeralportal.blogspot.jp/2014_07_01_archive.html