Home » Cisco Manuals » Desktops » Cisco NAC3350-PROF-K9 » Manual Viewer

Cisco NAC3350-PROF-K9 Hardware Installation Guide - Page 108

Step 1, To Con an Additional NIC

View all Cisco NAC3350-PROF-K9 manuals

Add to My Manuals
Save this manual to your list of manuals

Page 108 highlights

Configuring Additional NIC Cards Chapter 3 Installing the Clean Access Manager and Clean Access Server • If the NIC card is not recognized by BIOS (for example, for a non-appliance server machine), you may need to adjust IRQ/memory settings as per the manufacturer's recommendations. • Once the NIC is recognized by BIOS, it should be automatically recognized by the software (Linux). If for some reason, the NIC is recognized by BIOS, but not by Linux, then login to the system and run "kudzu". This will bring up a utility that helps you configure the NIC. To Configure an Additional NIC: Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 To verify that the NIC has been recognized by Linux, type ifconfig ethn (where n is the interface number). For example, if adding a NIC to a system that already has two built-in Ethernet interfaces (eth0 and eth1), n is 2 and you enter ifconfig eth2. Verify that the output displays information about the interface including MAC address and transmit and receive counters. This means the interface is recognized by Linux and can be used. Change to the following directory: cd /etc/sysconfig/network-scripts Use vi to edit the ifcfg-ethn file for the interface, for example: vi ifcfg-eth2 Add the following lines into the file-replacing IPADDR, NETMASK, BROADCAST, and NETWORK values with the actual values suitable for your network: DEVICE=eth2 IPADDR=192.168.0.253 NETMASK=255.255.255.252 BROADCAST=192.168.0.255 NETWORK=192.168.0.252 BOOTPROTO=static ONBOOT=yes TYPE=Ethernet Save the file and reboot the system. The network interface is now ready to be used for HA. Note If the NIC card is not recognized by BIOS (for example, for a non-appliance server machine), you may need to adjust IRQ/memory settings as per the manufacturer's recommendations. Once the NIC is recognized by BIOS, it should be automatically recognized by the software (Linux). If for some reason, the NIC is recognized by BIOS, but not by Linux, then login to the system and run kudzu. This brings up a utility that helps you to configure the NIC. Note Static IP addresses must be configured for the CAM/CAS interfaces. DHCP mode is not supported for configuration of these interfaces. See Chapter 4, "Configuring High Availability (HA)"for details on configuring HA. 3-38 Cisco NAC Appliance Hardware Installation Guide OL-20326-01

