This is still a problem with vyos 1.2.0-rc2.

After a reboot now the config misses the BGP config. Loading it and trying commit shows the following:
Warning: connecting to bgpd...failed!
bgpd is not running

@c-po i saved the working complete config to a file, and when loading this after reboot with a lot missing, not a single error message is shown besides: boot-config-loader: Commit failed at boot

At that location only a couple of pre-migration configs exist. In archive subfolder also only old files exist.
But i loaded the latest pre-migration script, this causes all BGP configuration to be removed by the commit.
The error message is:
% Specify remote-as or peer-group commands first

Trying to reproduce it by doing a reboot with a working BGP config i now have lost during the reboot all interface and firewall configuration.
But the BGP config is now present and loaded.
:-(

That would be very nice to be able to use.
I just tested the rolling image and when i try to start bgpd with this module loaded it cannot find it.

I found this to occur sometimes when you configure the same subnet on multiple interfaces. The IPv4 seems to be OK in your config but the IPv6 is hidden and missing the last digit as well.
Also maybe you have created some strange behaving rule in NAT, if you have NAT configured could you post this config, or run through it yourself?

I believe i found the cause in the following issue on FRRouting
https://github.com/FRRouting/frr/issues/1440

My impression was that is was related to the adding of ipv6-next-hop to a route-map.
But without the IPv6 static routes the config commits fine.
When adding the first IPv6 static route the error is shown.

I also tested it on latest rolling and it is not working. It however does change something because when i enable it i can no longer ping from the Vyos router to the gateway.

RFC compatibility settings prevents VRRP from working on Hyper-V because of promiscuous on NICs
Without the RFC compatibility this is working fine.

Option 2 seems best. VRRP version does not need a setting, use VRRP V2 when no vrrp6 block is present for backward compatibility. Use VRRP v3 when it is.

Tested on 1.2.0-rolling

I am running several Vyos instances on Hyper-V and can confirm that 1.1.7 and 1.1.8 are running without issues.
For memory we use 512MB and never have any issues.

The current Quagga included is rather old, so if it is possible to migrate to FRR that would make a big difference.
I am testing my configs in the alpha release and so far it looks good. To assist i can test setups and configs.

It seems this is a bug in FRR 3.0
https://github.com/FRRouting/frr/issues/509

@syncer @dmbaturin
I found the following discussion on Cisco forum very explainable
https://supportforums.cisco.com/discussion/11476526/when-use-bgp-address-family

I manually added the file from Diffusion and this works, but i do not know how to fix this in the source :-)
https://phabricator.vyos.net/diffusion/2/browse/master/scripts/ssh-server-key;970ff0cfe393ccfa63d1f875483f3df7543d6c62

At this moment i am not running the nightly build so i cannot get this information for you. In a week or so i can change it to nightly build and let it run.

I checked a couple of routers and every router without IPSec configured has this error, but every router with IPSec configured had this file so no errors.

I noticed that both routers having the SNMP issues are the VRRP masters. I switches VRRP to Backup en rebooted the routers. SNMP daemon seems stable at this moment.

@rps this distinction also seems to be easy in the original proposed solution by @dmbaturin because key value pairs are not followed by '{' and the rest is.

@dmbaturin I understand that the discussion is "unit 0" vs "unit { 0", what i meant was that i could be an option to keep following the JunOS style as much as possible to maybe enable more interoperability.

Well plain JSON would also be an option then :-)

In the blog post #7 i liked the address [ 192.168.2.1/24 10.10.10.1/30 ]; part. But since i work most of the time with mixed JunOS and Vyos environments a mostly the same syntax would be very nice :-)
However JunOS would be:

A pro for me would be that i can do 'edit interfaces ethernet eth0 vif' and work with all virtual interfaces.

In JunOS the root user enters in the shell and uses 'cli' to enter show mode followed by configure for config mode.
When i add an extra user without shell access, this user is placed directly into show mode.
The vyos user is not the root user, so the way it currently is makes perfect sense to me.

These are the details of the router with issues:

