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

2610 Switch VLAN not pingable unless untagged

SOLVED
Go to solution
ChopKC
Occasional Contributor

2610 Switch VLAN not pingable unless untagged

I have a 2610 setup with routing enabled and 2 subnets on the same VLAN. Both subnets connect to the same physical port on the switch. The switch is acting as the default gateway for those subnets and it is working correctly.

My problem is that I now need to put each of those subnets on their own VLAN while still allowing them to be routed through the same physical port on the 2610. So I need multiple routed VLANS on the same physical port. When I try to do this only one of the subnets will work because only one VLAN can be untagged. The other VLAN gateway becomes unpingable if I tag the port. It can only be pinged if the physical port I am attached to is untagged. Is this a limitation of this switch (do I need a true layer 3 to do this) or is there some config I'm overlooking.
8 REPLIES
Nic7_1
Occasional Visitor

Re: 2610 Switch VLAN not pingable unless untagged

Are you pinging from another networking device or a PC that supports dot1q encapsulation?

Is routing enabled?

Is the original vlan still multinetted?

Can you post a config?
ChopKC
Occasional Contributor

Re: 2610 Switch VLAN not pingable unless untagged

I am pinging from a PC attached to the port I have programmed. Routing is enabled. VLAN11 and VLAN12 are the ones I need to break into individual VLANS but each subnet within those VLANS come in on the same physical port. If I sit with a laptop on port 12 and change that port from untagged to tagged for VLAN12 then I instantly can't ping the gateway and cannot access the Internet. Here is my config:

; J9085A Configuration Editor; Created on release #R.11.54

hostname "ProCurve Switch 2610-24"
ip default-gateway 10.20.1.1
ip routing
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
untagged 1-10,13-15,17-28
ip address 10.20.1.6 255.255.255.0
no untagged 11-12,16
exit
vlan 12
name "VLAN12"
untagged 12
ip address 10.20.3.1 255.255.255.0
ip address 10.20.100.1 255.255.255.0
ip helper-address 192.168.1.10
tagged 2-3,23-24
exit
vlan 11
name "VLAN11"
untagged 11
ip address 10.20.2.1 255.255.255.0
ip address 10.20.4.1 255.255.255.0
ip address 10.20.101.1 255.255.255.0
ip helper-address 192.168.1.10
tagged 2-3,23-24
exit
ip route 0.0.0.0 0.0.0.0 10.20.1.1
EckerA
Respected Contributor

Re: 2610 Switch VLAN not pingable unless untagged

Ok,
what is behind port 12?
usualy a client can't tag, so it can't work with an tagged port if there is a client an port 12.

hth
alex
Pieter 't Hart
Honored Contributor
Solution

Re: 2610 Switch VLAN not pingable unless untagged

Like ecker said,
most (windows) clients cannot handle tagged packets.
most (windows) Server drivers can be configured to handle vlan's.
In linux it's also possible to handle vlan's.

but back to the problem:
>>I now need to put each of those subnets on their own VLAN while still allowing them to be routed through the same physical port <<<

what do mean here?
just let the switch route traffic from multiple subnets to a single subnet in a single vlan where the client is connected.
isn't that sufficient?
ChopKC
Occasional Contributor

Re: 2610 Switch VLAN not pingable unless untagged

I apologize for not being more clear on my network setup. What I will have (this is an ISP setup) is a customer computer on the 10.10.10.1 subnet and it will be connected to a .1q compliant modem. This modem will connect to other .1q compliant devices and then back to my HP 2610 switch. The HP switch must act as the network gateway for each of these devices. The customer computer will be on 10.20.101.1 for instance and the network devices are on the 10.20.4.1 network and each needs to be on its own VLAN. They also connect to the same physical port on my switch. How can I configure this so that the switch can act as a pingable IP gateway?
Pieter 't Hart
Honored Contributor

Re: 2610 Switch VLAN not pingable unless untagged

I misonderstood your question.

you want two subnets and two vlans internally, connected to a single port with a single vlan and both subnets externally?
like
- vlanA/subnet1 to vlanB/subnet1
and
- vlanA/subnet2 to vlanC/subnet2
that wont work!

The router in your switch wont know if a paacket in subnet1 needs to be sent to vlanA or vlanB (same for the other)

your best choise is to use different vlans/subnets internally than externally.

Then you can route
- vlanA/subnet1 to vlanB/subnet3
and
- vlanA/subnet2 to vlanC/subnet4

is this an option?
ChopKC
Occasional Contributor

Re: 2610 Switch VLAN not pingable unless untagged

What I need is vlan1/subnet1 and vlan2/subnet2 on the same physical port. Is that possible?
Pieter 't Hart
Honored Contributor

Re: 2610 Switch VLAN not pingable unless untagged

>>> What I need is vlan1/subnet1 and vlan2/subnet2 on the same physical port. Is that possible? <<<

look at the posts allready given.
That question is allready answered!
either
- tag all vlans on the connecting ports
- or untag one and tag (any/all) others