1755364 Members
3577 Online
108832 Solutions
New Discussion юеВ

vmunix messages

 
SOLVED
Go to solution
Carme Torca
Super Advisor

vmunix messages

Hi, I have seen in the /var/adm/syslog/syslog.log, this messages from vmunix.
It's something wrong?, What is the meaning?
Thanks!!
Carmen.
----------------
Dec 22 16:05:30 scs30 vmunix: td_create_domain_node: hw_path = ^D^D. For backward compatability domain
8 is not allowed.
Dec 22 16:05:30 scs30 vmunix: Configure the switch to assign a domain value other than 8.
Dec 22 16:05:30 scs30 vmunix: Domains > 8 will not be recognized till this problem is fixed.
Users are not too bad ;-)
7 REPLIES 7
Michael Schulte zur Sur
Honored Contributor
Solution

Re: vmunix messages

Steven E. Protter
Exalted Contributor

Re: vmunix messages

Id' say your hostname (/etc/rc.cofig.d/netconf) or domain name (/etc/resolv.conf) exceeds eight characters.

HP-UX doesn't like that at all.

Fix it and the message might go away.

hebron is okay as a hostname
hebron.juf.net is okay as a hostname

jerusalem is NOT okay as a hostname

hebron.investmenttool.com Is probably not okay as a hostname, but it can be done with the artful use of BIND 9.2.0 in the DNS database.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Jeff Schussele
Honored Contributor

Re: vmunix messages

Hi Carme,

This looks to me like an fibre switch zoning issue.
The way the domains are zoned & presented to the fibre channel HBA are breaking a rule.

Also you might want to check if you have the latest Fibre Channel Mass Storage Patch - PHKL_27751:

http://www2.itrc.hp.com/service/patch/patchDetail.do?BC=patch.breadcrumb.search|&patchid=PHKL_27751&context=hpux:800:11:11

HTH,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
Ashwani Kashyap
Honored Contributor

Re: vmunix messages

looks like your HBA is fabric enabled but the switch is not , it is still in private loop .

Domain ID of 8 is used for private or arbitrated loop , It is a reserved id . Dependng on the switch offset the fabric domain ID will be different .

For eg . for the hardware addrress :
8/12/.8.0 , 8=Bus_converter
12=Adapter
8=Protocol Type , reserved for private loop .

So if the switch is not operating in private loop mode and neither is HBA , change the domain ID of the switch form 8 to a value prefferably lower than 8 .







Carme Torca
Super Advisor

Re: vmunix messages

Hi,

And how I could see the path which is it?
At the ioscan, I couldn't see the .8 (??), How could I see if it's a disk??, or it's sure that it's a disk?

