VSC static route nexthop is wrong

[jbemmel]

https://github.com/nuagenetworks/nuage-metro/blob/master/roles/vsc-deploy/templates/config.cfg.j2

Next hop should be control IP of each peer, if in same subnet

Instead of /32 static routes, it's better to peer on control IP and add a default route only

[ghost]

The existing line is:

        static-route {{ hostvars[vsc_item].system_ip }}/32 next-hop {{ vsc_control_ip }}

I think you are suggesting that we drop this line and, instead, add do two things?

1. Peer on control IP (How do we do this?)
2. Create a default route (How do we do this?)

[jbemmel]

Yes, the logic to peer using control IP is already there, only system IP is currently preferred. Default route is 0.0.0.0/0 next-hop { control_net_gw }

…

On Sat, Mar 10, 2018 at 8:38 PM, Brian Castelli ***@***.***> wrote: The existing line is: static-route {{ hostvars[vsc_item].system_ip }}/32 next-hop {{ vsc_control_ip }} I think you are suggesting that we drop this line and, instead, add do two things? 1. Peer on control IP (How do we do this?) 2. Create a default route (How do we do this?) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#575 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB8AC-OTViGiJoAec1A-p9RCPQYhXLfgks5tdI4PgaJpZM4SlVvb> .

[ghost]

@jbemmel I'm trying to understand how to fix this issue. In one place, you wrote that the next hop should be the control ip of each peer. In another, you said it should be the control_network_gw. We do not collect the control_network_gw in build vars. What exactly is the fix here?

[jbemmel]

The way I would configure it, is a single static default route to the control network gateway if available- if the vscs are all in a single subnet and you are not connecting to dcgws, then you could also leave the static route out. The control interface ips should be used as bgp neighbors, not as the static route next hop