Symptom
the existing BNG implementation use a cisco AV-pair "sa=" to activate a service in radius access-accept or COA request. for OCN customer , their existing radius server and back end system do not support this format of AVpair for service activate, the working method is a non-AVPair VSA to achieve the same goal.
This defect was found during the certification test before deployment, an eng SMU on 5.1.3 built by Eng team helped pass the certification test and we successfully win the deal against Huawei who has installation base in OCN. now customer is going to deploy the first 2 sets of ASR9K as PPPoE BNG in Jan 2015 and the chosen image release 5.1.3 since that is the verified release in the certification test, according to customer's release management policy, only lab verified release could be used in production network. Without this production SMU, we must fail the deployment and loss the share back to huawei.
Further Problem Description
the existing BNG implementation use a cisco AV-pair "sa=" to activate a service in radius access-accept or COA request. for some customer , they want a non-AVPair VSA to achieve the same goal for interpretational reason, a possible way is to use a non-AVpair VSA ( 26,9, x x!=1) =
