Search

Google

Saturday, September 6, 2008

Upgrading system firmware

Upgrading Firmware

Pre-requisites.

Before starting the firmware upgrade ensure the following:

All LPAR’s have been shutdown gracefully.
Ensure that there are no serviceable events in the Service Focal Point.

In the Navigation Area of the HMC select Service Applications and the Service Focal Point. From the Tasks menu select Manage Serviceable Events.

Disable IBM Call Home prior to starting the upgrade.
If the firmware upgrade results in new serviceable events ensure these are deleted prior to enabling Call Home.

Upgrade Procedure

Download the firmware upgrade from the IBM web site

http://www14.software.ibm.com/webapp/set2/firmware/gjsn

From the drop down menus select the following

Machine Type: 9117-570

Press Go

From the available down loads check the RPM box for System Firmware SF240_320

Continue through the license agreement. From the listed packages download both the .rpm and .xml files. These can the be burnt to.

Insert the DVD into the HMC.

On the HMC select the Licensed Internal Code Maintenance folder and then select Licensed Internal Code Updates.

From the options select Upgrade to a New Release.

Select Upgrade Licensed Internal Code to a new release.

In the target host window select the system to update

9117-570*0265C30DE
nlscux21
9117-570*0265C30EE
nlscux22


In the specify LIC repository window enter the location of the firmware upgrade.

Upgrading the HMC Software

Upgrading the HMC Software

The Hardware Management Console (HMC) controls the configuration and monitoring of the Logical PARtitions (LPAR’s) in the managed frames. For this to function efficiently the Operating Systems must be updated to the latest supported level. Currently the Operating system is over 2 years old and is out of support. Because of the big changes made between release 4.5 and release 6.1 the upgrade path is slightly different than normal.

Pre-requisites

Order the HMC Version 6 Release 1.2 Recovery DVD’s, or download them, from the IBM Recovery media/Downloads web page.

Perform a Save Upgrade Data to preserve data on the HMC before starting the upgrade. The upgrade must begin immediately after the Save Upgrade Data action, and before restarting the HMC applications.

Select Licensed Internal Code Maintenance.
Select HMC Code Update.
Select Save Upgrade Data, and then insert a formatted DVD-RAM media into the DVD drive.
Select DVD drive, and then click Continue.
If the Save Upgrade Data task is successful, remove the DVD-RAM, insert the first V6.1.0 recovery media into the DVD-RAM drive. Close the HMC console and reboot.

Upgrade Procedure

The HMC will boot from the DVD and display the Install/Backup/Restore menu.

Select Install and press Next

Select Install From Media and press Next.

Installation of the HMC will then start. When prompted, replace the DVD with the next disk. When installation of the second disk is complete select option 2 (Finish Installation) from the menu.

Login into the HMC using the default user ID (hscroot) and password .

Open a restricted shell window (right-click on desktop, terminals and rshterm).

Load the Save Upgrade Data DVD from step 2 and mount the media

>mount /media/cdrom

Upgrade the data from the Save Upgrade Data DVD.

>rstupgdata –r dvd

When the upgrade is complete un-mount the DVD

>umount /media/cdrom

Reboot the HMC

>hmcshutdown -r -t now


Post Installation Check

From the menu bar select:

Help About the Hardware Management Console

Open the About panel

The Version is 6The Release is 1.0HMC Build level 20060719.1","base_version=V6.1.0

Increasing size of System Dumpdeivice

Overview

When an unexpected system halt occurs, the system dump facility automatically copies selected areas of kernel data to the primary dump device. These areas include kernel segment 0, as well as other areas registered in the Master Dump Table by kernel modules or kernel extensions. An attempt is made to dump to a secondary dump device if it has been defined.
When you install the operating system, the dump device is automatically configured for you. By default, the primary device is /dev/hd6, which is a paging logical volume, and the secondary device is /dev/sysdumpnull.
Note:
If your system has 4 GB or more of memory, then the default dump device is /dev/lg_dumplv, and is a dedicated dump device.


