Network Move Upgrade 20082009 September 2008 Les Cottrell

Network Move & Upgrade 2008/2009: September 2008 Les Cottrell. SLAC for SCCS core services network group (Antonio Ceseracciu, Jared Greeno, Yee Ting Li, Gary Buhrmaster), Presented at the OU Admin Group Meeting Sept. 18, 2008 www. slac. stanford. edu/grp/scs/net/racks/netmove-sep 08. ppt

Move • Major project: – 20 racks of equipment to move to new racks, ~ 140 separate units, includes switches/routers, management, monitoring, security equipment, 200 VLANs, 4000 hosts – Have to connect up, configure etc, minimize outages – Hardest part is moving the switches with the building connections and moving/upgrading fibres • Will be some building outages in work hours • In many cases will be re-addressing (single subnet/switch) and periods of a few days with no redundancy • Needs coordination with: user groups, OU admins, networking, win admins, print server admins, unix-admins – Must complete move by April 1, 2009 (floor replace)

Benefits • auto speed/duplex (replace older switches) • enable higher speeds to desktop (1 Gbps with 10 GBps uplinks) • better problem isolation • utilize redundant links (double capacity) • isolate broadcasts (don’t go through core) • enable better security

Documentation • See “Seismic Retrofitting Rack Move 2008” site – https: //confluence. slac. stanford. edu/display/Net. Man/Seismic+Retrofitting+Rack +Move+2008 – Contains background information, overview of procedures, milestones, drill down to lots more details (tickets, spreadsheets, subnet allocations, hosts on individual switches etc. ) – This is where to go to get detailed information. It is very dynamic. – If you need more, let us know we will add as appropriate • Email to core-neteng • There is an FAQ at https: //confluence. slac. stanford. edu/display/Net. Man/Frequently+Asked+Questions

Current Status • Identified switches/buildings we are ready to move: – CGB 1, TL 1, WHS, B 267, CLA 1, CLA 2 • In process of moving CGB 1 (will be re-addressed) – Met with Building 50 OU admins to go into details & get feedback (Tues 16 Sep) – Justus 3 hosts (user=admin), pin down exact procedures, identifying coordination etc. needs (Wed) – Training room with Windows automation (Thurs) – Printers - coordinate with print server admins (Fri) – Others • Identifying where we need extra fibre (Fred Hooker)

Next steps • Update procedures, documentation based on initial moves. • Order fibre and install to add extra switches to upgrade • ID buildings where there will be a work hours outage so OU admins can work with users to alert & schedule outage • Buildings TL 1 (new switches), WHS, B 267, CLA – Will contact and meet with OU Admins for each building • Build and configure COREOLD (3&4) switches for: – – If a building cannot re-address Move to a temporary switch in seismically retrofitted location Then later re-address & move again to building switch Would like to avoid multiple outages, relocations, lack of backup periods

Switch upgrade procedure • The procedure for upgrading each building switch is: – net-eng chooses, creates and configures the new subnets (multiple/switch, e. g. public, printers, training rooms, equip controllers) – Meet with OU admins to explain, set expectations, learn about special needs/hosts • Will be a web accessible web page for each switch (e. g. https: //confluence. slac. stanford. edu/display/Net. Man/Building+050+Floor+1 ) – OU admins work with users on re-addressing hosts. Net-eng will be involved to change VLAN when an host is readdressed. – During this time, • Many switches will have no redundant uplinks, (because one uplink is used for the old subnets, one for the new ones). Therefore we need to keep the readdressing time as short as possible! (make sure resources are available & coordinated). – Net-eng clears the old subnets from the switch and enables redundant uplink