Implementing 100 Seat IP 9608 2

[maxse]

We will be implementing about 90-100 IP Phones 9608 and 9611G almost all using the built-in two port switch.

If we had separate cabling we would create a separate VLAN on its own subnet to segment the traffic. However, we are using one cable for voice/data. What is the best method for achieving a quality setup?

Will the built-in two port switch already prioritize traffic? If so we would still like to use two separate subnets on the same switch, otherwise we will run out of IPs.

 

[intrigrant]

Use VLAN tagging and create two VLANs, if you don't know how then consult one of the forums in communication rack, this is worth reading too.

Know your product and become a Pro

 

[sNNNeaker]

Another easy way: use the Avaya Routing switches and run the command "run ipoffice" on them. It will do everything for you. Link

ACIS SME | ACSS SME

http://www.kriesten.de

 

[holdmusic34]

Nice!

 

[sNNNeaker]

Thanks for the star!

ACIS SME | ACSS SME

http://www.kriesten.de

 

[g18c]

HP Procurve 2500 series switches work great...

Log into the switch, create a voice VLAN (i.e. VOICE_VLAN 43) in addition the default data (DEFAULT_VLAN 1), then go to VLAN management, set DEFAULT_VLAN to untagged and VOICE_VLAN to tagged on each of the phone access ports.

If you are using IP Office as the DHCP server for the voice network make sure you are not connecting any other DHCP server (i.e. Windows Server) on a port which has tagged VOICE_VLAN traffic as it will cause a dhcp conflict (it will actually listen on all VLAN interfaces and respond to any requests), in this case just set the port to which the Windows Server is connected to DEFAULT_VLAN `untagged` and VOICE_VLAN to `no`.

Of course you may want to run your management network on a different VLAN and you can set the native VLAN and ports accordingly, in this case you would add an additional VLAN.

Hope that helps

 

[NLPeterK]

In addition to g18c's post:

after you create the Voice vlan, make sure to give the 'voice' command. It will enable LLDP so the phones will automatically switch to the correct vlan. Otherwise you'd have to configure your data dhcp to have extra options. With LLDP you don't need this.

Also, to keep it simple, only tag/untag VLANS's on ports where it's needed.

Windows data server: untag only on data vlan, no voice tags
IPO voice vlan port: untag only on voice vlan, no data tags
IPO data vlan port: untag only on data vlan, no voice tags

This way your always safe and you won't get any dhcp conflict like g18c said.