Maximum LUNS in solaris 10,9

Hi,
Pl. let me know the maximum number of LUNS that can be added to a solaris 10 and solaris9 OS .
I am using both Qlogic and Emulex fiber card.

user5782900 wrote:
hmmm, its IBM ThinkCentre A50-8175 KAA.
i don't whether the system has the driver for the ethernet or not.If there are no prompts, then the OS has no knowledge of whatever chipset you might have.
You will need to figure that out on your own.
Once you know the actual chipset, you can review the Hardware Compatibility List (HCL)
http://www.sun.com/bigadmin/hcl/
and then determine whether you have to manually install a third party driver for what might be there,
or whether you have to purchase and install another NIC that is+ usable by Solaris.

Similar Messages

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.

How do I map Hitachi SAN LUNs to Solaris 10 and Oracle 10g ASM?

Hi all,
I am working on an Oracle 10g RAC and ASM installation with Sun E6900 servers attached to a Hitachi SAN for shared storage with Sun Solaris 10 as the server OS. We are using Oracle 10g Release 2 (10.2.0.3) RAC clusterware
for the clustering software and raw devices for shared storage and Veritas VxFs 4.1 filesystem.
My question is this:
How do I map the raw devices and LUNs on the Hitachi SAN to Solaris 10 OS and Oracle 10g RAC ASM?
I am aware that with an Oracle 10g RAC and ASM instance, one needs to configure the ASM instance initialization parameter file to set the asm_diskstring setting to recognize the LUNs that are presented to the host.
I know that Sun Solaris 10 uses /dev/rdsk/CwTxDySz naming convention at the OS level for disks. However, how would I map this to Oracle 10g ASM settings?
I cannot find this critical piece of information ANYWHERE!!!!
Thanks for your help!

Yes that is correct however due to use of Solaris 10 MPxIO multipathing software that we are using with the Hitachi SAN it does present an extra layer of complexity and issues with ASM configuration. Which means that ASM may get confused when it attempts to find the new LUNs from the Hitachi SAN at the Solaris OS level. Oracle Metalink note 396015.1 states this issue.
So my question is this: how to configure the ASM instance initialization parameter asm_diskstring to recognize the new Hitachi LUNs presented to the Solaris 10 host?
Lets say that I have the following new LUNs:
/dev/rdsk/c7t1d1s6
/dev/rdsk/c7t1d2s6
/dev/rdsk/c7t1d3s6
/dev/rdsk/c7t1d4s6
Would I set the ASM initialization parameter for asm_diskstring to /dev/rdsk/c7t1d*s6
as correct setting so that the ASM instance recognizes my new Hitachi LUNs? Solaris needs to map these LUNs using pseudo devices in the Solaris OS for ASM to recognize the new disks.
How would I set this up in Solaris 10 with Sun multipathing (MPxIO) and Oracle 10g RAC ASM?
I want to get this right to avoid the dreaded ORA-15072 errors when creating a diskgroup with external redundancy for the Oracle 10g RAC ASM installation process.

Maximum LUN size for Windows 2012 server

Dear All
What is the Maximum size of the LUN that can be provided to windows 2012 server. Earlier it was 2 TB for windows 2008 server has the policy changed or it is still
the same.
Regards
Zubair

Hi,
Would you please let me know if your OS version is Windows Server 2012 or Windows Server 2012 Essentials? If it’s Windows Server 2012, you’d better ask the question in the File Services and
Storage forum. We will get a better assistance there.
File Services and Storage
http://social.technet.microsoft.com/Forums/en-US/winserverfiles/threads
Best Regards,
Andy Qi
Andy Qi
TechNet Community Support

Unable to detect LUNS in solaris 9.

Hi all,
We added HBA card to one of the Solaris 9 server (Sun Fire V240). Configured zoning and presented the LUNs to the server from EVA6100. But LUNs are not visible in OS side. Verified the link, zone config and the Storage config. All looks fine.
Applied all required packages and patches from server level.
Storage Details:
Storage Model: EVA 6100
Server Details:
OS Version: Sun Solaris 9
HBA Model: SG-XPCI2FC-EM4-Z - Sun StorageTek PCI-X Enterprise 4Gb Dual Channel FC Emulex Host Bus Adapter, includes standard and low profile brackets. RoHS 6 compliant
luns are visible in OK prompt but not in OS.
if there are additional parameters i need to know
Regards,
parkar
UAE
Edited by: parkar on Jul 16, 2012 10:23 PM

