ROOTVG - AIX & POWER Portal

Problem with removing a Fiber adapter on VIOserver with MPIO.

Home

Help

Login

Register

	Welcome, Guest. Please login or register.	January 08, 2009, 09:57:47 PM
		Login with username, password and session length

ROOTVG > AIX > Administration > Problem with removing a Fiber adapter on VIOserver with MPIO.

Pages: [1] Go Down

« previous next »

Print

	Author	Topic: Problem with removing a Fiber adapter on VIOserver with MPIO. (Read 210 times)
0 Members and 1 Guest are viewing this topic.

Michael

Administrator
Hero Member

Posts: 539

Re: Problem with removing a Fiber adapter on VIOserver with MPIO.

« Reply #1 on: January 04, 2009, 05:16:06 PM »

Not sure atm about removing fcs1 without reboot.

As you are trying to do this without a reboot I am assuming you have a system that permits a hot swap of adapters. If not, you are going to need to power down anyway to replace the adapter.

In any case I would highly recommend a dual VIO solution (with MPIO in the clients). Then you can easily shutdown one VIO server without needing to shutdown the client LPARs.

afaik - if lspath does not show the fcsX card in any of the paths, the card should be for removal.

Before doing any odmdeletes - make sure you have a copy of the Cu* files, so you can restore the ODM.

If that still fails, use some odmdelete commands to delete the fcs1 from the ODM. You will need to do extra maintenance as well - and thinking, try deleteing any records showing fcs1 as the parent, and then try bringing the device to defined (rmdev without the -d) - if that works, then remove the device completely.

Some disks have the same location code as the fcs1 - do thay have an entry for fcs0 as well, or only for fcs1? If both, use odmdelete to delete the entries that show fcs1 as parent.

Last note: this is not a simple task!

If you have already resolved this - please tell us how you solved it.


	Logged

jesperbidstrup

Registered

Posts: 1

Problem with removing a Fiber adapter on VIOserver with MPIO.

« on: December 20, 2008, 01:43:34 AM »

I have a VIOserver with two Fiber adapters, connected to two IBM 2005-16
SAN switch, and a DS8300 with all the LUN’s.
and a bunch of LPAR using more than 150 disks thru the VIO-server.

Maybe I/we must have “fool-around” with Fiber cables short after the installation, but it have run fine for more than a year. But now the one Fiber adapter is sick.
There was a lot off old “Missing path’s”, but they are removed now.

In the VIOserver I have a defective FC-adapter, I want to remove. (fcs1).
(Is writing in the errlog every second ADAPTER FAILURE)
I have removed all path’es to fscsi1.
I have removed the Fiber cable.
All path’es to the all the hdisk’s is on fscsi0 and working fine!(lspath)

BUT when I try to use hotplug tool to remove the fcs1 adapter I get the messages
“No possible - it is busy.”
I have triyed “rmdev –l fcs1 –R” and “rmdev –l fscsi1”, and get the same error.
When I look on the hdisk’s (lsdev –Ccdisk) can I see that some disks have the same locationcode
as the defective adapter. (and some are sitting on the good one).
Is that the reason to the messages about protocol (fscsi1) is busy ??
Does any buddy know how to fix this situation, without rebooting the VIOserver ?
When I run “fuser –Vxuc /dev/fscsi1”, there are more than 30 process on the entry.

If I power every LPAR down and remove all the hdisk, and run “cfgdev” will the vhost to backing-device mapping go bad?
How can I bee sure that the LUN’s will get the old hdisk number back ?

I hope that some one have some good ideas.

Regard
/Jesper