Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About MrMarco
MrMarco
Comes here often
Member since Jul 10, 2024
Oct 30 2024
Community Record
5
Posts
0
Kudos
0
Solutions
Badges
Sep 24 2024
3:06 AM
Hi WW, Switch2 of stack B reports Switch1 as Root via the port connected to Switch2
... View more
Sep 23 2024
4:55 AM
Hi Philip, to answer your questions: * Forgot to put it in the image, but the Core switch 1 is configred as an L3 switch with VLAN gateways, the Core switch 2 is the warm spare for this. Switch 1 and Switch 2 are linked together with an aggregate trunk * Link speeds are the same for the ports, and I cant give the stack members separate STP priorities * Tried both port cycle (shut/no shut of port the Meraki way) and rebooting the switch stacks * VLAN 1 is not the native VLAN on the trunks, but is allowed on all Trunks. All trunk ports are configured the same (Native VLAN 900, allowed VLAN 1-1000) * Configured no other spanning-tree features besides giving priorities to the switches so the correct Root is elected.
... View more
Sep 23 2024
3:33 AM
Hi, I need some help figuring something out with STP. My environment is still begin setup up, consists of the following Core switch 1 - Root bridge priority 0 Core switch 2 - priority 4096 Stack A - 2 switches, switch connected to the core switch 1 primary Stack B - 2 switches, switch connected to the core switch 1 primary Stack C - 2 switches, switch connected to the core switch 1 primary Single meraki switches Everything is connected redundanty, so the single meraki switches have a connection directy to both core switches, designating the corrects for spanning-tree (Block to SW002, designate port to SW001 as active) My stacks however, show unexpected behaviour. For all the stacks the primary (active) switch is connected to SW001 and the secondary (member) switch connected to SW002. STP however decides to STP block the port on the active switch to SW001 and use the SW002 as shortest path to the root bridge (SW001). This behaviour is seen on 2 out of 3 stacks. Anyone got any pointers on how to troubleshoot this behaviour, or correct the situation?
... View more
Aug 21 2024
4:09 AM
I checked the firewalls, no blockades there. Maybe because I try to assign the switch an IP address as management IP where the switch itself is the gateway for? When I go to to Tools page and use the Management Gateway IP for the ping to dashboard.meraki.com I can reach it. The second switch is connected to this primary switch, using it as a gateway on the Mnagement VLAN and connecting to Meraki Dashboard withouth issues.
... View more
Aug 21 2024
2:50 AM
Hi. I have an issue that one of my 9300-M does not want to have a statically assigned IP address in my management VLAN. This unit is the Primary in a warm spare and has L3 interfaces configured with also the management VLAN gateway (VLAN140). It is a test setup. I have a firewall interface in VLAN100 where both my 9300-M are connected to. The 9300-M has an interface in that VLAN with a default route pointing to the firewall for all networks. The secondary 9300-M accepts the Management VLAN IP address, but the primary 9300-M refuses to get it statically assigned IP and stays on DHCP in VLAN100. Anyone got any pointers on to why the device refuses to get an IP address in VLAN140? Is it because the switch itself is the gateway for that management network?
... View more
Labels:
- Labels:
-
Interfaces
© 2024 Cisco Systems, Inc.