hi
we are still unable to detect luns in OS.
We have installed the recommended packages/patches from Oracle mentioned below, but still the LUN is not visible. Kindly check and let us know if any other parameters to be configured in Solaris side.
dvsrv19:/export/home/osteam/SAN_Patches/p10297699_440_Generic/SAN_S9_4.4.15_install_it#./install_it
Logfile /var/tmp/install_it_Sun_StorEdge_SAN.log : created on Mon Aug 6 12:31:30 GMT 2012
This routine installs the packages and patches that
make up Sun StorEdge SAN on Solaris 9 (only).
Would you like to continue with the installation?
[y,n,?] y
Verifying system...
Checking for incompatible patches : Done
Begin installation of SAN software
Installing StorEdge SAN packages -
Package SUNWsan : Installed Previously.
Package SUNWcfpl : Installed Previously.
Package SUNWcfplx : Installed Previously.
Package SUNWcfclr : Installed Previously.
Package SUNWcfcl : Installed Previously.
Package SUNWcfclx : Installed Previously.
Package SUNWfchbr : Installed Previously.
Package SUNWfchba : Installed Previously.
Package SUNWfchbx : Installed Previously.
Package SUNWfcsm : Installed Previously.
Package SUNWfcsmx : Installed Previously.
Package SUNWmdiu : Installed Previously.
Package SUNWqlc : Installed Successfully.
Package SUNWqlcx : Installed Successfully.
Package SUNWjfca : Installed Previously.
Package SUNWjfcax : Installed Previously.
Package SUNWjfcau : Installed Previously.
Package SUNWjfcaux : Installed Previously.
Package SUNWemlxs : Installed Previously.
Package SUNWemlxsx : Installed Previously.
Package SUNWemlxu : Installed Previously.
Package SUNWemlxux : Installed Previously.
StorEdge SAN packages installation completed.
Installing StorEdge SAN patches and required patches -
Patch 111847-08 : Installed Successfully.
Patch 113046-01 : Installed Previously.
Patch 113049-01 : Installed Previously.
Patch 113039-21 : Later version installed 113039-25.
Patch 113040-26 : Later version installed 113040-33.
Patch 113041-14 : Installed Previously.
Patch 113042-19 : Installed Successfully.
Patch 113043-15 : Installed Previously.
Patch 113044-07 : Installed Successfully.
Patch 114476-09 : Later version installed 114476-10.
Patch 114477-04 : Installed Successfully.
Patch 114478-08 : Installed Successfully.
Patch 114878-10 : Installed Successfully.
Patch 119914-14 : Later version installed 119914-15.
Patch installation completed.
Installation of Sun StorEdge SAN completed Successfully
Please reboot your system.
dvsrv19:/export/home/osteam/SAN_Patches/p10297699_440_Generic/SAN_S9_4.4.15_install_it#
Regards,

Removing LUNs from Solaris 10

Hi all, I have a 2-node Solaris 10 11/06 cluster running Sun Cluster 3.2. It's shared storage is supplied from an EMC Clariion SAN. Some of the LUNs used by the cluster have recently been replaced. I now have multiple LUNs on this cluster that are no longer needed. But there's a problem.
Last week I added, then removed, a new LUN to the cluster and one of the nodes in the cluster rebooted. Sun Microsystems analysed the problem and identified the reboot as a known issue (Bug ID is 6518348):
On Solaris 10 Systems, any SAN interruptions causing a path to SAN devices to be temporarily offlined may cause the system to panic. The SAN interruption may be due to regular SAN switch and/or array maintenance, or as simple as a fibre cable disconnect.
I need to remove the unused LUNs as the SAN that they live on is being moved.
Is there any way I can safely remove the unused LUNs without causing or requiring server reboots?
Thanks in advance,
Stewart

