vyos-1x.git/src/migration-scripts/quagga, branch yevhenVyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)
https://git.amelek.net/vyos/vyos-1x.git/atom?h=yevhen2024-06-26T20:38:41+00:00migration: T6007: convert all migration scripts to load as module2024-06-26T20:38:41+00:00John Estabrookjestabro@vyos.io2024-06-20T01:16:05+00:00urn:sha1:26740a8d583f64dc0a27b59dd4ae303056972c0bT5427: Fix migration script arguments len expects 2 args2023-08-02T09:12:23+00:00Viacheslav Hletenkov.gletenko@vyos.io2023-08-02T09:12:23+00:00urn:sha1:d1923b7b58795f0d9635ae0e8df110f591881bdf
The script's name is always provided as the first argument sys.argv[0]
Expected length for argv is 2 (script itself + config file)
Change: 'if (len(argv) < 1)' to 'if len(argv) < 2'
T5150: migrate CLI configs to new Kernel/Zebra route-map support2023-04-13T07:01:31+00:00Christian Breunigchristian@breunig.cc2023-04-12T19:11:50+00:00urn:sha1:7d642a2862dcd0c7c2f80ac42ea9427970804d06policy: T4414: add support for route-map "as-path prepend last-as x"2022-05-05T16:45:17+00:00Christian Poessingerchristian@poessinger.com2022-05-05T16:44:01+00:00urn:sha1:799b7f511248d68bbbe05e0dfd2aa4849fc32387migration: T548: Rename quagga scripts for correct seq2021-08-06T11:56:00+00:00Viacheslavv.gletenko@vyos.io2021-08-06T11:55:45+00:00urn:sha1:4ae22dd44fd480ef4fc2e71c6f2eb00750a22fa4
Rename quagga migration scripts for correct sequences
between 1.3 and 1.4 branches
7-to-8 in 1.3 uses the same migration as 8-to-9 in 1.4
This PR fix it
vrf: route: static: T2450: we also need to migrate the interface based routes2021-07-12T16:38:41+00:00Christian Poessingerchristian@poessinger.com2021-07-12T16:38:14+00:00urn:sha1:73e58b7d000c92608b263f2f52b60d21d741db04
Previously during migration if one had used interface routes, the VRF based
ones got not migrated.
The following "old" VyOS 1.3 configuration did not get migrated:
set protocols static interface-route 10.20.0.0/24 next-hop-interface eth2 next-hop-vrf 'blue'
set protocols static interface-route 10.30.0.0/24 next-hop-interface br10 next-hop-vrf 'red'
set protocols vrf blue static interface-route 10.0.0.0/24 next-hop-interface eth1 next-hop-vrf 'default'
set protocols vrf red static interface-route 10.0.0.0/24 next-hop-interface eth1 next-hop-vrf 'default'
set vrf name blue table '3000'
set vrf name mgmt table '1000'
set vrf name red table '2000'
It must get migrated to:
set protocols static route 10.20.0.0/24 interface eth2 vrf 'blue'
set protocols static route 10.30.0.0/24 interface br10 vrf 'red'
set vrf name blue protocols static route 10.0.0.0/24 interface eth1 vrf 'default'
set vrf name blue table '3000'
set vrf name mgmt table '1000'
set vrf name red protocols static route 10.0.0.0/24 interface eth1 vrf 'default'
set vrf name red table '2000'
bgp: T3391: migrate old IPv4 only maximum-paths config to new syntax2021-03-08T18:38:11+00:00Christian Poessingerchristian@poessinger.com2021-03-08T18:38:11+00:00urn:sha1:ab6ef466c128ba48f85b13ba8d4be1476e844726bgp: T3311: remove remote-as from address-family2021-02-15T16:23:33+00:00Christian Poessingerchristian@poessinger.com2021-02-15T16:23:33+00:00urn:sha1:dd291b2312f0fca49ae8ad6876e280bc46f45d2e
When moving from Quagga to FRR the BGP address-family was extended by an
invalid peer-group statement. FRR always moved a configured peer-group
from the AFI level down to the neighbor level.
With the migration to FRR reload we must take care about this by ourselves.
bgp: T2844: add IPv4 disable-send-community support2021-02-14T12:03:34+00:00Christian Poessingerchristian@poessinger.com2021-02-14T11:46:49+00:00urn:sha1:5868cbeba1bd9a4c3daaad7aa81af5c45e00cd16route: static: T2450: provide full protocol support in XML and Python with new CLI2021-02-05T21:42:29+00:00Christian Poessingerchristian@poessinger.com2021-02-04T18:35:18+00:00urn:sha1:1f8c257f126d492a3f41eee72728b2c35b6b534e