Quote:
Originally Posted by
bakunin
Adapters can be broken because of the power-cycling of the host system. In most cases if an adapter is defective it shows once you power-cycle a system. This is a common effect.
Only a few weeks ago we had a power failure in one of our datacenters (lightning struck and UPS failed come up). When we restarted the complete environment an hour later we had several adapters (and in one case even a sysplanar) failing completely or in parts.
In the end we replaced the sysplanar, two power supplies, 2 FC cards and 1 10G-adapter, distributed over ~20 managed systems (mostly 780s and 740s)
Even if they do soft zoning (based on WWNs) there is a chance that you changed to another part of the fabric when you moved the system. In many cases there are several switches ("clusters") and a zone defined on one doesn't necessarily mean it is defined on any other.
In any case i suggest you also check all the connecting cables. There is always the chance of a FC cable broken.
I hope this helps.
bakunin
Possibility of power cycling the system. Even though this system has been bought brand new less then a year old.
We did change fibre cables as well.
---------- Post updated at 10:01 AM ---------- Previous update was at 09:51 AM ----------
Quote:
Originally Posted by
ibmtech
It almost come down to what x-ray and bakunin has said,
To add more,
Are you not seeing the SAN disks on VIO2 itself or on clients coming from VIO2?
If the answer is latter, I had a personal experience with VIO2, wherein the other SysAdmin just added the virtual fibre dynamically and forget to add it in profile. You may want to run a second pair of eyes over there.
If all is set and you can see those are connected and vfchosts defined, then it could be either faulty FC card or zoning issue.
As an sysadmin you can create virtual adapters and establish a connection between VIO and Client (using NPIV), but how the disk is presented to the system is the task of Storage Admin.
Its very simple, after you have provided WWN's of VIO, there is not much you can do (may be except for pulling the fibre cable from Fabric to Server).
Is error log showing any errors for FC card?
I have VIO2 booting from SAN, so unfortuantely I can not even start the VIO2 unless I see the boot disks, which has come down to, me posting on this forum for help.
As mentioned previously, I'm using vscsi not vfchosts.
You are definitely right, in regards to providing the WWN's and not much I can do, unless the FC is faulty, but without evidence of faulty adapters, I can't move forward and neither can SAN team.
No errors on anything regarding to FC cards.
---------- Post updated at 11:02 AM ---------- Previous update was at 10:01 AM ----------
UPDATE: SAN team have updated me will the following completed on their end
Reseat cable and SFTP on switch and HBA side
Disable and enable ports
Change port speed and disable/enable ports
Xray - you are right, fcstat comes back immediately (I tested on another server.). But that's probably because I have that ports wwn online on the switch. Where this issue, my wwn is not logged online.