I'm implementing a BNG setup that requires me to format the username sent to a radius server for IPoEv6 authentication (fiber access). Customer requirement is that the username is created through the use of two fields: dhcpv6-interface-id and remote-id-tag. The problem I'm faced with is that the remote-id-tag attribute is coming in with extra characters that the ONT/OLT attach at the front of this field. For example: we're receiving "000007db302f332f30" instead of only "302f332f30" which is what we actually need from the remote-id-tag. (dhcpv6-interface-id is coming in as we expect it).
This string (000007db302f332f30) if converted to ASCII reflects the slot where this ONT resides, in this case "something+Û+0/3/0". Customer requirement mandates that we use "0/3/0" as part of the username, along with the information in dhcpv6-interface-id. I've been told by TAC that the problem is the 0000007 which is not printable by BNG (the documentation they sent me points to option82 in an ASR1k, I'm working with options 18 and 37 on an ASR9k), which forces the box to send the HEX string as is, instead of printing it (ASCII).
So, here's a few question to see if some of you have an idea how to deal with this.
- Does the BNG support a way to truncate the remote-id-tag attribute so that we only process/send the characters we need?
- If yes, can you provide a sample of how to achieve this?
- If this cannot be solved by the BNG itself and I'm not allowed to do this in the radius server (at least, at this point, I'm not allowed), can you thing of another solution?
IOS upgrade on asr9xx mandates rommon upgrades sometimes while they can be optional at other times. You may land up in unwanted situation if proper procedure is not followed during upgrades.
This article will include complete details about rommon ...
In some situation NCS560 RP become unresponsive after reload or powercycle.
In many deployments NCS560 far edge, deployment is large and human intervention should be kept at minimum
Engineering team have been working on a strategy to have functi...
In simple terms, 'Route Churn' is defined as the 'rate of change of prefixes'. Different XR versions across 4.x to 7.x have differing behavior & support for the BGP churn handling and some enhancements made from 6.5.3 onwards (listed in appendix) mak...
Prior to Cisco IOS XR Software Release 7.1.2, XR dual RP devices did not support file mirroring from active RP to standby RP. Administrators had to manually perform the task or use EEM scripts to sync files across active RP and stand...
Hi Everyone, Would like to extend my thanks in advance for anyone offering assistance. As the subject hints, anyone here know of a way to convert IOS configs to XR config? I seen and heard about SOX tool but i am unable to find it. I also tried ...