- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: Problem with armdiscover & armdsp
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-07-2005 12:50 AM
тАО09-07-2005 12:50 AM
Solution/opt/sanmgr/hostagent/config/commIpAddr.txt
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-07-2005 01:06 AM
тАО09-07-2005 01:06 AM
Re: Problem with armdiscover & armdsp
Thank you very much!!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-07-2005 01:08 AM
тАО09-07-2005 01:08 AM
Re: Problem with armdiscover & armdsp
This could take several minutes ...
HP-A6255A /dev/rscsi/c5t15d0 S521K1412016 smcp1
HP 36.4G-ST336754LC /dev/dsk/c2t0d0 3KQ03ET500007531 smcp1
HPQ-BF03658242 /dev/dsk/c5t0d0 3KQ04ESE00007529 smcp1
HP-A6255A /dev/rscsi/c4t15d0 S51PK1411833 smcp1
HPQ-BF03658242 /dev/dsk/c4t0d0 3KQ04EPQ00007529 smcp1
HP 36.4G-ST336754LC /dev/dsk/c2t1d0 3KQ03EYL00007531 smcp1
# armdsp -i
No devices found.
But seems like armdsp can't show... Will continue to debug! Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-07-2005 01:12 AM
тАО09-07-2005 01:12 AM
Re: Problem with armdiscover & armdsp
/opt/sanmgr/hostagent/config/commIpAddr.txt
Was the old address inside?
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-07-2005 01:14 AM
тАО09-07-2005 01:14 AM
Re: Problem with armdiscover & armdsp
But something strange with armdsp...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-07-2005 03:33 AM
тАО09-07-2005 03:33 AM
Re: Problem with armdiscover & armdsp
But are you sure to have a VA???
The only thing I can see is 1 dual connected or 2 single connected DS2405 and some disks.
The DS2405 can either be a standalone JBOD or an extension to a VA. Both look exactly the same in front view, except it's written "DS2404" or "vitual array" on it.
The ioscan you posted shows 8 or 16 disks, depends on dual/single path to it.
Please provide a full ioscan -fn.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-14-2005 11:54 PM
тАО09-14-2005 11:54 PM
Re: Problem with armdiscover & armdsp
Full result of ioscan -fn
Class I H/W Path Driver S/W State H/W Type Description
=============================================================================
root 0 root CLAIMED BUS_NEXUS
ioa 0 0 sba CLAIMED BUS_NEXUS System Bus Adapter (880)
ba 0 0/0 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
usb 0 0/0/1/0 hcd CLAIMED INTERFACE NEC USB Interface
usbhub 0 0/0/1/0.1 hub CLAIMED DEVICE USB Root Hub
usb 1 0/0/1/1 hcd CLAIMED INTERFACE NEC USB Interface
usbhub 1 0/0/1/1.1 hub CLAIMED DEVICE USB Root Hub
/dev/hub
usb 2 0/0/1/2 ehci CLAIMED INTERFACE NEC USB Interface
sideba 0 0/0/2/0 side_ba CLAIMED INTERFACE CMD IDE controller
ext_bus 0 0/0/2/0.0 side CLAIMED INTERFACE IDE Primary Channel
target 0 0/0/2/0.0.0 tgt CLAIMED DEVICE
disk 0 0/0/2/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-C
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
target 1 0/0/2/0.0.7 tgt CLAIMED DEVICE
ctl 0 0/0/2/0.0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c0t7d0
ext_bus 1 0/0/2/0.1 side CLAIMED INTERFACE IDE Secondary Channel
target 2 0/0/2/0.1.7 tgt CLAIMED DEVICE
ctl 1 0/0/2/0.1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c1t7d0
ba 1 0/1 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
ext_bus 2 0/1/1/0 c8xx CLAIMED INTERFACE SCSI C1010 Ultra160 Wide LVD
target 3 0/1/1/0.0 tgt CLAIMED DEVICE
disk 2 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 36.4GST336754LC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
target 4 0/1/1/0.1 tgt CLAIMED DEVICE
disk 1 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 36.4GST336754LC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0
target 5 0/1/1/0.7 tgt CLAIMED DEVICE
ctl 2 0/1/1/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c2t7d0
ext_bus 3 0/1/1/1 c8xx CLAIMED INTERFACE SCSI C1010 Ultra160 Wide LVD
target 6 0/1/1/1.7 tgt CLAIMED DEVICE
ctl 3 0/1/1/1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c3t7d0
lan 0 0/1/2/0 igelan CLAIMED INTERFACE HP PCI 1000Base-T Core
ba 2 0/2 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
ba 3 0/2/1/0 PCItoPCI CLAIMED BUS_NEXUS PCItoPCI Bridge
fc 0 0/2/1/0/4/0 fcd CLAIMED INTERFACE HP 2Gb PCI/PCI-X Fibre Channel FC/GigE Dual Port Combo Adapter
/dev/fcd0
fcp 0 0/2/1/0/4/0.8 fcd_fcp CLAIMED INTERFACE FCP Protocol Adapter
ext_bus 4 0/2/1/0/4/0.8.0.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
target 7 0/2/1/0/4/0.8.0.255.0.0 tgt CLAIMED DEVICE
disk 3 0/2/1/0/4/0.8.0.255.0.0.0 sdisk CLAIMED DEVICE HPQ BF03658242
/dev/dsk/c4t0d0 /dev/rdsk/c4t0d0
target 8 0/2/1/0/4/0.8.0.255.0.1 tgt CLAIMED DEVICE
disk 4 0/2/1/0/4/0.8.0.255.0.1.0 sdisk CLAIMED DEVICE HPQ BF03658242
/dev/dsk/c4t1d0 /dev/rdsk/c4t1d0
target 9 0/2/1/0/4/0.8.0.255.0.2 tgt CLAIMED DEVICE
disk 5 0/2/1/0/4/0.8.0.255.0.2.0 sdisk CLAIMED DEVICE HPQ BF03658242
/dev/dsk/c4t2d0 /dev/rdsk/c4t2d0
target 10 0/2/1/0/4/0.8.0.255.0.3 tgt CLAIMED DEVICE
disk 6 0/2/1/0/4/0.8.0.255.0.3.0 sdisk CLAIMED DEVICE HPQ BF03658242
/dev/dsk/c4t3d0 /dev/rdsk/c4t3d0
target 11 0/2/1/0/4/0.8.0.255.0.4 tgt CLAIMED DEVICE
disk 7 0/2/1/0/4/0.8.0.255.0.4.0 sdisk CLAIMED DEVICE HPQ BF03658242
/dev/dsk/c4t4d0 /dev/rdsk/c4t4d0
target 12 0/2/1/0/4/0.8.0.255.0.5 tgt CLAIMED DEVICE
disk 8 0/2/1/0/4/0.8.0.255.0.5.0 sdisk CLAIMED DEVICE HPQ BF03658242
/dev/dsk/c4t5d0 /dev/rdsk/c4t5d0
target 13 0/2/1/0/4/0.8.0.255.0.6 tgt CLAIMED DEVICE
disk 9 0/2/1/0/4/0.8.0.255.0.6.0 sdisk CLAIMED DEVICE HPQ BF03658242
/dev/dsk/c4t6d0 /dev/rdsk/c4t6d0
target 14 0/2/1/0/4/0.8.0.255.0.7 tgt CLAIMED DEVICE
disk 10 0/2/1/0/4/0.8.0.255.0.7.0 sdisk CLAIMED DEVICE HPQ BF03658242
/dev/dsk/c4t7d0 /dev/rdsk/c4t7d0
target 15 0/2/1/0/4/0.8.0.255.0.15 tgt CLAIMED DEVICE
ctl 4 0/2/1/0/4/0.8.0.255.0.15.0 sctl CLAIMED DEVICE HP A6255A
/dev/rscsi/c4t15d0
lan 1 0/2/1/0/6/0 igelan CLAIMED INTERFACE HP A9784-60001 PCI/PCI-X 1000Base-T FC/GigE Combo Adapter
ba 4 0/3 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
ba 5 0/3/1/0 PCItoPCI CLAIMED BUS_NEXUS PCItoPCI Bridge
fc 1 0/3/1/0/4/0 fcd CLAIMED INTERFACE HP 2Gb PCI/PCI-X Fibre Channel FC/GigE Dual Port Combo Adapter
/dev/fcd1
fcp 1 0/3/1/0/4/0.8 fcd_fcp CLAIMED INTERFACE FCP Protocol Adapter
ext_bus 5 0/3/1/0/4/0.8.0.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
target 16 0/3/1/0/4/0.8.0.255.0.0 tgt CLAIMED DEVICE
disk 11 0/3/1/0/4/0.8.0.255.0.0.0 sdisk CLAIMED DEVICE HPQ BF03658242
/dev/dsk/c5t0d0 /dev/rdsk/c5t0d0
target 17 0/3/1/0/4/0.8.0.255.0.1 tgt CLAIMED DEVICE
disk 12 0/3/1/0/4/0.8.0.255.0.1.0 sdisk CLAIMED DEVICE HPQ BF03658242
/dev/dsk/c5t1d0 /dev/rdsk/c5t1d0
target 18 0/3/1/0/4/0.8.0.255.0.2 tgt CLAIMED DEVICE
disk 13 0/3/1/0/4/0.8.0.255.0.2.0 sdisk CLAIMED DEVICE HPQ BF03658242
/dev/dsk/c5t2d0 /dev/rdsk/c5t2d0
target 19 0/3/1/0/4/0.8.0.255.0.3 tgt CLAIMED DEVICE
disk 14 0/3/1/0/4/0.8.0.255.0.3.0 sdisk CLAIMED DEVICE HPQ BF03658242
/dev/dsk/c5t3d0 /dev/rdsk/c5t3d0
target 20 0/3/1/0/4/0.8.0.255.0.4 tgt CLAIMED DEVICE
disk 15 0/3/1/0/4/0.8.0.255.0.4.0 sdisk CLAIMED DEVICE HPQ BF03658242
/dev/dsk/c5t4d0 /dev/rdsk/c5t4d0
target 21 0/3/1/0/4/0.8.0.255.0.5 tgt CLAIMED DEVICE
disk 16 0/3/1/0/4/0.8.0.255.0.5.0 sdisk CLAIMED DEVICE HPQ BF03658242
/dev/dsk/c5t5d0 /dev/rdsk/c5t5d0
target 22 0/3/1/0/4/0.8.0.255.0.6 tgt CLAIMED DEVICE
disk 17 0/3/1/0/4/0.8.0.255.0.6.0 sdisk CLAIMED DEVICE HPQ BF03658242
/dev/dsk/c5t6d0 /dev/rdsk/c5t6d0
target 23 0/3/1/0/4/0.8.0.255.0.7 tgt CLAIMED DEVICE
disk 18 0/3/1/0/4/0.8.0.255.0.7.0 sdisk CLAIMED DEVICE HPQ BF03658242
/dev/dsk/c5t7d0 /dev/rdsk/c5t7d0
target 24 0/3/1/0/4/0.8.0.255.0.15 tgt CLAIMED DEVICE
ctl 5 0/3/1/0/4/0.8.0.255.0.15.0 sctl CLAIMED DEVICE HP A6255A
/dev/rscsi/c5t15d0
lan 2 0/3/1/0/6/0 igelan CLAIMED INTERFACE HP A9784-60001 PCI/PCI-X 1000Base-T FC/GigE Combo Adapter
ba 6 0/4 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
ba 7 0/6 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
ba 8 0/7 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
tty 0 0/7/1/0 asio0 CLAIMED INTERFACE PCI SimpleComm (103c1290)
/dev/diag/mux0 /dev/mux0 /dev/tty0p0
tty 1 0/7/1/1 asio0 CLAIMED INTERFACE PCI Serial (103c1048)
/dev/GSPdiag1 /dev/diag/mux1 /dev/mux1 /dev/tty1p0 /dev/tty1p2 /dev/tty1p4
unknown -1 0/7/2/0 UNCLAIMED UNKNOWN PCI Display (10025159)
memory 0 8 memory CLAIMED MEMORY Memory
ipmi 0 16 ipmi CLAIMED INTERFACE IPMI Controller
/dev/ipmi
processor 0 128 processor CLAIMED PROCESSOR Processor
processor 1 129 processor CLAIMED PROCESSOR Processor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-15-2005 02:03 AM
тАО09-15-2005 02:03 AM
Re: Problem with armdiscover & armdsp
I'm quite sure you have 1 or 2 direct connected DS2405 JBODs - no VA7xxx.
The Commandview SDM software works also with this device, but you'll have only a view options.
If you download a version from HP's website, there should be the manual included - at least for the VA command sets. Try it!
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-15-2005 06:55 PM
тАО09-15-2005 06:55 PM
Re: Problem with armdiscover & armdsp
I've found this from product specification: HP dual rp3440 server,2*1GHz,2G,2*36G,2*NIC,2*FC,2*DS2405(8*36G),DDS4,1*E33 Rack,1*CRT TC,HP UX11.i-MC/SG/MD,3Y5*9&Installation,Eng.Doc
THANKS!!!
I've just thought that this disk arrays is the same that I have on another HP:
# armdsp -i
Product ID: HP-A6189B
Device Type: Virtual Disk Array
Alias: va7110
World Wide Name: 50060b000014f9f5
Unique ID: HPA6189B00SG410J0008
Serial Number: 00SG410J0008
Management Path: scp1:/dev/rscsi/c7t0d0
Sorry, for that.... :'-(
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-21-2005 09:08 PM
тАО09-21-2005 09:08 PM
Re: Problem with armdiscover & armdsp
recently I saw the error
failed to obtain remote database interface to host: localhost
after updating CommandView SDM from Version 1.07 to 1.09.01.
Tuning the kernel parameter max_thread_proc from 64 to 256 was the solution!
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!