Hi Stewart,
Usually devfsadm -Cv ( -C = cleanup, v = verbose) does a good job
If it doesn't work, you can use cfgadm -c unconfigure/remove <LUNid>
Ex: cfgadm -c unconfigure c2::50060161106023dd;cfgadm -c remove c2::50060161106023dd
Marco

Maximum # socket descriptors, Solaris 2.5.1?

Hello,
Does anyone know what is the maximum number of socket descriptors that can be opened simultaneously in one process? Where in the system do I check/set that?
Also, what is maximum number of children a process can have and where is that setting?
I am working with Solaris 2.5.1.
Any help is appreciated. Thanks in advance!
-Max

When the keyboard is disconnected...display automatically goes to the serial port. If your keyboard is connected, reboot and make sure you have a video card installed. The onboard one may not have the vsimm(video memory) option, in which case you will have to get memory for it(very, very expensive) or get a separate sbus video card(these can be had very cheap on ebay). Let us know how it works out for you.

Cannot label 6Terabyte lun on solaris 8 host

Hello,
I have a 6 terabyte lun, I cannot label it. I get the following error:
Warning: error writing VTOC.
This is an emcpower device. The os is solaris 8 117350-26.
-- Milo A.

Been there tried that.....Solaris 8 will only support up to 1TB. You must then use software(SVM, SAMFS, Veritas,etc.) to stripe the 1TB LUN together to make your 6TB volume.
It is my understanding that prior to ZFS(Newly released) that Solaris 9 & 10 properly patched with support a LUN up to 2TB.

Multi-terabyte LUNs in Solaris 9 64bit

According to the Solaris Volume Manager documentation, recent versions of Solaris 9 now supports multi-terabyte disks. There are references to the automatic usage of EFI disk labels for LUNs that are larger than 1TB, but no explanation beyond this.
I am planning to set up a large volume for backup2disk on a Sunfire V240. Our SAN vendor (EMC) recommends that we implement this in the form of a striped meta-LUN spanning multiple RAID3 groups, and discourages the use of volume managers to achieve the same striping. Not wanting to deviate from best practice where avoidable I have therefore configured a 1.3 TB (which will become ~3TB once I get this working) on the SAN and presented this to my Solaris box in the form of a single logical unit.
Unfortunately, format does not understand the geometry at all. During probe it reports that nsect is being adjusted from 178 to 128, and in the disk list the new volume is reported as unknown with a negative size. To me this indicates that a counter is being overflowed so that a positive integer becomes a negative.
Also since this is a logical disk I cannot easily determine the real parameters to configure if I were to create my own format.dat - this is not readily available from the management tools provided by EMC (of which I am aware of anyway).
Does anyone of you, fellow admins, know of a way to resolve this problem?
I could do this the harder way and present this in the form of multiple LUNs and chain them together in a single SVM volume but I would be giving up a lot of flexibility and incurring a higher level of complexity which I would rather avoid if possible. And the document from sun clearly states that on a 64bit kernel, Solaris 9 revision 03/04 and later do indeed support single LUN of multiple TBs. Documentation bug?

Okay, classic case of asking then finding the answer yourself here.
Turns out that the documentation is indeed correct, but that a cfgadm -c configure <ctr id> ; devfsadm -C is insufficient for this particular task. Just for the hell of it I did a configuration reboot - lo and behold, my disks went straight up in format with correct geometry and size. Quite possibly there is necessary magic going on during initialization of the ssd driver that doesn't happen during a DR, but there's also the option of me being ignorant ;)
Anyway, I guess other people might benefit from this so here you go; Solaris 9 does indeed support single disks of multi-terabyte sizes, but quite possibly you need to perform a reboot -- -r (or touch /etc/reconfigure and then reboot) before format can understand their geometry.
Cheers!

Maximum LUN size (2TB?) on Mac OS X Server 10.4.9 (Intel)

