Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About TMaki
TMaki
Comes here often
Member since Jun 12, 2024
Thursday
Community Record
6
Posts
0
Kudos
0
Solutions
Badges
Wednesday
Client sampling is set to all interfaces and client tracking on the MX95 is set to use MAC address. I know about the roaming devices thing, and that explains a lot of the events I see in the log, but others are from an AP port to a trunk port and back, or just trunk port to local port to trunk port, which I guess could be connecting a laptop to a hardline? EDIT: I went ahead and swapped MS uplink sampling to exclude uplink interfaces, the B and C switches still see all devices but now they don't see their OWN devices
... View more
Wednesday
Yeah at this point I've come to terms with that, but it's a warehouse environment and 'downtime' to make that kind of change is... hard to come by.
... View more
Wednesday
Inherited this network from a previous engineer, I THINK I know what's going on but I need another set of eyes. We have a small network, an MX95 firewall performing L3 duties, three switches direct-connected to it (A, B, and C), and two more switches downstream from A (A1 and A2). Switch A has access clients as well as the switch A1 and A2 trunks. RTSP is globally enabled, switch A is root-0 and no other device has bridge priority assigned to it, which I think is the root cause for what's going on: Switches B and C see every single device in the network as direct-connection devices, and when I go to check the physical path of a connection it almost always shows me that the device path is device-B/C-MX95 until I refresh a few times, at which point it gives me the correct path (usually something like device-AP-A1/A2-A-MX95). Additionally, there is a LOT of mac flapping going on on the network, most of it occurring between AP ports on switch A and trunk ports either up to the MX or down to A1 or A2 If I'm correct and this is an RTSP issue?
... View more
Labels:
- Labels:
-
Layer 2
3 weeks ago
Hey, @alemabrahao, the status page shows no issues but I'm also experiencing the same outage situation as the OP, cannot access the dashboard and Client VPN is down for my org. Maybe consider not just dropping the status page like it's a definitive source of info when clearly it can be wrong. @PDSKturley thanks for the head's up about Meraki ack'ing issues. EDIT: seems resolved for me, at least.
... View more
© 2024 Cisco Systems, Inc.