If a dump occurs to paging space, the system will automatically copy the dump when the system is rebooted. By default, the dump is copied to the/var/adm/ras directory in the root volume group. See the sysdumpdev command for details on how to control dump copying.

sometimes we get an error like “Largest Dump Device is too small”

Checking for the current dump device

Get the size of the current dump devices:
sysdumpdev -l
Example:
nlasltp2@/home/a124037>sudo sysdumpdev -l
primary /dev/hd7
secondary /dev/hd7x
copy directory /var/adm/ras
forced copy flag TRUE
always allow dump TRUE
dump compression OFF

Get the estimate of the size needed for the dumpdevice:

sysdumpdev –e
Example:
nlasltp2@/home/a124037>sudo sysdumpdev -e
0453-041 Estimated dump size in bytes: 5002756096



Check the size of the current dump devices (based on the primary and secondary from the sysdumpdev -), the dump device will most likely be found on the rootvg:

nlasltp2@/home/a124037>lsvg -l rootvg
rootvg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
hd5 boot 1 2 2 closed/syncd N/A
hd6 paging 90 180 2 open/syncd N/A
hd8 jfslog 1 2 2 open/syncd N/A
hd4 jfs 1 2 2 open/syncd /
hd2 jfs 21 42 2 open/syncd /usr
hd9var jfs 2 4 2 open/syncd /var
hd3 jfs 4 8 2 open/syncd /tmp
hd1 jfs 1 2 2 open/syncd /home
hd10opt jfs 1 2 2 open/syncd /opt
appllv jfs 1 2 2 open/syncd /appl
tsulv jfs 2 4 2 open/syncd /appl/tsu
esmlv jfs 2 4 2 open/syncd /appl/esm
operflv jfs 1 2 2 open/syncd /appl/sptools/operf
sptoolslv jfs 4 8 2 open/syncd /appl/sptools
hd7 sysdump 19 19 1 open/syncd N/A
hd7x sysdump 19 19 1 open/syncd N/A
hascriptlv jfs 2 4 2 open/syncd /appl/ha-scripts
tivlv jfs 4 8 2 open/syncd /appl/Tivoli

From the example you can see that hd7 is using 19 PP (the same for hd7x). They should be on different disks and you might like to check that at this time although it is unrelated to the size (on different disks such that the dump is available if a disk fails). This can be checked by the following commands:

nlasltp2@/home/a124037>lslv -m hd7
hd7:N/A
LP PP1 PV1 PP2 PV2 PP3 PV3
0001 0092 hdisk0
0002 0093 hdisk0
0003 0094 hdisk0
0004 0095 hdisk0
0005 0096 hdisk0
0006 0097 hdisk0
0007 0098 hdisk0
0008 0099 hdisk0
0009 0100 hdisk0
0010 0101 hdisk0
0011 0102 hdisk0
0012 0103 hdisk0
0013 0104 hdisk0
0014 0105 hdisk0
0015 0106 hdisk0
0016 0107 hdisk0
0017 0108 hdisk0
0018 0109 hdisk0
0019 0110 hdisk0
nlasltp2@/home/a124037>lslv -m hd7x
hd7x:N/A
LP PP1 PV1 PP2 PV2 PP3 PV3
0001 0092 hdisk2
0002 0093 hdisk2
0003 0094 hdisk2
0004 0095 hdisk2
0005 0096 hdisk2
0006 0097 hdisk2
0007 0098 hdisk2
0008 0099 hdisk2
0009 0100 hdisk2
0010 0101 hdisk2
0011 0102 hdisk2
0012 0103 hdisk2
0013 0104 hdisk2
0014 0105 hdisk2
0015 0106 hdisk2
0016 0107 hdisk2
0017 0108 hdisk2
0018 0109 hdisk2
0019 0110 hdisk2

(The increase procedure is based on the above example)

Increasing the size of the Dump device


PP size in the example was 128 MB. 19 PPs was used which gives us 2432 MB current dump device. Compare that to the estimated of 5002756096 which is roughly 5000MB. This is 40+PP so select 44 (~10% extra) for growth. Thus we need to increase with 44-19= 25PPs for each of the logical volumes. In our case this is fine as we have 778 PPs free (make sure there are at least 200 more free in addition to this, otherwise escalate as the PP might be needed for more urgent matters). Thus we increase each of the LVs (and it is pure 25PP as they are not mirrored):
extendlv hd7 25
extendlv hd7x 25

