Radius attribute vs bng config

[jvunc]

Hello

i am testing both solutions to retreive attribute to PPPoE/IPoE/V4/V6 subscriber, through Radius and "hard" config on ASR9K.

The results is that both solution work well.

Nevertheless, which solution is better, i mean:

* minimal attributes config on Radius and all others on BNG ?

* or opposite on BNG ?

what is the best practice?

jacques

[xr-escalation]

as always, "it depends". :) In low scale deployments you can go either way.

In high scale deployments it makes a difference in these scenarios:

1) IP address assignment: if you allow radius to allocate IP addresses to subscribers, the BNG may end up with lots of host routes that can't be summarised. Redistribution of subscriber routes causes unnecessary churn in the routing table. It's better to have an address pool per BNG, so that only the summary route is advertised though IGP/BGP.

2) QoS: if QoS policies are defined on the router and through radius you only decide which policy to apply to which subscriber, HW resources are used optimally. One policy instance is programmed in HW and each subscriber gets a dedicated counter space for statistics. If you use the parametrised QoS on radius, every policy instance is programmed into HW independently. This may prevent the BNG from reaching the nominal subscriber scale.

Maybe some has more use cases to suggest...

/Aleksandar