Adding 2 HBA's to an M5000

I have been asked to add and configure 2 Emulex 10K HBA's into a M5000.
What do I need to do from the SC, OBP and OS side to configure these ?
Thanks

Yes, you are getting there. But you have to decide if you want to extend the range or just making them as clients. See the differences here.
Clients only - simple (requires no change to AEBSn)
http://docs.info.apple.com/article.html?artnum=302153
Extend existing network - more complex (requires changes to AEBSn)
http://docs.info.apple.com/article.html?path=AirPortUtility/5.1/en/ap2045.html
Message was edited by: dchao99

Similar Messages

Anyone added a modem to M4000 / SUN M5000 servers - via xscf or other ?

Hi,
Have any of you lads attempted to add a std analogue modem to an M class server, on older sun boxes the procedure is clear [ dedicated serial port, use tip with standard settings ] But for modern servers, cannot find any documentation on sunsolve or in server manuals etc - everything is for older class boxes where the procedure is clear.
New M class boxes have no serial port, the only option is the RJ 45 serial connector on the xscf console card.
I can connect to the port [ get "connected response from tip ], which is the default local serial console. But cannot get any response from the modem. Tried all sorts of cable combinations. The port is successfully configured for modem dial out. And if i take the modem off a normal terminal console window works fine if i re-enable the console service on the port. I have tried deleting and re-adding the standard ports and their associated port monitor services
Note i am only trying to get a response from basic AT commands not trying to configure PPP or a remote console or anything.
Dying to hear from someone who has done it and configured a modem to respond over this port. I assume this is /dev/term/0 or /dev/tty/a.
Can anyone let me know if i have missed something basic or need a non standard cable
--thanks -gregoire

For those interested, Sun support confirmed it is not possible and suggested it was a bit of a silly request. Though i did state the request was born out of hard core experience, when we completely lost our console and standard networks for 16 hours rendering the xscf card useless

Converting Storedge 3310 RAID unit to act as JBOD?

Hello, I have been struggling with this configuration, any advice is appreciated.
I have 4 x Storedge 3310 RAID units each with it own controller. I have 1 x Linux host and 1 x HBA in the host, with ch0 and ch1. I want to be able access to all 4 Storedge 3310s. Normally if this were 2 x Storedge 3310 RAID + 2 x JBOD then I just connect each RAID unit to a JBOD then each RAID to ch0 and ch1 respectively to the host. Instead what I have is 4 x Storedge 3310 RAID units, is there a way to convert two of the Storedge 3310 unit to make it act exactly like a JBOD? So that I can daisy-chain them to make them all accessible to the host?
Or adding another HBA card to the host is the only option?
thank you.

What is the difference between the host/drive channel? Besides the fact that they are their for connecting to disk drive or to host. Because lets say I connect the first RAID controller to the second one, host-to-host configuration from one RAID to another, will the host see this transparently?
By the way, I tried the JBOD method you mention so basically just connect one of the RAID unit to the other one just as a JBOD and the RAID controller can see the disks on a difference channel but only half of the disk because the RAID I/O actually have internal conneciton to half of the disk, while the other half is jumper.

Adding eSAN storage to a Solaris 9 box, with MPXIO and Qlogic HBAs

I recently added a few SAN drives to a Solaris-9 box and enabled MPXIO. I noticed that after you install the qlc drivers and do a reconfigure boot you see two additional devices besides the disks. These additional devices are very small and present themselves as disks. See example below
12. c5t50060482D5304D88d0 <EMC-SYMMETRIX-5772 cyl 4 alt 2 hd 15 sec 128>
/pci@8,700000/fibre-channel@4,1/fp@0,0/ssd@w50060482d5304d88,0
13. c7t50060482D5304D87d0 <EMC-SYMMETRIX-5772 cyl 4 alt 2 hd 15 sec 128>
/pci@8,700000/fibre-channel@5,1/fp@0,0/ssd@w50060482d5304d87,0
14. c8t60060480000190103862533032384632d0 <EMC-SYMMETRIX-5772 cyl 37178 alt 2 hd 60 sec 128>
/scsi_vhci/ssd@g60060480000190103862533032384632
15. c8t60060480000190103862533032384541d0 <EMC-SYMMETRIX-5772 cyl 37178 alt 2 hd 60 sec 128>
/scsi_vhci/ssd@g60060480000190103862533032384541
notice the difference in the number of cylenders. I have a couple of questions about these devices
1. What are these. The SAN storage is EMC Symmetrix
2. I see the following errors in the /var/adm/messages any time a general disk access command is run, such as format. Should I be concerned
Feb 4 13:05:35 Corrupt label; wrong magic number
Feb 4 13:05:35 scsi: WARNING: /pci@8,700000/fibre-channel@4,1/fp@0,0/ssd@w50060482d5304d88,0 (ssd21):
Feb 4 13:05:35 Corrupt label; wrong magic number
Feb 4 13:05:35 scsi: WARNING: /pci@8,700000/fibre-channel@5,1/fp@0,0/ssd@w50060482d5304d87,0 (ssd28):
Feb 4 13:05:35 Corrupt label; wrong magic number
Feb 4 13:05:35 scsi: WARNING: /pci@8,700000/fibre-channel@5,1/fp@0,0/ssd@w50060482d5304d87,0 (ssd28):
Feb 4 13:05:35 Corrupt label; wrong magic number

Gate keepers from EMC Storage, is normal.

M5000 and Qlogic QLE4062C issues

I am having a problem getting one M5000 server to recognize the Qlogic iSCSI HBAs in PCI slots 3, 4, and 5. We have 2 M5000 servers and one of them is working fine, but the other does not present to Solaris the HBAs. I have done a reconfiguration reboot many times, shut down the domain, rebooted the xscf. The xscf sees the PCI cards on both systems. Is there something I can do to dig deeper as to why Solaris 10 does not see the adapters? Thanks in advance for any insight.
XSCF> showhardconf
SPARC Enterprise M5000;
+ Serial:*************; Operator_Panel_Switch:Locked;
+ Power_Supply_System:Single; SCF-ID:XSCF#0;
+ System_Power:On; System_Phase:Cabinet Power On;
Domain#0 Domain_Status:Running;
MBU_B Status:Normal; Ver:0201h; Serial:************ ;
+ FRU-Part-Number:CF00541-0478 05 /541-0478-05 ;
+ Memory_Size:32 GB;
CPUM#0-CHIP#0 Status:Normal; Ver:0201h; Serial:************;
+ FRU-Part-Number:CA06761-D105 A4 /375-3477-01 ;
+ Freq:2.150 GHz; Type:16;
+ Core:2; Strand:2;
CPUM#0-CHIP#1 Status:Normal; Ver:0201h; Serial:************;
+ FRU-Part-Number:CA06761-D105 A4 /375-3477-01 ;
+ Freq:2.150 GHz; Type:16;
+ Core:2; Strand:2;
CPUM#1-CHIP#0 Status:Normal; Ver:0201h; Serial:************;
+ FRU-Part-Number:CA06761-D105 A4 /375-3477-01 ;
+ Freq:2.150 GHz; Type:16;
+ Core:2; Strand:2;
CPUM#1-CHIP#1 Status:Normal; Ver:0201h; Serial:************;
+ FRU-Part-Number:CA06761-D105 A4 /375-3477-01 ;
+ Freq:2.150 GHz; Type:16;
+ Core:2; Strand:2;
MEMB#0 Status:Normal; Ver:0101h; Serial:**************;
+ FRU-Part-Number:CF00541-0545 05 /541-0545-05 ;
MEM#0A Status:Normal;
+ Code:2c000000000000000836HTF25672PY-667D10100-dc17def7;
+ Type:2B; Size:2 GB;
MEM#0B Status:Normal;
+ Code:2c000000000000000836HTF25672PY-667D10100-dc17dbae;
+ Type:2B; Size:2 GB;
MEM#1A Status:Normal;
+ Code:2c000000000000000836HTF25672PY-667D10100-dc17def4;
+ Type:2B; Size:2 GB;
MEM#1B Status:Normal;
+ Code:2c000000000000000836HTF25672PY-667D10100-dc17def5;
+ Type:2B; Size:2 GB;
MEM#2A Status:Normal;
+ Code:2c000000000000000836HTF25672PY-667D10100-dc17def8;
+ Type:2B; Size:2 GB;
MEM#2B Status:Normal;
+ Code:2c000000000000000836HTF25672PY-667D10100-dc17defa;
+ Type:2B; Size:2 GB;
MEM#3A Status:Normal;
+ Code:2c000000000000000836HTF25672PY-667D10100-dc17defc;
+ Type:2B; Size:2 GB;
MEM#3B Status:Normal;
+ Code:2c000000000000000836HTF25672PY-667D10100-dc17defb;
+ Type:2B; Size:2 GB;
MEMB#1 Status:Normal; Ver:0101h; Serial:*************;
+ FRU-Part-Number:CF00541-0545 05 /541-0545-05 ;
MEM#0A Status:Normal;
+ Code:7f7f7f7f7f5100004572T256220HP3SB 258c-1526ba16;
+ Type:2B; Size:2 GB;
MEM#0B Status:Normal;
+ Code:7f7f7f7f7f5100004572T256220HP3SB 258c-1526ba14;
+ Type:2B; Size:2 GB;
MEM#1A Status:Normal;
+ Code:7f7f7f7f7f5100004572T256220HP3SB 258c-1526ba10;
+ Type:2B; Size:2 GB;
MEM#1B Status:Normal;
+ Code:7f7f7f7f7f5100004572T256220HP3SB 258c-1526ba17;
+ Type:2B; Size:2 GB;
MEM#2A Status:Normal;
+ Code:7f7f7f7f7f5100004572T256220HP3SB 258c-1526c117;
+ Type:2B; Size:2 GB;
MEM#2B Status:Normal;
+ Code:7f7f7f7f7f5100004572T256220HP3SB 258c-1526c014;
+ Type:2B; Size:2 GB;
MEM#3A Status:Normal;
+ Code:7f7f7f7f7f5100004572T256220HP3SB 258c-1526c016;
+ Type:2B; Size:2 GB;
MEM#3B Status:Normal;
+ Code:7f7f7f7f7f5100004572T256220HP3SB 258c-1526e820;
+ Type:2B; Size:2 GB;
DDC_A#0 Status:Normal;
DDC_A#1 Status:Normal;
DDC_A#2 Status:Normal;
DDC_A#3 Status:Normal;
DDC_B#0 Status:Normal;
DDC_B#1 Status:Normal;
IOU#0 Status:Normal; Ver:0101h; Serial:**************;
+ FRU-Part-Number:CF00541-2240 03 /541-2240-03 ;
DDC_A#0 Status:Normal;
DDCR Status:Normal;
DDC_B#0 Status:Normal;
PCI#0 Name_Property:pci; Card_Type:Other;
PCI#1 Name_Property:network; Card_Type:Other;
****PCI#2 Name_Property:pci; Card_Type:Other;_****        This is the first card
****PCI#3 Name_Property:pci; Card_Type:Other;_****        Second
****PCI#4 Name_Property:pci; Card_Type:Other;_****        Third
XSCFU Status:Normal,Active; Ver:0101h; Serial:*************;
+ FRU-Part-Number:CF00541-0481 04 /541-0481-04 ;
OPNL Status:Normal; Ver:0101h; Serial:****************;
+ FRU-Part-Number:CF00541-0850 06 /541-0850-06 ;
PSU#0 Status:Normal; Serial:0017527-0803010468;
+ FRU-Part-Number:CF00300-2011 0150 /300-2011-01-50;
+ Power_Status:On; AC:200 V;
PSU#1 Status:Normal; Serial:0017527-0803010469;
+ FRU-Part-Number:CF00300-2011 0150 /300-2011-01-50;
+ Power_Status:Input fail; AC: - ;
PSU#2 Status:Normal; Serial:0017527-0803010459;
+ FRU-Part-Number:CF00300-2011 0150 /300-2011-01-50;
+ Power_Status:On; AC:200 V;
PSU#3 Status:Normal; Serial:0017527-0803010460;
+ FRU-Part-Number:CF00300-2011 0150 /300-2011-01-50;
+ Power_Status:Input fail; AC: - ;
FANBP_C Status:Normal; Ver:0301h; Serial:**************;
+ FRU-Part-Number:CF00541-0848 05 /541-0848-05 ;
FAN_A#0 Status:Normal;
FAN_A#1 Status:Normal;
FAN_A#2 Status:Normal;
FAN_A#3 Status:Normal;
-dcw-

Here are the command and the responses...I have one box identical to this one with the same setup with the exception of 1 memory board rather than this one that has two. Basically there are 3 Qlogic QLE4062C cards in PCI slot 2, 3, and 4. On the other machine the driver is installed and initialized each port after I did a reboot -- -r like it should. On this one, I cannot get the cards to initialize. I am thinking it is something with the XSCF, but the network cards initialize fine. I did a reset to factory defaults (of the XSCF) this evening, but it did not help (had to spend some time setting things back up). Thanks for an insight.
# cfgadm -a
Ap_Id Type Receptacle Occupant Condition
SB0 System_Brd connected configured ok
SB0::cpu0 cpu connected configured ok
SB0::cpu1 cpu connected configured ok
SB0::cpu2 cpu connected configured ok
SB0::cpu3 cpu connected configured ok
SB0::memory memory connected configured ok
SB0::pci0 io connected configured ok
SB0::pci1 io connected configured ok
SB0::pci2 io connected configured ok
SB0::pci3 io connected configured ok
SB0::pci8 io connected configured ok
SB1 disconnected unconfigured unknown
SB2 disconnected unconfigured unknown
SB3 disconnected unconfigured unknown
SB4 disconnected unconfigured unknown
SB5 disconnected unconfigured unknown
SB6 disconnected unconfigured unknown
SB7 disconnected unconfigured unknown
SB8 disconnected unconfigured unknown
SB9 disconnected unconfigured unknown
SB10 disconnected unconfigured unknown
SB11 disconnected unconfigured unknown
SB12 disconnected unconfigured unknown
SB13 disconnected unconfigured unknown
SB14 disconnected unconfigured unknown
SB15 disconnected unconfigured unknown
c0 scsi-bus connected configured unknown
c0::dsk/c0t0d0 disk connected configured unknown
c0::dsk/c0t1d0 disk connected configured unknown
c0::dsk/c0t3d0 CD-ROM connected configured unknown
iou#0-pci#0 pci-pci/hp connected configured ok
iou#0-pci#1 etherne/hp connected configured ok
iou#0-pci#2 pci-pci/hp connected configured ok
iou#0-pci#3 pci-pci/hp connected configured ok
iou#0-pci#4 pci-pci/hp connected configured ok
px_pci3.pci1 ; unknown empty unconfigured unknown
px_pci5.pci1 ; unknown empty unconfigured unknown
px_pci7.pci1 ; unknown empty unconfigured unknown
# prtdiag
System Configuration: Sun Microsystems sun4u Sun SPARC Enterprise M5000 Server
System clock frequency: 1012 MHz
Memory size: 32768 Megabytes
==================================== CPUs ====================================
CPU CPU Run L2$ CPU CPU
LSB Chip ID MHz MB Impl. Mask
00 0 0, 1, 2, 3 2150 5.0 ; 6 147
00 1 8, 9, 10, 11 2150 5.0 ; 6 147
00 2 16, 17, 18, 19 2150 5.0 ; 6 147
00 3 24, 25, 26, 27 2150 5.0 ; 6 147
============================ Memory Configuration ============================
Memory Available Memory DIMM # of Mirror Interleave
LSB Group Size Status Size DIMMs Mode Factor
00 A 16384MB okay 2048MB 8 no 4-way
00 B 16384MB okay 2048MB 8 no 4-way
========================= IO Cards =========================
LSB Name Model
00 scsi LSI,1064
00 network N/A
00 network N/A
00 network SUNW,pci-x-q
00 network SUNW,pci-x-q
00 network SUNW,pci-x-q
00 network SUNW,pci-x-q
00 network SUNW,pcie-qg
00 network SUNW,pcie-qg
00 network SUNW,pcie-qg
00 network SUNW,pcie-qg
00 ethernet N/A
00 pci1014,36e N/A
00 ethernet N/A
00 pci1014,36e N/A
00 ethernet N/A
00 pci1014,36e N/A
00 ethernet N/A
00 pci1014,36e N/A
00 ethernet N/A
00 pci1014,36e N/A
00 ethernet N/A
00 pci1014,36e N/A
==================== Hardware Revisions ====================
System PROM revisions:
OBP 4.24.10 2008/08/12 19:52
=================== Environmental Status ===================

Unable to regenerate /dev/rmt/0 drivers with cfgadm -c configure on Solaris 10 update 11 (1/13). How does one do this for SAS HBA StorageTek Autoloader?

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.

LUN has gone AWOL - Solaris 10 x86, Emulex HBAs, IBM DS8300

We're setting up a test environment for our backup software, currently running on Windows, but targeted for Solaris. This is also a test of our first Solaris x86 deployment.
* HP DL580 G5 server.
* Solaris 10 x86 10/08 w/patch cluster from ~March 18th.
* One dual port Emulex HBA
* IBM DS8300 SAN
When we first set this up, we could see the one LUN in format. After adding in the IBM Multipathing software, the LUN disappeared and the FC devices are shown as unconfigured in `cfgadm -al`. We removed the IBM multipathing software, but still cannot see the LUN. Did a reconfiguration reboot and all that.
Current state:
# cfgadm -al c6
Ap_Id                          Type         Receptacle   Occupant     Condition
c6                             fc-fabric    connected    unconfigured unknown
c6::5005076306130287           unknown      connected    unconfigured unknown
# luxadm -e port
/devices/pci@0,0/pci8086,3607@4/pci10b5,8533@0/pci10b5,8533@a/pci10df,fe00@0/fp@0,0:devctl CONNECTED
/devices/pci@0,0/pci8086,3607@4/pci10b5,8533@0/pci10b5,8533@a/pci10df,fe00@0,1/fp@0,0:devctl NOT CONNECTED
# luxadm -e dump_map /devices/pci@0,0/pci8086,3607@4/pci10b5,8533@0/pci10b5,8533@a/pci10df,fe00@0/fp@0,0:devctl
Pos Port_ID Hard_Addr Port WWN         Node WWN         Type
0    a0200   0        5005076306130287 5005076306ffc287 0x1f (Unknown Type)
1    a0100   0        10000000c97a7866 20000000c97a7866 0x1f (Unknown Type,Host Bus Adapter)
# modinfo|grep FC
102 ffffffffefc2c000 1aab0 190   1 fp (SunFC Port v20090205-1.79)
103 ffffffffefc47000 199f0 194   1 fcp (SunFC FCP v20090205-1.132)
104 ffffffffefc63000   a2a0   -   1 fctl (SunFC Transport v20090205-1.59)
107 ffffffffefc6c000 377bc0 191   1 emlxs (SunFC emlxs FCA v20081211-2.31p)
189 ffffffffefb547e0   9620 193   1 fcip (SunFC FCIP v20090205-1.50)
190 ffffffffefb49dc0   5610 196   1 fcsm (Sun FC SAN Management v20070116)
#c6 is the first port on the dual port card. c7, not shown, is the second port. Prior to installing the IBM multipathing software, we were seeing the one assigned LUN on c6.
Trying to `cfgadm -c c6` does nothing. Adding `-f` causes an error:
# cfgadm -c configure c6
# cfgadm -al c6
Ap_Id                          Type         Receptacle   Occupant     Condition
c6                             fc-fabric    connected    unconfigured unknown
c6::5005076306130287           unknown      connected    unconfigured unknown
# cfgadm -f -c configure c6
cfgadm: Library error: failed to create device node: 5005076306130287: Invalid argument
failed to configure ANY device on FCA port
# cfgadm -al c6
Ap_Id                          Type         Receptacle   Occupant     Condition
c6                             fc-fabric    connected    unconfigured unknown
c6::5005076306130287           unknown      connected    unconfigured unknown
#We're currently at a loss here. Any pointers would be greatly appreciated. I am checking sunsolve and google, with plenty of similar hits, but no resolution as yet.
Thanks,
Mark

Ok, so after that detailed message, my SAN admin just realised he hadn't assigned any LUNs to the server. :D
The LUN that we had seen previously was an artifact from an earlier configuration.

Whole root zone and fibre channel hba

I have Solaris 10 x86 loaded up on an IBM blade. I've created a whole root zone on it and have installed Symantec NetBackup 6.5.5 and configured it as Media Server. I have an SL8500 tape library in the environment and all the tape drives are fibre channel. Now, in the global zone, I can run fcinfo hba-port or scli and the global zone finds the hba's with no problem. I've added the /dev/cfg/c1 and /dev/cfg/c2 devices to the zone, but running the commands, it cannot find the hba's at all.
Is there something else that I need to do so that the zone can see the hba's, or is this just not possible in a zone?
Thanks in advance,
Ed Coates

Hi.
Check release notes for Netbackup. As i know Media Server is supported anly at Global zones.
You can add access to /dev/rmt/* and give access to tapes, but stiil problem with robot device and this configuration not supported.
Regards.

How to setup NPIV as Cisco9124 directly linked a Emulex HBA N-port

I had a cisco9124 switch and enabled npiv on the switch.
also I had a HBA card, and setup a N-port.
I can find the N-port pwwn number on the cisco9124,
and setup the virtual pwwn to my vsan1.
my question is:
my configuration is correct? can let 9124 directly linked a HBA N-port as NPIV configuration? I think something is wrong. I am no NPV device.
how can let the virtual ports know which actual port manage the virtual ports.
I mean for example:
my fc1/8 port is with 4 virtual ports, how to setup the 4 virtual ports to fc1/8,
or just donot care the fc1/8, just found all the virtual ports and setup the virtual ports luns, then my emulex HBA card will find the luns?
BRs

we use Qlogic 4G 2-port HBA and use RHEL5 OS on DellT105
we are in RHEL5 created 4 virtual ports on one port of HBA.
then we can find the 4 virtual pwwn on our MDS9124, then I added the pwwn on our vsan and reactivated.
then created 4 luns, each lun assigned to each virtual port separately, finally I checked our RHEL5, only found 1 lun is correct. found 2 luns lost and 1 luns allocated to 2 virtual HBA.
configuration like the following on our switch:
vsan 1 wwn 21:01:00:1b:32:a9:f0:04 fcid 0x2e1435 dynamic
vsan 1 wwn 21:01:00:1b:32:a9:f0:05 fcid 0x2e1436 dynamic
vsan 1 wwn 21:01:00:1b:32:a9:f0:06 fcid 0x2e1439 dynamic
vsan 1 wwn 21:01:00:1b:32:a9:f0:07 fcid 0x2e143a dynamic
    member pwwn 21:01:00:1b:32:a9:f0:06
    member pwwn 21:01:00:1b:32:a9:f0:07
    member pwwn 21:01:00:1b:32:a9:f0:04
    member pwwn 21:01:00:1b:32:a9:f0:05
zoneset name IBMzoneset2 vsan 1
    member IBMzone2
zoneset activate name IBMzoneset2 vsan 1

Diskinfo -a command not listing the newly added disk

Hi,
I replaced an internal disk on my T4-1 box. After the replacement, I am able to find the disk listed in:
echo | format
cfgadm -al
df -hk (have mounted a file system on this new disk)
But the issue is that I am unable to find the disk getting listed in the diskinfo -a output.
Please suggest what needs to be done.
# cfgadm -al
c9::w5000cca012c4ec8d,0 disk-path connected configured unknown
c10 scsi-sas connected configured unknown
c10::w5000cca012b4d099,0 disk-path connected configured unknown
c10::w5000cca012c99be5,0 disk-path connected unconfigured unknown
c11 scsi-sas connected configured unknown
c11::w5000cca012d20555,0 disk-path connected configured unknown
bash-3.2# echo | format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t5000CCA012B4D098d0 <LSI-MR9261-8i-2.12 cyl 65533 alt 2 hd 287 sec 31> solaris
/scsi_vhci/disk@g5000cca012b4d098
1. c0t5000CCA012C4EC8Cd0 <LSI-MR9261-8i-2.12 cyl 65533 alt 2 hd 287 sec 31> solaris
/scsi_vhci/disk@g5000cca012c4ec8c
2. c0t5000CCA012C9AA14d0 <LSI-MR9261-8i-2.12 cyl 65533 alt 2 hd 287 sec 31> solaris
/scsi_vhci/disk@g5000cca012c9aa14
3. c0t5000CCA012D20554d0 <LSI-MR9261-8i-2.12 cyl 65533 alt 2 hd 287 sec 31> solaris
/scsi_vhci/disk@g5000cca012d20554
4. c0t60080E50002499E60000039B504D627Fd0 <SUN-LCSM100_S-0780 cyl 38398 alt 2 hd 256 sec 64>
/scsi_vhci/disk@g60080e50002499e60000039b504d627f
5. c0t60080E50002499E60000039E504D62ABd0 <SUN-LCSM100_S-0780 cyl 38398 alt 2 hd 256 sec 64>
/scsi_vhci/disk@g60080e50002499e60000039e504d62ab
6. c1t50080E52499E6000d31 <SUN-UniversalXport-0777 cyl 8 alt 2 hd 64 sec 64>
/pci@400/pci@1/pci@0/pci@8/LSI,sas@0/iport@f/disk@w50080e52499e6000,1f
7. c3t50080E5249EC8000d31 <SUN-UniversalXport-0777 cyl 8 alt 2 hd 64 sec 64>
/pci@400/pci@2/pci@0/pci@8/LSI,sas@0/iport@f/disk@w50080e5249ec8000,1f
Specify disk (enter its number): Specify disk (enter its number):
bash-3.2#
bash-3.2# diskinfo -a
Enclosure path: 1203BD02DA-physical-hba-1
Chassis Serial Number: 1203BD02DA-physical-hba-1
Chassis Model: ORCL,Netra-SPARC-T4-1
Label Disk name Vendor Product Vers
/SYS/HDD0 c0t5000CCA012C9AA14d0 HITACHI H106030SDSUN300G A2B0
/SYS/HDD1 c0t5000CCA012C4EC8Cd0 HITACHI H106030SDSUN300G A2B0
/SYS/HDD3 c0t5000CCA012D20554d0 HITACHI H106030SDSUN300G A2B0
bash-3.2#
Seems like the issue will get resolved if I can remove the old entry of the disk in the cfgadm -al output.
But in our setup we can not use the luxadm command to make the disk unused.
So please suggest any alternative way to remove the extra entry (old disk's):
# cfgadm -la | grep “c10::”
c10::w5000cca012b4d099,0 disk-path connected configured unknown
c10::w5000cca012c99be5,0 disk-path connected unconfigured unknown
After reboot:
Output after reboot:
# cfgadm -al | grep “c10::”
c10::w5000cca012b4d099,0 disk-path connected configured unknown
Edited by: 951222 on Oct 23, 2012 4:57 AM

Please note that the diskinfo command was added to Solaris 10U10 to provide the disk location, but due to bug 7093855 it only displays disks from the first controller. This will be corrected in S10U11.
From Document 1365089.1 (How to locate a failed internal disk drive on a T3/T4 series system)

I/O error when adding quorum device

Hi all, i'm in the process of building a two-node 3.2 Sun cluster using two HP DL380 servers. I seem to have managed to get the sun cluster 3.2 s/w installed on both nodes but i'm having problems adding a quorum device.
Using either scsetup or clquorum, i get the following error:
# /usr/cluster/bin/clquorum add d4
clquorum: (C192716) I/O error.
Does anyone know what this means?
Thanks in advance,
Stewart
******** Here are my devices ***********
# /usr/cluster/bin/cldevice list -v
DID Device Full Device Path
d1 nfst1:/dev/rdsk/c1t0d0
d2 nfst1:/dev/rdsk/c3t0d0
d3 nfst1:/dev/rdsk/c2t5006016A106023E0d4
d3 nfst1:/dev/rdsk/c2t50060162106023E0d4
d3 nfst2:/dev/rdsk/c2t50060160106023E0d4
d3 nfst2:/dev/rdsk/c2t50060168106023E0d4
d4 nfst1:/dev/rdsk/c2t5006016A106023E0d3
d4 nfst1:/dev/rdsk/c2t50060162106023E0d3
d4 nfst2:/dev/rdsk/c2t50060160106023E0d3
d4 nfst2:/dev/rdsk/c2t50060168106023E0d3
d5 nfst1:/dev/rdsk/c2t5006016A106023E0d2
d5 nfst1:/dev/rdsk/c2t50060162106023E0d2
d5 nfst2:/dev/rdsk/c2t50060160106023E0d2
d5 nfst2:/dev/rdsk/c2t50060168106023E0d2
d6 nfst1:/dev/rdsk/c2t5006016A106023E0d1
d6 nfst1:/dev/rdsk/c2t50060162106023E0d1
d6 nfst2:/dev/rdsk/c2t50060160106023E0d1
d6 nfst2:/dev/rdsk/c2t50060168106023E0d1
d7 nfst1:/dev/rdsk/c2t5006016A106023E0d0
d7 nfst1:/dev/rdsk/c2t50060162106023E0d0
d7 nfst2:/dev/rdsk/c2t50060160106023E0d0
d7 nfst2:/dev/rdsk/c2t50060168106023E0d0
d8 nfst1:/dev/rdsk/c2t5006016A1060235Dd3
d8 nfst1:/dev/rdsk/c2t500601621060235Dd3
d8 nfst2:/dev/rdsk/c2t500601681060235Dd3
d8 nfst2:/dev/rdsk/c2t500601601060235Dd3
d9 nfst1:/dev/rdsk/c2t5006016A1060235Dd2
d9 nfst1:/dev/rdsk/c2t500601621060235Dd2
d9 nfst2:/dev/rdsk/c2t500601681060235Dd2
d9 nfst2:/dev/rdsk/c2t500601601060235Dd2
d10 nfst1:/dev/rdsk/c2t5006016A1060235Dd1
d10 nfst1:/dev/rdsk/c2t500601621060235Dd1
d10 nfst2:/dev/rdsk/c2t500601681060235Dd1
d10 nfst2:/dev/rdsk/c2t500601601060235Dd1
d11 nfst1:/dev/rdsk/c2t5006016A1060235Dd0
d11 nfst1:/dev/rdsk/c2t500601621060235Dd0
d11 nfst2:/dev/rdsk/c2t500601681060235Dd0
d11 nfst2:/dev/rdsk/c2t500601601060235Dd0
d12 nfst1:/dev/rdsk/c2t5006016830220BA0d0
d12 nfst1:/dev/rdsk/c2t5006016130220BA0d0
d12 nfst2:/dev/rdsk/c2t5006016930220BA0d0
d12 nfst2:/dev/rdsk/c2t5006016030220BA0d0
d13 nfst2:/dev/rdsk/c1t0d0
d14 nfst2:/dev/rdsk/c3t0d0
Cluster DID Devices ===
Device Instance Node Status
/dev/did/rdsk/d10 nfst1 Ok
nfst2 Ok
/dev/did/rdsk/d11 nfst1 Ok
nfst2 Ok
/dev/did/rdsk/d12 nfst1 Ok
nfst2 Ok
/dev/did/rdsk/d14 nfst2 Ok
/dev/did/rdsk/d2 nfst1 Ok
/dev/did/rdsk/d3 nfst1 Ok
nfst2 Ok
/dev/did/rdsk/d4 nfst1 Ok
nfst2 Ok
/dev/did/rdsk/d5 nfst1 Ok
nfst2 Ok
/dev/did/rdsk/d6 nfst1 Ok
nfst2 Ok
/dev/did/rdsk/d7 nfst1 Ok
nfst2 Ok
/dev/did/rdsk/d8 nfst1 Ok
nfst2 Ok
/dev/did/rdsk/d9 nfst1 Ok
nfst2 Ok

Hi All,
I have a very similar problem, maybe someone has seen it ?
I'm trying to finish installation of Sun Solaris 3.2 on two Sun-Fire-V240s (HBAs are QLogic QLA2342) over SPARC Solaris 10.
When I get to the stage of adding a quorum disk to Sun Cluster 3.2:
# scconf -a -q globaldev=d24
the following error is received:
scconf: Failed to add quorum device (d24) - unable to scrub the device.
I ran the commands:
# scdidadm -r
# scdidadm -i
# scdidadm -L
Where the d24 is as follows:
# scdidadm -L
24 SRV-00-003:/dev/rdsk/c5t128d41 /dev/did/rdsk/d24
24 SRV-00-049:/dev/rdsk/c5t128d41 /dev/did/rdsk/d24
# ls -ls /dev/did/rdsk/d24
2 lrwxrwxrwx 2 root root 42 Apr 7 13:40 /dev/did/rdsk/d24 -> ../../../devices/pseudo/did@24:24,24s7,raw
Format describes the disk as:
Current Disk = c5t128d40
<StoreAge-rbarak_vol40_clu-#12 cyl 98 alt 2 hd 4 sec 512>
/pseudo/vhba@0/vsd@80,28
I Googled the net, and beside references to disks bigger than 1 GB, I couldn't find any relevant suggestions.
Anyone has any experience with this "unable to scrub the device" error ?
Thanks,
Ron.

M5000 Question

Hi i 've a M5000 running 2 domains in my Lab with following hardconf
Code:
SPARC Enterprise M5000; Memory_Size:128 GB;
FRU     Quantity
MBU_B     1
CPUM     2
Freq:2.150 GHz;     ( 4)
MEMB     8
MEM     64
Type:2B; Size:2 GB;     ( 64)
DDC_A     4
DDC_B     2
IOU     2
DDC_A     2
DDCR     2
DDC_B     2
XSCFU     1
OPNL     1
PSU     4
FANBP_C     1
FAN_A     4
-----------------------------------------------+
Now i want to partition the 2nd domain further to create a 3rd domain with equal resources on both 2nd and 3rd. For that i set the XSB to quad mode and created the 3rd domin. But now the 3rd domain does not have any network interface and no HDD and the 2nd domain has been deprived of HBA cards. Is it possible to move one HBA card from 3rd to second domain and one network interface from 2nd to 3rd domain ?
Let me know if i some needs more info on this.
Code:
XSCF> showboards -a
XSB DID(LSB) Assignment Pwr Conn Conf Test Fault
00-0 00(00) Assigned y y y Passed Normal
01-0 01(01) Assigned y y y Passed Normal
01-1 02(00) Assigned y n n Passed Normal
01-2 SP Unavailable y n n Unmount Normal
01-3 SP Unavailable y n n Unmount Normal
XSCF>
And if i try to assign the XSB to the domain 2 or domain 1 it gives me following error
XSCF> addboard -c assign -d 01 01-2 01-3
XSB#01-2 will be assigned to DomainID 1. Continue?y :y
XSB#01-2 is not installed.

Ahhh.
The days of the old supportforum.sum.com ...
When such a stupid response to your question would just be summarily deleted !
No polite warning to them, their post would just magically disappear.
dumbfilter at gmail's response #1 is from some web bot,
trolling to lure you into responding,
then spamming you with a sales pitch for their filter material products.
Don't be gullible. Ignore them.
@min_2,
I don't know where your filters need to be installed,
but simply suggest you use the warranty of your system
and open a support case with Sun directly.
h5. [How to contact Sun for support.|http://www.sun.com/contact/index.jsp|How to contact Sun for support.]

Adding storage to an Xserve

Hey folks,
We're thinking about buying an Xserve, in preparation for Final Cut Server.
However, we're wondering about adding storage.
I've heard that it's possible to connect an external RAID system through fiber to the Xserve, and have it manage the remote filesystem. I can build a 12TB Windows / Linux RAID5 box for about $6k. Can the Xserve manage this? If so, how does it work?
Thanks!
~Misfit

Details on the Xserve RAID are available here:
http://www.apple.com/xserve/raid/
All the RAID is done on the controllers that come in the Xserve RAID. Configuration is done via a Java application called RAID Admin, which accesses it through a couple management ports (over Ethernet).
You need a fibre channel card (a.k.a. HBA) to connect the Xserve RAID to a system -- so you get one for $500 and put it in a Mac Pro, connect up the Xserve RAID (not all that unlike a super duper Firewire 800 connection) and you're good to go, with read speeds in the 300+ MB/sec range and writes in the 200 MB/sec range (so ~4x the theoretical max of Firewire 800, but about 5-10x the actual speed you'd get from typical FW 800 external solutions).

Error while adding A/P Credit Memo!

Error while adding A/P Credit Memo..........
'G/L Accounts' (OACT) (ODBC-2028) Message - 131-183
Please advice me .....
Thanks...

Hi
Check this thread this may help you.
[Re: AP Invoice - No Matching Account Error]
Regards
Balaji

Added new field to cube but data not passed from DSO

Hope someone can help.
(BI 7.0) We added new fields into a cube. The fields already existed in the DSO. When we ran the process chain in development for the first time after making this change, we notice that the 'historical' data for these fields is populated in the cube. When we do this in our quality system only new data passed to the cube is updated. In development in the sub-chain DTP request we see all previous requests listed under selections. In quality it is only the latest request. The only difference is that the DeltaInit flag in the DTP request in development is ticked (extraction mode) - but not in quality. Does anyone know whyb this is?

hi peter,
Adding fields to cube doesn't affect delta status...The delta DTP should be able to handle delta requests automatically.
I guess in you quality system, the cube already got all requests updated from ODS before you importing the change request. And in develop system none of the requests in ODS were updated before the change.
Regards,
Frank

Adding 2 HBA's to an M5000

Similar Messages

Maybe you are looking for