VSR static-route bug

[brncoguz]

Hi,

I'm trying to deploy a vsr, sysinfo tag inside the xml template looks like this:

  <sysinfo type='smbios'>
    <system>
      <entry name='product'>TIMOS:slot=A chassis=VSR-I card=cpm-v mda/1=m20-v address=10.52.100.15/24@active static-route=0.0.0.0/1@10.52.100.1 static-route=128.0.0.0/1@10.52.100.1 license-file=cf3:/license.txt</entry>
    </system>
  </sysinfo>

The problem here is, vsr doesn't accept this entry "static-route=0.0.0.0/1@10.52.100.1", when i try to add it manually from bof it's okay. It seems like a bug.

Maybe we can use a bof.cfg template to get over this problem.

[jonasvermeulen]

As much as possible vsr-deploy and vsr-predeploy relies on dynamic configuration changes. Effectively making it ready for evolution to NetConf usage.

The issue with pushing code dynamically is that the node needs to be reachable after its first boot. So a minimum static route is required in the XML so that the deployment host can actually push configuration changes after.
If there are issues, it might make sense though to copy a bof.cfg into the qcow via guestfish before bootup.

[brncoguz]

@jonasvermeulen as you mentioned most of the project probably uses a minimum static route, but in our pods we usually use static-route=0.0.0.0/1@<next-hop> static-route=128.0.0.0/1@<next-hop> to make it reachable to every subnet, that's how i faced this issue. I'll try to change it so we can copy bof.cfg file before booting up the vm.

@oakyurek can you comment on this request?