We have a newly acquired Xserve (Quad Xeon) with the Apple (LSI OEM) Dual-Channel 2Gb FC HBA. The system is attached via a Sun (QLogic OEM) SANbox2-16 switch to a Sun 3511 (SATA-based FC array).
The Sun 3511 is configured with a single RAID5 volume/partition across 12 x 400GB disks and has a single LUN (LUN0) mapped to this volume. As such, the array indicates a partition of 4194223 MB (~ 4TB) should be presented to the host.
The host, however, sees the following (some output omitted for brevity) :
# system_profiler SPFibreChannelDataType
Fibre Channel:
Fibre Channel Domain 1:
Vendor: LSILogic
Product: LSI7202EP
Revision: Firmware 1.2.13.0
Bus: PCI
Slot: Slot-2
Initiator Identifier: 15
Node World Wide Name: 20:00:00:06:2B:0D:CA:41
Port World Wide Name: 10:00:00:06:2B:0D:CA:41
Address Identifier: 01:01:00
Description: Port 1
Speed: Automatic (2 Gigabit)
Topology: Automatic (Point-to-Point)
Status: Link Established
Cable Type: Copper
SCSI Target Device @ 1:
Node World Wide Name: 20:60:00:C0:FF:09:21:18
Port World Wide Name: 22:60:00:C0:FF:99:21:18
Address Identifier: 01:07:00
SCSI Target Identifier: 1
SCSI Peripheral Device Type: 0
Manufacturer: SUN
Model: StorEdge 3511
Revision: 415F
SCSI Logical Unit @ 0:
Capacity: 2 TB
SCSI Logical Unit Number: 0
Manufacturer: SUN
Model: StorEdge 3511
Revision: 415F
Removable Media: Yes
Detachable Drive: No
BSD Name: disk1
OS9 Drivers: No
S.M.A.R.T. status: Not Supported
Volumes:
data03:
Capacity: 2 TB
Available: 2 TB
Writable: Yes
File System: Case-sensitive Journaled HFS+
BSD Name: disk1s2
Mount Point: /data03
Volumes:
disk1s2:
Capacity: 2 TB
Available: 2 TB
Writable: Yes
File System: Case-sensitive Journaled HFS+
SCSI Target Device @ 2:
Node World Wide Name: 20:60:00:C0:FF:09:21:18
Port World Wide Name: 21:60:00:C0:FF:89:21:18
Address Identifier: 01:06:00
SCSI Target Identifier: 2
SCSI Peripheral Device Type: 0
Manufacturer: SUN
Model: StorEdge 3511
Revision: 415F
SCSI Logical Unit @ 0:
Capacity: 2 TB
SCSI Logical Unit Number: 0
Manufacturer: SUN
Model: StorEdge 3511
Revision: 415F
Removable Media: Yes
Detachable Drive: No
BSD Name: disk1
OS9 Drivers: No
S.M.A.R.T. status: Not Supported
Volumes:
data03:
Capacity: 2 TB
Available: 2 TB
Writable: Yes
File System: Case-sensitive Journaled HFS+
BSD Name: disk1s2
Mount Point: /data03
Volumes:
disk1s2:
Capacity: 2 TB
Available: 2 TB
Writable: Yes
File System: Case-sensitive Journaled HFS+
Fibre Channel Domain 0:
Vendor: LSILogic
Product: LSI7202EP
Revision: Firmware 1.2.13.0
Bus: PCI
Slot: Slot-2
Initiator Identifier: 15
Node World Wide Name: 20:00:00:06:2B:0D:CA:40
Port World Wide Name: 10:00:00:06:2B:0D:CA:40
Address Identifier: 01:00:00
Description: Port 0
Speed: Automatic (2 Gigabit)
Topology: Automatic (Point-to-Point)
Status: Link Established
Cable Type: Copper
SCSI Target Device @ 1:
Node World Wide Name: 20:60:00:C0:FF:09:21:18
Port World Wide Name: 22:60:00:C0:FF:99:21:18
Address Identifier: 01:07:00
SCSI Target Identifier: 1
SCSI Peripheral Device Type: 0
Manufacturer: SUN
Model: StorEdge 3511
Revision: 415F
SCSI Logical Unit @ 0:
Capacity: 2 TB
SCSI Logical Unit Number: 0
Manufacturer: SUN
Model: StorEdge 3511
Revision: 415F
Removable Media: Yes
Detachable Drive: No
BSD Name: disk1
OS9 Drivers: No
S.M.A.R.T. status: Not Supported
Volumes:
data03:
Capacity: 2 TB
Available: 2 TB
Writable: Yes
File System: Case-sensitive Journaled HFS+
BSD Name: disk1s2
Mount Point: /data03
Volumes:
disk1s2:
Capacity: 2 TB
Available: 2 TB
Writable: Yes
File System: Case-sensitive Journaled HFS+
SCSI Target Device @ 2:
Node World Wide Name: 20:60:00:C0:FF:09:21:18
Port World Wide Name: 21:60:00:C0:FF:89:21:18
Address Identifier: 01:06:00
SCSI Target Identifier: 2
SCSI Peripheral Device Type: 0
Manufacturer: SUN
Model: StorEdge 3511
Revision: 415F
SCSI Logical Unit @ 0:
Capacity: 2 TB
SCSI Logical Unit Number: 0
Manufacturer: SUN
Model: StorEdge 3511
Revision: 415F
Removable Media: Yes
Detachable Drive: No
BSD Name: disk1
OS9 Drivers: No
S.M.A.R.T. status: Not Supported
Volumes:
data03:
Capacity: 2 TB
Available: 2 TB
Writable: Yes
File System: Case-sensitive Journaled HFS+
BSD Name: disk1s2
Mount Point: /data03
Volumes:
disk1s2:
Capacity: 2 TB
Available: 2 TB
Writable: Yes
File System: Case-sensitive Journaled HFS+
# diskutil info disk1
Device Node: /dev/disk1
Device Identifier: disk1
Mount Point:
Volume Name:
Partition Type: GUIDpartitionscheme
Bootable: Not bootable
Media Type: Generic
Protocol: Fibre Channel Interface
NodeWWN: 20:60:00:C0:FF:09:21:18
SCSI LUN: 0
SMART Status: Not Supported
Total Size: 2.0 TB
Free Space: 0.0 B
Read Only: No
Ejectable: Yes
OS 9 Drivers: No
Low Level Format: Not Supported
You will notice that the fibre channel multipathing on the host is working correctly (no setup required). However, the LUN is presented as exactly 2TB. In searching Apple's KB, I've come across articles relating to Xsan and > 2TB LUNs. On the other hand, Apple is clear that both the partitioning method in use (GPT) and the file system (JHFS+) support much larger sizes.
Xserve Quad Xeon Mac OS X (10.4.9)

