We are trying to configuration LDP pseudowire auto-sensing on a MX Series router:
root@JTAC> show configuration protocols l2circuit
traceoptions {
file debug-l2c.log size 10m;
flag all;
flag auto-sensing;
}
auto-sensing {
password "abc"; ## SECRET-DATA
However, there is no documentation telling us how a response is supposed to look like. Can you help us to find the appropriate RADIUS Reply-Items to specify:
The Interface End-Point on which the PW will terminate.
I have tried various attributes from: https://datatracker.ietf.org/doc/html/rfc2868, but they do not seem to work. Unfortunately, we could not find any documentation on the specific radius attributes for this feature.
(19) Received Access-Request Id 199 from a.b.c.d:x to a.b.c.e:y length 151
(19) User-Name = "root"
(19) User-Password = "root"
(19) Service-Type = Framed-User
(19) Chargeable-User-Identity = 0x00
(19) Acct-Session-Id = "273"
(19) Calling-Station-Id = "#"
(19) ERX-Dhcp-Mac-Addr = "0000.0000.0000"
(19) NAS-Identifier = "xyz1"
(19) NAS-Port = 4095
(19) NAS-Port-Id = "-0/0/0.0"
(19) NAS-Port-Type = Ethernet
(19) ERX-Pppoe-Description = "pppoe 00:00:00:00:00:00"
This RLI minimally two VSAs need to be returned (VSA is Vendor Specific Attribute):
> VSA 26-4874-65 Activate-Service which will contain the op-script name with any arguments
> VSA 26-4874-173 Service-Activate-Type, which needs to contain the value 2, for op-script. This isa cue for authd to initiate exchanges with essmd, which will run the op-script using the dictionary to provision the PW
Note that VSA 26-4874-65 is used for both services applied by a dynamic service profile (the default use case, such that VSA 26-4874-173 Service-Activate-Type is optional but can be explicitly returned with the value 1, for dynamic-profile) or apply a service not supported by a dynamic service profile using an op-script via essmd. For this case VSA 26-4874-173 Service-Activate-Type must be returned with the value 2.
The attributes are based on the use cases & below is such an example,
A distinct user with username and password is created on the SBR for each auto-sensed PW. The username is constructed in the format of <AN-address>.VC-ID. The password should match the “protocols l2circuit auto-sensing password” configuration on the SN. The Activate Service attribute in the return list may contain any service string depending on use cases. In this unit test, it simply contains the service name “pw_auto_sensing” and a PS IFD
Call Flow:
1.CPE sends DHCP discover in c-vlan to OLT which adds S-VLAN and forwards to Access Node (AN)
2.Optionally, AN checks with Radius to authorize QinQ VLAN. Radius sends Access Accept
3.AN sends LDP Label Mapping Message to Service Node (SN)
•Include PW ID, Encapsulation type (VLAN or Eth), MTU and Control Word
4.SN checks with Radius and if allowed creates PW
5.SN sends LDP Label Mapping Message to AN and completing PW signalling and creating PW