Techdocs

Full fabric feature not activating

2012-01-25T12:47:00.003+01:00

Symptom:
After adding new full fabric license key to a brocade fc switch the feature is unusable despite the licenseshow displays the new feature. The fabswitchshow output display "fabric license: FALSE"
The ISL does not work. Isolating with "No fabric license" error message.

Workaround:
Reboot the switch after adding the new license key.
The instructions on the license paper/email do not suggest it and the web interface also does not display any message. Only the cli displays a warning message.
After the switch is rebooted the fabswitchshow displays the flag as TRUE.

Locating the WWPN without restarting the host in linux os

2012-01-19T10:18:00.004+01:00

"To locatethe WWPN without restarting the host, you can use any of the followingmethods:
- For QLogic or Emulex adapters, you can find the WWPN in the /proc/scsi/adapter_type/n directory,where adapter_type is the host adapter type and n isthe host adapter number for your card. Your host adapter type canbe either qlaxxxx for QLogicadapters or lpfc for Emulex adapters.
- If you downloaded a QLogic adapter from the QLogic websiteinstead of using the default version that is included with RHEL, tofind the WWPN run the cat /proc/scsi/adapter_type/n command,where adapter_type is the host adapter type (forexample, qla2xxx or qla2300),and n is the host adapter number for your card.
- For a QLogic adapter that is included with RHEL 4.x orearlier, to find the WWPN run the cat /proc/scsi/adapter_type/n command,where adapter_type is the host adapter type, and n isthe host adapter number for your card. In most cases, the adaptertype is qla2xxx.
- For a QLogic adapter that is included with RHEL 5.x orlater, the adapter WWPN information might not be available in the/proc/scsi/adapter_type/n directorybecause of the migration to sysfs, If so, run the following command:
```
cat /sys/class/scsi_host/hostn/device/fchost\:hostn/port_name
```
  where n isthe host adapter number for your card."

RPT test does not work after exporting to the AMC

2012-01-05T11:22:00.001+01:00

Problem description:

RPT test works fine but after you export to the AMC via ITCAM plugin it stops working and get a "Request timed out" error.

After examining the request xml in the log you can see extra header information:

<reqmetrics:arm_correlator soapenv:actor="reqmetricsURI"
xmlns:reqmetrics="http://websphere.ibm.com" > ...
< /reqmetrics:arm_correlator >

I faced this problem when I created test against a webservice running in Webshpere Message Broker that does not implemented the ARM feature.

Solution:

"Starting with RPT version 8.2 and later,you can modify the `eclipse.ini` file (typically locatedin the RPT workbench installation directory, for example, C:\ProgramFiles\IBM\SDP) by adding the Java option RPTNOSOAPHEADERRTB to suppressthe generation of these additional SOAP headers. For example:

...
-install
C:/Program Files/IBM/SDP/rptse
-launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.0.v20100503
-vmargs
-DRPTNOSOAPHEADERRTB
-Xquickstart
...

If you experience this problem, enable this RPTNOSOAPHEADERRTBoption in your RPT workbench and regenerate your scripts before uploadingthem to the Application Management Console for playback by the RoboticResponse Time agent."
Full IBM artikle here

Recommended parameters in dual-VIOs environmnent

2011-12-14T14:02:00.011+01:00

Here are some recommended parameters when using dual-VIO and vscsi adapters

1. Load balance/Failover
Because the vscsi adapter does not support other then failover settings, you should manual load balance the io between the VIOS.

chpath -l hdiskX -p vscsiY -a priority=Z

Starting with AIX 5.3 TL9 (APAR IZ28537) and AIX 6.1 TL2 (APAR IZ28554), a
new Virtual SCSI adapter error recovery parameter has been added and must
be configured to fast_fail. When this parameter is set to fast_fail, the virtual client
adapter sends FAST_FAIL_MAD to the Virtual I/O Server and it fails the I/Os
immediately rather than delayed. This parameter is configured using the chdev
command as shown in the following example.

chdev -l vscsiX -a vscsi_err_recov=fast_fail -P

2. Health check

chdev -l hdiskX -a hcheck_interval=60 -a hcheck_mode=nonactive -P

hcheck_mode=nonactive means that healthcheck commands are sent down paths that have no active I/O,including paths with a state of failed.
The hcheck_interval attribute defines how often the healthcheck is performed.

chdev -l vscsiX -a vscsi_path_to=30 -P

It allows the client adapter to check the health of the Virtual I/O
Server servicing a particular adapter and detect if a Virtual I/O Server is not
responding to I/O requests.

3. Queue depth

Must be configured to match the queue depth value used for the physical disk on the Virtual I/O Server.

chdev -l hdiskX -a queue_depth=20 -P

Care should be taken if you set the queue depth on VIOC. The vhost adapter in VIOS has a fixed queue_depth value: 512. That value is divided by the number of LUNs accessible by the vhost adapter. 2 are reserved for the adapter use and 3 are reserved for each LUN.
The formula: (512 - 2) / (vioc_queue_depth + 3) = X
If VIOC's disks are using the default 3 value, then the max LUN number is 85.

4. VIOS settings

chdev -dev fscsiX -attr fc_err_recov=fast_fail dyntrk=yes -perm
chdev -dev hdiskX -attr reserve_policy=no_reserve
chdev -dev hdiskX -attr algorithm=round_robin
chdev -dev hdiskX -attr hcheck_interval=60 -attr hcheck_mode=nonactive -perm

Some comments and the figure is from the "IBM PowerVM Virtualization Introduction and Configuration" Redbook

Get PATH priority in AIX

2011-12-14T13:08:00.001+01:00

#!/bin/ksh

printf "disk path priority \n"
lsdev -Cc disk | while read disk rest
do
     for path in `lspath -l ${disk} | awk '{print $3}'`
       do
           pri=`lspath -AEl ${disk} -p ${path} | awk '{print $2}'`
           printf "$disk $path $pri\n"
      done
done

RBAC scripting

2011-12-05T22:14:00.001+01:00

I found a bit difficult to check authorizations, privileges ..etc in RBAC.
Here is a simple script to make easier the administration of RBAC environmnet.
Its the first beta. It need to test.

#!/bin/ksh
usage="Usage:\n
$0 [list|checkauth cmd|checkcmd cmd] role\n
$0 copy srcrole dstrole\n
$0 add role authorization\n
$0 remove role authorization\n"

mkrole=/usr/bin/mkrole
chrole=/usr/bin/chrole
lsrole=/usr/sbin/lsrole

