Change Details

It has been decided that codfw rack A1 should be a "network" rack, containing core network devices like cr1-codfw and ssw1-a1-codfw, but not containing any servers. As such we do not need a 'leaf' switch in this rack, so the plan is to decom //lsw1-a1-codfw// and re-use this device for the upcoming codfw row c/d upgrade as //lsw1-d1-codfw//. At a high level I believe we need to do the following: [] Remove lsw1-a1-codfw from monitoring [] Remove configuration of lsw1-a1-codfw spine uplinks and ports [] Remove all references to private1-a1-codfw vlan and networks from netbox [] Remove all references to private1-a1-codfw vlan from puppet (including lvs sub-interfaces) [] Rename lsw1-a1-codfw to lsw1-d1-codfw in netbox, and push name change to device with homer [] Set lsw1-d1-codfw to 'planned' status in netbox [] Remove all physical cabling from lsw1-a1-codfw, and optics from both sides of any links [] Move to rack d1 and connect to mgmt network At this point the device should be ready to have new configuration elements (interfaces, IPs etc.) added for its new life in the other rack.

It has been decided that codfw rack A1 should be a "network" rack, containing core network devices like cr1-codfw and ssw1-a1-codfw, but not containing any servers. As such we do not need a 'leaf' switch in this rack, so the plan is to decom //lsw1-a1-codfw// and re-use this device for the upcoming codfw row c/d upgrade as //lsw1-d1-codfw//. At a high level I believe we need to do the following: [] Remove lsw1-a1-codfw from monitoring [] Remove lsw1-a1-codfw from route-reflector config in codfw [] Remove configuration from ssw1-a1-codfw and ssw1-a8-codfw ports connecting to lsw1-a1-codfw in Netbox [] Push updated config to ssw1-a1-codfw and ssw1-a8-codfw to remove BGP peerings, OSPF and interfaces [] Remove configuration of lsw1-a1-codfw interfaces (apart from em0) in Netbox [] Push updated config to lsw1-a1-codfw to remove it's ssw uplink config, BGP peerings etc. [] Remove all references to private1-a1-codfw vlan and networks from netbox [] Remove all references to private1-a1-codfw vlan from puppet (including lvs sub-interfaces) [] Rename lsw1-a1-codfw to lsw1-d1-codfw in netbox (and change mgmt dns name) [] Manually change device hostname on device [] Set lsw1-d1-codfw to 'planned' status in netbox [] Remove all physical cabling from lsw1-a1-codfw, and optics from both sides of any links [] Move to rack d1 and connect to mgmt network At this point the device should be ready to have new configuration elements (interfaces, IPs etc.) added for its new life in the other rack.

It has been decided that codfw rack A1 should be a "network" rack, containing core network devices like cr1-codfw and ssw1-a1-codfw, but not containing any servers. As such we do not need a 'leaf' switch in this rack, so the plan is to decom //lsw1-a1-codfw// and re-use this device for the upcoming codfw row c/d upgrade as //lsw1-d1-codfw//. At a high level I believe we need to do the following: [] Remove lsw1-a1-codfw from monitoring [] Remove configuration of lsw1-a1-codfw spine uplinks and portslsw1-a1-codfw from route-reflector config in codfw [] Remove configuration from ssw1-a1-codfw and ssw1-a8-codfw ports connecting to lsw1-a1-codfw in Netbox [] Push updated config to ssw1-a1-codfw and ssw1-a8-codfw to remove BGP peerings, OSPF and interfaces [] Remove configuration of lsw1-a1-codfw interfaces (apart from em0) in Netbox [] Push updated config to lsw1-a1-codfw to remove it's ssw uplink config, BGP peerings etc. [] Remove all references to private1-a1-codfw vlan and networks from netbox [] Remove all references to private1-a1-codfw vlan from puppet (including lvs sub-interfaces) [] Rename lsw1-a1-codfw to lsw1-d1-codfw in netbox, and push (and change mgmt dns name) [] Manually change to device with homerhostname on device [] Set lsw1-d1-codfw to 'planned' status in netbox [] Remove all physical cabling from lsw1-a1-codfw, and optics from both sides of any links [] Move to rack d1 and connect to mgmt network At this point the device should be ready to have new configuration elements (interfaces, IPs etc.) added for its new life in the other rack.