- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- new hba presentation
Categories
Company
Local Language
Forums
Discussions
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
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
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
01-25-2007 09:27 PM
01-25-2007 09:27 PM
new hba presentation
Ok, here is my problem.
I have a two node hpux11.23 ia cluster.
In each i had one hba with two fibre ports.
One of them was attached to the switch, the other was not.
I noted that powerpath was not install either.
The port tha was not attaches got fixed and the disks are now presented by both ways.
here is my ioscan result:
>ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
=============================================================================
disk 0 0/0/2/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-C
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 36.4GMAU3036NC
/dev/dsk/c2t0d0 /dev/dsk/c2t0d0s2 /dev/rdsk/c2t0d0 /dev/rdsk/c2t0d0s2
/dev/dsk/c2t0d0s1 /dev/dsk/c2t0d0s3 /dev/rdsk/c2t0d0s1 /dev/rdsk/c2t0d0s3
disk 2 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 36.4GMAU3036NC
/dev/dsk/c2t1d0 /dev/dsk/c2t1d0s2 /dev/rdsk/c2t1d0 /dev/rdsk/c2t1d0s2
/dev/dsk/c2t1d0s1 /dev/dsk/c2t1d0s3 /dev/rdsk/c2t1d0s1 /dev/rdsk/c2t1d0s3
disk 3 0/2/1/0.5.12.0.0.0.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t0d0 /dev/rdsk/c5t0d0
disk 4 0/2/1/0.5.12.0.0.0.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t0d1 /dev/rdsk/c5t0d1
disk 5 0/2/1/0.5.12.0.0.1.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d0 /dev/rdsk/c5t1d0
disk 6 0/2/1/0.5.12.0.0.1.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d1 /dev/rdsk/c5t1d1
disk 7 0/2/1/0.5.12.0.0.1.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d2 /dev/rdsk/c5t1d2
disk 8 0/2/1/0.5.12.0.0.1.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d3 /dev/rdsk/c5t1d3
disk 9 0/2/1/0.5.12.0.0.1.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d4 /dev/rdsk/c5t1d4
disk 10 0/2/1/0.5.12.0.0.1.6 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d6 /dev/rdsk/c5t1d6
disk 11 0/2/1/0.5.12.0.0.1.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d7 /dev/rdsk/c5t1d7
disk 12 0/2/1/0.5.12.0.0.2.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t2d0 /dev/rdsk/c5t2d0
disk 13 0/2/1/0.5.12.0.0.2.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t2d1 /dev/rdsk/c5t2d1
disk 14 0/2/1/0.5.12.0.0.2.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t2d2 /dev/rdsk/c5t2d2
disk 15 0/2/1/0.5.12.0.0.2.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t2d3 /dev/rdsk/c5t2d3
disk 16 0/2/1/1.6.12.0.0.0.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c6t0d0 /dev/rdsk/c6t0d0
disk 17 0/2/1/1.6.12.0.0.1.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 18 0/2/1/1.6.12.0.0.1.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 19 0/2/1/1.6.12.0.0.1.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 20 0/2/1/1.6.12.0.0.1.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 21 0/2/1/1.6.12.0.0.1.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 22 0/2/1/1.6.12.0.0.1.6 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 23 0/2/1/1.6.12.0.0.1.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 24 0/2/1/1.6.12.0.0.2.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 25 0/2/1/1.6.12.0.0.2.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 26 0/2/1/1.6.12.0.0.2.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 27 0/2/1/1.6.12.0.0.2.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
As you can see, there are not dispositive files.
I tried to start my SGCLUSTER and the machine halted.
I am not sure what steps do i have to do, ones the disks are presented the new way.
Could you pleas help me ?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-25-2007 09:50 PM
01-25-2007 09:50 PM
Re: new hba presentation
Then you need to add th erelevant Alternate Link into it's proper VG with the vgextend command, and then import those changes to the other node
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-25-2007 10:08 PM
01-25-2007 10:08 PM
Re: new hba presentation
Hi:
I have made the insf -e command before you answered. I reboot the system and know is in
a boot crash cycle.
System Console is on the Built-In Serial Interface
Logical volume 64, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x2 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 8388608
Starting the STREAMS daemons-phase 1
msgcnt 1 vxfs: mesg 037: vx_metaioerr - vx_dirlook - /dev/root file system meta
data read error in block 200688
msgcnt 2 vxfs: mesg 017: vx_dirlook - / file system inode 2812 marked bad incore
?vxfs msgcnt 2 offset 0x00000000 0 0 0 0
?vxfs msgcnt 2 offset 0x00000010 0 0 0 0
?vxfs msgcnt 2 offset 0x00000020 0 0 0 0
?vxfs msgcnt 2 offset 0x00000030 0 0 0 0
?vxfs msgcnt 2 offset 0x00000040 0 0 0 0
?vxfs msgcnt 2 offset 0x00000050 0 0 0 0
?vxfs msgcnt 2 offset 0x00000060 0 0 0 0
?vxfs msgcnt 2 offset 0x00000070 0 0 0 0
?vxfs msgcnt 2 offset 0x00000080 0 0 0 0
?vxfs msgcnt 2 offset 0x00000090 0 0 0 0
?vxfs msgcnt 2 offset 0x000000a0 0 0 0 0
?vxfs msgcnt 2 offset 0x000000b0 0 0
The device file /dev/rroot does not exist or is not correct.
Automatic checks of the root file system not performed.
Calling function e0000000010f73c0 for Shutdown State 8 type 0x2
What should i do know ? I guess to start up in lvm mode right ?
Could you be a little more specific with the comands i have to execute ? Or if you know any documentation where is described ??
Thanks a lot
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-25-2007 10:35 PM
01-25-2007 10:35 PM
Re: new hba presentation
First you need to get the system booting before you can do any remedies to the io_tree or device files. So if you have access to the SAN switch conencted to this host login ito it and disable the switch port from the switch end and let the system boot completely. Or if you have a SAN team ask them to disable the switch port connected to new HBA. By booting the system we might get more opportunity to troubleshoot and also an opportunity to install powerpath if required.
If it were a brocade silkworm switch...
Admin>alishow *HOSTNAME* (find the nport)
Lets say nport is 0x5f6400 then, the port is connected to switch with domain id "95" and aread id "100". login to that switch and run switchshow and find the "slot and port" of the area ID 100 and issue the following command.
Admin> portdisable slot_id/port_id
Then get your system booting......
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-25-2007 10:48 PM
01-25-2007 10:48 PM
Re: new hba presentation
Hi:
More info.
First of all I installed powerpath, but i didn´t made the insf -e command, the vgextend and export to other nodes as the previos answers tells.
Powerpath was not "seeing" the new alternate path.
I made then the insf -e command and then powermt display displayed the correct information.
Finally i reboot the system and know i am blocked because of the boot error.
Could you please help me booting the system ? I could i correct the boot problem ?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-25-2007 11:39 PM
01-25-2007 11:39 PM
Re: new hba presentation
As I have mentioned earlier, disabling the port from the switch end for the new HBA should most likely get you booting. I guess, the Server is hung querying the new luns during the boot process. So by disabling the server is not allowed to see those luns anymore, and you can bypass the hung state. Once we boot up , we can run cstm commands on the fc card and check its validity or do some other troubleshooting, But troubleshooting when having multiple times at a time sounds like .."Beating around a wrong bush, Bush never-the-less".... So take it one step at a time....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-25-2007 11:40 PM
01-25-2007 11:40 PM
Re: new hba presentation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-25-2007 11:58 PM
01-25-2007 11:58 PM
Re: new hba presentation
Hi:
Ok, i will talk with the SAN group but...i did not post the worse part....:(
System Panic:
panic: all VFS_MOUNTROOTs failed: NEED DRIVERS ?????
Stack Trace:
IP Function Name
0xe000000000f46580 vfs_mountroot+0x1d0
0xe000000001247220 im_preinitrc+0x300
0xe000000001614350 DoCalllist+0x3a0
End of Stack Trace
linkstamp: Thu Jan 25 15:49:33 MET 2007
_release_version: @(#) $Revision: vmunix: B11.23_LR FLAVOR=perf Fri Aug 29
22:35:38 PDT 2003 $
It seems that there is a problem with the disk...
what do you think ?
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2007 01:17 AM
01-26-2007 01:17 AM
Re: new hba presentation
Sounds like, its failing to configure some drivers, thus failing to recognize or mount the FS. I would wait for more experienced admin to respond with their past experience before, you start following my previous suggestions....
Have you tried calling in HP support center. Passing on this error messages to them , can get you solutions faster sometimes, because they can get WTEC engineers, if it were more serious...