HPE EVA Storage
1846983 Members
4037 Online
110257 Solutions
New Discussion

Re: Fiber Channel configuration

 
Adrian.Aldea
New Member

Fiber Channel configuration

Posted some messages on sun forums, but no answers as far, so as I see some posts that could be related to my problem, well, I’ll give it a try.



I’ll explain my problem; I have a StorEdgeA5000 connected to an Enterprise 4500 via FC.

Solaris 5.10 installed.



Everything went just fine until I tried to configure the multipathing to the StorEdge. I followed instructions in document 819-0139 Solaris Fiber Channel and Storage Multipathing Admin, I then the problems begin.

Obviously, I have the library that assumes multipathing



# mpathadm list mpath-support

mpath-support: libmpscsi_vhci.so



but I don’t have any other initiator port as required for multipathing configuration



# mpathadm list initiator-port

Initiator Port: iqn.1986-03.com.sun:01:080020e11688.461b8e2f,4000002a00ff

#



So my cfgamd command is not listing any fiber channel either



# cfgadm

Ap_Id Type Receptacle Occupant Condition

ac0:bank0 memory connected configured ok

ac0:bank1 memory empty unconfigured unknown

ac1:bank0 memory connected configured ok

ac1:bank1 memory empty unconfigured unknown

c0 scsi-bus connected configured unknown

c8 scsi-bus connected unconfigured unknown

sysctrl0:slot0 cpu/mem connected configured ok

sysctrl0:slot1 soc+sbus connected configured ok

sysctrl0:slot2 cpu/mem connected configured ok

sysctrl0:slot3 soc+sbus connected configured ok

sysctrl0:slot4 unknown empty unconfigured unknown

sysctrl0:slot5 unknown empty unconfigured unusable

sysctrl0:slot6 unknown empty unconfigured unknown

sysctrl0:slot7 unknown empty unconfigured unusable

#

1 REPLY 1
Adrian.Aldea
New Member

Re: Fiber Channel configuration

And

# cfgadm -lao show_SCSI_LUN
cfgadm: Configuration administration not supported
#

Iâ m lost â ¦ especially still the luxadm show me the storedge

# luxadm -e port
/devices/sbus@2,0/SUNW,socal@d,10000:0 NOT CONNECTED
/devices/sbus@2,0/SUNW,socal@d,10000:1 NOT CONNECTED
/devices/sbus@3,0/SUNW,socal@0,0:0 CONNECTED
/devices/sbus@3,0/SUNW,socal@0,0:1 NOT CONNECTED
/devices/sbus@6,0/SUNW,socal@d,10000:0 NOT CONNECTED
/devices/sbus@6,0/SUNW,socal@d,10000:1 NOT CONNECTED
/devices/sbus@7,0/SUNW,socal@0,0:0 CONNECTED
/devices/sbus@7,0/SUNW,socal@0,0:1 NOT CONNECTED
#

# luxadm probe -p
Found Enclosure(s):
SENA Name:SUN01A Node WWN:508002000006ad50
Logical Path:/dev/es/ses0
Physical Path:/devices/sbus@3,0/SUNW,socal@0,0/sf@0,0/ses@w508002000006ad53,0:0
Logical Path:/dev/es/ses1
Physical Path:/devices/sbus@7,0/SUNW,socal@0,0/sf@0,0/ses@w508002000006ad52,0:0
Logical Path:/dev/es/ses2
Physical Path:/devices/sbus@7,0/SUNW,socal@0,0/sf@0,0/ses@w508002000006ad51,0:0
Logical Path:/dev/es/ses3
Physical Path:/devices/sbus@3,0/SUNW,socal@0,0/sf@0,0/ses@w508002000006ad54,0:0
#

When Iâ m using the format command I can see all 14 FC disks in the enclosure on both paths

# format
Searching for disks...done

