2 x 3300s need to share DHCP for connecting IP phones

[pea123]

Hie to you all.

I have two 3300s at a single site stacked one on top of the other. They are both linked by E1 and they both belong to one subnet. ICP1 = 10.0.0.1/24 & ICP2 = 10.0.0.101/24.

The licenses for the ICPs are 100IP users each(no Enterprise license). I must install 200IP phones in total. I would like to enable DHCP on ICP1 & install the first 100IP phones. My problem arises when I am installing the second 100IP phones.

I need ICP1 to lease addresses to the 2nd batch of phones but the phones will be connecting to ICP2. I need help on the configuration that is required on ICP1 to achieve this. For now I have connected 5 phones of the 2nd batch by statically assigning the ICP & TFTP addresses then the Phone IP address would come from ICP1.

Is there a way that I do not manually enter the above two addresses but just plug the phone & the phone gets an address from ICP1 but connect to ICP2?

Thank you.

 

[sarond]

Not if your on the same subnet and LAN, are these for different customers?
Is there any need for these controllers to be linked by network or other means?

Just trying to understand why you would want to do this.

 

[kwbMitel]

What I understand is that you have 2 standalone systems networked via E1 and you need them to operate (as best you can) as 1 system.

Are you sharing the Data cable with PC's or is the port dedicated to the phone?

How familiar are you with vLAN'ing?

**********************************************
What's most important is that you realise ... There is no spoon.

 

[pea123]

Have now settled for IP Trunking connecting the 2 ICPs however they are still on the same subnet.So the ICPs behave like a single ICP now but the problem is still that the 2nd set of 100IP phones need to be manually entered ICP & TFTP addresses to point them to ICP2 otherwise they prefer connecting themselves to ICP1 .
Sharing ports with PCs.I have an average knowledge of vLaning.

 

[kwbMitel]

Is this within your capabilities?

Create a separate voice vlan for system 1 and 2
Setup the Ports for CDP or LLDP (whichever applies) (this delivers VLAN information to the phone Prior to DHCP)
Configure your Network ports appropriately as to whether they register with system 1 or system 2

I am uncertain as to whether you will need routing between the vLans. My gut says no as long as they exist on the same Network. I've never tried this though, so I'm not sure. Make sure you test before reconfiguring everything.

Boot sequence
Phone boots
Phone gets VLAN info from data switch via CDP or LLDP
Phone Sends Tagged DHCP request (the tagged request is how they get separated)
Appropriate controller responds.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[DoubleUT]

You have connected both controllers via an IP trunk connection. If you cluster both switches togetter then both controllers tell eigh other what numbers they have installed and if a phone from ICP2 is trying to register at ICP1 it will be redirected.

 

[jayhwf]

The easiest way, although it can be a pain, is to just change the DHCP settings for the second batch of phones when needed.
The first 100 phones receive an IP address and are told to connect to the controller IP address for call control, TFTP etc.
Change the DHCP settings to your second controllers IP address when the next 100 phones are installed. This way an IP address is given to the handset by the first controller, it will then register with the second controller for its call control, TFTP etc.
It's an old trick used by Mitel themselves in the past, although administering it can be an issue, especially with the number of phones you're talking about.

 

[pea123]

I would like to take the path of DoubleUT. I have created Custer Element IDs and must then set up Remote DNs but cant seem to find the Remote Directory Number Assignment Form. Using MCD5.Can only a Remote Directory Number Form with which is blank and I can not make any changes on it.Do you know were the appropriate form is?

 

[kwbMitel]

At the beginning, you said you do not have enterprise licensing

From this I assumed you have 2 standalone systems

If in fact, you have systems that can be fully networked and clustered, you must turn on sharing. Once sharing is active, you must sync the systems, this will populate the RDN form automatically

**********************************************
What's most important is that you realise ... There is no spoon.

 

[pea123]

The enterprise wasn't there at first kwbMitel but because of the above complications we got it afterwards and networked the pbxs. Im set to go your route now ( fully networked and clustered, you must turn on sharing. Once sharing is active, you must sync the systems, this will populate the RDN form automatically)
Could you please extrapolate on the process sharing & sync part as this is completely new to me. The systems are networked by IP trunking & Clustered already.
Thank you.

 

[DoubleUT]

The last step that you need todo is Sharing and Sync in the Voice networking page. Sharing will try to make forms identical. Common fault here is that Pickup Groups if used should NOT have the same indexnumbers. If you are using PG then remove them and add after the sync was successfull. For the sync make sure that every number only exist once in the network. If that is done you are finished.

 

[LoopyLou]

To the original question as I understand it is to serve IP address to 200 phones split between 2 systems.

You state you are clustered therefore if you have 100 licenses on system 1 and 100 on system 2 you can still use a single DHCP server for both. If you want you can set it up on system 1 with a scope to support the 200 phones. The phones don't care where the DHCP is. When a phone boots and gets an IP address it will then look to register on a controller based on the info in Option 12. If it can't register to system one ( because it is not programmed there ) it will simply register to system 2 ( or in the case of multiple 3300's ) it will check with each system in the cluster until it can register. At least that's how I understand it.

So program the DHCP and then program your sets to the appropriate system.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.