Hello and welcome. In today's session, we are going to explore the Cisco sassy solution focusing on the integration between Meraki and Cisco Secure Access, as well as the streamlined onboarding process that makes this deployment possible.00:04Our agenda today covers three key areas. 1st, we will provide an overview of the Cisco SASE architecture using Meraki and Cisco Secure Access. Next, we will review design best practices. Finally, we will walk through the configuration steps to successfully complete this integration. Let's begin.00:19This integration seamlessly connects your Meraki SD WAN fabric with Cisco Secure Access. It provides secure, consistent access to the internet, cloud services, and private applications enabling users to work effectively from anywhere. The solution simplifies management by using Cisco Secure Access API keys to automatically provision and maintain secure.00:39Pure IPsec tunnels from your Meraki MX appliances directly into the Cisco Secure Access Cloud.00:59Furthermore, it ensures unified security by providing granular visibility and consistent enforcement of access policies across all your locations. Now, let's talk about the design supported by this integration. When planning your deployment, we recommend aligning your topology with one of Cisco's validated designs. Design A.01:04Cloudspokes and cloud hubs is our cloud 1st approach where all branch traffic routes directly into secure access.01:25Design B, hybrid and cloud hubs, is ideal if you maintain physical data centers for internal resources while routing internet traffic through secure access. Design C, local and cloud hubs, allows for local internet breakout at the branch for specific traffic while securing remaining traffic through the cloud.01:31We encourage you to consult the Cisco Secure Access integration, design best practices documentation to determine which architecture best fits your organization's needs. Now that we have covered the high level architecture and benefits, let's jump right into the integration. Before enabling the Secure Access integration, it is important to determine if your environment.01:48Requirement requires a maintenance window. Please consider the following two questions.02:081st, do you have the secure internet access package only without the SPA package? Second, does your organization require spoke to spoke communication using an MX hub? If the answer to either of these questions is yes, we strongly recommend scheduling a maintenance window before proceeding with the integration. Once you have confirmed your requirements and scheduled any necessary maintenance.02:12We can begin the configuration.02:32Now that we have covered the high level architecture and best practices, let's jump right into the integration. In this section, we will walk through the configuration steps required to complete the Meraki Sassy integration. We will guide you through generating the necessary API keys in Cisco secure access, applying them to the Meraki dashboard, and establish.02:34Publishing your 1st automated sassy tunnels.02:54To start, log into your Cisco Secure Access dashboard. Navigate to the admin menu, and select API keys. Once in the API keys section, click on API keys box and then click add to create a new key. To find the API key scopes and permissions needed for the Meraki.02:58See integration, open the admin section, then integrations and select the MSA scope. Then make sure it is read and write permissions and then click on create key.03:18Cisco Secure Access will generate your API key and key secret. Please save these credentials in a secure location. Once you click accept and close, the key secret will NO longer be visible in the dashboard. Once the API credentials are saved, click on accept and close.03:29Now, log into your Meraki dashboard. Navigate to organization and select integrations under the configure section. On the integrations page, locate and select the Cisco Secure Access integration. The integration page provides details on the various use cases for Meraki space with Cisco.03:46To Secure access. To proceed with the setup, click connect.04:06Review the provided prerequisites to determine if a maintenance window is required for your network, then click next. Enter the API key and key secret you generated from Cisco Secure Access, then click add integration. Once the credentials are verified, a new sassy section will appear in the.04:12Dashboard, this confirms the integration is active. To begin configuring your tunnels, click on sassy, and then select sites.04:32On the Meraki sassy page, click connect Meraki Networks. Select the specific Meraki networks you wish to connect to Cisco secure access. Next, select the secure access region for your connection. We recommend choosing the region closest to your MX appliance location for optimal performance.04:41Click next to proceed. Review your settings and click confirm. After a few minutes, the Meraki side will appear as connected on the sites page, indicating the tunnel to Cisco Secure Access is established.05:03By default, internet traffic does not automatically pass through Cisco secure access as default route learning is disabled. To modify this, click on the name of your Meraki site. Select manage default route. Finally, toggle the configuration to enable default route and click confirm to complete the setup.05:20Thank you for watching this video.05:40
