- User Since
- May 17 2020, 10:37 AM (36 w, 3 d)
Tested on VyOS 1.4-rolling-202101261956. Works fine
Tue, Jan 19
Looks good. But maybe it is reasonable to change argument start-suppress-time to start-suppress because it is not a time, but penalty points
Sat, Jan 16
If I use
Wed, Jan 13
Tue, Jan 12
Mon, Jan 11
I have just re-checked. It works fine for everyone LSAs type.
summary and asbr-summary also works fine
It works fine for show ip ospf database router x.x.x.x and show ip ospf database network x.x.x.x
It does not work for show ip ospf database <summary|asbr-summary|external> x.x.x.x
The output of these commands is empty.
Sun, Jan 10
Ok. I'll do it
FRR value for the same command
Sat, Jan 9
Fri, Jan 8
Oct 26 2020
Can you add this commands
Aug 21 2020
Aug 19 2020
@Viacheslav what about abnormal label allocation behavior which I wrote earlier? Was it fixed?
May 18 2020
I found abnormal behavior during label allocation. As I wrote above VyOS generate label for all prefixes presented in routing table. But when we have for example 5 connected routes (four /24 and one /32) on Egress LSR and we start mpls VyOS allocates labels for all routes and neighbor (downstream LSR) receives label=3 (implicit null). But if we have 2 connected routes (one /24 and one /32) then we start mpls, Egress LSR allocates labels for all routes (two in this case), but if we add on Egress LSR one, two or more new connected routes VyOS does not allocate label=3 for this routes and does not send Label Mapping Message to its neighbors for FECs related to new added routes. The software version is 1.3-rolling-202005160117
May 17 2020
As I understood from my lab VyOS generate label in cisco fashion (for all presented prefixes in routing table). And it is good as for me. But I think it is necessary to be able to filter the FEC for which labels will be generated (for example only for /32 routes, or only for particular routes).