Section	Page
Cisco NAC Appliance Hardware Installation Guide	1
Contents	3
About This Guide	9
Cisco NAC Appliance Hardware Platforms	15
About Cisco NAC Appliance	15
FIPS 140-2 Compliant and Non-FIPS Hardware Platforms	15
NAC-3315, NAC-3355, and NAC-3395	17
NAC-3315 Serial Number Location	19
Cisco NAC-3315 Front and Rear Panels	19
Front Panel Features	19
Rear Panel Features	20
NAC-3355 Serial Number Location	22
Cisco NAC-3355 Front and Rear Panels	22
Front Panel Features	22
Rear Panel Features	24
NAC-3395 Serial Number Location	26
Cisco NAC-3395 Front and Rear Panels	26
Front Panel Features	26
Rear Panel Features	28
NAC-3310, NAC-3350, and NAC-3390	30
Cisco NAC-3310 Front and Rear Panels	32
Front Panel Features	32
Rear Panel Features	34
Cisco NAC-3350 Front and Rear Panels	35
Front Panel Features	35
Rear Panel Features	37
Cisco NAC-3390 Front and Rear Panels	38
Front Panel Features	39
Rear Panel Features	40
Cisco Product Identification Tool	41
Preparing for Installation	43
Safety Guidelines	44
General Precautions	44
Safety with Equipment	45
Safety with Electricity	45
Preventing Electrostatic Discharge Damage	47
Lifting Guidelines	47
Preparing Your Site for Installation	48
Site Planning	48
Rack Installation Safety Guidelines	49
Four-Post (Partially-Enclosed) Rack	49
Four-Post (Open) Rack	49
Site Environment	50
Airflow Guidelines	51
Temperature and Humidity Guidelines	51
Power Considerations	51
Method of Procedure	52
Shipping Package Contents	52
Failover Bundles	53
Required Equipment	53
Configuration Worksheets	53
Clean Access Manager (CAM) Configuration Worksheet	54
Clean Access Server (CAS) Configuration Worksheet	54
CAS Mode IP Addressing Considerations	55
Rack-Mounting Your Cisco NAC Appliance CAM/CAS	56
Mounting the NAC-3315 Appliance in a 4-Post Rack	57
NAC-3315 4-Post Rack-Mount Hardware Kit	57
Installing the NAC-3315 Slide Rails into a Rack	58
Installing the NAC-3315 Appliance into the Slide Rails	61
Mounting the NAC-3355/3395 Appliance in a Four-Post Rack	63
NAC-3355/3395 4-Post Rack-Mount Hardware Kit	64
Installing the NAC-3355/3395 Slide Rails Into the 4-Post Rack	64
Installing the NAC-3355/3395 Appliance Into the Slide Rails	67
Cisco NAC Appliance Licensing	68
Upgrading Cisco NAC Appliance Software	69
Downloading Cisco NAC Appliance Software	70
Upgrading Firmware	70
Installing the Clean Access Manager and Clean Access Server	71
Overview	71
Important Release Information	72
Installing the Clean Access Manager	72
Overview	72
Summary of Steps For New Installation	73
Connect the Clean Access Manager	74
Install the Clean Access Manager (CAM) Software from CD-ROM	75
Perform the Initial CAM Configuration	76
Configuration Utility Script	76
Access the CAM Web Console	81
Install CAM License	83
Add Additional Licenses	85
Important Notes for SSL Certificates	87
Installing the Clean Access Server	88
Overview	88
Switch/Router Configuration	88
Virtual Gateway Mode Connection Requirements	89
Switch Support for CAS Virtual Gateway/VLAN Mapping (IB and OOB)	90
Determining VLANs For Virtual Gateway	90
Summary of Steps For New Installation	91
Connect the Clean Access Server	92
Install the Clean Access Server (CAS) Software from CD-ROM	92
Perform the Initial CAS Configuration	94
Configuration Utility Script	94
Important Notes for SSL Certificates	103
Cisco NAC Appliance Connectivity Across a Firewall	104
Configuring the CAS Behind a NAT Firewall	106
Connectivity Across a Wide Area Network	107
Configuring Additional NIC Cards	107
Serial Connection to the CAM and CAS	109
Configuring Boot Settings on the Cisco NAC Appliance CAM/CAS	110
Useful CLI Commands for the CAM/CAS	112
CAM CLI Commands	112
CAS CLI Commands	113
CAS CLI Commands for Cisco NAC Appliance	113
CAS CLI Commands for Cisco NAC Profiler	114
Manually Restarting the CAM/CAS Configuration Utility	116
Troubleshooting the Installation	117
Verify/Change Current Master Secret on CAM/CAS	118
Recover From Corrupted Master Secret	118
Network Interface Card (NIC) Driver Not Supported	119
Resetting and Restoring an Unreachable Clean Access Server	119
Enabling TLSv1 on Internet Explorer Version 6	119
Powering Down the NAC Appliance	120
Configuring High Availability (HA)	121
Adding High Availability Cisco NAC Appliance To Your Network	121
Installing a Clean Access Manager High Availability Pair	123
CAM High Availability Overview	124
Before Starting	127
Connect the Clean Access Manager Machines	128
Serial Connection	129
Configure the HA-Primary CAM	129
Configure the HA-Secondary CAM	132
Complete the Configuration	136
Upgrading an Existing Failover Pair	136
Failing Over an HA-CAM Pair	136
Accessing High Availability Pair CAM Web Consoles	137
Determining Active and Standby CAM	137
Determining Primary and Secondary CAM	137
Installing a Clean Access Server High Availability Pair	137
CAS High Availability Overview	138
Failover Events	141
Choosing External IPs for Link-Based Failover	142
CAS High Availability Requirements	142
Physical Connection	142
Switch Interfaces for OOB Deployment	143
Service IP Addresses	143
Host Names	143
DHCP Synchronization	143
SSL Certificates	143
Before Starting	144
Selecting and Configuring the Heartbeat UDP Interface	145
Serial Port High-Availability Connection	146
Configure High Availability	146
Configure the HA-Primary Clean Access Server	147
a. Access the HA-Primary CAS Directly	147
b. Configure the Host Information for the HA-Primary CAS	147
c. Configure HA-Primary Mode and Update	148
d. Configure the SSL Certificate	152
e. Reboot the HA-Primary CAS	153
f. Add the CAS to the CAM Using the Service IP	153
Configure the HA-Secondary Clean Access Server	154
a. Access the HA-Secondary CAS Directly	154
b. Configure the Host Information for the HA-Secondary CAS	154
c. Configure HA-Secondary Mode and Update	154
d. Configure the SSL Certificate	158
e. Reboot the HA-Secondary CAS	158
Connect the Clean Access Servers and Complete the Configuration	158
Failing Over an HA-CAS Pair	159
Modifying CAS High Availability Settings	160
To Change IP Settings for an HA-CAS	160
Upgrading an Existing Failover Pair	161
Configuring High Availability for Virtual Gateway Mode	162
Useful CLI Commands for HA	163
Clean Access Manager	163
Verifying Active/Standby Runtime Status on the HA CAM	163
Clean Access Server	164
HA CAS Configuration Status	164
Heartbeat/Link-Based Connections	164
Link-Detect Interfaces	165
Active/Standby Status	165
Accessing High Availability Pair CAS Web Consoles	166
Determining Active and Standby CAS	166
Determining Primary and Secondary CAS	166
Password Recovery	167
Recovering Root Password for CAM/CAS	167
Recovering Root Password for CAM/CAS (Release 3.5.x or Below)	167
Open Source License Acknowledgements	169
Notices	169
OpenSSL/Open SSL Project	169
License Issues	169

