Is there a way to tag all vlans on a port on an HP Procurve, without typing them all out?

I'm implementing eight new HP procurve switches.  In configuring them and doing all the tagged/untagged commands, I'm hoping to find a simpler way to tag all the vlans to certain ports.

We are putting some access points on some of the ports (differs for each switch). Since the APs handle multiple SSIDs and VLANs, I need to have those ports accept tagged traffic for all VLANs.  On a Cisco switch, it's simple.  Set it as a "Cisco trunk port" and you're good.  For HP, you need to manually allow the tagged traffic on the ports for each vlan.  That's fine, but I'm hoping there is a simpler way to allow ALL VLANs on a port, and not have to type out each VLAN.  This inevitably leads to forgetting one, misstyping one, and much frustration.

So, currently, this is roughly what I do to set it up like Cisco (with made up VLANs):

config term
int 2-9 (interface ports 2-9)
tagged vlan 1,4,6,12,20,30,50,80,130,210

I don't want to type out that VLAN string every time I configure a switch or add a new "trunk" port.
I've tried the following, but neither work:

tagged vlan 1-210
  this one fails, saying vlan 2 doesn't exist

tagged vlan all
  this one fails with unkown input: all

Any ideas?
Who is Participating?

Improve company productivity with a Business Account.Sign Up

Don JohnstonConnect With a Mentor InstructorCommented:
Sadly, no.  You may find managing it with the web-based GUI is easier and less error prone, but I don't see that much of an improvement using the GUI.
davebuhlAuthor Commented:
Thanks Don, that's what I feared.  I had heard the web interface was fairly easy to use, but, so far, I haven't found anything that is faster or easier to do with the web interface.   It may just get a little getting used to.
Don JohnstonInstructorCommented:
Yeah.  It's just different.   I'm from the Cisco side and things like this are definitely different.  But I had an HP guy one time tell me about something we do on Cisco switches was more work than the same task on an HP (can't remember what it was now) and he was right. So I guess it cuts both ways.
NEW Internet Security Report Now Available!

WatchGuard’s Threat Lab is a group of dedicated threat researchers committed to helping you stay ahead of the bad guys by providing in-depth analysis of the top security threats to your network.  Check out this quarters report on the threats that shook the industry in Q4 2017.

Have you tried trunking the ports to be used for the AP's?
You can then use the command:
port trunk permit vlan 1 to 210
I would try to find out whether you could use the GVRP - protocol in connection with the AP's.
Between the switches you can use this protocol to set up links with the relevant vlans.
Don JohnstonInstructorCommented:
szichen: The commands you're referring to are for A-Series switches.  The switch in question appears to be an E-Series switch which use different commands and have different terminology.
davebuhlAuthor Commented:
Correct, I'm implementing eight Procurve 2530 POE switches, both 24 and 48 port.

So for the A-series, a "trunk port" is a Cisco type, vlan trunk port, but the E-series uses "trunk port" as the aggregation of multiple ports (etherchannel)??  Now that's messed up if you ask me.
Don JohnstonInstructorCommented:
Yep.  :-)
the way i prefer to configure vlans on a Procurve (E-switch) is by way of MENU interface ( in CLI type menu - configure.. ) .
here you will have a nice tabular setup with  ports X vlans
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.