Web and Unmanaged
cancel
Showing results for 
Search instead for 
Did you mean: 

Setup 1810 switches - trunk

 
lucver7
Occasional Advisor

Setup 1810 switches - trunk

Hi all

I have the following setup:

Vlans:

1: default vlan

10: admin

20: guest

 Hardware:

1 x CISCO RV180 router (DHCP server - vlan 10: 192.168.1.0/24 - vlan 20: 192.168.2.0/24)

1x HP 1810-24 (port 23/24 Trunk static (untagged in Vlan1) - port 1-12 vlan 10 (TR1 en TR2: tagged)- port 13-22  vlan 20 - (TR1 en TR2: tagged)

5x HP 1810-8 (port 7/8 Trunk static (untagged in Vlan1) - port 1-3 vlan 10 (TR1 en TR2: tagged)- port 4-6  vlan 20 - (TR1 en TR2: tagged)

Connection of the switches:

Cisco-RV180 port 1 (vlan 10) connected to 1810-24 (switch ip 192.168.1.30) port 8 (vlan 10)

Cisco-RV180 port 3 (vlan20) connected to 1810-24 (switch ip 192.168.1.30) port 22 (vlan 20)

1810-24 (switch ip 192.168.1.30) TR1 connected to 1810-8 (switch ip 192.168.1.31) and TR2 to 1810-8 (switch ip 192.168.1.32)

1810-8 (switch ip 192.168.1.31) TR1 connected to 1810-8(switch ip 192.168.1.33) and TR2 to 1810-8 (switch ip 192.168.1.34)

1810-8 (switch ip 192.168.1.32) TR1 connected tot 1810-8 (switch ip 192.168.1.35)

I've made sure that all the links between the switches are the same speed and type.

I've stacked them on top of one another on my desk, connected the switches and router and everything works fine. I tried all vlan ports on all the switches to get a correct IP form the CISCO, no problem everything is OK. The trunk prots show up as active.

When I tried this setup in the actual situation, the trunk ports remain down. I've tested the CAT6 cable running between the swiches and it is fine. When I connect say port 8 on the 1810-24 (switch ip 192.168.1.30) with port 3 on an 1810 (switch ip 192.168.1.31) in the actual situation, both ports show up as active.

I can't figure out what is wrong.

Help would be appriciated!

Luc

13 REPLIES
parnassus
Honored Contributor

Re: Setup 1810 switches - trunk

Have you configured both (Static) LAGs before manually connecting both Switches with those Cat.6 Ethernet cable pairs?

IF so, disconnect them, then, on each Switch, configure the LAG to use LACP (Dynamic) or No Protocol (Statico) and redo the VLAN Tagging against that BAGG (BAGG port type should be set to Trunk, then you can set the BAGG port VLAN Tagged for the VLANs you need to be tagged)...once all is done connect both Switches as you did before. The BAGG (Static or Dynamic) should go up in few seconds.

Better to use LACP (Dynamic) if you are working with very similar (if not equals) Switches.

Better to start with necessary ports (LAG members ports) in their default configuration so you know yet the settings are corrects on both Switches for all involved ports.

lucver7
Occasional Advisor

Re: Setup 1810 switches - trunk

Tnx but it doesn't work.

I changed the ports to LACP active, still no go.

 

parnassus
Honored Contributor

Re: Setup 1810 switches - trunk

Could you please draw and post a simple diagram of the Network Topology you're trying to configure?

An image is better than hundreds words.

Maybe I'm missing (or I misunderstood) something about what you wrote in relation of your Trunks...since you have 5 Switches I hope you haven't done any network loop (I mean: is it your Switches topology a Star, a Daisy Chain or what?).

From each Switch you should have only one Trunk (a LAG or just a single Link, doesn't matter) to any other Switch of your network...no loops, no rings (no other links or LAGs coming back directly from the same Switch or indirectly through other Switches).

Vince-Whirlwind
Honored Contributor

Re: Setup 1810 switches - trunk

The topology is clear from the description.
You mention 5 trunks:
Sw30 TR1 & TR2
Sw31 TR1 & TR2
Sw32 TR1

This is either incomplete or completely spurious: you either have 10 trunks or none. You haven't provided the port membership information about the trunks.
The only port membership information you give is "port 23/24 Trunk static (untagged in Vlan1)" without saying what trunk this is.

When you configured these "trunks" were you attempting to perform link aggregation?

One good trick (on a tiny network) with link aggregation is to use the same TR ID on both sides of each aggregated link. For example, personally, I would configure the link between Sw31<==>Sw33 as TR3, Sw31<==>Sw34 as TR4, Sw32<==>Sw35 as TR5

When you say "the CAT6 cable running between the swiches", do you mean each inter-switch link is a single CAT6 cable?

parnassus
Honored Contributor

Re: Setup 1810 switches - trunk

Network Topology is clear but, at first sight, its trunking isn't...IMHO a network diagram will be better than hundreds words.

lucver7
Occasional Advisor

Re: Setup 1810 switches - trunk

Attached are a drawing of the network I'm trying to create and the config of the switches.

Just to be clear:

I've tested the CAT6 kabels and they are OK. There is a single CAT 6 cable running between the switches.

When I connect a tagged port to an untagged port, the connection is active. If I do the same with the same cable between 2 tagged ports, they  stay down.

I've tested the whole setup on my desk, and everything works fine (i.e. I get an ip in the correct range from the router if I connect to any of the untagged ports).

I've tried to configure the tagged ports as static and with LACP.

Tnx for your time. I appriciate your help!

Luc

 

Vince-Whirlwind
Honored Contributor

Re: Setup 1810 switches - trunk

You don't need to use Static or LACP, because you don't have any trunks.

If you get rid of all the Trunk config, you will have fewer variables and disctractions in troubleshooting what your issue is.

If it works fine on your desk, but not in production, then the problem is with whatever is different between your desk and production - the cabling?

lucver7
Occasional Advisor

Re: Setup 1810 switches - trunk

Thanks for the help. I do need trunks however, the IP's on the drawing are the IP's of the switches.

What I need is a guest and an admin network running over the switches. (192.168.1.0/24  and 192.168.2.0/24)

I will double check the cabeling though.

Luc

Vince-Whirlwind
Honored Contributor

Re: Setup 1810 switches - trunk

If I've understood the information you've provided correctly, you raen't using trunks.

Trunks are for link aggregation, if you have single links between switches, then you don't need any trunk configuration.

lucver7
Occasional Advisor

Re: Setup 1810 switches - trunk

Each switch has two vlan's. The switches are connected with 1 cat6 cable. I thought trunks were ports that can carry traffic between swiched with different vlan's and that they do this by adding a unique identity tag (802.q or ISL)?

How do I configure this without trunk ports an 1 cable which connects the switches?

Thank you for your help.

Luc

parnassus
Honored Contributor

Re: Setup 1810 switches - trunk

Well, in HP/HPE jargon the "Link Aggregation" is also known as "Port Trunking"...that is the CISCO EtherChannel. CISCO calls Trunk what is VLAN 802.1Q Tagging...so there is some confusion when we speak about "Trunk"...read, as example, here and here.

When you need to carry more than a VLAN on the same link (no matter which type of link), in HP world, you need to change the VLAN Port Type (of a Physical Port <- like your case OR of a Logical Port <- like the case of a LAG) from "Access Type" to "Trunk Type"...that's the confusion of terms (Trunk/Trunk) IMHO.

In the HP/HPE world there are basically three VLAN Port Types (that you can associate with a Physical/Logical port):

  • Access
  • Trunk ----> a VLAN Port Type set to "Trunk" is able to (A) Carry multiple VLANs on a single physical link, (B) tag VLAN(s) with IEEE 802.1Q and (C) leave the native VLAN Untagged <-- Which is what you want.
  • Hybrid

Differences are explained in this document.

So basically you can have an Aggregated Physical Ports uplink (a LAG) <-- it's not your case...or you can have just a Single Physical Port uplink <-- that's your case...OK...both uplinks are able to carry multiple VLAN(s) if their VLAN Port Types are set to "Trunk Type":

  • Aggregated Physical Ports uplink (a LAG) -> set (as example) LACP or Static -> go to the BAGG Logical Port and set the VLAN Port Type as "Trunk Type" to assign/permit that link to carry more VLAN(s).
  • Single Physical Port uplink -> set the VLAN Port Type as "Trunk Type" to assign/permit that link to carry more VLAN(s).

It's just a matter of terms.

lucver7
Occasional Advisor

Re: Setup 1810 switches - trunk

Thanks for the very clear explanation!

So, if i've got 2 vlans, 192.168.1.0/24 (vlan 10) and 192.168.2.0/24 (vlan 20)I have to configure i.e. 2 connected switches as follows:

Both: managemet port 4 on vlan 10 (ip of switches is in the 192.168.1.0/24 range)

SW1: port 1 -4 vlan 10 untagged, 5-8 vlan 20 untagged

SW2: port1  -> T,  port 2-4 vlan10 (all untagged), 5-8 vlan20 (all untagged)

SW3: port 1 -> T, port 2-4 vlan10 (all untagged), 5-8 vlan20 (all untagged)

I connect the SW1 port 1 tot SW2 port1, SW2 port 2 to SW3 port 1

Is this OK?

Luc

parnassus
Honored Contributor

Re: Setup 1810 switches - trunk

Focusing on the uplinks only I think you should consider to set each uplink port as VLAN Tagged for all VLAN(s) you want be permitted on that uplink and so permitted between that Switches' pair (do that considering your chain of three - or more - Switches and how the VLAN(s) are distributed/used on those ones).

So a scenario could be (here I used the uplinking schema: Switch "N" port 1 to 2 of the next Switch "N+1" in the chain):

        Switch 1                   Switch 2                  Switch 3 
port 1 <-- uplink --> port 2 / port 1 <-- uplink --> port 2
| | | |
| | | |
VLAN Tagged X VLAN Tagged X VLAN Tagged X
VLAN Tagged Y VLAN Tagged Y VLAN Tagged Y