Jump to content

Recommended Posts

Posted

Hi Guys

 

We have a HP 2610-24 POE switch that recently needed a VLAN on port 28 (Fibre), we put it on no problem all works fine, intill it turns off and then we always have to retag the port. I can't seem to find a 'save' button any ware. The other vlans are fine but the one on 28 always needs re-tagging when the power comes back on. Any help will be great.

 

Thanks

Posted
Well we did what you said, I can't remember the wording to the letter but basically saying successful, restarted the device and it lost its vlan again (and also the clock)
Posted
HP Procurve lifetime warranty, don't be afraid to use it.

 

We do use it, but it is the day before we break up for over a week!, might have to wait in till Easter time to replace the switch if it keeps going it.

Posted (edited)

Was it originally config through the browser or telnet? Can you post your running config. Type Sh run in to telnet then copy paste out.

 

Try removing the vlan from the switch

Config t

no vlan #

Wr mem

 

Reboot ( you shouldn't have to do this to commit changes)

 

Telnet on again

Config t

Vlan #

Name useful name

Tagged 28

Untagged 1-24 (example)

Wr mem

 

Sh run (show running config to confirm the setting is there)

 

Reboot

Edited by dapaulio
Posted

Another thought is have you got a trunk set up on the switch which includes port 28.

If so you won't/shouldn't be tagging the port you would need to tag the trunk.

Sh run will confirm what port/trunk the other vlans use. And also what the trunk Id is for you to tag

Although one fibre is plugged in I have seen switch trunks set up on both fibres ports and multiple gig up links and not all of them are utilised.

You can also check your switches higher in the network. Eg core switch. confirm the fibre is not set up in a trunk there also.

Posted

I'd suggest 2 reasons behind the issue:

 

Incorrect tagging so doesn't save OR

A firmware issue - so check on the latest.

 

Over the years I have discovered minor firmware issues which have resulted in being send an updated version with fixes.

Posted

are you doing it

 

CLI

GUI

OR Menu

 

I would go with "Menu" as GUI has more bugs than london zoo insect house.

CLI sometimes does not give proper feedback.

 

Menu also updates the startup config realtime.

 

Also check if the bootloader is loading something othert than the startup config, I can't remember if Procurve supports different startup configs.

 

TT

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...