Moving several 5212 handsets to remote site

[andrewdh]

Mitel 3300 ICP CXi
Hi all - need some help here

We have a new office but exchange lines are 3 weeks away so I need to move a bunch of 5212 POE handsets there and connect over a new set of ADSL links (keeps it away from other traffic). They came with Netgear ADSL routers I plan to run as pure ADSL modems with VPN behind them.

The handsets are currently connected to a HP Procurve 2626 with POE on VLAN1 10.0.0.x (VLAN2 10.0.1.x is used for data and the PC's need to move also).

Also have a Netcomm NP2480 Pro Switch with Port based VLAN support (not configured yet) remaining as it currently connects the Data LAN to the WAN port of the Mitel for remote management.

I gather I will have to totally reconfigure IP on the Mitel to use multiple subnets and reallocate IP for remote sites and open a swag of ports.

Also the DNS server is currently on 10.0.1.x network staying at the old site for now.

I have a pair of Netgear ProSafe VPN routers or could build a pair of Linux boxes for the VPN if push comes to shove.

Oh and when new lines installed I need to do this in reverse to support 2 handsets back at the original location.

Any help configuring this would be great.

 

[danramirez]

andrewdh,

Let me ask a question: Are you going to install a new Mitel at the remote site? Or you just want to have remote phones that are registered at the current location?

Regards,

Daniel

 

[andrewdh]

Thanks Daniel - I need to move some of the existing phones to the remote location until the system can be relocated to that site - which will be several weeks. Once it is moved the remote site will become the main site and the current site will become a remote location.

We have outgrown our office so we are moving. We will keep the old office as a remote site.

 

[JimHilton]

Hi, I think you have pretty much summed up what you need to do. I'd go with the linux boxes only because i know NAT better then I know the model of vpn boxes you have.

If you use the linux boxes, once your tunnel is established you should be able to point the DNS server from the remote site to your current site. (We use cisco PIX boxes and a series 3K concentrator and point all the remote sites to our main DNS server).

At your remote site, the linux box would need a second NIC say programmed at 10.0.3.xxx. You also probably would need a 3rd nic to service the pc's etc.

In theory, you should be able to subnet hop EG from the remote linux box to the local unix box to your LAN and to the mitel. A ping test would confirm this.

If so, then I would just hard code the sets as there are only a few of them and its a quick way to get running.

The local sites' linux box would need access to the the mitel subnet. Hardcode a nic to to 10.0.0.253 or something where it is outside the DHCP scope

I run a similar setup with a BSD can, We have 4 subnets in the building. The BSD can has a 6 nics in it and 4 of the nics connect into switch to provide the various subnets. But they can all subnet hop.

My thoughts are if you think about carefully you may find that you can use your new settings once setup at the new location and simply change the IP of the mitel to the new subnet (EG 10.0.3.).

 

[andrewdh]

Thanks Jim
Your advice gives me some comfort. I thought the tin can with a bunch of nics was going to be the answer.
Regards
Andrew