case $1 in
#List authorization of the given role
list)
if [ $# -ne 2 ]; then
echo $usage
exit 1
fi

role=$2
p_auths=`lsrole -a all_auths ${role} | cut -d "=" -f 2`
echo "Authorization(s) for role ${role}:"
echo "================================"
list=`echo ${p_auths} | tr "," "|" `
cmds=`lssecattr -c -a accessauths ALL | grep -E "${list}" | awk '{print $1}' | tr "\n\r" ","`
echo $p_auths | tr "," "\n\r" | sort
echo ""
echo "Accessible commands by the role:"
echo "================================"
echo ${cmds}
;;

#Find the given command in the privileged command database
checkauth)
if [ $# -ne 2 ]; then
echo $usage
exit 1
fi
cmd=`which $2 2>/dev/null`
if [ $? -eq 0 ]; then
lssecattr -c -F ${cmd}
else
echo "Command ${2} not found! Try to use full path!"
exit 2
fi
;;

#Try to find given command in the privileged command database and than try to find the associated authorization
checkcmd)
if [ $# -ne 3 ]; then
:120
n_auth=$3
if [ $# -ne 3 ]; then
echo $usage
exit 1
fi

s_auths=`lsrole -a all_auths ${s_role} | cut -d "=" -f 2 2>/dev/null`
if [ ${#s_auths} -eq 0 ]; then
echo "Warning! The specified role ${s_role} does not contain any authorization!"
exit 0
fi

$chrole authorizations=${s_auths},${n_auth} $s_role
if [ $? == 0 ]; then
echo "$s_role has the following authorizations now: ";lsrole -a all_auths ${s_role} | cut -d "=" -f 2 | tr "," "\n\r"
fi
;;
copy)
s_role=$2
d_role=$3
s_auths=`lsrole -a all_auths ${s_role} | cut -d "=" -f 2`
if [ ${#s_auths} -eq 0 ]; then
echo "Warning! The specified role ${s_role} does not contain any authorization!"
fi

$mkrole authorizations=${s_auths} $d_role
if [ $? = 0 ]; then
echo "Done. $d_role has the following authorizations: ${s_auths} "
fi
;;

remove)
s_role=$2
r_auth=$3

if [ `lsrole -f $s_role 2>/dev/null | wc -l` -eq 0 ]; then
echo "The specified role ${s_role} does not exist!"
exit 2
fi

r_auths=`lsrole -a all_auths ${s_role} | cut -d "=" -f 2 |tr "," "\n\r" | grep -i ${r_auth}`
orig_auths=`lsrole -a all_auths ${s_role} | cut -d "=" -f 2|tr "," "\n\r"`
echo "All authorizations used by this role:\n$orig_auths"
if [ ${#r_auths} -eq 0 ]; then
echo "Nothing to remove!"
exit 3
fi
echo "Do you real want to remove this authorizations from role ${s_role}?\n${r_auths}"
printf "Y/N"; read answer;
answer=`echo $answer | tr '[:upper:]' '[:lower:]'`

if [ "${answer}" == "y" ]; then
n_auths=`lsrole -a all_auths ${s_role} | cut -d "=" -f 2 | tr "," "\n\r" | grep -vi ${r_auth}|tr "\n\r" ","`
if [ ${#n_auths} -eq 0 ]; then
echo "Warning! The specified role ${s_role} will not have any authorization!"
fi
${chrole} authorizations=${n_auths} ${s_role}
${lsrole} -f ${s_role}
else
echo "Exiting ..."
exit 1
fi

;;
*)
echo $usage
;;

Successful steps to get a working sudosh in AIX

2011-11-29T21:27:00.008+01:00

sudosh is a very imressive tool to log the activity on an AIX host.

Instead of using the prebuild rpm package I suggest compile your own sudosh binary. Theese errors may happen if You are using the rpm (all version v1.6.3, v2 ..etc)
1. CTRL+C kick you off You from the shell
2. Smitty screens don't working whatever TERM settings You're using.
3. Cant set vi and other env variable

After I compiled from source this errors aren't occured.

Theese are the configure paramateres I used:
./configure --with-defshell=`which ksh` --prefix=/usr/
You need sudo-1.6.9p15-2noldap or other sudo rpm package installed.

dsm sample scripts

2011-11-21T15:59:00.001+01:00

#!/bin/ksh
####################################################
# This simple script helps to add new DSM node #
# to the nodeinfo file set in the properties file #
####################################################

E_INVALID_USAGE=1
E_NODE_ALREADY_EXISTS=2
E_COULD_NOT_FIND_LPAR=3
E_APPEND_TO_FILE=4

node=$1
lpar_name=$2

access_type=hmc
access_ip=hmc
access_usr=hscroot
passwd_file=/etc/ibm/sysmgt/dsm/config/hmc_passwd
dsm_nodeinfo_file=`grep nodeinfo /etc/ibm/sysmgt/dsm/dsm.properties | cut -d "=" -f 2 | tr -d " "`

if [ $# -lt 1 ]; then
echo "Usage $0 {nodename} [lpar_name]. You can use separate dsm node name and lpar name "
exit $E_INVALID_USAGE
fi

if [ $# == 1 ]; then
lpar_name=$node
fi

rc=`grep -i "^${node}|" ${dsm_nodeinfo_file} | wc -l`
if [ ${rc} == 1 ]; then
echo "Node ${node} already exists in nodeinfo file ${dsm_nodeinfo_file}!"
exit ${E_NODE_ALREADY_EXISTS}
fi

function get_server {

s_file=serverlist.tmp
export i=1
ssh ${access_usr}@${access_ip} lssyscfg -r sys -F name,type_model,serial_num > $s_file
cat $s_file |cut -d "," -f 1 | while read name
do
echo "${i}. ${name}"
i=`expr ${i} + 1`
done

print -n "Server to use:";read server_no

server=`cat $s_file | head -${server_no} | tail -1`
t_hw=`echo $server| cut -d "," -f 2`
t_sn=`echo $server| cut -d "," -f 3`
t_name=`echo $server| cut -d "," -f 1`
}

get_server
lpar_id=`ssh ${access_usr}@${access_ip} lssyscfg -r lpar -m ${t_name} -F name,lpar_id | grep ^"${lpar_name},"| cut -d "," -f 2`

if [ "${lpar_id}" == "" ]; then
echo "Could not find lpar ${lpar_name} in system ${t_name}"
exit ${E_COULD_NOT_FIND_LPAR}
fi

line="${node}|${access_type}|${access_ip}|TargetHWTypeModel=${t_hw}:TargetHWSerialNum=${t_sn}:TargetLPARID=${lpar_id}|${passwd_file}"
echo $line >> ${dsm_nodeinfo_file}

if [ $? == 0 ]; then
echo "${line} added to ${dsm_nodeinfo_file}"
else
echo "An error occured during adding new line to ${dsm_nodeinfo_file}"
exit $E_APPEND_TO_FILE
fi

dsm error

2011-11-18T14:28:00.009+01:00

Today I tried to use the replacement of dsh called dsm.
I followed the guide and try to get the lpar mac using the dgetmacs command.
The program returned with RC=1 and not reported the ethernet macs.

"nim:/etc/ibm/sysmgt/dsm# dgetmacs -n dsm -V
Using an adapter type of "ent".
Output log for dgetmacs is being written to /var/ibm/sysmgt/dsm/log/dgetmacs.log.
Running Command: /opt/csm/bin/dsh -C DSH -n dsm -v -t 10 /bin/echo test.success
Could not dsh to node dsm.
Attempting to use openfirmware method to collect MAC addresses.
Acquiring adapter information from Open Firmware for node dsm.
Running Command: /opt/ibm/sysmgt/dsm/dsmbin/lpar_netboot -i -v -x -M -temp_file /tmp/dgetmacs.dsm.15401108 -n -t ent -J hmc -j hmc -F /etc/ibm/sysmgt/dsm/config/hmc_passwd -A 8 067213P 8233-E8B 2>>/var/ibm/sysmgt/dsm/log//dgetmacs.dsm.log.322 2>&1
dgetmacs: 2760-185 Issuing the command "/opt/ibm/sysmgt/dsm/dsmbin/lpar_netboot -M -n -t ent -J hmc -j hmc -F /etc/ibm/sysmgt/dsm/config/hmc_passwd -A 8 067213P 8233-E8B" gave a return code of 1. The routine will continue.
No adapters found for node dsm.
Could not get mac address for this aix node "dsm" "

I found the following article at Chris' Blog.

He said that this issue was found in 7.1 SP2 and maybe it will resolved in SP3. So, NOT!
The cat file size still 3905 dispite he talked to the developpers.

The funnies thing is that the lppchk is NOT reporting any CRC or other error.

The /usr/lib/nls/msg/en_US/IBMhsc.netboot.cat file is part of the bos.msg.en_US.rte.
and the current version is 7.1.0.0

I sent an email to Chris. If he send me the right cat file I will give it a last chance.

..
Chris sent me the right-size cat file. After I replaced the original with this one the problem disappeared.
The last (this time 7100-01-01-1141) TL+SP does not solve the problem. The bos.msg.en_US.rte fileset version is still 7.1.0.0!

VIO profile

2011-11-16T14:35:00.002+01:00

1. Add export ENV=/home/padmin/.kshrc to the /home/padmin/.profile
2. Create /home/padmin/.kshrc file with the following / similar content:

HOSTNAME=`hostname`
set -o vi

PWD=`pwd`

if id >/dev/null 2>&1 ; then
export USER='root(oem_setup_env)'
PS1='[${USER}@${HOSTNAME}:#${PWD}] '
else
export USER=$LOGNAME
PS1='[${USER}@${HOSTNAME}:] '
alias aix=oem_setup_env
fi

IBM SAN Volume Controller SVC console inital config

2011-10-24T11:11:00.003+02:00

How to add SVC Cluster to SVC console.
The steps I always forget

There is a default icat.ppk file in "C:\Program Files\IBM\svcconsole\cimom" directory. Load this file to the puttygen and save the public key. Use this public key when adding new user to the svc. Define "SVC Console" access when creating the user.

This error message indicating that the above steps resolve your problem:
"Availibility Status"
- "Key Refused"
- "Invalid account"

IBM SAN Volume Controller V4x Resetting SVC Console Password

2011-10-06T12:10:00.001+02:00

1/ Stop the CIMOM service
2/ go to the install directory svcconsole\cimom\pegasus (or just %SVCAGENT_HOME%\pegasus)
3/ open the cimserver.passwd file in a text editor
4/ delete the entry for user being reset(the file is formatted user:password, delete the entire entry)
5/ save and close the file
6/ restart the CIMOM service
7/ From a Windows command line prompt perform the following;
cimuser -a -u superuser -w passw0rd
8/ Verify log in from the GUI

IBM SAN Volume Controller V4x Resetting SVC Console Password

2011-10-06T12:10:00.000+02:00

Useful nim commands and some common error

2011-09-06T13:07:00.005+02:00

create mksysb backup on nim master:
nim -o define -t mksysb -a server=master -a location=[LOCATION] -a source=[SOURCE NODE] -a mk_image=yes [OBJECT NAME]

First use the "-a size_preview=yes" to investigate the needed space in the filesystem.

0042-175 c_ch_nfsexp: An unexpected result was returned by the
"/usr/sbin/exportfs" command:
exportfs: 1831-186 /nim/mksysb/ha-node2.mksysb not found in /etc/exports

In this case the exportfs -e displays similar like this:
nim:/# showmount -e
export list for nim:
/nim/mksysb (everyone)

Resolution: you have to remove the above nfs export and let nim exports the needed dirs

To be continued ...

Instructions to convert DS4000 disks from MPIO to AIX_fcparray(RDAC).

2011-08-30T13:49:00.001+02:00

Useful article from www.aixmind.com

" Instructions to convert DS4000 disks from MPIO to AIX_fcparray(RDAC).

Note: The manage_disk_drivers command usage changed with AIX 6.1 TL4 and 5.3 TL11. The AIX infocenter describes the old usage:
http://publib.boulder.ibm.com/infocenter/aix/v6r1/index.jsp?topic=/com.ibm.aix.cmds/doc/aixcmds3/manage_disk_drivers.htm

Examples
1. To list storage families and drivers, enter the following command:
manage_disk_drivers
The system displays a message similar to the following message:
1: DS4100: currently RDAC; supported: RDAC/fcparray, MPIO 2: DS4300: currently MPIO; supported: RDAC/fcparray, MPIO 3: DS4500: currently RDAC; supported: RDAC/fcparray, MPIO 4: DS4700/DS4200: currently RDAC; supported: RDAC/fcparray, MPIO 5: DS4800: currently RDAC; supported: RDAC/fcparray, MPIO
2. To modify the driver for a storage family, enter the following command:
manage_disk_drivers -c 1
The system displays a message similar to the following message, prompting for confirmation of the change:
DS4100 currently RDAC/fcparray Change to alternate driver? [Y/N] Y DS4100 now managed by MPIO It is necessary to perform a bosboot before rebooting the system in order to incorporate this change into the boot image. In order to change to the new driver, either a reboot or a full unconfigure and reconfigure of all devices of the type changed must be performed.

————
Here is an example showing the updated command usage:
1) Check the AIX systems driver support and state by running the following command:manage_disk_drivers -l

This will display the DS4000 devices that are supported by MPIO as well as RDAC and if they are currently configured for MPIO or RDAC enablement.

Example A:
manage_disk_drivers -l
Device Present Driver Driver Options
2810XIV AIX_AAPCM AIX_AAPCM,AIX_non_MPIO
DS4100 AIX_SDDAPPCM AIX_APPCM,AIX_fcparray
DS4200 AIX_SDDAPPCM AIX_APPCM,AIX_fcparray
DS4300 AIX_SDDAPPCM AIX_APPCM,AIX_fcparray
DS4500 AIX_SDDAPPCM AIX_APPCM,AIX_fcparray
DS4700 AIX_SDDAPPCM AIX_APPCM,AIX_fcparray
DS4800 AIX_SDDAPPCM AIX_APPCM,AIX_fcparray
DS3950 AIX_SDDAPPCM AIX_APPCM
DS5020 AIX_SDDAPPCM AIX_APPCM
DS5100 AIX_SDDAPPCM AIX_APPCM

2) From “example A” we know that the DS4500 is currently enabled for AIX_SDDAPPCM (MPIO with SDDPCM). To change which driver is managing the DS4000, do the following commands in order-

manage_disk_drivers -d DS4800 -o AIX_fcparray

The “d” flag for which storage and “o” flag which driver you would like to use.

Example B:
manage_disk_drivers -d DS4800 -o AIX_fcparray

bosboot: Boot image is 42141 512 byte blocks.
********************** ATTENTION *************************
For the change to take effect the system must be rebooted
# shutdown –Fr

3) Once the server has rebooted, all the hdisk devices that were converted will now be configured under the RDAC driver.

manage_disk_drivers -l
Device Present Driver Driver Options
2810XIV AIX_AAPCM AIX_AAPCM,AIX_non_MPIO
DS4100 AIX_SDDAPPCM AIX_APPCM,AIX_fcparray
DS4200 AIX_SDDAPPCM AIX_APPCM,AIX_fcparray
DS4300 AIX_SDDAPPCM AIX_APPCM,AIX_fcparray
DS4500 AIX_SDDAPPCM AIX_APPCM,AIX_fcparray
DS4700 AIX_SDDAPPCM AIX_APPCM,AIX_fcparray
DS4800 AIX_Fcparray AIX_APPCM,AIX_fcparray
DS3950 AIX_SDDAPPCM AIX_APPCM
DS5020 AIX_SDDAPPCM AIX_APPCM
DS5100 AIX_SDDAPPCM AIX_APPCM

You can also use lsdev to see what driver is managing the disks. Example:
$ lsdev -Cc disk

hdisk5 Available 0D-08-02 1815 DS4800 Disk Array Device <=== fcparray managed (RDAC)

hdisk61 Available 06-09-02 IBM MPIO DS4800 Array Disk <=== SDDPCM managed

hdisk6 Available 06-08-02 MPIO Other DS4K Array Disk <=== AIX APPCM managed"

HP - Brocade SAN switch model naming matrix

2011-07-13T10:17:00.001+02:00

ODM Device Configuration Object Classes

2011-07-06T11:52:00.000+02:00

A list of the ODM Device Configuration Object Classes follows:

PdDv	Predefined Devices
PdCn	Predefined Connection
PdAt	Predefined Attribute
Config_Rules	Configuration Rules
CuDv	Customized Devices
CuDep	Customized Dependency
CuAt	Customized Attribute
CuDvDr	Customized Device Driver
CuVPD	Customized Vital Product Data

hacmp tutorial

2011-07-04T19:20:00.001+02:00

Cluster Manager (clstrmgr)
It uses services provided by the RSCT subsystems to monitor the status of the nodes and their interfaces. It receives ibformation from Topology Sevices and uses Group Services for inter-node communication. It invokes the appropriate scripts in response to node or network events.(recovering from SW/HW failures, request to online/offline a node, request to move/online/offline a resource group) It maintains update informations about the resource groups (status, location) A daemon which runs on each cluster nodes.

If clstrmgr hangs or is terminated the default action taken by SRC is to issue halt -q, causing the system to crash. Clstrmgr is dependent on RSCT; if topsvcs or grpsvcs has problems with starting, the clstrmgr will not start either.

Cluster Information Program (clinfo)
Clinfo obtains updated cluster information from the Cluster Manager. It makes information about the state of the cluster, nodes, networks and applications. Used by clstat, and it is optional on cluster nodes and clients.

startsrc -s clinfoES starts clinfo (/usr/es/sbin/cluster/etc/rc.cluster this script also starts everything)
stopsrc -s clinfoES stops clinfo

Address Resolution Protocol (ARP)
The Internet communication protocol used to dynamically map Internet addresses to physical (hardware/MAC) addresses on local area networks.
The /usr/sbin/cluster/etc/clinfo.rc script, which is called by the clinfo utility whenever a network or node event occurs, updates the system’s ARP cache.

Cluster Communication Daemon (clcomd)
All cluster communication is going through clcomd. It must be running before any cluster services can be started. The trusted IP addresses are stored in the /usr/sbin/cluster/etc/rhosts file. (root.system 0600). Nodes with a non-empty /usr/es../rhosts file (or missing ...rhosts file) will refuse all HACMP related communication with nodes not listed in their rhosts file. If an adapter is missing or there is a format error in the file, clcomd will not function, all connections will be denied. After the first synchronization HACMP ODM classed are populated, so rhosts file can be emptied.

Clcomd is started via /etc/inittab entry, which is created during PowerHA install (clverify is using the clcomd subsystem). It uses port 6191, and it is the transport medium for PowerHA cluster verification, global ODM changes and remote command execution.

clcomd is managed by src (startsrc, stopsrc, refresh; refresh is useful to reread /usr/sbin/cluster/etc/rhosts file), and logs are in /var/hacmp/clcomd/clcomd.log

RSCT (Reliable Scalable Cluster Technology) (earlier: RS/600 Cluster Technology)
It is a software stack, a package of services ("cient subsystems"), which is a prerequisite for HACMP and is packaged with AIX.

-Topology Services: generates heartbeats to monitor nodes, networks and network adapters, diagnoses failures. When a node joins the cluster, topology services adds the adapter information to the machine list.
This "topology" or "connectivity" information is then passed on to group services.

-Group Services: "Client subsystems" (e.g. event management subsystem, RMC subsystems...) forms groups, with a membership list. Provides reliable communication and protocols required for cluster operation. The main daemon is hagsd. Group services coordinates/monitors state changes within the cluster (e.g. node join/leave) and then passes these state changes to the interested subscribers, for example cluster manager or. event management.Enhanced Concurrent mode disks use RSCT group services to control locking.

-Resource Monitoring and Control (RMC): RMC notifies the Cluster Manager about events, so it responds to this event by RSCT. Main damon is rmcd. The process application monitoring uses RMC and therefore does not require any custom script. Dynamic Node Priority (DNP) is calcuated by the use of RMC

-Event Management: Match information about the state of system resources, it initiates the scripts needed managing the cluster.

HACMP relies on topology services for heartbeats and group services for reliable messaging. These services are started prior to the cluster processes. If there are problems with these services the cluster will not start.
-----------------------------------------
SNMP (Simple Network Management Protocol)
It is a popular protocol for network management. It is used for collecting information from, and configuring, network devices, such as servers, printers, hubs, switches, and routers
When giving cldump it says: "Obtaining information via SNMP from Node: xx11b01..."

lssrc -a | egrep 'snm|mib' lists the necessary daemons
ls -l /etc | grep snmp location of conf. files
ls -l /var/tmp | grep snmp location of log files

clsmuxpd (SMUX Peer daemon)
Clusmuxpd provides SNMP support. (IT is before v 5.3, as clinfo improved)
clinfo is based on SNMP; it queries the clsmuxpd daemon for up-to-date cluster information and provides a simple display of it.

-----------------------------------------
C-SPOC (Cluster Single Point of Control)

It helps managing the entire cluster from a single point. In smitty hacmp or with commmands which are under /usr/es/sbin/cluster/cspoc.
C-SPOC using clcomd for HACMP communication between nodes, so /etc/rhosts file no longer used.
If there is a failure of a C-SPOC function it will be logged in the /tmp/cspoc.log, on the node performing the operation.

cspoc.log contains the used commands in this file

-----------------------------------------

Important files:

odmget HACMPlogs shows where are the log files
odmget HACMPcluster shows cluster version
odmget HACMPnode shows info from nodes (cluster version)
(changing the location of the log files: C-SPOC > Log Viewing and Management)
/etc/es/objrepos HACMP ODM files

HACMP Logs: (location differs on newer and older HACMP versions)

/var/hacmp/adm/log/cluster.log main PowerHA log file (errors,events,messages ... /usr/es/adm/cluster.log)
/var/hacmp/adm/history/cluster.mmddyy shows only the EVENTS, generated daily (/usr/es/sbin/cluster/history/cluster.mmddyyyy)
/var/hacmp/log/hacmp.out similar to cluster.log, but more detailed (with all the output of the scripts)

/var/hacmp/clcomd/clcomd.log contains every connect request between the nodes and return status of the requests
/var/hacmp/log/clinfo.log records the activity of the clinfo daemon
/var/hacmp/clverify shows the results of the verifications (verification errors are logged here)
/var/hacmp/log/clutils.log summary of nightly verification

/tmp/clstrmgr.debug debug info about the cluster (clstrmg.debug.long also exists) IBM support using these
/tmp/cspoc.log shows more info of the smitty c-spoc command (good place to look if a command fails)
/tmp/clconvert.log after cluster upgrade shows info about the results

RSCT Logs:
/var/ha/log RSCT logs are here
/var/ha/log/nim.topsvcs... the heartbeats are logged here (comm. is OK between the nodes)

clRGinfo Shows the state of RGs (in earlier HACMP clfindres was used)
clRGinfo -p shows the node that has temporarily the highest priority (POL)
clRGinfo -t shows the delayed timer information
clRGinfo -m shows the status of the application monitors of the cluster
resource groups state can be: online, offline, acquiring, releasing, error, unknown

cldump (or clstat -o) detailed info about the cluster (realtime, shows cluster status) (clstat requires a running clinfo)
cldisp detailed general info about the cluster (not realtime)
cltopinfo Detailed information about the network of the cluster (this shows the data in DCD not in ACD)
cltopinfo -i good overview, same as cllsif: this also lists cluster inetrfaces, it was used prior HACMP 5.1
cltopinfo -m shows heartbeat statistics, missed heartbeats
clshowres Detailed information about the resource group(s)
cllsserv Shows which scripts will be run in case of a takeover

clrgdependency -t PARENT_CHILD -sl shows parent child dependencies of resource groups

clshowsrv -v shows status of the cluster daemons (very good overview!!!)
lssrc -g cluster lists the running cluster daemons

lssrc -ls clstrmgrES shows if cluster is STABLE or not, cluster version, Dynamic Node Priority (pgspace free, disk busy, cpu idle)
ST_STABLE: cluster services running with resources online
NOT_CONFIGURED: cluster is not configured or node is not synced
ST_INIT: cluster is configured but not active on this node
ST_JOINING: cluster node is joining the cluster
ST_VOTING: cluster nodes are voting to decide event execution
ST_RP_RUNNING: cluster is running a recovery program
RP_FAILED: recovery program event script is failed
ST_BARRIER: clstrmgr is in between events waiting at the barrier
ST_CBARRIER: clstrmgr is exiting a recovery program
ST_UNSTABLE: cluster is unstable usually due to an event error
lssrc -ls topsvcs shows the status of individual diskhb devices, heartbeat intervals, failure cycle (missed heartbeats)
lssrc -ls grpsvcs gives info about connected clients, number of groups)
lssrc -ls emsvcs shows the resource monitors known to the event management subsystem)
lssrc -ls snmpd shows info about snmpd

-----------------------------------------
/usr/es/sbin/cluster/utilities/get_local_nodename shows the name of this node within the HACMP
/usr/es/sbin/cluster/utilities/clexit.rc this script halt the node if the cluster manager daemon stopped incorrectly

-----------------------------

Remove HACMP:

1. stop cluster on both nodes
2. remove the cluster configuration ( smitty hacmp) on both nodes
3. remove cluster filesets (startinf with cluster.*)

--------------------------------

If you are planning to do crash-test, do it with halt -q or reboot -q
shutdown -Fr will not work, because it stops hacmp and resource groups garcefully (rc.shutdown), so no takeover will occur

--------------------------------

clhaver - clcomd problem:

If there are problems during start up a cluster or synch. and verif., and you see something like this:

1800-106 An error occurred:
connectconnect: : Connection refusedConnection refused
clhaver[113]: cl_socket(rs2aa05)clhaver[113]: cl_socket(xx04a05): : Connection refusedConnection refused

Probably there is a problem with clcomd.

1. check if if it is running: clshowsrv -v or lssrc -a | grep clcomd
refresh or start it: refresh -s clcomdES or startsrc -s clcomdES

2. check log file: /var/hacmp/clcomd/clcomd.log
you can see something like this: CONNECTION: REJECTED(Invalid address): xx10g01c: 57.57.91.100->57.57.88.139

for me the solution was:
-update /usr/sbin/cluster/etc/rhosts file on both nodes (I added all ip's of both servers (except service ip + service backup ip))
-refresh -s clcomdES

--------------------------------

When trying to bring up a resource group in HACMP, got the following errors in the hacmp.out log file.

cl_disk_available[187] cl_fscsilunreset fscsi0 hdiskpower1 false
cl_fscsilunreset[124]: openx(/dev/hdiskpower1, O_RDWR, 0, SC_NO_RESERVE): Device busy
cl_fscsilunreset[400]: ioctl SCIOLSTART id=0X11000 lun=0X1000000000000 : Invalid argument

To resolve this, you will have to make sure that the SCSI reset disk method is configured in HACMP. For example, when using EMC storage:

Make sure emcpowerreset is present in /usr/lpp/EMC/Symmetrix/bin/emcpowerreset.

Then add new custom disk method:
smitty hacmp -> Ext. Conf. -> Ext. Res. Conf. -> HACMP Ext. Resources Conf. -> Conf. Custom Disk Methods -> Add Cust. Disk

* Disk Type (PdDvLn field from CuDv) [disk/pseudo/power]
* Method to identify ghost disks [SCSI3]
* Method to determine if a reserve is held [SCSI_TUR]
* Method to break a reserve [/usr/lpp/EMC/Symmetrix/bin/emcpowerreset]
Break reserves in parallel true
* Method to make the disk available [MKDEV]

--------------------------------

Once I had a problem with commands 'cldump' and 'clstat -o' (version 5.4.1 SP3)

cldump: Waiting for the Cluster SMUX peer (clstrmgrES)
to stabilize...

Can not get cluster information.

Solution was:
-checked all the below mentioned daemons (clinfo, clcomd,snmpd, hostmibd...) and started what was missing
-and after that I did: refresh -s clstrmgrES (cldump and clstat was OK only after this refresh has been done)

things what can be checked regarding snmp:

-clinfoES and clcomdES:
clshowsrv -v

-snmpd and mibd daemons (if not active startsrc can start it)
root@xx20e01b: / # lssrc -a | egrep 'snm|mib'
snmpmibd tcpip 552998 active
aixmibd tcpip 524418 active
hostmibd tcpip 430138 active
snmpd tcpip 1212632 active

-snmpd conf and log files

root@xx20e01b: / # ls -l /etc | grep snmp
-rw-r----- 1 root system 2302 Aug 16 2005 clsnmp.conf
-rw-r--r-- 1 root system 37 Jun 16 16:18 snmpd.boots
-rw-r----- 1 root system 10135 Aug 11 2009 snmpd.conf
-rw-r----- 1 root system 2693 Aug 11 2009 snmpd.peers
-rw-r----- 1 root system 10074 Jun 16 16:22 snmpdv3.conf
drwxrwxr-x 2 root system 256 Aug 11 2009 snmpinterfaces
-rw-r----- 1 root system 1816 Aug 11 2009 snmpmibd.conf

root@xx20e01b: / # ls -l /var/tmp | grep snmp
-rw-r--r-- 1 root system 83130 Jun 16 20:32 snmpdv3.log
-rw-r--r-- 1 root system 100006 Oct 01 2008 snmpdv3.log.1
-rw-r--r-- 1 root system 16417 Jun 16 16:19 snmpmibd.log

AIX .profile

2011-06-29T10:08:00.001+02:00

~/.profile
PS1=[${USER}@${HOSTNAME}:'$PWD]# '
ENV=/.kshrc

/etc/profile
HOSTNAME=`hostname`
PWD=`pwd`
PS1='[${LOGNAME}@${HOSTNAME}:${PWD}] '

Migrating Users from One AIX System to Another AIX System

2011-06-29T08:55:00.002+02:00

Technote (FAQ)

Question
Migrating Users from One AIX System to Another AIX System

Answer
This document discusses migrating users from one AIX system to another. This does not include transferring the user's personal data or home directories.
The information in this document applies to AIX 5.2 and above.
Since the files involved in the following procedure are flat ASCII files and their format has not changed from V4 to V5, the users can be migrated between systems running the same or different versions of AIX (for example, from V4 to V5).

Files that can be copied over
/etc/group
/etc/passwd
/etc/security/group
/etc/security/limits
/etc/security/passwd
/etc/security/.ids
/etc/security/environ
/etc/security/.profile
NOTE: Edit the passwd file so the root entry is as follows:
root:!:0:0::/:/usr/bin/ksh
When you copy the /etc/passwd and /etc/group files, make sure they contain at least a minimum set of essential user and group definitions.
Listed specifically as users are the following:
• root
• daemon
• bin
• sys
• adm
• uucp
• guest
• nobody
• lpd
Listed specifically as groups are the following:
• system
• staff
• bin
• sys
• adm
• uucp
• mail
• security
• cron
• printq
• audit
• ecs
• nobody
• usr
If the bos.compat.links fileset is installed, you can copy the /etc/security/mkuser.defaults file over. If it is not installed, the file belongs in the /usr/lib/security directory.
If you copy over mkuser.defaults, changes must be made to the stanzas. Replace group with pgrp, and program with shell. A proper stanza should look like the following:
user:
pgrp = staff
groups = staff
shell = /usr/bin/ksh
home = /home/$USER
The following files may also be copied over, as long as the AIX version in the new machine is the same:
/etc/security/login.cfg
/etc/security/user
NOTE: If you decide to copy these two files, open the /etc/security/user file and make sure that variables such as tty, registry, auth1 and so forth are set properly with the new machine. Otherwise, do not copy these two files, and just add all the user stanzas to the new created files in the new machine.
Once the files are moved over, execute the following:
usrck -t ALL
pwdck -t ALL
grpck -t ALL
This will clear up any discrepancies (such as uucp not having an entry in /etc/security/passwd). Ideally this should be run on the source system before copying over the files as well as after porting these files to the new system.
NOTE: It is possible to find user ID conflicts when migrating users from older versions of AIX to newer versions. AIX has added new user IDs in different release cycles. These are reserved IDs and should not be deleted. If your old user IDs conflict with the newer AIX system user IDs, it is advised that you assign new user IDs to these older IDs.

Support for passwords with more than 8 characters and Loadable Password Algorithm

2011-06-22T13:16:00.003+02:00

Support for passwords with more than 8 characters and Loadable Password Algorithm:
Recent advancements in computer hardware makes tradition UNIX password encryption vulnerable to
brute-force password guessing attacks. A cryptographically weak algorithm can lead to recovery of even
strong passwords. AIX 5L introduced Loadable Password Algorithm (LPA) that supports secure password
hash mechanisms. It also removes the eight-character password limitation.
Traditional password crypt function:
The standard AIX authentication mechanism uses a one-way hash function called crypt to authenticate
users. The crypt function is a modified DES algorithm. It performs a one-way encryption of a fixed data
array with the supplied password and a Salt.
The crypt function uses only the first eight characters from the password string; the user's password is
truncated to eight characters. If the password contains less than eight characters, it is padded with zero
bits on the right. The 56-bit DES key is derived by using the 7 bits from each character.
Salt is a two-character string (the 12 bits of the Salt is used to perturb the DES algorithm) chosen from
the character set "A-Z", "a-z","0-9","."(period) and "/". Salt is used to vary the hashing algorithm, so that
the same clear text password can produce 4,096 possible password encryptions. A modification to the
DES algorithm, swapping bits i and i+24 in the DES E-Box output when bit i is set in the Salt, achieves
this while also making DES encryption hardware useless for password guessing.
The 64-bit all-bits-zero block is encrypted 25 times with the DES key. The final output is the 12-bit salt
concatenated with the encrypted 64-bit value. The resulting 76-bit value is recoded into 13 printable
ASCII characters in the form of base64.
Password hashing algorithms:
Hashing algorithms such as MD5 are harder to break than the crypt function. This provides a strong
mechanism against brute-force password guessing attacks. Since the whole password is used for
generating the hash, there is no password length limitation when password hashing algorithms are used
to encrypt the password.
Loadable Password Algorithm:
AIX 5.3 TL7 and AIX 6.1 implemented a Loadable Password Algorithm (LPA) mechanism that can easily deploy new
password encryption algorithms.
64 AIX Version 7.1: Security
Each supported password encryption algorithm is implemented as a LPA load module that is loaded at
runtime when the algorithm is needed. The supported LPAs and their attributes are defined in the
/etc/security/pwdalg.cfg system configuration file.
An administrator can set up a system-wide password encryption mechanism that uses a specific LPA to
encrypt the passwords. After the system-wide password mechanism is changed, passwords that are
encrypted by the previous selected password encryption mechanisms (such as the crypt function) are still
supported.
Support for passwords longer than eight characters:
All of the LPAs implemented for AIX 6.1 and later support passwords longer than eight characters. The
password length limitations vary for different LPAs. The supported maximum password length is 255
characters.
LPA configuration file:
The LPA configuration file is /etc/security/pwdalg.cfg. It is a stanza file that defines the attributes of
the supported LPAs.
The following LPA attributes are defined in the config file:
v The path to the LPA module
v The optional flags that is passed to the LPA module at runtime
The LPA attributes defined in the configuration file can be accessed with the getconfattr and setconfattr
interfaces.
The following example stanza in /etc/security/pwdalg.cfg defines a LPA named ssha256:
ssha256:
lpa_module = /usr/lib/security/ssha
lpa_options = algorithm=sha256
System password algorithm:
A system administrator can set a system-wide password algorithm by selecting an LPA as the password
hashing algorithm. There can only be one active system password algorithm at a time. The system
password algorithm is defined by the pwd_algorithm system attribute in the usw stanza in the
/etc/security/login.cfg file.
The valid values for the pwd_algorithm attribute in the /etc/security/login.cfg file are LPA stanza
names that are defined in the /etc/security/pwdalg.cfg file. Another valid value for the pwd_algorithm
attribute is crypt, which refers to traditional crypt encryption. If the pwd_algorithm attribute is omitted
from the config file, crypt is used as the default value.
The following example of the /etc/security/login.cfg file uses ssha256 LPA as the system-wide
password encryption algorithm.
... ...
usw:
shells = /bin/sh,/bin/bsh,/bin/csh,/bin/ksh,/bin/tsh,/bin/ksh93
maxlogins = 32767
logintimeout = 60
maxroles = 8
auth_type = STD_AUTH
pwd_algorithm = ssha256
... ...
Security 65
The system password algorithm takes effect only for newly created passwords and changed passwords.
After the migration, all subsequent new passwords or password changes use the system password
algorithm. The passwords that existed before the system password algorithm is chosen, either generated
by the standard crypt function or by other supported LPA modules, still work on the system. Therefore,
mixed passwords that were generated by different LPAs can coexist on the system.
Setting up the system password algorithm:
A system administrator can use the chsec command to set up the system password algorithm or use an
editor such as vi to manually modify the pwd_algorithm attribute in the /etc/security/login.cfg file.
It is recommended that you use the chsec command to set the system password algorithm, as the chsec
command automatically checks the definition of the specified LPA.
Using the chsec command
Run the following command to set the smd5 LPA as the system-wide password encryption module:
chsec -f /etc/security/login.cfg -s usw -a pwd_algorithm=smd5
When you use the chsec command to modify the pwd_algorithm attribute, the chsec command checks
the /etc/security/pwdalg.cfg file to verify the specified LPA. The chsec command fails if this check fails.
Using an editor
If you use an editor to manually change the pwd_algorithm attribute value in the /etc/security/
login.cfg file, ensure that the specified value is the name of a stanza that is defined in the
/etc/security/pwdalg.cfg file.
Extending password restrictions:
The rules used by the password program to accept or reject passwords (the password composition
restrictions) can be extended by system administrators to provide site-specific restrictions.
Restrictions are extended by adding methods, which are called during a password change. The
pwdchecks attribute in the /etc/security/user file specifies the methods called.
The AIX Version 6.1 Technical Reference contains a description of the pwdrestrict_method, the subroutine
interface to which specified password restriction methods must conform. To correctly extend the
password composition restrictions, the system administrator must program this interface when writing a
password-restriction method. Use caution in extending the password-composition restrictions. These
extensions directly affect the login command, the passwd command, the su command, and other
programs. The security of the system could easily be subverted by malicious or defective code.

Link to IBM technote

AIX "Fast I/O Failure for Fibre Channel Devices" and "Dynamic Tracking of Fibre Channel Devices".

2011-04-13T15:55:00.000+02:00

  * Introduction
 * Fast I/O Failure for Fibre Channel Devices.
 * Dynamic Tracking of Fibre Channel Devices
 * Fast Fail and Dynamic Tracking Interaction
 * Known Hardware Issues

============
Introduction
============

The purpose of this README is to introduce two new features in the Fibre
Channel Device Driver stack, "Fast I/O Failure for Fibre Channel Devices"
and "Dynamic Tracking of Fibre Channel Devices".


==========================================
Fast I/O Failure for Fibre Channel Devices
==========================================

This release of AIX supports Fast I/O Failure for Fibre Channel devices
after link events in a switched environment.  If the FC adapter driver
detects a link event such as a lost link between a storage device and a
switch, the FC adapter driver will wait a short period of time, on the order
of 15 seconds, to allow the fabric to stabilize.  At that point, if the FC
adapter driver detects that the device is not on the fabric, it will begin
failing all I/Os at the adapter driver.   Any new I/O or
future retries of the failed I/Os will be failed immediately by the adapter
until the adapter driver detects that the device has rejoined the fabric.

Fast Failure of I/O is controlled by a new fscsi device attribute,
'fc_err_recov'.  The default setting for this attribute is 'delayed_fail',
which is the I/O failure behavior that has existed in previous versions
of AIX.  Setting this attribute to 'fast_fail', as shown in the example

chdev -l fscsi0 -a fc_err_recov=fast_fail

(assuming the fscsi device instance is fscsi0), enables fast I/O failure.
Fast fail logic is invoked when the adapter driver receives an indication
from the switch that there has been a link event involving a remote storage
device port via a Registered State Change Notification (RSCN) from the switch.

Fast I/O failure may be desirable in situations where multipathing software
is being used.  Setting 'fc_err_recov' to 'fast_fail' may decrease the I/O
fail times due to link loss between the storage device and switch and allow
faster failover to alternate paths.

In single-path configurations, especially configurations with a single-path
to a paging device, the default 'delayed_fail' setting is the
recommended setting.

The requirements for Fast I/O Failure support are the following:

- Fast Fail is only supported in a switched environment.  It is not supported
 in arbitrated loop environments, including public loop.

- FC 6227 adapter firmware - level 3.22A1 or greater.

- FC 6228 adapter firmware - level 3.82A1 or greater.

- FC 6239 adapter firmware - all firmware levels


Failure to meet these requirements may cause the fscsi device to log an
error log of type INFO indicating that one of these requirements was
not met and that fast fail has NOT been enabled.


=========================================
Dynamic Tracking of Fibre Channel Devices
=========================================

This release provides support for Dynamic Tracking of Fibre Channel Devices.
Previous releases of AIX required a user to unconfigure FC storage device and
adapter device instances before making changes on the SAN that might result
in an N_Port ID (SCSI ID) change of any remote storage ports.

If Dynamic Tracking of FC Devices is enabled, the FC adapter driver will
detect when the Fibre Channel N_Port ID of a device changes and then re-route
traffic destined for that device to the new address while the devices are
still online.  Examples of events that can cause an N_Port ID to change are
moving a cable between a switch and storage device from one switch port to
another, connecting two separate switches via an Inter-Switch Link (ISL),
and possibly rebooting a switch.

Dynamic Tracking of FC devices is controlled by a new fscsi device attribute,
'dyntrk'.  The default setting for this attribute is 'no'.  Setting this
attribute to 'yes', as shown in the example

chdev -l fscsi0 -a dyntrk=yes

(assuming fscsi device instance is fscsi0), enables dynamic tracking.
Dynamic Tracking logic is invoked when the adapter driver receives an
indication from the switch that there has been a link event involving a
remote storage device port.

The requirements for Dynamic Tracking support are the same as those for
"Fast I/O Failure for Fibre Channel Devices" and also include the following
requirements:

- Dynamic Tracking requires that device World Wide Name (Port Name) and
 Node Names remain constant, and that World Wide Name be unique.
 Changing the World Wide Name or Node Name of an available or on-line device
 could result in I/O failures.

 In addition, each FC storage device instance must have world_wide_name
 and node_name attributes.  Updated filesets that contain the 'sn_location'
 attribute mentioned in the next bullet should also be updated to contain
 both of these attributes.

- The storage device must provide a reliable method to extract a unique serial
 number for each LUN. The AIX FC device drivers will not autodetect serial
 number location, so the method for serial number extraction must be
 explicitly provided by any storage vendor in order to support
 dynamic tracking for their devices. This information is conveyed to the
 drivers via the 'sn_location' ODM attribute for each storage
 device.  If the disk or tape driver detects that the 'sn_location'
 ODM attribute is missing, an error log of type INFO will be generated and
 dynamic tracking will NOT be enabled.

 Note: The 'sn_location' attribute may be non-displayable, so
 running the 'lsattr' command on an hdisk, for example, may not show
 the attribute, but it may, indeed, be present in ODM.

- The FC device drivers will be able to track devices on a SAN fabric, where
 a SAN fabric is defined as a fabric as seen from a single host bus adapter,
 if the N_Port IDs on the fabric stabilize within about 15 seconds.
 If cables are not reseated or N_Port IDs continue to change after the
 initial 15 seconds, I/O failures could result.

- Devices will not be tracked across host bus adapters. Devices will only
 track if they remain visible from the same HBA that they were originally
 connected to.

 For example, if device A were moved from one location to another on fabric A
 attached to host bus adapter A (i.e., its N_Port on fabric A changes), the
 device would seamlessly be tracked without any user intervention and I/O
 to this device can continue.

 However, if a device A is visible from HBA A but not from HBA B,
 and device A is moved from the fabric attached to HBA A to the fabric
 attached to HBA B, device A will not be accessible on fabric A nor on
 fabric B.  User intervention would be required to make it available on
 fabric B by invoking cfgmgr. The AIX device instance on fabric A would no
 longer be usable, and a new device instance on fabric B would be created.
 This device would have to manually be added to volume groups, multipath
 device instances, etc.   In essence, this is the same as removing a device
 from fabric A and adding a new device to fabric B.

- No dynamic tracking will performed for FC dump devices while an AIX
 system dump is in progress.  In addition, dynamic tracking is not supported
 during boot or during cfgmgr invocations.  SAN changes should not be made
 while any of these operations are in progress.

- Once devices are tracked, ODM will potentially contain stale information as
 SCSI IDs in ODM will no longer reflect actual SCSI IDs on the SAN. ODM will
 remain in this state until cfgmgr is run manually or the system is
 rebooted, provided all drivers, including any third party FC SCSI target
 drivers, are dynamic-tracking capable. If cfgmgr is run manually, cfgmgr
 must be invoked on all affected fscsi devices, which can easily be
 accomplished by running cfgmgr without any options, or by invoking
 cfgmgr on each fscsi device individually.

 Note: Running cfgmgr at run time to recalibrate the SCSI IDs may not
 update the SCSI ID in ODM for a storage device if the storage device is
 currently opened, such as when volume groups are varied on.
 cfgmgr would need to be run on devices that are not opened or the system
 should be rebooted to recalibrate the SCSI IDs.  Note that stale SCSI IDs
 in ODM have no adverse affect on the FC drivers and recalibration of
 SCSI IDs in ODM is not necessary for the FC drivers to function properly.
 Any applications that communicate with the adapter driver directly via
 ioctl calls and use the SCSI ID values from ODM, however, need to be
 updated as indicated in the next bullet to avoid using potentially
 stale SCSI IDs.

- All applications and kernel extensions that communicate with the FC Adapter
 Driver, either via ioctl calls or directly to the FC driver's entry points,
 must support the version 1 ioctl and scsi_buf APIs of the FC Adapter
 Driver in order to work properly with FC dynamic tracking.  Non-compliant
 applications or kernel extensions may not function properly and/or fail
 after a dynamic tracking event.  If the FC adapter driver detects an
 application or kernel extension that is not adhering to the new version 1
 ioctl and/or scsi_buf API, an error log of type INFO will be generated and
 dynamic tracking may not be enabled for the device that this application/
 kernel extension may be trying to communicate with.

 ISVs developing kernel extensions and/or applications that communicate with
 the AIX Fibre Channel Driver stack should refer to the "Fibre Channel
 Protocol for SCSI and iSCSI Subsystem" article in "AIX 5L Version 5.2 Kernel
 Extensions and Device Support Programming Concepts" (pay special attention
 to the "Required FCP and iSCSI Adapter Device Driver ioctl Commands" and
 "Understanding the scsi_buf Structure sections") for changes necessary
 to support Dynamic Tracking.

- Even with dynamic tracking enabled users are strongly encouraged to make
 SAN changes, such as cable moves/swaps and establishing ISL links, during
 maintenance windows. Making SAN changes during full production runs is
 discouraged.  This is due to the fact that there is a short interval of
 time to perform any SAN changes.  Cables that are not reseated correctly,
 for example, could result in I/O failures. Performing these operations
 during a time of little/no traffic minimizes impact of I/O failures due to
 misplugging of cables, taking too long to recable, etc.

At the time of this release, the base AIX FC SCSI Disk and FC SCSI Tape
device drivers support dynamic tracking.

For status on dynamic tracking support for the FAStT product line,
refer to the following URLs:

IBM FAStT Storage Manager v7.10:

   http://www-3.ibm.com/pc/support/site.wss/MIGR-40711.html

IBM FAStT Storage Manager v8.21:

   http://www-3.ibm.com/pc/support/site.wss/MIGR-43839.html

IBM FAStT Storage Manager v8.3:

   http://www-3.ibm.com/pc/support/site.wss/MIGR-50177.html

After accepting the license agreement, proceed to the link for
Storage Manager for AIX.  Look for the current version of this
software and follow the link to the associated README.  Product
support and enhancement announcents will be made here.  These
announcements should contain information on what AIX APARs are
required to support dynamic tracking on FAStT.

In addition, the IBM ESS, EMC Symmetrix and HDS storage devices support
dynamic tracking provided that the vendor provides the ODM filesets with
the necessary 'sn_location' and 'node_name' attributes.  Contact the
storage vendor if you are not sure if your current level of ODM fileset
supports dynamic tracking.

If vendor-specific ODM entries are not being used for the storage device,
but the ESS, Symmetrix or HDS storage subsystem is configured with the
displayable message of "MPIO Other FC SCSI Disk", then dynamic tracking
is supported for these devices in this configuration.

The STK tape device using the standard AIX device driver also supports
dynamic tracking provided the STK fileset contains the necessary
'sn_location' and 'node_name' attributes.

Note: It is strongly recommended that SAN changes involving tape devices
be made with no active I/O.  Due to the serial nature of tape devices,
a single I/O failure can cause an application, such as a tape backup,
to fail.

Devices that configure with the displayable messages of "Other FC SCSI Disk"
or "Other FC SCSI Tape" will not support dynamic tracking.


==========================================
Fast Fail and Dynamic Tracking Interaction
==========================================

Although Fast Fail and Dynamic Tracking of FC Devices are technically separate
features, the enabling of one may change the interpretation of the other in
certain situations.  The following table shows the behavior exhibited
by the FC drivers with the various permutations of these settings.


dyntrk  fc_err_recov    FC Driver Behavior
======  ============    ==================
no      delayed_fail    This is the default setting.  This is legacy behavior
                       existing in previous versions of AIX.  The FC drivers
                       will not recover if the scsi_id of a device changes,
                       and I/Os will take longer to fail when a link loss
                       occurs between a remote storage port and switch.
                       This may be desirable in single-path situations
                       if dynamic tracking support is not a requirement.

no      fast_fail       If the driver receives a Registered State Change
                       Notification (RSCN) from the switch, this could
                       indicate a link loss between a remote storage port
                       and switch.  After an initial 15 second delay, the
                       FC drivers will query to see if the device is on
                       the fabric.  If not, I/Os will be flushed back by
                       the adapter.  Future retries or new I/Os will fail
                       immediately if the device is still not on the fabric.

                       If the FC drivers detects the device is on the fabric
                       but the scsi_id has changed, the FC device drivers
                       will not recover, i.e., I/Os will be failed with
                       PERM errors.

yes     delayed_fail    If the driver receives a Registered State Change
                       Notification (RSCN) from the switch, this could
                       indicate a link loss between a remote storage port
                       and switch.  After an initial 15 second delay, the
                       FC drivers will query to see if the device is on
                       the fabric.  If not, I/Os will be flushed back by
                       the adapter.  Future retries or new I/Os will fail
                       immediately if the device is still not on the fabric,
                       although the storage driver (disk, tape, FAStT)
                       drivers may inject a small delay (2-5 seconds) between
                       I/O retries.

                       If the FC drivers detects the device is on the fabric
                       but the scsi_id has changed, the FC device drivers
                       will reroute traffic to the new scsi_id.

yes     fast_fail       If the driver receives a Registered State Change
                       Notification (RSCN) from the switch, this could
                       indicate a link loss between a remote storage port
                       and switch.  After an initial 15 second delay, the
                       FC drivers will query to see if the device is on
                       the fabric.  If not, I/Os will be flushed back by
                       the adapter.  Future retries or new I/Os will fail
                       immediately if the device is still not on the fabric.
                       The storage driver (disk, tape, FAStT) will likely
                       not delay between retries.

                       If the FC drivers detects the device is on the fabric
                       but the scsi_id has changed, the FC device drivers
                       will reroute traffic to the new scsi_id.


Note that with dynamic tracking disabled, there is a marked difference
between the 'delayed_fail' and 'fast_fail' settings of the 'fc_err_recov'
attribute.  However, with dynamic tracking enabled, the setting of the
'fc_err_recov' attribute is less significant.  This is because there
is some overlap in the dynamic tracking and fast fail error recovery
policies.  As such, enabling dynamic tracking inherently enables some
of the fast fail logic.

The general error recovery procedure when a device is no longer reachable
on the fabric is the same for both 'fc_err_recov' settings with dynamic
tracking enabled, with the minor difference that the storage drivers may
choose to inject delays between I/O retries if 'fc_err_recov' is
set to 'delayed_fail'.  This will increase the I/O failure time by some
additional amount depending on the delay value and number of retries before
permanently failing the I/O.  With high I/O traffic, however, the difference
between 'delayed_fail' and 'fast_fail' may be more noticeable.

SAN administrators may want to experiment with these settings to find
the correct combination of settings for their environment.


=====================
Known Hardware Issues
=====================

--------
SWITCHES
--------
In general, if problems are encountered due to cable swaps or other operations
involving a switch, the switch firmware should always be updated to the
latest supported levels regardless of the type of switch being used.

IBM 2109 FC Switch
------------------
Some problems were experienced when using these features and performing
multiple cable swaps with the IBM FC 2109 F16 switch at GA firmware
level 3.0.  These problems are solved by updating the switch firmware to
the latest levels.  These features were tested using v3.0.2k firmware
for this switch.

Inrange Switch
--------------
If using an Inrange FC/9000 FC Director, the Inrange switch must
be at a minimum level of "FC 4.1.2.7" firmware in order to support
Dynamic Tracking and Fast Fail.

X11 libraries required for TPC server install on Linux

2011-03-27T18:10:00.002+02:00

TPC for Replications stopped with swing error.

java.lang.ExceptionInInitializerError
at javax.swing.plaf.metal.MetalTheme.(MetalTheme.java:61)
at javax.swing.plaf.metal.MetalLookAndFeel.getCurrentTheme(MetalLookAndFeel.java:1374)
at javax.swing.plaf.metal.MetalLookAndFeel.createDefaultTheme(MetalLookAndFeel.java:1306)
at javax.swing.plaf.metal.MetalLookAndFeel.getDefaults(MetalLookAndFeel.java:1313)
at javax.swing.UIManager.setLookAndFeel(UIManager.java:425)
at javax.swing.UIManager.setLookAndFeel(UIManager.java:455)
at com.installshield.wizard.swing.SwingWizardUI.switchToSystemLAF(SwingWizardUI.java:134)
at com.installshield.wizard.swing.SwingWizardUI.initialize(SwingWizardUI.java:487)
at com.installshield.wizard.StandardWizardListener.wizardInitializing(Unknown Source)
at com.installshield.wizard.Wizard$WizardListenerInitializer.run(Wizard.java:1862)
at java.lang.Thread.run(Thread.java:568)

Resolving the problem In addition to the standard X11 libraries, these libraries are required:
libXft 64bit & 32bit (TPC SE)
libXmu-1.0.2-5 (or latest version for your Linux distribution) 64bit & 32bit (TPC-R)
libXmu.i386 32bit (TPC-R)

H196488: DS3500/DS3950/DS5000 systems not working with Brocade on 8 Gbps host ports - IBM System Storage

2011-02-23T11:09:00.000+01:00

Source

RETAIN tip: H196488

Symptom

When attaching System Storage DS5000 series storage subsystems, System Storage DS3500 series storage subsystems, or System Storage DS3950 storage subsystems to Brocade 8 Gigabit (Gb) Fibre Channel switches running at 8 Gb host port speeds, the host connection will not establish at 8 gigabits per second (Gbps).

The following Brocade FC switches, running firmware 6.2.0e or above, are affected:

2498-B40	Brocade 5100
2498-B80	Brocade 5300
2499-192	Brocade DCX-4S
2499-384	Brocade DCX

Affected configurations

The system may be any of the following IBM servers:

DS5020 Disk Controller (1814-20A), any model
DS5100 Storage Controller, type 1818, any model
DS5300 Storage Controller, type 1818, any model
IBM System Storage DS3512, type 1746, any model
IBM System Storage DS3524, type 1746, any model
IBM System Storage DS3950 Express, type 1814, any model

This tip is not software specific.

This tip is not option specific.
The 6.2.0e firmware for the Brocade FC switches is affected.
The system has the symptom described above.

Workaround

The following Workaround should be used on the Brocade switch to establish 8 Gb host port connections.

To enable IDLE on ports, execute the following command on the switch console

portcfgfillword x 0

Where x is the port number.

Once ports are set to IDLE on Brocade switches, the connection with the storage subsystem will be established at 8 Gbps.

Additional information

Brocade switches that support 8 Gbps host port speeds have a connection issue with DS5000, DS3500, and DS3950 series storage subsystems. If one of the Brocade switches that supports 8 Gbps is shipped with 6.2.0e firmware and above, then the fillword setting is ARB instead of IDLE.

In order to work at 8 Gbps host port speeds, the following command should be executed on the affected switches

portcfgfillword x 0

Where x is the port number.

To check the status of the ports, use the following command:

portcfgshow

0- Fillword set to IDLE (This is how it should be set.)
1- Fillword set to ARB

Installshield error on x86_64 RedHat Linux

2011-02-16T18:20:00.003+01:00

TWS install fails with the following error message:

SETUP.sh -is:log /tmp/tws.log ->
The installer is unable to run in graphical mode. Try running the installer with the -console or -silent flag.

Log says:
Wizard, com.installshield.wizard.StandardWizardListener, dbg, java.lang.NoClassDefFoundError: java/awt/Frame
java.lang.NoClassDefFoundError: java/awt/Frame
at com.installshield.wizard.awt.AWTWizardUI.createFrame(Unknown Source)
at com.installshield.wizard.awt.AWTWizardUI.initialize(Unknown Source)
at com.installshield.wizard.StandardWizardListener.wizardInitializing(Unknown Source)
at com.installshield.wizard.Wizard$WizardListenerInitializer.run(Wizard.java:1871)
at java.lang.Thread.run(Thread.java:568)
(Feb 16, 2011 6:06:30 PM), Wizard, com.installshield.wizard.StandardWizardListener, err, could not initialize interface awt

Solution:
You have to install the i386 version of the necessary rpms.
- libXp-1.0.0-8.1.el5.i386.rpm
-compatlib .. etc

Install Leopard With An External Hard Drive

2011-02-02T20:05:00.002+01:00

I found a useful guide to install MAC OS X from external harddrive.

"If you have an external hard drive and made an image of leopard copy, but don’t have any dual layered disks lying around, you can always use an external hard drive to install Mac OS X 10.5 Leopard. This is incredibly easy, and works with both USB and Firewire hard drives:

1. Plug in your external hard drive
2. Open up Disk Utility
3. Click on the name of your external harddrive
4. Click on the “Restore” tab
5. In the “Source” field, select the image file (such as leopard.dmg) from wherever it is on your hard drive
6. In the “Destination” field, drag your external hard drive from the Disk Utility drive list on the left onto this field. Of course, if it’s only a partition on the external drive that you want to use, drag only the partition.
Note: anything on the partition will be erased and replaced with the installation files for Leopard. Therefore, it is best to make a partition on the external hard drive which has about 8 gigabytes. Use this partition as the destination so that everything else on the drive remains unchanged.
7. Click on restore. This may take awhile.
8. Once its done, open up System Preferences
9. Click on Startup Disk
10. Select the external hard drive (or partition in it) with the Leopard Install
11. Click Restart. The leopard installation will begin from the external hard drive. This installation is identical to installing leopard with a DVD."

Original link

How To Enable Dvd Drive Sharing on a Non-Air Macbook

2011-02-02T18:48:00.000+01:00

defaults write com.apple.NetworkBrowser EnableODiskBrowsing -bool true
defaults write com.apple.NetworkBrowser ODSSupported -bool true

Qlogic SANBox password reset

2011-02-02T10:34:00.003+01:00

How do you reset the SANbox switch password file back to factory default?

Question: How do you reset the SANbox switch password file back to factory default?

Response: Put switch into Maintenance Mode (disruptive) by pressing the maintenance mode switch/button for 4 seconds or power on and press the maintenance mode switch until the heartbeat LED is on solid (the maintenance mode switch is in the hole located under the Ethernet connection). Use Telnet and log in as prom/prom (username/password). Select menu option#3 (Reset Password File) to defaults (admin/password = username/password). Select menu option#7 (Reset Switch) to reset switch once selecting exiting from Maintenance Mode menu, then menu item#0 (Exit).

Sanbox2 login: prom

Password: prom

0) Exit
1) Image Unpack
2) Reset Network Config
3) Reset Password File
4) Copy Log Files
5) Remove Switch Config
6) Remake Filesystem
7) Reset Switch

