[cisco-voip] HP Switches

[Jason Aarons (US)]

Since the cheaper phone is only 10/100 a lot of customers have
structured wiring with 3 or more runs to each desk. In the closet they
have non-POE 1000BaseT switches for PCs and 10/100BaseT switches for
phones with PoE.   They run 10/100 to the phone and 1000 to the PC.  The
cost of 10/100/1000 PoE switches is pretty expensive compared to 10/100
PoE.  Still one network on backend just no IP Phones on expensive
1000BaseT ports. This also reduces SmartNet costs.

 

All Cisco makes it easier to manage/troubleshoot, but Ethernet is
Ethernet.

 

 

 

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Voice Noob
Sent: Friday, July 18, 2008 10:04 AM
To: Bill Simon
Cc: cisco voip
Subject: Re: [cisco-voip] HP Switches

 

So there are two network cables going from your distribution closet to
your desk. One cable to the phone and one cable to the PC? I want to run
one cable, have the phone on the voice network and PC on the data
network. If I have to configure the VLAN manually that is fine I just
want to know if it will work this way. 

On Fri, Jul 18, 2008 at 8:28 AM, Bill Simon <bills at psu.edu> wrote:

Note I said logically separated not physically separated.  Yes you run a
cable to your PC and a cable to your phone.  You can do the logical
separation at the switch (configure port-based VLANs) or further
downstream if you want a whole switch of just phones and another whole
switch of just PCs... etc.  We do not run separate core networks.
Disadvantages?... if we want to connect from pc to the voice network
it's routed (but this is to our advantage because then we have the
ability to set up access lists at the router level).  We can't use VT
Advantage (not a concern) and we miss out on some silly click-to-dial
stuff that no one in our organization seems to care much about.  Rather,
they want a rock-solid phone system and that's what they get.

I guess the definition of "converged network" is different for everyone
though.

Voice Noob wrote:

Bill I don't think you situation is comparable to most. You are not
using a converged network which is one of the big reasons to go with an
IPT system. You have two physical networks one for voice and one for
data.
 I want to have one physical and two logical networks like I can with
Cisco phones and Cisco switches. The phone boots up and changes to the
voice vlan and the phones are on the data vlan. I don't care to tell the
customer that they must manually configure this but can they still use
DHCP for all of the IP info and just manually set the voice vlan?
ALso if I do this how do I set it up on the HP switch side? Is it a
trunk or an access port with two vlans?

On Fri, Jul 18, 2008 at 7:00 AM, Bill Simon <bills at psu.edu
<mailto:bills at psu.edu>> wrote:

   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.

   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.

   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.

 

 




-----------------------------------------
Disclaimer:

This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only.  If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful.  If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080718/8c6f4368/attachment-0001.html>