Building Block

1. Cables required
Network cable
Serial cable
Storage cable
HA cable or 10GBe Network cable
2. Front View
Bezel
Power Led
Attention Led
Controller A and B status Led
HA interconnect ports (c0a,c0b)
Fibre channel ports ( 0c, 0d)
Gigabit Ethernet port ( e0a,e0b)
Remote /node management (wrench icon)
Console port usb port
NVRam led
Controller attention led
SAS port 0a 0b
Few slots for adapter card
3. Cabling controller to switches
1. Management arms to pull like a belt
2. Connect c0a to c0a and c0b to c0b ( AB)
3. Wrench icon cable (connect to switch port)
4. E0a E0b to data switch (isci switch)
( cluster mode ) it will be e1a e2a connect to cluster switch
3. Plug power cord
4. Cable storage ( disk shelves)
## Installing expansion card
sysconfig -v l
sysconfig -v (slot number)
cntrl C choose 5 maintenance mode
## Setting disk shelf id's
SAS - 1-99
00 reserved for internal drives
To change shelf id
1. turn it off
For sas just hold it for long till it blink and then change it
Daisy chaining sas
inport of shelf1 to outport of shelf two ( daisy chain it )
Do it for both A and B

### ACP cabling

This is done with ethernet cables
e0p port to ACP
acpadmin list_all
run -node name1 acpdmin list_all
Note config advisor tool
Config validate and health check tool
- Correctness of hardware installation
- It collects information about connectivity
- It generates reports in pdf , excel
# Service processor and how to use
SP helps with remote management
sp setup
provide ip of sp
sp reboot
Control + g from serial port
naroot and root password
SSH sp to naroot + root password
Basic command
date
version
system powercycle
system poweroff
sp uptime
system console
sp reboot
# how collect perfstat data over ssh
storage image show
On windows
plink + perfstat utility from netapp
Navigate via cli
1.plink ip of netapp
2.perfstat.exe -f <ip> -t 5 -i 6 -l root -s pw:password > log.txt.out
# how to use RLM for hardware issue
Remote lan module ..
login with naroot
type system console
enter root credentials
options autosupport
options.autosuport.to autosupport@netapp.com
options autosupport - is added to send info
options autosupport.transport smtp
options autosupport.mailhost 10.0.0.1
system power status
events all ( low level hardware events)
system log ( log)
rlm test autosupport

# How to collect network trace with pktt

pktt start all -d /etc/crash -b 2 m -s 1000m
pktt stop all
# how to identify faulty disk
sysconfig -r
priv set advanced
blink_on 0a.22 ( to enable blinking )
blink_off 0a.22
storage disk set-led 0d.21 -action blink
if led is fault then blink disk port close by
led_on led_off
priv set off
aggr status -f (7 mode)
storage disk show -state broken
system node autosupport invoke -node cluster -type all -message "replacing disk
nmber"
run config advisor
Controller-to-stack connections: Each storage system controller is
connected to each stack of disk shelves through a dedicated Ethernet port:
- Controller 1/A always connects to the top shelf IOM A square port in a
stack.
- Controller 2/B always connects to the bottom shelf IOM B circle port in a
stack.
In essence, you daisy all IOMs of all shelves and then connect two remaining por
ts to both controllers. If you have single controller, you connect just one port
. How exactly you daisy chain does not really matter, but keeping suggested orde
r makes it easier to support.
### Low latency
statistics volume show -interval 5 -iterations 10 -max 25
optimus : 12/4/2015 11:13:06
*Total Read Write Other

Read

rite Latency
Volume
Vserver
Ops Ops Ops Ops (Bps) (
Bps)
(us)
----------------------- -------------------- ------ ---- ----- ----- ------- ------ ------svm_optimus_esx_demo_ds svm_optimus_esx_demo 1744 869 874
0 3561728 357
0216
4361
Volume - volume name.
Vserver - vserver name.
Aggregate - aggregate name.
Total Ops - total number of operations per second.
Read Ops - read operations per second.
Write Ops - write operations per second.

Other Ops - other operations per second.

Read (Bps) - read throughput in bytes per second.
Write (Bps) - write throughput in bytes per second.
Latency (us) - average latency for an operation in microseconds.