Deployment Guide

Table Of Contents
20/0 00:13:49
via 10.10.0.2
B EX 10.1.0.1/32 via 10.10.0.1
20/0 00:14:22
via 10.10.0.2
B EX 10.1.0.2/32 via 10.10.0.1
20/0 00:14:24
via 10.10.0.2
C 10.10.0.0/24 via 10.10.0.3 vlan100
0/0 00:23:16
B EX 172.16.1.1/32 via 10.10.0.1
20/0 00:22:58
via 10.10.0.2
B EX 172.16.1.2/32 via 10.10.0.1
20/0 00:22:58
via 10.10.0.2
B EX 172.16.1.3/32 via 10.10.0.1
20/0 00:22:58
via 10.10.0.2
B EX 172.16.1.4/32 via 10.10.0.1
20/0 00:22:58
via 10.10.0.2
B EX 172.16.1.201/32 via 10.10.0.1
20/0 00:22:58
via 10.10.0.2
B EX 172.16.1.202/32 via 10.10.0.1
20/0 00:22:58
via 10.10.0.2
B EX 192.168.0.1/32 via 10.10.0.1
20/0 00:22:58
via 10.10.0.2
B EX 192.168.0.2/32 via 10.10.0.1
20/0 00:22:58
via 10.10.0.2
B EX 192.168.2.0/31 via 10.10.0.1
20/0 00:14:11
via 10.10.0.2
B EX 192.168.2.2/31 via 10.10.0.1
20/0 00:14:11
via 10.10.0.2
B EX 192.168.2.4/31 via 10.10.0.1
20/0 00:13:49
via 10.10.0.2
B EX 192.168.2.6/31 via 10.10.0.1
20/0 00:13:49
via 10.10.0.2
B EX 192.168.2.240/31 via 10.10.0.1
20/0 00:14:11
via 10.10.0.2
Example: Migrating from Asymmetric IRB to Symmetric IRB
Until Release 10.5.0, OS10 provided support only for the Asymmetric IRB mode. Starting from Release 10.5.1, OS10 supports the
Symmetric IRB mode. Symmetric IRB mode efficiently uses next hop tables in the NPU. If there are no local hosts, Symmetric
IRB mode does not require creation of destination VNI in the local VTEP. You can migrate your network from Asymmetric IRB
mode to Symmetric IRB mode. For a seamless migration with less or no downtime in the VLT environment, perform the following
steps:
NOTE:
Before you start this migration, all leaf nodes acting as VTEPs in the Clos network must be upgraded to 10.5.1.x.
If there are overlay hosts in default VRF, migration to Symmetric IRB mode is not supported because Symmetric IRB
mode cannot be used in default VRF.
VXLAN 155