Procurve 1700-8 Configuration

[Ric_]

I usually buy nice big Procurve 2600-series switches. I've got the hang of setting these up and have three VLANs on each (with the inter-switch links set as tagged ports and the endpoints set as untagged points).

 

I decided that I needed a switch on my testbench that had VLAN capability for testing a few bits and pieces so I bought a 1700-8 for just under £50 from Oliis. I realised that these were very much cut down but they do have 802.1Q VLAN capabilities.

 

My question is... what the hell do I need to set the cryptic buttons to in the interface for the following config?

 

Port 1 - Untagged VLAN 14

Port 2 - Untagged VLAN 14

Port 3 - Untagged VLAN 14

Port 4 - Untagged VLAN 14

Port 5 - Untagged VLAN 14

Port 6 - Untagged VLAN 14

Port 7 - Untagged VLAN 11

Port 8 - Tagged VLAN 11, 12 & 14

[Geoff]

Presumably you've flashed it to the latest firmware? Because if you read the release notes, several Web UI and VLAN related things were bug fixed/clarified.

[DMcCoy]

I can break the vlan config for all Procurves in about 10 minutes. Just set a few vlan and truck options and it never works again!

 

I do everything from the CLI now

[Geoff]

The 1700 series does not have a CLI.

[DMcCoy]

Oh :/

[Ric_]

The software is the latest revision. The attached image shows the settings that I have used.

 

I can access the switch management on VLAN 14 by using an untagged port however if I use tagging on the upstream switch and then try to access the switch via a tagged port, it dows not work

[Ric_]

No takers?

 

I have emailed HP support to see if they can shed any light on the subject :?

[Ric_]

The reply from HP:

 

Dear Customer,

 

Thank you for using Hewlett Packard Customer Service.

 

The management VLAN can only be on the Default_vlan on VLAN1 and name must not be changed.

 

Best Regards,

 

Hewlett Packard Customer Service

 

What sort of use is that? Especially when they give you the option of changing the management VLAN in the interface!!!!!!!!!

[Oops_my_bad]

Oooh that's a bit crap innit.. wonder if you need to buy the full procurve software with all the bells and whistles to go down to that level of config.

 

My colleague has been playing around with 2650's this week and the only way of changing the management VLAN was apparently through the CLI

 

But then again if it's a cheapy switch then perhaps thats just one of the (deliberate) limitations :?

[Ric_]

The 2600-series, 2800-series and 4100-series switches all work in a sensible way (incidentally you can change the management VLAN on them by using the menu in the CLI). I know that this is a ut down switch but the whole point of me buying it was because it had VLAN tagging and I rather foolishly assumed I would be able to re-configure the thing at a later date without doing a factory reset!

 

Why offer you the chance to change it if you can't actually do it?

[Geoff]

incidentally you can change the management VLAN on them by using the menu in the CLI

 

For future forum searchers, the command is:

configure
management-vlan 

 

Why offer you the chance to change it if you can't actually do it?

 

Well, you didn't pay very much for it, so what do you expect? If you're lucky I suppose they might fix this in a future revision of the firmware. Have you asked them further about it?