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 nateynate
nateynate
New here
Member since Feb 12, 2023
Feb 13 2023
Community Record
4
Posts
0
Kudos
0
Solutions
Feb 13 2023
5:14 AM
@cmr : currently the 9500 and 9k switches are not monitored in the dashboard. Also, we for sure use port-channels on the 9500 at least to the two meraki stacks, because there are two 9500s configured together for redundancy, and each meraki stack has a connection into the core 9500. Sounds like I will just have to continue to deal with inaccurate data for the time being. My setup doesn't seem like an edge-case. It's not very complicated.
... View more
Feb 12 2023
11:54 AM
Correct, the 9500 is the core, and the RSTP root. All other switches are connected to the 9500 for redundancy. The two MS225-48fp stacks have two connections each to the core, and each of the other smaller idfs (single switches) have a single connection to the core. VLANs are distributed to from the core outward to all switches, as this is a small corporate environment with a necessity of having most all VLANs available at each IDF for clients. It would be difficult to create a "sub-core" as the Meraki infrastructure is designed for client access. I could move the connections theoretically for the other IDFs into the Merakis, but that presents other problems like not having enough port density in the "sub-core" Meraki's for redundancy. The idea with this design was easily manageable client access side, with a robust core that also serves the local datacenter.
... View more
Feb 12 2023
9:45 AM
Yes. There is no L3 meraki device, and no MX device. The Cisco 9500 is the core L3 swtich and handles routing. Its a very simple network.
... View more
Feb 12 2023
9:23 AM
Anyone else see wildly inaccurate client data on the "Clients" page of the dashboard? My clients, almost always show on an incorrect switch, usually on the up link port. ie. ClientA, which is workstation plugged in to IDF1-02, shows connected to IDF5-01 (not at all the correct switch). This is super frustrating and essentially makes the client page on the dashboard useless. We also see inaccurate client data.. ie. a computer named ComputerA, which has not physically been plugged in for over a year, shows connected, yet the MAC address is another device on the network. We have a very simple deployment: Cisco 9500 core switches (pair) Cisco 9k TOR switches (two set up in a pair) Two Meraki Stacks (MS225-48FP) both connected directly to core Four other single switch deployments, all connected directly to core +10 WAPs connected directly to Meraki switches No other switches in the network, all clients are connected to Meraki switches or APs, with the exception of data-center things that are connected to the 9k stack.
... View more
Labels:
- Labels:
-
Administrators
© 2024 Cisco Systems, Inc.