Match case Limit results 1 per page

3-38

Cisco NAC Appliance Hardware Installation Guide

OL-20326-01

Chapter 3

Installing the Clean Access Manager and Clean Access Server

Configuring Additional NIC Cards

•

If the NIC card is not recognized by BIOS (for example, for a non-appliance server machine), you

may need to adjust IRQ/memory settings as per the manufacturer’s recommendations.

•

Once the NIC is recognized by BIOS, it should be automatically recognized by the software (Linux).

If for some reason, the NIC is recognized by BIOS, but not by Linux, then login to the system and

run “kudzu”. This will bring up a utility that helps you configure the NIC.

To Configure an Additional NIC:

Step 1

To verify that the NIC has been recognized by Linux, type

ifconfig eth

(where

is the interface

number). For example, if adding a NIC to a system that already has two built-in Ethernet interfaces (eth0

and eth1),

is 2 and you enter

ifconfig eth2

Step 2

Verify that the output displays information about the interface including MAC address and transmit and

receive counters. This means the interface is recognized by Linux and can be used.

Step 3

Change to the following directory:

cd /etc/sysconfig/network-scripts

Step 4

Use vi to edit the

ifcfg-eth

file for the interface, for example:

vi ifcfg-eth2

Step 5

Add the following lines into the file—replacing

IPADDR

NETMASK

BROADCAST

, and

NETWORK

values with the

actual values suitable for your network:

DEVICE=eth2

IPADDR=192.168.0.253

NETMASK=255.255.255.252

BROADCAST=192.168.0.255

NETWORK=192.168.0.252

BOOTPROTO=static

ONBOOT=yes

TYPE=Ethernet

Step 6

Save the file and reboot the system. The network interface is now ready to be used for HA.

Note

If the NIC card is not recognized by BIOS (for example, for a non-appliance server machine), you may

need to adjust IRQ/memory settings as per the manufacturer’s recommendations.

Once the NIC is recognized by BIOS, it should be automatically recognized by the software (Linux). If

for some reason, the NIC is recognized by BIOS, but not by Linux, then login to the system and run

kudzu

. This brings up a utility that helps you to configure the NIC.

Note

Static IP addresses must be configured for the CAM/CAS interfaces. DHCP mode is not supported for

configuration of these interfaces.

See

Chapter 4, “Configuring High Availability (HA)”

for details on configuring HA.