| Asset ID: |
1-75-1009403.1 |
| Update Date: | 2010-10-05 |
| Keywords: | |
Solution Type
Troubleshooting Sure
Solution
1009403.1
:
Sun StorEdge[TM] SAN Foundation software: Configuration error can be reported as "cfgadm: Library error"
| Related Items |
- Sun Storage 6320 System
- Sun Storage SAN Foundation Software
- Sun Storage T3 Array
- Sun Storage T3+ Array
- Sun Storage 6120 Array
- Sun Storage 6130 Array
|
| Related Categories |
- GCS>Sun Microsystems>Storage - Disk>Modular Disk - 6xxx Arrays
- GCS>Sun Microsystems>Storage Software>Sun Storage SAN Software
- GCS>Sun Microsystems>Storage - Disk>Modular Disk - Other
|
PreviouslyPublishedAs
213000
DescriptionA configuration error, such as: switch zoning, LUN permission, and/or mistake in
World Wide Number(WWN) can be misleadingly reported as "cfgadm: Library error"
Example:
# cfgadm -c configure c3
cfgadm: Library error: failed to create device node: 20030003ba13e6e4:
Invalid argument
Steps to FollowSteps to Follow
Samples
________________________________________________________________________________________________________
A customer connected a node to a Sun StorEdge 6320 with two arrays via a fabric switch.
What customer did:
cfgadm: Library error: failed to create device node: 20030003ba13e6e4: Invalid argument
Investigation:
1. Check what the Host Bus Adapter(HBA) sees:
luxadm -e dump_map /devices/ssm@0,0/pci@18,700000/SUNW,qlc@1/fp@0,0:devctl
Pos Port_ID Hard_Addr Port WWN Node WWN Type
0 10000 0 20030003ba13e6e4 10000003ba13e6e4 0x0 (Disk device)
^^^^^^^^^^^^^^^^
1 10100 0 210000e08b0c9613 200000e08b0c9613 0x1f (Unknown Type)
2 10201 0 210100e08b2b24f7 200100e08b2b24f7 0x1f (Unknown Type)
3 10301 0 210000e08b0b5bf7 200000e08b0b5bf7 0x1f (Unknown Type)
4 10400 0 210000e08b165bfc 200000e08b165bfc 0x1f (Unknown Type)
5 10700 0 210000e08b18aa66 200000e08b18aa66 0x1f (Unknown Type,Host Bus Adapter)
^^^^^^^^^^^^^^^^
luxadm -e dump_map /devices/ssm@0,0/pci@19,700000/SUNW,qlc@2/fp@0,0:devctl
Pos Port_ID Hard_Addr Port WWN Node WWN Type
0 10000 0 20030003ba13f842 10000003ba13f842 0x0 (Disk device)
^^^^^^^^^^^^^^^^
1 10100 0 210000e08b0e032d 200000e08b0e032d 0x1f (Unknown Type)
2 10201 0 210100e08b2b5bf7 200100e08b2b5bf7 0x1f (Unknown Type)
3 10301 0 210000e08b0b24f7 200000e08b0b24f7 0x1f (Unknown Type)
4 10700 0 210000e08b1910ce 200000e08b1910ce 0x1f (Unknown Type,Host Bus Adapter)
^^^^^^^^^^^^^^^^
From above:
2. Check the Sun StorEdge 6320 array:
On sp0-Array00:
============================
| COMMAND: port list
============================
port targetid addr_type status host wwn
u1p1 0 hard online sun 20030003ba13e6e4
u3p1 3 hard online sun 20030003ba13f842
Note: The node is connected to sp0-Array00 (per luxadm -e dump_map), but checking the LUN Permission List, our HBA PWWN is not listed, that is - no permission.
============================
| COMMAND: lun perm list
============================
lun slice WWN Group Name Group Perm WWN Perm Effective Perm
--------------------------------------------------------------------------------------------------------
0 0 default -- -- none none
0 0 210000e08b0b5bf7 E4500 rw none rw
0 0 210100e08b2b5bf7 E4500 rw none rw
0 0 210000e08b0b24f7 E4500 rw none rw
0 0 210100e08b2b24f7 E4500 rw none rw
1 1 default -- -- none none
1 1 210000e08b0b5bf7 E4500 rw none rw
1 1 210100e08b2b5bf7 E4500 rw none rw
1 1 210000e08b0b24f7 E4500 rw none rw
1 1 210100e08b2b24f7 E4500 rw none rw
2 2 default -- -- none none
2 2 210000e08b0b5bf7 E4500 rw none rw
2 2 210100e08b2b5bf7 E4500 rw none rw
2 2 210000e08b0b24f7 E4500 rw none rw
2 2 210100e08b2b24f7 E4500 rw none rw
3 3 default -- -- none none
3 3 210000e08b0e032d oatest rw none rw
3 3 210000e08b0ed02d oatest rw none rw
4 4 default -- -- none none
4 4 210000e08b0e032d oatest rw none rw
4 4 210000e08b0ed02d oatest rw none rw
--------------------------------------------------------------------------------------------------------
3. Check the other array:
On sp0-Array01:
============================
| COMMAND: port list
============================
port targetid addr_type status host wwn
u1p1 1 hard offline sun 20030003ba68ebea
u2p1 2 hard offline sun 20030003ba68e956
Note: From the LUN permission list, we found that the node is meant to be connected to sp0-Array01.
============================
| COMMAND: lun perm list
============================
lun slice WWN Group Name Group Perm WWN Perm Effective Perm
--------------------------------------------------------------------------------------------------------
5 0 default -- -- none none
5 0 210000e08b18aa66 E2900 rw none rw
5 0 210000e08b1910ce E2900 rw none rw
6 1 default -- -- none none
6 1 210000e08b18aa66 E2900 rw none rw
6 1 210000e08b1910ce E2900 rw none rw
7 2 default -- -- none none
7 2 210000e08b18aa66 E2900 rw none rw
7 2 210000e08b1910ce E2900 rw none rw
8 3 default -- -- none none
8 3 210000e08b18aa66 E2900 rw none rw
8 3 210000e08b1910ce E2900 rw none rw
--------------------------------------------------------------------------------------------------------
Conclusion:
The mistake was in the switch zoning. sp0-Array01 should have been configured in the zone instead of sp0-Array00.
Section Top
________________________________________________________________________________________________________
A customer added a Sun StorEdge[TM] T3+ array pair, into a Sun StorEdge[TM]
39x0, and created new volumes/luns in this new array, but could not configure them from the host.
What customer did:
cfgadm: Library error: failed to create device node: 50020f2300011455: Invalid argument
failed to configure ANY device on FCA port
Investigation:
1. Check what the HBA sees:
#luxadm -e dump_map /devices/pci@9,600000/pci@1/SUNW,qlc@4/fp@0,0:devctl
Pos Port_ID Hard_Addr Port WWN Node WWN Type
0 1082e4 1000e4 50020f2300011455 50020f2000011455 0x0 (Disk device)
^^^^^^^^^^^^^^^^
1 108500 0 210100e08b3945d7 200100e08b3945d7 0x1f (Unknown Type,Host Bus Adapter)
#luxadm -e dump_map /devices/pci@9,600000/pci@1/SUNW,qlc@5/fp@0,0:devctl
Pos Port_ID Hard_Addr Port WWN Node WWN Type
0 1042e4 1000e4 50020f2300011475 50020f2000011475 0x0 (Disk device)
^^^^^^^^^^^^^^^^
1 104500 0 210000e08b1945d7 200000e08b1945d7 0x1f (Unknown Type,Host Bus Adapter)
From above:
2. Check the Sun StorEdge 39x0 array:
On t3b1 (the newly added array):
::::::::::::::
port_list
::::::::::::::
port list
port targetid addr_type status host wwn
u1p1 2 hard online sun 50020f2300011475
u2p1 3 hard online sun 50020f2300011455
Note: The host HBA ports are connected to t3b1's ports (per luxadm -e dump_map), but checking the LUN Permission List, the HBA PWWN are not listed, i.e. no permission.
::::::::::::::
lun_perm_list
::::::::::::::
lun perm list
lun slice WWN Group Name Group Perm WWN Perm Effective Perm
--------------------------------------------------------------------------------------------------------
0 0 default -- -- none none
0 0 50020f2000011475 TEAM rw none rw
0 0 50020f2300011455 TEAM rw none rw
1 1 default -- -- none none
1 1 50020f2000011475 TEAM rw none rw
1 1 50020f2300011455 TEAM rw none rw
2 2 default -- -- none none
2 2 50020f2000011475 TEAM rw none rw
2 2 50020f2300011455 TEAM rw none rw
3 3 default -- -- none none
3 3 50020f2000011475 TEAM rw none rw
3 3 50020f2300011455 TEAM rw none rw
4 4 default -- -- none none
4 4 50020f2000011475 TEAM rw none rw
4 4 50020f2300011455 TEAM rw none rw
5 5 default -- -- none none
5 5 50020f2000011475 TEAM rw none rw
5 5 50020f2300011455 TEAM rw none rw
6 6 default -- -- none none
6 6 50020f2000011475 TEAM rw none rw
6 6 50020f2300011455 TEAM rw none rw
--------------------------------------------------------------------------------------------------------
Note: The WWN's listed in lun perm list are t3b1's WWN's! It should have been host HBA's WWN's.
3. Check hwwn definitions:
::::::::::::::
hwwn_listgrp
::::::::::::::
hwwn listgrp
Group Name
----------------------
TEAM
----------------------
** Total 1 entries **
::::::::::::::
hwwn_list
::::::::::::::
hwwn list
WWN in this group TEAM
-----------------------------------------
50020f2000011475
50020f2300011455
-----------------------------------------
** Total 1 groups **
Note: The hwwn definitions should define host HBA's WWN's and not the t3b1's own WWN's.
Conclusion:
The mistake was in the hwwn definition. The user mistook the Sun StorEdge T3+
array's WWN as the host WWN. Effectively the host's HBA has no permission to
access the LUN, as the permission was never created. Removing all of the hwwn
definition and permission, and re-creating them with the correct HBA WWN will
resolve the problem.
Variation Of the Same Theme:
Sometimes the hwwn definitions appear to be configured correctly with
the host's HBA WWN, however, a careful review shows that it was misconfigured.
For example:
hwwn list
WWN in this group TEAM
-----------------------------------------
210100e08b3945d7
200000e08b1945d7 <--- THIS WWN is misconfigured (one digit off)
-----------------------------------------
** Total 1 groups **
The correct WWN is 210000e08b1945d7, i.e. 21* instead of 20*. The "node WWN"
was incorrectly added when the "port WWN" should have been used.
Removing the misconfigured WWN, and adding the correct WWN to the
LUN permission will resolve the issue.
Section Top
________________________________________________________________________________________________________
cfgadm fail with Library error:... when configuring a Sun StorEdge 6130.
Symptoms:
cfgadm: Library error: failed to create device node: 200600a0b8170fb2:
Invalid argument failed to configure ANY device on FCA port
Ap_Id Type Receptacle Occupant Condition
c5 fc-fabric connected unconfigured unknown
c5::200600a0b8170fb2 disk connected unconfigured unknown
Investigation:
1. Check what the HBA sees:
# luxadm -e port
/devices/pci@1f,4000/SUNW,qlc@2/fp@0,0:devctl CONNECTED
# luxadm -e dump_map /devices/pci@1f,4000/SUNW,qlc@2/fp@0,0:devctl
Pos Port_ID Hard_Addr Port WWN Node WWN Type
0 140200 0 200600a0b8170fb2 200600a0b8170fb1 0x0 (Disk device)
1 140500 0 210000e08b0a62e0 200000e08b0a62e0 0x1f (Unknown Type,Host Bus Adapter)
^^^^^^^^^^^^^^^^
From above:
The correct host bus adapter port WWN is 210000e08b0a62e0.
2. Verify inititor WWN defined in Sun StorEdge 6130:
This can be done either through CLI sscs or BUI (Browser User Interface).
Use sscs as example:
# sscs login -h localhost -u <Correct_userid>
Type your password:
# sscs list array
Array: se6130-c
Array: se6130-b
# sscs list -a se6130-b initiator
Initiator: e420r-c-qlc1
Initiator: e420r-b-qlc
# sscs list -a se6130-b initiator e420r-b-qlc
Initiator: e420r-b-qlc
WWN: 21:01:00:E0:8B:0A:62:E0
^^^^
Host: e420r-b
OS Type: Solaris (with Traffic Manager)
From above:
Initiator WWN was defined as 210100e08b0a62e0, i.e. 2101* instead of 2100*.
Conclusion:
Initiator WWN defined in the array was incorrect.
How To Fix:
Remove and recreate with the correct initiator port WWN
Using sscs:
# sscs delete -a se6130-b initiator e420r-b-qlc
# sscs create -a se6130-b -w 210000e08b0a62e0 -h e420r-b -o solaris initiator e420r-b-qlc
# sscs list -a se6130-b initiator e420r-b-qlc
Initiator: e420r-b-qlc
WWN: 21:00:00:E0:8B:0A:62:E0
Host: e420r-b
OS Type: Solaris (with Traffic Manager)
# luxadm -e forcelip /devices/pci@1f,4000/SUNW,qlc@2/fp@0,0:devctl
Using Sun StorEdge 6130 Configuration Services BUI:
Volumes with incorrect initiator wwn can be checked by selecting
-- Storage -- Logical -- Volumes
-- select the volume to display volume details -- select initiators
-> The incorrect initiator wwn is displayed
To recreate the host with correct initiator wwn
-- Physical -- Initiators
-- select the initiator -- check the box -- delete
-- select new and input the correct wwn
Section Top
_
ProductSun StorageTek SAN 4.4.1 Software
Sun StorageTek SAN 4.4 Software
Sun StorageTek SAN 4.3 Software
Sun StorageTek SAN 4.2 Software
Sun StorageTek SAN 4.1 Software
Sun StorageTek SAN 4.0 Software
Sun StorageTek 6320 System
Sun StorageTek 6120 Array
Sun StorageTek SAN 4.4.3 Software
Storage Area Network (SAN)
Configuration Service
Sun StorageTek 6130 Array (SATA)
Sun StorageTek 6130 Array
Sun StorageTek T3+ Array
Sun StorageTek T3 Array
Internal Comments
For Internal Sun Use Only
- CR 6222732 Vague message "cfgadm: Library error: failed to create device node:" was filed as RFE for better error description.
- Scenario 2 was taken from Esc 1-8241597.
- The addition to scenario 2 was from ESC 1-6403315.
- The addition to Scenario 3 was from ESC 1-9374104.
"cfgadm: Library Error" when connecting Solaris hosts to IBM storage Model 1742 (FastT700).
This IBM storage system is similar to our SE6130 (a rebadge Engenio storage). IBM GUI called "IBM FAStT Storage Manager"
is the equivalent GUI as the "Sun StorEdge 6130 Configuration Services"
cfgadm, SAN, SAN 4.4.4, LUN permission, zoning, library, invalid, argument, T3, T3+, T4, 6120, SE6120, 6130, SE6130
Previously Published As
80698
Change History
Date: 2007-10-09
User Name: 7058
Action: Update Canceled
Comment: *** Restored Published Content *** Delete working copy. Existing published copy stays on sunsolve. IBIS migration prep.
Version: 0
Date: 2007-10-09
User Name: 7058
Action: Reassign
Comment: Delete working copy. Existing published copy stays on sunsolve. IBIS migration prep.
Version: 0
Date: 2006-02-22
User Name: 195642
Action: Update Started
Comment: Updating doc based on different problem with similar errors.
Version: 0
Attachments
This solution has no attachment
