Planning Hybrid Campus LAN Architectures with Cloud Management – Meraki Switching Design and Recommendations – Cisco Meraki

Designing a campus LAN is not a one-size-fits-all task. The scale can vary from a simple setup with a single switch and wireless access point at a small site, to a complex, multibuilding structure with high-density wired and wireless requirements. The deployment may demand high availability for network services with a low tolerance for risk, or it may allow for a fix-on-failure approach with acceptable service outages for a limited number of users. Factors like network capacity needs, device capabilities, compliance requirements, and organizational priorities typically drive the choice of platforms.

The Meraki document “Hybrid Campus LAN Design Guide (CVD)” at https://documentation.meraki.com provides a pre-validated design and deployment guide for a Hybrid Campus LAN, incorporating both Cisco and Meraki platforms. It covers various design guidelines, topologies, technologies, configurations, and considerations relevant to creating a highly available campus switching fabric. The guide also directs readers to general design best practices for Cisco Hybrid Campus LANs. Figure 7-6 illustrates a Hybrid Campus LAN architecture with Meraki and cloud managed Catalyst.

Note

The “Additional Reading” section at the end of this chapter provides the full URL for every article that is cross-referenced in this chapter. Alternatively, you can search for the article title at https://documentation.meraki.com to locate it.

Figure 7-6 Example Hybrid Campus LAN Architecture

Cisco offers various monitoring solutions, such as Cisco DNA Center and the Cisco Meraki Dashboard, that can provide comprehensive monitoring capabilities for Catalyst switches. These platforms collect data from the switches, analyze it, and present it in a centralized dashboard, enabling network administrators to monitor Catalyst switches remotely.

When using Catalyst switches with Meraki, there are two approaches to integration: cloud-monitored and cloud-managed. These differ slightly in their capabilities and operation, which we will talk about briefly here.

Cloud-monitored Catalyst switches: These switches are traditional on-premises switches that can now be monitored through the Meraki cloud, as depicted in Figure 7-7. Administrators can gain visibility into the switch’s status, performance, and some level of configuration. However, the primary management and configuration of these switches is typically done through the on-premises Cisco DNA Center rather than the cloud.

Figure 7-7 Cloud Monitoring on Catalyst 9000 Series

Cloud-managed Catalyst switches: These switches are either migrated from on-premises managed or preconfigured from the factory to be fully cloud-managed. As shown in the example in Figure 7-8, they are provisioned, configured, and monitored entirely through the cloud-based Meraki Dashboard. Administrators have complete control over the switch’s configuration, policies, ability to deploy firmware updates, and full device monitoring. The Dashboard provides a comprehensive view of the switch, enabling centralized management, advanced analytics, and troubleshooting capabilities.

Figure 7-8 Cloud-Managed Catalyst 9000 Series

It is important to note that the availability and features of cloud monitoring and cloud management may vary depending on the Catalyst switch model and software version. We recommend consulting Cisco documentation or contacting Cisco support for detailed information on the cloud-based capabilities available for your Catalyst switches.