You can comment in the sections. it only creates an error when deleting vrf bgp instances
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Aug 12 2021
Waiting on 3rd party fix: https://github.com/FRRouting/frr/issues/9384
https://github.com/vyos/vyos-1x/pull/965
Another bug.
From time to time I get errors in debug mode ("touch /tmp/vyos.frr.debug" and "sudo systemctl stop vyos-configd") when changing lsp-mtu size
vyos@r1-roll# set protocols isis lsp-mtu 1308 [edit] vyos@r1-roll# commit [ protocols isis ]
We have this problem in more then one case. The solution so gar is to use " as quote which we later on render in Jinja2
Sounds like a missing validator. Wo should prevent users from doing such things ;)
@Viacheslav, when we use a migrator we should enable the ipv4 afi for each and every ipv4 neighbor if its not configured explicitly. What do you think? If a peer group is configured for that neighbour, too - that will be no issue.
Aug 11 2021
Thanks for you comment ! it's good consider that options
Similar task T2315, also there is bug related T1976, etc.
It should be a migration script that determines ip/ipv6 neighbor and set neighbor to properly afi.
So there is one question, how to determine which afi we should to use if we see "peer-group" in configuration?
I don't think that we can implement it in 1.3 as it uses an old codebase.
This will be merged, pending discussion on pros/cons of preprocessing vs. relaxing schema restriction.
Gotcha. Thanks. Will wait.
Hi @paunadeu yeah that is an open issue (https://github.com/vyos/vyos-1x/commit/d77709252de54757d3f3e76ce6c52492ba967488) it got disabled recently.
OK. Seeing VyOS output now:
I think wasn't a problem. Not defined VNI in VRF, in L3 respects config in L2 don't, asked for the behavior in FRR Slack.
@raphielscape Are there still problems after updating PR? Please provide the configuration and I'll take the time to check it
As Workaround in T3350 set raw option "config /path/to/config/file"
@fernando Thanks.
Aug 10 2021
i've been testing this new feature in our last release and it works well :
A bit of background: the error here is is a result of the Relax-NG schema requiring a leaf node to have a 'properties' entry; that is considered a sanity check by the schema author, but emerges as an issue when we moved to a modular structure for the *.xml.i include files. Leaving that restriction as-is, the solution of merging leaf nodes in the lxml script should be straightforward (the general case more intricate), so I will look at amending the override-default script.
Sure ! i'll test this feature and let you know !
@fernando Can you check this feature in the next rolling release?
set service snmp community public client 127.0.0.1 set service snmp oid-enable route-table
Aug 9 2021
PR for Equuleus https://github.com/vyos/vyos-1x/pull/959
Need to implement in customer, if I can help in something, please don't hesitate to ask.
Maybe with FRR 8.1
In any case, we'll do more tests.
It's upgrade on FRR planned?
In T3728#99683, @Viacheslav wrote:It is possible this bug.
https://github.com/FRRouting/frr/issues/9181
It is possible this bug.
https://github.com/FRRouting/frr/issues/9181
Take a look to:
PR for 1.3 https://github.com/vyos/vyos-1x/pull/957
Aug 8 2021
>>> from vyos.config import Config
>>> conf = Config()
>>> conf.get_config_dict(['service', 'ssh'])
{'ssh': {'disable-host-validation': {}, 'port': ['22']}}
>>> conf.get_config_dict(['service', 'non-existing'])
{}Aug 7 2021
Did more checks.....and noticed it *IS* properly sending the ping command:
It's not a bug, it's simply a weird syntax. That command could never be used without the delete option, so your config example wouldn't work in 1.2 or 1.1.8 either.