-
- Monitoring Devices
- Monitoring Wireless Devices
- Creating Monitoring Policies and Thresholds
- Monitoring Alarms
- Monitoring Clients and Users
- Performance Routing Version 3 Based Network Monitoring
- Monitoring Wireless Technologies
- Using Monitoring Tools
- Viewing Performance Graphs
- Troubleshooting
- Monitoring Multiple Prime Infrastructure Instances
-
- Securing Network Services
- Configuring and Monitoring IWAN
- Using Converged Access Workflow
- Configuring and Monitoring Cisco Catalyst Instant Access
- Configuring Application Visibility and Control
- Ensuring Consistent Application Experiences
- Troubleshooting Applications
- Monitoring Microsoft Lync Traffic
- Using Mediatrace
- Cisco Mobility Services Engine and Services
- Configuring the Cisco AppNav Solution
- Configuring WAAS Container
- Working with Wireless Mobility
Cisco Prime Infrastructure 3.1 User Guide
- Updated:
- July 31, 2018
Chapter: Using Converged Access Workflow
- Converged Access Workflow Overview
- Supported Cisco IOS-XE Platforms
- Prerequisites for Converged Access Deployment
- Converged Access Template-Based Deployment
- Guidelines for Entering Configuration Values
- Converged Access Template Field Descriptions
- Entering Configuration Values for Controller-Less Single-Switch Deployment Model
- Entering Configuration Values for Controller-Less Single/Multi-Domain Wireless Deployment Model
- Entering Configuration Values for Controller-Based Single/Multi-Domain Wireless Deployment Model
- Entering Configuration Values for Centralized Wireless Campus Deployment Model
Converged Access Workflow Overview
The Converged Access workflow simplifies, automates and optimizes deployment of various enterprise-class next generation wireless deployment models for campus and branch networks.
Cisco Prime Infrastructure can automate the converged access deployment of wireless networks using converged access components such as Catalyst 3650, 3850, 4500 SUP 8-E switches, and Cisco 5760 Wireless LAN controller (WLC). The catalyst switches can be deployed as Mobility Agent (MA), Mobility Controller (MC), and Guest Anchor controller (GA).
Figure 38-1 illustrates the wireless converged access deployment models.
Figure 38-1 Converged Access Workflow Overview
Single-Switch Small Network Deployment Model
This deployment model assumes single Catalyst 3650, 3850 or 4500 SUP 8-E switch deployed in Access layer in combined MA and MC roles. The Catalyst switches can be deployed in individual standalone system mode or in stackwise redundant supervisor mode.
Controller-Less Single/Multi-Domain Deployment Model
This deployment model consists of multiple sub-domains and allows inter-domain MC peering for end-to-end seamless roaming across sub-domains. The MA switches are deployed in Access layer while the MC switches can be placed in Distribution layer.
Controller-Based Single/Multi-Domain Deployment Model
A large scale converged access campus building is deployed with external 5760 WLC as MC. The Access layer switches are deployed as MA across multiple buildings with centralized 5760 MC. In such large network, multiple 5760 WLCs may co-exist for better load balancing and redundancy. Depending on the roaming requirement across different buildings, the inter-domain mobility peering between 5760 WLCs can be established.
Centralized Wireless Campus Deployment Model
In this deployment model, the switches in Access layer remain in traditional switching mode and wireless communication between Access Point (AP) and WLC is built as overlay network. In large scale campus deployments, multiple 5760 WLCs can be deployed for better load balancing and redundancy. To provide seamless large mobility domains, the inter-domain mobility peering 5760 WLCs can be established.
- Simple Automated Deployment—Simplifies the converged access deployment by automating the device configuration process. Requires only a few deployment specific inputs from the network administrator and pushes the complete converged access configurations to the network devices.
- Error Free Deployment—The template-based configuration used by Cisco Prime Infrastructure avoids manual misconfigurations, making it easier to build/maintain enterprise-wide standardized configurations that are well understood by the network administrator.
- Optimized Deployment—The configuration templates used by Cisco Prime Infrastructure incorporates a large number of Cisco best practice guidelines, improving the deployment quality. Some of the best practice wireless technologies/features that are automatically included in the template are Band-Select, Radio Resource Management (RRM), Fast SSID-Change, CleanAir, and Wireless QoS.
- High Scalability—Supports large enterprises with thousands of branches. It not only reduces efforts to deploy greenfield branches, but also simplifies large scale conversion of traditional Ethernet based branch networks to converged access branches in an error-free way.
Supported Cisco IOS-XE Platforms
The following tables describe the supported Cisco IOS-XE platforms for small, large, and centralized network deployment models.
Prerequisites for Converged Access Deployment
To successfully deploy the Converged Access solution using the Converged Access Workflow, the wired infrastructure of the network should be set for further configuration required for converged access. This section describes the prerequisite configurations for Converged Access Workflow based deployment.
You can view the prerequisites using the click here link in the Before you Begin page in the Converged Access Workflow (Services > Network Services > Converged Access).
- Prerequisites for Layer 2 and Layer 3
- Prerequisites for Server Configuration
- Converged Access Workflow Overview
- Supported Cisco IOS-XE Platforms
- Converged Access Template-Based Deployment
- Guidelines for Entering Configuration Values
Prerequisites for Layer 2 and Layer 3
Table 38-4 describes the Layer 2 and Layer 3 prerequisites, and sample configuration for the Converged Access Workflow. In the sample configuration, the following nomenclature is used to represent the various wireless management VLANs in the MA and MC.
- WM_VLAN - Name of the Wireless Management VLAN
- WM_VLAN_id - ID of the Wireless Management VLAN
- WLAN1_Client_VLAN_Name - VLAN name of WLAN 1
- WLAN2_Client_VLAN_Name - VLAN name of WLAN 2
- WLAN3_Client_VLAN_Name - VLAN name of WLAN 3
- WLAN1_Client_VLAN_id - VLAN ID of WLAN 1
- WLAN2_Client_VLAN_id - VLAN ID of WLAN 2
- WLAN3_Client_VLAN_id - VLAN ID of WLAN 3
Note WLANx_Client_VLAN_id represents all the three client VLAN Ids.
Table 38-4 Layer 2 and Layer 3 Prerequisites for Converged Access Switches for Device Roles MA and MC
Table 38-5 describes the Layer 2 and Layer 3 prerequisites, and sample configuration for GA. In the sample configuration, the following nomenclature is used to represent the wireless management VLAN and Guest VLAN details for GA:
- WM_VLAN - Name of the Wireless Management VLAN
- WM_VLAN_id - ID of the Wireless Management VLAN
- GUEST_VLAN_Name - VLAN name of Guest Anchor Controller
- GUEST_VLAN_id - VLAN ID of Guest Anchor Controller
Table 38-5 Layer 2 and Layer 3 Prerequisites for Guest Anchor Controller
Prerequisites for Server Configuration
– All network-wide catalyst switches and 5760 WLCs must be configured with SNMP.
– The Converged Access switches must be added to the inventory of Cisco Prime Infrastructure. You need to provide SNMP and Telnet credentials to add the devices to the inventory.
– Link Cisco Prime Infrastructure with Cisco ISE engine as external server to centrally monitor end-to-end client connectivity and policy enforcement details.
– All network devices including catalyst switches and Guest Anchor WLC must be configured in Cisco ISE/ACS to enable centralized policy engine function.
– AAA configuration is not required for converged access on individual network devices as it is automatically generated by Converged Access Workflow.
Converged Access Template-Based Deployment
Cisco Prime Infrastructure uses different templates for different deployment models. You need to select the appropriate template-based on your network topology as explained in Table 38-6 :
Table 38-6 Network Topology and Configuration Template Mapping
To deploy a converged access template:
Step 1 Choose Services > Converged Access.
Step 2 Click Next to choose the deployment model.
Step 3 From the Select Deployment Model drop-down list, choose any one of the following options:
Step 4 Click Next to choose the devices to be deployed.
Step 5 Choose the devices and click Next to apply the selected network configuration.
The selected device will be listed out in the left pane, and in the right pane you can configure the templates by entering the values for the Wireless Management, WLANs, Guest WLAN, Mobility, Security, Application Visibility and Control (AVC), and Quality of Services (QoS).
Step 6 Choose the devices individually and enter the Wireless Management configuration values.
Step 7 Click Apply and then Next.
Step 8 Enter the WLANs configuration values that are common to all the selected devices.
By default, the All Selected Devices check box is enabled. You can enter the WLAN configuration values for all the devices at the same time.
Step 9 Click Apply and then Next .
Step 10 (Optional) Enter the Radio configuration values that are common to all the selected devices. By default, the All Selected Devices check box is enabled.
Step 11 Click Apply and then Next .
Step 12 (Optional) Enter the Guest WLAN configuration values that are common to all the selected devices.
By default, the All Selected Devices check box is enabled.
Step 14 Choose the devices individually and enter the Guest Controller configuration values.
Step 15 Click Apply and then Next .
Step 16 Select the individual devices and enter the Mobility configuration values. The Mobility configuration fields will be available in the Converged Access Wizard only for large and centralized network deployments.
Step 17 Click Apply and then Next .
Step 18 (Optional) Enter the Security configuration values that are common to all the selected devices. By default, the All Selected Devices check box is enabled.
Step 19 Click Apply and then Next .
Step 20 (Optional) Enter the AVC and QoS configuration values that are common to all the selected devices. By default, the All Selected Devices check box is enabled.
Step 21 Click Apply and then Next to view the confirmation screen.
The confirmation screen allows you to view the device configuration information before deployment.
Step 22 (Optional) Enter the job name and click the Date radio button to schedule the deployment job.
Guidelines for Entering Configuration Values
This section provides the field descriptions for converged access template and guidelines for entering the global and local configuration values for the following deployment models with specific examples.
- Controller-less single-switch deployment model
- Controller-less single/multi-domain deployment model
- Controller-based single/multi-domain deployment model
- Centralized wireless campus deployment model
- Prerequisites for Converged Access Deployment
- Converged Access Template Field Descriptions
- Entering Configuration Values for Controller-Less Single/Multi-Domain Wireless Deployment Model
- Entering Configuration Values for Controller-Based Single/Multi-Domain Wireless Deployment Model
- Entering Configuration Values for Centralized Wireless Campus Deployment Model
Converged Access Template Field Descriptions
This section contains the field descriptions for converged access template.
Refer Table 38-8 for Guest WLAN field descriptions.
IP address of the Remote Authentication Dial In User Service (RADIUS) server. |
|
Select this in order to enable TACACS based device authentication to access the converged access device. |
|
- Prerequisites for Converged Access Deployment
- Converged Access Template-Based Deployment
- Entering Configuration Values for Controller-Less Single-Switch Deployment Model
- Entering Configuration Values for Controller-Less Single/Multi-Domain Wireless Deployment Model
- Entering Configuration Values for Controller-Based Single/Multi-Domain Wireless Deployment Model
- Entering Configuration Values for Centralized Wireless Campus Deployment Model
Entering Configuration Values for Controller-Less Single-Switch Deployment Model
A small-sized remote branch office or retail store may consists of a single converged access switch (standalone or stack) to provide network connectivity to the wired and wireless users.
For such network designs, the switch integrates both MC and MA functions. These networks may need guest wireless services, as well as common security and network access policy enforcement across all deployed sites.
The network administrator can use Cisco Prime Infrastructure IOS-XE Controller Small Network template to deploy converged access. Figure 38-2 illustrates the reference network for single-switch small network that shows three branch offices. Each site can be independently deployed using the workflow. Alternatively, one deployment workflow can deploy multiple sites. Prime Infrastructure allows you to configure the devices in five WLANs. Figure 38-2 illustrates three WLAN configuration scenario in the single-switch small network topology.
Figure 38-2 Controller-less Single-switch Small Network Model
You must enter the Wireless Management configuration values separately for each device. Table 38-14 describes the Wireless Management configuration values for MA/MC (10.100.1.109) and Guest Anchor (10.99.2.242) in the single-switch small network topology shown in Figure 38-2.
After applying the Wireless Management configuration values, you must enter at least one WLAN configuration values. up to Table 38-15 describes sample configuration of three WLANs for the single-switch small network topology shown in Figure 38-2.
After applying the WLAN configuration values, enter the Wireless Radio configuration values for all the devices at the same time. Table 38-16 shows the Wireless Radio configuration values for MC/MA and GA in the single-switch small network topology shown in Figure 38-2.
Yes (This check box is checked by default and it’s mandatory. You cannot uncheck this check box.) |
|
After applying the Wireless Radio configuration values, enter the Guest Services configuration values for all the devices at the same time. Table 38-17 describes the Guest WLAN configuration values for all the devices in the single-switch small network topology shown in Figure 38-2.
Table 38-18 describes the sample Guest Controller configuration values for MC/MA (10.100.1.109) and GA in the single-switch small network topology shown in Figure 38-2.
After applying the Guest Services configuration values, enter the Security configuration values for all the devices at the same time. Table 38-19 describes the sample Security configuration values for MC/MA and GA in the single-switch small network topology shown in Figure 38-2.
After applying the Security configurations values, enter the AVC and QoS configuration values for all the devices. Table 38-20 describes the sample configuration values for MC/MA and GA in the single-switch small network topology shown in Figure 38-2.
- Prerequisites for Converged Access Deployment
- Converged Access Template-Based Deployment
- Converged Access Template Field Descriptions
- Entering Configuration Values for Controller-Less Single/Multi-Domain Wireless Deployment Model
- Entering Configuration Values for Controller-Based Single/Multi-Domain Wireless Deployment Model
- Entering Configuration Values for Centralized Wireless Campus Deployment Model
Entering Configuration Values for Controller-Less Single/Multi-Domain Wireless Deployment Model
Figure 38-3 illustrates the controller-less deployment model that leverages Catalyst switches for MA and MC roles without depending on an external WLC. This converged access deployment model is suitable for large branches and campus, and can be implemented using Cisco Prime Infrastructure IOS-XE Controller Large Network template.
Figure 38-3 Controller-Less Large Branch Network Model
Enter the Wireless Management, WLANs, Wireless Radio, and Guest WLAN configuration values for all the devices as described in single-switch small network deployment model. Enter the Guest Controller configuration values and Mobility configuration values for MA, MC, and GA for the topology shown in Figure 38-3.
Table 38-22 describes the Mobility configuration values for MA, MC in SPG-1, and GA shown in Figure 38-3.
Repeat the same procedure for MA and MC in SPG-2 as shown in Figure 38-3.
After applying the Mobility configuration values, enter the Security, AVC and QoS configuration values as described in single-switch small network deployment model.
- Prerequisites for Converged Access Deployment
- Converged Access Template Field Descriptions
- Entering Configuration Values for Controller-Less Single-Switch Deployment Model
- Entering Configuration Values for Controller-Based Single/Multi-Domain Wireless Deployment Model
- Entering Configuration Values for Centralized Wireless Campus Deployment Model
Entering Configuration Values for Controller-Based Single/Multi-Domain Wireless Deployment Model
Figure 38-4 illustrates the controller-based single/multi-domain deployment model that leverages the same IOS-XE Controller Large Network template for deploying converged access with an external 5760 WLC as the MC.
Figure 38-4 Controller-Based Large Campus Model
Enter the configuration values as explained in controller-less single/multi-domain wireless deployment model.
- Prerequisites for Converged Access Deployment
- Converged Access Template Field Descriptions
- Entering Configuration Values for Controller-Less Single-Switch Deployment Model
- Entering Configuration Values for Controller-Less Single/Multi-Domain Wireless Deployment Model
- Entering Configuration Values for Centralized Wireless Campus Deployment Model
Entering Configuration Values for Centralized Wireless Campus Deployment Model
Cisco Prime Infrastructure IOS-XE Centralized Wireless template supports traditional wireless deployment model using next-generation 5760-WLC. In this model, any generation Access layer switches are deployed in traditional Ethernet switch mode over which WLC and the APs build an overlay network using CAPWAP Tunneling mechanism.
Figure 38-5 illustrates 5760-WLC based Centralized Wireless deployment using IOS-XE Centralized template.
Figure 38-5 Centralized Campus Network Model
Enter the Wireless Management, WLANs, Wireless Radio, and Guest WLAN configuration values for all the devices as described in single-switch small network deployment model. Enter the Guest Controller configuration values and Mobility configuration values for 5760 WLC in SPG-1 and GA for the topology shown in Figure 38-5.
Repeat the same procedure for 5760 WLC in SPG-2 shown in Figure 38-5. After applying the Mobility configuration values, enter the Security, AVC and QoS configuration values as described in single-switch small network deployment model.
- Prerequisites for Converged Access Deployment
- Converged Access Template Field Descriptions
- Entering Configuration Values for Controller-Less Single-Switch Deployment Model
- Entering Configuration Values for Controller-Less Single/Multi-Domain Wireless Deployment Model
- Entering Configuration Values for Controller-Based Single/Multi-Domain Wireless Deployment Model
Feedback