Option: 3

OK, password file has been reset to factory defaults.

0) Exit
1) Image Unpack
2) Reset Network Config
3) Reset Password File
4) Copy Log Files
5) Remove Switch Config
6) Remake Filesystem
7) Reset Switch

Option: 7

Are you sure you want to reboot the switch? (y/n) y

0) Exit
1) Image Unpack
2) Reset Network Config
3) Reset Password File
4) Copy Log Files
5) Remove Switch Config
6) Remake Filesystem
7) Reset Switch

Option: 0

Note: After resetting, the SANbox switch will come up in Normal mode and be ready to use with a default password file. When the switch is in Maintenance Mode, the IPaddress = 10.0.0.1. Once the switch is reset and boots normally, the IPaddress will return back to the configured setting.

Linux Storage Reconfiguration

2011-01-31T17:42:00.000+01:00

Because most RAID arrays allow LUNs to be created, removed and resized dynamically, it is important that the Linux kernel to react to these actions, preferably without a reboot. The Linux 2.6 kernel permits this by way of the /sys filesystem, which replaced the earlier /proc interfaces. For example, the following command causes the kernel to forget about the LUN on busid 3, channel 0, target 7 and LUN 1:

echo "1" > \
/sys/class/scsi_host/host3/device/3:0:7:1/delete