Procedure of replacing rootvg failed hdisk

=================================
1) unmirrorvg rootvg hdisk1 ( eg for hdisk1 is failed)

2) reducevg rootvg hdisk1 (if you receive error)
nlxenc06:a207081> reducevg rootvg hdisk1
0516-016 ldeletepv: Cannot delete physical volume with allocated
partitions. Use either migratepv to move the partitions or
reducevg with the -d option to delete the partitions.
0516-884 reducevg: Unable to remove physical volume hdisk1.

3) after getting error , try for reducevg -d rootvg hdisk1
even if you receive error

0516-914 rmlv: Warning, all data belonging to logical volume
hd7x on physical volume hdisk1 will be destroyed.
rmlv: Do you wish to continue? y(es) n(o)? y
0516-1252 rmlv: Warning, cannot remove logical volume hd7x.
This logical volume is also used as the secondary dump device.
Reset the dump device and retry the command.
0516-884 reducevg: Unable to remove physical volume hdisk1.

4) try rmlv hd7x (if you get still error)
nlxenc06:a207081> lsvg -p rootvg
rootvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION

hdisk0 active 542 17 00..00..00..00..17
hdisk1 active 542 512 93..108..108..108..95

problem was here for hd7x

5) create a file through touch command
touch /dev/sysdumpnull

6) sysdumpdev -Ps /dev/sysdumpnull
(changing hd7x to sysdumpnull by passing above command)

7) rmlv hd7x

8) attach the new disk. cfgmgr -v.

9) extendvg rootvg hdisk1

10) mirrorvg rootvg hdisk1

11) varryonvg rootvg

12) bootlist -m normal -o

13) bosboot -ad /dev/hdisk0

14) bosboot -ad /dev/hdisk1

15) bootlist -m normal hdisk0 hdisk1

16) create a lv hd7x ( sysdump) and assign it to hdisk1 (eg was 30pps)

17) sysdumpdev -l

18) sysdumpdev -Ps /dev/hd7x

19) sysdumpdev -l

Tuesday, September 2, 2008

EMC Solution Enabler Installation

#/tmp/se6500-AIX-powerpc-ni ./se6500_install.sh -install
#---------------------------------------------------------------------------- # EMC Installation Manager #---------------------------------------------------------------------------- Copyright 2007, EMC Corporation All rights reserved.
The terms of your use of this software are governed by the applicable contract.
Solutions Enabler Native Installer[RT] Kit Location : /tmp/se6500-AIX-powerpc-ni
Checking for OS version compatibility...... Checking for previous installation of Solutions Enabler......
Following daemons can be set to run as a non-root user: storevntd, storgnsd, storwatchd Do you want to run these daemons as a non-root user? [N]:
Checking for active processes..... Checking for /usr/symcli/storbin/cimserver... Checking for /usr/symcli/bin/symapisrv...
Checking for active SYMCLI daemons...
Checking for active SYMCLI components...
Install All EMC Solutions Enabler Shared Libraries and Run Time Environment ? [Y]: Install EMC Solutions Enabler 64-bit Shared Libraries ? [N]:Y Install Symmetrix Command Line Interface SYMCLI ? [Y]: Install EMC Solutions Enabler SRM Database Run Time Components ? [N]: Install Option to Enable JNI Interface for EMC Solutions Enabler APIs ? [N]: Install Option to Enable EMC Solutions Enabler Star Component ? [Y]: Install Option to Enable EMC Solutions Enabler SYMRECOVER Component ? [Y]:
Do you want to change default permission on /var/symapi directory from [755]? [N]:
Checking for disk space availability....
Persistent data files exist in directory[/usr/emc/API/symapi]...
Do you want to MOVE this data to /usr/emc/API/symapi_old? [N]:
Installing SYMCLI.DATACORE.rte.....
Installing SYMCLI.DATASTORBASE.rte.....
Installing SYMCLI.CORE.rte.....
Installing SYMCLI.STORBASE.rte.....
Installing SYMCLI.STORFULL.rte.....
Installing SYMCLI.SRMBASE.rte.....
Installing SYMCLI.64BIT.rte.....
Installing SYMCLI.SYMCLI.rte.....
Installing SYMCLI.STAR_PERL.rte.....
Installing SYMCLI.SYMRECOVER.rte.....
Creating OPENSSL Certificate....
Enabling stordaemon...

