Hello,
I have a customer with two PPPoE connections.
The first one is a FTTH and the second one is a FTTC.
I would like to use the second one as backup.
Customer side no problem, I use the track command.
My problem is BNG side.
The customer use public IP for the services so I have to "move" the routing from the primary to the secondary connection in case of fault.
One solution could be to have a Radius configuration like this one:
// FTTH primary
primary@itesys.it Cleartext-Password := "12345"
Service-Type = Framed-User,
Framed-Protocol = PPP,
Framed-IP-Address=10.20.20.100,
Framed-IP-Netmask=255.255.255.255,
Framed-Route="150.A1.B1.C1/30 10.20.20.100",
// FTTC secondary backup
backup@itesys.it Cleartext-Password := "12345"
Service-Type = Framed-User,
Framed-Protocol = PPP,
Framed-IP-Address=10.20.20.101,
Framed-IP-Netmask=255.255.255.255,
Framed-Route="150.A1.B1.C1/30 10.20.20.101 100",
The problem is that the second connection does not authenticate because there is this error:
LC/0/2/CPU0:Sep 22 10:10:32.705 CET: PPP-MA[316]: %L2-PPP_MA-3-ERR_DUPLICATE_IPV4_ADDRESS : TenGigE0/2/0/22.1.pppoe578: Subscriber IPv4 address 10.20.20.101 matches another route
But this is "wrong" because there are two routes with different AD so there is not a duplicate.
Moreover, the message is not very clear as the address (10.20.20.101) is unique but it is the route that would be duplicated if it were without AD.
What about the rule that different routes with different ADs do not conflict with each other is not supported in this case?
In other words: are floating static routes usable with Framed-Route radius parameter?
thankyou
Gianrico Fichera
