blog'o thnet - Comments

Update the HBA firmware on Oracle-branded HBAs - Julien Gabel

Julien Gabel — Mon, 29 Apr 2013 12:02:06 +0200

Good question! AFAIK, when you boot the system you will receive this kind of output in the messages file:

Apr 24 22:51:31 beastie emlxs: [ID 349649 kern.info] [ B.1A7F]emlxs0: NOTICE: 100: Driver attach. (Copyright (c) 2004-2012 Emulex. All rights reserved.)
Apr 24 22:51:31 beastie emlxs: [ID 349649 kern.info] [ 6.0B2E]emlxs0: NOTICE:1502: Firmware Library (LP10000-S: v1.92a1 (td192a1.all))
Apr 24 22:51:31 beastie emlxs: [ID 349649 kern.info] [ 6.0B2E]emlxs0: NOTICE:1502: Firmware Library (LP11000-S: v2.82a4 (bd282a4.all))
Apr 24 22:51:31 beastie emlxs: [ID 349649 kern.info] [ 6.0B2E]emlxs0: NOTICE:1502: Firmware Library (LP11002-S: v2.82a4 (bf282a4.all))
Apr 24 22:51:31 beastie emlxs: [ID 349649 kern.info] [ 6.0B2E]emlxs0: NOTICE:1502: Firmware Library (LPe11000-S: v2.82a4 (zd282a4.all))
Apr 24 22:51:31 beastie emlxs: [ID 349649 kern.info] [ 6.0B2E]emlxs0: NOTICE:1502: Firmware Library (LPe11002-S: v2.82a4 (zf282a4.all))
Apr 24 22:51:31 beastie emlxs: [ID 349649 kern.info] [ 6.0B2E]emlxs0: NOTICE:1502: Firmware Library (LPe12000-S: v2.01a4 (ud201a4.all))
Apr 24 22:51:31 beastie emlxs: [ID 349649 kern.info] [ B.1A84]emlxs0: NOTICE: 100: Driver attach. (Emulex-S s10-64 sparc v2.80.8.0 (2012.09.17.15.45))
Apr 24 22:51:31 beastie emlxs: [ID 349649 kern.info] [ B.1A87]emlxs0: NOTICE: 100: Driver attach. (LPe12000-S Dev_id:fc40 Sub_id:fc41 Id:35)
Apr 24 22:51:31 beastie emlxs: [ID 349649 kern.info] [ B.1A94]emlxs0: NOTICE: 100: Driver attach. (Firmware:2.00a3 (U3D2.00A3) Boot:5.03a0 Fcode:3.01a1)
Apr 24 22:51:31 beastie emlxs: [ID 349649 kern.info] [ B.1AC4]emlxs0: NOTICE: 100: Driver attach. (SLI:3 MSIX:8 NPIV:0 FCA)
Apr 24 22:51:31 beastie emlxs: [ID 349649 kern.info] [ B.1ACC]emlxs0: NOTICE: 100: Driver attach. (WWPN:10000000C9E43600 WWNN:20000000C9E43600)
Apr 24 22:51:32 beastie emlxs: [ID 349649 kern.info] [ 1.037A]emlxs0:WARNING:1540: Firmware update required. (To trigger an update, a manual HBA or link reset using luxadm, fcadm, or emlxadm is required.)

So, we can clearly see the different firmwares known by the system depending on the type of the HBA. In our case, we had an HBA of type LPe12000-S (seen in the same messages file, or from the output of the command fcinfo hba-port | grep Model). So, the corresponding new firmware will to be v2.01a4 for this particular host bus adapter, as we can confirm looking at the log during a firmware upgrade:

