Cisco NAC Appliance Configuration Quick Start Guide, Release 4.1
Total Page:16
File Type:pdf, Size:1020Kb
Cisco NAC Appliance Configuration Quick Start Guide, Release 4.1 1 Introduction 2 In-Band (IB) or Out-of-Band (OOB) Deployment 3 Add a Clean Access Server 4 Manage the Clean Access Server 5 Set Up DHCP 6 Add a Default Login Page 7 Create a User Role and Local User 8 Configure Traffic Policies for User Roles 9 Require Use of Clean Access Agent 10 Make Agent Auto-Upgrade Mandatory 11 Configure an AV Requirement 12 Test as a Managed Client 13 Configure Authentication Servers 14 User Authentication Test 1 Introduction About Cisco NAC Appliance Cisco® NAC Appliance (formerly Cisco Clean Access) is a Network Admission Control (NAC) product that allows network administrators to authenticate, authorize, evaluate, and remediate wired, wireless, and remote users and their machines prior to allowing users onto the network. It identifies whether networked devices such as laptops, desktops, and corporate assets are compliant with a network's security policies, and it repairs any vulnerabilities before permitting access to the network. Cisco NAC Appliance is a network-centric integrated solution administered from the web console of the Clean Access Manager (CAM), enforced through the Clean Access Server (CAS), and applied on clients through the Clean Access Agent client software. You can deploy the Cisco NAC Appliance solution in the configuration that best meets the needs of your network. The Cisco NAC Appliance is a Linux-based network hardware appliance which is pre-installed with either the CAM (MANAGER) or CAS (SERVER) application, the operating system and all relevant components on a dedicated server machine. The operating system comprises a hardened Linux kernel based on a Fedora core. Cisco NAC Appliance does not support the installation of any other packages or applications onto a CAM or CAS dedicated machine. About This Document Cisco NAC Appliance Configuration Quick Start Guide, Release 4.1 (this guide) assumes you have unpacked, installed, and licensed your Cisco NAC Appliances according to the guidelines in the Cisco NAC Appliance Hardware Installation Quick Start Guide, Release 4.1. Therefore, this guide is intended only to provide instructions for how to use the web administration console of the Clean Access Manager to configure your Cisco NAC Appliance system. It is intended to illustrate the minimum steps required to configure the Clean Access Manager and Clean Access Server in order to test as a network client on the system using the Clean Access Agent via local authentication. For comprehensive configuration information, refer to the Cisco NAC Appliance - Clean Access Manager Installation and Configuration Guide and Cisco NAC Appliance - Clean Access Server Installation and Configuration Guide applicable to your release (e.g. 4.1(1) or 4.1(2)). Both guides are available on Cisco.com under http://www.cisco.com/en/US/products/ps6128/products_installation_and_configuration_guides_list.html. When using the online publications, refer to the documents that match the software version running on your NAC Appliance. 2 In-Band (IB) or Out-of-Band (OOB) Deployment In-Band Except where noted, this guide describes basic configuration required for all Cisco Clean Access systems, whether deployed In-Band or Out-of-Band. Out-of-Band deployment requires additional configuration as described below. Out-of-Band In a traditional In-Band Cisco NAC Appliance deployment, all network traffic to or from clients always goes through the Clean Access Server. For high throughput or highly routed environments, a Cisco NAC Appliance Out-of-Band (OOB) deployment allows client traffic to pass through the Clean Access network only for authentication, posture assessment and remediation. Once a user’s device has successfully logged on, its traffic traverses the switch port directly and no longer passes through the Clean Access Server. With OOB deployment, you can add switches to the Clean Access Manager’s domain and control switches and VLAN assignments to ports using SNMP. To deploy OOB: • Install the latest 4.1(x) release of Cisco Clean Access software on your CAM and CAS(s). • Ensure your product license(s) for your CAM and CAS(s) enable OOB. The Clean Access Server itself is either IB or OOB. A Clean Access Manager that is license-enabled for OOB can control both IB and OOB Clean Access Servers. • Use supported switch models and IOS/CatOS versions for switches you will control through your CAM. For later configuration, you will need to know whether the switch OS supports MAC-notification SNMP traps. Refer to Switch Support for Cisco NAC Appliance for complete details. 2 • Configure your switches. • Configure the CAM to add and control your switches using the Switch Management module of the CAM web console. For more information on IB and OOB deployment options, see the Cisco NAC Appliance - Clean Access Manager Installation and Configuration Guide and Cisco NAC Appliance - Clean Access Server Installation and Configuration Guide. 3 Add a Clean Access Server Note This section and the following configuration sections assume you have unpacked, installed, and licensed your Cisco NAC Appliances according to the guidelines in the Cisco NAC Appliance Hardware Installation Quick Start Guide, Release 4.1. Once you have installed valid licenses and accessed the web admin console, add a Clean Access Server to the Clean Access Manager’s managed domain: Step 1 Go the Device Management module and click the CCA Servers link. Step 2 Click the New Server tab. Step 3 In the Server IP Address field, type the trusted interface (eth0) IP address of the Clean Access Server you want to add. Step 4 Server Location is an optional description of the server. Type a rack location, server type (e.g. NAC-3350) or any other information that identifies the CAS. Step 5 The Server Type sets whether the CAS operates as a bridge or a gateway when added to the CAM. Refer to Table 1 to determine the CAS operating mode as appropriate for your environment, then choose the Server Type from the dropdown menu. After the CAS is added, you can change the Server Type of the CAS, but this will require an Update and Reboot of the CAS. Note The CAM can manage all IB and OOB Clean Access Servers added to its domain, but the CAS itself can only be either IB or OOB. 3 Table 1 Clean Access Server Types Server Type 1 Description Required Configuration Steps Virtual Gateway CAS acts as a bridge between the untrusted network and an Warning For Virtual Gateway (IB or OOB), do not connect the untrusted existing gateway. interface (eth1) of the CAS to the switch until after the CAS is added to the CAM, and VLAN mapping is configured correctly under Device Management > CCA Servers > Manage [CAS_IP] > Advanced > VLAN Mapping. See the applicable Cisco NAC Appliance - Clean Access Server Installation and Configuration Guide for details. • The CAS interfaces must be on a different subnet/VLAN from the CAM. • The trusted (eth0) and untrusted (eth1) interfaces of the CAS can have the same IP address. • The CAS is automatically configured for DHCP Passthrough. Real-IP Gateway CAS acts as a gateway for the • For Real-IP/NAT Gateways, the trusted (eth0) and untrusted (eth1) untrusted network. interfaces of the CAS must be on different subnets/VLANs. • Static routes must be added on the L3 switch/router to route traffic for managed subnets to the trusted interface of the respective CAS(s). NAT Gateway CAS acts as a gateway and The trusted (eth0) and untrusted (eth1) interfaces of the CAS must be on performs NAT services for different subnets/VLANs. the untrusted network. Note NAT Gateway (in-band or out-of-band) should only be used for demo/testing purposes. For production deployments, only Virtual or Real-IP Gateway is supported. Out-of-Band CAS is a Virtual Gateway Virtual Gateway while traffic is in-band for Warning For Virtual Gateway (IB or OOB), do not connect the untrusted authentication and interface (eth1) of the CAS to the switch until after the CAS is certification. added to the CAM and VLAN mapping is correctly configured. • The CAS interfaces must be on a different subnet/VLAN from the CAM. • The trusted (eth0) and untrusted (eth1) interfaces of the CAS can have the same IP address. • The CAS is automatically configured for DHCP Passthrough. • For OOB Virtual Gateway, the CAS management VLAN must also be on a different VLAN than the user or Access VLANs. Out-of-Band CAS is a Real-IP Gateway • The trusted (eth0) and untrusted (eth1) interfaces of the CAS must be Real-IP Gateway while traffic is in-band for on different subnets/VLANs. authentication and • Static routes must be added on the L3 switch/router to route traffic for certification. managed subnets to the trusted interface of the respective CAS(s). Out-of-Band CAS is a NAT Gateway while The trusted (eth0) and untrusted (eth1) interfaces of the CAS must be on NAT Gateway traffic is in-band for different subnets/VLANs. authentication and certification. Note NAT Gateway (in-band or out-of-band) is not supported for production deployments. 4 1. For Out-of-Band Server Types, the CAS operates as a Virtual, Real-IP, or NAT Gateway while client traffic is in-band (passing through the NAC Appliance network) during authentication and certification.Once clients are authenticated and certified, they are considered out-of-band (no longer passing through the NAC Appliance network) and their traffic is allowed onto the access network. Step 6 Click Add Clean Access Server. Troubleshooting If the Clean Access Manager cannot add the Clean Access Server to its managed list of servers: • Make sure the CAS is pingable. If not, the network settings may be incorrect.