Cfgadm on Solaris 10
I have been using the Sun SAN software for a while on Solaris 9. Everytime we added storage to our Solaris 9 servers, we just used 'cfgadm -c configure <ctrlr>' to bring in the new storage and cfgadm created the /dev entries. After that, it was a matter of running format and labeling the disks. No reboots were necessary.
On Solaris 10, with the SAN software built-in, however, I'm getting different behavior.
cfgadm no longer works the same. I must do a reconfiguration reboot to get the storage array to see my new server, and after it is zoned and LUNs are mapped, I am able to do a cfgadm as above and it "sees" the LUNs. However, I must now do a 'devfsadm' to get the /dev entries to be able to run format and do something with the storage.
What gives? A bug? I'm using Solaris 10 3/05 with 2 Sun single port Fibre-channel HBAs on the server.
This has been resolved. Getting the /etc/driver_aliases set correctly: # update_drv -d -i st; update_drv -d -i sgen; add_drv -m '* 0600 root sys' -i '"scsiclass,01" "scsiclass,08" wa' worked. Making sure the st and sgen entries are in /etc/name_to_major were needed. For the Simpana/CommVault WA drivers, in opt/simpana/WA/wa.conf with the name="wa" parent="fp" target=16 lun=0 fc-port-wwn="device's World Wide Number> added for each lun 0 to 7. Then the touch /reconfigure; reboot worked. First the c1::rmt/0 tape and c1::scsi/changer/<wwn> med-changer were mapped. After modifying the minor_perm ('* 0600 root sys') and name_to_major entries, the WA CommValt entries , WA drivers showed up in cfgadm -al as c1::wa0 tape and c1::wa1 med-changer, only recognizable from CommVault. Also had to update the SAS-2 HBA StoregTek Autoloader driver with patch 145648-05. Solaris 10 update 11 (1/13) comes with 145648-03. In our particular case, we found cfgadm -al mapped SAS-2 HBA to c1 using the single mini-sas 6gb connector cable, where it mapped to c7 with the four tail connector.
Similar Messages
-
How does one regenerate the /dev/rmt/0 when cfgadm -c configure <device> will not rebuild it? Have attempted reboot -- -r, with modifing /kernel/drv/st.conf as well as /kernel/drv/sgen.conf. Running on a SPARC T4-1 Solaris 10 updat3 11, (1/13).
This has been resolved. Getting the /etc/driver_aliases set correctly: # update_drv -d -i st; update_drv -d -i sgen; add_drv -m '* 0600 root sys' -i '"scsiclass,01" "scsiclass,08" wa' worked. Making sure the st and sgen entries are in /etc/name_to_major were needed. For the Simpana/CommVault WA drivers, in opt/simpana/WA/wa.conf with the name="wa" parent="fp" target=16 lun=0 fc-port-wwn="device's World Wide Number> added for each lun 0 to 7. Then the touch /reconfigure; reboot worked. First the c1::rmt/0 tape and c1::scsi/changer/<wwn> med-changer were mapped. After modifying the minor_perm ('* 0600 root sys') and name_to_major entries, the WA CommValt entries , WA drivers showed up in cfgadm -al as c1::wa0 tape and c1::wa1 med-changer, only recognizable from CommVault. Also had to update the SAS-2 HBA StoregTek Autoloader driver with patch 145648-05. Solaris 10 update 11 (1/13) comes with 145648-03. In our particular case, we found cfgadm -al mapped SAS-2 HBA to c1 using the single mini-sas 6gb connector cable, where it mapped to c7 with the four tail connector.
-
Solaris 10connectivity to EMC: failed to configure ANY device on FCA port
I'm connecting a E2900 server with a EMC symmetrix storage with fiber channel.
But I'm getting the following errors, and I'm not able to see the external disks. Any help is really appreciated.
bash-3.00# cfgadm -al
c3 fc-fabric connected unconfigured unknown
c3::5006048c52a5b746 unavailable connected unconfigured failed
c4 fc-fabric connected unconfigured unknown
c4::5006048c52a5b749 unavailable connected unconfigured failed
bash-3.00# cfgadm -c configure c3
cfgadm: Library error: report LUNs failed: 5006048c52a5b746
failed to configure ANY device on FCA port
bash-3.00# tail -f /var/adm/messages
Nov 27 16:42:12 cosemm1 scsi: [ID 243001 kern.warning] WARNING: /pseudo/fcp@0 (fcp0):
Nov 27 16:42:12 cosemm1 Unsupported LUN Addressing method 40 in response to REPORT_LUN
bash-3.00#
SO is Solaris 10 and I have installed recommended pathes:
118833-36 SunOS 5.10: Kernel patch
125100-10 SunOS 5.10: Kernel patch
120011-14 SunOS 5.10: Kernel patch
127111-01 SunOS 5.10: Kernel patch
119130-33 SunOS 5.10: Sun Fibre Channel Device Drivers (only necessary for Leadville Stack driver)
125184-04 SunOS 5.10: Sun Fibre Channel Device Drivers.
120222-21 SunOS 5.10: Emulex-Sun LightPulse fibre channel adapter driver v2.20k (only required for Emulex HBAs running Leadville)
125166-06 SunOS 5.10: Qlogic ISP fibre channel device driver v2.22 (only required for Qlogic HBAs running Leadville)
122640-05 SunOS 5.10: zfs genesis patch (require for zfs)
120473-12 SunOS 5.10: lib nss ldap PAM zfs patch (require for zfs)
119090-24 SunOS 5.10: iSCSI device driver and utilities
Also I have modified /etc/system adding those lines:
set ssd:ssd_max_throttle=20
forceload: drv/ssd
bash-3.00# modinfo |grep qlc
66 7ba7e000 ce1f8 282 1 qlc (SunFC Qlogic FCA v20070717-2.22)
bash-3.00# luxadm -e port
/devices/ssm@0,0/pci@18,600000/SUNW,qlc@1/fp@0,0:devctl CONNECTED
/devices/ssm@0,0/pci@19,600000/SUNW,qlc@2/fp@0,0:devctl CONNECTED
bash-3.00# luxadm qlgc
Found Path to 2 FC100/P, ISP2200, ISP23xx Devices
Opening Device: /devices/ssm@0,0/pci@19,600000/SUNW,qlc@2/fp@0,0:devctl
Detected FCode Version: QLA2460 Host Adapter FCode(SPARC): 1.26 05/17/07
Opening Device: /devices/ssm@0,0/pci@18,600000/SUNW,qlc@1/fp@0,0:devctl
Detected FCode Version: QLA2460 Host Adapter FCode(SPARC): 1.26 05/17/07
Complete
bash-3.00# luxadm -e port
/devices/ssm@0,0/pci@18,600000/SUNW,qlc@1/fp@0,0:devctl CONNECTED
/devices/ssm@0,0/pci@19,600000/SUNW,qlc@2/fp@0,0:devctl CONNECTED
bash-3.00# luxadm -e dump_map /devices/ssm@0,0/pci@18,600000/SUNW,qlc@1/fp@0,0:
devctl
Pos Port_ID Hard_Addr Port WWN Node WWN Type
0 610f13 0 5006048c52a5b746 5006048c52a5b746 0x0 (Disk device)
1 617613 0 2100001b320122b7 2000001b320122b7 0x1f (Unknown Type,Host Bus Adapter)
bash-3.00# luxadm -e dump_map /devices/ssm@0,0/pci@19,600000/SUNW,qlc@2/fp@0,0:
devctl
Pos Port_ID Hard_Addr Port WWN Node WWN Type
0 620f13 0 5006048c52a5b749 5006048c52a5b749 0x0 (Disk device)
1 627613 0 2100001b32014eb8 2000001b32014eb8 0x1f (Unknown Type,Host Bus Adapter)Check the configuration on the EMC side. This error message is the heart of the problem:
"Unsupported LUN Addressing method 40 in response to REPORT_LUN"
A quick Googling leads me to believe this means you're trying to assign a LUN ID higher than 255 to the host.
Best of luck! -
Metainit/striping problem on Solaris 9
We are trying to deploy the Apple XServe RAIDS to customers running Solaris 9. The issue is that Solaris 9 will not recognize a device/LUN that is > 2TB. (No problem with Solaris 10) In trying to solve this problem, we sliced a 7 disk (4.09 TB) RAID into 3 slices. This presents three 1.36TB disks to the Solaris system. Basically, we have 6 disks being presented across both controllers to Solaris. They are direct connected from the XServe to a dual port QLogic HBA. The problem comes in when you try to create a stripe/concatenation across the logical devices being presented. (The disks are being presented on C4 and C5)
Results from a format AFTER I split both 7 disk RAID5s into 3 slices.
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@1c,600000/scsi@2/sd@0,0
1. c1t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@1c,600000/scsi@2/sd@1,0
2. c1t2d0 <SEAGATE-ST373307LSUN72G-0507 cyl 14087 alt 2 hd 24 sec 424>
/pci@1c,600000/scsi@2/sd@2,0
3. c1t3d0 <SEAGATE-ST373307LSUN72G-0507 cyl 14087 alt 2 hd 24 sec 424>
/pci@1c,600000/scsi@2/sd@3,0
4. c4t600039300001F461d0 <APPLE Xserve RAID 1.51 aea84000>
/pci@1e,600000/SUNW,qlc@3/fp@0,0/ssd@w600039300001f461,0
5. c4t600039300001F461d1 <APPLE Xserve RAID 1.51 aea84000>
/pci@1e,600000/SUNW,qlc@3/fp@0,0/ssd@w600039300001f461,1
6. c4t600039300001F461d2 <APPLE Xserve RAID 1.51 aea84000>
/pci@1e,600000/SUNW,qlc@3/fp@0,0/ssd@w600039300001f461,2
7. c5t600039300001F2ECd0 <APPLE Xserve RAID 1.51 aea84000>
/pci@1e,600000/SUNW,qlc@3,1/fp@0,0/ssd@w600039300001f2ec,0
8. c5t600039300001F2ECd1 <APPLE Xserve RAID 1.51 aea84000>
/pci@1e,600000/SUNW,qlc@3,1/fp@0,0/ssd@w600039300001f2ec,1
9. c5t600039300001F2ECd2 <APPLE Xserve RAID 1.51 aea84000>
/pci@1e,600000/SUNW,qlc@3,1/fp@0,0/ssd@w600039300001f2ec,2
Specify disk (enter its number):
Results of the cfgadm command. You will see there three logical devices presented to each controller. Six disks.
cfgadm -al -o showFCPdev
Ap_Id Type Receptacle Occupant Condition
c4 fc-private connected configured unknown
c4::600039300001f461,0 disk connected configured unknown
c4::600039300001f461,1 disk connected configured unknown
c4::600039300001f461,2 disk connected configured unknown
c5 fc-private connected configured unknown
c5::600039300001f2ec,0 disk connected configured unknown
c5::600039300001f2ec,1 disk connected configured unknown
c5::600039300001f2ec,2 disk connected configured unknown
Trying to initialize a 6 device stripe via Solaris Volume Manager (AKA disksuite)
metainit -f d77 6 1 c4t600039300001F461d0s0 1 c4t600039300001F461d1s0 1 c4t600039300001F461d2s0 1 c5t600039300001F2ECd0s0 1 c5t600039300001F2ECd1s0 1 c5t600039300001F2ECd2s0
I receive the following error:
metainit: hostname: c4t600039300001F461d1s0: overlaps with device in d77
I tried to do a work around where I create three striped devices then concatenate them:
Creating the first 2 device stripe across controllers c4 and c5 (1 device each)
metainit -f d77 2 1 c4t600039300001F461d0s0 1 c5t600039300001F2ECd0s0
I was able to create the first metadevice d77 using one logical LUN from each controller.
When I tried to create a second metadevice across the controllers: (Using d1 from each controller)
metainit -f d78 2 1 c4t600039300001F461d1s0 1 c5t600039300001F2ECd1s0
metainit: hostneme: c4t600039300001F461d1s0: overlaps with device in d77
I received the same error.
In doing some reaearch, it seems the problem is due to a problem with the disk duplication process, disk device IDs stored on the disks are not unique. I was curious if this is the problem that Apple presents the split disks with the SAME diskid? Has anybody else successfully created stripes (due to a LUN size limit) across the disk successfully on a Solaris system?I contacted Sun and here is an explination from them. I also noticed when I queried the Xserver RAIDS, there were no serial numbers.
Solaris 9 can support a 16Tb filesystem, but there is a scsi limitation on the device of 2Tb. So you are stuck with striping together several smaller devices if you want a single filesystem above 2Tb.
The problem you are having when metainit reports an overlap comes from the way Solaris Volume Manager identifies devices. The portion of the scsi inquiry that is returned is always unique when Sun firmware is involved, but in your case is not unique.
You may be able to make use of the appended infodoc to avoid this problem. I see no evidence of our having tested this with your particular scenario, but it has been successful in similar cases.
You might also inquire of whoever supports your storage device whether a mode is supported whereby the device's inquiry strings can be made unique.
Here is the steps he wanted me to take and the results. I still can not get the Xserve RAIDS to generate a unique device id:
Step 1
Determine the vendor and product strings. You can run these commands:
# netstat -k | grep -i vendor
# netstat -k | grep -i product
netstat -k | grep -i vendor
Soft Errors 2 Hard Errors 0 Transport Errors 0 Vendor APPLE
Soft Errors 2 Hard Errors 0 Transport Errors 0 Vendor APPLE
Soft Errors 2 Hard Errors 0 Transport Errors 0 Vendor APPLE
Soft Errors 2 Hard Errors 0 Transport Errors 0 Vendor APPLE
Soft Errors 2 Hard Errors 0 Transport Errors 0 Vendor APPLE
grep -i product
Product Xserve RAID Revision Revision 1.51 Serial No Size 1500294152192 Media Error 0 Device Not Ready 0
Product Xserve RAID Revision Revision 1.51 Serial No Size 1500294152192 Media Error 0 Device Not Ready 0
Product Xserve RAID Revision Revision 1.51 Serial No Size 1500294152192 Media Error 0 Device Not Ready 0
Product Xserve RAID Revision Revision 1.51 Serial No Size 1500294152192 Media Error 0 Device Not Ready 0
Product Xserve RAID Revision Revision 1.51 Serial No Size 1500294152192 Media Error 0 Device Not Ready 0
or you can run
# format -e
then select scsi, then inquiry.
scsi> inq
Inquiry:
00 00 05 12 5b 00 00 02 41 50 50 4c 45 20 20 20 ....[...APPLE
58 73 65 72 76 65 20 52 41 49 44 20 20 20 20 20 Xserve RAID
31 2e 35 31 63 00 00 00 00 00 00 00 00 00 00 00 1.51c...........
00 00 00 00 00 00 00 00 00 00 0d 40 0d a0 0e 20 ...........@...
0d 80 09 00 0a 00 00 20 00 00 00 20 20 20 20 20 ....... ...
20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
Vendor: APPLE
Product: Xserve RAID
Revision: 1.51
Removable media: no
Device type: 0
ISO version: 0
ECMA version: 0
ANSI version: 5
Async event notification: no
Terminate i/o process msg: no
Response data format: 2
Additional length: 91
Relative addressing: no
32 bit transfers: no
16 bit transfers: no
Synchronous transfers: no
Linked commands: no
Command queueing: yes
Soft reset option: no
Step 2
Add an entry in the file '/kernel/drv/sd.conf'.
sd-config-list=
"APPLE Xserve RAID ", "AppleRAID";
AppleRAID=1,0x8,0,0,0,0,0;
Step 3 Reboot.
Step 4 Check with SUNWexplo.
[email protected]:[/opt/SUNWexplo/bin] (8)# ./diskinfo.sparc
/dev/rdsk/c0t0d0s2: Device busy
AVAILABLE SCSI DEVICES:
Location Vendor Product Rev Serial #
c1t0d0 COMPAQ BD036863AC HPB5 B2FT4HMM
c1t1d0 SEAGATE ST336607LSUN36G 0507 0349A66VKQ
c1t2d0 SEAGATE ST373307LSUN72G 0507 0417B7C9ZC
c1t3d0 SEAGATE ST373307LSUN72G 0507 0425B7LV5Q
c4t600039300001F461d0 APPLE Xserve RAID 151 c
c4t600039300001F461d1 APPLE Xserve RAID 151 c
c4t600039300001F461d2 APPLE Xserve RAID 151 c
c5t600039300001F2ECd0 APPLE Xserve RAID 151 c
c5t600039300001F2ECd1 APPLE Xserve RAID 151 c
As you will notice, there are no serial numbers in this command or netstat -k | grep -i product commands. -
Unable to configure LUN in Solaris 10 (T3-1)
Hi everyone,
While trying to configure a LUN on Solaris 10u9, I'm running into a problem getting it configured and available in 'format'. These are the things I tried:
-bash-3.00# cfgadm -o show_FCP_dev -al c5
Ap_Id Type Receptacle Occupant Condition
c5 fc-fabric connected configured unknown
c5::200400a0b819d8c0,0 disk connected configured unknown
c5::201400a0b8481acc,0 disk connected configured unknown
c5::202500a0b8481acc,0 disk connected configured unknown
c5::20340080e52e4bc4 disk connected unconfigured unknown
c5::20350080e52e4bc4 disk connected unconfigured unknown
And if I try to configure it:
-bash-3.00# cfgadm -c configure c5::20340080e52e4bc4
cfgadm: Library error: failed to create device node: 20340080e52e4bc4: Invalid argument
Does anyone have an idea how to fix this?Apparently it was a faulty configuration on the SAN side, the issue was fixed and now I can see the LUN in Solaris without problems.
-
Usb masse storage in solaris 10 problem !!
Hi all
i have srss 3.0 with solaris10-GA, all work well but the usb masse storage
does' nt recognize by srss3.0 are there solution for that problem.
or patch for srss 3.0.
thanks teamCongratulations on your choice of Os ;-)
To solve this problem you can try and create a directory called /rmdisk , then start vold running:
/etc/init.d/volmgt stop
/etc/init.d/volmgt start
if you are lucky your USB flash will show up under /rmdisk/<name> after a few seconds.
If not you should be able to see the flash with cfgadm, which list the status of USB ports (among other things).
Solaris should automatically create a /dev/dsk/ and /dev/rdsk/ entries for your flash memory, if its not automatically mounted by vold, try and stop vold using
/etc/init.d/volmgt stop
Then do a cd /dev/dsk and run an ls -lart, the USB devices should be among the last devices in that list, then mount it using:
mount -F pcfs /dev/dsk/<device> /some/directory
the device should end with s2 or p2, some flash devices might also need :c, aka /dev/dsk/<device>:c, it depends how its configured.
See man mount_pcfs for more information...
Hope this helps a bit (:
//Magnus -
Mount FAT32 USB flash storage in Solaris 10
Hi guys, girls, and undecided.
I've just upgraded my Winblows XP laptop to dual-boot Solaris 10. I've been trying in vain to get a few things working, the most annoying of which is my USB flash storage disk.
I've tried 'pkill -HUP vold', to no avail
'iostat -En' shows my CDRW/DVD drive, but no USB drive.
Help would be muchly appreciated.Congratulations on your choice of Os ;-)
To solve this problem you can try and create a directory called /rmdisk , then start vold running:
/etc/init.d/volmgt stop
/etc/init.d/volmgt start
if you are lucky your USB flash will show up under /rmdisk/<name> after a few seconds.
If not you should be able to see the flash with cfgadm, which list the status of USB ports (among other things).
Solaris should automatically create a /dev/dsk/ and /dev/rdsk/ entries for your flash memory, if its not automatically mounted by vold, try and stop vold using
/etc/init.d/volmgt stop
Then do a cd /dev/dsk and run an ls -lart, the USB devices should be among the last devices in that list, then mount it using:
mount -F pcfs /dev/dsk/<device> /some/directory
the device should end with s2 or p2, some flash devices might also need :c, aka /dev/dsk/<device>:c, it depends how its configured.
See man mount_pcfs for more information...
Hope this helps a bit (:
//Magnus -
Qla2310f not shown in cfgadm/luxadm (san 4.4.11)
I have a problem, with two qlogic qla2310f HBA�s (not sun branded) that are not detected in luxadm/cfgadm.
The box is a SUN Fire 280R running solaris 8:
SunOS [hostname] 5.8 Generic_117350-27 sun4u sparc SUNW,Sun-Fire-280R
Originally it was connected to an older eva-san(HP) using HP-securepath 3.0d for multipathing.
When changing to a new EVA8000 san, i did the following:
1. Unmounted the san-disks, removed them fra Solstice.
2. deletede them in spmgr (HP Securepath)
3. unpresented the disks
4. unistalled Hp Securepath
5. presented disks from the new san (EVA8000)
6. installed SAN 4.4.11 and required pathces, using the "install_it" script
7. modified /kernel/drv/scsi_vhci.conf to enable mpxio globally and add hp specific Symmetric options for the eva8000 san.
After the reconfiguration reboot, i see the disks - however, i Cant see the two qla2310f in luxadm/cfgadm.
These utillities only see the internal controller, and the two internal disks:
Luxadm shows:
luxadm probe
No Network Array enclosures found in /dev/es
Found Fibre Channel device(s):
Node WWN:20000004cfbff6be Device Type:Disk device
Logical Path:/dev/rdsk/c1t0d0s2
Node WWN:2000000c500739e5 Device Type:Disk device
Logical Path:/dev/rdsk/c1t1d0s2
luxadm fcode_download -p
Found Path to 0 FC/S Cards
Complete
Found Path to 0 FC100/S Cards
Complete
Found Path to 1 FC100/P, ISP2200, ISP23xx Devices
Opening Device: /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:devctl
Detected FCode Version: ISP2200 FC-AL Host Adapter Driver: 1.15 04/03/22
Complete
Found Path to 0 JNI1560 Devices.
Complete
Found Path to 0 Emulex Devices.
Complete
cfgadm shows:
cfgadm -l
Ap_Id Type Receptacle Occupant Condition
c0 scsi-bus connected configured unknown
c1 fc-private connected configured unknown
c2 scsi-bus connected unconfigured unknown
c3 scsi-bus connected unconfigured unknown
c4 scsi-bus connected unconfigured unknown
cfgadm -al
Ap_Id Type Receptacle Occupant Condition
c0 scsi-bus connected configured unknown
c0::dsk/c0t6d0 CD-ROM connected configured unknown
c1 fc-private connected configured unknown
c1::21000004cfbff6be disk connected configured unknown
c1::2100000c500739e5 disk connected configured unknown
c2 scsi-bus connected unconfigured unknown
c3 scsi-bus connected unconfigured unknown
c4 scsi-bus connected unconfigured unknown
Qlogics SANSurfer CLI shows all three adapters:
SANsurfer FC HBA CLI
v1.06.16 Build 57
Device List Menu
HBA Model QLA2300/2310:
1: Port 1 (OS 0): WWPN: 21-00-00-E0-8B-0D-AE-BF Online
HBA Model QLA2300/2310:
2: Port 1 (OS 1): WWPN: 21-00-00-E0-8B-0D-B6-BF Online
HBA Model qlc:
3: Port 1 (OS 0): WWPN: 21-00-00-03-BA-2F-AA-EF Online
4: All HBAs
cat /etc/path_to_inst |grep qla2300
"/pci@8,700000/QLGC,qla@3" 0 "qla2300"
"/pci@8,600000/QLGC,qla@1" 1 "qla2300"
the adapters are recognized at boot as well (and probe-scsi-all sees them as well as the san disks)
Oct 22 19:15:43 [hostname] qla2300: [ID 818750 kern.notice] QLogic Fibre Channel Driver v5.01 Instance: 0
Oct 22 19:15:43 [hostname] qla2300: [ID 572349 kern.notice] hba0: QLogic QLA2300 Fibre Channel Host Adapter fcode version 2.00.05 01/29/03
Oct 22 19:15:50 [hostname] qla2300: [ID 818750 kern.notice] QLogic Fibre Channel Driver v5.01 Instance: 1
Oct 22 19:15:50 [hostname] qla2300: [ID 572349 kern.notice] hba1: QLogic QLA2300 Fibre Channel Host Adapter fcode version 2.00.05 01/29/03
I currently use the disks "directly" without using multipathing:
ls -la /dev/dsk/c5t7d5s6
lrwxrwxrwx 1 root root 46 Oct 22 13:04 /dev/dsk/c5t7d5s6 -> ../../devices/pci@8,700000/QLGC,qla@3/sd@7,5:g
�
I need luxadm/cfgadm to "see" the two qla2310f adapters, in order to use multipathing, any ideas?Same here:
V240 and X4200, QLF2340, Solaris 9 and 10 plus latest 9 recommended patch cluster connectec to McData and HDS.
Seems like a problem with luxadm and cfgadm, as on V480 with QLC2340 all works well...
Any new patches/fixes?
Cheers. -
Couldn't see LUNS fpr Compaq Storage array 1000 solaris box
Hi All,
I want to connect Compaq storage Works SAN array to solaris10 Box. I can see array as connected but state as unusable.
How can i see the luns from the storage on solaris box??
dmesg output:
Feb 1 08:29:54 testappl ndi_devi_online: failed for array-controller: target=11000 lun=0 ffffffff
Feb 1 08:30:25 testappl fctl: [ID 517869 kern.warning] WARNING: fp(7)::PLOGI succeeded: no skip(2) for D_ID 11000
Feb 1 08:30:25 testappl genunix: [ID 599346 kern.warning] WARNING: Page83 data not standards compliant COMPAQ MSA1000 2.38
Feb 1 08:30:25 testappl scsi: [ID 243001 kern.info] /pci@1d,700000/SUNW,emlxs@2/fp@0,0 (fcp7):
Feb 1 08:30:25 testappl ndi_devi_online: failed for array-controller: target=11000 lun=0 ffffffff
Feb 1 08:47:27 testappl emlxs: [ID 349649 kern.info] [ 5.05F8]emlxs3: NOTICE: 730: Link reset.
Feb 1 08:47:27 testappl emlxs: [ID 349649 kern.info] [ 5.0337]emlxs3: NOTICE: 710: Link down.
Feb 1 08:47:30 testappl emlxs: [ID 349649 kern.info] [ 5.054D]emlxs3: NOTICE: 720: Link up. (2Gb, fabric, initiator)
Feb 1 08:47:30 testappl genunix: [ID 599346 kern.warning] WARNING: Page83 data not standards compliant COMPAQ MSA1000 2.38
Feb 1 08:47:30 testappl scsi: [ID 243001 kern.info] /pci@1d,700000/SUNW,emlxs@2/fp@0,0 (fcp7):
Feb 1 08:47:30 testappl ndi_devi_online: failed for array-controller: target=11000 lun=0 ffffffff
cfgadm -al output:
bash-3.00# cfgadm -al
Ap_Id Type Receptacle Occupant Condition
c0 scsi-bus connected configured unknown
c0::dsk/c0t0d0 CD-ROM connected configured unknown
c1 scsi-bus connected configured unknown
c1::dsk/c1t0d0 disk connected configured unknown
c1::dsk/c1t1d0 disk connected configured unknown
c1::dsk/c1t2d0 disk connected configured unknown
c2 fc connected unconfigured unknown
c5 scsi-bus connected unconfigured unknown
c6 fc connected unconfigured unknown
c7 fc-fabric connected configured unknown
c7::500805f3000186d9 array-ctrl connected configured unusable
usb0/1 usb-device connected configured ok
usb0/2 unknown empty unconfigured ok
usb1/1 unknown empty unconfigured ok
usb1/2 unknown empty unconfigured okthanks in advance.Looks like the LUN is not configured correctly on the storage array. The kernel can't take the LUN online.
I have seen this on various boxes, most of the time it was either that the LUN wasn't set online on the SAN box or there is a SCSI reservation on the LUN.
Can you access the LUN from another host? -
Solaris containers and Fiber connection
Hi guys,
I have sucsessfully migrated solaris 8 system to solaris 10 containers. and also mounted some RAID enabled partition on non global zone without any issue. now i need to connect a fiber channel to my host OS (solaris 10) and add the SAN partition to my container (solaris 8). if i run cfgadm command it says cfgadm: Library error: Device library initialize failed: Invalid argument.
there are some other ways to mount the SAN (mount the SAN on host and export the partition to container). but i need the above method . is it possible to mount the SAN partition from the non-global zone ? if so how should i do it .
thanks,
TharangaAs far as i know you can't give the non-global zones the required permissions which is needed to mount a FC LUN directly into the non-global zone.
I think you have to mount the LUN in the global zones, and then loop-back-mount them into the non-global zone.
.7/M. -
Solaris 11.1 ehci bug: usb-printer not anymore recognized
same hardware, same printer:
after upgrading to 11.1 the usb-printer is not detected
cfgadm does not list it, not detected by HAL.
No usb kern.info for the printer in /var/adm/messages
but unplugging USB cable causes ehci error message in /var/adm/messages.
Rollback to 11.0 BE, and printer is there again:
$> cfgadm
Ap_Id Type Receptacle Occupant Condition
sata6/0::dsk/c5t0d0 disk connected configured ok
sata6/1 sata-port empty unconfigured ok
sata6/2 sata-port empty unconfigured ok
sata6/3::dsk/c5t3d0 cd/dvd connected configured ok
sata6/4 sata-port empty unconfigured ok
sata6/5 sata-port empty unconfigured ok
usb2/1 unknown empty unconfigured ok
usb2/2 unknown empty unconfigured ok
usb2/3 unknown empty unconfigured ok
usb2/4 unknown empty unconfigured ok
usb2/5 unknown empty unconfigured ok
usb2/6 unknown empty unconfigured ok
usb3/1 usb-printer connected configured ok
in /var/adm/messages printer shows up again:
Nov 2 23:16:20 mini11 usba: [ID 349649 kern.info] Samsung Electronics Co., Ltd. CLP-310 Series 1434BABS103573Z
Nov 2 23:16:20 mini11 genunix: [ID 936769 kern.info] usbprn1 is /pci@0,0/pci1025,228@2,1/printer@1
Nov 2 23:16:20 mini11 genunix: [ID 408114 kern.info] /pci@0,0/pci1025,228@2,1/printer@1 (usbprn1) online
example hardware: Acer Aspire X3400
Herstellername:Acer
Manufacture model:Aspire X3400
64 Bit:True
OS version:SunOS mini11 5.11 11.0 i86pc i386 i86pc
CPU Type:AMD Athlon(tm) II X2 220 Processor
CPU Number:1
Number Of Cores Per Processor:2
Number Of Threads Per Processor:2
Bios/Firmware Maker:AMI Version:P01-B1 Release Date:04/02/2010
prtconf -pv:
System Configuration: Oracle Corporation i86pc
Memory size: 4096 Megabytes
System Peripherals (PROM Nodes):
Node 0x000001
bios-boot-device: '80'
stdout: 00000000
name: 'i86pc'
Node 0x000002
existing: 00c21000.00000000.029d1001.00000000
name: 'ramdisk'
Node 0x000003
acpi-namespace: '\_SB_.PCI0'
compatible: 'pciex_root_complex'
device_type: 'pciex'
reg: 00000000.00000000.00000000.00000000.00000000
#size-cells: 00000002
#address-cells: 00000003
name: 'pci'
Node 0x000004
reg: 00000000.00000000.00000000.00000000.00000000
compatible: 'pci10de,754.1025.228.a2' + 'pci10de,754.1025.228' + 'pci1025,228' + 'pci10de,754.a2' + 'pci10de,754' + 'pciclass,050000' + 'pciclass,0500'
model: 'Ram'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001025
subsystem-id: 00000228
unit-address: '0'
class-code: 00050000
revision-id: 000000a2
vendor-id: 000010de
device-id: 00000754
name: 'pci1025,228'
Node 0x000005
#size-cells: 00000001
#address-cells: 00000002
ranges: 00000001.00000000.81000000.00000000.00000000.0000004e.00000001.00000050.81000000.00000000.00000050.000000b0.00000001.000004d0.81000000.00000000.000004d0.00000002.00000001.00000800.81000000.00000000.00000800.00000010.00000001.00000a00.81000000.00000000.00000a00.00000040.00000001.00000cf8.81000000.00000000.00000cf8.00000008.00000001.00004000.81000000.00000000.00004000.00000100.00000001.00004400.81000000.00000000.00004400.00000100.00000001.00004800.81000000.00000000.00004800.00000100.00000000.00000000.82000000.00000000.00000000.000a0000.00000000.000c0000.82000000.00000000.000c0000.00010000.00000000.000e0000.82000000.00000000.000e0000.c7f20000.00000000.e0000000.82000000.00000000.e0000000.10000000.00000000.fec00000.82000000.00000000.fec00000.01400000.00000000.fec00000.82000000.00000000.fec00000.00001000.00000000.fed00000.82000000.00000000.fed00000.00001000.00000000.fed04000.82000000.00000000.fed04000.00001000.00000000.fee00000.82000000.00000000.fee00000.00100000
acpi-namespace: '\_SB_.PCI0.SBRG'
device_type: 'isa'
assigned-addresses: 81000810.00000000.00004f00.00000000.00000100
reg: 00000800.00000000.00000000.00000000.00000000.01000810.00000000.00000000.00000000.00000100
compatible: 'pci10de,75c.1025.228.a2' + 'pci10de,75c.1025.228' + 'pci1025,228' + 'pci10de,75c.a2' + 'pci10de,75c' + 'pciclass,060100' + 'pciclass,0601'
model: 'ISA bridge'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001025
subsystem-id: 00000228
unit-address: '1'
class-code: 00060100
revision-id: 000000a2
vendor-id: 000010de
device-id: 0000075c
name: 'isa'
Node 0x000024
unit-address: '1,60'
interrupts: 00000001.0000000c
reg: 00000001.00000060.00000001.00000001.00000064.00000001
name: 'i8042'
Node 0x000025
compatible: 'pnpPNP,303'
device-type: 'keyboard'
interrupts: 00000001.0000000c
reg: 00000000
acpi-namespace: '\_SB_.PCI0.SBRG.PS2K'
model: 'System keyboard'
name: 'keyboard'
Node 0x000026
compatible: 'pnpPNP,f03'
device-type: 'mouse'
reg: 00000001
interrupts: 0000000c
acpi-namespace: '\_SB_.PCI0.SBRG.PS2M'
model: 'Microsoft PS/2-style Mouse'
name: 'mouse'
Node 0x000027
compatible: 'pnpPNP,c01'
reg: 00000000.00000000.000a0000.00000000.000c0000.00010000.00000000.000e0000.00020000.00000000.00100000.c7f00000.00000000.fec00000.01400000
acpi-namespace: '\_SB_.RMEM'
model: 'Motherboard'
name: 'motherboard'
Node 0x000006
acpi-namespace: '\_SB_.PCI0.SMB0'
assigned-addresses: 81000910.00000000.00004900.00000000.00000040.81000920.00000000.00004d00.00000000.00000040.81000924.00000000.00004e00.00000000.00000040
reg: 00000900.00000000.00000000.00000000.00000000.01000910.00000000.00000000.00000000.00000040.01000920.00000000.00000000.00000000.00000040.01000924.00000000.00000000.00000000.00000040
compatible: 'pci10de,752.1025.228.a1' + 'pci10de,752.1025.228' + 'pci1025,228' + 'pci10de,752.a1' + 'pci10de,752' + 'pciclass,0c0500' + 'pciclass,0c05'
model: 'SMBus (System Management Bus)'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
interrupts: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001025
subsystem-id: 00000228
unit-address: '1,1'
class-code: 000c0500
revision-id: 000000a1
vendor-id: 000010de
device-id: 00000752
name: 'pci1025,228'
Node 0x000007
reg: 00000a00.00000000.00000000.00000000.00000000
compatible: 'pci10de,751.1025.228.a1' + 'pci10de,751.1025.228' + 'pci1025,228' + 'pci10de,751.a1' + 'pci10de,751' + 'pciclass,050000' + 'pciclass,0500'
model: 'Ram'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001025
subsystem-id: 00000228
unit-address: '1,2'
class-code: 00050000
revision-id: 000000a1
vendor-id: 000010de
device-id: 00000751
name: 'pci1025,228'
Node 0x000008
assigned-addresses: 82000b10.00000000.fce80000.00000000.00080000
reg: 00000b00.00000000.00000000.00000000.00000000.02000b10.00000000.00000000.00000000.00080000
compatible: 'pci10de,753.1025.228.a2' + 'pci10de,753.1025.228' + 'pci1025,228' + 'pci10de,753.a2' + 'pci10de,753' + 'pciclass,0b4000' + 'pciclass,0b40'
model: 'Co-processor'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
interrupts: 00000002
max-latency: 00000001
min-grant: 00000003
subsystem-vendor-id: 00001025
subsystem-id: 00000228
unit-address: '1,3'
class-code: 000b4000
revision-id: 000000a2
vendor-id: 000010de
device-id: 00000753
name: 'pci1025,228'
Node 0x000009
acpi-namespace: '\_SB_.PCI0.IMAP'
reg: 00000c00.00000000.00000000.00000000.00000000
compatible: 'pci10de,568.1025.228.a1' + 'pci10de,568.1025.228' + 'pci1025,228' + 'pci10de,568.a1' + 'pci10de,568' + 'pciclass,050000' + 'pciclass,0500'
model: 'Ram'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001025
subsystem-id: 00000228
unit-address: '1,4'
class-code: 00050000
revision-id: 000000a1
vendor-id: 000010de
device-id: 00000568
name: 'pci1025,228'
Node 0x00000a
acpi-namespace: '\_SB_.PCI0.USB0'
assigned-addresses: 82001010.00000000.fce7f000.00000000.00001000
reg: 00001000.00000000.00000000.00000000.00000000.02001010.00000000.00000000.00000000.00001000
compatible: 'pci10de,77b.1025.228.a1' + 'pci10de,77b.1025.228' + 'pci1025,228' + 'pci10de,77b.a1' + 'pci10de,77b' + 'pciclass,0c0310' + 'pciclass,0c03'
model: 'Universal Serial Bus OHCI compliant'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
interrupts: 00000001
max-latency: 00000001
min-grant: 00000003
subsystem-vendor-id: 00001025
subsystem-id: 00000228
unit-address: '2'
class-code: 000c0310
revision-id: 000000a1
vendor-id: 000010de
device-id: 0000077b
name: 'pci1025,228'
Node 0x00000b
acpi-namespace: '\_SB_.PCI0.USB2'
assigned-addresses: 82001110.00000000.fce7ec00.00000000.00000100
reg: 00001100.00000000.00000000.00000000.00000000.02001110.00000000.00000000.00000000.00000100
compatible: 'pci10de,77c.1025.228.a1' + 'pci10de,77c.1025.228' + 'pci1025,228' + 'pci10de,77c.a1' + 'pci10de,77c' + 'pciclass,0c0320' + 'pciclass,0c03'
model: 'Universal Serial Bus EHCI compliant'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
interrupts: 00000002
max-latency: 00000001
min-grant: 00000003
subsystem-vendor-id: 00001025
subsystem-id: 00000228
unit-address: '2,1'
class-code: 000c0320
revision-id: 000000a1
vendor-id: 000010de
device-id: 0000077c
name: 'pci1025,228'
Node 0x00000c
acpi-namespace: '\_SB_.PCI0.US15'
assigned-addresses: 82002010.00000000.fce7d000.00000000.00001000
reg: 00002000.00000000.00000000.00000000.00000000.02002010.00000000.00000000.00000000.00001000
compatible: 'pci10de,77d.1025.228.a1' + 'pci10de,77d.1025.228' + 'pci1025,228' + 'pci10de,77d.a1' + 'pci10de,77d' + 'pciclass,0c0310' + 'pciclass,0c03'
model: 'Universal Serial Bus OHCI compliant'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
interrupts: 00000001
max-latency: 00000001
min-grant: 00000003
subsystem-vendor-id: 00001025
subsystem-id: 00000228
unit-address: '4'
class-code: 000c0310
revision-id: 000000a1
vendor-id: 000010de
device-id: 0000077d
name: 'pci1025,228'
Node 0x00000d
acpi-namespace: '\_SB_.PCI0.US12'
assigned-addresses: 82002110.00000000.fce7e800.00000000.00000100
reg: 00002100.00000000.00000000.00000000.00000000.02002110.00000000.00000000.00000000.00000100
compatible: 'pci10de,77e.1025.228.a1' + 'pci10de,77e.1025.228' + 'pci1025,228' + 'pci10de,77e.a1' + 'pci10de,77e' + 'pciclass,0c0320' + 'pciclass,0c03'
model: 'Universal Serial Bus EHCI compliant'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
interrupts: 00000002
max-latency: 00000001
min-grant: 00000003
subsystem-vendor-id: 00001025
subsystem-id: 00000228
unit-address: '4,1'
class-code: 000c0320
revision-id: 000000a1
vendor-id: 000010de
device-id: 0000077e
name: 'pci1025,228'
Node 0x00000e
acpi-namespace: '\_SB_.PCI0.IDE0'
#size-cells: 00000000
#address-cells: 00000001
device_type: 'pci-ide'
assigned-addresses: 81003000.00000000.000001f0.00000000.00000008.81003000.00000000.000003f6.00000000.00000001.81003000.00000000.00000170.00000000.00000008.81003000.00000000.00000376.00000000.00000001.81003020.00000000.0000ffa0.00000000.00000010
reg: 00003000.00000000.00000000.00000000.00000000.81003000.00000000.000001f0.00000000.00000008.81003000.00000000.000003f6.00000000.00000001.81003000.00000000.00000170.00000000.00000008.81003000.00000000.00000376.00000000.00000001.01003020.00000000.00000000.00000000.00000010
compatible: 'pci10de,759.1025.228.a1' + 'pci10de,759.1025.228' + 'pci1025,228' + 'pci10de,759.a1' + 'pci10de,759' + 'pciclass,01018a' + 'pciclass,0101'
model: 'IDE controller'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
max-latency: 00000001
min-grant: 00000003
subsystem-vendor-id: 00001025
subsystem-id: 00000228
unit-address: '6'
class-code: 0001018a
revision-id: 000000a1
vendor-id: 000010de
device-id: 00000759
name: 'pci-ide'
Node 0x00000f
reg: 00000000
name: 'ide'
Node 0x000010
reg: 00000001
name: 'ide'
Node 0x000011
acpi-namespace: '\_SB_.PCI0.HDAC'
assigned-addresses: 82003810.00000000.fce78000.00000000.00004000
reg: 00003800.00000000.00000000.00000000.00000000.02003810.00000000.00000000.00000000.00004000
compatible: 'pci10de,774.1025.228.a1' + 'pci10de,774.1025.228' + 'pci1025,228' + 'pci10de,774.a1' + 'pci10de,774' + 'pciclass,040300' + 'pciclass,0403'
model: 'Mixed Mode device'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
interrupts: 00000001
max-latency: 00000005
min-grant: 00000002
subsystem-vendor-id: 00001025
subsystem-id: 00000228
unit-address: '7'
class-code: 00040300
revision-id: 000000a1
vendor-id: 000010de
device-id: 00000774
name: 'pci1025,228'
Node 0x000012
acpi-namespace: '\_SB_.PCI0.P0P1'
slot-names: 00000600.746f6c53.6c530034.0035746f
reg: 00004000.00000000.00000000.00000000.00000000
compatible: 'pci10de,75a.a1' + 'pci10de,75a' + 'pciclass,060401' + 'pciclass,0604'
model: 'Subtractive Decode PCI-PCI bridge'
bus-range: 00000001.00000001
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pci'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
unit-address: '8'
class-code: 00060401
revision-id: 000000a1
vendor-id: 000010de
device-id: 0000075a
name: 'pci10de,75a'
Node 0x000013
acpi-namespace: '\_SB_.PCI0.ATA0'
assigned-addresses: 81004810.00000000.0000d480.00000000.00000008.81004814.00000000.0000d400.00000000.00000004.81004818.00000000.0000d080.00000000.00000008.8100481c.00000000.0000d000.00000000.00000004.81004820.00000000.0000cc00.00000000.00000010.82004824.00000000.fce76000.00000000.00002000
reg: 00004800.00000000.00000000.00000000.00000000.01004810.00000000.00000000.00000000.00000008.01004814.00000000.00000000.00000000.00000004.01004818.00000000.00000000.00000000.00000008.0100481c.00000000.00000000.00000000.00000004.01004820.00000000.00000000.00000000.00000010.02004824.00000000.00000000.00000000.00002000
compatible: 'pci10de,ad4.1025.228.a2' + 'pci10de,ad4.1025.228' + 'pci1025,228' + 'pci10de,ad4.a2' + 'pci10de,ad4' + 'pciclass,010601' + 'pciclass,0106'
model: 'SATA AHCI 1.0 Interface'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
interrupts: 00000001
max-latency: 00000001
min-grant: 00000003
subsystem-vendor-id: 00001025
subsystem-id: 00000228
unit-address: '9'
class-code: 00010601
revision-id: 000000a2
vendor-id: 000010de
device-id: 00000ad4
name: 'pci1025,228'
Node 0x000014
acpi-namespace: '\_SB_.PCI0.NMAC'
assigned-addresses: 82005010.00000000.fce7c000.00000000.00001000.81005014.00000000.0000c880.00000000.00000008.82005018.00000000.fce7e400.00000000.00000100.8200501c.00000000.fce7e000.00000000.00000010
reg: 00005000.00000000.00000000.00000000.00000000.02005010.00000000.00000000.00000000.00001000.01005014.00000000.00000000.00000000.00000008.02005018.00000000.00000000.00000000.00000100.0200501c.00000000.00000000.00000000.00000010
compatible: 'pci10de,760.1025.8000.a2' + 'pci10de,760.1025.8000' + 'pci1025,8000' + 'pci10de,760.a2' + 'pci10de,760' + 'pciclass,020000' + 'pciclass,0200'
model: 'Ethernet controller'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
interrupts: 00000001
max-latency: 00000014
min-grant: 00000001
subsystem-vendor-id: 00001025
subsystem-id: 00008000
unit-address: 'a'
class-code: 00020000
revision-id: 000000a2
vendor-id: 000010de
device-id: 00000760
name: 'pci1025,8000'
Node 0x000015
acpi-namespace: '\_SB_.PCI0.MXR0'
slot-names: 00000001.746f6c53.00003233
reg: 00008000.00000000.00000000.00000000.00000000
compatible: 'pciex10de,778.a1' + 'pciex10de,778' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci10de,778.a1' + 'pci10de,778' + 'pciclass,060400' + 'pciclass,0604'
model: 'PCI-PCI bridge'
ranges: 81000000.00000000.000003b0.81000000.00000000.000003b0.00000000.0000000c.81000000.00000000.000003c0.81000000.00000000.000003c0.00000000.00000020.81000000.00000000.0000e000.81000000.00000000.0000e000.00000000.00001000.82000000.00000000.000a0000.82000000.00000000.000a0000.00000000.00020000.82000000.00000000.fcf00000.82000000.00000000.fcf00000.00000000.01100000.c2000000.00000000.ce000000.c2000000.00000000.ce000000.00000000.12000000
bus-range: 00000002.00000002
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pciex'
power-consumption: 00000001.00000001
physical-slot#: 00000001
devsel-speed: 00000000
interrupts: 00000001
unit-address: '10'
class-code: 00060400
revision-id: 000000a1
vendor-id: 000010de
device-id: 00000778
name: 'pci10de,778'
Node 0x00001d
assigned-addresses: 82020010.00000000.fd000000.00000000.01000000.c3020014.00000000.d0000000.00000000.10000000.c302001c.00000000.ce000000.00000000.02000000.81020024.00000000.0000ec00.00000000.00000080.a1020000.00000000.000003b0.00000000.0000000c.a1020000.00000000.000003c0.00000000.00000020.a2020000.00000000.000a0000.00000000.00020000
reg: 00020000.00000000.00000000.00000000.00000000.02020010.00000000.00000000.00000000.01000000.43020014.00000000.00000000.00000000.10000000.4302001c.00000000.00000000.00000000.02000000.01020024.00000000.00000000.00000000.00000080.a1020000.00000000.000003b0.00000000.0000000c.a1020000.00000000.000003c0.00000000.00000020.a2020000.00000000.000a0000.00000000.00020000
compatible: 'pciex10de,a22.174b.1141.a2' + 'pciex10de,a22.174b.1141' + 'pciex10de,a22.a2' + 'pciex10de,a22' + 'pciexclass,030000' + 'pciexclass,0300' + 'pci10de,a22.174b.1141.a2' + 'pci10de,a22.174b.1141' + 'pci10de,a22.a2' + 'pci10de,a22' + 'pciclass,030000' + 'pciclass,0300'
model: 'VGA compatible controller'
power-consumption: 00000001.00000001
devsel-speed: 00000000
interrupts: 00000001
subsystem-vendor-id: 0000174b
subsystem-id: 00001141
device_type: 'display'
unit-address: '0'
class-code: 00030000
revision-id: 000000a2
vendor-id: 000010de
device-id: 00000a22
name: 'display'
Node 0x00001e
assigned-addresses: 82020110.00000000.fcf7c000.00000000.00004000
reg: 00020100.00000000.00000000.00000000.00000000.02020110.00000000.00000000.00000000.00004000
compatible: 'pciex10de,be2.174b.1141.a1' + 'pciex10de,be2.174b.1141' + 'pciex10de,be2.a1' + 'pciex10de,be2' + 'pciexclass,040300' + 'pciexclass,0403' + 'pci10de,be2.174b.1141.a1' + 'pci10de,be2.174b.1141' + 'pci174b,1141' + 'pci10de,be2.a1' + 'pci10de,be2' + 'pciclass,040300' + 'pciclass,0403'
model: 'Mixed Mode device'
power-consumption: 00000001.00000001
devsel-speed: 00000000
interrupts: 00000001
subsystem-vendor-id: 0000174b
subsystem-id: 00001141
unit-address: '0,1'
class-code: 00040300
revision-id: 000000a1
vendor-id: 000010de
device-id: 00000be2
name: 'pci174b,1141'
Node 0x000016
acpi-namespace: '\_SB_.PCI0.BR12'
slot-names: 00000001.746f6c53.00003433
reg: 00009000.00000000.00000000.00000000.00000000
compatible: 'pciex10de,75b.a1' + 'pciex10de,75b' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci10de,75b.a1' + 'pci10de,75b' + 'pciclass,060400' + 'pciclass,0604'
model: 'PCI-PCI bridge'
bus-range: 00000003.00000003
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pciex'
power-consumption: 00000001.00000001
physical-slot#: 00000003
devsel-speed: 00000000
interrupts: 00000001
unit-address: '12'
class-code: 00060400
revision-id: 000000a1
vendor-id: 000010de
device-id: 0000075b
name: 'pci10de,75b'
Node 0x000017
acpi-namespace: '\_SB_.PCI0.BR13'
slot-names: 00000001.746f6c53.00003533
reg: 00009800.00000000.00000000.00000000.00000000
compatible: 'pciex10de,77a.a1' + 'pciex10de,77a' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci10de,77a.a1' + 'pci10de,77a' + 'pciclass,060400' + 'pciclass,0604'
model: 'PCI-PCI bridge'
bus-range: 00000004.00000004
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pciex'
power-consumption: 00000001.00000001
physical-slot#: 00000004
devsel-speed: 00000000
interrupts: 00000001
unit-address: '13'
class-code: 00060400
revision-id: 000000a1
vendor-id: 000010de
device-id: 0000077a
name: 'pci10de,77a'
Node 0x000018
acpi-namespace: '\_SB_.PCI0.K800'
reg: 0000c000.00000000.00000000.00000000.00000000
compatible: 'pci1022,1200.0' + 'pci1022,1200' + 'pciclass,060000' + 'pciclass,0600'
model: 'Host bridge'
power-consumption: 00000001.00000001
devsel-speed: 00000000
max-latency: 00000000
min-grant: 00000000
unit-address: '18'
class-code: 00060000
revision-id: 00000000
vendor-id: 00001022
device-id: 00001200
name: 'pci1022,1200'
Node 0x000019
reg: 0000c100.00000000.00000000.00000000.00000000
compatible: 'pci1022,1201.0' + 'pci1022,1201' + 'pciclass,060000' + 'pciclass,0600'
model: 'Host bridge'
power-consumption: 00000001.00000001
devsel-speed: 00000000
max-latency: 00000000
min-grant: 00000000
unit-address: '18,1'
class-code: 00060000
revision-id: 00000000
vendor-id: 00001022
device-id: 00001201
name: 'pci1022,1201'
Node 0x00001a
acpi-namespace: '\_SB_.PCI0.K802'
reg: 0000c200.00000000.00000000.00000000.00000000
compatible: 'pci1022,1202.0' + 'pci1022,1202' + 'pciclass,060000' + 'pciclass,0600'
model: 'Host bridge'
power-consumption: 00000001.00000001
devsel-speed: 00000000
max-latency: 00000000
min-grant: 00000000
unit-address: '18,2'
class-code: 00060000
revision-id: 00000000
vendor-id: 00001022
device-id: 00001202
name: 'pci1022,1202'
Node 0x00001b
acpi-namespace: '\_SB_.PCI0.K803'
reg: 0000c300.00000000.00000000.00000000.00000000
compatible: 'pci1022,1203.0' + 'pci1022,1203' + 'pciclass,060000' + 'pciclass,0600'
model: 'Host bridge'
power-consumption: 00000001.00000001
devsel-speed: 00000000
max-latency: 00000000
min-grant: 00000000
unit-address: '18,3'
class-code: 00060000
revision-id: 00000000
vendor-id: 00001022
device-id: 00001203
name: 'pci1022,1203'
Node 0x00001c
reg: 0000c400.00000000.00000000.00000000.00000000
compatible: 'pci1022,1204.0' + 'pci1022,1204' + 'pciclass,060000' + 'pciclass,0600'
model: 'Host bridge'
power-consumption: 00000001.00000001
devsel-speed: 00000000
max-latency: 00000000
min-grant: 00000000
unit-address: '18,4'
class-code: 00060000
revision-id: 00000000
vendor-id: 00001022
device-id: 00001204
name: 'pci1022,1204'
Node 0x00001f
device_type: 'aSo Solaris 11.1 is supposed to support USB 3.0 and I think that may have something to do with it. I have two Gigaware 16GB USB thumb drives that work fine with 11.0 FCS but one of them fails under 11.1. Also not recognized but on occasion I can get /var/adm/messages to log something although most times it has nothing.
So I used a Windows utility to look at both of them and one of them has an older firmware version than the other. The older one doesn't work with 11.1 but the one with the newer firmware runs just fine. Made a nice excuse to upgrade one of them to 32 GB's.
alan -
Hi:
I am from the HP-UX sysadmin world and i would like to Master Solaris Admin. I have about 8 years of experience in hp-ux and have worked briefly on solaris 7 before. Please let me know the answers to the following questions.
1. Am i in the correct form to post this question?
2. What should be the useful docs/url's that i would have to go thru (i went thru thre 2.x FAQ) and looks like those were basic admin stuff. where can i find details for advanced solaris admin details(even if it is a book please mention it to me)
3. Also i found that for SAN Migrations in Solaris, it is very different from HP in the sense that the LUN masking information, WWN, information have to entered in sd.conf and lpfc.conf etc..where can i get more infor about SAN/veritas cluster etc on Solaris?
Best Regards
Saiseldocs.sun.com for solaris related documentation
support.veritas.com for veritas related documentation -- I however doubt very much whether there's any website (outside of veritas) that covers VCS very well.
With the advent of the Leadville driver in Solaris, SAN administration (from the server persepective) has become relatively simple (look up on leadville driver, luxadm, cfgadm and devfsadm).
hth -
Solaris 10 can not boot; disks drive offline
hi, solaris 10 can not boot the operating system has 10 luns and this enabled the multipathing, he settled patches and reboot the computer does not start showing me the following errors:
WARNING: /pci@0/pci@0/pci@8/pci@0/pci@1/SUNW,qlc@0/fp@0,0/ssd@w203400a0b875837d,1f (ssd0): drive offline
WARNING: /pci@0/pci@0/pci@8/pci@0/pci@1/SUNW,qlc@0/fp@0,0/ssd@w203400a0b875837d,1e (ssd3): drive offline
WARNING: /pci@0/pci@0/pci@8/pci@0/pci@1/SUNW,qlc@0/fp@0,0/ssd@w203400a0b875837d,1d (ssd5): drive offline
into failsafe mode and slow 2 days in, I try to see the running operating system disk format and takes the response format and shows me the following errors:
# format
Searching for disks...WARNING: /pci@0/pci@0/pci@8/pci@0/pci@1/SUNW,qlc@0/fp@0,0/ssd@w203400a0b875837d,1f (ssd0): drive offline
WARNING: /pci@0/pci@0/pci@8/pci@0/pci@1/SUNW,qlc@0/fp@0,0/ssd@w203400a0b875837d,1e (ssd3): drive offline
WARNING: /pci@0/pci@0/pci@8/pci@0/pci@1/SUNW,qlc@0/fp@0,0/ssd@w203400a0b875837d,1d (ssd5): drive offline
hba ports have been connected
# luxadm -e port
/devices/pci@0/pci@0/pci@8/pci@0/pci@1/SUNW,qlc@0/fp@0,0:devctl CONNECTED
/devices/pci@0/pci@0/pci@8/pci@0/pci@9/SUNW,qlc@0/fp@0,0:devctl CONNECTED
# cfgadm -al
Ap_Id Type Receptacle Occupant Condition
c2 fc-fabric connected configured unknown
c2::203400a0b875837d disk connected configured unknown
c3 fc-fabric connected configured unknown
c3::202400a0b875837d disk connected configured unknown
cfgadm -al command output c2 and c3 appears has been connected and configured, because luns in the format output informs me that disks have state drive offline?
any idea.Hi--
Can you list the steps that lead this problem, please?
The drive offline message is a symptom of some kind of connection or underlying hardware problem.
If there were no system changes that lead to this problem, then I would look for connection or hardware issues.
Thanks, Cindy -
Solaris 10 does not see new RAM
Hello,
We have Solaris 10 (SunOS solaris 5.10 Generic_142910-17 i86pc i386 i86pc) on Compaq ProLiant ML350 G3 server (yes, that's old).
Originally it had 1024MB of RAM, but recently added 2x512 PC2100 DDR modules. Currently, BIOS counts up to 2 gigs of memory in POST screen, but Solaris seems like ignoring it:
#prtconf -v | grep Memory
Memory size: 1024 Megabytes
Some more info:
#prtdiag
System Configuration: Compaq ProLiant ML350 G3
BIOS Configuration: Compaq D14 09/15/2004
==== Processor Sockets ====================================
Version Location Tag
Intel Xeon Proc 1
==== Memory Device Sockets ================================
Type Status Set Device Locator Bank Locator
DDR in use 1 DIMM 01
DDR in use 1 DIMM 02
DDR empty 2 DIMM 03
DDR empty 2 DIMM 04
==== On-Board Devices =====================================
==== Upgradeable Slots ====================================
ID Status Type Description
1 available PCI-X PCI Slot 1
2 available PCI-X PCI Slot 2
3 available PCI-X PCI Slot 3
4 available PCI-X PCI Slot 4
5 in use PCI PCI Slot 5
So it says that two slots are empty, though in reality they aren't!
Currently (yet) I have no possibility to boot some kind LiveCD to check if, for example, Linux can see the memory - server is at distant office of a client...
What could this mean? Do I have to make Solaris to "refresh" hardware configuration somehow or should I try to reinstall it..?
Thank you!# cfgadm -al
Ap_Id Type Receptacle Occupant Condition
c0 scsi-bus connected configured unknown
c0::dsk/c0t1d0 disk connected configured unknown
c0::dsk/c0t2d0 disk connected configured unknown
c2 scsi-bus connected unconfigured unknown
usb0/1 unknown empty unconfigured ok
usb0/2 unknown empty unconfigured ok
usb0/3 unknown empty unconfigured ok
usb0/4 unknown empty unconfigured ok -
Hi
I'm trying to get this Intel 845 graphic chip to work with Solaris 9.
I've installed The XFree86 porting kit, tried the VESA driver but it still doesn't work.
Had a look att this page, but it didn't help me.
http://www.xfree86.org/~dawes/845driver.html
Any ideas anyone???After two days of hard work and digging the Sun documents site, I found the following:
Execute the code below to re-scan the SCSI bus and identify any changes made in the storages, like adding or removing virtual disks.
cfgadm -al -o show_FCP_dev c#where c# is the controller number allocated for your SAN
bash-3.2# cfgadm -a
Ap_Id Type Receptacle Occupant Condition
c5 fc-fabric connected configured unknown
...Cheers,
Andreas
Maybe you are looking for
-
<p>HI, we are having problems with a report that uses a stored procedure. </p><p>When we run the report and enter the parameters, the report comes back blank. Having a look in the 'Show SQL' box says that Crystal Reports is executing the stored pro
-
Error in writing to file - Oracle
Dear All, We have to upgrade Oracle from 10.2.0.2 to 11.2.0.2. For this we are applying patches till 10.2.0.4. OS is AIX 6.1. Before proceeding I have stopped SAP, DB, Listerner and emctl also. But after starting the patches we found the msg that, Er
-
Changing the column names displayed via an ODBC driver
Hi we are just starting to used Crystal Reports to improve the reporting capabaility of a legacy application, we can access the data fine using an ODBC driver. What we want to do is change the column names that are displayed within Crystal Reports so
-
Stsadm command - enumerate subsites/list/libraries under 1 site collection into a csv file
Hi all Do we have any examples of stsadm commands that I can write to enumerate the subsites/lists/libraries under the sharepoint 2007 site.
-
Can send characters to the standard input while DOS Command is under execution
Can Labview send characters to the standard input while DOS Command is under running with System Exec.vi?