Solved

possible nclu bug with net add mpls ldp address-family ipv4 discovery transport-address


Hi All,

I'm trying out Cumulus VX 3.6.1 to see if it can do mpls with an IOS-XR VM.

While doing a commit of the following line, I get an error and after that nclu and frr.conf is out of sync and nclu thinks someone else edited frr.conf:

net add mpls ldp address-family ipv4 discovery transport-address 10.10.11.0
net pending
--- /run/nclu/frr//frr.conf.scratchpad.baseline 2018-06-07 16:50:08.541725099 +0000
+++ /run/nclu/frr//frr.conf.scratchpad 2018-06-07 16:50:08.541725099 +0000
@@ -1,12 +1,14 @@
frr version 4.0+cl3u2
frr defaults datacenter
hostname cumulus
username cumulus nopassword
service integrated-vtysh-config
mpls ldp
router-id 10.10.11.0
!
+ address-family ipv4
+ discovery transport-address 10.10.11.0
end
line vty

end


net add/del commands since the last "net commit"
================================================

User Timestamp Command
------- -------------------------- ---------------------------------------------------------------------------
cumulus 2018-06-07 16:50:08.544506 net add mpls ldp address-family ipv4 discovery transport-address 10.10.11.0


cumulus@cumulus:~$ net commit
--- /run/nclu/frr//frr.conf.scratchpad.baseline 2018-06-07 16:50:08.541725099 +0000
+++ /run/nclu/frr//frr.conf.scratchpad 2018-06-07 16:50:08.541725099 +0000
@@ -1,12 +1,14 @@
frr version 4.0+cl3u2
frr defaults datacenter
hostname cumulus
username cumulus nopassword
service integrated-vtysh-config
mpls ldp
router-id 10.10.11.0
!
+ address-family ipv4
+ discovery transport-address 10.10.11.0
end
line vty

end


net add/del commands since the last "net commit"
================================================

User Timestamp Command
------- -------------------------- ---------------------------------------------------------------------------
cumulus 2018-06-07 16:50:08.544506 net add mpls ldp address-family ipv4 discovery transport-address 10.10.11.0




/usr/lib/frr/frr-reload.py failed.
================================================================================
2018-06-07 16:50:33,506 INFO: Called via "Namespace(debug=False, filename='/etc/frr/frr.conf', input=None, overwrite=True, reload=True, stdout=True, test=False)"
2018-06-07 16:50:33,507 INFO: Loading Config object from file /etc/frr/frr.conf
2018-06-07 16:50:33,642 INFO: Loading Config object from vtysh show running
2018-06-07 16:50:33,779 INFO: /var/run/frr/reload-CE89WY.txt content
['\naddress-family ipv4',
'\naddress-family ipv4\n discovery transport-address 10.10.11.0']
2018-06-07 16:50:33,846 WARNING: frr-reload.py failed due to
line 2: % Unknown command[4]: address-family ipv4
line 4: % Unknown command[4]: address-family ipv4
line 5: % Unknown command[4]: discovery transport-address 10.10.11.0

2018-06-07 16:50:33,846 INFO: Loading Config object from vtysh show running
2018-06-07 16:50:33,982 INFO: /var/run/frr/reload-DRDRS5.txt content
['\naddress-family ipv4',
'\naddress-family ipv4\n discovery transport-address 10.10.11.0',
'\naddress-family ipv4',
'\naddress-family ipv4\n discovery transport-address 10.10.11.0']
2018-06-07 16:50:34,051 WARNING: frr-reload.py failed due to
line 2: % Unknown command[4]: address-family ipv4
line 4: % Unknown command[4]: address-family ipv4
line 5: % Unknown command[4]: discovery transport-address 10.10.11.0
line 7: % Unknown command[4]: address-family ipv4
line 9: % Unknown command[4]: address-family ipv4
line 10: % Unknown command[4]: discovery transport-address 10.10.11.0

Note: this version of vtysh never writes vtysh.conf
Building Configuration...
Integrated configuration saved to /etc/frr//frr.conf
[ok]

================================================================================



cumulus@cumulus:~$

Did I do something wrong? Is the only way to recover to do a "net del all" and "rm /etc/frr/frr.conf"?

Regards

John
icon

Best answer by Mark Horsfield 31 July 2018, 14:12

@John Hay
We do not support LDP for exchanging MPLS label information (as of Cumulus Linux 3.6). It is planned for a future release -- please contact us directly (through your sales team, or open a support case) to understand the use-case and prioritize the feature delivery (if desired).
View original

1 reply

Userlevel 1
@John Hay
We do not support LDP for exchanging MPLS label information (as of Cumulus Linux 3.6). It is planned for a future release -- please contact us directly (through your sales team, or open a support case) to understand the use-case and prioritize the feature delivery (if desired).

Reply