ProCurve 1810-24G VLAN configuration help

[fhturner]

In a home setup involving Crestron home automation/AV control and Lutron lighting control, I'm trying to accomplish the following network segmentation w/ VLANs on an HP ProCurve 1810-24G v2 (but I'm not sure it can be done):

- Currently the network is not segmented and has no VLANs
- I'd like to have the Lutron able to "talk to" the Crestron, but otherwise isolated from the rest of the network
- I'd like for the Crestron to be able to still connect to the Internet and the rest of the network

As far as I can tell, this is very similar to the example given in this well-written guide, but using different hardware, and exchanging the VoIP in the example for my Lutron segmentation:

http://www.smallnetbuilder.com/lanwan/lanwan-howto/30071-vlan-how-to-segmenting-a-small-lan

Is the SRW2008 Linksys switch referred to there doing Layer 3 vs. Layer 2 on the ProCurve, and therefore more capable of doing this? Basically, I'd like to have something like this:

VLAN 1: Default/management
VLAN 2: Data
VLAN 3: Lutron

Port 1: Management [VLAN 1 & 2]
Ports 2 – 19, 21, 23: Main data network [VLAN 2]
Port 20: Lutron controller [VLAN 3]
Port 22: Crestron [VLAN 2 & 3]
Port 24: Uplink to router (AirPort Extreme) [VLAN 1, 2, 3]

I've tried tagging thusly:

VLAN 1 [Default]-- Untagged: 1, 24; Tagged: 2-23
VLAN 2 [Data]-- Untagged: 2-19, 21, 23; Tagged: 1, 22, 24; Excluded: 20
VLAN 3 [Lutron]-- Untagged: 20, 22; Tagged: 24; Excluded: 1-19, 21, 23

However, I'm not able to communicate between, say, the Crestron port (22) and the router (24) or other data network ports (e.g. 5), although the Crestron and Lutron can "talk".


It appears from looking at this thread that I might be out of luck: http://hardforum.com/showthread.php?t=1742558

I've also read through this thread, but can't seem to figure out how to match to my setup: http://hardforum.com/showthread.php?t=1742558

Can I have my VLANs arranged like this and still have some "cross-traffic" so that the Crestron can access the Internet and be visible to other network devices, or is the ProCurve unequipped to do this?

Thanks,
Fred

 

[+Eric]

The procurve can't do routing between VLAN's.

Maybe your router can, but I've never used an AirPort.

EDIT: It looks like AirPort routers don't even support VLANs, so it would appear you can't do any of the things you want to do. VLANS are out of the cards for you unless you get a better router.

 

[fhturner]

The procurve can't do routing between VLAN's.

Maybe your router can, but I've never used an AirPort.

Okay, thanks. Is that what the SRW2008 (in the example link) is doing..."Inter-VLAN routing"? And that the ProCurve does not? I also read something about "GARP VLAN Registration Protocol" that may function like routing between VLANs.

Is the ProCurve limitation due to it being Layer 2 only and such routing between VLANs needs Layer 3 (or something like the GARP VRP)?

Thanks for any add'l info or tips you can provide.

Fred

 

[+Eric]

As far as I can tell, in the article listed the router is dealing with inter vlan routing. The SRW2008 also doesn't appear to be capable of routing between VLANS on its own.

 

[+Eric]

BTW, in case you missed it, your router appears to lack support for VLAN's. Meaning, that until you get a better router, VLANs aren't going to really work for you.

 

[bmh.01]

The SRW2008 is what is now called a "Cisco" SG300 switch it's decent enough for home use and will do static L3 routing.

GVRP is a layer 2 protocol that lets switches dynamically share the vlans attached or configured on them so you don't have to manually configure that half of it. It's beside the point for what you want and only something to consider if adding several switches which will have common vlan(s) connectivity.

http://en.wikipedia.org/wiki/Multiple_Registration_Protocol

 

[fhturner]

The SRW2008 is what is now called a "Cisco" SG300 switch it's decent enough for home use and will do static L3 routing.

GVRP is a layer 2 protocol that lets switches dynamically share the vlans attached or configured on them so you don't have to manually configure that half of it. It's beside the point for what you want and only something to consider if adding several switches which will have common vlan(s) connectivity.

http://en.wikipedia.org/wiki/Multiple_Registration_Protocol

Okay, thanks. Just out of curiosity, what about the SRW2008 (SG300) from the example makes it able to separate data & VoIP into VLANs, yet still allow the Asterisk server to be reachable by the data network? Would that be the "static L3 routing" you mention or something else?

Also, doesn't it seem extremely limiting to not have the ability on the ProCurve to selectively let ports talk to one another? Seems to me like if you're going to go to the trouble of designing/providing a managed switch, that's a pretty basic desired behavior to have...

Thx,
Fred