Information Technology
asked on
Transitionning from VPN tunnels to MPLS with Sonicwall as router and gateway
Hi guys,
I have a new project and would like some inputs. I have basic network understanding but I think that i'm in over my head with the new project. We have 10 locations, one main loation and 9 sites connected back to main with VPN. All site are using TZ100 and main site is using a NSA3500 with latest sonicwall firmare. We are bringing in new MPLS circuits to all the locations. This is what I need help with. All the sites are coded with a 192.168.X.1/24 subnet. Main office is 192.168.1.1/24. The NSA3500 will stay the gateway and router for a FIOS 50/20 internet connection. MPLS circuits are private. I will need to transition the sites from VPN to MPLS one by one. If needed I can change the site IP scheme at any sites.
Question: How should I set the MPLS router IP and how should I connect it to the NSA3500? I have an extra interface (X5) not in use on the NSA that I was thinking about dedicating to the MPLS route. Now what IP could I assign to the main office router X5 interface? Once I transition one site from VPN to MPLS, how is the routing going to work. For example, how can I tell the NSA that site 1 is not going to be 192.168.X.0 through VPN but will be 192.168.Y.0 and will be going through interface X5 instead...
Any advices would be great!
I have a new project and would like some inputs. I have basic network understanding but I think that i'm in over my head with the new project. We have 10 locations, one main loation and 9 sites connected back to main with VPN. All site are using TZ100 and main site is using a NSA3500 with latest sonicwall firmare. We are bringing in new MPLS circuits to all the locations. This is what I need help with. All the sites are coded with a 192.168.X.1/24 subnet. Main office is 192.168.1.1/24. The NSA3500 will stay the gateway and router for a FIOS 50/20 internet connection. MPLS circuits are private. I will need to transition the sites from VPN to MPLS one by one. If needed I can change the site IP scheme at any sites.
Question: How should I set the MPLS router IP and how should I connect it to the NSA3500? I have an extra interface (X5) not in use on the NSA that I was thinking about dedicating to the MPLS route. Now what IP could I assign to the main office router X5 interface? Once I transition one site from VPN to MPLS, how is the routing going to work. For example, how can I tell the NSA that site 1 is not going to be 192.168.X.0 through VPN but will be 192.168.Y.0 and will be going through interface X5 instead...
Any advices would be great!
ASKER
Hi, here is what I know for sure: the MPLS network and routers are managed by the service provider and they will take care of making modifications and updating the routes according to our request.
I am not running any specific routing protocol beside what comes standard with the sonicwall. As far as the routes I think the sonicwall created all of them when I added all the VPN tunnels.
I'm kind of wondering if I just add the routes manually on the sonicwall and tell it for each network to go to a specific interface if that's going to work. For example what if I assign 192.168.3.1 for the X5 interface and 192.168.3.2 for the MPLS router, then all the other sites connected to the MPLS router will have something like 192.168.X.X/24, does the IP I assign to the X5 interface and MPLS router matter beside that they need to be from a different subnet than any other subnets that are assigned to the VPN? (Gosh I hope I am not making this seems more complicated than it is...)
I am not running any specific routing protocol beside what comes standard with the sonicwall. As far as the routes I think the sonicwall created all of them when I added all the VPN tunnels.
I'm kind of wondering if I just add the routes manually on the sonicwall and tell it for each network to go to a specific interface if that's going to work. For example what if I assign 192.168.3.1 for the X5 interface and 192.168.3.2 for the MPLS router, then all the other sites connected to the MPLS router will have something like 192.168.X.X/24, does the IP I assign to the X5 interface and MPLS router matter beside that they need to be from a different subnet than any other subnets that are assigned to the VPN? (Gosh I hope I am not making this seems more complicated than it is...)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It makes sense and maybe I should enable routing on the SW. for now all the routing protocals are turned off on all the interfaces but I could turn RIP on. I will have a few MPLS sites running in a few days and will do some testing. At least it's not like I have to do the cut over tomorrow :).
Well you could have a default route to the CE and the service provider is managing your routing?
First step is to call them, tell them what you need and see if they can implement or advise you on your next step. If they manage your CE then this should be part of what you are paying for.
Let me know how i can help out?
harbor235 ;}
ASKER
After more reflexion, this is what we ended up doing:
Set another gateway on the LAN with IP *.*.*.254 for all MPLS traffic
Create a custom route on the main sonicwall and remote sonicwall to send appropriate traffic through the MPLS network. So far it's working great
Set another gateway on the LAN with IP *.*.*.254 for all MPLS traffic
Create a custom route on the main sonicwall and remote sonicwall to send appropriate traffic through the MPLS network. So far it's working great
ASKER
had to play around with the sonicwall specific options. Works great now
So is the MPLS router manged by you or the service provider?
Are you running a routing protocol? Which one?
The outside interface or peering interface with the provider PE router should be using a different IP range for peering? The inside router interface should be connected to a route to the 192.168.x.x/24 net.
harbor235 ;}