Switches, Hubs, and Modems
cancel
Showing results for 
Search instead for 
Did you mean: 

Cascading Multiple Procurve's ?

SOLVED
Go to solution
Karl Collinson
Frequent Advisor

Cascading Multiple Procurve's ?

Morning\Afternoon All,

Just want to clear something up..

If one had 4x Procurves, same model..
All configured to work the same with 3 VLANS, 1=Default, 2=VoIP, 3=DATA...

How would one setup the switchs to Cascade and work as one LAN?

Ensure all the switches are configured the same (All have VLAN 1&2&3 QoS etc) and use Port 25 and 26 Ethernet or Fibre set the ports to Trunks and link all the switchs (English term = Daisy Chain)

Or Just configure Ports 25/26 with the VLANs as Tagged\untagged??

Thx,
Karl.
20 REPLIES
Mohieddin Kharnoub
Honored Contributor

Re: Cascading Multiple Procurve's ?

Hi

You can Stack them all together, and in this case the Master will have the IP address.

Or you Cascade the switches by connecting them on with Uplinks with all Vlans TAGGED.

Switch1 - Switch2
Switch2 - Switch3
Switch3 - Switch4
Switch4 - Switch1

the Term TRUNK is Misleading here because the links between the Switches are called UPLINKS,only Cisco call them Trunk since it carries all the Vlans.

Trunk is a logical port formed of at least of physical ports, and the term Trunk is used with All the Vendors with this explanation except cisco.

Good Luck !!!
Science for Everyone
Karl Collinson
Frequent Advisor

Re: Cascading Multiple Procurve's ?

Thanx Mohieddin:

How does one stack them, ie config example?

Thx,
Karl.
Mohieddin Kharnoub
Honored Contributor

Re: Cascading Multiple Procurve's ?

Hi Karl

I will consider you have 2600, then the configuration with examples can be found here :

ftp://ftp.hp.com/pub/networking/software/AdvTraff-Oct2005-59908853-Chap08-Stacking.pdf

And its the general way of most of the ProCurve switches if not all :)

Good Luck !!!
Science for Everyone
Karl Collinson
Frequent Advisor

Re: Cascading Multiple Procurve's ?

Thx!!

Never took notice of the Stacking option at the bottom in menu..

=0).
Karl.
Alessandro_78
Regular Advisor

Re: Cascading Multiple Procurve's ?

Sorry for the intrusion :)
I think that HP stacking is only for management.
For example: from a master switch i can configure other 3 switches directly.

I think that Karl is asking for stacking switch like Cisco:

For example: switch 1 with 24 port, switch 2 with 24 port, make a single logical switch with 48 ports....
Karl Collinson
Frequent Advisor

Re: Cascading Multiple Procurve's ?

Afternoon All,

I am just trying to create a since LAN with 3 VLANS, QoS etc and all the switches working as one..

?

Thx,
Karl.
Colonelk
Frequent Advisor

Re: Cascading Multiple Procurve's ?

What switches are you using Karl?

On my 2900's they have 10GbE stacking ports on the back that can be linked with the supplied cable. Those ports can be members of vlans just like any other and I can manage all three switches from the one I designated as master.

Karl Collinson
Frequent Advisor

Re: Cascading Multiple Procurve's ?

They will b the 2626... >:-\

Thx,
Karl.
Alessandro_78
Regular Advisor

Re: Cascading Multiple Procurve's ?

Hi Colonelk,
with that stack cable, can you put port1 of the first switch in turnk (LACP) with the port 22 of the second switch?

I think that HP stack is just for management, not stack like cisco where you can make a single logical switch formed by two or more physical switches.
Colonelk
Frequent Advisor

Re: Cascading Multiple Procurve's ?

Hi Allesandro

If I look in the menus of the 2900 switch under Port/Trunk settings, I can alter ports A2 and A3 (the uplink ports) and enable/disable flow control, mode, group and type (including LACP) just like I could any other port.

In my configuration I don't need trunking so I'm not 100% sure it can do exactly what you ask but so far I see no reason why it can't.....

Tino
Colonelk
Frequent Advisor

Re: Cascading Multiple Procurve's ?

Looking in the Management Guide it says:

For proper trunk operation, all ports in a trunk must have the same media type and mode (such as 10/100TX set to 100FDx, or 100FX set to 100FDx). The flow control settings must also be the same for all ports in a given trunk. To verify these settings, refer to â Viewing Port Status and Configuring Port Parametersâ on page 10-3.
â ¢

I'm therefore guessing that using a combination of 10GbE uplinks and 1GbE Rj45 ports wouldn't work.

Alessandro_78
Regular Advisor

Re: Cascading Multiple Procurve's ?

Ok but AFAIK HP trunk is used to manage multiple switches from a single master switch.
Doing so you don't need to log on all switches but only to the master switch.

Can you try to trunk in LACP multiple port on multiple switches?

Like port A1,A2,B1,B2 in a single LACP trunk...
Just to see...

Colonelk
Frequent Advisor

Re: Cascading Multiple Procurve's ?

According to the manual stacking is for management of switches via a commander.

Trunking is for aggregating ports of identical types to increase bandwidth.


I'm reluctant to try trunking for you as its taken me the best part of 4 days to get this setup working the way I want it to (I've been learning along the way!)

I suggest you read the trunking parts of the 2900 MgmtCfg guide (7700kb download) from the Procurve website.

