07-03-2019 12:42 PM
Hoping you can help- I configured an sg220-50P - sub-net ip address, default gateway, added vlans, shipped it to site. When switch is patched into a stack of 4 SGE2000P switches, (Ethernet to Ethernet link lights light) I browse to the static IP of the new switch, it won't connect- (I am on the same subnet). I have the local smart hands connect to switch, browse to it's IP and log in, no problem. Plugged into that switch, you can't ping the 2000P stack- nor can you ping the 220 when from the 2000P stack-
Because of time constraints, I could not fart around with it and sent a used backup 2000P configured the same way connected it the same way and all performed as normal.
They are sending the switch back, and I have another deployment for which I would like to use it- any ideas on what may be going on?
I had a similar problem before, but it was being cause by an SG350 in the works that was shutting off ports- This is not the case here-
I had to go under port security and unlock and switch to "classic lock"
Ideas?
07-03-2019 01:07 PM
Hello,
to my best knowledge, the SG220 cannot be stacked, these are standalone switches only. You can configure a trunk between them, obviously, but not stack them...
07-03-2019 01:12 PM
I am merely trying to cascade switch to another switch- I have done it many times. Not a stackable switch, that's correct.
07-03-2019 01:13 PM
..and I have to make all the ports trunks to program VLANs etc- weird issue.
07-03-2019 02:14 PM
Hello,
how do you have the trunk configured ? Are you using only the default VLAN 1 ? I think on the trunk you still need to explicitly allow any other VLAN (switchport trunk allowed vlan add x)...
07-08-2019 06:21 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide