Reference Guide

Aruba 600 Series Controllers FIPS 140-2 Level 2 Security Policy|41

Setup and Configuration

The Aruba 600 Series Controllers meet FIPS 140-2 Level 2 requirements. The sections below describe how to place and

keep the controller in FIPS-approved mode of operation. The Crypto Officer (CO) must ensure that the controller is kept in

a FIPS-approved mode of operation.

The controller can operate in two modes: the FIPS-approved mode, and the standard non-FIPS mode. By default, the

controller operates in non-FIPS mode.

Setting Up Your Controller

To set up your controller:

1. Make sure that the controller is not connected to any device on your network.

2. Boot up the controller.

3. Connect your PC or workstation to a line port on the controller.

For further details, see the ArubaOS 6.3 Quick Start Guide.

Enabling FIPS Mode

For FIPS compliance, users cannot be allowed to access the controller until the CO changes the mode of operation to

FIPS mode. There are two ways to enable FIPS mode:

 Use the WebUI

 Use the CLI

Enabling FIPS Mode with the WebUI

The IP address of the controller will be set during initial setup of the controller, as described in the ArubaOS 6.3 Quick

Start Guide. When you connect a PC or workstation to a line port on the controller, you can connect to this IP address

through a Web browser.

To log in with the WebUI:

1. Open a Web browser and connect to https://ip_address.

2. Log in using the username/password set during the initial setup procedure.

3. Go to the Configuration > Network > Controller > System Settings page (the default page when you click the

Configuration tab).

4. Click the FIPS Mode for Controller Enable checkbox.

Enabling FIPS Mode with the CLI

(established during the initial setup procedure), enable FIPS mode using the following commands:

#configure terminal

Enter Configuration commands, one per line. End with CNTL/Z

(config) #fips enable

(config) #exit

#write memory

Saving Configuration...