From the manual:


trunk group
Port trunking allows you to assign up to eight physical links to one logical link (trunk) that functions as a single, higher-speed link providing dramatically increased bandwidth. This capability applies to connections between backbone
devices as well as to connections in other network areas where traffic bottlenecks exist. A trunk group is a set of up to eight ports configured as members of the same port trunk. Note that the ports in a trunk group do not have to be consecutive. For example:
The multiple physical links in a trunk behave as one logical linkSwitch 2:
Alessandro_78
Regular Advisor

Re: Cascading Multiple Procurve's ?

Ok.
So HP stacking is what i've said before:
just for management, not for physical switch aggregation into one bigger logical switch.

Thanks.
Karl Collinson
Frequent Advisor

Re: Cascading Multiple Procurve's ?

Thx for all your help so far all..

But im still alil unsure on what i should look to be doing....

Senario: -

3 Vlans.. 1 for Voice, 1 for Data, 3rd is the Default..

Want all 3 switchs to work as one LAN with the 3 VLAN's working across the board...

Fibre is the Medium on port 25 on two of the switchs, port 25 and 26 on the third..

Same VLAN config on all three switchs, what do i need to do to ports 25 and 26 for the LAN to work as 1: -
Trunk? "Believe thats only for bandwidth so no good in this senario"
All VLANS tagged?
Etc

Thanks all =0)
Karl.
Joel Belizario
Trusted Contributor

Re: Cascading Multiple Procurve's ?

Hi Karl,

I'm having trouble understanding what you want to accomplish - what exactly do you mean by wanting the switches to work as one LAN?

What is throwing me is you also want 3 VLANs running, which seems to be contradicting with your other statement (at least to me).

Can you clarify?

Thanks,
Joel
Karl Collinson
Frequent Advisor

Re: Cascading Multiple Procurve's ?

Hi Joel,

Gonna make this as simple as poss...

One big switch in the comms room "Gonna call this the mother ship".

2x Smaller 24 port switchs -> 1x in warehouse -> 1x in Prebuild.

------------------------------------

-Mother ship config-
3x VLANS

Ip routing
VLAN 1(Default)
Ip 192.168.0.243
--------
VLAN 2 (Voip)
172.16.0.253
QoS
etc
--------
VLAN 3 (Data)
10.0.1.253
etc
------------------------------------

Now i need to config the Warehouse and prebuild switchs to work with the mother ships config.
Out of the box they will only have the default VLAN.

How do i config the 2 other switchs to work with the VLANS on the mother ship?

Thx,
Karl.

Joel Belizario
Trusted Contributor
Solution

Re: Cascading Multiple Procurve's ?

Hi Karl,

Ok I follow you now. You should create the VLANs on the 2 new switches and tag the uplinks with all VLANs.

IP routing should be turned off on these switches as your "mothership" switch should be doing the routing between VLANs.

Do not assign any IP addresses in the VOIP and Data VLANs, but assign IP addresses in the default VLAN for management access.

Lastly, tag / untag the appropriate ports on the new switches depending on how you are connecting the hosts.

Also, when you mentioned cascading the switches everyone assumed you meant you wanted to "stack" the switches - i.e. connect multiple switches together to behave as one big virtual switch for management or connectivity purposes.

Hope this makes sense, anyone else have anything to add?

Cheers,
Joel
Karl Collinson
Frequent Advisor

Re: Cascading Multiple Procurve's ?

Hi Joel.. â Thanksâ â ¦. =0)

-Uplink-
When u say â uplinkâ , is that a generic name for any port that links two switches?
Or
Is there a dedicated port on the Procurveâ s for this?
Or
A command line required to configure the port?

-IPs & VLANS.-
So assign a Static address to all 3 VLANs, same subnet.
No IP address for VLAN Data and VLAN VoIP across the board?

The last config I did I had the router in VLAN1, Ip routing 0.0.0.0 0.0.0.0 to the routers IP, and static addresses on the router directing traffic back to the VLAN IPâ s.

How will I get round this issue if the VLANâ s have no IP address?

-DHCP, IP Routing-
The IP phones and Computer terminals where DHCP issued IPâ s, all with the default gatewayâ s being the Data or VoIP VLAN IP, what config changes do I need to make?


Thanks,
Karl.

Joel Belizario
Trusted Contributor

Re: Cascading Multiple Procurve's ?

Hi Karl,

Yes I'm using the term "uplink" generically - you could call it an inter-switch link too I guess. There is no dedicated function for this.

When you assign an IP address to a VLAN you are creating a virtual router. For management purposes (over network) each switch requires an IP address (in your management VLAN, which you may or may not have explicitly defined).

Think of the IP addresses on your mothership switch as routers downstream from your "real" router. A VLAN is a totally isolated network until you connect it to another network with a router (just like a real LAN).

The concept of tagging and untagging ports is to extend the logical boundary of the VLANs across switches (and other devices that understand 802.1Q tagging).

When you untag a port, that port is "physically" in the assigned VLAN. When you tag a port with a particular VLAN, you are encapsulating that traffic on top of the untagged traffic that is being carried by that port.

I've found it's helped me to wrap my head around the concept by understanding what how the tagging process works:

http://en.wikipedia.org/wiki/IEEE_802.1Q

Hope this clears any confusion.

Cheers,
Joel