The busid of 3 is redundant with the 3 in host3. This format also is used, however, in contexts where the busid is required, such as in /sys/bus/scsi/devices.

To later restore only that particular LUN, execute:

echo "0 7 1" > /sys/class/scsi_host/host3/scan

To resize this same LUN, use:

echo 1 > /sys/bus/scsi/devices/3:0:7:1/rescan

To scan all channels, targets and LUNs, try:

echo "- - -" > /sys/class/scsi_host/host3/scan

BOMC (Bootable Media Creator) error

2011-01-12T21:23:00.003+01:00

I got this error after I tried to create bootable iso with IBM ToolsCenter software called BOMC:
"Error(s) occurs while creating the bootable media! Error message: Media creation error: The mkisofs utility failed to create ISO file"

This error occurs when cygwin1.dll already loaded by another program. I use LinuxTSC that use this dll. After unloaded the xwin.exe the problem disappeared.

Determine the process running on a particular port

2010-12-21T08:49:00.000+01:00

IBM - Determine the process running on a particular port: "Determine the process running on a particular port
Technote (FAQ)

Question
How to find out which application is using what port?

Answer
For AIX:
1. netstat -Aan | grep
- This shows if the specified is being used. The hex number in the first column is the address of protocol control block (PCB)

2. rmsock tcpcb
- This shows the process who is holding the socket. Note that this command must be run as root.

An AIX example:
# netstat -Aan | grep 9515
f100060003743b98 tcp4 0 0 *.9515 *.* LISTEN

# rmsock f100060003743b98 tcpcb
The socket 0x3743808 is being held by proccess 438488 (java).

For Windows:
Let’s say that we are looking for port 9549 — Data server.

Here is the command.

C:\> netstat -aon | findstr 9549

-a means list all active connections and their ports.
-o means include their process IDs.
-n means display the port numbers numerically.

The pipe symbol ( | ) means, that instead of the result of netstat being displayed on the screen, feed it’s result to the findstr process — we are looking specifically for the line which has port 9549.

You might see something like this
TCP 0.0.0.0:9549 0.0.0.0:0 LISTENING 3444

Now we know that process 3444 is using port 9549 (that last column right there, is the process ID).
You could now enter 'tasklist'.

C:\> tasklist | findstr 3444
java.exe 3444 Console 0 22,920 K

tasklist is another Windows command line utility which shows you a list of all active processes.

In this case, the process is the java process link to the data server process.
If you kill process 3444, you kill the data server service.

- Sent using Google Toolbar"

Brocade Password Recovery

2010-12-15T14:40:00.000+01:00

Brocade Communities : Brocade Password Recovery Notes Publication Number: 53-1000114-01: "Fabric OS

Password Recovery Notes

Supporting Fabric OS v2.6.x, v3.1.x, v4.x, v5.x

2 of 12 Fabric OS Password Recovery Notes

Publication Number: 53-1000114-01

Copyright © 2006, Brocade Communications Systems, Incorporated.

ALL RIGHTS RESERVED. Publication Number: 53-1000114-01

If you have access to the root account you can reset the passwords for all other accounts on the system including: the

factory, admin, and user accounts. The root account can reset the root, factory, and admin accounts; admin can reset the

user login. See “Password Recovery Using Root Account” on page 3.

If you do not have access to the root account, you can use the Boot PROM password to reset the system passwords to

default values. This option is only available on Fabric OS v4.1 or greater, and you must have the Boot PROM password

(unless no Boot PROM password was set). See “Password Recovery Using the Boot PROM” on page 4.

If you do not have either the root or Boot PROM password, or your system is loaded with a version older than Fabric OS

v4.1, contact your switch service provider for a Boot PROM recovery string to regain access to the switch. See “Obtaining

the Boot PROM Recovery Password” on page 7.

Password Recovery Using Root Account

If you have access to the root account, you can reset the password for any admin, factory, and user accounts without

knowing the account’s current password.

To reset any account password from the root account:

1. Open a CLI session (serial or telnet for an unsecured system and sectelnet for a secure system) to the switch.

2. Log in as root.

3. At the prompt, enter the passwd command, followed by the account name as shown below:

switch:root> passwd account

Note

When connected through a serial cable to the console, always save the output using the capture functionality

under windows (or script functionality for UNIX or Linux).

Note

In a fabric with Secure Fabric OS enabled, you must log in to the primary FCS to perform these tasks.

4 of 12 Fabric OS Password Recovery Notes

Publication Number: 53-1000114-01

4. Follow the prompts to reset the password for the selected account. For example:

Password Recovery Using the Boot PROM

If you know the Boot PROM password or none was set on your system, use this procedure to reset the passwords to

default values on the switch or director. The current Fabric OS level of the switch or director must be v4.1 or greater.

To reset the root password to default using the Boot PROM password:

1. Connect to the serial console port of the switch (SilkWorm 200E, 3250, 3850, 3900, 4100, 4900 or 7500 switch) or

the standby CP of a director (SilkWorm 12000, 24000, or 48000). Use the hashow command to see which CP is

active and which is standby.

2. Enter the reboot command.

3. Press ESC at the message “Press escape within 4 seconds...” The Boot PROM menu is displayed with the following

options:

- 1) Start system

Used to reboot the system.

- 2) Recover password.

Used to generate a character string for your support provider to recover the Boot PROM password.

- 3) Enter command shell.

Used to enter the command shell, to reset all passwords on the system.

switch:root> passwd admin

Changing password for admin

Enter new password: xxxxxxx

Re-type new password: xxxxxxx

passwd: all authentication tokens updated successfully

Saving password to stable storage.

Password saved to stable storage successfully.

Note

This procedure is disruptive to traffic on the SilkWorm 200E, 3250, 3850, 3900, 4100, 4900 and 7500 switches,

because it requires you to reboot the switch; traffic resumes after the switch is rebooted. On a SilkWorm 12000,

24000, or 48000 director, you can reset the passwords without disruption by performing this procedure on the

standby CP.

Note

If you are attempting to recover passwords for Fabric OS v4.4.0, you must review “Password Recovery for

Fabric OS v4.4.0” on page 8 prior to beginning this procedure.

Fabric OS Password Recovery Notes 5 of 12

Publication Number: 53-1000114-01

4. Type 3 at the prompt to open the command shell.

5. Type the Boot PROM password, if prompted, then press Enter. The Boot PROM has a password only if one was

defined earlier.

6. Run the printenv command, then save the output to a file. You will need to refer to this output later in the procedure.

7. Locate the first memory address; it is the string after OSLoader= in the printenv output.

8. Run the boot command with the first memory address and the –s option. For example:

9. For a SilkWorm 200E, 3250, 3850, 3900, 4100, 4900, or 7500 switch, perform the following steps:

a. Enter the mount command with the following parameters:

> mount -o remount,rw,noatime /

This will remount the root partition as read/write.

b. Enter the mount command with the following parameters where hda is followed by the second partition value

(such as 1 or 2) from OSRootPartition in the printenv output:

> mount /dev/hda2 /mnt

The system is coming up, please wait...

Checking system RAM - press any key to stop test

01a00000

System RAM check terminated by keyboard

System RAM check complete

Press escape within 4 seconds to enter boot interface.

1) Start system.

2) Recover password.

3) Enter command shell.

Option? 3

1) Start system.

2) Recover password.

3) Enter command shell.

Option? 3

Boot PROM password has not been set.

> printenv

AutoLoad=yes

ENET_MAC=0060696019B4

InitTest=MEM()

LoadIdentifiers=Fabric Operating System;Fabric Operating System

OSBooted=MEM()0xF0000000

OSLoadOptions=quiet;quiet

OSLoader=MEM()0xF0000000;MEM()0xF0800000

OSRootPartition=hda1;hda2

SkipWatchdog=yes

>

> boot MEM()0xF0000000 -s

Booting 'Manually selected OS' image.

Entry point at 0x00800000 ...

6 of 12 Fabric OS Password Recovery Notes

