Unsolved
This post is more than 5 years old
76 Posts
0
4218
December 1st, 2011 10:00
"Not Visible" problem on HP-UX box
We solved this with the IBM AIX box.. but I'm having the trouble again masking storage to an HP-UX box. Cannot get the new masked device to get out of the "Not Visible" stage. There is no "cfgmgr" for HP-UX.
# ./symmaskdb list devs -wwn 50060xxxxxxx
Symmetrix ID : 00019xxxxxxx
Originator Port wwn : 50060xxxxxx
User-generated Name : tartan/fcdo
Sym Dev LUN
Name Dir:P Physical Device Name VBUS TID SYMM HOST Attr Cap(MB)
------ ----- ----------------------- ---- --- ---- ---- ---- -------
0221 8C:0 Not Visible 0 0 88 N/A (M) 107170 <==========
03A3 8C:0 /dev/rdsk/c22t7d5 0 0 75 5 (M) 107170
03A6 8C:0 /dev/rdsk/c22t7d6 0 0 76 6 (M) 250064
03AD 8C:0 /dev/rdsk/c22t7d7 0 0 77 7 (M) 250064
03B4 8C:0 /dev/rdsk/c22t8d0 0 0 80 0 (M) 250064
03BB 8C:0 /dev/rdsk/c22t8d1 0 0 81 1 (M) 250064
03C2 8C:0 /dev/rdsk/c22t8d2 0 0 82 2 (M) 250064
03C9 8C:0 /dev/rdsk/c22t8d3 0 0 83 3 (M) 250064
03D0 8C:0 /dev/rdsk/c22t8d4 0 0 84 4 (M) 250064
03D7 8C:0 /dev/rdsk/c22t8d5 0 0 85 5 (M) 250064
03DE 8C:0 /dev/rdsk/c22t8d6 0 0 86 6 (M) 250064
03E5 8C:0 /dev/rdsk/c22t8d7 0 0 87 7 35723
tried running the symmaskdb refresh, powermt config, and symcfg discover
dynamox
9 Legend
•
20.4K Posts
0
December 1st, 2011 10:00
on HPUX did you run ioscan and insf ?
markdf
76 Posts
0
December 1st, 2011 11:00
Well, let me try it all again from scratch. One thing I noticed on the ./sympd list is that all of the devices that were originally attached to this server, came from a RAID-5 pool, but I'm masking from a RAID-6 pool. Maybe it makes no difference, but at least let me try with consistency. I'm gonna unmap, unmask, and try again.
Also, when mapping do I need to map them to both director ports (i.e. 8C:0 & 9C:0), or just one like I just did. On the AIX box, I just mapped to one:
map dev 0222 to dir 8C:1 target=0, lun=03D;
and it worked. On this box, I did the same thing:
map dev 0221 to dir 8C:0 target=0, lun=088;
and it shows up, but looks like this:
# ./symmaskdb list assignment -dev 0221
Symmetrix ID : 000190105528
Device Identifier Type Dir:P
------ ---------------- ----- ----------------
0221 50060b0000c9a2e0 FIBRE FA-8C:0
10000000c95ef8b9 FIBRE FA-8C:1
But here's what another device looks like already present on this system:
# ./symmaskdb list assignment -dev 03b4
Symmetrix ID : 000190105528
Device Identifier Type Dir:P
------ ---------------- ----- ----------------
03B4 50060b0000c9a2e0 FIBRE FA-8C:0
50060b0000c9a2f8 FIBRE FA-9C:0
I don't even know where FA-8C:1 is (what server.. and that might be the whole problem itself.. but how did it automatically get there?)
markdf
76 Posts
0
December 1st, 2011 11:00
I sure did. ioscan -fnC disk didn't find it, and insf did nothing either. Perhaps the order I did them in is wrong?
1. map device to local luns
2. symmask refresh
3. powermt config
4. symcfg discover
5. ioscan -fnC disk
6. insf
?
dynamox
9 Legend
•
20.4K Posts
0
December 1st, 2011 11:00
i don't see it in this list. Order is map, mask, ioscan, insf, powermt config, powermt save, symcfg discover and then sympd list
markdf
76 Posts
0
December 1st, 2011 11:00
hmm.. im not sure if I do..
# ./syminq
Device Product Device
------------------------ --------------------------- ---------------------
Name Type Vendor ID Rev Ser Num Cap (KB)
------------------------ --------------------------- ---------------------
/dev/rdsk/c2t8d0 HP 73.4G MAX3073NC HPC1 X1032500 71687369
/dev/rdsk/c2t10d0 HP 73.4G MAX3073NC HPC1 X1032661 71687369
/dev/rdsk/c14t7d5 M(3) EMC SYMMETRIX 5773 28003A3000 109742400
/dev/rdsk/c14t7d6 M(7) EMC SYMMETRIX 5773 28003A6000 256065600
/dev/rdsk/c14t7d7 M(7) EMC SYMMETRIX 5773 28003AD000 256065600
/dev/rdsk/c14t8d0 M(7) EMC SYMMETRIX 5773 28003B4000 256065600
/dev/rdsk/c14t8d1 M(7) EMC SYMMETRIX 5773 28003BB000 256065600
/dev/rdsk/c14t8d2 M(7) EMC SYMMETRIX 5773 28003C2000 256065600
/dev/rdsk/c14t8d3 M(7) EMC SYMMETRIX 5773 28003C9000 256065600
/dev/rdsk/c14t8d4 M(7) EMC SYMMETRIX 5773 28003D0000 256065600
/dev/rdsk/c14t8d5 M(7) EMC SYMMETRIX 5773 28003D7000 256065600
/dev/rdsk/c14t8d6 M(7) EMC SYMMETRIX 5773 28003DE000 256065600
/dev/rdsk/c14t8d7 EMC SYMMETRIX 5773 28003E5000 36580800
/dev/rdsk/c16t8d7 EMC SYMMETRIX 5773 28003E5000 36580800
/dev/rdsk/c20t0d0 GK EMC SYMMETRIX 5773 2800020000 2880
/dev/rdsk/c20t7d5 M(3) EMC SYMMETRIX 5773 28003A3000 109742400
/dev/rdsk/c20t7d6 M(7) EMC SYMMETRIX 5773 28003A6000 256065600
/dev/rdsk/c20t7d7 M(7) EMC SYMMETRIX 5773 28003AD000 256065600
/dev/rdsk/c20t8d0 M(7) EMC SYMMETRIX 5773 28003B4000 256065600
/dev/rdsk/c20t8d1 M(7) EMC SYMMETRIX 5773 28003BB000 256065600
/dev/rdsk/c20t8d2 M(7) EMC SYMMETRIX 5773 28003C2000 256065600
/dev/rdsk/c20t8d3 M(7) EMC SYMMETRIX 5773 28003C9000 256065600
/dev/rdsk/c20t8d4 M(7) EMC SYMMETRIX 5773 28003D0000 256065600
/dev/rdsk/c20t8d5 M(7) EMC SYMMETRIX 5773 28003D7000 256065600
/dev/rdsk/c20t8d6 M(7) EMC SYMMETRIX 5773 28003DE000 256065600
/dev/rdsk/c20t8d7 EMC SYMMETRIX 5773 28003E5000 36580800
/dev/rdsk/c22t0d0 GK EMC SYMMETRIX 5773 2800020000 2880
/dev/rdsk/c22t7d5 M(3) EMC SYMMETRIX 5773 28003A3000 109742400
/dev/rdsk/c22t7d6 M(7) EMC SYMMETRIX 5773 28003A6000 256065600
/dev/rdsk/c22t7d7 M(7) EMC SYMMETRIX 5773 28003AD000 256065600
/dev/rdsk/c22t8d0 M(7) EMC SYMMETRIX 5773 28003B4000 256065600
/dev/rdsk/c22t8d1 M(7) EMC SYMMETRIX 5773 28003BB000 256065600
/dev/rdsk/c22t8d2 M(7) EMC SYMMETRIX 5773 28003C2000 256065600
/dev/rdsk/c22t8d3 M(7) EMC SYMMETRIX 5773 28003C9000 256065600
/dev/rdsk/c22t8d4 M(7) EMC SYMMETRIX 5773 28003D0000 256065600
/dev/rdsk/c22t8d5 M(7) EMC SYMMETRIX 5773 28003D7000 256065600
/dev/rdsk/c22t8d6 M(7) EMC SYMMETRIX 5773 28003DE000 256065600
/dev/rdsk/c22t8d7 EMC SYMMETRIX 5773 28003E5000 36580800
can you pick it out of there based on the info above? these all appear to have device assignments (i.e. /dev/rdsk/cx0x0x), but if you look above in the thread, it doesn't seem like we got that far.
dynamox
9 Legend
•
20.4K Posts
0
December 1st, 2011 11:00
you need to map to at least two different FA ports if you expect any kind of redundancy. When you map devices for HPUX you need to specify target, bus and ID, your mapping does not look right to me. If you run "symcfg list -sid 123 -dir 8c -p 0 -address -available" , you will see how existing devices are mapped on these FAs.
dynamox
9 Legend
•
20.4K Posts
0
December 1st, 2011 11:00
if you run syminq ..do you see the new device ?
markdf
76 Posts
0
December 3rd, 2011 12:00
Okay, this is really getting to be upsetting.. let's just try to add one drive from the DMX-4
1. HPUX version
# uname -a
HP-UX tartan B.11.23 U 9000/800 2015509276 unlimited-user license
2. Check for any dead paths
# powermt check
#
3. Check to make sure we're logged into the SAN
# ./symmask list logins | grep tartan
50060b0000c9a2e0 Fibre tartan fcdo 4a0600 Yes Yes
50060b0000c9a2f8 Fibre tartan fcd1 b20700 Yes Yes
4. Check for free devices on SAN
# ./symdev list -noport | more
Symmetrix ID: 000190105528
Device Name Directors Device
--------------------------- ------------- -------------------------------------
Cap
Sym Physical SA![]()
DA :IT Config Attribute Sts (MB)
--------------------------- ------------- -------------------------------------
5. Check for available luns on server
# ./symcfg list -fa 8c -p 0 -addresses -avail
Symmetrix ID: 000190105528 (Local)
Director Device Name Attr Address
---------------------- ----------------------------- ---- --------------
Ident Symbolic Port Sym Physical VBUS TID LUN
------ -------- ---- ---- ----------------------- ---- --- ---
FA-8C 08C 0 0020 /dev/rdsk/c22t0d0 VCM 0 00 000
0351 Not Visible 0 00 001
0352 Not Visible 0 00 002
0353 Not Visible 0 00 003
0354 Not Visible 0 00 004
0355 Not Visible 0 00 005
0356 Not Visible 0 00 006
0357 Not Visible 0 00 007
- AVAILABLE 0 00 008 *
So.. we're gonna map device 0408 to FE 8C port 0 on lun 008
9. Map .cmd file
# cat addspace/tempmap.cmd
map dev 0408 to dir 8C:0, lun=008;
10. Preview the file
# ./symconfigure -f addspace/tempmap.cmd preview -nop
Establishing a configuration change session...............Established.
Processing symmetrix 000190105528
Performing Access checks..................................Allowed.
Checking Device Reservations..............................Allowed.
Submitting configuration changes..........................Submitted
Locking devices...........................................Locked.
Validating configuration changes..........................Validated.
Closing configuration change request......................Closed.
Terminating the configuration change session..............Done.
The configuration change session has completed successfully.
11. Prepare the map
# ./symconfigure -f addspace/tempmap.cmd prepare -nop
Establishing a configuration change session...............Established.
Processing symmetrix 000190105528
Performing Access checks..................................Allowed.
Checking Device Reservations..............................Allowed.
Submitting configuration changes..........................Submitted
Locking devices...........................................Locked.
Validating configuration changes..........................Validated.
Initiating PREPARE of configuration changes...............Prepared.
Closing configuration change request......................Closed.
Terminating the configuration change session..............Done.
The configuration change session has completed successfully.
12. Commit the mapping..
# ./symconfigure -f addspace/tempmap.cmd commit -nop
Establishing a configuration change session...............Established.
Processing symmetrix 000190105528
Performing Access checks..................................Allowed.
Checking Device Reservations..............................Allowed.
Submitting configuration changes..........................Submitted
Locking devices...........................................Locked.
Validating configuration changes..........................Validated.
Initiating PREPARE of configuration changes...............Prepared.
Initiating COMMIT of configuration changes................Queued.
COMMIT requesting required resources......................Obtained.
Step 002 of 013 steps.....................................Executing.
Step 011 of 013 steps.....................................Executing.
Local: COMMIT............................................Done.
Terminating the configuration change session..............Done.
The configuration change session has successfully completed.
13. Add the device..
# ./symmask -sid 28 -wwn 50060b0000c9a2e0 -dir 8c -p 0 add devs 0408
The following devices are already assigned in at least one entry:
0408
Would you like to continue (y/ )?y
14. Refresh the sym database
# ./symmask refresh
Refresh Symmetrix FA/SE directors with contents of SymMask database 000190105528 (y/ ) ? y
Symmetrix FA/SE directors updated with contents of SymMask Database 000190105528
15. ioscan to find the new device
# ioscan
H/W Path Class Description
==========================================================================
root
0 cell
0/0 ioa System Bus Adapter (805)
0/0/1 ba Local PCI-X Bus Adapter (783)
0/0/1/1/0 ba PCItoPCI Bridge
0/0/1/1/0/4/0 fc HP A9784-60002 PCI/PCI-X Fibre Channel FC/GigE Combo Adapter (FC Port 1)
0/0/1/1/0/4/0.74 fcp FCP Domain
0/0/1/1/0/4/0.74.0.8.0 ext_bus FCP Array Interface
0/0/1/1/0/4/0.74.0.8.0.0 target
0/0/1/1/0/4/0.74.0.8.0.0.0 disk EMC SYMMETRIX
0/0/1/1/0/4/0.74.0.8.0.7 target
0/0/1/1/0/4/0.74.0.8.0.7.5 disk EMC SYMMETRIX
0/0/1/1/0/4/0.74.0.8.0.7.6 disk EMC SYMMETRIX
0/0/1/1/0/4/0.74.0.8.0.7.7 disk EMC SYMMETRIX
0/0/1/1/0/4/0.74.0.8.0.8 target
0/0/1/1/0/4/0.74.0.8.0.8.0 disk EMC SYMMETRIX
0/0/1/1/0/4/0.74.0.8.0.8.1 disk EMC SYMMETRIX
0/0/1/1/0/4/0.74.0.8.0.8.2 disk EMC SYMMETRIX
0/0/1/1/0/4/0.74.0.8.0.8.3 disk EMC SYMMETRIX
0/0/1/1/0/4/0.74.0.8.0.8.4 disk EMC SYMMETRIX
0/0/1/1/0/4/0.74.0.8.0.8.5 disk EMC SYMMETRIX
0/0/1/1/0/4/0.74.0.8.0.8.6 disk EMC SYMMETRIX
0/0/1/1/0/4/0.74.0.8.0.8.7 disk EMC SYMMETRIX
0/0/1/1/0/4/0.74.0.255.0 ext_bus FCP Device Interface
0/0/1/1/0/4/0.74.0.255.0.8 target
0/0/1/1/0/4/0.74.0.255.0.8.0 ctl EMC SYMMETRIX
0/0/1/1/0/6/0 lan HP A9784-60002 PCI/PCI-X 1000Base-T FC/GigE Combo Adapter
0/0/2 ba Local PCI-X Bus Adapter (783)
0/0/2/1/0 ba PCItoPCI Bridge
0/0/2/1/0/4/0 fc HP A9784-60002 PCI/PCI-X Fibre Channel FC/GigE Combo Adapter (FC Port 1)
0/0/2/1/0/4/0.178 fcp FCP Domain
0/0/2/1/0/4/0.178.2.3.0 ext_bus FCP Array Interface
0/0/2/1/0/4/0.178.2.3.0.0 target
0/0/2/1/0/4/0.178.2.3.0.0.0 disk EMC SYMMETRIX
0/0/2/1/0/4/0.178.2.3.0.7 target
0/0/2/1/0/4/0.178.2.3.0.7.5 disk EMC SYMMETRIX
0/0/2/1/0/4/0.178.2.3.0.7.6 disk EMC SYMMETRIX
0/0/2/1/0/4/0.178.2.3.0.7.7 disk EMC SYMMETRIX
0/0/2/1/0/4/0.178.2.3.0.8 target
0/0/2/1/0/4/0.178.2.3.0.8.0 disk EMC SYMMETRIX
0/0/2/1/0/4/0.178.2.3.0.8.1 disk EMC SYMMETRIX
0/0/2/1/0/4/0.178.2.3.0.8.2 disk EMC SYMMETRIX
0/0/2/1/0/4/0.178.2.3.0.8.3 disk EMC SYMMETRIX
0/0/2/1/0/4/0.178.2.3.0.8.4 disk EMC SYMMETRIX
0/0/2/1/0/4/0.178.2.3.0.8.5 disk EMC SYMMETRIX
0/0/2/1/0/4/0.178.2.3.0.8.6 disk EMC SYMMETRIX
0/0/2/1/0/4/0.178.2.3.0.8.7 disk EMC SYMMETRIX
0/0/2/1/0/4/0.178.2.255.0 ext_bus FCP Device Interface
0/0/2/1/0/4/0.178.2.255.0.3 target
0/0/2/1/0/4/0.178.2.255.0.3.0 ctl EMC SYMMETRIX
0/0/2/1/0/4/0.178.4.255.0 ext_bus FCP Device Interface
0/0/2/1/0/4/0.178.4.255.0.0 target
0/0/2/1/0/4/0.178.4.255.0.0.1 tape IBM ULTRIUM-TD3
0/0/2/1/0/4/0.178.4.255.0.0.2 tape IBM ULTRIUM-TD3
0/0/2/1/0/6/0 lan HP A9784-60002 PCI/PCI-X 1000Base-T FC/GigE Combo Adapter
0/0/4 ba Local PCI-X Bus Adapter (783)
0/0/4/1/0 ext_bus SCSI Ultra320 A6961-60011
0/0/4/1/0.7 target
0/0/4/1/0.7.0 ctl Initiator
0/0/4/1/0.8 target
0/0/4/1/0.8.0 disk HP 73.4GMAX3073NC
0/0/4/1/0.10 target
0/0/4/1/0.10.0 disk HP 73.4GMAX3073NC
0/0/4/1/1 ext_bus SCSI Ultra320 A6961-60011
0/0/4/1/1.7 target
0/0/4/1/1.7.0 ctl Initiator
0/5 memory Memory
0/6 ipmi IPMI Controller
0/10 processor Processor
0/15 processor Processor
0/16 processor Processor
0/17 processor Processor
64 tty Virtual Console Client
65 tty Virtual Console Server
#
(I already know at this point it's not gonna work because the new disk doesn't appear up above.. those are already established sym disks that our previous admin did before he left.. but I'll continue on)
16. insf
# insf -ev
insf: Installing special files for sdisk instance 193 address 0/0/1/1/0/4/0.74.0.8.0.0.0
insf: Installing special files for sdisk instance 194 address 0/0/1/1/0/4/0.74.0.8.0.7.5
insf: Installing special files for sdisk instance 195 address 0/0/1/1/0/4/0.74.0.8.0.7.6
insf: Installing special files for sdisk instance 196 address 0/0/1/1/0/4/0.74.0.8.0.7.7
insf: Installing special files for sdisk instance 197 address 0/0/1/1/0/4/0.74.0.8.0.8.0
insf: Installing special files for sdisk instance 198 address 0/0/1/1/0/4/0.74.0.8.0.8.1
insf: Installing special files for sdisk instance 199 address 0/0/1/1/0/4/0.74.0.8.0.8.2
insf: Installing special files for sdisk instance 200 address 0/0/1/1/0/4/0.74.0.8.0.8.3
insf: Installing special files for sdisk instance 201 address 0/0/1/1/0/4/0.74.0.8.0.8.4
insf: Installing special files for sdisk instance 202 address 0/0/1/1/0/4/0.74.0.8.0.8.5
insf: Installing special files for sdisk instance 203 address 0/0/1/1/0/4/0.74.0.8.0.8.6
insf: Installing special files for sdisk instance 204 address 0/0/1/1/0/4/0.74.0.8.0.8.7
insf: Installing special files for sctl instance 11 address 0/0/1/1/0/4/0.74.0.255.0.8.0
insf: Installing special files for sdisk instance 181 address 0/0/2/1/0/4/0.178.2.3.0.0.0
insf: Installing special files for sdisk instance 182 address 0/0/2/1/0/4/0.178.2.3.0.7.5
insf: Installing special files for sdisk instance 183 address 0/0/2/1/0/4/0.178.2.3.0.7.6
insf: Installing special files for sdisk instance 184 address 0/0/2/1/0/4/0.178.2.3.0.7.7
insf: Installing special files for sdisk instance 185 address 0/0/2/1/0/4/0.178.2.3.0.8.0
insf: Installing special files for sdisk instance 186 address 0/0/2/1/0/4/0.178.2.3.0.8.1
insf: Installing special files for sdisk instance 187 address 0/0/2/1/0/4/0.178.2.3.0.8.2
insf: Installing special files for sdisk instance 188 address 0/0/2/1/0/4/0.178.2.3.0.8.3
insf: Installing special files for sdisk instance 189 address 0/0/2/1/0/4/0.178.2.3.0.8.4
insf: Installing special files for sdisk instance 190 address 0/0/2/1/0/4/0.178.2.3.0.8.5
insf: Installing special files for sdisk instance 191 address 0/0/2/1/0/4/0.178.2.3.0.8.6
insf: Installing special files for sdisk instance 192 address 0/0/2/1/0/4/0.178.2.3.0.8.7
insf: Installing special files for sctl instance 10 address 0/0/2/1/0/4/0.178.2.255.0.3.0
insf: Installing special files for stape instance 3 address 0/0/2/1/0/4/0.178.4.255.0.0.1
insf: Installing special files for stape instance 4 address 0/0/2/1/0/4/0.178.4.255.0.0.2
insf: Installing special files for sctl instance 1 address 0/0/4/1/0.7.0
insf: Installing special files for sdisk instance 0 address 0/0/4/1/0.8.0
insf: Installing special files for sdisk instance 1 address 0/0/4/1/0.10.0
insf: Installing special files for sctl instance 3 address 0/0/4/1/1.7.0
insf: Installing special files for ipmi instance 0 address 0/6
insf: Installing special files for pseudo driver cn
insf: Installing special files for pseudo driver mm
insf: Installing special files for pseudo driver iomem
insf: Installing special files for pseudo driver udp
insf: Installing special files for pseudo driver tcp
insf: Installing special files for pseudo driver rawip
insf: Installing special files for pseudo driver nuls
insf: Installing special files for pseudo driver ptym
insf: Installing special files for pseudo driver ptys
insf: Installing special files for pseudo driver ip
insf: Installing special files for pseudo driver arp
insf: Installing special files for pseudo driver tlcotsod
insf: Installing special files for pseudo driver dmem
insf: Installing special files for pseudo driver diag0
insf: Installing special files for pseudo driver tlcots
insf: Installing special files for pseudo driver tlclts
insf: Installing special files for pseudo driver devkrs
insf: Installing special files for pseudo driver dmp
insf: Installing special files for pseudo driver stcpmap
insf: Installing special files for pseudo driver dev_config
insf: Installing special files for pseudo driver strlog
insf: Installing special files for pseudo driver sad
insf: Installing special files for pseudo driver tels
insf: Installing special files for pseudo driver telm
insf: Installing special files for pseudo driver vols
insf: Installing special files for pseudo driver asyncdsk
insf: Installing special files for pseudo driver echo
insf: Installing special files for pseudo driver dlpi
insf: Installing special files for pseudo driver ptm
insf: Installing special files for pseudo driver pts
insf: Installing special files for pseudo driver diag1
insf: Installing special files for pseudo driver klog
insf: Installing special files for pseudo driver sy
insf: Installing special files for pseudo driver kepd
insf: Installing special files for pseudo driver diag2
insf: Installing special files for pseudo driver root
making rroot c 255 0xffffff
making root b 255 0xffffff
(still not showing up)
17. powermt config/save/symcfg discover
# powermt config
# powermt save
# ./symcfg discover
This operation may take up to a few minutes. Please be patient...
18. sympd list
This operation may take up to a few minutes. Please be patient...
# ./sympd list
Symmetrix ID: 000190105528
Device Name Directors Device
--------------------------- ------------- -------------------------------------
Cap
Physical Sym SA![]()
DA :IT Config Attribute Sts (MB)
--------------------------- ------------- -------------------------------------
/dev/rdsk/c20t0d0 0020 09C:0 16A:CB 2-Way Mir N/Grp'd VCM RW 3
/dev/rdsk/c20t7d5 03A3 09C:0 01D:C9 RAID-5 N/Grp'd (M) RW 107170
/dev/rdsk/c20t7d6 03A6 09C:0 01B:D6 RAID-5 N/Grp'd (M) RW 250064
/dev/rdsk/c20t7d7 03AD 09C:0 01C:D7 RAID-5 N/Grp'd (M) RW 250064
/dev/rdsk/c20t8d0 03B4 09C:0 01A:C8 RAID-5 N/Grp'd (M) RW 250064
/dev/rdsk/c20t8d1 03BB 09C:0 16D:D9 RAID-5 N/Grp'd (M) RW 250064
/dev/rdsk/c20t8d2 03C2 09C:0 16B:CA RAID-5 N/Grp'd (M) RW 250064
/dev/rdsk/c20t8d3 03C9 09C:0 01A:DB RAID-5 N/Grp'd (M) RW 250064
/dev/rdsk/c20t8d4 03D0 09C:0 16D:C6 RAID-5 N/Grp'd (M) RW 250064
/dev/rdsk/c20t8d5 03D7 09C:0 16B:D7 RAID-5 N/Grp'd (M) RW 250064
/dev/rdsk/c20t8d6 03DE 09C:0 16C:D8 RAID-5 N/Grp'd (M) RW 250064
/dev/rdsk/c20t8d7 03E5 09C:0 16A:C9 RAID-5 N/Grp'd RW 35723
/dev/rdsk/c22t0d0 0020 08C:0 16A:CB 2-Way Mir N/Grp'd VCM RW 3
/dev/rdsk/c22t7d5 03A3 08C:0 01D:C9 RAID-5 N/Grp'd (M) RW 107170
/dev/rdsk/c22t7d6 03A6 08C:0 01B:D6 RAID-5 N/Grp'd (M) RW 250064
/dev/rdsk/c22t7d7 03AD 08C:0 01C:D7 RAID-5 N/Grp'd (M) RW 250064
/dev/rdsk/c22t8d0 03B4 08C:0 01A:C8 RAID-5 N/Grp'd (M) RW 250064
/dev/rdsk/c22t8d1 03BB 08C:0 16D:D9 RAID-5 N/Grp'd (M) RW 250064
/dev/rdsk/c22t8d2 03C2 08C:0 16B:CA RAID-5 N/Grp'd (M) RW 250064
/dev/rdsk/c22t8d3 03C9 08C:0 01A:DB RAID-5 N/Grp'd (M) RW 250064
(not there)
# ./symmaskdb list devs -wwn 50060b0000c9a2e0
Symmetrix ID : 000190105528
Originator Port wwn : 50060b0000c9a2e0
User-generated Name : tartan/fcdo
Sym Dev LUN
Name Dir:P Physical Device Name VBUS TID SYMM HOST Attr Cap(MB)
------ ----- ----------------------- ---- --- ---- ---- ---- -------
03A3 8C:0 /dev/rdsk/c22t7d5 0 0 75 5 (M) 107170
03A6 8C:0 /dev/rdsk/c22t7d6 0 0 76 6 (M) 250064
03AD 8C:0 /dev/rdsk/c22t7d7 0 0 77 7 (M) 250064
03B4 8C:0 /dev/rdsk/c22t8d0 0 0 80 0 (M) 250064
03BB 8C:0 /dev/rdsk/c22t8d1 0 0 81 1 (M) 250064
03C2 8C:0 /dev/rdsk/c22t8d2 0 0 82 2 (M) 250064
03C9 8C:0 /dev/rdsk/c22t8d3 0 0 83 3 (M) 250064
03D0 8C:0 /dev/rdsk/c22t8d4 0 0 84 4 (M) 250064
03D7 8C:0 /dev/rdsk/c22t8d5 0 0 85 5 (M) 250064
03DE 8C:0 /dev/rdsk/c22t8d6 0 0 86 6 (M) 250064
03E5 8C:0 /dev/rdsk/c22t8d7 0 0 87 7 35723
0408 8C:0 Not Visible 0 0 8 N/A 35723
What am I doing wrong or missing?
dynamox
9 Legend
•
20.4K Posts
0
December 3rd, 2011 13:00
can you try mapping like this:
map dev "xxxx" to dir "xx:x", vbus="0" target="1" lun="000";
markdf
76 Posts
0
December 4th, 2011 18:00
# ./symcfg list -fa 8c -p 0 -addresses -avail
Symmetrix ID: 000190105528 (Local)
Director Device Name Attr Address
---------------------- ----------------------------- ---- --------------
Ident Symbolic Port Sym Physical VBUS TID LUN
------ -------- ---- ---- ----------------------- ---- --- ---
FA-8C 08C 0 0020 /dev/rdsk/c22t0d0 VCM 0 00 000
0351 Not Visible 0 00 001
0352 Not Visible 0 00 002
0353 Not Visible 0 00 003
0354 Not Visible 0 00 004
0355 Not Visible 0 00 005
0356 Not Visible 0 00 006
0357 Not Visible 0 00 007
0408 Not Visible 0 00 008
- AVAILABLE 0 00 009 *
(gonna try another free single device - 0430 - and use lun 009.. all the vbus' and targets report as 0, from what it looks like above)
# ./symconfigure -f addspace/tempmap2.cmd preview
Establishing a configuration change session...............Established.
Error occurred while Parsing change number 1:
An invalid vbus mapping value was specified
Terminating the configuration change session..............Done.
The configuration change session has failed.
# cat addspace/tempmap2.cmd
map dev 0430 to dir 8C:0, vbus=0 target=0 lun=009;
??
thanks for helping me with this.
dynamox
9 Legend
•
20.4K Posts
0
December 4th, 2011 19:00
for HPUX addresses go from 0-7 and then you have to increment the target by one. Did you get that error when you ran it with the example i gave you ?
markdf
76 Posts
0
December 5th, 2011 05:00
Okay, I'm just a little confused. The line I used to map was:
map dev 0430 to dir 8C:0, vbus=0 target=0 lun=009;
I got the vbus=0 and target=0 based on the info from the available addresses on the server (see two posts above) where the VBUS column read as 0 and the TID column read as 0.. I also tried multiple combinations to no avail, and yes, the target=1, but I kept all vbus to 0. Are you saying the line should read:
map dev 0430 to dir 8C:0, vbus=1 target=1 lun=009;
because I am using lun 009? I'll try it.
dynamox
9 Legend
•
20.4K Posts
0
December 5th, 2011 05:00
Can you also post output from symcfg list -sid XXX -dir 8c -p 0 -v
markdf
76 Posts
0
December 5th, 2011 05:00
Nope, still get a vbus error:
# ./symconfigure -f addspace/tempmap2.cmd prev
Establishing a configuration change session...............Established.
Error occurred while Parsing change number 1:
An invalid vbus mapping value was specified
Terminating the configuration change session..............Done.
The configuration change session has failed.
# cat addspace/tempmap2.cmd
map dev 0430 to dir 8C:0, vbus=1 target=1 lun=009;
dynamox
9 Legend
•
20.4K Posts
0
December 5th, 2011 05:00
Try the example i gave above..exact options.