Identify amount of traffic to special IP address in Radius

Hi,


In order to summrize broadband subsciber's traffic
data, we need to identify those traffic to our video
servers by BRAS which use Radius. Currently, our BRAS
could only report total amount of traffic a subscriber
transferred.

Could we make BRAS genenrate radius accounting data
including tags indicating destination IP information ?


thanks 

Joe 



		
__________________________________ 
Do you Yahoo!?
Yahoo! Movies - Search movie info and celeb profiles and
photos.
http://sg.movies.yahoo.co
m/

On Feb 28, 2006, at 10:55 PM, Joe Shen wrote:

>
> Hi,
>
>
> In order to summrize broadband subsciber's traffic
> data, we need to identify those traffic to our video
> servers by BRAS which use Radius. Currently, our BRAS
> could only report total amount of traffic a subscriber
> transferred.
>
> Could we make BRAS genenrate radius accounting data
> including tags indicating destination IP information ?

I'm trying to contain my horror and be nice , but why
in the world  
would you want to do something like that rather than have
another  
device generate flow records which you then can correlate
with RADIUS  
accounting data?

Best regards,
Christian

> why in the world  
> would you want to do something like that rather than
> have another  
> device generate flow records which you then can
> correlate with RADIUS  
> accounting data?
> 

The reason is the cost of system building. As there
are a lot of broadband subscribers, if we want to
corelate subscriber with web site they visit we have
to make Radius allocate a fixed IP to a special
subscriber. Netflow based accounting is costy and we
could not guarantee its accuracy. 

In fact, we only need to identify a small set of IPs
which should not be considered in accounting.

Joe


Send instant messages to your online friends http://asia.messenger
.yahoo.com 

On Feb 28, 2006, at 11:59 PM, Joe Shen wrote:

>> why in the world
>> would you want to do something like that rather
than
>> have another
>> device generate flow records which you then can
>> correlate with RADIUS
>> accounting data?
>>
>
> The reason is the cost of system building. As there
> are a lot of broadband subscribers, if we want to
> corelate subscriber with web site they visit we have
> to make Radius allocate a fixed IP to a special
> subscriber. Netflow based accounting is costy and we
> could not guarantee its accuracy.

I would submit to you that getting such functionality built
and  
operating via RADIUS is expensive as well.  If you have a
lot of  
broadband subscribers, your BRAS will already be busy doing
what it  
does 'best': terminating subscriber sessions.  Plus, you
have to get  
your vendor to implement such a feature.. I haven't seen
something  
like what you describe in the years of looking at BRAS
requirements.   
But, that doesn't mean it doesn't exist in a scalable
fashion.

> In fact, we only need to identify a small set of IPs
> which should not be considered in accounting.

If you need to generate IP accounting for just a small set
of IPs,  
the above engineering challenge you describe is very
straightforward  
for capturing flow records.

YMMV, of course.