List LUNs attached to HBA / Disk controllers in Solaris 10

As a system administrator you may come across situations where in your SAN admin presents you some storage (LUNS) and you can’t find where the hell has it gone. The following are some of the ways to list the LUNS presented on a controller or all the controllers on the server.

1. Using fcinfo

In Solaris 10, you can use the “fcinfo” utility which is a 2 step process to identify the Luns presented to the server.

1. Find the HBA port WWN number on the server:

# fcinfo hba-port

This command will show the HBA Port WWN (world wide Node ) among other information like the Node WWN, Device name, manufacturer, firmware, driver details etc.

root@myserver:/root # fcinfo hba-port
HBA Port WWN: 21000022ff0553e9
OS Device Name: /dev/cfg/c5
Manufacturer: QLogic Corp.
Model: 371-4324-02
Firmware Version: 05.03.02
FCode/BIOS Version: BIOS: 2.02; fcode: 2.03; EFI: 2.01;
Serial Number: 0402R00-1102885753
Driver Name: qlc
Driver Version: 3.00p
Type: L-port
State: online
Supported Speeds: 2Gb 4Gb 8Gb
Current Speed: 4Gb
Node WWN: 20000022ff0553e9

Here 21000022ff0553e9 is the WWN number for the HBA port.

2. List SCSI targets for the remote port attached to the HBA port attached to the above.

# fcinfo -sl -p HBA-Port-WWN

root@myserver:/root # fcinfo remote-port -sl -p 21000022ff0553e9
Remote Port WWN: 202400a0b8744072
Active FC4 Types:
SCSI Target: yes
Node WWN: 200400a0b8744072
Link Error Statistics:
Link Failure Count: 1
Loss of Sync Count: 2
Loss of Signal Count: 72
Primitive Seq Protocol Error Count: 0
Invalid Tx Word Count: 0
Invalid CRC Count: 0
LUN: 0
Vendor: SUN
Product: LCSM100_F
OS Device Name: /dev/rdsk/c5t202400A0B8744072d0s2
LUN: 2 Vendor: SUN
Product: LCSM100_F
OS Device Name: /dev/rdsk/c5t202400A0B8744072d2s2
LUN: 31 Vendor: SUN
Product: Universal Xport
OS Device Name: /dev/rdsk/c5t202400A0B8744072d31s2

Here, LUN0 and LUN2 are the actual disks and LUN31 is the Command device for the Storage controller
2. Using cfgadm

You can also find the above information using the “cfgadm” utility. One of the following commands should reveal the LUNS attached to the controller. Although the later works only on Solaris 10.

# cfgadm -al -o show_FCP_dev c5
 
or
 
# cfgadm -al -o show_SCSI_LUNS c5

where c5 is the controller. If you do not mentioned the controller, it then displays for every single disk controller on the server.

root@myserver:/root # cfgadm -al -o show_FCP_dev c5
Ap_Id Type Receptacle Occupant Condition
c5 fc-private connected configured unknown
c5::202400a0b8744072,0 disk connected configured unknown
c5::202400a0b8744072,2 disk connected configured unknown
c5::202400a0b8744072,31 disk connected configured unknown

root@myserver:/root # cfgadm -al -o show_SCSI_LUN c5
Ap_Id Type Receptacle Occupant Condition
c5 fc-private connected configured unknown
c5::202400a0b8744072,0 disk connected configured unknown
c5::202400a0b8744072,2 disk connected configured unknown
c5::202400a0b8744072,31 disk connected configured unknown

                      thanks for Reading.. 

DISK QUOTA PERMISSIONS IN SOLARIS 10

verify before prceeding.

SUN#df -k or df -h
sun#format

follow the below screen shots.

next create a filesystem on partition.
#newfs /dev/rdsk/c0t0d0s(enter the slice no you have selected)


1.create a user account with home directory and assign password to the user.
sun#useradd -d /export/home/<home dir> -m sun<username>
sun#passwd <username>
password:
confirm password :

2.mount the partition on user home directory.
sun#mount /dev/dsk/c0t0d0s<no> /export/home/<user home dir>

quota permissions:
sun#cd /export/home
sun#touch quotas
sun#quotaon -v /export/home
sun#edquota <username>
new window will appear
fs /export/home   blocks(soft=4,hard=8)
                inodes (soft=4,hard=8)
then save the file.

To copy the quota permissions from one user to another user.
sun#edquota -p <old user> <new user>

To verify-
sun#repquota -v /export/home

To turnoff quota
sun#quotaoff -v /export/home.

                                                Thank you for Reading.

  

CISCO MDS 9509 vs Brocade DCX - Fibre Channel Showdown

In the past few years Brocade and Cisco have dominated the fibre channel director market. Both companies produce top-notch equipment; the Brocade DCX is a powerful, enterprise-class director rivaled only by the CISCO MDS 9509.
With very similar technology and offerings, which director is the best for your existing SAN switching infrastructure?
Here are 5 things to consider when deciding which director, the Brocade DCX or the Cisco MDS 9509, is a better fit for your enterprise needs.
Brocade DCX vs Cisco MDS 9509

1. Reliability: Both Brocade and Cisco MDS produce high-quality, reliable switching infrastructure. As the directors have no single point of failure, the Brocade DCX and Cisco MDS 9509 are both dependable SAN directors that prevent downtime.
Brocade and Cisco MDS directors are built to support mission-critical networks and prevent downtime. Since SAN directors contain individual blades, failed blades can be replaced without causing inconvenient downtime for the director. Since any difference in reliability would be slight, the Brocade DCX and Cisco MDS 9509 seem to be tied in this category.

2. Scalability: The Brocade DCX backbone and Cisco 9509 provide the scalability to conquer even the fastest growing SAN networks. The Brocade DCX scales up to 384 ports and is well-suited for large enterprises. The Brocade DCX will hold up to eight blades and supports Fibre Channel technology as well as Fibre Channel over IP.
The Cisco MDS 9509 provides nine blade slots and scales up to 336 Fibre Channel ports. This large, powerful director is equipped to support demanding growth. With similar growth options and scalable models to accommodate future needs, the Brocade DCX and Cisco MDS 9509 appear to be even in terms of scalability.

3. Latency: In an effort to reduce latency, the Brocade DCX Backbone offers a local switching option that the Cisco MDS 9509 does not possess. Local switching reduces latency for devices that are connected to the same blade and lowers the total amount of traffic that travels through the core switching blades.
Although Cisco says that local switching does not actually result in a reduction in latency, a lack of local switching is a weak point of the Cisco MDS 9509. In terms of latency, the Brocade DCX director has the advantage.*

4. Raw Throughput and Performance: Both the Brocade DCX and Cisco MDS directors provide powerful switching infrastructure built to handle demanding storage environments.
Offering 256 Gbps raw throughput per port, the Brocade DCX backbone provides one of the fastest Fibre Channel switching infrastructures on the market. When comparing the two directors, the Cisco MDS director appears to be slightly slower as it provides only 96 Gbps raw throughput per port.

5. Strategy: In the long run, one other important consideration when choosing a director is how that director will fit with the rest of your switching infrastructure and your future switching strategy. What brand of switches do you currently have implemented in your SAN environment? Does the enterprise plan to stay with fibre channel technology and invest in Brocade’s highly developed 16 Gbps fibre channel product line, or is the enterprise interested in changing protocols?
Noting strategy differences and matching current products with your future plan should help you choose whether a Cisco MDS 9509, a Brocade DCX backbone, or another SAN director is the right fit for your enterprise environment.