Solved

Switching from an old network service provider to a new network service provider

Posted on 2011-02-18
7
339 Views
Last Modified: 2012-05-11
Have a question, my company is switching over from an old network service provider Verizon to ATT and has been assigned to prepare a checklist what needs to be monitored and/or done. The switch over will be done per location. I have the following ideas as enumerated below but would like to find out if you have any suggestions, inputs and recommendations to handle this switch over safely and in a most efficient manner. I'm a systems admin person and routing and networking are not my strongest suit, so your input would be much appreciated.

If there are any components that I might have missed, please let me know also.  

My Idea: I'm thinking that the external network should be the (only) major concern and internally everything should be unaffected. We have to ensure that the external DNS record will be updated to the new service provider's IP address (which is handled by the vendor). That being said, internally, I think the IP address update should only be done in the email, vpn settings, firewall and external sites areas (ie, such as www.company.com dns record and ftp sites' dns records to reflect the new service provider's IP address. Is there something that I'm missing? And, are there internal components (ie, Active Directory, DNS..etc) that I need to worry about? Would like to find out if this turn over will also impact Active Directory or the internal components in our environment.

Appreciate all of your input on this.
0
Comment
Question by:mmoya
  • 2
  • 2
  • 2
  • +1
7 Comments
 
LVL 8

Accepted Solution

by:
Toxacon earned 250 total points
ID: 34931837
Well, it greatly depends on your internal network using private addressing. If it does, you have to update only external references, firewall outer leg address and modifying the routing table, incoming email address (if hosting it internally) and possibly dns forwarders in AD DNS.
0
 
LVL 13

Expert Comment

by:kdearing
ID: 34933376
Agree with Toxacon, assuming you are using private IP addressing for your network, then the only things to worry about are external-facing devices (firewall) and DNS.

If you have any control over the timing of the cut-overs, I would STRONGLY recommend you schedule them for a Friday evening.

Why, you ask?
1. DNS changes can take up to 48 hours to propagate.
2. If something does go wrong, you've got all weekend to fix it.

This way you avoid having downtime during business hours.

I've done alot of network conversions, even the simplest ones can go wrong.
0
 

Author Comment

by:mmoya
ID: 34951718
For curiosity sake and if our network does not use private addressing, then what steps are needed then? Thank yoU!
0
Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

 
LVL 7

Assisted Solution

by:bcrosby007
bcrosby007 earned 250 total points
ID: 34951826
You really have to use private networking (10.x.x.x, 192.168.x.x, 172.16.x.x - 172.16.32.x) for  your internal network unless you only have a few client machines. So, your internal network probably wont change.
To give you a good list, you must provide more information. Do you host your own email server. Own web server. Own firewall/ router. Basically, anything that connects to the outside world statically.
0
 
LVL 8

Assisted Solution

by:Toxacon
Toxacon earned 250 total points
ID: 34953299
If your network does not use private addresses, you very likely have to change every single IP address in your internal network, including DHCP scopes, Active Directory subnets etc.

Usually the Service Provider RIPE owns rights to the public block and only assigns IP block to its own customers so changing the SP means changing internal IPs as well, if not private.
0
 

Author Comment

by:mmoya
ID: 34960246
Thank you for the input. Just confirmed and we are using private IP addresssing..

To bcrosby007, yes, we host your own email server, own web servers and own firewall/ router.
0
 
LVL 7

Assisted Solution

by:bcrosby007
bcrosby007 earned 250 total points
ID: 34960294
Ok. Then you are going to have to update your DNS registrar with the appropriate IP information for your MX recort for mail, plus your A records for all of your other public ip's. Then you will have to change your firewall mapping from the new public ips to your internal private ip's. All in all, it is a pretty seamless operation. @KDearing was correct that it could take the internet dns registrars up to 48 hours to update to your new IP scheme, but i have never seen it take that long. So, some of your clients may get email delivery delays on their end.
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

In this tutorial I will show you with short command examples how to obtain a packet footprint of all traffic flowing thru your Juniper device running ScreenOS. I do not know the exact firmware requirement, but I think the fprofile command is availab…
Introduction Many times we come across a slowness or instability between two hosts, and almost always we blame the poor networking guys, just because they're an easy target.  Sometimes we forget that other factors including disk bottlenecks, CPU …
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

856 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question