Hipster Handbook - System Administration

NOTE:

This is a DRAFT document which may contain errors!

Help us improve and expand this site.

Please see the Contrib section for more details about joining the OpenIndiana Documentation Team.

< place holder for introduction content >

Configuring and Tuning

< place holder >

Configuring a UPS

Fault management (FMA)

< place holder >

Service management (SMF)

DOC TEAM NOTE:

ITEMS TO WRITE ABOUT:

Start a service

svcadm enable <service name>

Start service along with it's dependencies

svcadm enable -r <service name>

Start a service temporarily (won't survive a reboot)

svcadm enable -t <service name>

Check service dependencies

svcs -d <service name >

Check status of services

svcs -vx

Systems logging and monitoring

< place holder >

Illumos boot process

< place holder >

Security

< place holder >

Role based access control (RBAC)

< place holder >

Zones

DOC TEAM NOTE:

ITEMS TO WRITE ABOUT:

  • Need to mention some of the changes to zone management...e.g..
    • sys-unconfig gone.
    • sysding replaced syscfg
    • now have to have DNS, root password, etc. all configured inside the zone before being able to logon using zlogin -C <zonename>, otherwise have to do zlogin <zonename>.

So a fair amount of stuff has changed there.

Storage

< place holder >

Mounting file systems

DOC TEAM NOTE:

ITEMS TO WRITE ABOUT:

  • Need a walkthrough of mounting options for other filesystems...NTFS, FAT, UFS, etc.

NTFS support - 3rd party

Configuring OpenIndiana as an ISCSI Target Server - (COMSTAR)

< Place holder for content >

System backups

OpenIndiana offers several backup solutions. Here are just a few of them:

ZFS

DOC TEAM NOTE:

ITEMS TO WRITE ABOUT:

Gotcha's such as the following:

<e^ipi> don't suppose there's any solution to this:
<e^ipi> cannot replace 1509280528045021472 with /dev/dsk/c0t5000C5009204EB9Bd0s0: devices have different sector alignment
<tsoome> thats 512 versus non-512 sector issue
<tsoome> you need to build new pool based on larger sector
<tsoome> if its mirror, you can attach 512B disk to 4k pool, but not vice versa...
<e^ipi> well, damn.
<tsoome> that error message is too confusing, should be replaced by more clear one;)
<e^ipi> I swear this pool is already mix & match, freebsd complained about it
<e^ipi> (but still used it)
<tsoome> there is that thing that ashift is vdev property;)
<tsoome> not pool property (one reason why that linux zpool create ashift= option is bad)
<tsoome> or sort of bad anyhow

Importing ZFS disks

DOC TEAM NOTE:

ITEMS TO WRITE ABOUT:

  • Talk about the ZFS import command.

How does one mirror their root zpool?

DOC TEAM NOTE:

ITEMS TO WRITE ABOUT:

  • Adding a 2nd disk to the root pool

How does one create additional zpools?

DOC TEAM NOTE:

ITEMS TO WRITE ABOUT:

  • zpool create command
    • Mirrors
    • Raidz

Modifying zpool settings and attributes

DOC TEAM NOTE:

ITEMS TO WRITE ABOUT:

  • zpool get/set commands

Modifying zfs file system settings and attributes

DOC TEAM NOTE:

ITEMS TO WRITE ABOUT:

  • zfs get/set commands

How does one create additional zfs datasets?

DOC TEAM NOTE:

ITEMS TO WRITE ABOUT:

  • zfs create command

Configuring system swap

DOC TEAM NOTE:

ITEMS TO WRITE ABOUT:

  • zfs set command
  • swap -l

Virtualization

< Place holder >

OpenIndiana as a virtualization host server

DOC TEAM NOTE:

ITEMS TO WRITE ABOUT:

  • Qemu-KVM (KVM) walkthrough
    • illumos KVM port does not support AMD processors.
    • Intel processors require EPT support.
  • Virtualbox walkthrough
    • There is no package for this yet, but folks do have it working, see the wiki for details.

DOC TEAM NOTE:

ITEMS TO WRITE ABOUT:

In a nutshell, most modern Intel processors such as i3, i5, i7, and Xeon provide EPT support. Most older processors such as Core2duo and Core2Quad lack EPT support, and a few of them lack virtualization support at all. You can check your processor for EPT support via the following link: http://ark.intel.com/Products/VirtualizationTechnology

  • Hipster is currently testing a new package for managing KVM instances as SMF services.
  • libvirt is on the roadmap for the future releases and will open the door for virsh, and likely virt-manager as well.
<leoric> Testers needed! pkg://userland/system/qemu/kvmadm@0.10.3,5.11-2015.0.2.0:20160322T212709Z
<leoric> jeffpc: I know, you like kvm :)
<jeffpc> heh
<jeffpc> leoric: is there documentation for it?
<leoric> https://github.com/hadfl/kvmadm/blob/master/doc/kvmadm.pod
<jeffpc> oh, is it http://www.kvmadm.org/ ?
<leoric> yes
<jeffpc> interesting
<jeffpc> I'll have to give it a try at some point

Localization

DOC TEAM NOTE:

ITEMS TO WRITE ABOUT:

Possible resources to help write this section:

Dtrace

< Place Holder >

Configuring Networking

< Place Holder >

Manual Configuration (static IP)

:~$ sudo svcadm disable physical:nwam

Define in your IP/hostname /etc/hosts, if not already, an entry for this host. For example:

192.168.1.22 hostname hostname.local localhost loghost
# Subsittude 192.168.1.22 for YOUR IP

Enable the default physical service with svcadm and configure the interface:

:~$ sudo svcadm enable physical:default

Configure interface with ipadm:

:~$ sudo ipadm create-addr -T static -a local=192.168.1.22/24 bge0/v4static

If you do not know what the interface name is (bge0 in this case); then type in

:~$ dladm show-link

or:

:~$ kstat -c net | grep net

# look for hme0, bge0, e1000g0 or soemthing that resembles the driver in use.

Add gateway

:~$ sudo route -p add default 192.168.1.121

or

:~$ sudo nano /etc/defaultrouter

# Enter in your gateways IP

Set DNS server(s)

:~$ sudo nano /etc/resolv.conf
# Enter in the DNS server IP(s)
nameserver 192.168.1.121

or


:~$ sudo sh -c 'echo "nameserver 192.168.1.121" >> /etc/resolv.conf'

Restart

:~$ sudo reboot

NOTE:

IF you cannot ping an external IP (e.g. google.com) run this command and try again.

:~$ sudo cp /etc/nsswitch.dns /etc/nsswitch.conf

credit for this section of docs go to /u/127b

Automatic Configuration (NWAM)

Network automagic online help

Comprehensive and fully illustrated online help for using NWAM is available by right clicking the NWAM tray icon and selecting Help. This opens the online help browser.

Troubleshooting NWAM

If NWAM is already configured and fails to connect to a wireless network try restarting the service.

For example:

svcadm restart nwam

Sometimes the location gets set to NoNet and it's nessessary to manually change the location.

When the location setting is configured to Switch Locations Automatically, it's not possible to change the location. This is resolved by reconfiguring the location to allow manual switching. To perform this task, do the following:

Right click the NWAM tray icon and select Location > Switch Locations Manually. Right click the NWAM tray icon and select Location > Automatic.

Desktop GUI

< Place Holder >

Manual Configuration

< Place Holder >

Automatic Configuration

< Place Holder >

Troubleshooting

Clustering with Open HA Cluster

DOC TEAM NOTE:

ITEMS TO WRITE ABOUT:

See old sun docs

Also see: