Hi, I need help in understanding the completed steps involved in an office move from one location to other.
1. Service provider will provide last mile connectivity to the new office.
2. LAN cabling will be done by 3rd party vendor
3. New cisco equipment(router and switches) will be ordered and placed in racks.
4. Servers (mail/web/application) will need to be re-located from old place to new one. This will be done at what point? I presume, over the weekend once the new network connectivity is confirmed and router and switches are configured.
1) This is usually what dictates the timescales for the rest of the move. You need to talk to your SP as soon as possible as they may need to do site surveys etc. and there is always a lead time. Last position i had was at Network Rail and some of the places we had to connect up took ages simply because of their remote location.
2) Yes. Make sure you are absolutely clear on how you want the patch panels set up as this can make the difference between easy and not so easy maintenance in the future.
2a) Do not forget about power to the racks and if needed redundant power supplies. Make sure you provide enough power to the racks for the current equipment but also try to think of future requirements. An example would be where you are not running VOIP currently. You may move into the new office and then decided 6 months down the line you want to run VOIP. You may then need to upgrade the power supplies to your racks. Better to get the right ones in now if you can see requirements coming down the line.
3) Yes, and you would want them all powered up, tested before moving any servers/desktop in there. Also you need to connect to the WAN so you are dependant on 1) above.
4) This is done when you have a fully functioning LAN room with WAN connectivity. If you were provisioning new servers then you could overlap with some of the above but if you are moving existing servers you will need to have the network up and running beforehand.
You don't need to complete them all in a weekend unless you only have access to the new building 2 days before you go live. Everything other than step 4 should have been done before the weekend of the move. Trust me, there are always a few surprises when you start moving servers/clients into a new building.
If timescales are really tight, get 2 and 2a done before the weekend. Arrange to have the last mile connected up at the start of the weekend. And then 3 & 4 could be done over the weekend. But i would strongly recommend against this approach as there is little room for error.
I have assumed as it is an office environment that there are not huge amounts of servers etc. Also i've made the assumption that you don't have a huge amount of networked printers etc.
Finally, a lot depends on the importance of the work this office does. If outages loose a lot of money or are safety critical etc. you may need to take extra steps.
With one of the moves i was involved with we would never have been able to do it over a weekend, we had multiple WAN connections, mainframe connectivity etc. So we temporarily setup a bridged connection between the old site and the new site so we could move in phased stages. I'm not saying this is what you should do but be aware there are always other alternatives.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...