Do not forget to run 'symcfg discover' after the installation completes and whenever your configuration changes.
You may need to manually rediscover remotely connected arrays. Please see the installation notes for further information.
#----------------------------------------------------------------------------- # The following HAS BEEN INSTALLED in /opt/emc via the installp utility. #----------------------------------------------------------------------------- ITEM PRODUCT VERSION 01 EMC Solutions Enabler V6.5.0.0 RT KIT #-----------------------------------------------------------------------------
#/tmp/se6500-AIX-powerpc-ni ./se6500_install.sh -check
#---------------------------------------------------------------------------- # EMC Installation Manager #---------------------------------------------------------------------------- Copyright 2007, EMC Corporation All rights reserved.
The terms of your use of this software are governed by the applicable contract.
Checking for Solutions Enabler Native Installer kit Installation......
Sl No Fileset Version ----- ------- -------- 1 SYMCLI.64BIT.rte 6.5.0.0 2 SYMCLI.CORE.rte 6.5.0.0 3 SYMCLI.DATACORE.rte 6.5.0.0 4 SYMCLI.DATASTORBASE.rte 6.5.0.0 5 SYMCLI.SRMBASE.rte 6.5.0.0 6 SYMCLI.STAR_PERL.rte 6.5.0.0 7 SYMCLI.STORBASE.rte 6.5.0.0 8 SYMCLI.STORFULL.rte 6.5.0.0 9 SYMCLI.SYMCLI.rte 6.5.0.0 10 SYMCLI.SYMRECOVER.rte 6.5.0.0#/opt/emc/SYMCLI/V6.5.0/bin ./symcfg discover
This operation may take up to a few minutes. Please be patient...#/ symlmf
E M C S O L U T I O N S E N A B L E R
SOLUTIONS ENABLER LICENSE MANAGEMENT FACILITY
Register License Key (y/[n]) ? yEnter License Key : *********************
Register License Key (y/[n]) ? n
#/ cat /var/symapi/config/symapi_licenses.datCheck for License Files .And all is done.

Monday, September 1, 2008

Easily Configure TCP/IP on Your AIX System

Easily Configure TCP/IP on Your AIX System::::::
Summary: With AIX, you can configure your TCP/IP network with a single command, mktcpip. On other systems, setting up TCP/IP might involve creating and editing multiple files, executing a number of commands, setting various variables, locating values for persistence after reboot, and starting several daemons. The mktcpip command completes all the necessary TCP/IP configuration tasks for a typical system. The process is even easier when you use the System Management Interface Tool (SMIT) to prompt you for all necessary parameters to configure your network.
After you gather the prerequisite information, you can run the mktcpip command three ways: by using SMIT, the command line, or the Web-based System Manager.
Prerequisites::::::
Gather your network configuration information:
v IP address
v Host name
v Domain Name
v Subnetmask (optional)
v Name server (optional)
v Gateway address (optional)
Procedure::::::
Configuring TCP/IP is easiest when you use SMIT. On the command line, type the
following fast path:
smitty mktcpip





A dialog box requests which type of interface you plan to use. Then, SMIT builds a screen that lists each required value, as shown in the following example. After you fill in the fields with the network information that you have collected, the tool runs the mktcpip command in the background and makes the network available. Your task is finished.


If you prefer the command line approach, you can specify all the necessary
parameters in a single instruction, as shown in the following example:


