Switches, Hubs, and Modems
cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to add stack member: No response

Domenico Viggiani
Super Advisor

Unable to add stack member: No response

Hi,
I'm unable to create a stack between two Procurve 2650 switches.
I know that it is the simplest thing in the universe and that I manage tons of other devices, but now I'm able only to get:
Unable to add stack member: No response
when I add a member from commander.
Any help?
4 REPLIES
Antonio Milanese
Trusted Contributor

Re: Unable to add stack member: No response

Hello Domenico,

are switches:

a) up to the same firmware rev
b) in the same network id /bcast domain (maybe mispelled submask ?)
c) members of the same primary vlan on uplinks
f) "link-test switch_MAC", "link-test vlan primary_VID switch_MAC" of switch positive
e) "show stack all" show the candadite MAC

Regards,
Antonio


Domenico Viggiani
Super Advisor

Re: Unable to add stack member: No response

Ciao,
> up to the same firmware rev
Yes

> in the same network id /bcast domain
> (maybe mispelled submask ?)
No, contiguous IPs and same netmask

> members of the same primary vlan on
> uplinks
Yes, VLAN_4

> "link-test switch_MAC"
> "link-test vlan primary_VID switch_MAC"
> of switch positive
Positive only the second!!!

>"show stack all" show the candadite MAC
Yes

Thanks again
Antonio Milanese
Trusted Contributor

Re: Unable to add stack member: No response

Hi Domenico,

my guess is:

a) you have not configured the vlan_4 as primary vlan so it's still the default one (DEFAULT_VLAN with VID 1)

b) VLAN_4 has the network id / IPs which you use to define stacking

c)ports between switches are't carrying VID 1 neither tagged nor untagged (first link-test failed)

as per documentations stacking operations are allowed only on primary vlan..just type "show vlan" to confirm my supposition.

If yes you should change primary vlan or stacking using default vlan (VID 1).

Regards,

Antonio
Domenico Viggiani
Super Advisor

Re: Unable to add stack member: No response

I was able to solve with non-habitual procedure (reboot, password input, ??...)
Things never seen on 50+ Procurve devices!

Thanks for your patience