<div>Just out of curiosity... why dont you use the PC port?</div>
<div>You have phones where you dont have pc's? or you run 2 cables, and sets of switches?</div>
<div> </div>
<div>As far as I know with Cisco.. DHCP will not help config your VLAN on the phone. A lot of 3rd party systems have this capability though. They boot in a data vlan, get a DHCP lease from the data scope, and some custom DHCP option tells them which vlan to use, and then they reboot themselves with this config using separate voice and data vlans.</div>
<div> </div>
<div>Manual config comes in when you want to use the pc port in the phone, and you want to run separate voice and data vlans..</div>
<div>If you didnt have Cisco switches with CDP v2.. the switch could not tell the phone which vlan to use for which port automatically.</div>
<div>So to configure your phone to use the voice vlan, you could manually set it from the phone interface itself. (Lots of work on a large deployment)</div>
<div> </div>
<div>Now there is LLDP-MED, there is talk of this in Cisco, and I've seen support on phone config pages in CCM... but I'm not sure if it can be used / deployed the same way yet. Would be interesting to know if it is possible.</div>
<div> </div>
<div>Personally Cisco is still my favourite, and Cisco on Cisco is probably always going to be the easiest.. but I do like the HP gear, and where budget doesnt allow, i think it's certainly a worthy contender... </div>
<div> </div>
<div>Same can be said for the Nortel stuff too... you had stacking and layer 2 meshing without blocking links (and between multiple physical chassis!) long before 3750's, stackwise, cross stack etherchannel and virtualisation came out..... </div>
<div> </div>
<div>I'm going to wash my mouth out now... i feel a bit dirty :) I hope John Chambers is not reading this forum..</div>
<div> </div>
<div>Cheers,</div>
<div> </div>
<div>Tim<br><br> </div>
<div><span class="gmail_quote">On 7/18/08, <b class="gmail_sendername">Bill Simon</b> <<a href="mailto:bills@psu.edu">bills@psu.edu</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">We use (have used but are phasing out) HP Procurve on the voice network. No problem. But note: we have a logically-separated voice network, do not use the phone's PC port (thus no need for VLAN) and have had to deal with power insertion because our HP switches are not powered.<br>
<br>CDP is not needed. I don't understand what you mean about hard-code the configuration. DHCP provides the options the phone needs to contact Call Manager.<br><br>I was watching the other thread about Adtran and some of the stuff people said seems quite like FUD. Cisco appreciates this scare-tactic marketing but the truth is that you can use any LAN switch. Using Cisco gear will make your life easier though.<span class="q"><br>
<br>Voice Noob wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I saw someone post about HP switches in a different e-mail but thought I would start a new thread. I have a customer that has a significant investment in HP switches. Has anyone used these in a Cisco IPT network? I understand about the CDP issue but what if I hard code the configuration or can I set it as a DHCP option like an Avaya IP phone? anyone tried?<br>
</blockquote><br></span>
<div><span class="e" id="q_11b360ae736d9ef6_2">_______________________________________________<br>cisco-voip mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a onclick="return top.js.OpenExtLink(window,event,this)" href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br></span></div></blockquote></div>
<br>