mktcpip -h server1 -a 10.47.1.3 -m 255.255.0.0 -i en0 \ -n 9.3.240.2 -d itsc.austin.ibm.com -g 9.3.240.1 -s -C 0 -Ano If you prefer a more graphical interface, you can use the Web-based System Manager tool to complete this task. This tool uses icons, windows, and wizards to
guide you through the configuration. To start this interface, type the following on
the command line:
wsm
No matter which method you choose, online help is available to assist you. For example, to access online help within SMIT, use the F1 key. If you want to further configure your network, for example, if you want to select more than one interface type, SMIT has an easy interface for that, too. On the command line, type:
smitty configtcp

The following sections provide additional information to help you with configuring your network.
Further Configuration ::::
Customizing your TCP/IP configuration beyond the minimal configuration is easily done through SMIT, the command line, or the Web-based System Manager.

SMIT menus guide you through such tasks as:
v Managing static routes
v Flushing the routing table
v Setting or showing host names
v Managing network interfaces or drivers
v Managing domain names or the hosts table (/etc/hosts file)
v Managing network services for the client or server
v Starting or stopping TCP/IP daemons
Naming Conventions for Your Network Devices and Interfaces
When you install AIX, it automatically detects each adapter card and installs the corresponding interface software. AIX uses the following naming convention for network devices and interfaces:
Device Type Device Name Interface Name
Asynchronous Transfer Mode (ATM) atm# at#
Ethernet (IEEE 802.3) ent# et#
Ethernet (Standard, Version 2) ent# en#
Fiber Distributed Data Interface (FDDI) fddi# fi#
Loopback N/A lo#
Token-ring tok# tr#
The # sign represents the number of the device or interface you intend to use.

Name Services
If you use name services, you can provide the minimal information needed through the mktcpip command. Typically, the /etc/resolv.conf file stores your domain name and name server IP address. The mktcpip command creates or updates the /etc/resolv.conf file for you. By default, the resolver routines on hosts running TCP/IP use the following lookup sequence:
1. Domain Name Server (DNS)
2. Network Information Service (NIS or NIS+), if active
3. Local /etc/hosts file
But you can override the default lookup by editing the /etc/netsvc.conf file. (See the AIX Files Reference for details.) Also, you can set the NSORDER environment variable to override the host settings in the /etc/netsvc.conf file.
Gateways
A machine can communicate to the network through a gateway. A gateway contains the addressing and routing information for each host on its network, and can use routing daemons to broadcast routing information to, and receive routing information from, other gateways. TCP/IP routes information to the appropriate computer on the network using address information carried in a packet or stream of information.


AIX version 5.0 allows a host to discover if one of its gateways is down (called dead gateway detection) and, if so, choose a backup gateway, if one has been configured. Dead gateway detection can be passive (the default) or active. In passive mode, a host looks for an alternate gateway when normal TCP or ARP requests notice the gateway is not responding. Passive mode provides a ″best effort″ service and requires very little overhead, but there may be a lag of
several minutes before a dead gateway is noticed. In active mode, the host periodically pings the gateways. If a gateway fails to respond to several consecutive pings, the host chooses an alternate gateway. Active mode incurs added overhead, but maintains high availability for your
network. In either mode, the host chooses the alternate gateway with the lowest associated
cost value. You determine the cost value, using any criteria you wish, when configuring TCP/IP. The value can be any number from 0 (the default) to 2147482647.
Flags for the mktcpip Command :
The mktcpip command can do much more than minimal TCP/IP configuration.
The following table defines all the flags available for the mktcpip command.
-A yes/no Active dead gateway detection (AIX Version 5.0 and later). If set to no (the default), dead gateway detection remains in passive mode.
-a Address Sets the Internet address of the host. Specify the address in dotted decimal notation. Each network interface on the host should have a unique Internet address. The following is the
standard format for setting the Internet address: 127.10.31.2
-C number Specifies the cost of using the selected interface type. This value affects which alternate gateway is chosen when dead gateway detection (AIX Version 5.0 and later) determines the current gateway is down. The value can be any number from 0 (the default) to 2147482647.
-c Subchannel Specifies the subchannel address for a System/370 channel adapter.
-D Destination Sets the destination address for a static route. Specify the address in dotted decimal notation. The following is the standard format for setting the destination address for a
static route: 192.9.52.1
-d Domain Specifies the domain name of the name server the host should use for name resolution, if any. The domain name should be in the following format: Subbdomain.subdomain.rootdomain
-g Gateway Sets the gateway address for a static route. Specify the address in dotted decimal notation. The following is the standard format for setting the gateway address for a static
route: 192.9.52.0
-h Hostname Sets the name of the host. If using a domain naming system, the domain and any subdomains must be specified. The following is the standard format for setting the host name:
hostname The following is the standard format for setting the host name in a domain naming system: hostname.subdomain.subdomain.rootdomain
-i Interface Specifies a particular network interface, for example: tr0
-m SubnetMask Specifies the mask that the gateway should use in determining the appropriate subnetwork for routing. The subnet mask is a set of 4 bytes, as in the Internet address.
The subnet mask consists of high bits (1s) corresponding to the bit positions of the network and subnetwork address, and low bits (0s) corresponding to the bit positions of the host address.
-n NameserverAddress Specifies the Internet address of the name server that the host uses for name resolution, if applicable. The address should be entered in dotted decimal notation, for example: 127.1.0.1
-r RingSpeed Specifies the ring speed for a token-ring adapter. Valid values for the RingSpeed variable are either 4- or 16-Mbps.