Thanks a lot of!!!
Carmen.

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 (803)
ba 0 0/0 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
lan 0 0/0/0/0 btlan3 CLAIMED INTERFACE HP PCI 10/100Base-TX Core
/dev/diag/lan0 /dev/ether0
ext_bus 0 0/0/1/0 c720 CLAIMED INTERFACE SCSI C895 Ultra Wide Single-Ended
target 0 0/0/1/0.1 tgt CLAIMED DEVICE
disk 4 0/0/1/0.1.0 sdisk CLAIMED DEVICE HP DVD-ROM 305
/dev/dsk/c0t1d0 /dev/rdsk/c0t1d0
target 1 0/0/1/0.3 tgt CLAIMED DEVICE
tape 0 0/0/1/0.3.0 stape CLAIMED DEVICE HP C1537A
/dev/rmt/0m /dev/rmt/c0t3d0BEST /dev/rmt/c0t3d0DDS
/dev/rmt/0mb /dev/rmt/c0t3d0BESTb /dev/rmt/c0t3d0DDSb
/dev/rmt/0mn /dev/rmt/c0t3d0BESTn /dev/rmt/c0t3d0DDSn
/dev/rmt/0mnb /dev/rmt/c0t3d0BESTnb /dev/rmt/c0t3d0DDSnb
target 2 0/0/1/0.7 tgt CLAIMED DEVICE
ctl 0 0/0/1/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c0t7d0
ext_bus 1 0/0/2/0 c720 CLAIMED INTERFACE SCSI C875 Ultra Wide Single-Ended
target 3 0/0/2/0.6 tgt CLAIMED DEVICE
disk 0 0/0/2/0.6.0 sdisk CLAIMED DEVICE SEAGATE ST318404LC
/dev/dsk/c1t6d0 /dev/rdsk/c1t6d0
target 4 0/0/2/0.7 tgt CLAIMED DEVICE
ctl 1 0/0/2/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c1t7d0
ext_bus 2 0/0/2/1 c720 CLAIMED INTERFACE SCSI C875 Ultra Wide Single-Ended
target 5 0/0/2/1.6 tgt CLAIMED DEVICE
disk 1 0/0/2/1.6.0 sdisk CLAIMED DEVICE SEAGATE ST318404LC
/dev/dsk/c2t6d0 /dev/rdsk/c2t6d0
target 6 0/0/2/1.7 tgt CLAIMED DEVICE
ctl 2 0/0/2/1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c2t7d0
tty 0 0/0/4/0 asio0 UNCLAIMED UNKNOWN PCI BaseSystem (103c128d)
tty 2 0/0/4/1 asio0 CLAIMED INTERFACE PCI Serial (103c1048)
/dev/GSPdiag2 /dev/diag/mux2 /dev/mux2 /dev/tty2p1
ba 1 0/1 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 2 0/2 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 3 0/4 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
lan 1 0/4/0/0 btlan5 CLAIMED INTERFACE HP A5230A/B5509BA PCI 10/100Base-TX A
ddon
/dev/diag/lan1 /dev/ether1 /dev/lan1
ba 4 0/5 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
lan 2 0/5/0/0 btlan5 CLAIMED INTERFACE HP A5230A/B5509BA PCI 10/100Base-TX A
ddon
/dev/diag/lan2 /dev/ether2 /dev/lan2
ba 5 0/8 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 6 0/10 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 7 0/12 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
fc 0 0/12/0/0 td CLAIMED INTERFACE HP Tachyon TL/TS Fibre Channel Mass S
torage Adapter
/dev/td0
fcp 2 0/12/0/0.4 fcp CLAIMED INTERFACE FCP Domain
ext_bus 9 0/12/0/0.4.30.0.0 fcparray CLAIMED INTERFACE FCP Array Interface
target 7 0/12/0/0.4.30.0.0.0 tgt CLAIMED DEVICE
disk 46 0/12/0/0.4.30.0.0.0.0 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c9t0d0 /dev/rdsk/c9t0d0
disk 47 0/12/0/0.4.30.0.0.0.1 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c9t0d1 /dev/rdsk/c9t0d1
disk 49 0/12/0/0.4.30.0.0.0.2 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c9t0d2 /dev/rdsk/c9t0d2
disk 50 0/12/0/0.4.30.0.0.0.3 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c9t0d3 /dev/rdsk/c9t0d3
disk 51 0/12/0/0.4.30.0.0.0.4 sdisk CLAIMED DEVICE DGC C4700WDR1
/dev/dsk/c9t0d4 /dev/rdsk/c9t0d4
disk 52 0/12/0/0.4.30.0.0.0.5 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c9t0d5 /dev/rdsk/c9t0d5
disk 53 0/12/0/0.4.30.0.0.0.6 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c9t0d6 /dev/rdsk/c9t0d6
disk 59 0/12/0/0.4.30.0.0.0.7 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c9t0d7 /dev/rdsk/c9t0d7
target 8 0/12/0/0.4.30.0.0.1 tgt CLAIMED DEVICE
disk 61 0/12/0/0.4.30.0.0.1.0 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c9t1d0 /dev/rdsk/c9t1d0
disk 62 0/12/0/0.4.30.0.0.1.1 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c9t1d1 /dev/rdsk/c9t1d1
disk 63 0/12/0/0.4.30.0.0.1.2 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c9t1d2 /dev/rdsk/c9t1d2
disk 64 0/12/0/0.4.30.0.0.1.3 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c9t1d3 /dev/rdsk/c9t1d3
disk 65 0/12/0/0.4.30.0.0.1.4 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c9t1d4 /dev/rdsk/c9t1d4
disk 66 0/12/0/0.4.30.0.0.1.5 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c9t1d5 /dev/rdsk/c9t1d5
disk 67 0/12/0/0.4.30.0.0.1.6 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c9t1d6 /dev/rdsk/c9t1d6
ext_bus 7 0/12/0/0.4.30.255.0 fcpdev CLAIMED INTERFACE FCP Device Interface
target 9 0/12/0/0.4.30.255.0.0 tgt CLAIMED DEVICE
ctl 5 0/12/0/0.4.30.255.0.0.0 sctl CLAIMED DEVICE DGC C4700
/dev/rscsi/c7t0d0
ctl 6 0/12/0/0.4.30.255.0.0.1 sctl CLAIMED DEVICE DGC C4700
/dev/rscsi/c7t0d1
ctl 7 0/12/0/0.4.30.255.0.0.2 sctl CLAIMED DEVICE DGC C4700
/dev/rscsi/c7t0d2
ctl 8 0/12/0/0.4.30.255.0.0.3 sctl CLAIMED DEVICE DGC C4700
/dev/rscsi/c7t0d3
ctl 9 0/12/0/0.4.30.255.0.0.4 sctl CLAIMED DEVICE DGC C4700
/dev/rscsi/c7t0d4
ctl 10 0/12/0/0.4.30.255.0.0.5 sctl CLAIMED DEVICE DGC C4700
/dev/rscsi/c7t0d5
ctl 11 0/12/0/0.4.30.255.0.0.6 sctl CLAIMED DEVICE DGC C4700
/dev/rscsi/c7t0d6
ctl 12 0/12/0/0.4.30.255.0.0.7 sctl CLAIMED DEVICE DGC C4700
/dev/rscsi/c7t0d7
ext_bus 10 0/12/0/0.4.31.0.0 fcparray CLAIMED INTERFACE FCP Array Interface
target 10 0/12/0/0.4.31.0.0.0 tgt CLAIMED DEVICE
disk 45 0/12/0/0.4.31.0.0.0.0 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c10t0d0 /dev/rdsk/c10t0d0
disk 48 0/12/0/0.4.31.0.0.0.1 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c10t0d1 /dev/rdsk/c10t0d1
disk 54 0/12/0/0.4.31.0.0.0.2 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c10t0d2 /dev/rdsk/c10t0d2
disk 55 0/12/0/0.4.31.0.0.0.3 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c10t0d3 /dev/rdsk/c10t0d3
disk 56 0/12/0/0.4.31.0.0.0.4 sdisk CLAIMED DEVICE DGC C4700WDR1
/dev/dsk/c10t0d4 /dev/rdsk/c10t0d4
disk 57 0/12/0/0.4.31.0.0.0.5 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c10t0d5 /dev/rdsk/c10t0d5
disk 58 0/12/0/0.4.31.0.0.0.6 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c10t0d6 /dev/rdsk/c10t0d6
disk 60 0/12/0/0.4.31.0.0.0.7 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c10t0d7 /dev/rdsk/c10t0d7
target 11 0/12/0/0.4.31.0.0.1 tgt CLAIMED DEVICE
disk 72 0/12/0/0.4.31.0.0.1.0 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c10t1d0 /dev/rdsk/c10t1d0
disk 73 0/12/0/0.4.31.0.0.1.1 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c10t1d1 /dev/rdsk/c10t1d1
disk 74 0/12/0/0.4.31.0.0.1.2 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c10t1d2 /dev/rdsk/c10t1d2
disk 75 0/12/0/0.4.31.0.0.1.3 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c10t1d3 /dev/rdsk/c10t1d3
disk 76 0/12/0/0.4.31.0.0.1.4 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c10t1d4 /dev/rdsk/c10t1d4
disk 77 0/12/0/0.4.31.0.0.1.5 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c10t1d5 /dev/rdsk/c10t1d5
disk 78 0/12/0/0.4.31.0.0.1.6 sdisk CLAIMED DEVICE DGC C4700WDR5
/dev/dsk/c10t1d6 /dev/rdsk/c10t1d6
ext_bus 8 0/12/0/0.4.31.255.0 fcpdev CLAIMED INTERFACE FCP Device Interface
target 12 0/12/0/0.4.31.255.0.0 tgt CLAIMED DEVICE
ctl 13 0/12/0/0.4.31.255.0.0.0 sctl CLAIMED DEVICE DGC C4700
/dev/rscsi/c8t0d0
ctl 14 0/12/0/0.4.31.255.0.0.1 sctl CLAIMED DEVICE DGC C4700
/dev/rscsi/c8t0d1
ctl 15 0/12/0/0.4.31.255.0.0.2 sctl CLAIMED DEVICE DGC C4700
/dev/rscsi/c8t0d2
ctl 16 0/12/0/0.4.31.255.0.0.3 sctl CLAIMED DEVICE DGC C4700
/dev/rscsi/c8t0d3
ctl 17 0/12/0/0.4.31.255.0.0.4 sctl CLAIMED DEVICE DGC C4700
/dev/rscsi/c8t0d4
ctl 18 0/12/0/0.4.31.255.0.0.5 sctl CLAIMED DEVICE DGC C4700
/dev/rscsi/c8t0d5
ctl 19 0/12/0/0.4.31.255.0.0.6 sctl CLAIMED DEVICE DGC C4700
/dev/rscsi/c8t0d6
ctl 20 0/12/0/0.4.31.255.0.0.7 sctl CLAIMED DEVICE DGC C4700
/dev/rscsi/c8t0d7
ioa 1 1 sba CLAIMED BUS_NEXUS System Bus Adapter (803)
ba 8 1/0 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 9 1/2 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 10 1/4 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 11 1/8 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 12 1/10 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
fc 1 1/10/0/0 td CLAIMED INTERFACE HP Tachyon TL/TS Fibre Channel Mass S
torage Adapter
/dev/td1
fcp 3 1/10/0/0.1 fcp CLAIMED INTERFACE FCP Domain
ext_bus 11 1/10/0/0.1.19.255.0 fcpdev CLAIMED INTERFACE FCP Device Interface
target 13 1/10/0/0.1.19.255.0.0 tgt CLAIMED DEVICE
autoch 1 1/10/0/0.1.19.255.0.0.0 schgr CLAIMED DEVICE HP C7200
/dev/rac/c11t0d0
tape 3 1/10/0/0.1.19.255.0.0.1 stape CLAIMED DEVICE HP Ultrium 1-SCSI
/dev/rmt/3m /dev/rmt/3mnb /dev/rmt/c11t0d1BESTn
/dev/rmt/3mb /dev/rmt/c11t0d1BEST /dev/rmt/c11t0d1BESTnb
/dev/rmt/3mn /dev/rmt/c11t0d1BESTb
tape 4 1/10/0/0.1.19.255.0.0.2 stape CLAIMED DEVICE HP Ultrium 1-SCSI
/dev/rmt/4m /dev/rmt/4mnb /dev/rmt/c11t0d2BESTn
/dev/rmt/4mb /dev/rmt/c11t0d2BEST /dev/rmt/c11t0d2BESTnb
/dev/rmt/4mn /dev/rmt/c11t0d2BESTb
ba 13 1/12 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
lan 3 1/12/0/0 btlan5 CLAIMED INTERFACE HP A5230A/B5509BA PCI 10/100Base-TX A
ddon
/dev/diag/lan3 /dev/ether3 /dev/lan3
pbc 0 36 pbc CLAIMED BUS_NEXUS Bus Converter
processor 0 37 processor CLAIMED PROCESSOR Processor
pbc 1 44 pbc CLAIMED BUS_NEXUS Bus Converter
processor 1 45 processor CLAIMED PROCESSOR Processor
pbc 2 100 pbc CLAIMED BUS_NEXUS Bus Converter
processor 2 101 processor CLAIMED PROCESSOR Processor
pbc 3 108 pbc CLAIMED BUS_NEXUS Bus Converter
processor 3 109 processor CLAIMED PROCESSOR Processor
memory 0 192 memory CLAIMED MEMORY Memory
Users are not too bad ;-)
Michael Schulte zur Sur
Honored Contributor

Re: vmunix messages

Hi,

check for a fibre switch with the domain id=8 and reconfigure it to another id.

greetings,

Michael
Ashwani Kashyap
Honored Contributor

Re: vmunix messages

YOur HBA's and ioscan looks ok and they are running switched fabric , as suggested by FCP DOMAIN protocol .

You will haveto look at the storage switch itself . What kind of switch is it and what is the domain id of the switch .

YOu will have to look at the switch management software to find the domain id of the switch .

If the domain id of the switch is 8 , then you will have to change that , because a domain id of 8 is reserved for arbitrated loop and should not be used for switched fabrics .

On changing the domain id , beware that all your disk device file will change and you will have to reimport all your volume groups again .