Yup, spanning tree was definitly the issue. Turning it off resolved the issue. I knew it was something straight foward.
That being said - you're absolutely right. I don't understand STP that much at all, and I'm very hesitant leaving it off long term.
Had some time from my billion hours of public health overtime to play quickly. Forgot about this thread revisit and holy crap spanning tree shows a blockage on any port I test when connecting to another router. Ty so much, will find the command to allow.
I've tried both. I created a switching profile and associated to 0/0/0. I tried access/trunk with all allowed vlans, access vlan 1, native vlan 1. I also tried associating the profile manually, via the gui, via the wizard etc.
Sorry I was devoid of any useful information in my original post LOL (municipal government worker in IT so very busy). I assigned the vlan 1 interface an IP address (10.0.0.11) that's on the same subnet as the gateway of hte other switch (10.0.0.253) but there is absolutely no communication...
Wondering if I bit off more than i can chew.
I performed the initial setup and connected to my existing switch (nothing complicated going on) but I can't even ping the existing switch interface from the S2500 and vice versa. I tried a trunked port, a non trunked port, everything.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.