Publication Number: 53-1000114-01

c. Enter the passwddefault command, as follows:

> /sbin/passwddefault

This resets all account passwords to the default values. If there were additional user accounts created, they are

deleted and only the default accounts and passwords remain.

d. Reboot the switch using the reboot –f command.

> reboot -f

Traffic flow resumes when the switch completes rebooting. If you do not use the –f you will have to manually

reboot the switch.

e. Log in as root to the switch by serial or telnet and set new passwords for all accounts.

The process is now complete.

10. For a SilkWorm 12000, 24000, or 48000 director, perform the following steps

a. From the serial connection to the standby CP, determine the hostname of the CPs. This can be done using the

# /bin/cat /etc/hosts command:

b. From the serial connection to the standby CP, set the appropriate hostname to the CP. Use the hostname displayed

in the previous step. In the above example mycp0 is the standby CP.

hostname

c. Start networking on the standby CP:

> /etc/init.d/network start

d. Perform one of the following according to which slot the CP card is in:

- If the standby CP card is in slot 5 (CP0), enter:

> rsh 10.0.0.6 /sbin/passwddefault

- If the standby CP card is in slot 6 (CP1), enter:

> rsh 10.0.0.5 /sbin/passwddefault

e. Reboot the standby CP using the reboot –f command.

> reboot –f

If you do not use the –f option you will have to manually reset the CP by moving the slider switch to the off and

then on position.

# /bin/cat /etc/hosts

127.0.0.1 localhost

10.64.148.23 swd77 #sw0 255.255.240.0

10.64.148.24 swd76 #sw1 255.255.240.0

10.64.148.25 mycp0 #cp0 255.255.240.0 < CP0 SLOT 5

10.64.148.26 cp1 #cp1 255.255.240.0 < CP1 SLOT 6

0.0.0.0 fc0 #fc0 0.0.0.0

0.0.0.0 fc1 #fc1 0.0.0.0

10.0.0.5 cp_0_inteth #cp_0_internaleth

10.0.0.6 cp_1_inteth #cp_1_internaleth

Note

The hostname for CP0 or CP1 are user definable, and may be different for each installation.

Fabric OS Password Recovery Notes 7 of 12

Publication Number: 53-1000114-01

f. Log in to the active CP as admin from a telnet or serial connection, and enter Ctrl + C to bypass the request to

modify passwords.

g. Log in to either logical switch by serial or telnet as admin and set new passwords for all accounts. The password

recovery procedure is now complete.

Obtaining the Boot PROM Recovery Password

This section explains how to gather the information you need to send to your switch support provider in order to get a

Boot PROM recovery password. Once you have received the Boot PROM recovery password, and gained access to the

Boot PROM, you reset the passwords using “Password Recovery Using the Boot PROM” on page 4.

To obtain the Boot PROM recovery password from your switch support provider:

1. Connect to the serial port interface of the switch or standby CP.

2. Reboot the switch or standby CP.

3. Press ESC within four seconds after the message “Press escape within 4 seconds...”.

4. Enter 2 at the prompt. A character string is displayed.

5. Send the character string to your switch support provider to obtain a Boot PROM recovery password.

6. Perform the appropriate steps to set the Boot PROM password if it was not set, as prompted:

Recovery password is NOT set. Please set it now.

7. Enter the Recovery Password that is generated from your support provider when prompted.

8. When prompted with “New password:”, enter the new Boot PROM password and re-enter when prompted.

9. Record the new password for future reference.

10. Enter the saveenv command.

1) Start system.

2) Recover password.

3) Enter command shell.

Option? 2

Send the following string to Customer Support for password recovery:

/uasLR1raCqT3FToqy0ZjA==

Enter the supplied recovery password.

Recovery Password: YnfG9DDrlFMDVkNM0RkPtg== < Supplied by your support provider

Re-enter Recovery Password: YnfG9DDrlFMDVkNM0RkPtg==

New password: xxx

Re-enter new password: xxx

> saveenv

8 of 12 Fabric OS Password Recovery Notes

Publication Number: 53-1000114-01

Password Recovery for Fabric OS v4.4.0

In Fabric OS v4.4.0, you must take additional steps prior to and after performing the “Password Recovery Using the Boot

PROM” on page 4. Otherwise, the switch is left in single-user mode.

Password Recovery Steps Before Root Command

1. Connect to the serial port of the switch or the standby CP.

2. Reboot the switch and press ESC within 4 seconds after the message 'Press escape within 4 seconds...'.

3. Enter the Boot PROM password.

4. Enter 3 at the prompt to enter the command shell.

5. Enter the printenv command and save the output. For example:

6. From the output of the printenv, record the value for OSLoader.

OSLoader ___________________________________________

Password Recovery Steps After Root Command

After you have recovered the passwords:

1. Connect to the serial port interface of the switch or standby CP.

2. Reboot the switch and press ESC within 4 seconds after the message 'Press escape within 4 seconds...' displays.

'Enter Boot PROM interface:'

3. Enter the Boot PROM password.

4. Enter 3 at the prompt to enter the command shell.

The system is coming up, please wait...

Checking system RAM - press any key to stop test

Checking memory address: 01300000

System RAM check terminated by keyboard

System RAM check complete

Press escape within 4 seconds to enter boot interface.

1) Start system.

2) Recover password.

3) Enter command shell.

Option? 3

Password:

> printenv

AutoLoad=yes

ENET_MAC=006069602BD6

InitTest=MEM()

LoadIdentifiers=Fabric Operating System;Fabric Operating System

OSLoader=MEM()0xF0000000;MEM()0xF0800000

OSLoadOptions=quiet;quiet

OSRootPartition=hda1;hda2

SkipWatchdog=yes

Fabric OS Password Recovery Notes 9 of 12

Publication Number: 53-1000114-01

5. Enter the following command strings, one at a time, to reset the passwords:

unsetenv OSBooted

setenv LoadIdentifiers=Fabric Operating System;Fabric Operating System

setenv OSLoadOptions=quiet;quiet

setenv OSLoader=MEM()0xF0000000;MEM()0xF0800000

saveenv

printenv

reset

Password Recovery on VXWorks-Based Switches

This procedure requires Password Recovery firmware, available from your switch support provider. The Password

Recovery firmware is effective only for the first time it is launched. You cannot use the Password Recovery firmware to

perform any other switch functions.

These procedures require switch downtime. Brocade recommends removing the switch from the fabric and rejoining it

after the recovery process is complete.

In order to complete the steps in this section you need the following:

• Password Recovery firmware: Send the switch WWN to your switch support provider with a request for the Password

Recovery firmware. This firmware can be launched once, and it recovers the password for the specific switch only.

• Ethernet connection between host and switch. It can be either a network connection from a host to the switch or a

direct connection with an Ethernet crossover cable.

• Serial connection to the switch

Reset Passwords for Fabric OS v2.6.1+, and v3.1+

To reset the passwords on a Fabric OS v2.6.x and greater, or v3.1.x and greater switch using the Password Recovery

firmware:

1. Copy the Password Recovery firmware to a secure location that is accessible to the switch; that is, an FTP server

accessible to the switch. You must use either FTP or RSHD to copy the firmware. If FTP is used, the password cannot

be blank.

2. Connect to the console port.

3. Power the switch off and back on.

4. Set the boot parameters on your switch to perform a netboot:

a. At the “[VxWorks Boot]” prompt for the switch, enter c.

Note

The value of the OSLoader= string should be set to the exact value from step 6 on page 8.

10 of 12 Fabric OS Password Recovery Notes

Publication Number: 53-1000114-01

b. Type the requested information at the prompts. To accept the default value for a parameter, press Enter.

The parameters are defined as follows.

host name Name of machine on which Password Recovery firmware is located

file name Full pathname where Password Recovery firmware is located

inet on ethernet Switch IP address

host inet Host IP address

gateway inet Gateway address

user Login name of user account on host machine

Press any key to stop auto-boot...

[VxWorks Boot]: c

'.' = clear field; '-' = go to previous field; ^D = quit

boot device : fei

processor number : 0

host name : host

file name : /usr/switch/firmware resetPasswd303f6f

inet on ethernet (e) : 192.168.132.217:fffff000

inet on backplane (b):

host inet (h) : 192.168.132.133

gateway inet (g) : 192.168.132.133

user (u) : user

ftp password (pw) (blank = use rsh):

flags (f) : 0x0

target name (tn) : sw2800

startup script (s) :

other (o) :

Fabric OS Password Recovery Notes 11 of 12

Publication Number: 53-1000114-01

5. Type @ at the [VxWorks Boot] prompt to begin booting the Password Recovery version of the firmware from the

network.

The user, admin, factory, and root passwords are reset to the default values.

6. Power the switch off and back on.

7. Press any key when you see the message “Press any key to stop autoboot...” This provides access to the boot prompt.

8. Set the switch to boot from the flash again:

a. At the [VxWorks Boot] prompt, type c to begin resetting the boot parameters to the default settings.

b. Remove the values that you added by typing a period (.) after each parameter, then pressing Enter. The boot

parameters are returned to the default settings.

9. Power the switch off and back on to reload the original firmware from flash. The switch resumes normal operation.

10. Log in to the switch by telnet or serial as root, and set new passwords for all accounts.

[VxWorks Boot]: @

boot device : fei

processor number : 0

host name : host

file name : resetPasswd303f6f

inet on ethernet (e) : 192.168.132.217:fffff000

host inet (h) : 192.168.132.133

gateway inet (g) : 192.168.132.133

user (u) : user

flags (f) : 0x0

target name (tn) : sw2800

Attaching network interface fei0... done.

Attaching network interface lo0... done.

host is alive <-------------------------CONNECTION TO HOST PROVIDING FIRMWARE IMAGE

Loading... 4407608 + 329564 + 1153796

Starting at 0x10400000...

Attaching network interface fei0... done.

Attached TCP/IP interface to fei unit 0

Attaching network interface lo0... done.

telnetInit: telnetd initialized.

NFS client support not included.

efwHookAdd: Added Ethernet Hook

Adding 9407 symbols for standalone.

Model: 4

flash time 0, creation time 1048818644

Committing configuration...done.

setting passwd to defaults <-------FIRMWARE IMAGE RESETS PASSWORD TO BROCADE

DEFAULTS

Time Bomb has been set

RESTRICTED ONE TIME USE

Passwords have been reset. Please power cycle the switch.

12 of 12 Fabric OS Password Recovery Notes

Publication Number: 53-1000114-01

- Sent using Google Toolbar"

Sample script to check wheter TPC performance collection is working well

2010-12-02T14:09:00.005+01:00

checktime.sh
"#!/bin/sh
device=$1
type=$2
option=$3

maxDiff=3600
tpccli=/home482/TPC/cli/tpccli
usage="Usage @0 [device] [fabric|subsys] -l"

getDiff () {
now=`date +%s`
c_time=`date --date "$s_time" +%s`
x_diff=$(($now - $c_time))
if [ $x_diff -lt $maxDiff ]; then
str_diff="OK"
RC=0
else
str_diff="Difference is greater than ${maxDiff} sec!! Diff: ${x_diff} sec"
RC=4
fi
}

if [ $# -lt 2 ]; then
echo $usage
exit 1
fi

case $type in
subsys)
TT=`$tpccli lstime -subsys ${device} -level sample -ctype subsystem| tail -n 1 | sed -e "s/:/ /" -e "s/\./-/g" | awk '{print $1 " " $2 " " $3}'`
;;
fabric)
TT=`$tpccli lstime -fabric ${device} -level sample -ctype switch | tail -n 1 | sed -e "s/:/ /" -e "s/\./-/g" | awk '{print $1 " " $2 " " $3}'`
;;
*)
echo $usage
exit 1
esac

if [ "${TT}" != "" ]; then
#echo ""
#echo "***************************"
echo "Current maximum difference is ${maxDiff} sec"
echo $TT | while read d t dur
do
s_time=`date --date "$d $t $dur sec"`
getDiff
printf "$device=>${str_diff}\n"
if [ "${option}" == "-l" ]; then
printf "Calculated Time: `date --date "$s_time" "+%F %H:%M"`\nCurrent time: `date "+%F %H:%M"`\nStarted at $d $t Duration:${dur} sec\n"
fi
done
else
echo ""
#echo "***************************"
echo "$device has no performance data!!"
RC=5
fi

exit $RC"

Calling script:
#!/bin/ksh

_tmp=.checktime.res

echo "Checking performance monitors ..."
cat $TPCCLIHOME/devices | while read device
do
sh gettime ${device} > $_tmp
if [ $? -gt 3 ]; then
cat $_tmp
else
printf " `echo ${device} | cut -d " " -f 1` "
fi
done

devices file format:
#device [subsys|fabric]
ds8k subsys
sanswitch1 fabric

Disk I/O and the Network | AIX | IBM Systems Magazine

2010-10-22T09:07:00.000+02:00

Disk I/O and the Network | AIX | IBM Systems Magazine: "Disk I/O

Many of the most common performance problems are related to I/O issues. In particular, data layout can affect performance more than any I/O tunable the administrator can set. Since changing these later is extremely painful, it’s important to plan in advance to avoid these problems.

The trend in the industry right now is to provide fewer, larger hdisks to the server. For example, the server may be given one 500 GB hdisk that’s spread across several disks in the disk subsystem, rather than being given 10, 50 GB or five 100 GB hdisks. However, I/O performance depends on bandwidth, not size. While that data may be spread across multiple disks in the back end, this doesn’t help with queuing in the front end. At the server, the hdisk driver has an in-process and a wait queue. Once an I/O is built in the JFS2 buffer, it gets queued to the LUN (hdisk). Queue_depth for an hdisk (LUN) represents the number of in-flight I/Os that can be outstanding for an hdisk at any given time.

The in-process queue for the hdisk can contain up to queue-depth I/Os and the hdisk driver submits the I/Os to the adapter driver. Why is this important? If your data’s striped by LVM across five hdisks then you can have more I/Os in process at the same time. With one big hdisk, you’ll be queuing. Multipath I/O drivers such as subsystem device driver (SDD) won’t submit more than queue_depth I/Os to an hdisk, which can affect performance. You either need to increase queue_depth or disable that limit. In SDD, use the 'datapath qdepth disable' command.

Some vendors do a nice job of setting the queue_depth, but if you’re using large logical-unit numbers from multiple disks in the back end, then you’ll want to grow this. You can use the iostat -D or the sar -d commands to figure this out. Interactive nmon also has a -D option, which lets you monitor sqfull as well. If you’re using sddpcm, then you can use 'pcmpath query devstats' to monitor sqfull and 'pcmpath query adaptstats' to monitor adapter queuing.

In particular, look at the avgsqsz, avgwqsz and sqfull fields to determine if you need to increase queue_depth. Don’t increase queue_depth beyond the disk manufacturer’s recommendations. lsattr -El hdisk? shows the current queue_depth setting. queue_depth is a disruptive change and requires a reboot.

For Fibre Channel, the adapter also has an in-process queue, which can hold up to num_cmd_elems of I/Os. The adapter submits the I/Os to the disk subsystem and it uses direct memory access (DMA) to perform the I/O. You may need to consider changing two settings on the adapter. By default num_cmd_elems is set to 200 and max_xfer_size is set to 0x100000. The latter equates to a DMA size of 16 MB. For a heavy I/O load, I increase the DMA to 0x200000 (128 MB) and I’ve set num_cmd_elems as high as 2,048, although I normally start at 1,024. This has to be done before the hdisks, etc., are assigned or you’ll have to rmdev them all to set these values. lsattr -El fcs? shows the current settings. Before changing these, check with your disk vendor. The fcstat command can be used to monitor these. Look for entries like:

FC SCSI Adapter Driver Information
No DMA Resource Count: 0
No Adapter Elements Count: 2567
No Command Resource Count: 34114051

In the above, it’s clear that num_cmd_elems isn’t high enough and that the DMA area also needs increasing. This is a disruptive change that requires a reboot.

When using VIO servers, max_xfer_size and num_cmd_elems should be set on the VIO servers and, if using N_Port ID Virtualization (NPIV), they’ll also need to be set on the NPIV client LPARs. Don’t set the values on the NPIV client LPAR higher than the VIO servers; I tried this and my LPAR wouldn’t boot, which was probably lucky, as I am sure there would have been overruns."

Linux FC tape devices persistent binding

2010-10-13T14:24:00.003+02:00

udevinfo -a -p $(udevinfo -q path -n /dev/IBMtape0)
looking at device '/class/lin_tape/IBMtape0':
KERNEL=="IBMtape0"
SUBSYSTEM=="lin_tape"
SYSFS{sys_encryption_write}=="2"
SYSFS{sys_encryption_proxy}=="1"
SYSFS{dev}=="253:0"
looking at device
'/devices/pci0000:00/0000:00:03.0/0000:15:00.1/host6/rport-6:0-0/target6:0:0/6:0:0
:0':
ID=="6:0:0:0"
BUS=="scsi"
DRIVER=="lin_tape"
SYSFS{primary_path}=="NA"
SYSFS{ww_port_name}=="0x500507630F810916"
SYSFS{ww_node_name}=="0x500507630F010916"
SYSFS{serial_num}=="000001327093"
SYSFS{rev}=="268F"
SYSFS{model}=="03592E06 "
SYSFS{vendor}=="IBM

defining rules
BUS=="scsi", KERNEL=="IBMtape[0-9]", SYSFS{serial_num}=="000001327093",
SYSFS{ww_port_name}=="0x500507630F410916", SYMLINK+="tape0"
BUS=="scsi", KERNEL=="IBMtape[0-9]n", SYSFS{serial_num}=="000001327093",
SYSFS{ww_port_name}=="0x500507630F410916", SYMLINK+="tape0n"

How to find brocade switch model type based on switchshow output.

2010-10-05T14:58:00.006+02:00

The following table lists Brocade switch type codes as they appear in Command-Line Interface (CLI) command output and their corresponding Brocade model names. The switch type is a field (switchType) displayed in the output of the switchShow command. When you are gathering information for your switch support provider, you may be asked to provide the switch name (model). If you do not know the model, you can use this table to map the switch type to the model.
NOTE: Switch type output displays these values with 1.x for the Brocade 1000 family, 2.x for Brocade 2800, and so on. The "x" value refers to motherboard revision level.

