HPE Aruba Networking & ProVision-based
1832592 Members
3129 Online
110043 Solutions
New Discussion

Re: HP ProCurve2810

 
Drampley
Occasional Visitor

HP ProCurve2810

I am installing 2810 in my network 2 being used as Distro switches and 2 as access switches.

I feed my routered port from a Cisco 7604-a router routed ports to the Distro switchI-a and Cisco 7604 router-b to distro switch-b

 on the distro switch the connections from routers are untagged ther are 3 interfaces for 3 different networks. one is for Data then one for management and the last is for VoIP.

I am trying to put the data and management together and the VoIP on different connection.

 

I want a connection from the a distro to Access a VoIP on one connection and Data on a different connection and the from disro a to access b and the same on distro b to access a and access b

 

I am running RSTP on the switches and two port trunk links between access switch a and b and distro a and b.

 

When I hookup the connection the Data and management works fine but both VoIP connection on the Access switches are blocked what am I doing wrong.

should the diffrent connections be independent of each other because they are different vlans between the distro and access switches.

4 REPLIES 4
paulgear
Esteemed Contributor

Re: HP ProCurve2810

Hi Drampley,

 

You've provided very little detail about the problem so it's not possible to know exactly, but it sounds to me like you don't have the correct tagging on both ends of your links.  If the switches you've mentioned are the only ones in your environment, then by far the easiest way to correct this is by turning on GVRP, but you should read up about this before doing it.  See the Advanced Traffic Management guide at http://www.hp.com/rnd/support/manuals/2810.htm for more details.

Regards,
Paul
Vince_Whirlwind
Trusted Contributor

Re: HP ProCurve2810

You need MSTP for that to work.

Even though you have physical links dedicated to a VLAN, the switch doesn't look at the VLANs to see if there's a loop, therefore it's disabling your physical link with the VOIP VLAN on it.

 

 

paulgear
Esteemed Contributor

Re: HP ProCurve2810

I missed the part about separate links for different VLANs in Drampley's first post. I think combining the links into a single LACP trunk and setting appropriate QoS priorities for the different VLANs would be a better solution than MSTP or separate links.
Regards,
Paul
Vince_Whirlwind
Trusted Contributor

Re: HP ProCurve2810

Agreed.

 

I know how the "separate physical links" thing comes about - design by committee.

 

Combining the physical links into an aggregated link gives you redundancy for your networks, which is far better risk mitigation than whatever they think separate links gives them.

You get improved resiliency (any single failure to cables, transceivers, or switchports does'nt interrupt traffic), and more efficient management.

 

Additionally, you need QoS anyway to protect your voice packets on the switch, so QoS will protect your packets on the interfaces.