NetApp FAS2240-4 with DS4243 Installation Notes: Part 1/2 - Basic Setup

Part 1/2 - Basic Setup

The following post contains some notes created for installing a FAS2240-4 (HA Pair) with DS4243 shelves. This mainly covers the updating software and firmware piece after powering up the shelves and controllers including: initial setup, upgrading Data ONTAP 7-Mode software to version 8.1.2, upgrading Service Processor firmware to 2.1.1, upgrading disk shelf firmware on the FAS2240-4 IOM6E’s to 0121, and DS4243 IOM3’s to 0152.

0. Preliminary Steps

i. Rack and stack the FAS2240-4 and DS4243’s as per provided cabinet diagram - check the serial numbers on the shelves for identifying stacks and order of installation
ii. Cable the FAS2240-4 and DS4243’s as per provided cabling diagrams (front-end connectivity, back-end SAS cabling and ACP cabling)
iii. Power on the shelves and set the shelf ID’s as instructed
iv. Connect to the serial port of both controllers, and power on the controller shelf checking the shelf ID is 00

As an example, we can consider a layout as below:

Shelf ID 00: FAS2240-4 (4U) - topmost unit
Shelf ID 01: DS4243 (4U) - middle unit
Shelf ID 02: DS4243 (4U) - bottom unit

Note: NetApp recommends to avoid numbering external shelves from 00 to 09, but if you’re requested to use 01, 02, 03, ... , that’s okay and we can sort of make an exception with the FAS2240 since it is a shelf in itself unlike the grander FAS 3XXX and 6XXX's.

1. FAS2240-4 initial Setup

Controller A or 1 (Top)

The FAS2240-4 controller should autoboot into the setup script, if it sits on the LOADER-A prompt then:

LOADER-A> setenv AUTOBOOT true
LOADER-A> boot_ontap

On first boot, the NetApp filer will automatically boot into the setup script. What we do in the initial setup doesn’t really matter; the setup can be re-run at any time by simply typing setup from the ONTAP CLI.

Information for Setup

Most essential is the Service Processor, as long as this is configured, pretty much everything else can be done remotely at a later stage:

Service Processor IP, Subnet Mask, Default Gateway

Note: You will need at least one IP address for e0a, e0b, e0c, e0d, or e0M – otherwise the setup script will loop back to asking for an IP from e0a… A tip – if you’re not configuring any of these for the customer, and just doing the SP – is to enter an IP for e0a, and then do an ifconfig e0a later.

An example FAS2240 setup prompts are below:

Please enter the new hostname: CTR-1
Do you want to enable IPv6: n
Do you want to configure interface groups: n
Please enter the IP address for Network Interface e0a: {RETURN}
Please enter the IP address for Network Interface e0b: {RETURN}
Please enter the IP address for Network Interface e0c: {RETURN}
Please enter the IP address for Network Interface e0d: {RETURN}
Please enter the IP address for Network Interface e0M: {RETURN}
Please enter the netmask for Network Interface e0M: X.X.X.X
Would you like to continue setup through the web interface: n
Please enter the name or IP address of the IPv4 default gateway: X.X.X.X
Please enter the name or IP address of the administration host: {RETURN}
Please enter timezone: {RETURN}
Where is the filer located: Site Address
What language will be used for multi-protocol files: {RETURN}
Enter the root directory for HTTP files: {RETURN}
Do you want to run DNS resolver: n
Do you want to run NIS client: n
Would you like to configure the SP LAN interface: y
Would you like to enable DHCP on the SP LAN interface: n
Please enter the IP address for the SP: X.X.X.X
Please enter the netmask for the SP: X.X.X.X
Please enter the IP address for the SP gateway: X.X.X.X

When you are satisfied that all the entries are correct, type reboot to apply the changes

Note 1: The SP and e0M exist on the same interface
Note 2: e0M needs to be on a different subnet to the data network interfaces
Note 3: “Always configure SP. Don’t configure e0M unless SP is connected to a dedicated management network.”

Image: The Remote Management RJ45 port hosts both e0M and the SP

Controller B or 2 (Bottom)

Repeat the above.

2. (Optional) Verifying the System

Using SLDIAG (System Level Diags)

To run diagnostics before handing the system over to a customer, use SLDIAG (if AUTOBOOT is set, you will need to interrupt the boot) from the LOADER> prompt. At the LOADER> prompt type boot_diags and from the *> prompt, we can execute the sldiag command.

*> sldiag
*> sldiag version show
*> sldiag device types
*> sldiag device run -dev mem
*> sldiag device status
*> sldiag device status -long
*> halt
LOADER> boot

Using Config Advisor (Wire Gauge)

Download and install the Config Advisor (Wire Gauge) GUI tool, to run diagnostics and verify cabling.

Using System Manager

Download and install the System Manager GUI tool. System Manager 2.1 includes the Network Configuration Checker too.

Using the CLI

Verify and install licences (e.g. cf license is required before a cf enable):
CTR-1> license
CTR-1> license add XXXXXXX

Verify failover status…:
CTR-1> cf status
CTR-1> cf enable
CTR-1> cf takeover
CTR-1> cf giveback
CTR-1> cf disable

Verify disk paths and aggregate:
CTR-1> storage show disk -p

Verify aggregate:
CTR-1> agg status -f

Verify Service Processor (login username=naroot and same root password):
CTR-1> Ctrl+g
SP CTR-1> sp status
SP CTR-1> system sensors
SP CTR-1> system acp show
SP CTR-1> system acp sensors show
SP CTR-1> exit

Verify Maintenance Mode:
Ctrl+C to interrupt the boot sequence and option 5 to boot into Maintenance mode:
*> sasadmin shelf
*> aggr status
*> disk show -a
*> halt
LOADER-A> boot_ontap
CTR-1> environment status
CTR-1> disks show -n
CTR-1> version -b
CTR-1> version

3. Assigning Disks

CTR-1> options disk
CTR-1> options disk.auto_assign off
CTR-1> options disk
CTR-1> disk show -n
CTR-1> disk assign {disk_name}
CTR-1> disk assign all
Note: In 7-mode, this disk is assigned to whatever controller the command is run from!

If a spare disk needs to be unassigned you can use:

CTR-1> priv set advanced
CTR-1*> disk show
CTR-1*> disk remove_ownership {disk_name}
CTR-1*> disk show -n
CTR-1*> priv set

Note: Alternatively, can use disk reassign –s old_sysid –d new_sysid

Tip: If there is a requirement to have all odd disks assigned to the top controller, and even disks assigned to the bottom controller, and the unit powers up only to find the internal shelf disks are assigned the wrong way around, you can just halt the controllers and swap the heads around. The LOADER-A prompt stays with the topmost controller in a FAS2240 (can do a halt after swapping the heads to confirm this.)


Post a Comment