3300icp vlan

[ralph]

Also, 172.16.30.0/24 isn't an rfc1918 network.

I had to stop an look up the RFC.
172.16.0.0      -   172.31.255.255  (172.16/12 prefix) is the actual private space subnet.

172.16.30.0/24 is just subnetting it down further.   Shouldn't be an issue.

Ralph

[NewVoIP]

Been out sick, here are additional informations, we have a total of 102 phones, the MS Dhcp isn't assosicated with the VoIp vlan, Keep in mind the phones are working but there is so much echo, etc. We were told that we need to Untag the port that Mitel 3300 ICP and then set the opiton 125 of the mitel dhcp, Vlan 30 and Priorty 6. We test everything worked fine. Echo, jitters, etc tremendously reduce. But now we need to configure our HP switch to route/dhcp relay.
There are 5550 consoles, third party CA and VM that are interface with the Mitel via IP. We are trying to use one nic for above items needs. They need too access both data and voice network.

Thanks for all whom reply, greatly apprieciated.

[v2win]

Your ports should be configured something like this

The MS DHCP server untagged on the data vlan only
the 3300 server untagged on the voice vlan only

Phones and PC's untagged data vlan and tagged voice vlan

for QoS  type-of-service diff-services is the line in the configuration for HP it shouldn't really matter if its all on the same lan.

I have a document on how to configure the MS DHCP server but its too large to attach here.

PM your address an I will send it to you or maybe one of the moderators can raise the limit on the size of attachments.

[ralph]

Also,
You shouldn't need an IP Helper address if the options are set correctly in the native VLAN DHCP server.

Ralph

[Chakara]

Didn't realize it was so low - bumped it to a meg - is that enough?

-Chak

[v2win]

2.5 meg unzipped

Here is the DHCP configuration guide for the MS DHCP server

This is a ZIP file rename it from .txt to .zip

[chadmaynard]

Also, 172.16.30.0/24 isn't an rfc1918 network.

I had to stop an look up the RFC.
172.16.0.0      -   172.31.255.255  (172.16/12 prefix) is the actual private space subnet.

172.16.30.0/24 is just subnetting it down further.   Shouldn't be an issue.

That should have read 172.168.30.0/24 isn't a valid rfc1918 network.

[Northeaster]

I am curious as to why the echo problems would have been reduced.  His IP sets were in the correct subnet (Voice Vlan IP address range, correct??)

Is it possible that the sets could have been in the right Vlan, but the data wans't being tagged / prioritized properly?

If someone could explain what was wrong, and is now corrected, I would appreciate it!!

[Northeaster]

Using option 125 to identify the Vlan ID and priority is juts another way of providing the same info as options 132, 133.  So was it the untagging of the port that the 3300 was connected to, that fixed the echo?

NewVoip -  Do your IP sets now tell you what VLan / Piority they have, as they boot up??