- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- 2610 Switch VLAN not pingable unless untagged
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2011 12:02 PM
тАО02-17-2011 12:02 PM
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.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2011 03:06 PM
тАО02-17-2011 03:06 PM
Re: 2610 Switch VLAN not pingable unless untagged
Is routing enabled?
Is the original vlan still multinetted?
Can you post a config?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2011 06:00 PM
тАО02-17-2011 06:00 PM
Re: 2610 Switch VLAN not pingable unless untagged
; 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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2011 10:01 PM
тАО02-17-2011 10:01 PM
Re: 2610 Switch VLAN not pingable unless untagged
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2011 11:48 PM
тАО02-17-2011 11:48 PM
Solutionmost (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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-21-2011 05:41 AM
тАО02-21-2011 05:41 AM
Re: 2610 Switch VLAN not pingable unless untagged
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-21-2011 08:03 AM
тАО02-21-2011 08:03 AM
Re: 2610 Switch VLAN not pingable unless untagged
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-21-2011 08:36 AM
тАО02-21-2011 08:36 AM
Re: 2610 Switch VLAN not pingable unless untagged
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-23-2011 02:09 AM
тАО02-23-2011 02:09 AM
Re: 2610 Switch VLAN not pingable unless untagged
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