Re: logging, DANOS mounts a permanent /var/log at boot (I think it's shared by all images). If any work on logging is going to be done, /var/log should be mounted before any vyos config migration or load is done so it can be used as the destination for logging.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Apr 6 2020
Note, there is /opt/vyatta/etc/config/vyos-migrate.log (/config/vyos-migrate.log after image installation) that will list failed migration scripts, if any). This is created before /var/log is available, hence the non-canonical location.
Regarding the first question, yes, cfg-stdout.log is cleared on reboot, unfortunately. The commit error logging is currently a mixture of (un-verbose) reporting from the backend, and limited reporting from python; improvements pending. Firstly, if there are migration errors, those need to be investigated; secondly, the error that you initially reported is (generally) related to stale information in the config hierarchy itself, but may be obscuring earlier errors.
If you comment out this line, arp after reboot doesn't lose.
I couldn't find anything in /var/log/vyatta the last few times I've ran into boot-time commit errors. It seems like the python code doesn't log commit errors into a file or syslog, or at least I couldn't find it. I had to log into the console, go into config mode, load the config (usually pre-migration when there are migrator script errors) and commit it, then the errors are printed to the console. Someone can correct me if I'm wrong.
Latest rolling.
[email protected]:~$ poweroff in 5 Poweroff is scheduled 2020-04-06 12:02:52 [email protected]:~$
I think we can close this task
@dongjunbo Can you send an example?
Commands were rewritten to:
$ reset ip igmp interfaces $ reset ip multicast route
@c-po the second part of task.
An example, we can't execute analog of this command in the VyOS syntax:
sudo ip link add vxlan11 type vxlan id 11 dstport 8472 local 22.22.22.1 nolearning
We need to add commands for vxlan:
Does this get cleared on each reboot? Because I usually rebooted after it "locked".
Apr 5 2020
Pull request: https://github.com/vyos/vyos-1x/pull/306
In this failure case, there are some expected "failed" lines in /var/log/vyatta/cfg-stdout.log. Although they are not detailed log messages, they may help narrow down the source of the failure, if you could share those.
Thanks a lot!
I also connected ldp neighbor.
Pull request: https://github.com/vyos/vyos-1x/pull/305
I was not able to recreate that issue. Both /24 and /8 networks were tested.
All the tests have been done on the VyOS 1.3-rolling-202004020117.
vyos@R7# run show configuration commands | match "mpls|address|ospf" set interfaces dummy dum0 address '1.1.1.1/32' set interfaces ethernet eth1 address '10.0.0.1/24' set protocols mpls ldp discovery transport-ipv4-address '1.1.1.1' set protocols mpls ldp interface 'eth1' set protocols mpls ldp router-id '1.1.1.1' set protocols ospf area 0 network '0.0.0.0/0' set protocols ospf parameters abr-type 'cisco' set protocols ospf parameters router-id '1.1.1.1'
set interfaces dummy dum0 address '2.2.2.2/32' set interfaces ethernet eth1 address '10.0.0.2/24' set interfaces ethernet eth2 address '10.0.255.1/24' set protocols mpls ldp discovery transport-ipv4-address '2.2.2.2' set protocols mpls ldp interface 'eth1' set protocols mpls ldp interface 'eth2' set protocols mpls ldp router-id '2.2.2.2' set protocols ospf area 0 network '0.0.0.0/0' set protocols ospf parameters abr-type 'cisco' set protocols ospf parameters router-id '2.2.2.2'
set interfaces dummy dum0 address '3.3.3.3/32' set interfaces ethernet eth1 address '10.0.255.2/24' set protocols mpls ldp discovery transport-ipv4-address '3.3.3.3' set protocols mpls ldp interface 'eth1' set protocols mpls ldp router-id '3.3.3.3' set protocols ospf area 0 network '0.0.0.0/0' set protocols ospf parameters abr-type 'cisco' set protocols ospf parameters router-id '3.3.3.3'
hi,
Please show router configurations, VyOS_R7, VyOS_R8, VyPS_R9.
I tried mpls configuration as your sample, but I could not establish ldp neighbor.