IP Routing VLAN's

[k3lvin]

I need some assistance with routing between VLAN's with a HP ProCurve 2610 (first time I have had to work with VLAN's so go easy)

These are my 3 VLAN's:
VLAN1 Ports 1-6 Untagged 192.168.0.x/24
VLAN2 Ports 7-12 Untagged 192.168.8.x/24
VLAN3 Ports 13-26 Untagged 220.0.0.x/24

Now how do I configure the switch to route between the three VLAN's?? I have enabled IP routing.

 

[burtsbees]

That's it---"ip routing".

/

tim@tim-laptop ~ $ sudo apt-get install windows
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package windows...Thank Goodness!

 

[k3lvin]

I think I'm missing a step somewhere. I have host A on VLAN1 and host B on VLAN2. Host A can only ping host B if I patch port 6 and 7 together to link the VLAN's together. Is this what you are supposed to do? I thought I was supposed to configure a static route somewhere?

 

[burtsbees]

NO! You'll cause a switching loop if you do that! The vlans in a layer 3 switch are routed and communicate with each other by virtue of being directly connected---the switch backplane, or the switching fabric, is what physically ties the ports together!

Post a config please---let's start there. Also, post the interface stats of the two ports (6 & 7).

/

tim@tim-laptop ~ $ sudo apt-get install windows
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package windows...Thank Goodness!

 

[k3lvin]

ProCurve Switch 2610-24# show running-config


Running configuration:

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


hostname "ProCurve Switch 2610-24"
ip default-gateway 192.168.0.1
ip routing
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
untagged 1-6
ip address 192.168.0.250 255.255.255.0
no untagged 7-28
exit
vlan 8
name "TLAN"
untagged 7-12
ip address 192.168.8.254 255.255.255.0
exit
vlan 220
name "ELAN"
untagged 13-28
ip address 220.0.0.254 255.255.255.0
exit
password manager
password operator

ProCurve Switch 2610-24#

(I have used VLAN1-3 naming to make it easier but as you can see I have configured it slightly differently)

What are the port stats? Do you mean: Switch Configuration > VLAN > VLAN Port Assignment ?

Port DEFAULT_VLAN TLAN ELAN
---- + ------------ ------------ ------------
1 | Untagged No No
2 | Untagged No No
3 | Untagged No No
4 | Untagged No No
5 | Untagged No No
6 | Untagged No No
7 | No Untagged No
8 | No Untagged No
9 | No Untagged No
10 | No Untagged No
11 | No Untagged No
12 | No Untagged No
13 | No No Untagged
14 | No No Untagged
15 | No No Untagged
16 | No No Untagged
17 | No No Untagged
18 | No No Untagged
19 | No No Untagged
20 | No No Untagged
21 | No No Untagged
22 | No No Untagged
23 | No No Untagged
24 | No No Untagged
25 | No No Untagged
26 | No No Untagged
27 | No No Untagged
28 | No No Untagged

Thanks for your help so far

 

[burtsbees]

A few more questions...

1.What is this switch connected to (i.e. the gateway device)?
2.How is the port on the gateway device configured?

those first two questions have little relevance on how the vlans communicate with each other in the same switch...

3.So you're saying that any node in TLAN is not able to ping or communicate in ANY way with any node in ELAN or DEFAULT?
4.Why are you using a routeable address (public non-RFC1918 ip address) range on ELAN?

/

tim@tim-laptop ~ $ sudo apt-get install windows
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package windows...Thank Goodness!

 

[k3lvin]

1. The Switch is connected to a SonicWall PRO 2040 (hardware firewall) This is our gateway on 192.168.0.1

2. We have a default route policy to route any source to our Primary LAN subnet (192.168.0.x) I really did not think I would need to make any changes on our SonicWall to make this work?

3. Yes, any node in its own VLAN can not ping a node in a different VLAN. The only thing it can ping is its own VLAN address.

4. BT (British Telecom) have specified that the IP address must be 220.0.0.x even though it is internal. This switch will be used on our Telecoms network.

220.0.0.x on its own VLAN and does not matter if it can not connect to anything else.

192.168.8.x must be on its own VLAN and have access to our network 192.168.0.x

I have spoken to HP about this, they are as confused as me and said how I have it configured should work fine. On a HP manual for my switch it says "Separate VLANs on the switch can communicate with each other through either IP static routing configured on the switch, or through an external router."

Don't I just need to add in some static routes?

 

[VinceWhirlwind]

I would have a re-read of your 2610 manual. That one isn't a proper layer-3 switch.

Essentially, I think you need to delete your VLANs and any associated VLAN interfaces and IP addresses.

Then, remove "ip routing" and then put it back on. Then re-create your VLANs and VLAN interfaces and IP addresses.

 

[burtsbees]

Three weeks later...

/

Cisco IOS Software, C2600 Software (C2600-ADVENTERPRISEK9-M), Version 12.4(25c), RELEASE SOFTWARE (fc2)
Technical Support:

http://www.cisco.com/techsupport

Copyright (c) 1523-2010 by Cisco Systems, Inc.
Compiled Thu 11-Feb-1539 23:02 by ßµ®†Šß€€Š

ROM: System Bootstrap, Version 12.2(7r) [ÝØÝØMØÑ], RELEASE SOFTWARE (fc1)

Edge uptime is 469¼

 

[k3lvin]

Lol I manage to configure this switch ok in the end BT. All I needed to do was set the clients default gateway to the VLAN address they are in. Then everything could talk to each other. Thanks for all your help