Migration Process and Strategies

migration process the migration process consists of the following 5 steps nsb bringup user/device segments and subnets firewall configuration nile portal settings device migration and validation nsb bringup to bring up the nile access service, administrators must complete the following tasks sign up for nile service create sites/buildings/floors and upload floor plans identify nsb and sensor subnet configure the uplink ip addresses provide the dns and ntp server list configure the uplink router or firewall or layer 3 switch firewall allow nsb and sensor subnets to communicate over https, dns and ntp user/device subnet and segments identify user subnets (e g , employee, guest, contractor, faculty, staff) identify device subnets (e g , printers, conference room systems, cameras) configure dhcp portals configure the radius server configure guest portals firewall configuration the firewall must be configured to allow or deny communication between users, devices, and external resources here's an example nile portal settings log in to the nile portal and set up the network please see the"settings" section, starting with setup dhcp docid\ yf0rq3chvx1tclbsyamv7 , for more details once this step is complete the network is fully up and devices can connect to the network provide dhcp server details provide radius server details create segments for users and devices create ssids setup up access management rules sign up for alerts validation verify users can authenticate, get an ip address, and pass traffic verify devices can authenticate, get an ip address, and pass traffic verify the firewall rules verify the nile sla’s verify that the infrastructure (dhcp/dns/radius/internet is being monitored by nile verify that alerts are generated and received migration strategies there a two options to migrate a brownfield deployment to the nile access service define new subnets migrate existing subnets phased migration yes no downtime no yes leverage existing firewall rule no yes leverage existing dhcp scopes no yes defining new subnets this strategy can be adopted when customers want to bring up the nile access service in parallel with their existing network and perform a phased migration of the devices the migration can be done building by building without disrupting the existing network this approach requires creating brand new subnets for existing devices as shown in the diagram, all laptops will migrate from vlan 1 to segment 1, cameras from vlan 2 to segment 2, and printers from vlan 3 to segment 3 migrating existing subnets this strategy requires removing vlans from the existing infrastructure and leveraging the subnets on the nile infrastructure this strategy is best when the entire site can be migrated during a maintenance window the primary advantage is that all devices can be migrated in one go as seen in the above diagram the old network is decommissioned and the vlan l3 svi's are migrated from the old infrastructure to nile