Switch Type Switch Name
1 Brocade 1000 Switches
2,6 Brocade 2800 Switch
3 Brocade 2100, 2400 Switches
4 Brocade 20x0, 2010, 2040, 2050 Switches
5 Brocade 22x0, 2210,2240, 2250 Switches
7 Brocade 2000 Switch
9 Brocade 3800 Switch
10 Brocade 12000 Director
12 Brocade 3900 Switch
16 Brocade 3200 Switch
17 Brocade 3800VL
18 Brocade 3000 Switch
21 Brocade 24000 Director
22 Brocade 3016 embedded Blade Switch
23 8Gbit 10-port embedded fabric switch
26 Brocade 3850 Switch
27 Brocade 3250 Switch
29 Brocade 4012 EmbeddedBlade Switch
32 Brocade 4100 Switch
33 Brocade 3014 Switch
34 Brocade 200E Switch
36 Brocade FR4-18i DirectorBlade
37 Brocade 4020 Embedded Blade Switch
38 Brocade 7420 SAN Router
40 Fibre Channel Routing (FCR) Front Domain
41 Fibre Channel Routing (FCR) Xlate Domain
42 Brocade 48000 Director
43 Brocade 4024 Embedded Blade Switch
44 Brocade 4900 Switch
45 Brocade 4016 Embedded Blade Switch
46 Brocade 7500 Switch
47 Brocade FC4-16IP Director Blade
50 Brocade 4GB FC Port Blade
51 Brocade 4018 Embedded Blade Switch
55 Brocade FA4-18i Extension Director Blade
55,2 Brocade 7600 Switch
58 Brocade 5000 Switch
62 Brocade DCX Backbone
63 Brocade 8Gb Backbone Core Fabric Switch
64 Brocade 5300 Switch
66 Brocade 5100 Switch
67 Brocade Encryption Switch
68 Brocade 8Gb 16 FC 2 GigE ports Director Encryption Blade
69 Brocade 5410 Blade
70 Brocade 8GB 10 Port Embedded Fabric Switch
71 Brocade 300 Switch
72 Brocade 5480 Embedded Blade Switch
75 Brocade M5424 Embedded Blade Switch
76,6 Brocade 8000 FCoE Switch
77,3 Brocade DCX-4S
82 Brocade 8Gb 24-port Embedded Blade Switch
83 Brocade 16-FC port,
6-GE port, auto sensing 1, 2, 4 or 8Gbit Switch
86 Brocade 8Gbit 26-port embedded Switch
88 Brocade 10Gb 24 GigE ports DCE Blade
89 Brocade 8Gb 12 FC, 1Gb 10 GigE FCIP Blade, 10Gb 2 GigE ports FCR

source brocade

GPFS portability layer compile fals Part II.

2010-08-04T11:56:00.002+02:00

I tried to compile the portability layer on Centos (RedHat) but the "make Autoconfig" shows the following message:
"Cannot find a valid kernel include dir"

The full message is:
[root@gpfs02 src]# make Autoconfig
cd /usr/lpp/mmfs/src/config; ./configure --genenvonly; /usr/bin/cpp -P def.mk.proto > ./def.mk; exit $? || exit 1
Cannot find a valid kernel include dir
def.mk.proto:12:19: error: env.mcr: No such file or directory
make: *** [Autoconfig] Error 1
[root@gpfs02 src]#

This error message means that the it cannot read the version.h file under the defined module library dierctory. This file is located in the kernel build directory. After I installed the kernel-devel-2.6.18-164.el5.x86_64.rpm package the build was successful.

Centos RHEL WHATPROVIDES

2010-08-04T10:49:00.001+02:00

I found a usefull option to yum called 'whatprovides'

# yum whatprovides libstdc++.so.5
Loaded plugins: rhnplugin, security
...
compat-libstdc++-33-3.2.3-61.i386 : Compatibility standard C++ libraries
Matched from:
Other : Provides-match: libstdc++.so.5

DB2 instance wont start at system startup.

2010-07-14T15:00:00.002+02:00

The db2 instance wont start at boot but the AUTOSTART=YES is set.
Problem:
Missing fmc section from inittab.
Resolution:
db2fmcu -u -p /opt/IBM/db2/V9.5/bin/db2fmcd
This command set the appropriate settings in inittab:
#lsitab "fmc"
#fmc:2:respawn:/opt/IBM/db2/V9.5/bin/db2fmcd #DB2 Fault Monitor Coordinator

Detailed settings:

"Configuring DB2 fault monitor using db2fmc and system commands

You can configure the DB2® fault monitor using the DB2 Fault Monitor Controller Utility (FMCU) command db2fmcu or system commands.

Here are some examples of using db2fmcu and system commands to configure the fault monitor:

Example 1: Prevent FMC from being launched

You can prevent the FMC from being launched by using the DB2 Fault Monitor Controller Utility (FMCU). The FMCU must be run as root because it accesses the system's inittab file. To block the FMC from being run, type the following command as root:

db2fmcu -d

Note: If you apply a DB2 Data Server fix pack this will be reset so that the inittab will again be configured to include the FMC. To prevent the FMC from being launched after you have applied a fix pack, you must reissue the above command.
Example 2: Include FMC to be launched

To reverse the db2fmcu -d command and reconfigure the inittab to include the FMC, type the following command:

db2fmcu -u -p

where is the complete path to the db2fmcd object, for example /opt/IBM/db2/bin/db2fmcd.
Example 3: automatically start the DB2 database manager instance

You can also enable FMC to automatically start the instance when the system is first booted. To enable this feature for instance DB2INST1, type the following command:

db2iauto -on db2inst1

Example 4: disable automatically starting the instance

To turn off the autostart behaviour, type the following command:

db2iauto -off db2inst1

Example 5: prevent fault monitor processes from being launched

You can also prevent fault monitor processes from being launched for a specific instances on the system by changing a field in the global registry record for the instance. To change the global registry field to disable fault monitors for instance DB2INST1, type the following command as root:

db2greg -updinstrec instancename=db2inst1!startatboot=0

To reverse this command and re-enable fault monitors for instance DB2INST1, type the following command as root:

db2greg -updinstrec instancename=db2inst1!startatboot=1"

JFS2 filesystem is clean but won't be mounted

2010-07-14T12:16:00.004+02:00

I faced with this problem with AIX 5.2.
The customer couldn't kill the process that used a filesystem. After a restart the they could not mount this fs. The error message was like this:
"...failure replaying log for ..."
" ..media is not formatted or format is not correct"

This is a known problem documented in the following APAR:
"IY60872: MOUNT OF JFS2 FILESYSTEM FAILS
fsck runs and claims a clean JFS2 filesystem. When the mount
of the file-system is attempted it fails with an error message
about "Unformatted or incompatible media"

Problem summary
fsck runs and claims a clean JFS2 filesystem. When the mount
of the filesystem is attempted it fails with an error message
about "Unformatted or incompatible media"
Problem conclusion
When stale log pages or I/O errors are detected in
logredo make sure log is reformatted in all cases."

Another usefull IBM site here

Problem resolultion:
The file-system log volume was used by only this filesystem therefore we could use the "logform" command to reformat the log.

After logform and another fsck the mount was succesful.

Numeric display diagnostic codes DS 4000

2010-07-05T14:16:00.001+02:00

Value Controller State Description
L0 Suspended Mismatched controller board ID
L1 Suspended Missing interconnect canister
L2 Suspended Persistent memory errors
L3 Suspended Persistent hardware errors
L4 Suspended Persistent data protection errors
L5 Suspended ACS failure
L6 Suspended Unsupported host card
L7 Suspended Submodel identifier not set or mismatched
L8 Suspended Memory configuration error
L9 Suspended Link speed mismatch
LA Suspended Reserved
LB Suspended Host card configuration error
LC Suspended Persistent cache backup configuration error
LD Suspended Mixed cache memory DIMMs
LE Suspended Uncertified cache memory DIMM sizes
LF Suspended Lockdown with limited SYMbol support
LH Suspended Controller firmware mismatch

DS drive migration changes

2010-07-05T13:32:00.001+02:00

"There is no need to verify drive migration enable settings in storage
expansion enclosures with controller firmware level 7.xx or later and Storage
Manager software version 10.xx or later"

Hard Disk Drive and Storage Expansion
Enclosure Installation and Migration Guide
Chapter 4 , Activity 4

Fedora 13 : no mount.cifs found!

2010-06-22T14:26:00.003+02:00

After I upgraded my fedora12 to 13 I've got this error ever I try to mount my samba share:
"CIFS VFS: cifs_mount failed w/return code = -22"

I found this message in the strace output:
stat64("/sbin/mount.cifs", 0xbf9133a8) = -1 ENOENT (No such file or directory)

`locate mount.cifs` didn't find the mount.cifs program.

Solution:
You have to install the following package to make cifs-mount working:
cifs-utils-4.5-2.fc13.i686

Useful stuffs : LINUX

2010-06-22T14:21:00.000+02:00

strace - trace system calls and signals

MACbook EFI

2010-06-18T14:05:00.001+02:00

[root@macko ~]# gptsync /dev/sda

Current GPT partition table:
# Start LBA End LBA Type
1 35 409633 EFI System (FAT)
2 409634 117209121 Linux LVM

Current MBR partition table:
# A Start LBA End LBA Type
1 1 34 ee EFI Protective
2 * 35 409633 83 Linux
3 409634 117209121 8e Linux LVM

Status: Analysis inconclusive, will not touch this disk.

X forward after "su"

2010-05-10T17:11:00.003+02:00

I found a good article about, how to prevent the "loss" of X forward after su to another user.

"X authentication is based on cookies -- secret little pieces of random data that only you and the X server know... So, you need to let the other user in on what your cookie is. One way to do this is as follows:
Before you issue the su or sudo (but after having ssh'ed into the remote system), request the cookie for the current DISPLAY that's connecting to your X server:

$ xauth list
You'll get something like

somehost.somedomain:10 mit-magic-cookie-1 4d22408a71a55b41ccd1657d377923ae

Then, after having done su, tell the new user what the cookie is:

$ xauth add somehost.somedomain:10 MIT-MAGIC-COOKIE-1 4d22408a71a55b41ccd1657d377923ae

(just copy'n-paste the output of the above 'xauth list' onto 'xauth add') That's it. Now, you _should_ be able to start any X application.)"

Another pretty trick:
xauth merge /home/user/.Xauthority
where /home/user is the username with made the ssh connection before "su"

Checked, It works.

Thanks

GPFS portability layer compile fails on CentOS

2010-03-25T20:17:00.003+01:00

When I tried to compile the GPFS v3.3 portability layer on CentOS 5.4 I`ve got the following errors:

[root@gpfsnode2 src]# make Autoconfig
........
........
lines ommited
........
Invoking Kbuild...
make[2]: Entering directory `/usr/src/kernels/2.6.18-164.15.1.el5-PAE-i686'
LD /usr/lpp/mmfs/src/gpl-linux/built-in.o
CC [M] /usr/lpp/mmfs/src/gpl-linux/kdump-kern.o
CC [M] /usr/lpp/mmfs/src/gpl-linux/kdump-stub.o
CC [M] /usr/lpp/mmfs/src/gpl-linux/mmwrap.o
CC [M] /usr/lpp/mmfs/src/gpl-linux/mmfsmod.o
CC [M] /usr/lpp/mmfs/src/gpl-linux/cfiles_cust.o
In file included from /usr/lpp/mmfs/src/gpl-linux/cfiles.c:56,
from /usr/lpp/mmfs/src/gpl-linux/cfiles_cust.c:60:
/usr/lpp/mmfs/src/gpl-linux/inode.c: In function ‘printInode’:
/usr/lpp/mmfs/src/gpl-linux/inode.c:130: error: ‘struct inode’ has no member named ‘i_blksize’
/usr/lpp/mmfs/src/gpl-linux/inode.c: In function ‘cxiSetOSNode’:
/usr/lpp/mmfs/src/gpl-linux/inode.c:346: error: ‘struct inode’ has no member named ‘i_blksize’
/usr/lpp/mmfs/src/gpl-linux/inode.c: In function ‘gpfs_i_getattr’:
/usr/lpp/mmfs/src/gpl-linux/inode.c:1921: error: ‘struct inode’ has no member named ‘i_blksize’
In file included from /usr/lpp/mmfs/src/gpl-linux/cfiles.c:59,
from /usr/lpp/mmfs/src/gpl-linux/cfiles_cust.c:60:
/usr/lpp/mmfs/src/gpl-linux/cxiSystem.c: In function ‘cxiFcntlLock’:
/usr/lpp/mmfs/src/gpl-linux/cxiSystem.c:714: error: too few arguments to function ‘posix_test_lock’
/usr/lpp/mmfs/src/gpl-linux/cxiSystem.c:741: error: too few arguments to function ‘posix_test_lock’
/usr/lpp/mmfs/src/gpl-linux/cxiSystem.c:768: error: implicit declaration of function ‘posix_block_lock’
/usr/lpp/mmfs/src/gpl-linux/cxiSystem.c: In function ‘cxiFlockToVFS’:
/usr/lpp/mmfs/src/gpl-linux/cxiSystem.c:975: error: ‘FL_LOCKD’ undeclared (first use in this function)
/usr/lpp/mmfs/src/gpl-linux/cxiSystem.c:975: error: (Each undeclared identifier is reported only once
/usr/lpp/mmfs/src/gpl-linux/cxiSystem.c:975: error: for each function it appears in.)
/usr/lpp/mmfs/src/gpl-linux/cxiSystem.c: In function ‘cxiVFSToFlock’:
/usr/lpp/mmfs/src/gpl-linux/cxiSystem.c:1064: error: ‘FL_LOCKD’ undeclared (first use in this function)
make[3]: *** [/usr/lpp/mmfs/src/gpl-linux/cfiles_cust.o] Error 1
make[2]: *** [_module_/usr/lpp/mmfs/src/gpl-linux] Error 2
make[2]: Leaving directory `/usr/src/kernels/2.6.18-164.15.1.el5-PAE-i686'
make[1]: *** [modules] Error 1
make[1]: Leaving directory `/usr/lpp/mmfs/src/gpl-linux'
make: *** [Modules] Error 1

Resolution:
GPFS is supported only on REDHAT distribution. BUT we now that CentOS has binary compatibilty with RHEL so change the /etc/redhat-release to the appropiate RHEL release and everything will work fine ..

# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.4 (Tikanga)

HBA & multipathing on RHEL

2010-03-24T19:48:00.001+01:00

A usefull guide to
HBA & multipathing on RHEL

Introduction
The firmware gets updated by the driver or each time the "qla2300" or "qla2400" modules are loaded. Drivers need specific firmware versions. Nevertheless here's QLogic firmware repo : ftp.qlogic.com/outgoing/linux/firmware/

Note. it's ok to have a more recent BIOS than firmware, but not the contrary.

Driver & Firmware installation
The driver should be included into the RHEL distribution. If not, use constructor's provided one e.g.,
- HP Approved Software : driverdownloads.qlogic.com/QLogicDriverDownloads_UI/Product_detail.aspx?oemid=21
- IBM Supported Software : driverdownloads.qlogic.com/QLogicDriverDownloads_UI/IBM.aspx?companyid=6
make sure you have the gcc package,
rpm -q gcc
and install the driver,
./INSTALL -h
./INSTALL -f -a

Note. make sure the default binary isn't a link to gcc 2.95 (as it's sometimes the case on Oracle installs),
ll /usr/bin/gcc
or check that the gcc version matches the distribution build,
dmesg | head -1
/usr/bin/gcc --version

Driver, firmware and BIOS versions
To check the driver and firmware versions,
cat /proc/scsi/qla2300/1 | grep Firmware

To check the BIOS version, either note it during machine's boot process, or use SANsurfer.

SANsurfer installation
Install the SANsurfer agent on the server and use the SANsurfer Windows GUI to access it. Note. the default password for SANsurfer is "config".

BIOS update
SANsurfer allows you to update HBA's BIOS, FCode and NVRAM (if you do so, read multi-boot's image release notes).

Failover & multipathing
SANsurfer
SANsurfer also allows you to configure failover and multipathing. It uses that module,
qla2xxx_conf
with that configuration file,
/etc/hba.conf

DS4000
Prerequesties,
yum install kernel-devel kernel-headers gcc
yum update kernel
sync
reboot
and check after boot,
uname -r
ls -l /lib/modules

Install IBM RDAC,
tar xvzf rdac-LINUX-09.03.0C05.0030-source.tar.gz
cd linuxrdac-09.03.0C05.0030
make clean
make
make install

Edit GRUB,
cd /boot/grub
vi menu.lst
add above the other titles (default=0),
title CentOS (2.6.18-164.el5) with MPP support
root (hd0,0)
kernel /vmlinuz-2.6.18-164.el5 ro root=LABEL=/
initrd /mpp-2.6.18-164.el5.img
N.B. change kernel package version accordingly

Reboot and before Redhat starts up, connect the fiber channel cables,
shutdown -r now
once started check everything's fine,
fdisk -l
sfdisk -s
Note. you should see one multipathed disk per LUN, as sdX.

Redhat multipathing
Prerequesties,
rpm -q device-mapper-multipath

Configure,
cd /etc
mv multipath.conf multipath.conf.dist
sed '/^#/d; /^$/d' multipath.conf.dist > multipath.conf
vi multipath.conf
change to blacklist local harddrive only,
blacklist {
devnode "sda"
}
enable,
service multipathd start
chkconfig multipathd on
check everything's fine,
fdisk -l
sfdisk -s

Note. SLES names it "multipath-tools"
Note. the old method was to use an "md" raid device on both pathes, treating one path as spare,
#mdadm --create -f -lmp -n2 -x1 /dev/md0 /dev/ /dev/
DM Multipath : www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/en-US/RHEL510/DM_Multipath/index.html
Note. make sure write cach mirroring is enabled (marc.info/?l=linux-lvm&m=108690553031551&w=2).

EMC
Use PowerPath. Also install "navihostagent" and "navicli".

IBM ESS, DS600, DS9000
Use "sdd" for failover and load balancing.

References
Welcome to SPOCK : h20272.www2.hp.com/
BIOS : en.wikipedia.org/wiki/BIOS
Extensible Firmware Interface : en.wikipedia.org/wiki/Extensible_Firmware_Interface
FCode : en.wikipedia.org/wiki/Open_Firmware#Advantages
NVRAM : en.wikipedia.org/wiki/NVRAM
Firmware : en.wikipedia.org/wiki/Firmware

Multipathing with Qlogic HBAs - failover and LUN load balancing : twiki.cern.ch/twiki/bin/view/PSSGroup/Multipathing
Device-mapper Resource Page : sources.redhat.com/dm/
LVM2 Resource Page : sources.redhat.com/lvm2/

[linux-lvm] LVM - Multipath / Failover : www.redhat.com/archives/linux-lvm/2003-September/thread.html#00160
[linux-lvm] Multipath without round-robin? : www.redhat.com/archives/linux-lvm/2004-June/thread.html#00053
How do I modify my modules.conf file so my external fiber channel disks stop showing up as /dev/sda and my internal drives as /dev/sdb? : kbase.redhat.com/faq/docs/DOC-8079
How do I modify the /etc/modules.conf file? : kbase.redhat.com/faq/docs/DOC-6919

How to setup / use multipathing on SLES : support.novell.com/techcenter/sdb/en/2005/04/sles_multipathing.html
[suse-oracle] qla2xxx failover : lists.suse.com/archive/suse-oracle/2005-Apr/index.html#138

How to Connect to the DS4000 system using Hyperterm

2010-03-24T19:42:00.001+01:00

I found a usefull guide to make reacheable a IBM ds3/4k storage if it have ip address other than default.

1. Attach the null modem serial cable to Controller A or Controller B

If this is a system with a round serial port (DS3000’s & DS4700), the serial adapter & cable have IBM part numbers; 39M5942 – Adapter, 39M5908 – Cable

