Search results for query: *

cajuntank is exactly right. I'll try to give a little more explaination. Let's assume that you are going to put a cable between the switches and use port 24 on each switch. on switch 1, from the web interface (not that familiar with CLI) click on the configuration tab click VLAN...

I would guess in your 1810G that 'trunk' might have something do with with LACP (link aggregation) more than the trunking of multiple VLANs on a single link. Your having 'Taggeg' the uplink port (the one that goes to your router) already did that function. But this is only a guess.

ISPKing, thanks. I guess I was kinda expecting 802.3ab or 802.1ax (link aggregation to kick in automatically. I see now (at least on HP switches) that it is set to passive, and won't work unless at least one side of the LACP is set to active. Though (again, at least on HP's) this would not...

OK... removing port 50 (fiber port on the 2824, and the second 2650) did infact resolve this issue. Would having two paths, not trucked, to the main switch cause one or both of the lines to stop working even if Spanning Tree is turned off? Thank.

Doesn't seem likely since I have spanning tree turned off on all of these switches. Also, for this VLAN, The only VLAN listed with an untagged port is port 50. I do have other VLANs listing port 50 as a Tagged Port though. Could that be part of the problem, even though Spanning Tree is turned...

I have a HP 2824 that currently has a single fiber connection to a set of 2650's (fiber to one, and copper 1GB between the two remote 2650's). This link currently supports 4 VLANs. I would like to install a second fiber link between the 2824 and the remote 2650 that does not have a fiber...