Policy implementation based on OLT/access identification rather than Per subscriber on the BNG

[somnathsafi2344]

We are stuck in the situation where the user behind a specific OLT are to be provided with
one particular service and rest OLT to be provided with service per subscriber. Policy per subscriber
here means the service/policy name which is being received by the BNG during the Radius-accept message

[Fredrik Lönnman]

If you're able to separate the users that need the special configuration to a different VLAN than the VLAN can be used as an access identifier with a different service policy etc.

[somnathsafi2344]

Thanks for the quick response. Like to add few line so that more precision toward the Use case can be made from my end.
Every OTL packed are marked with separate VLAN but all these OLT are aligned with predefined configuration to get the service name from the Radius server i.e in radius Accept message.
whether we can configure static policy map based on these VLAN NUMBER where priority is given to this policy rather than what received from the Radius Server.
kindly share some CLM line if possible

[Fredrik Lönnman]

Kind of depends on your configuration today, but if you have for example the access interfaces in the BNG configured for ambigious matching of your VLANs, then you can create another subinterface with a more specific VLAN combo matching and put a separate policy-map there.

More specific VLAN combo subinterfaces will be matched before the more general ambigious matching interfaces so you can match specific customers based on VLAN tag.