Apr 25 14:14:14 beastie emlxs: [ID 349649 kern.info] [ 5.03DD]emlxs0: NOTICE: 710: Link down.
Apr 25 14:14:18 beastie emlxs: [ID 349649 kern.info] [13.02D5]emlxs0: NOTICE: 200: Adapter initialization. (Firmware update needed. Updating. id=35 fw=6)
Apr 25 14:14:18 beastie emlxs: [ID 349649 kern.info] [ 3.111E]emlxs0: NOTICE:1520: Firmware download. (AWC file: KERN: old=1.10a8  new=1.11a3  Update.)
Apr 25 14:14:18 beastie emlxs: [ID 349649 kern.info] [ 3.113E]emlxs0: NOTICE:1520: Firmware download. (DWC file: TEST:             new=1.00a4  Update.)
Apr 25 14:14:18 beastie emlxs: [ID 349649 kern.info] [ 3.1152]emlxs0: NOTICE:1520: Firmware download. (DWC file: STUB: old=2.00a3  new=2.01a4  Update.)
Apr 25 14:14:18 beastie emlxs: [ID 349649 kern.info] [ 3.1170]emlxs0: NOTICE:1520: Firmware download. (DWC file: SLI2: old=2.00a3  new=2.01a4  Update.)
Apr 25 14:14:18 beastie emlxs: [ID 349649 kern.info] [ 3.117F]emlxs0: NOTICE:1520: Firmware download. (DWC file: SLI3: old=2.00a3  new=2.01a4  Update.)
Apr 25 14:14:30 beastie emlxs: [ID 349649 kern.info] [ 3.0151]emlxs0: NOTICE:1521: Firmware download complete. (Status good.)
Apr 25 14:14:36 beastie emlxs: [ID 349649 kern.info] [ 5.061B]emlxs0: NOTICE: 720: Link up. (8Gb, fabric, initiator)

Update the HBA firmware on Oracle-branded HBAs - Ajay

Ajay — Mon, 29 Apr 2013 11:35:40 +0200

Hi,

Nice Post.

Without doing "luxadm -e forcelip /dev/cfg/cx" , is there any way to check the version of new firmware level to be upgraded.

Regards,
Ajy

Finding The Process Responsible For Crashing A System - Norbert Lenz

Norbert Lenz — Thu, 28 Feb 2013 11:05:14 +0100

The cause of the panic can be much more easier obtained by using Solaris Crash Analysis Tool (scat).

Just type the command 'panic' within scat.

Update the HBA firmware on Oracle-branded HBAs - Julien Gabel

Julien Gabel — Tue, 26 Feb 2013 09:19:53 +0100

Well, as stated in the post, you can execute luxadm -e forcelip on Solaris 10 and Solaris 11 (or a fcadm force-lip on Solaris 11 only). Please be aware that this procedure is disruptive.

Update the HBA firmware on Oracle-branded HBAs - Zeeshan Ahmed

Zeeshan Ahmed — Tue, 26 Feb 2013 09:07:28 +0100

emlxs: [ID 349649 kern.info] [ 1.0340]emlxs1:WARNING:1540: Firmware update required. (A manual HBA reset or link reset (using luxadm or fcadm) is required.)

- How to reset HBA

Discrepancies Between df And du Outputs - Julien Gabel

Julien Gabel — Wed, 07 Nov 2012 15:30:14 +0100

Hi Johnny, I think lsof might help in this particular case.

Discrepancies Between df And du Outputs - johnny

johnny — Mon, 05 Nov 2012 08:59:41 +0100

Is there a way to find out the file that was deleted.

How to Add a New "sshd_adm" Service on AIX 5L - Michal Rozek

Michal Rozek — Tue, 14 Aug 2012 12:19:09 +0200

Great tuto :) This is what I was looking 4... cheers Juls!

Export and Import a Volume Group... When Things Goes the Wrong Way - Julien Gabel

Julien Gabel — Thu, 09 Aug 2012 13:42:23 +0200

The problem is that the local ODM already know about a logical volume which has the same name. Because there is only one namespace foe the devices, there can be only one name for each logical volume.

When working on a rootvg, we generally work through a network booted (mini-)environment to be able to work on the rootvg. As pointed by Benoit Creau, you can also try to import the volume using the importvg command. As stated by the manual page:

The importvg command changes the name of a logical volume if the name already exists in the system. It prints a message and the new name to standard error, and updates the /etc/filesystems file to include the new logical volume name. If the importvg command renames any filesystem log logical volumes, you must manually update any file systems using that log device to know about the renamed device.

So, here is a little test case. Verify that the second disk (hdisk1 in this case) is the rootvg of another system:

# cfgmgr && lspv
hdisk0          00c0ce845d3c0846                    rootvg          active
hdisk1          00c0ce745d1f562b                    None

