Configuring routes per EVS
Multi-tenancy causes the routing engine to keep routes by EVS, so it is necessary to maintain different sets of routes for each EVS. Gateway, network and host routes (IPv4 and IPv6) are configured per EVS when multi-tenancy is enabled using the following commands: route-gateway-add, route-net-add, and route-host-add.
Configuration is done with the EVS in context. Prefix lengths are accepted for IPv4 and IPv6 network addresses.
Command examples:
hnas:$ evs-select 1 hnas[EVS01]:$ route-gateway-add fdca:f995:220a:a00::1 Route cache flushed. hnas[EVS01]:$ evs-select 2 hnas[EVS02]:$ route-net-add 10.2.0.0/16 -g 10.1.2.3 -m 9000 Route cache flushed. hnas[EVS02]:$ evs-select 3 hnas[EVS03]:$ route-host-add 10.1.2.3 -g 10.1.3.4 Route cache flushed.
The route command is display only when multi-tenancy is enabled. The route command displays routes for the EVS in context.
[EVS01]:$ route Routes for EVS 1: Destination Gateway MTU Flags ::/0 fdca:f995:220a:a00::1 Default G ::/0 fe80::208:e3ff:feff:fc28 1500 GD via eth0 ::/0 fe80::208:e3ff:feff:fc28 1500 GD via ag1
[EVS02]:$ route Routes for EVS 2: Destination Gateway MTU Flags 10.2.0.0/16 10.1.2.3 9000 ::/0 fe80::208:e3ff:feff:fc28 1500 GD via eth0 ::/0 fe80::208:e3ff:feff:fc28 1500 GD via ag1
The route command will redirect the user to the route commands for configuration when multi-tenancy is enabled.
[Tenant2-EVS2]:$ route add gateway route: as multi-tenancy is enabled, use route-gateway-add [Tenant2-EVS2]:$ route add host route: as multi-tenancy is enabled, use route-host-add [Tenant2-EVS2]:$ route add net route: as multi-tenancy is enabled, use route-net-add
The commands
router-dump-by-evs and
test-route-by-evs can be used to diagnose networking problems, where routes are configured per EVS.
