Hello all,
Let me introduce about the context and my environment.
We have an AIX 6.1 system, it has 4 FC channels
- 2 virtual FC fcs0, fcs2 comes from VIOS_A --> mapped to the only 1 physical FC
- 2 virtual FC fcs1, fcs3 comes from VIOS_B --> mapped to the only 1 physical FC
--> We can say we have 2 physical FC path.
There is a chance that I reboot the machine, and it cannot boot up. It said that the boot partition is not found. In the SMS mode, I have checked and found that the fcs2 is failed, and fcs3 is partially worked
First action, I have asked the storage guy to remove the fcs3 WWPN from the mapping, try to detect the boot device, then asked again to remove fcs2 WWPN, the both case didn't help.
Second action, I asked the storage guy to map back the fcs2 & fcs3 WWPN back to the machine. Try to detect and get the positive results. Now fcs3 can see all the LUN and detect the boot device.
At the end I can boot up the AIX machine back to normal.
Check further with multipath to verify fcs2, found that the LUN are missing on fcs2. This is matched with fcs2 is failed from the beginning.
So my concern here is:
I repeat:
With the first action, the fcs2 & fcs3 were removed. We still have fcs0 & fcs1 (mapped to 2 different physical FCs) can see the LUN, but not see the bootable partition.
With the second action, fcs2 & fcs3 were re-added, this action makes fcs3 refreshed and see the LUN with bootable partition.
Why in the first action, the LUN & boot partition is not detected? we still have the full visibility to the LUN.
Why in the second action, we can see the LUN and boot partition?
As I know, FC card has 2 ports. if 1 port failed, the rest can continue to work. Please correct me if I'm wrong.
Here in reality, we have 2 physical FCs with 1 port failure per each, and still not boot the server until 1 port failure come up again.
Please advise.
Let me introduce about the context and my environment.
We have an AIX 6.1 system, it has 4 FC channels
Code:
[root@xxx] / > lsdev -Cc adapter | grep fcs
fcs0 Available 23-T1 Virtual Fibre Channel Client Adapter
fcs1 Available 23-T1 Virtual Fibre Channel Client Adapter
fcs2 Available 23-T1 Virtual Fibre Channel Client Adapter
fcs3 Available 23-T1 Virtual Fibre Channel Client Adapter- 2 virtual FC fcs1, fcs3 comes from VIOS_B --> mapped to the only 1 physical FC
--> We can say we have 2 physical FC path.
There is a chance that I reboot the machine, and it cannot boot up. It said that the boot partition is not found. In the SMS mode, I have checked and found that the fcs2 is failed, and fcs3 is partially worked
Code:
WorldWidePortName: c050760941350104
1. 202700a0b86e87a4,0 0 MB Disk drive - reserved
2. 202700a0b86e87a4,1000000000000 107 GB Disk drive
3. 202700a0b86e87a4,2000000000000 0 MB Disk drive - reserved
4. 202700a0b86e87a4,3000000000000 0 MB Disk drive - reserved
5. 202700a0b86e87a4,4000000000000 0 MB Disk drive - reserved
6. 202700a0b86e87a4,5000000000000 0 MB Disk drive - reserved
7. 202700a0b86e87a4,6000000000000 0 MB Disk drive - reserved
8. 202700a0b86e87a4,7000000000000 0 MB Disk drive - reserved
9. 202700a0b86e87a4,8000000000000 107 GB Disk drive
10. 202700a0b86e87a4,9000000000000 107 GB Disk drive
11. 202700a0b86e87a4,a000000000000 107 GB Disk drive
12. 202700a0b86e87a4,b000000000000 0 MB Disk drive - reservedSecond action, I asked the storage guy to map back the fcs2 & fcs3 WWPN back to the machine. Try to detect and get the positive results. Now fcs3 can see all the LUN and detect the boot device.
Code:
Select Attached Device
Pathname: /vdevice/vfc-client@300001a7
WorldWidePortName: c050760941350104
1. 202700a0b86e87a4,0 107 GB Disk drive - bootable
2. 202700a0b86e87a4,1000000000000 107 GB Disk drive
3. 202700a0b86e87a4,2000000000000 107 GB Disk drive
4. 202700a0b86e87a4,3000000000000 107 GB Disk drive
5. 202700a0b86e87a4,4000000000000 107 GB Disk drive
6. 202700a0b86e87a4,5000000000000 107 GB Disk drive
7. 202700a0b86e87a4,6000000000000 107 GB Disk drive
8. 202700a0b86e87a4,7000000000000 107 GB Disk drive
9. 202700a0b86e87a4,8000000000000 107 GB Disk drive
10. 202700a0b86e87a4,9000000000000 107 GB Disk drive
11. 202700a0b86e87a4,a000000000000 107 GB Disk drive
12. 202700a0b86e87a4,b000000000000 107 GB Disk driveCheck further with multipath to verify fcs2, found that the LUN are missing on fcs2. This is matched with fcs2 is failed from the beginning.
Code:
Enabled hdisk7 fscsi1
Enabled hdisk8 fscsi1
Enabled hdisk9 fscsi1
Enabled hdisk10 fscsi1
Enabled hdisk11 fscsi1
Enabled hdisk12 fscsi1
Missing hdisk2 fscsi2
Missing hdisk3 fscsi2
Missing hdisk4 fscsi2
Missing hdisk5 fscsi2
Missing hdisk6 fscsi2
Missing hdisk7 fscsi2
Missing hdisk8 fscsi2I repeat:
Code:
- 2 virtual FC fcs0, fcs2 comes from VIOS_A --> mapped to the only 1 physical FC
- 2 virtual FC fcs1, fcs3 comes from VIOS_B --> mapped to the only 1 physical FCWith the second action, fcs2 & fcs3 were re-added, this action makes fcs3 refreshed and see the LUN with bootable partition.
Why in the first action, the LUN & boot partition is not detected? we still have the full visibility to the LUN.
Why in the second action, we can see the LUN and boot partition?
As I know, FC card has 2 ports. if 1 port failed, the rest can continue to work. Please correct me if I'm wrong.
Here in reality, we have 2 physical FCs with 1 port failure per each, and still not boot the server until 1 port failure come up again.
Please advise.