# lqueryvg -Atp hdisk1
[...]
Logical:        00c0ce7400004c00000001385d1f56b7.1   hd5 1
                00c0ce7400004c00000001385d1f56b7.2   hd6 1
                00c0ce7400004c00000001385d1f56b7.3   hd8 1
                00c0ce7400004c00000001385d1f56b7.4   hd4 1
                00c0ce7400004c00000001385d1f56b7.5   hd2 1
                00c0ce7400004c00000001385d1f56b7.6   hd9var 1
                00c0ce7400004c00000001385d1f56b7.7   hd3 1
                00c0ce7400004c00000001385d1f56b7.8   hd1 1
                00c0ce7400004c00000001385d1f56b7.9   hd10opt 1
[...]

So, it seems to be the case. Then import it, and if the logical volume names are already used locally, it will be renamed on the fly:

# importvg -y testvg hdisk1
0516-530 synclvodm: Logical volume name hd5 changed to bootlv00.
0516-530 synclvodm: Logical volume name hd6 changed to pagelv00.
0516-530 synclvodm: Logical volume name hd8 changed to loglv00.
0516-712 synclvodm: The chlv succeeded, however chfs must now be
        run on every filesystem which references the old log name hd8.
0516-530 synclvodm: Logical volume name hd4 changed to fslv00.
0516-530 synclvodm: Logical volume name hd2 changed to fslv01.
0516-530 synclvodm: Logical volume name hd9var changed to fslv02.
0516-530 synclvodm: Logical volume name hd3 changed to fslv03.
0516-530 synclvodm: Logical volume name hd1 changed to fslv04.
0516-530 synclvodm: Logical volume name hd10opt changed to fslv05.
[...]
testvg

# lsvg -l testvg
testvg:
LV NAME             TYPE       LPs     PPs     PVs  LV STATE      MOUNT POINT
bootlv00            boot       1       1       1    closed/syncd  N/A
pagelv00            paging     128     128     1    closed/syncd  N/A
loglv00             jfs2log    1       1       1    closed/syncd  N/A
fslv00              jfs2       7       7       1    closed/syncd  /export/um_lpp_source
fslv01              jfs2       64      64      1    closed/syncd  N/A
fslv02              jfs2       14      14      1    closed/syncd  N/A
fslv03              jfs2       5       5       1    closed/syncd  N/A
fslv04              jfs2       1       1       1    closed/syncd  N/A
fslv05              jfs2       11      11      1    closed/syncd  N/A
fslv06              jfs2       4       4       1    closed/syncd  N/A
lv00                sysdump    32      32      1    closed/syncd  N/A
fslv07              jfs2       8       8       1    closed/syncd  N/A
fslv08              jfs2       32      32      1    closed/syncd  N/A

Here, the logical volume hd2 of the other rootvg has been renamed to fslv01. Then, depending on the problem you are trying to solve, you can mount the filesystem (without forgetting to specify the jfs2log logical volume):

# mount -o log=/dev/loglv00 /dev/fslv01 /mnt
Replaying log for /dev/fslv01.

Hope this helps.

Export and Import a Volume Group... When Things Goes the Wrong Way - Fran

Fran — Wed, 08 Aug 2012 18:41:31 +0200

I am trying to import a VG from a PV from another system in order to mount the LVs for analysis. It is the rootvg from that system. It appears I am running into an issue with duplicate LV names.

Everything is fine until synclvodm. I get this:

# synclvodm -v -P tempvg08 hd2
synclvodm: Physical volume data updated.
0516-522 synclvodm: Unable to update logical volume hd2.

Any ideas?

Fake the hostid of a Solaris Zone - Julien Gabel

Julien Gabel — Fri, 27 Jul 2012 14:12:03 +0200

Well, thank you for your comment.

As can be seen, this post was written in mid-2006, and this property was not yet available at this time. It was mentioned in a more recent entry though on this same subject in late 2008.

Fake the hostid of a Solaris Zone - Gmann

Gmann — Fri, 27 Jul 2012 14:03:21 +0200

Easiest was to change the host ID for a none global zone is to:

zonecfg -z chrvs042
zonecfg:chrvs042> set hostid=844645ba
zonecfg:chrvs042>exit
zoneadm -z chrvs042 reboot

