IP routing between Vlans on Procurve 2626

[Joshua Engen]

Is it possible to route between vlans on the 2626 using the ip routing function in the 2626 ?

[Mohieddin Kharnoub]

Hi

Yes, the 2600 series support Basic IP routing between its connected Vlans.

http://www.hp.com/rnd/products/switches/switch2600series/features.htm

To look into the configuration of the IP routing:
ftp://ftp.hp.com/pub/networking/software/AdvTraff-Oct2005-59908853-Chap07-IProuting.pdf

Good Luck !!!

[Joshua Engen]

well i seem to be unable to get this switch to route data between vlans. What iam trying to do is isolate 3 different branches of the company being production, sales, and engineering while letting them all access a centeral server / printer.
heres my show run

Running configuration:

; J4900B Configuration Editor; Created on release #H.08.98

hostname "ProCurve Switch 2626"
ip routing
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
untagged 25-26
ip address 192.168.1.252 255.255.255.0
no untagged 1-24
exit
vlan 2
name "Sales"
untagged 1-8
ip address 192.168.2.252 255.255.255.0
tagged 25-26
exit
vlan 3
name "Engineering"
untagged 9-16
ip address 192.168.3.252 255.255.255.0
tagged 25-26
exit
vlan 4
name "Production"
untagged 17-24
ip address 192.168.4.252 255.255.255.0
tagged 25-26
exit
ip route 192.168.2.0 255.255.255.0 192.168.1.1
ip route 192.168.3.0 255.255.255.0 192.168.1.1
ip route 192.168.4.0 255.255.255.0 192.168.1.1

Please let me know where my issue is so i can fix the problem. Thanks in advance.

[André Beck]

Hi Joshua,

using a 2600 as a router is possible, but it doesn't perform too well. I was told once that as soon as it exceeds 128 ARP cache entries (or was it 256?), it will start punting every packet to be routed to the switch CPU, which isn't made for that job. I'm using a 2626 for Internet access routing though, where things are in the low-traffic range and there are just a handful of connected routes, where it seemingly works.

> vlan 1
> ip address 192.168.1.252 255.255.255.0
> vlan 2
> ip address 192.168.2.252 255.255.255.0
> vlan 3
> ip address 192.168.3.252 255.255.255.0
> vlan 4
> ip address 192.168.4.252 255.255.255.0
> ip route 192.168.2.0 255.255.255.0 192.168.1.1
> ip route 192.168.3.0 255.255.255.0 192.168.1.1
> ip route 192.168.4.0 255.255.255.0 192.168.1.1

What is the sense of having static routes for networks where you already have connected routes to?

And the general question #1 here: You have all your access devices' default gateways set up correctly, here to 192.168..252?

Andre.

[Joshua Engen]

Well the issue that iam having is vlans 2-4 need access to vlan 1 but they arent suppost to be able to access each other. Now even with those routes i am unable to ping anything on vlan 1 from any of the other vlans.

If you have any better ideas let me know iam pretty open to more or less anything. Also the total network is less then 100 computers. So iam pretty sure that the 2626 should be able to handle it

[CDTi]

You are using the 2626 as your routing device yes? It is capable of basic routing but don't rely on it too heavily.

From what I can see you are using IP routing command which on it's own will allow routing between all VLAN's without any IP route commands.

Also the IP routes go back to 192.168.1.1 what is this IP address on? Which you specify in your static routes?

Personally I would create a seperate VLAN for your printer (Try to not to use the default VLAN) and do a static route from each of your other 3 VLAN's to that.

Using 25 PC's and 25 IP phones with 10 Misc IP devices I have found a 2650 to be on it's limit routing. My personal experience.

Also upgrade your firmware asap. That is extremely old version.

[Dmitry G. Spitsyn]

Hi, Joshua !

If your server's network card/driver supports 802.1Q (many HP servers do!) you can set up "the server on the stick" by connecting the server to a switch port which is configured as a tagged memeber of users' VLANs. Users of each users' VLAN will see the server by its ip address in that VLAN.
If you disable ip forwarding on the server, users of each VLAN will be segregated from users in other VLANs.

Good luck,
Dmitry

[Joshua Engen]

Okay i have made some changes and heres my show run:
Running configuration:

; J4900B Configuration Editor; Created on release #H.10.50

hostname "ProCurve Switch 2626"
ip routing
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
ip address 192.168.10.252 255.255.255.0
no untagged 1-26
exit
vlan 2
name "Sales"
untagged 1-8
ip address 192.168.2.252 255.255.255.0
exit
vlan 3
name "Engineering"
untagged 9-16
ip address 192.168.3.252 255.255.255.0
exit
vlan 4
name "Production"
untagged 17-24
ip address 192.168.4.252 255.255.255.0
exit
vlan 5
name "VLAN5"
untagged 25-26
ip address 192.168.1.252 255.255.255.0
exit
primary-vlan 5


With this configuration i am still unable to ping anything on any different vlan. And yes i have the default gateways set correctly as per what vlan they are on. Also The Firmware has been upgraded. Any ideas? The Server we are currently using as our login server doesnt have a 802.1Q compatable NIC in it. Iam just currently trying to setup this Vlan service without having to buy any new hardware.

[Matt Hobbs]

Make sure you don't have any firewalls enabled on your client machines. This will stop successful pings.