AVAILABLE DISK SELECTIONS:
0. c0t2d0
/sbus@3,0/SUNW,fas@3,8800000/sd@2,0
1. c0t3d0
/sbus@3,0/SUNW,fas@3,8800000/sd@3,0
2. c1t32d0
/sbus@3,0/SUNW,socal@0,0/sf@0,0/ssd@w22000020372015a3,0
3. c1t33d0
/sbus@3,0/SUNW,socal@0,0/sf@0,0/ssd@w22000020372002c3,0
4. c1t34d0
/sbus@3,0/SUNW,socal@0,0/sf@0,0/ssd@w2200002037200e1a,0
5. c1t35d0
/sbus@3,0/SUNW,socal@0,0/sf@0,0/ssd@w220000203720032e,0
6. c1t36d0
/sbus@3,0/SUNW,socal@0,0/sf@0,0/ssd@w2200002037511147,0
7. c1t37d0
/sbus@3,0/SUNW,socal@0,0/sf@0,0/ssd@w22000020372014db,0
8. c1t38d0
/sbus@3,0/SUNW,socal@0,0/sf@0,0/ssd@w2200002037201783,0
9. c1t48d0
/sbus@3,0/SUNW,socal@0,0/sf@0,0/ssd@w2200002037200353,0
10. c1t49d0
/sbus@3,0/SUNW,socal@0,0/sf@0,0/ssd@w2200002037201aa6,0
11. c1t50d0
/sbus@3,0/SUNW,socal@0,0/sf@0,0/ssd@w22000020372012e1,0
12. c1t51d0
/sbus@3,0/SUNW,socal@0,0/sf@0,0/ssd@w2200002037175c88,0
13. c1t52d0
/sbus@3,0/SUNW,socal@0,0/sf@0,0/ssd@w220000203717f4c9,0
14. c1t53d0
/sbus@3,0/SUNW,socal@0,0/sf@0,0/ssd@w2200002037200d73,0
15. c1t54d0
/sbus@3,0/SUNW,socal@0,0/sf@0,0/ssd@w220000203717fec5,0
16. c2t32d0
/sbus@7,0/SUNW,socal@0,0/sf@0,0/ssd@w21000020372015a3,0
17. c2t33d0
/sbus@7,0/SUNW,socal@0,0/sf@0,0/ssd@w21000020372002c3,0
18. c2t34d0
/sbus@7,0/SUNW,socal@0,0/sf@0,0/ssd@w2100002037200e1a,0
19. c2t35d0
/sbus@7,0/SUNW,socal@0,0/sf@0,0/ssd@w210000203720032e,0
20. c2t36d0
/sbus@7,0/SUNW,socal@0,0/sf@0,0/ssd@w2100002037511147,0
21. c2t37d0
/sbus@7,0/SUNW,socal@0,0/sf@0,0/ssd@w21000020372014db,0
22. c2t38d0
/sbus@7,0/SUNW,socal@0,0/sf@0,0/ssd@w2100002037201783,0
23. c2t48d0
/sbus@7,0/SUNW,socal@0,0/sf@0,0/ssd@w2100002037200353,0
24. c2t49d0
/sbus@7,0/SUNW,socal@0,0/sf@0,0/ssd@w2100002037201aa6,0
25. c2t50d0
/sbus@7,0/SUNW,socal@0,0/sf@0,0/ssd@w21000020372012e1,0
26. c2t51d0
/sbus@7,0/SUNW,socal@0,0/sf@0,0/ssd@w2100002037175c88,0
27. c2t52d0
/sbus@7,0/SUNW,socal@0,0/sf@0,0/ssd@w210000203717f4c9,0
28. c2t53d0
/sbus@7,0/SUNW,socal@0,0/sf@0,0/ssd@w2100002037200d73,0
29. c2t54d0
/sbus@7,0/SUNW,socal@0,0/sf@0,0/ssd@w210000203717fec5,0
Specify disk (enter its number):

I donâ t really now where to start, could you help me on this? Maybe itâ s a driver problem?