2910 stacked can not access it via IP

[r00dguy]

We got 4 2910's stacked, the commander and only the commander has an IP, when we try to access via PING, web etc we can not get to it, we are directly connected via laptop. Im sure its something simple this is my first time setting HP switches in a stack. This is out of box stack, only thing we done is upgrade to latest firmware, also they are running on the defualt vlan, i do not have any other vlans configured and wondered if i needed to create another vlan....When i take them out of stack i can get to it fine,what am i missing? thank you 

[David_Schwartzs]

Are you absolutely sure that the other three switches:
1) Have no IP address, or at least are assigned different IPs than the commander?
2) That the commander is assigned as a commander (ID 0), and all of the other switches are assigned as members with unique IDs and that none of the other switches are also trying to be a commander?
3) All switches are properly cabled together and there's no looped connection and/or spanning tree is properly configured and enabled to prevent such looped connection from being active?

These are the things I can think of.

The other option would be to perform a reset on each of the switches and start over, using guidance from the 2910's stacking guide:
http://cdn.procurve.com/training/Manuals/2910-ATG-Feb09-6-Stacking.pdf

Just a few educated guesses, there's a lot of really intelligent people on these forums, so hopefully this helps, otherwise I'm sure there's some other folks with some excellent ideas!

[r00dguy]

I will double check monday make sure none have IP's im pretty sure they dont,

How we have them wired, 

pic attached sorry im not that good of drawer lol 

[David_Schwartzs · Accepted solution]

Try disconnecting the long wire from the top of stack to the bottom of stack that you have in purple. If your spanning tree isn't configured properly, that wire could be causing some connectivity issues.

The way you have it wired is best practices, but only if spanning tree is configured properly. Removing that wire is the easiest way to see if that's the current issue.

[r00dguy]

Yep that was it, it made sense after you said it, thanks