2. Launch HyperTerm.

Try to get HyperTerm baud rate to 38200 or 57600, 8, 1, None (8 data, 1 stop, no parity)

>> Rumor has it that using flow control other than "None" can cause HyperTerm lock ups when connected to DS4000 controllers. This may be dependent on the version of firmware (5.4 vs. 6.6 vs. 7.15). Some of the documentation also has Xon/Xoff as the flow control protocol.

3. Press and (you may have to keep doing this until you get a response)

4. When you see "Press Space Bar within 5 Seconds To Set Baud rate,…" press the Space Bar. Wait till you see that the Baud rate reports being set before going to step 5.

5. Press and once.

6. When you see "Press Space Bar within 5 Seconds To Set Baud rate, or Press To Exit To Shell", press .

7. You will now be prompted for the password infiniti

For firmware versions 7.x and above (not the DS4300 in this example), there is a username/password combination instead of just the password. The user name is “shellUsr”, and the password is “Wy3oo&w4” (which is just up and the left of shellUsr). Depending on the method of updating, I’ve seen the user name/password set to “shellUsr/infiniti” also.

Field Tip: If you cannot break into controller, the culprit is usually the cable. Please ensure you have a 'null modem serial cable'

Troubleshooting: If you cannot break into the controller and you’re sure you have a null-modem serial cable, I find that re-booting my laptop resolves the problem. Sometimes the COM1 port on your laptop gets hung. This especially happens if you’ve been connecting and re-connecting to various serial ports.

Please follow the procedure outlined here exactly, because some commands that can be issued from the serial console can cause data loss.

You will need one IP address for each controller. Ctlr A __________ Ctlr B __________

1. Log into Controller A

2. Type netCfgSet.

a. This command will display each line, one line at a time. When each line is displayed, the cursor will be placed to the right of the current value waiting for user input. Entering a "Carriage Return" at the cursor will cause the current line to be skipped with no changes being made to its value. Entering a "." (period) at the prompt will cause the value of the current line to be reset to the factory default. To change the value of a field, simply enter the new value at the cursor. Make sure to include the "." in IP addresses and to precede the Network Init Flags with "0x" if this value is to be changed. As a minimum requirement, four fields must have non-default values in order to grant a particular host access to a controller. These fields are titled:

i. "My IP Address",

ii. "Gateway IP Address"

iii. "Subnet Mask"

3. Repeat the process for Controller B

Notes:

· It is strongly recommended that during an initial configuration that all values be set to their default values using a ".", except for the three required settings

· Change Network Init Flag to 0x01 if using a static IP address (keep it at 0x00 if using DHCP or Bootp server). In some HW versions of the DS4300, the default value is not 0x00 its 0x80, and in that case it should be set to 0x81, so the last digit is the key.

Verify Network IP Settings

Check settings using netCfgShow command via serial connection and/or Ping IP address from Command prompt. netCfgShow will dump the following:

-> netCfgShow

==== NETWORK CONFIGURATION ====

Interface Name : dse0

My Host Name : DS_a

My IP Address : 100.100.100.236

Server Host Name : host

Server IP Address : 0.0.0.0

Gateway IP Address : 100.100.100.9

Subnet Mask : 255.255.255.0

Network Init Flags : 0x01

Network Mgmt Timeout : 30

Shell Password : ************

User Name : guest

User Password : ************

NFS Root Path : (null)

NFS Group ID Number : 0

NFS User ID Number: 0n.

value = 27 = 0x1b

Once this procedure is complete, you should be able to attach with the StorageManager, and proceed as expected.

Forcing uninstall of TPC ca agent

2010-03-11T13:50:00.001+01:00

./uninstall -W beanArguments.forceUninstall=true

TPC 4.1 with EMC Clariion

2010-02-25T13:20:00.008+01:00

There isn't any publicly available step-by-step guide how to configure an oldy Clariion like FC4700 to use under TPC.
So here comes..

- Download EMC Solutions Enabler v6.0.2. If you have access to EMC download links you are pretty lucky. I wasn't. I asked an EMC customer to download me the SE package.
- It does not matter whether You use it under Linux or Windows
- Start the installation process (under windows you have to start the \osl_cd\install_shield\runprog.exe)
- Do not forget to check the "SMI Provider and cimserver" option on.

- Leave all options in default

- After the install is successfully ended start the cimserver service manually or let the install to start it.
- Open a command prompt and enable the BASE license with key you received from EMC.
cd C:\Program Files\EMC\SYMCLI\bin
symlmf
- After the key successfully added you need authorize the symcli to the Clariion SPs
symcfg authorization add -host [ipadd] -username [username] -password [password]
where [host] is ip/name of the SP , [username] is the admin defined on Clariion
First register SPA then SPB.

- Them run command
symcfg discover -clariion -file [discovery_file]
where [discovery_file] is a file containing the IP address of SP A and SPB (both on the same line with ipaddress of SPA first, and separated by a space)
- Confirm the CLARiiON is discovered with command:
symcfg -clariion list

After all start to configure TPC CIMOM data source as usual
Use /root/emc namespace and do not enter any username/pass. (if you want to use the default settings)

Creating new GUID with tivguid

2010-02-18T15:38:00.007+01:00

If you clone the AIX systems than the TivGUID will be same on all machines.
To recreate a new guid use the
/usr/tivoli/guid/tivguid command with -WRITE -NEW optins.
You can check the new Guid by issuing the
/usr/tivoli/guid/tivguid -show command.

# /usr/tivoli/guid/tivguid -show
Tivoli GUID utility - Version 1, Release 3, Level 0.
(C) Copyright IBM Corporation 2002, 2004 All Rights Reserved.

Guid:04.d8.5e.7e.38.8d.11.de.a1.bf.08.63.ac.10.cb.b4

I've seen this error when tried to install the new TPC Storage Resource Agent on two remote AIX servers. The first install was success but the second failed with errors:

NAD0124E: Failed to register Agent to Server.
NAD0040E: Agent install exited with an error code: 45

The two systems are clones of each others.
After I generate a brand new GUID on the failing system the agent registration was success.

IBM technote:
The globally unique identifier (GUID) associates a client node with a host
system. When you install the Tivoli software, the tivguid program is run to
generate a GUID which is stored in the /etc/tivoli directory on a UNIX
system. The GUID for a client node on the server can change if the host
system machine is corrupted, if the file entry is lost, or if a user obtaines the
same node name from different host systems. You can perform the
following functions from the command line:

- Create a new GUID
- View the current GUID
- Write a specific value

Under AIX other tivguid related files are installed under
/usr/tivoli/guid/. This files are installed with fileset tivoli.tivguid. There is
a README.guid with additional information.

Some useful TIVGUID commands :

tivguid -show : shows current tivguid
tivguid -create : generates a new tivguid if none exists
tivguid -write : writes the guid
tivguid -help : lists available commands

Migrating SAN booting Windows with SVC

2010-02-15T15:04:00.003+01:00

I performed an SVC migration at the weekend.
The official IBM dokumentation is not obvious.
So I took some comment to the original instructions.

The migration to IBM SVC is not a tricky rocket science work. But If you facing with Windows + SAN boot the process becomes hardener and longer than you expected.

For successful migration you must have a lot of OS/machine reboot. So relax. You will need your patience!!

Perform the following steps to migrate your existing SAN boot images:
First of all: Do not install the SDDDSM driver before the migration. Leave everything unchanged. (only the SDD needs some configuration!) Just bring down the os and follow the IBM suggested way. (My comments are after the original instructions)

