Hi Chris, Thanx for the info. Isn't the RADIUS CoA also licensed and part of the servivce manager ?
Kind regards, Tom ________________________________ Van: Chris Hellberg [ch...@chrishellberg.com] Verzonden: vrijdag 5 augustus 2011 21:38 Aan: Tom Teeuwen CC: juniper-nsp@puck.nether.net Onderwerp: Re: [j-nsp] simple QoS-policy ERX310 Hi Tom, There are a couple of ways of doing this in real time without clearing the session: * use service manager to change the QoS profile. Service manager is a hefty feature that can do various subscriber management magic, such as on-box volume and time quotas. One of the other capabilities of service manage is to be able to change the user's QoS profile. It's a licensable/chargeable feature tho. * switch to using policies to cap user bandwidth and use RADIUS CoA to change session rate limits. Cheers, Chris ________________________________ From: Tom Teeuwen <t...@tomteeuwen.eu> To: "ch...@chrishellberg.com" <ch...@chrishellberg.com> Cc: "juniper-nsp@puck.nether.net" <juniper-nsp@puck.nether.net> Sent: Thursday, 4 August 2011, 12:17 Subject: RE: [j-nsp] simple QoS-policy ERX310 Hello Chris, I already looked at the first two options but our wholesaleprovider doesn't support this option. Now i'm thinking of the last option, i can retrieve the downstreamrate via SNMP and add it to the RADIUS database. But is there a way to configure the ERX to adjust the queue with the new retrieved bandwidth ? Kind regards, Tom ________________________________________ Van: Chris Hellberg [ch...@chrishellberg.com<mailto:ch...@chrishellberg.com>] Verzonden: woensdag 3 augustus 2011 22:05 Aan: Tom Teeuwen; juniper-nsp-boun...@puck.nether.net<mailto:juniper-nsp-boun...@puck.nether.net>; juniper-nsp@puck.nether.net<mailto:juniper-nsp@puck.nether.net> Onderwerp: Re: [j-nsp] simple QoS-policy ERX310 Tom, The tricky part is getting the line rate out of yours (or your wholesaler's) equipment. What you do with it (ie on the 310) is easier. You could extract it in these ways: * ANCP between DSLAM/AN and the ERX to continually exchange line rate details (best) and feed these data into your qos profile. * PPPoE rate info stamped in PADI and PADR packets by the AN. The drawback is when the line speeds(s) adjust(s) without retraining the DSL line, which is normal, the ERX will not have an accurate view of the new line speed(s) * an out-of-band homegrown solution to put the line rate from the AN or its NMS into your radius server and use QoS parameters in conjunction with QoS profiles. But the same drawback exists here as with the second option. Regards, Chris -----Original Message----- From: Tom Teeuwen <t...@tomteeuwen.eu<mailto:t...@tomteeuwen.eu>> Sender: juniper-nsp-boun...@puck.nether.net<mailto:juniper-nsp-boun...@puck.nether.net> Date: Wed, 3 Aug 2011 18:23:10 To: juniper-nsp@puck.nether.net<mailto:juniper-nsp@puck.nether.net><juniper-nsp@puck.nether.net<mailto:juniper-nsp@puck.nether.net>> Subject: [j-nsp] simple QoS-policy ERX310 Hello, We have a setup with an ERX310 for aggregating PPPoE connection (xDSL). The connections are terminated on a GigabitEthernet interface. Now we want to setup QoS for VoIP on the downstreamtraffic. I can create a QoS policy with 2 queues, one best-effort and a voice queue with strict priority and give it an assured-rate of 500Kbps. Via RADIUS i can assign the policy to the PPPoE interface. But i need to specify the maximum bandwidth for the best-effort queue to let it work. The problem is that when i have a customer with a 8mbps ADSL-connection this can be a 7Mbps connection in practice because of the local-loop lenght. So this qos policy is not gonna work. Is there a easier way to achieve this, without the need to assign this maximum bandwidth ? Kind regards, Tom _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net<mailto:juniper-nsp@puck.nether.net> https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
