Link to home
Start Free TrialLog in
Avatar of itnordic
itnordic

asked on

HP Procurve 4000 connectivity

We are having problem with a switch that don't allow any new hardware to connect. When I try to ping from "behind" i.e going through another switch, it works.

But if I connect a pc directly through the switch I am having big problems just getting an ip address. It could take up to ten tries of ipconfig /renew. And when I do get an ip, I can't ping the switch. No reply.

The strange thing is that all the pc's that are connected since before (been working for years) works just fine.

I have tried rebooting the switch as well as updating the firmware to the latest version. I have tried to connect three different pcs to different jacks in the switch, but with the same nonworking result
Avatar of Tim_Jr
Tim_Jr

Any type of switch security on here that you may not be aware of?
Have you made sure the ports you are using aren't "tagged".  
Avatar of itnordic

ASKER

No switch security is enabled. Compared with an identical switch that doesn't have these problems, and all the settings are the same.

I checked vlan and all ports are set as un-tagged, but vlan isn't enabled so it shouldn't matter either way, right?

Is there a way to reset the table and start that part over, without resetting all settings made?
ASKER CERTIFIED SOLUTION
Avatar of Mick Finley
Mick Finley
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Yes, auto negotiation seems to be working allright. I checked the new devices and they are recognized by the switch and there are no errors logged on those ports (I have tried several different ports, so that shouldn't be the problem)

I compared the settings in this switch with those of another, functioning, switch and they are set exactly the same.

The only thing that has ever been changed are the IP settings. The rest is set to factory default. That is what makes it so strange to me

Could it be that the firmware has "frozen" and is unable to accept new connections? I'm thinking that the only thing left to try is to do a reset to factory default.  
It's possible the update went wrong....I checked my 4000s and have IOS version C.09.28.  Only now did I realize another update is available.  Maybe it was more than a couple of months ago that I updated.  Time flys when your breaking things..ha
I don't think there is a default ip address on the 4000 btw.  
Don't think it has anything to do with updating the software. I updated to 09.30 in order to solve this problem.

I can still connect with rs-232 and access the console. But what struck me as odd was that I couldn't update the switch from a pc, but had to update another switch and update the problem switch from there.

The way I see it right now is that I've got to possibilities. Either the software has gotten messed up somehow, or some hardware isn't working. I hope for the first option
I've always updated via tftp through pc.  

I have had the modules go out on me before tho.  
The RJ-45 modules are brand new, but I have got the same problem no matter if I plug in the cable in a new module or one of the old. So if it is a hardware issue I guess it might be the main board screwing with me :-)

I'll do a reset  to factory default just to try it and hopefully that helps
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
On that switch I have 5 modules x 8 jacks and one fiber connection module. Not very much traffic on the switch, mostly business application.

On one of the other switches we've got, I can't connect anything more and there is a much higher bandwidth load. Still no problems.

To me it seems as if the table arent accepting new additions
I reset the switch back to factory defaults and it seems to be working. Thanks for taking an interest in my question
No real solution for this problem. Got some tips to try before I finally reset the switch
Seems resetting the switch didn't solve the problem after all. I have now contacted HP to see if they can help me