1. If the existing SAN boot images are controlled by an IBM® storage controller that uses SDD as the multipathing driver, you must use SDD v1.6 or higher. Run the SDD command datapath set bootdiskmigrate 2145 to prepare for image migration. See the IBM System Storage™ Multipath Subsystem Device Driver User's Guide for more information about this command.
2. Shut down the host.
3. Perform the following configuration changes on the storage controller:
1. Remove all the image-to-host mappings from the storage controller. (Storage Controller = the original storage system .. FastT, EMC, DS .. etc.)
2. Map the existing SAN boot image and any other disks to the SAN Volume Controller. (Use the subsystem storage manager to perform the needed configurations)
4. Zone one port of each host bus adapter (HBA) to one of the SAN Volume Controller ports that is associated with the I/O group for the target image-mode VDisk.
(This means: create only ONE zone on only ONE SAN fabric. For example: Create a zone in SAN "A" like this: [SVCNODE1_HBA1] + [WINDOWS HOST HBA PORT 1])
5. Perform the following configuration changes on the SAN Volume Controller:
1. Create an image-mode VDisk for the managed disk (MDisk) that contains the SAN boot image. Use the MDisk unique identifier to specify the correct MDisk. (You can start the migration also)
2. Create a host object and assign it to the HBA port that you zoned to the SAN Volume Controller port in step 4. (You can assign all HOST ports. This does not matter)
3. Map the image mode VDisk to the host. For example, you might map the boot disk to the host with SCSI LUN ID 0.
4. Map the swap disk to the host, if required. For example, you might map the swap disk to the host with SCSI LUN ID 1. (You can map all disk to the OS.)
6. Change the boot address of the host by performing the following steps:
1. Restart the host and open the BIOS utility of the host during the booting process. (Use CTRL+Q if you use Qlogic and use CTRL+E if you use Emulex HBA)
2. Set the BIOS settings on the host to find the boot image at the worldwide port name (WWPN) of the node that is zoned to the HBA port. (It is easy because this is the only port use can "see". Otherwise You made some mistake!)
7. Boot the host in single-path mode. (It means simply boot the host. There isn't any Windows boot option called "single-path mode" ..")
8. Uninstall any multipathing driver that is not supported for SAN Volume Controller hosts that run the applicable Windows Server operating system.
9. Install a supported multipathing driver. (SDDSM. Before the SDDDSM install You have to install the suggested OS hotfixes. This can be do before the migration. It is also a time consuming process.)
10. Restart the host in single-path mode to ensure that the supported multipath driver was properly installed.
11. Zone each HBA port to one port on each SAN Volume Controller node.
12. Add HBA ports to the host object that you created in step 5.b.
13. Configure the HBA settings on the host by using the following steps:
1. Restart the host and open the host's BIOS utility during the booting process.
2. Ensure that all HBA ports are boot-enabled and can see both nodes in the I/O group that contains the SAN boot image. Configure the HBA ports for redundant paths.
3. Exit the BIOS utility and finish booting the host.
14. Map any additional VDisks to the host as required.

IBM / Brocade naming conventions

2010-02-11T10:58:00.000+01:00

PowerChute Network Shutdown System Requirements

2010-02-01T16:13:00.000+01:00

Hardware Requirements:

Smart-UPS w/ Smart Slot, Matrix, Symmetra or Silcon and either of the following:

Web/SNMP Card (AP9606)
Any of the Network Management Cards (AP9617, AP9618, AP9619, AP9630, 9631)

Software Requirements:

PowerChute Network Shutdown utilizes the following TCP/IP ports: tcp/udp 3052 and tcp/udp 80. Versions 2.2.3 utilizes port 6547 for instance 1, 6548 for instance 2, and 6549 for instance 3.

Java Runtime Environment v1.2.2 or higher for PCNS 2.0.x
Java Runtime Environment v1.4.2_02 or higher for PCNS 2.2.x

A supported Java™ Runtime Environment (JRE) as listed in the Compatibility Chart for PCNS on the APC Web site
http://www.apcc.com/tools/download/index.cfm?isocountrycode=US&tsk=

On Windows EXCEPT the Itanium and Server 2008 Server Core versions, PCNS has to determine whether it installs JRE or uses a version already installed on your system. If your JRE version is lower in number than the installation JRE, it installs the packaged JRE. If your JRE version is higher, PCNS uses your JRE version that is closest in number to the PCNS installation package (for example, if PCNS is packaged with JRE 5.0 Update 13 and you have JRE 5.0 Update 14 and 15, the installation program uses Update 14, not 15). Note that PCNS does NOT uninstall any version of JRE.

On HP-UX, AIX, Solaris 10 for x64/ x86, NetWare, Mac OS X, and Windows Itanium/ Server 2008 Server Core, PCNS does NOT install JRE.

On Linux, VMware, and SPARC versions of Solaris, PCNS gives you a choice whether or not to install JRE.

Microsoft Internet Explorer v5.01 or higher

Unix:

Xwindows must be installed and running (non-rpm versions).

Netware:

Xserver must be running

Powerchute Network Shutdown (PCNS) network checklist

2010-02-01T16:09:00.001+01:00

The following steps should help establish communication between PCNS and the Network Management Card.

1. Verify the version of PCNS that is running The most current version of PowerChute Network Shutdown can be downloaded from the site below: http://www.apcc.com/tools/download

2. Confirm the type of Network Management Card being used along with the firmware type on the card. The Network Management Cards that are designed to work with PCNS are part numbers AP9606, AP9617, AP9618, AP9619, AP9630, and AP9631. The AP9605 and the AP9603 are older cards and will not work with PCNS.

3: Check the network settings on the server running PCNS. Incorrect subnet mask or default gateway settings will cause communications issues even the PCNS can register with the card successfully during installation. For Unix server,use the command "#ifconfig -a" to display the network settings.You may also need to verify network settings in file /etc/networks if the server is running Solaris.

4: Verify multiple PCNS install daemons are not running on the server. In this case, the PCNS client can't register with the network management card during installation. For Unix server, use the command "#ps -ef |grep java" to display java related daemon. Since PCNS is java based, all PCNS install daemons will be displayed in the list. Make sure that there is only one install daemon running.

5. Verify that the PCNS service is started. If it is already started, try stopping the service and then restarting it again. Instructions for starting and stopping the PCNS service can be found in the Installation guide.

6. Check the Network Management Card to see if the IP address of the PCNS client is listed under the PowerChute menu. If it is not, either add the PCNS client IP to the list, or make sure that the Network Management Card and the PCNS client are on the same segment. Otherwise, communication will not be possible.

7. See if the customer has set up an Authentication Phrase on the Network Management Card. If so, have the customer reset the card to default except TCP/IP. This option can be found under the System>Tools menu on the Network Management Card. Resetting to defaults with reset any configurations changes that the customer has made.

8. Verify that the proper user name and password for the Network Management Card are being used and that the user name is 10 characters or less.

9. Verify that there is a network connection between the PCNS client computer and the Network Management Card. Try accessing the Network Management Card from the PCNS client computer or try using the ping utility from the Network Management Card.

10. Have the customer verify that ports 3052 and port 80 are open on their router or server. These two ports must be open for bi-directional communication. If the customer's router, firewall, or anti-virus software is blocking these ports, communication will be lost. If the ports are open, make sure that there are no other devices that could be using these ports.

11. Check the IP address of the Network Management Card and make sure that it is the same address that PCNS is looking for. To check the IP address that PCNS is looking for, go under Communications. The IP addresses should match.

12. Make sure that the customer doesn't have proxy settings set up on the server. To disable proxy, open up Internet Explorer. Go to Tools>InternetOptions>Connections>LAN Settings. From here, make sure that Proxy is disabled (unchecked).

IBM Tape SMI-S agent settings

2010-01-28T13:51:00.000+01:00

The SMI-S Agent follows the security settings of the Web server. When SSL is disabled, it listens on the standard CIM HTTP port 5988. When SSL is enabled, it uses the CIM HTTPS port 5989. When user security is enabled the CIMOM requires a Web user and password that are part of the Administrator or Monitor Roles. The SMI-S agent uses the namespace root/ibm

Recording an SAP® 6.2 GUI Transaction with Rational Robot

2010-01-22T11:59:00.003+01:00

Rational Robot supports SAP® GUI V4.5, but there is no official statement of support for SAP® GUI V6.2, which many companies are today using. However, since the SAP® GUI uses the Windows GUI, you can of course record an SAP® GUI transaction. There is just one thing to watch out for; the SAP® GUI V6.2 will freeze when the Logon button is clicked while Robot is recording. So you need to take a few simple steps to work around this.

The SAP GUI freezes when you click on the Logon button while recording

The recording of the freeze, and multiple attempts to click the Logon button

Fortunately, this is quite easy to work around; just complete the following steps.
1. Stop the recording in Robot.
2. Open the script and delete any duplicate PushButton commands that you may have recorded, so that only one of them remains.
3. Open the Windows Task Manager and terminate the process saplogon.exe.
4. Restart the SAP® GUI and click the Logon button.
5. Open the recorded Robot script and move the cursor below the failed PushButton command.
6. Click on the menu option to restart Robot recording at the current line.
7. Return to the SAP® GUI and proceed with the transaction.
The final recorded script will simply be a splice of the two separate recording sessions.

mount nfs export on MAC

2010-01-04T15:17:00.003+01:00

If you try to mount an NFS on to your Mac OS X by using
"sudo mount -t nfs /[NFS export] [LOCAL DIR]"
maybe you got an error message like this:
"mount_nfs: ******* : Operation not permitted"

Resolution:
Add the "insecure" option to the nfs export.

the MySQL client library is not bundled anymore with php 5x

2009-12-18T16:14:00.004+01:00

PHP 5.3.1

If you'd like compile php 5x from source with option --with-mysql you get a message like this:

"...
configure: error: Cannot find MySQL header files under yes.
Note that the MySQL client library is not bundled anymore!"

The mysql headers file location on RHEL /usr/include/mysql

So, the right option setting is: --with-mysql=/usr/include/mysql

Correcting the Java Virtual Machine Not Found Error

2009-12-02T20:59:00.002+01:00

Complete this task to correct the Java™ Virtual Machine Not Found Error.

About this task

The Java Virtual Machine Not Found error occurs when the DS CLI installer cannot find the correct version of Java in the standard directories of your system. You must have Java 1.4.1 or higher on your system for the DS CLI application to work.

Notes:

This error might also occur if you are installing the DS CLI on an AIX® system. The LIBPATH environment variable can interfere with the installation of the DS CLI and can result in the display of the Java Virtual Machine Not Found error. To prevent this error, disable the LIBPATH environment variable before you install the DS CLI. After the installation of the DS CLI, enable the LIBPATH environment variable so that it can be used with other applications.
If you have already installed the DS Storage Manager, you have installed Java 1.5 on your system. However, because it was not installed in one of your standard directories, the DS CLI installer did not find it during its initial check.

If Java 1.4.1 or higher is not found during the initial check, the following message is displayed:

If you are using Windows®, the following message is displayed:

LaunchAnywhere Error: Could not find a valid Java virtual machine to load.

You may need to reinstall a supported Java virtual machine.

If you are using Unix or Linux®, the following message is displayed:

No Java virtual machine could be found from your PATH
environment variable.  You must install a VM prior to
running this program.

Java 1.4.2 is available on the DS CLI installation CD for installation on some systems.

After ensuring that Java 1.4.1 or higher is installed, perform one of the following actions to correct the Java Virtual Machine Not Found error:

Run the DS CLI installer again from the console, and provide the path to the JVM using the LAX_VM option. The following examples represent paths to the correct version of Java:
- For a Windows system, specify the following:
```
dsclisetup.exe LAX_VM "C:\Program Files\java-whatever\jre\bin\java.exe"
```
  Note: Because there is a space in the Program Files directory name, you are required to add quotes around the file name.
- For a Unix or Linux system, specify the following:
```
dsclisetup.bin LAX_VM /opt/ibm-Java-whatever/java/bin/java
```
  Note: If you use this argument, the installer attempts to use whatever JVM that you specify. You must use a supported version.
- Continue with the installation of the DS CLI application.
(For Unix or Linux) Add the Java virtual machine location to your PATH environment variable by running the following command:
```
export PATH=$PATH:/opt/ibm-Java-whatever/java/bin
```
Then, run the dsclisetup.bin program to install the DS CLI.
(AIX only) Run the following commands to sequentially disable the LIBPATH environment variable, install the DS CLI, and restore the LIBPATH environment variable:
```
export LIBSAVE=$LIBPATH
     unset LIBPATH
dsclisetup.bin LAX_VM/opt/ibm-Java-whatever/java/bin/java
     export LIBPATH=$LIBSAVE
     unset LIBSAVE
```

While loop variable lost after loop ends

2009-11-27T14:18:00.001+01:00

"I'm having a problem returning variables from a loop. the variable test get incremented each time it goes through the loop but if I try to get the count after the loop has run I get 0. Can anyone explain to me why this is happening and maybe show the correct way to go about doing this?"

The answer:
"sh is running the while loop in a subshell. Variables changed in the subshell do affect the values in the main shell.

ksh won't do that. Switch to ksh.

And ksh can increment the variable directly:
((test=test+1))"

RPT 8.0 RPWC0002E

2009-10-29T12:58:00.005+01:00

When you call a webservice in RPT sometimes you receive the following error:
RPWC0002E Unexpected exception (com.ibm.rational.test.lt.models.wscore.transport.impl.HttpTransporterImpl)
java.lang.NullPointerException
at com.ibm.rational.test.lt.models.wscore.datamodel.security.util.KeyStoreUtil$SSLCreationUtil.getSSLContext(KeyStoreUtil.java:122)
at com.ibm.rational.test.lt.models.wscore.transport.noblck.impl.SocketFactoryUtil.create(SocketFactoryUtil.java:97)
at com.ibm.rational.test.lt.models.wscore.transport.noblck.impl.SocketFactoryUtil.buildSocket(SocketFactoryUtil.java:57)
at com.ibm.rational.test.lt.models.wscore.transport.http.impl.HttpRequest.(HttpRequest.java:43)
at com.ibm.rational.test.lt.models.wscore.transport.impl.HttpTransporterImpl.setUpIO(HttpTransporterImpl.java:466)
at com.ibm.rational.test.lt.models.wscore.transport.impl.HttpTransporterImpl.connect(HttpTransporterImpl.java:146)
at com.ibm.rational.test.lt.models.wscore.transport.impl.SynchronousUtil.send(SynchronousUtil.java:27)
at com.ibm.rational.ttt.common.ui.send.ObservableWSCommunication.sendAndReceive(ObservableWSCommunication.java:110)
at com.ibm.rational.ttt.common.ui.send.SendRequestThread$ObservedThread.run(SendRequestThread.java:186)

The cause of the problem is that you try to use http insteed of https. The endpoint call points to an https site but the transport is set to http.

Solutions:

Change the transport configuration to a user defined HTTPS with SSL.

Recovering from bad certificate errors on TPC agents

2009-10-19T13:52:00.001+02:00

Technote (troubleshooting)

Problem(Abstract)

A TPC data or fabric agent is not working. This may be due to a problem with the certificate for the common agent component.

Symptom

One or both of:

- Agent shows as down or unreachable in TPC gui.
- Common agent is down or not communicating, and subagents are down or not responding.

Cause

Damaged/corrupted certificate/truststore files.

Diagnosing the problem

Common agent log file msgAgent.log contains java error messages about a 'bad certificate':

- Error codes: BTC5019E, BTC4045E
- 'Rejected connection attempt' on port 9511.

Resolving the problem

Take the following steps to correct this problem:

1. Log in to the agent machine with the userid account used to install IBM Tivoli Storage Productivity Center (usually 'root' on UNIX and 'Administrator' on Windows).

2. Stop the common agent service if it is running (it probably is not because of this error) using the following commands:

- UNIX: cd /opt/IBM/TPC/ca; ./endpoint.sh stop
- Windows: stop the 'Tivoli Common Agent' service through the Computer Management 'Services' panel

3. Change directory to the common agent installation directory:

- UNIX: /opt/IBM/TPC/ca
- Windows: c:\Program Files\IBM\TPC\ca

4. Locate and rename the 'cert' directory to 'cert.backup', and create a new, empty 'cert' directory in its place.

4. Change directory to the 'config' directory and locate the endpoint.properties file.

6. Edit the endpoint.properties file (make a backup copy if you wish) and change the following line as shown:

'agent.ssl.truststore.download=false' to 'agent.ssl.truststore.download=true'

7. Restart Common Agent.

- UNIX: cd /opt/IBM/TPC/ca; ./endpoint.sh start
- Windows: start the 'Tivoli Common Agent' service through the Computer Management 'Services' panel

8. Check files in the new 'cert' directory. The directory should contain 4 files once registration with the Agent Manager is successful.

TPC - Help to Find the Supported Products and Platforms Interoperability Matrix Links

2009-10-19T11:15:00.000+02:00

Abstract

Since the migration of the TotalStorage Productivity Center support site to Tivoli Storage Productivity Center, it has been difficult to find certain content items. This document intends to provide a variety of links for the 3.x and 4.x version interoperability and support matrices to make navigating a little easier.

Content

Supported Platforms		Supported Products
Agents, Servers and GUI	Replication	HBAs	Switches & Directors	Storage
4.1.0	4.1.0	4.1.0	4.1.0	4.1.0
Not Applicable	3.4	Not applicable	Not Applicable
3.3.2		3.3.2	3.3.2	3.3.2
3.3.1		3.3.1	3.3.1	3.3.1
3.3.0	3.3	3.3.0	3.3.0	3.3.0
		3.1.3/3.2.1	3.1.3/3.2.1	3.1.3/3.2.1
3.1.2/3.2.0		3.1.2/3.2.0	3.1.2/3.2.0	3.1.2/3.2.0
		3.1.1	3.1.1	3.1.1
3.1.0 Operating Systems 3.1.0 Databases	3.1	3.1.0	3.1.0	3.1.0

This table will be updated as additional links become available.

IPL LED 518 555

2009-10-15T22:46:00.006+02:00

About this document

This document covers the use of the fsck (file system check) command in Maintenance mode to repair inconsistencies in file systems. The procedure described is useful when file system corruption in the primary root file systems is suspected or, in many cases, to correct an IPL hang at LED value 518 or LED value 555.

Recovery procedure

Boot your system into a limited function maintenance shell (Service, or Maintenance mode) from AIX bootable media to perform file system checks on your root file systems.
Please refer to your system user's or installation and service guide for specific IPL procedures related to your type and model of hardware. You can also refer to the document titled "Booting in Service Mode," available at http://techsupport.services.ibm.com/rs6k/techbrowse/.
With bootable media of the same version and level as the system, boot the system. The bootable media can be any ONE of the following:
- Bootable CD-ROM
- NON_AUTOINSTALL mksysb
- Bootable Install Tape
Follow the screen prompts to the following menu:
```
   Welcome to Base Operating System
 Installation and Maintenance
```
Choose Start Maintenance Mode for System Recovery (Option 3).
The next screen displays the Maintenance menu.
Choose Access a Root Volume Group (Option 1).
The next screen displays a warning that indicates you will not be able to return to the Base OS menu without rebooting.
Choose 0 continue.
The next screen displays information about all volume groups on the system.
Select the root volume group by number.
Choose Access this volume group and start a shell before mounting file systems (Option 2).
If you get errors from the preceding option, do not continue with the rest of this procedure. Correct the problem causing the error. If you need assistance correcting the problem causing the error, contact one of the following:
- local branch office
- your point of sale
- your AIX support center
If no errors occur, proceed with the following steps.
Run the following commands to check and repair file systems.
NOTE: The -y option gives fsck permission to repair file system corruption when necessary. This flag can be used to avoid having to manually answer multiple confirmation prompts, however, use of this flag can cause permanent, unnecessary data loss in some situations.
```
 fsck /dev/hd4
 fsck /dev/hd2
 fsck /dev/hd3
 fsck /dev/hd9var
 fsck /dev/hd1
```
To format the default jfslog for the rootvg Journaled File System (JFS) file systems, run the following command:
```
 /usr/sbin/logform /dev/hd8
```
Answer yes when asked if you want to destroy the log.
If your system is hanging at LED 518 during a Normal mode boot, it is possible the /etc/filesystems file is corrupt or missing. To temporarily replace the disk-based /etc/filesystems file, run the following commands:
```
 mount /dev/hd4 /mnt
 mv /mnt/etc/filesystems /mnt/etc/filesystems.[MMDDYY]
 cp /etc/filesystems /mnt/etc/filesystems
 umount /mnt
```
MMDDYY represents the current two-digit representation of the Month, Day and Year, respectively.
Type exit to exit from the shell. The file systems should automatically mount after you type exit. If you receive error messages, reboot into a limited function maintenance shell again to attempt to address the failure causes.
If you have user-created file systems in the rootvg volume group, run fsck on them now. Enter:
```
 fsck /dev/[LVname]
```
LVname is the name of your user-defined logical volume.
If you used the preceding procedure to temporarily replace the /etc/filesystems file, and you have user-created file systems in the rootvg volume group, you must also run the following command:
```
 imfs -l /dev/[LVname]
```
If you have file systems in a volume group other than rootvg, run fsck on them now. Enter:
```
 varyonvg [VGname]
 fsck /dev/[LVname]
```
VGname is the name of your user-defined volume group.
If you used the preceding procedure to temporarily replace the /etc/filesystems file, also run the following command:
```
 imfs [VGname]
```
The preceding commands can be repeated for each user-defined volume group on the system.
If your system was hanging at LED 518 and you are unable to activate non-rootvg volume groups in Service mode, you can manually edit the /etc/filesystems file and add the appropriate entries.
The file /etc/filesystems.MMDDYY saved in the preceding steps may be used as a reference if it is readable. However, the imfs method is preferred since it uses information stored in the logical volume control block to re-populate the /etc/filesystems file.
If your system has a mode select key, turn it to the Normal position.
Reboot the system into Normal mode using the following command:
```
 sync;sync;sync;reboot
```
If your system still halts at the LED 518 display, in many cases, it is faster and more cost-effective to reinstall from a recent system backup. Attempting to isolate the cause of the problem can be very time-consuming and often results in the determination that a reinstall is required to correct the problem anyway.
If you need assistance correcting the problem causing the halt, contact one of the following:
- local branch office
- your point of sale
- your AIX support center

[ Doc Ref: 90605188914738 Publish Date: Nov. 06, 2000 4FAX Ref: 2535 ]

IPL LED 518 555

2009-10-15T22:46:00.005+02:00

About this document

Recovery procedure

Boot your system into a limited function maintenance shell (Service, or Maintenance mode) from AIX bootable media to perform file system checks on your root file systems.
With bootable media of the same version and level as the system, boot the system. The bootable media can be any ONE of the following:
- Bootable CD-ROM
- NON_AUTOINSTALL mksysb
- Bootable Install Tape
Follow the screen prompts to the following menu:
```
   Welcome to Base Operating System
Installation and Maintenance
```
Choose Start Maintenance Mode for System Recovery (Option 3).
The next screen displays the Maintenance menu.
Choose Access a Root Volume Group (Option 1).
The next screen displays a warning that indicates you will not be able to return to the Base OS menu without rebooting.
Choose 0 continue.
The next screen displays information about all volume groups on the system.
Select the root volume group by number.
Choose Access this volume group and start a shell before mounting file systems (Option 2).
If you get errors from the preceding option, do not continue with the rest of this procedure. Correct the problem causing the error. If you need assistance correcting the problem causing the error, contact one of the following:
- local branch office
- your point of sale
- your AIX support center
If no errors occur, proceed with the following steps.
Run the following commands to check and repair file systems.
NOTE: The -y option gives fsck permission to repair file system corruption when necessary. This flag can be used to avoid having to manually answer multiple confirmation prompts, however, use of this flag can cause permanent, unnecessary data loss in some situations.
```
 fsck /dev/hd4
fsck /dev/hd2
fsck /dev/hd3
fsck /dev/hd9var
fsck /dev/hd1
```
To format the default jfslog for the rootvg Journaled File System (JFS) file systems, run the following command:
```
 /usr/sbin/logform /dev/hd8
```
Answer yes when asked if you want to destroy the log.
If your system is hanging at LED 518 during a Normal mode boot, it is possible the /etc/filesystems file is corrupt or missing. To temporarily replace the disk-based /etc/filesystems file, run the following commands:
```
 mount /dev/hd4 /mnt
mv /mnt/etc/filesystems /mnt/etc/filesystems.[MMDDYY]
cp /etc/filesystems /mnt/etc/filesystems
umount /mnt
```
MMDDYY represents the current two-digit representation of the Month, Day and Year, respectively.
Type exit to exit from the shell. The file systems should automatically mount after you type exit. If you receive error messages, reboot into a limited function maintenance shell again to attempt to address the failure causes.
If you have user-created file systems in the rootvg volume group, run fsck on them now. Enter:
```
 fsck /dev/[LVname]
```
LVname is the name of your user-defined logical volume.
If you used the preceding procedure to temporarily replace the /etc/filesystems file, and you have user-created file systems in the rootvg volume group, you must also run the following command:
```
 imfs -l /dev/[LVname]
```
If you have file systems in a volume group other than rootvg, run fsck on them now. Enter:
```
 varyonvg [VGname]
fsck /dev/[LVname]
```
VGname is the name of your user-defined volume group.
If you used the preceding procedure to temporarily replace the /etc/filesystems file, also run the following command:
```
 imfs [VGname]
```
The preceding commands can be repeated for each user-defined volume group on the system.
If your system was hanging at LED 518 and you are unable to activate non-rootvg volume groups in Service mode, you can manually edit the /etc/filesystems file and add the appropriate entries.
The file /etc/filesystems.MMDDYY saved in the preceding steps may be used as a reference if it is readable. However, the imfs method is preferred since it uses information stored in the logical volume control block to re-populate the /etc/filesystems file.
If your system has a mode select key, turn it to the Normal position.
Reboot the system into Normal mode using the following command:
```
 sync;sync;sync;reboot
```
If your system still halts at the LED 518 display, in many cases, it is faster and more cost-effective to reinstall from a recent system backup. Attempting to isolate the cause of the problem can be very time-consuming and often results in the determination that a reinstall is required to correct the problem anyway.
If you need assistance correcting the problem causing the halt, contact one of the following:
- local branch office
- your point of sale
- your AIX support center

[ Doc Ref: 90605188914738 Publish Date: Nov. 06, 2000 4FAX Ref: 2535 ]

Techdocs

Full fabric feature not activating

Locating the WWPN without restarting the host in linux os

RPT test does not work after exporting to the AMC

Problem description:

RPT test works fine but after you export to the AMC via ITCAM plugin it stops working and get a "Request timed out" error.

After examining the request xml in the log you can see extra header information:

<reqmetrics:arm_correlator soapenv:actor="reqmetricsURI"xmlns:reqmetrics="http://websphere.ibm.com" > ...< /reqmetrics:arm_correlator >

I faced this problem when I created test against a webservice running in Webshpere Message Broker that does not implemented the ARM feature.

Solution:

"Starting with RPT version 8.2 and later,you can modify the eclipse.ini file (typically locatedin the RPT workbench installation directory, for example, C:\ProgramFiles\IBM\SDP) by adding the Java option RPTNOSOAPHEADERRTB to suppressthe generation of these additional SOAP headers. For example:

Recommended parameters in dual-VIOs environmnent

Get PATH priority in AIX

RBAC scripting

Successful steps to get a working sudosh in AIX

dsm sample scripts

dsm error

VIO profile

IBM SAN Volume Controller SVC console inital config

IBM SAN Volume Controller V4x Resetting SVC Console Password

IBM SAN Volume Controller V4x Resetting SVC Console Password

Useful nim commands and some common error

Instructions to convert DS4000 disks from MPIO to AIX_fcparray(RDAC).

HP - Brocade SAN switch model naming matrix

ODM Device Configuration Object Classes

hacmp tutorial

AIX .profile

Migrating Users from One AIX System to Another AIX System

Support for passwords with more than 8 characters and Loadable Password Algorithm

AIX "Fast I/O Failure for Fibre Channel Devices" and "Dynamic Tracking of Fibre Channel Devices".

X11 libraries required for TPC server install on Linux

H196488: DS3500/DS3950/DS5000 systems not working with Brocade on 8 Gbps host ports - IBM System Storage

Source

Symptom

Affected configurations

Workaround

Additional information

Installshield error on x86_64 RedHat Linux

Install Leopard With An External Hard Drive

How To Enable Dvd Drive Sharing on a Non-Air Macbook

Qlogic SANBox password reset

Linux Storage Reconfiguration

BOMC (Bootable Media Creator) error

Determine the process running on a particular port

Brocade Password Recovery

Sample script to check wheter TPC performance collection is working well

Disk I/O and the Network | AIX | IBM Systems Magazine

Linux FC tape devices persistent binding

How to find brocade switch model type based on switchshow output.

GPFS portability layer compile fals Part II.

Centos RHEL WHATPROVIDES

DB2 instance wont start at system startup.

JFS2 filesystem is clean but won't be mounted

Numeric display diagnostic codes DS 4000

DS drive migration changes

Fedora 13 : no mount.cifs found!

Useful stuffs : LINUX

MACbook EFI

X forward after "su"

GPFS portability layer compile fails on CentOS

HBA & multipathing on RHEL

How to Connect to the DS4000 system using Hyperterm

Forcing uninstall of TPC ca agent

TPC 4.1 with EMC Clariion

Creating new GUID with tivguid

Migrating SAN booting Windows with SVC

IBM / Brocade naming conventions

PowerChute Network Shutdown System Requirements

Powerchute Network Shutdown (PCNS) network checklist

IBM Tape SMI-S agent settings

Recording an SAP® 6.2 GUI Transaction with Rational Robot

mount nfs export on MAC

the MySQL client library is not bundled anymore with php 5x

Correcting the Java Virtual Machine Not Found Error

While loop variable lost after loop ends

RPT 8.0 RPWC0002E

Recovering from bad certificate errors on TPC agents

Technote (troubleshooting)

Problem(Abstract)

Symptom

<reqmetrics:arm_correlator soapenv:actor="reqmetricsURI"
xmlns:reqmetrics="http://websphere.ibm.com" > ...
< /reqmetrics:arm_correlator >

"Starting with RPT version 8.2 and later,you can modify the `eclipse.ini` file (typically locatedin the RPT workbench installation directory, for example, C:\ProgramFiles\IBM\SDP) by adding the Java option RPTNOSOAPHEADERRTB to suppressthe generation of these additional SOAP headers. For example: