IBM AIX VIOS 2.x VLAN with SEA

Problem

How to add another LPAR with a new vlan to an existing SEA.

Solution

  • Without downtime: Create one more virtual Ethernet with new vlan, then add this adapter to the current SEA and change the property with chdev command.

    chdev -dev entX -attr virt_adapters=entY,entZ

    (where entX is the SEA and entY is the adapter that was already part of the SEA and entZ is the new virtual adapter.
  • With Downtime: Simple destroy and recreate the SEA with extra vlan tag port.

Migrating a directory to a separate filesystem on AIX

Problem

You have a directory that deserves it’s own file system for some reason. This could be because you need to increase throughput, manage backups separately, manage quotas separately or just to have a cleaner data architecture.

Solution

  • Create a new filesystem using mkfs
  • Mount the new filesystem temporarily to /mnt
  • Stop all processes that access the directory to move
  • Move all contents to the new filesystem using mv
  • umount /mnt
  • mount /new/filesystem /path/to/directory

This principle is pretty much the same of any Unix operating system.


Installing RHEL from an AIX NIM master

Summary

The AIX NIM server allows a very flexible automated installation process to deploy hundreds or AIX nodes as well as LPARs in a matter of hours. It is possible to achieve similar results using the RHEL kickstart system. This article is about a way of automating the RHEL 5 deployment directly from AIX 6.1 NIM.

Process

  • Copy the RHEL 5 DVD to an NFS file system. E.g. /nfs/rhel5
  • Configure the NIM server to offer the correct boot image in /etc/bootptab:

    rhel-host1.domain.com:bf=/nfs/rhel5/images/netboot.img:ip=xxx.xxx.xxx.xxx:ht=ethernet::sa=xxx.xxx.xxx.yyy:sm=255.255.255.0:
    rhel-host2.domain.com:bf=/nfs/rhel5/images/netboot.img:ip=xxx.xxx.xxx.zzz:ht=ethernet::sa=xxx.xxx.xxx.yyy:sm=255.255.255.0
  • Configure TFTP on the NIM server in /etc/tftpaccess.ctl:

    # NIM access for network boot
    allow:/usr/lpp/sysback/netinst/boot
    allow:/tftpboot
    allow:/nfs/rhel5/images
  • Restart TFTP and reload INETD:

    stopsrc -s tftpd
    startsrc -a -n -s tftpd
    refresh -s inetd
  • Boot the network client with SMS: remote ip setup (with client ip, server ip, router ip, subnet mask, ping test), multiboot setup (with ethernet as first boot device)
  • Follow the regular RHEL install process. (This is where you can get kickstart going.)
  • Reboot the system and reset the boot order.