napp-it ZFS Storage User manual

napp- it
ZFS Storage Server
User‘s Guide
Setup on OmniOS
First steps
published: 2016-Oct-12 (c) napp-it.org
Licence:
CC-BY-SA see http://creativecommons.org/licenses/by-sa/2.0/

Content:
1. Introduction to the Solaris Family
2. ZFS Distributions
3. Hardware and ZFS congurations
4. Napp-it ToGo setup (precongured)
5. Napp-it manual setup and remove
6. Manuals, help and infos
7. Remote Management
8. Napp-it Web-UI
9. ZFS Pools
10. ZFS lesystems
11. Solarish SMB Server
12. User and Groups/ Active Directory
13. NFS server
14. iSCSI/ FC server
15. Data scrubbing
16. Data snapshots/ versioning/ backup
17. Data replikation/ availability
18. Rollback and Clones
19. Operational settings
20. Appliance Security
21. Appliance Tuning
22. Appliance Maps
23. Disaster and general data security
24. napp-it Free vs Pro & Extensions
25. Appliance Z-RAID / ZPOOL-RAID
with SSF (Storage/Service Failover)
26. HA/ RSF-1 Clustering (3rd party extension)
27. Addendum: About Storage Problems
and Solutions
28. other manuals

1. The Solaris Family - OPENSOLARIS based operating systems
Developed by Sun with its initial release in 2008, based on Unix System 5, Release 4 with revolutionary
features like ZFS (http://en.wikipedia.org/wiki/ZFS), Comstar (enterprise ready iSCSI and FC technology), Dtrace,
Crossbow virtual networking, virtualization with Zones (http://en.wikipedia.org/wiki/Solaris_Zones), ZFS inte-
grated kernel based CIFS/SMB and NFS server among other features like ZFS boot mirrors, disk unique WWN
enumeration or fault management service with auto hotspare support.
If you want to follow the way from Sun OpenSolaris to the free forks like the current Illumos based
distributions, you should look at Bryan Cantrills (Joyent) slideshow at
http://www.slideshare.net/bcantrill/fork-yeah-the-rise-and-development-of-illumos or
http://www.youtube.com/watch?v=-zRN7XLCRhc
Some essentials from the slideshow:
„In the mid-1990 it becomes a foregone conclusion that UNIX would die at the hands of Windows NT Hard to
believe, but SUN seems the only computer vendor whose Windows NT strategy was to beat Windows NT
Sun‘s dedication to this vision - the operating system as a nexus of innovation - attracted an entire new
generation of engineers to the company Development started on more radical ideas, each of it would become
revolutionary in its own right (ZFS, DTrace, Zones, Crossbow, Comstar, Fault Management, Service Manag-
ment, Least Privilege) These were technologies invented and initiated by engineers, not managers or marke-
ters These projects reected the people behind them..Organizations don‘t innovate - people do
As the rise of Linux forced the market price of OS aquisition to zero, that open sourcing the (Solaris) operating
system was the right business decision (in 2005. Unfortunately, not all elements of the OS could be open-
sourced, some contracts prevented some small but important bits from beeing opensourced. To allow such
proprietary drivers, Sun developed a le based copy left licence (CDDL) ... this was not done to deliberatly GPL
incompatible!
Ailing Sun was bought by Oracle in 2009. Over 2010, it becomes clear that Oracle had obsolutely no interest
in OpenSolaris... There was.. a move to close the system (OpenSolaris)
Starting in the summer of 2010, Garett D‘Amore at Nexenta - with the help of Rich Lowe, Jason King and
others - began the process of ether writing the closed bits from scratch or porting from BSD. Dubbed „Illumos“
(from illuminare, Latin for illuminate) and made available on August 3, 2010
Illumos was not designed to be a fork, but rather an entirely open downstream repository of
OpenSolaris
Solaris 11 was released on November 9, 2011 - and there was no source release
The entire DTrace team, all primary ZFS inventors and primary engineers for zones and networking had left
Oracle.. nearly all of these engineers went to companies betting on Illumos.
In Illumos, we have seen critical innovations and bug xes in ZFS, DTrace, Zones and other core technologies.
These innovations ill never be in Oracle Solaris. Joyent team ported KVM from Linux. Illumos distributions
SmartOS and OpenIndiana have KVM support by default.“
Solarish
If we talk about common features of Oracle Solaris and the free Solaris fork Illumos (ex OmniOS, OpenIndiana,
SmartOS) the term Solarish is common.

2. ZFS Distributions
Unlike storage appliances that are based on their own distribution of BSD, Illumos or Linux,
napp-it is a „Nasier“ for some general-use enterprise operating systems that you can keep up to date like
Based on Solarish
- Oracle Solaris 11.3+ (commercial OS)
- OmniOS (free and stable Solaris fork with a commercial support option)
- OpenIndiana Hipster (unstable but with a desktop option)
Based on Linux
- Ubuntu
- Debian
Linux - support is limited to ZFS management, Autosnap, Autoscrub and AutoJob features
and does not include the advanced features of the Solaris release.
Between ZFS distributions you can move ZFS pools with the follwing restrictions
- From/to Oracle Solaris: Pools must be V28, ZFSv5
- From BSD based systems: Possible with GEOM or with GPT partitions spanning the whole disk
- Beside that: OpenZFS distributions must support same features. No problem with current releases.
What is the preferred napp-it distribution
Napp-it is developed under OmniOS and this is the default distribution:
Without a special reason to select something other, you should use OmniOS with napp-it.
The reasons for OmniOS
- active development with a stable every 6 months
- long term stable editions
- minimal OS, just enough for a fully functional ZFS server for best stability
- free but with a commercial support option
- Just enough ZFS Storage OS, the ZFS server with the smalles footprint, reason of its stability
The reasons for a Solarish based ZFS System
- 100% focus on ZFS that was developed for Solaris 10 years ago and is most stable and complete there
- a complete storage OS from one hand, not the toolbox with a core OS and many options and vendors
- stable support for mirrorred ZFS boot systems with boot environments (restore a former bootable OS state)
- WWN enumeration of disks (disk unique identication) to keeps disk id identical over controller, server or OS
- fault management with active hot-spares that replaces faulted disks automatically
- SMB, NFS and iSCSI integrated in the core OS and maintained by Oracle or Illumos (OmniOS)
- virtual networking with virtual switches and virtual nics with vlan support
- service management SMF with service auto restart
- Solarish CIFS server with NFS4 ACL (more Windows NTFS alike than Posix ACL) and AD support,
Windows SID as extended ZFS attribute (Permissions stay intact after a restore to another AD server),
- ZFS snaps as Windows „previous version“, stable and just working out of the box since years

2.1. OpenIndiana Hipster 2016.04
with GUI and SMB 2.1 („desktop edition“), use for home and lab use
You can run napp-it on OpenIndiana Hipster 2016.04 (OpenSource) or Oracle Solaris 11.3. Both support
SMB 2.1 and come with a GUI. You manage storage via the napp-it Web-UI but the local GUI helps to transfer
and organize data locally or to setup things like ip v6. If you want the GUI in production systems, prefer Solaris.
Alternatively you can use the „text-edition“ of OpenIndiana or Solaris or OmniOS, a minimalistic and very stable
OpenSource distribution for storage and other production use cases (This is the preferred platform for napp-it)
2.2. OmniOS
or OpenIndiana or Oracle Solaris server edition
They come with a console only interface.
To manage local data, you can use
Midnight Commander via Putty.
Storage management is done via the
napp-it Webinterface. As they include only
the absolute needed software, they are the
most stable option.

2.3. Storage-Management via napp-it
on OmniOS, OpenIndiana or Oracle Solaris
ZFS Filesystems and disk details

3. Hardware
OmniOS runs on common desktop and serverhardware, see http://illumos.org/hcl/
You should mainly care about the network and the disk controller.
Rules for a trouble free minimal system
- use Sata/ AHCI with a 30GB Bootsdisk (60GB when using the napp-it ToGo image)
- prefer Intel nics
- use at least 4 GB ECC RAM (2 GB is the absolute minimum, more gives performance as readcache)
- use at least 8GB if you enable na--it realtime monitoring or acceleration
- enabling dedup may increase these minimums
Rules for barebone „quality storage“ or „Napp-in-One“
- use server class hardware/ server chipsets and IPMI remote management
- use ECC RAM and an Sata bootdidk/ DOM with 60GB or more (SuperMicro DOM or prefer an Intel S3510)
- use a Celeron G4400 or a Xeon as they offers ECC support and vt-d (virtualized SAN)
- use Intel Nics (10 GbE preferred, ex Intel X540)
- use LSI HBA with raidless IT rmware, ex LSI 9207 that comes with IT rmware per default
- prefer SAS disks with an expander
- use SAS disks for HA solutions based on Multipath IO
- prefer Sata disks with multiple HBAs (without expander)
- prefer 24/7 enterprise disks
Rules for high capacity storage
- prefer raid Z2 vdevs with 6 or 10 disks or Z3 vdevs with 11 disks
- prefer enterprise SAS disks or 24/7 high quality Sata/ NAS drives
- with desktop disks, check reliability, ex with backplaze annual failure rates
https://www.backblaze.com/blog/best-hard-drive-q4-2014/
Rules for High-Performance storage
- prefer Enterprise SSD with powerloss protection and build in overprovisioning
like Intel S3500-S3710 or Samsung PM/SM 863 series - optionally use manual overprovisioning
example with a host protected area (HPA) on new SSDs
You can create a HPA with hdat2, http://www.hdat2.com/
Rules for fast but write secure storage like ESXi datastores
- use sync write with a dedicated high perfomance Slog device
Rules for a dedicated Slog device
- ultra low latency
- continous high write iops, even under load
- powerloss protection
- should be noticable faster than your pool like Intel S3700 with a disk pool or a ZeusRAM with an SSD pool
- examples: ZeusRAM, a Dram based device (best of all) or Intel S3700/ 3710
more: http://napp-it.org >> Sample Congs

3.1 ZFS Congurations

4. napp-it ToGo setup (install from a precongured image, beta)
There are two options, one for a barebone setup and one for a virtualized ESXi setup
4.1 ready to use barebone napp-it ToGo distribution for an Sata bootdisk
This is the easiest and suggested setup method of installing, backup and recover a napp-it barebone appliance
based on a precongured image for a ready to use ZFS storage server. It works best for OEM use with known
hardware. It may not work with any hardware or disk. On success, please send a mail to [email protected]
with your mainboard, interface, disk type and remark. I will create then a list of known to work setups.
Download and clone the 512n or 512e image. For best reliability use an Intel S3510 - 80 GB with powerloss
protection (512e). You may use a 64 GB SuperMicro Sata DOM or a 60GB+ Sata disk or SSD (mostly 512n). Use
an Sata port for your bootdisk. As Clonezilla currently is not ZFS aware it clones the whole disk via dd.
Step 1: Create a bootable USB stick (256MB is ok) with Clonezilla, a free cloning tool.
You can use a 16/32GB USB FAT-32 stick (depend on size), USB/Sata disk or share for the systemimage.
Step 2: Download the zipped napp-it image from https://www.napp-it.org/downloads/index_en.html, either
the version for 512n disks or the version for 512e (4k physical sectorsize), unzip and copy the included folder
to another USB stick or a network share ex NFS/SMB. You can download an image with a precongured OmniOS
+ napp-it 512n for free. The foldername is something like „2016-04-05-img18-disk-mainboard-512n. For
napp-it Pro users, there are plans to add images with different mainboards, disk sizes and napp-it.
Step 3: Boot your server from the CloneZilla USB stick to restore napp-it. Select your keyboard type, device-
image-mode and a the source of the image ex a local USB Stick/ disk or a NAS. Default is restoring the image
from a local USB stick/disk to your local Sata disk. The Sata bootdisk or DOM can be 512n or 512e (the disk is
physically 4k sectorsize) with 64 GB or more (Imagesize 62 GB). It is important that you use an image that ts to
your disk (512n or 512e physical sectorsize). With an USB device for the image, plug it in prior selecting source
image. see http://clonezilla.org/show-live-doc-content.php?topic=clonezilla-live/doc/02_Restore_disk_image
btw: You can use CloneZilla to backup, clone or restore any bootdisk, even a Mac with OSX.
Step 4: Boot napp-it from your Sata disk (Set the Sata disk as boot-disk in the mainboard bios).
All network adapters are enabled automatically in DHCP mode. You can logon at console as root
(no password) and enter ifcong -a to list all network adapters with their ip adresses.
Start your browser and connect napp-it via http://ip:81
Next, set a root password, a napp-it password and optionally enable/disable SSH root access
On a new setup, create now a new datapool, optionally some users and share lesystems:
If this is a restore after a crash, import the old datapool and optionally restore users and settings
from a backup on your datapool (manually or with the ACL extension in menu Users > restore) settings.
Download tuxboot.exe from
https://sourceforge.net/projects/tuxboot/les/
This is a tool to create a bootable USB stick
with Clonezilla live on it. Start tuxboot on
a Windows machine, select Update and an
amd64 clonezilla stable or testing edition
and clone it to the USB stick

4.1.2 Screenshots of a base setup (asuming you have a Clonezilla USBStick)
Copy the napp-it imagefolder to you USB stick (root directory) and boot your server from the USB stick
1. Start Clonezilla 2. select device-image mode
3. select local_dev (USB drive) 4. Clonezilla is now ready to read the napp-it image
If the image is on an USB(3) stick or disk, insert the
stick now, wait 5s, press enter and select the image.
5. select your USB stick as source and select Top 6. select Beginner mode
directory on next screen
Your napp-it image must be on another stick/ disk
or partition than CloneZilla itself.

7. select restoredisk 8. Select the Imagele that you want to restore
If restoredisk is missing (savedisk only), go back
to 4. as Clonezilla did not read the image properly.
9. Select your Sata disk (> 60 GB) where you want 10. Clonezilla is now restoring the image to your
to restore the image. You can optionally check bootdisk. You can also create your own images as
the image on next screen. Otherwise press Enter a source for a recovery. On problems with the image,
and conrm that you want to proceed. do a manual setup and send a message with the
problem and mainboard to [email protected]
After the restore:
Optionally enter a key and update napp-it to newest Free or Pro edition.
Optionally update OmniOS
On problems with the restored image:
1. If napp-it boots, but network not working: do a manual network setup, see 5.2
2. Image is not compatible with your SSD, use the ones that were used to create the image
3. Image is incompatible with your hardware: do a manual setup and create your image for restore
4. Image cannot boot due a problem with the bootmanager grub (ex different controller). This can be solved:
- boot your server with a regular OmniOS installer disk or USB stick (available from OmniTi), select keyboard
- select 3=Shell after boot, what gives you a console, enter format ti list disks (cancel afterwards with ctrl-C)
format
format lists all disks, write down id of your bootdisk ex c1t0d0, then enter ctrl-c to to return to console
- modify grub to use a different bootdisk/ controller, enter the following CLI command (add s0 to disk-id) ex
installgrub /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c1t0d0s0
reboot
There is an option with installgrub -m that installs a new master boot record
If this does not help, do a manual setup of OmniOS + napp-it.

Create a Master image for a certain platform:
Important: If you want to create a new master image, use a new SSD or do a secure erase (smaller image)
1. Install OmniOS, OpenIndiana or Oracle Solaris
Download the ISO or USB image and burn a bootable CD/DVD or clone the USB stick
Boot the installer and run a default setup
2. enable compress
set compress=lz4 rpool
set atime=off rpool
3. set network
dladm show-link
ipadm create-if e1000g0
3.1 use DHCP (preferred method on initial setup)
ipadm create-addr -T dhcp e1000g0/dhcp
3.2 add nameserver
echo ‚nameserver 8.8.8.8‘ >> /etc/resolv.conf
3.3 use dns (copy over DNS template)
cp /etc/nsswitch.dns /etc/nsswitch.conf
If something happens (typo error), retry, opt. delete interface ex ipadm delete-if e1000g0
4 Setup the napp-it appliance
wget -O - www.napp-it.org/nappit | perl
5. reset root root (Unix and SMB), no password (press enter twice)
passwd root
6. enable SSH root access via napp-it menu Services > SSH
7. Login via Putty (to copy/paste commands with a mouse right-click)
8. set TLS for encrypted mai ex Gmail (run the from Putty/ Console and conrn any questions with enter)
perl -MCPAN -e shell
notest install Net::SSLeay
notest install IO::Socket::SSL
notest install Net::SMTP::TLS
exit;
9. disable services SSH root access and sendmail service in napp-it (menu Service)
set netbios_enable=true (Windows network browsing in OmniOS 151016 and up, menu Service>SMB>prop.)
10. set basic tunings in napp-it System > Tuning,
11. delete all BE
12. run
perl /var/web-gui/data/tools/other/prepare_image.pl
13 beadm create backup.setup (console, creates a backup bootenvinment with nics not congured)
14. Enter halt and power off, start cloneZilla
15. clone the systemdisk with defaults (quite fast, medium compress). name like date-img18-board-disk
or select advanced settings with z2p compress , compromise between compression time and size

4.2 ready to use ESXi distribution (napp-in-one, virtual NAS/SAN)
This is the fastest and easiest conguration method on ESXi that comes as a downloadable ready to use ESXi
storage server template that combines the minimalistic and in professional environments leading VM Server
ESXi with a complete but tiny Enterprise class NAS/SAN Storage solution based on the Solaris fork OmniOS as a
precongured ESXi VM template with napp-it and Vmware tools for ESXi up to 6.0. Both ESXi and the napp-it
VM are installed or reinstalled after a complete crash within minutes as they do not include any important con-
gurations. All services that require conguration like databases, webservers etc should be virtualized on stable
ZFS storage with online backup and snap support. The VM requires a DHCP server. You must only import the VM
(OVA Template). For disaster recovery, you can export your individual template from ESXi.
The template is ready to use. Download from http://napp-it.org/downloads/napp-in-one_en.html
You can download the image with a precongured OmniOS + napp-it VM for free.
For napp-it Pro users, there are images with newer OmniOS releases, TLS preinstalled and napp-it Pro available.
If you want to create your own storage VM, upload the OmniOS ISO to your local datastore. Create a new VM
with type Solaris 64bit and a 30 GB bootdisk and tell Esxi to boot from this ISO.
Update napp-it to newest Free or Pro edition in menu About >> Update
5. napp-it manual barebone Installation (OmniOS)
Use this method if you want to setup a different OS version or a different ditribution ex OpenIndiana
or Oracle Solaris or if the default cloning method of a precongured image fails.
Use a 32 GB or larger Sata SSD/disk or Sata DOM as system disk (optionally two for a boot-mirror)
ex http://www.supermicro.com/products/nfo/SATADOM.cfm
Download the usb-dd installer le from http://omnios.omniti.com/wiki.php/Installation
You can create a bootable USB stick (1 MB min) with the free imager (Windows) from
http://www.napp-it.org/doc/downloads/napp-it-to-go_tools.zip
Boot your OS installer from USB stick and install OmniOS with defaults to your bootdisk.
Select „use whole disk“. If you want to mirror two bootdisks, you can do this later in napp-it.
The OS installation is nished after a few minutes.
Reboot the system after OS setup. OmniOS is installed without a congured network.
Only the user root is available after setup with empty password (no password needed)
For a working enterprise class storage appliance, you need to
- install OmniOS, OpenIndiana or Oracle Solaris
- congure network
- run the online napp-it installer
- reboot (or set current bootenvironment, BE as default) and set a root password (for console and SMB access)
- manage the appliance with any webbrowser at address http://your_serverip:81
optionally:
- install TLS if you want to send aencrypted lerts and statusmail ex to Gmail.
Create a disaster recovery image
Create a bootable USB stick 256MB+ with CloneZilla (see 4.1) and boot the stick.
If you want a fast backup, select Expert mode and z1p compression (very fast, medium compression rate)
and save the disaster recovery image to another disk or an NFS/SMB share.
You can restore your image from a local disk (can be an USB stick) or an NFS or SMB share.

5.1 Manual setup of a napp-it storage appliance with DHCP
Download the OmniOS or Solaris installer (ISO dvd or USB installer), boot the installer and install the OS.
Select UTC timezone, with bloody versions keep all defaults incl keyboard
After OS setup, your need to congure your network either with DHCP (5.1) or manually (5.2).
5.1.1 Initial setup of the napp-it appliance with DHCP
- boot OmniOS and login as root (no password)
- list available network adapters with their linkname (ex e1000g0):
dladm show-link
- create an ip interface based on the linkname
ipadm create-if e1000g0
- enable DHCP (requires a DHCP server)
ipadm create-addr -T dhcp e1000g0/dhcp
- add nameserver
echo ‘nameserver 8.8.8.8‘ >> /etc/resolv.conf
- use DNS name resolution (copy over DNS template)
cp /etc/nsswitch.dns /etc/nsswitch.conf
- install napp-it online (default/ free version)
wget -O - www.napp-it.org/nappit | perl
- reboot (or set current bootenvironment as default)
reboot
- set a root password (this password is valid for Unix shell logins and SMB connects)
passwd root
optional: check current network settings
ifcong -a
optional: If something happens (typo error), delete interface and retry
ipadm delete-if e1000g0
optional for ESXi: pkg install open-vm-tools, pkg install vmxnet3s
export template with dhcp, without pass-through devices or cd isos
optional with newest OmniOS: svcadm disable sendmail and sendmail-client
(https://blogs.oracle.com/souvik/entry/my_unqualied_host_name_sleeping)

5.2 Setup napp-it storage appliance with manual ip settings
After OS setup, your need to congure your network either with DHCP (5.1) or manually (5.2).
5.2.1 Initial setup of the napp-it appliance with manual ip settings
If you have a working DHCP server: use DHCP and set network manually later in napp-it
- boot OmniOS and login as root (no password)
- list available network adapters with their linkname (ex e1000g0):
dladm show-link
- create an ip interface based on the linkname
ipadm create-if e1000g0
- set a manual ip address
ipadm create-addr -T static -a 192.168.0.1/24 e1000g0/v4
- add default route (enter your router ip)
route -p add default 192.168.0.254
- add nameserver
echo ‘nameserver 8.8.8.8‘ >> /etc/resolv.conf
- use DNS name resolution (copy over DNS template)
cp /etc/nsswitch.dns /etc/nsswitch.conf
- install napp-it 0.9 online
wget -O - www.napp-it.org/nappit | perl
- reboot (or set current bootenvironment as default)
reboot
- set a root password (this password is valid for Unix shell logins and SMB connects)
passwd root
optional: check current network settings
ifcong -a
optional: If something happens (typo error), delete interface and retry
ipadm delete-if e1000g0
5.3 stop/ remove/ manual deinstall of napp-it
Napp-it installer creates a bootenvironment with the state prior the installation so you can always go back.
As napp-it is a pure copy and run installation, it copies everything to /var/web-gui If you delete this folder, the
init le /etc/init.d/napp-it, the user nappit and an entry in /etc/sudoers and user_attr you have wiped it beside
tools that are installed during setup like smartmontools, midnight commander, iperf or netcat. You do not need
napp-it for regular storage operations. If you want to stop napp-it, use /etc/init.d/napp-it stop (start | restart)
If you install add-ons like the AMP stack, they are using pkgsrc from Joyent with les in /opt

6. ZFS manuals and infos
You should now download and optionally printout some basic manuals.
6.1 napp-it manuals
http://www.napp-it.org/doc/downloads/napp-it.pdf
http://www.napp-it.org/doc/downloads/napp-in-one.pdf
http://www.napp-it.org/doc/downloads/advanced_user.pdf
http://www.napp-it.org/doc/manuals/ash_x9srh-7tf_it.pdf
6.2 manuals for Oracle Solaris 11
Download and print out needed manuals from
https://docs.oracle.com/en/operating-systems/
6.3 manuals for Oracle Solaris 11 Express and OmniOS
Download and print out needed manuals. As Oracle offers only manuals for their current release, you must
use an archive search for Solaris 11 Express manuals (OmniOS is more or less a fork of Solaris 11 Express)
http://archive.is/snZaS
The archive.is page refers to the old Solaris Express 11 page. If you click on a description, you
are forwarded to the current Solaris 11 page. If you click on „Download“ you get the correct manual.
Download manuals and print out at least the ZFS administration guides
6.4 other books and manuals, Less known Solaris features
http://www.c0t0d0s0.org/pages/lksfbook.html
http://www.c0t0d0s0.org/archives/6639-Recommended-SolarisSun-Books.html
6.5 Maillists, forums and IRC
Join the following maillists, threads and IRC discussions to keep you informed
http://lists.omniti.com/mailman/listinfo/omnios-discuss
http://echelog.com/logs/browse/illumos/
http://echelog.com/logs/browse/omnios
http://hardforum.com//showthread.php?t=1573272 (Hardforum)
https://forums.servethehome.com (Solaris/napp-it subforum)
http://www.hardwareluxx.de/community/f101/zfs-stammtisch-570052.html (DE)

7. Remote management
A Server can be managed remotely, use these tools
7.1 IPMI
IPMI ist a must have for a server: https://en.wikipedia.org/wiki/Intelligent_Platform_Management_Interface
IPMI is a remote management microcontroller on serverclass hardware like Supermicro mainboards that ends
with a „-F„ . You can connect the microcontroller remotely with a webbrowser even when the server is in a
power-off state. Functions are mainly power on/off/reset, a remote console/keyboard and the ability to mount
ISOs like a lokal CD/DVD drive.
IPMI window (Java applet) with a virtual keyboard and a console preview that can be displayed full size.
You can enable IPMI and its ip adress in your mainboard bios. It comes with a dedicated network port so
you can connect with a dedicated and isolated management network. As an option, you can use your regular
Lan port (insecure). IPMI requires a current Java (free download from www.java.com). For security reasons, you
must allow the ip of your server ( ex https://172.19.10.5 ) for java applets.
SuperMicro default IPMI user/pw (you should change that)
user: ADMIN
pw: ADMIN

7.2 Remote Console via Putty
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
Putty is a „must have“ tool.
Daily storage management is done via the napp-it Web-Interface. Some tasks require console access. This can
be done locally or remotely via Putty, a free Windows application. Download and run - no installation required.
To use Putty, you must enable SSH on OmniOS. This is the case per default but per default only regular users
can login, not root. So you must either create a regular user than can login. After this you can gain admin
permissions wit a su command. Other option is to enable remote root access in the napp-it Web-GUI in menu
„Services >> SSH >> allow root“. As this can be a security problem, you should disable remote root afterwards
with menu „Services >> SSH >> deny root“
Tips:
You can copy/ paste CLI commands with a „right mouse click“ into the Putty Window.
The same is the case when you mark text within the Putty console.
Midnight commander, a console lebrowser that runs on OmniOS with an optional usermenu
is installed automatically by napp-it to do local le management (copy/move/delete/edit).
This is the fastest way to copy/move les as it is done locally and not over your network.
You can start midnight commander when you enter „mc“ at console and quit with F10.
If Midnight commander is showing wrong characters, you can either set a proper environment variable or
call Midnight commander directly with a LANG envronment ex (German), start mc like:
LANG=de_DE mc

7.3 Remote Filemanagement/ Fileediting on Windows with WinSCP
http://winscp.net/eng/download.php
WinSCP is a „must have“ tool.
WinSCP is a free Windows application that allows
- upload/download les (binary/text/auto) like a ftp client but encrypted
- edit /nd les on your server (you can use different editors for differen letypes)
- delete/copy/move les (not as fast as Midnight Commander as les must be transferred encrypted over LAN)
- check/modify Unix permissions and ownership
To use WinSCP you must enable SSH on OmniOS. This is the case per default but per default only allows that
regular users can login, not root. An option is to enable remote root access in the napp-it Web-GUI in menu
„Services >> SSH >> allow root“. As this can be a security problem, you should disable remote root afterwards
with menu „Services >> SSH >> deny root“ .
Tips:
When you connect as root, you have full permissions to edit all les on OmniOS including systemles.
This makes Unix magagement a lot easier as you can manage remotely from Windows and do not need
to use ancient editors like vi.

8. First steps with the napp-it Web-Gui
Use your browser to manage napp-it: http://serverip:81 example
http://192.168.1.1:81
If you are unsure about your ip, enter the following console command
ifcong -a
If you start napp-it the rst time, you are asked to setup napp-it passwords and email.
Setup options (Menu About >> Settings):
User accounts: Admin and oprtator
These are napp-it only accounts and are used only for web-management and
appliance grouping
default-user
User operator has a reduced set of administration options
Menu and Language
You can select a menu-set that allows different menu descriptions and translatiions
You can also restrict menu items:
Default set is Solaris (sol) that offers only Storage options supported by Solaris or OmniOS
You should use this menu set in production environments.
As Solaris is an enterprise OS, you can use it for other services or applications as well
example a Webserver or Databese Server. You can use these services without support
Napp-it offers some menus that may help to manage them like the Apache webserver
You will nd according menus for this example under Services > Apache with the options
to edit the cong les, includes, modules or related like php condig les.
To enable these unsupported menus, you must select another menuset, example en or de.
You can force a special menu set if you rename /_my/zfsos/_lib/lang/MY to
/_my/zfsos/_lib/lang/MY!
You must place a menu description le about_menus.txt in this folder.
email
Napp-it can send alert and status emaile, either unencrypted or TLS encrypted
Enter the account details about your mailsetup.
Be aware: napp-it must store your cleartext password
push
Push alerts is an option to send alerts to your desktop or smartphone.