Is the switch configured as Open Fabric? This is the preferred config for an xserve. you might want to try a static setting vs "automatic."
Good luck!

What is the maximum number of Fibre Channel LUNS visibile in Solaris 11.2

I have SPARC T4-4's with 4 emulex HBA ports. What is the maximum number of LUNS I can have exported to that server?

Hi Jim,
MOS doc 1018739.1 describes maximum Solaris SCSI and FC targets, LUNs, and device instances.
The FC limit for maximum LUNs is either 65535 or unlimited.
Thanks, Cindy

Maximum number of LUNs per SCSI ID

(1)What is the maximum number of LUNs (logical units) per SCSI ID for the different Solaris releases (default value) ?
(2)How can I increase this maximum number (Patches, kernel or driver parameters, ...)?
(3) Is there any difference whether the devices are attched through SCSI or FC (fibre channel) ?
As a background. I am currently trying to attach a storage device with a maximum LUN number per ID of 32 to a UE450 (running Solaris 7 with the June00 Patch cluster). The problem is that Solaris only sees LUN 0..15 per SCSI ID. The /kernel/drv/sd.conf file was modified for 32 LUNs.
Many thanks for any feedback.

In addition to configuring the SCSI disk driver to support 32 LUNs you also need to configure the underlying SCSI bus driver to support 32 LUNs. With patch 106925-03 (now -04) the PCI SCSI driver, glm, will support upto 32 LUNs if configured in /kernel/drv/glm.conf but defaults to supporting 8. The PCI Fibre Channel driver, ifp, support 16 LUNs (patch 107292).
If you are using StorEdge RAID, the RAID manager software has a set of shell scripts to configure the drivers and RAID software to support 16 or 32 LUNs.
Andrew Walton
Sun Developer Technical Support