1. ROUTER2:~$ show hardware cpu
2. Architecture: x86_64
3. CPU op-mode(s): 32-bit, 64-bit
4. CPU(s): 4
5. Thread(s) per core: 1
6. Core(s) per socket: 4
7. CPU socket(s): 1
8. NUMA node(s): 1
9. Vendor ID: GenuineIntel
10. CPU family: 6
11. Model: 30
12. Stepping: 5
13. CPU MHz: 2393.940
14. Virtualization: VT-x
15. L1d cache: 32K
16. L1i cache: 32K
17. L2 cache: 256K
18. L3 cache: 8192K
19. ROUTER2:~$ show hardware dmi
20. bios_date: 09/10/2013
21. bios_vendor: Dell Inc.
22. bios_version: 1.10.0
23. board_asset_tag:
24. board_name: 05KX61
25. board_vendor: Dell Inc.
26. board_version: A02
27. chassis_asset_tag:
28. chassis_type: 23
29. chassis_vendor: Dell Inc.
30. chassis_version:
31. product_name: PowerEdge R210
32. product_version:
33. sys_vendor: Dell Inc.
34. ROUTER2:~$ show hardware pci
35. 00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11)
36. 00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 1 (rev 11)
37. 00:08.0 System peripheral: Intel Corporation Core Processor System Management Registers (rev 11)
38. 00:08.1 System peripheral: Intel Corporation Core Processor Semaphore and Scratchpad Registers (rev 11)
39. 00:08.2 System peripheral: Intel Corporation Core Processor System Control and Status Registers (rev 11)
40. 00:08.3 System peripheral: Intel Corporation Core Processor Miscellaneous Registers (rev 11)
41. 00:10.0 System peripheral: Intel Corporation Core Processor QPI Link (rev 11)
42. 00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing and Protocol Registers (rev 11)
43. 00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
44. 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05)
45. 00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
46. 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a5)
47. 00:1f.0 ISA bridge: Intel Corporation 3400 Series Chipset LPC Interface Controller (rev 05)
48. 00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller (rev 05)
49. 01:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
50. 01:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
51. 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5716 Gigabit Ethernet (rev 20)
52. 02:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5716 Gigabit Ethernet (rev 20)
53. 03:03.0 VGA compatible controller: Matrox Graphics, Inc. MGA G200eW WPCM450 (rev 0a)
54. ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-Core Registers (rev 04)
55. ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 04)
56. ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 04)
57. ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 04)
58. ff:03.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller (rev 04)
59. ff:03.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Target Address Decoder (rev 04)
60. ff:03.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Test Registers (rev 04)
61. ff:03.4 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Test Registers (rev 04)
62. ff:04.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Control Registers (rev 04)
63. ff:04.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Address Registers (rev 04)
64. ff:04.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Rank Registers (rev 04)
65. ff:04.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Thermal Control Registers (rev 04)
66. ff:05.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Control Registers (rev 04)
67. ff:05.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Address Registers (rev 04)
68. ff:05.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Rank Registers (rev 04)
69. ff:05.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Thermal Control Registers (rev 04)
70. ROUTER2:~$ show hardware scsi
71. [0:0:0:0] disk ATA SAMSUNG HD501LJ CR10 /dev/sda
72. [1:0:0:0] disk ATA SAMSUNG HD501LJ CR10 /dev/sdb
73. [3:0:0:0] cd/dvd TEAC DVD-ROM DV-28SW R.2A /dev/sr0
74. ROUTER2:~$ show hardware usb
75. Bus 002 Device 005: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
76. Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
77. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
78. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
79. ROUTER2:~$ show system routing-daemons
80. zebra ripd ripngd ospfd ospf6d bgpd #
81. ROUTER2:~$ show system image
82. The system currently has the following image(s) installed:
83. 1: VyOS-1.1.7 (default boot) (running image) #
84. ROUTER2:~$ show version all
85. Version: VyOS 1.1.7
86. Description: VyOS 1.1.7 (helium)
87. Copyright: 2016 VyOS maintainers and contributors
88. Built by: [email protected]
89. Built on: Wed Feb 17 09:57:31 UTC 2016
90. Build ID: 1602170957-4459750
91. System type: x86 64-bit
92. Boot via: image
93. HW model: PowerEdge R210
94. HW S/N: 507645J
95. HW UUID: 44454C4C-3000-1037-8036-B5C04F34354A

The configs on all the routers are roughly the same, the SNMP config is completely the same.
I will collect the hardware details.