-S Interface Retrieves information for System Management Interface Tool (SMIT) display.
-s Starts the TCP/IP daemons.
-t CableType Specifies cable size for Standard Ethernet or IEEE 802.3 Ethernet networks. Valid values for the CableType variable are dix for thick cable, bnc for thin cable, or N/A for Not
Applicable. The -t CableType flag should be used only for Standard Ethernet (en) and IEEE 802.3 Ethernet (et) interfaces.
TCP/IP Subsystems
The mktcpip command runs a shell script called rc.tcpip to start the TCP/IP
daemons for your configuration. The script contains start stanzas for the following
daemons:
autoconf6, ndpd-host Internet Protocol version 6 (IPv6)
dhcpcd, dhcprd,
dhrcpsd
Dynamic Host Control Protocol (DHCP) daemons
Easily Configure TCP/IP on Your AIX System
inetd Internet daemon that starts related services such as telnet and ftp
lpd Print server daemon

mrouted Multicast routing daemon

named Domain name server in a domain network

portmap Port lookup facility used for remote procedure calls (RPCs) routed or gated Dynamic routing (both daemons cannot run simultaneously) rwhod Remote uptime and users daemon sendmail Mail transfer agent snmpd, dpid2 Simple network management protocol (SNMP) daemons syslog Log server for standard UNIX error logs timed, xntpd Time synchronization daemons By default, the script starts the syslogd, portmap, inetd, lpd, and sendmail daemons and puts their entries into the /etc/inittab file so the subsystems begin automatically after every reboot. To automatically start any of the other listed daemons, simply uncomment their corresponding lines in the rc.tcpip file. You can add start stanzas for other daemons, too.
Useful TCP/IP References
Configuration, Status, and Troubleshooting Commands
lsdev -Cc adapter and
lsdev -Cc if
List system adapters and IP interfaces
netstat -in Show status of IP interfaces with numeric addresses
netstat -rn Show status of TCP/IP routes with numeric addresses
arp -a Display local ARP cache
no -a and no -o Display/set kernel variable values, such as ipforwarding
ifconfig and route Display status and configure temporarily
mkdev (chdev, rmdev, etc.) and SMIT Configure permanently
lsattr -El Display ODM database attributes for the specified interface or adapter
nslookup :Troubleshoot DNS
host: Resolve host name to IP address and vice versa
hostname :Display current local host name
System Files
/etc/hosts : Local hosts table
/etc/rc.* :Scripts for TCP/IP, NFS, and so forth
/etc/resolv.conf :Name resolver
/etc/netsvc.conf: Name resolution order
/usr/sample/tcpip/named.* : Sample files that can be copied and edited
/etc/named.*: DNS resolution files
/etc/hosts.equiv,
/etc/rhosts, and /etc/hosts.lpd :Remote user access files