Maximum Disk-Volume Capacity Solaris 8 supports (SPARC) ?

Any one knows what is the maximum capacity that Solaris 8 on SPARC supports for storage-set ( Raid set, Stripe Set ...)
Can Solaris 8 supports file system up to 2 Terabyes ?
Thanks

Yup.
EOL in November 2002
Which means EOSL November 2007
http://sunsolve.sun.com/handbook_pub/validateUser.do?target=Systems/U10/U10
Unless you've somehow maintained a service contract on that system,
by specific system serial number,
your best bet is to haunt an online auction site (such as Ebay),
and get a replacement cpu or cpus for shelf stock.
Your current OBP patch level is only down two patch levels,
but your kernel patch level is essentially "never patched".
If it were patched better it may have noticed the issue a lot sooner.
Expect to replace that cpu.

Re-read disk size in Solaris 10 x86 / VMware

Hi
Using
# uname -a
SunOS host1 5.10 Generic_142910-17 i86pc i386 i86pc
We have a 30G virtual disk, on top of which a UFS filesystem is living, mounted, and used.
The Virtual disk has been resized to 40G.
I know I need to change the fdisk partition size, after which i can change the "format" partition size, then use growfs.
But I don't know how to get S10 to recognise the new size for the disk.
fdisk tells me
Total disk size is 3916 cylinders
Cylinder size is 16065 (512 byte) blocks
Cylinders
Partition   Status
Type
Start   End   Length
=========   ======
============ =====   ===   ======   ===
1
Active
Solaris2
1 3915
3915
100
# prtvtoc -h /dev/dsk/c1t2d0s2
       0      0    00      16065 62846280 62862344   /xxx
       2      5    01          0 62862345 62862344
       8      1    01          0     16065     16064
# df -h /xxx
Filesystem             size   used avail capacity Mounted on
/dev/dsk/c1t2d0s0       30G    29G   498M    99%    /xxx
On Linux I might use partprobe or blockdev --rereadpt but on Solaris?
Cheers
KM

Hello
this document should help, but make a backkup before running it
How to expand a UFS Lun in Solaris 10 (Doc ID 1451858.1)
Regards
Eze

OCFS LUN / Filessytem Limit

We are planning to build 2 RHEL 5.5 (64bit) Servers with EMC SAN LUNs shared between them and we are going to use OCFS instead of ASM to share the disks for our application Oracle RAC 11g.
As per our design we need to have LUNs upto the size of 24TB From EMC SAN. In RHEL 5.5 with ext3 and ext4 the maximum supported filessytem size is 16TB. I want to know, what is the maximum LUN/filesystem size supported by OCFS ?
If I had to do a RAC with ASM disks, I know that we can present smaller LUNs of size 3000GBx8=24TB and the RAC will stipe across them and form a large usable space with in RAC. But in OCFS how do I do that? Can I present multiple LUNS of small size and form a bigger LUNs out of it inside OCFS? The space we are planing is 12 TB for Database files, 300 GB Redo Logs, 8 TB Flash Recovery, 24 TB of Backup Space to backup the Database files. How do I break down the LUN NUmbers for each of these? I can make a LUN as large as 64TB out of EMC Storage so there is no problem there.
Thanks for your help in advance.

I want to know, what is the maximum LUN/filesystem size supported by OCFS ?http://www.oracle.com/us/technologies/linux/025995.htm
http://oss.oracle.com/projects/ocfs2/dist/documentation/v1.6/ocfs2-1_6-usersguide.pdf
OCFS2 supports cluster sizes of 4KB, 8KB, 16KB, 32KB, 64KB, 128KB, 256KB, 512KB and 1MB.
A file system with 1MB cluster size can go up to *4PB*, while a file system with a 4KB cluster size can address up to 16TB.

Maximum LUNS in solaris 10,9

Similar Messages

Maybe you are looking for