How to Add a New "tsmsched" Service on AIX 5L - lemmy

lemmy — Thu, 21 Jun 2012 22:44:34 +0200

Yes, this is the way we start TSM since 2003 in AIX - but have you ever tried to get the dsmcad daemon defined as a functional subsystem. It can be defined without problems - but a stopsrc isn't possible ..

mkssys -s tsmcad -p /usr/tivoli/tsm/client/ba/bin64/dsmcad -u 0 -S -n 15 -f
9 -G tcpip -R -o /dev/null -e /dev/null -Q

start is successful:

:/usr/tivoli/tsm/client/ba/bin: startsrc -s tsmcad
0513-059 The tsmcad Subsystem has been started. Subsystem PID is 12189786.

processes running

ps -ef | grep dsm
root 7667928 1 15 09:45:05 - 0:00 /usr/tivoli/tsm/client/ba/bin64/dsmcad
root 11337922 1 0 09:44:52 - 0:00 /usr/tivoli/tsm/client/ba/bin64/dsmcad
root 11796702 1 0 09:44:58 - 0:00 /usr/tivoli/tsm/client/ba/bin64/dsmcad

but stop:

stopsrc -s tsmcad
0513-004 The Subsystem or Group, tsmcad, is currently inoperative.

Discrepancies Between df And du Outputs - slickyboy

slickyboy — Tue, 28 Feb 2012 22:10:26 +0100

Fantastic work around. I've got my space back until I can reboot server at a proper time. Thanks!

Deleting SCSI Device Paths For A Multipath SAN LUN - omar

omar — Sat, 11 Feb 2012 10:13:38 +0100

does the same can be gotten from 'multipath -ll' on centos 5? output example:

mpath1 (360080e500024f5740000028c4f29b94a) dm-0 IBM,1746 FAStT
[size=1.6T][features=3 queue_if_no_path pg_init_retries 50][hwhandler=1 rdac][rw]
\_ round-robin 0 [prio=200][active]
\_ 5:0:0:1 sdb 8:16 [active][ready]
\_ 6:0:0:1 sde 8:64 [active][ready]
\_ round-robin 0 [prio=0][enabled]
\_ 5:0:1:1 sdd 8:48 [active][ghost]
\_ 6:0:1:1 sdg 8:96 [active][ghost]

Oracle Unveils The World’s Fastest General Purpose Engineered System, The SPARC SuperCluster T4-4 - Julien Gabel

Julien Gabel — Tue, 31 Jan 2012 13:48:45 +0100

Well, AFAIK the Fcode utility can only be used to create a hardware RAID array from the OBP. According to the Oracle SPARC T3-2 documentation, it seems that this volumes may be managed through the LSI SAS2 2008 RAID Management Utility for SPARC T3 servers (sas2ircu) or using the RAIDconfig command from the Oracle Hardware Management Pack 2.1.1.

I had to say that I never ever worked with this tools, I tend to prefer some software RAID volumes, using ZFS or SVM.

Oracle Unveils The World’s Fastest General Purpose Engineered System, The SPARC SuperCluster T4-4 - Baban Gaigole

Baban Gaigole — Sun, 29 Jan 2012 04:01:21 +0100

recently i installed a Oracle SPARC T3-2 server with raid1 mirror using FCode Utility. How do i see the mirroring status from os as raidctl is not working. Do i have to take the server down to ok boot prompt every time i want to see the mirror status?

Export and Import a Volume Group... When Things Goes the Wrong Way - Julien Gabel

Julien Gabel — Mon, 21 Nov 2011 11:25:19 +0100

The problematic volume group hasn't to be imported on another system, it was imported on the real (and targeted) system.

Export and Import a Volume Group... When Things Goes the Wrong Way - saji6659

saji6659 — Sun, 20 Nov 2011 17:24:28 +0100

hi,
suppose I need to import the vg to another system, so while exporting the vg, where should I export , I mean need to export to tape drive?

Export and Import a Volume Group... When Things Goes the Wrong Way - Julien Gabel

Julien Gabel — Mon, 24 Oct 2011 10:30:44 +0200

You are right, thank you for commenting. Typos corrected.