Domain id 8 conflict error in syslog.log

[Avinash20]

Hi All,

Domain ID 8 limits the HP-UX host to private loop devices. If domain ID 8 is used, the HP-UX host is not able to detect the SAN Volume Controller.

But interestingly the messages about domain-id conflict are not getting updated in 11iv3 host syslog.log. If I can recollect, this used to happen in 11iv1/v2.

Anyone has an idea if there are any changes done ?

[Steven E. Protter]

Shalom,

More detail, the model number, OS, patch level of the server, the type of storage would be helpful in providing you with assistance.

SEP

[Stephan.]

Hi Avinash20,

11i v3 can handle this domain ID by default - for backward compatibility you can enable it again by changing the kernelparameter fclp_enable_domain_8_leg_dsf / fcd_enable_domain_8_leg_dsf for the FCLP and FCD driver release 11.31.0903 or later.

These parameters can only checked/changed by adb - they are not visible using kctune etc. .. 

I cannot currently find the the documents but its documented in QXCR1000837717(FCLP driver) and QXCR1000875122(FCD driver)

hth,

Stephan

[Avinash20]

Thanks Stephan.. You are correct.
But do you know why does the message does not log in syslog.log from HP-UX 11.31

[Stephan.]

Hi again,

because 11.31 does ID 8 not handle as privat loop by default, there for no reason to log anything into the syslog.

You can use (even I would never suggest this) ID 8 as well as any other ID as long you have only 11.31 Systems.

hth,

Stephan

[Avinash20]

I did not understand the following statement

"because 11.31 does ID 8 not handle as privat loop by default, there for no reason to log anything into the syslog"

[Avinash20]

Thanks for the response, but let me brief out the issue

We have four customer who have faced this issue, where the devices were not visible on the host HP-UX 11.31, with no errors in syslog.log.. In all the cases it turned out to be a domainid 8 issue.(Customer using switched Fabric - topology is PTTOPT_FABRIC)

In HP-UX 11.11 and 11.23 we have seen that if we use Domain-id 8, we used to get an error in syslog.log which will make the troubleshooting easier.

Would like to know if something got changed from 11.31 or if it is a Bug

[Stephan. · Accepted solution]

Hi (again),

For example:

On HP-UX 11i v3 system, ioscan does not show legacy hardware paths for a Lun behind fiber channel host bus adapter (HBA) . However it detects all Agile lunpaths for a Lun. For example, following disk16 (64000/0xfa00/0x19) has 8 lunpaths but it only shows 4 legacy hardware paths. This is caused by domain ID 8 which is interpreted as private loop.

# /usr/sbin/ioscan -m hwpath
Lun H/W Path Lunpath H/W Path Legacy H/W Path
====================================================================
::
64000/0xfa00/0x19
0/3/0/0/0/0.0x....a88.0x4001000000000000 0/3/0/0/0/0.7.0.0.0.0.1
0/3/0/0/0/0.0x....a8a.0x4001000000000000 0/3/0/0/0/0.7.1.0.0.0.1
0/3/0/0/0/0.0x....a8c.0x4001000000000000 0/3/0/0/0/0.7.2.0.0.0.1
0/3/0/0/0/0.0x....a8e.0x4001000000000000 0/3/0/0/0/0.7.3.0.0.0.1
0/3/0/0/0/1.0x....a89.0x4001000000000000
0/3/0/0/0/1.0x....a8b.0x4001000000000000
0/3/0/0/0/1.0x....a8d.0x4001000000000000
0/3/0/0/0/1.0x....a8f.0x4001000000000000

So yes 11.31 did change a lot - agile device adressing versus legacy device adressing.

• legacy and Domain ID 8 = privat loop = does not work in a switched enviroment
• agile and domain ID 8 = does work in a switched enviroment
• agile, domain ID 8 and Kernelparameters = same behavior as in 11.11 and 11.23

So my guess is, if you got customers with 11.31 and it does not work - they disabled agile device adressing. Probably because 11.31 can handle it using agile device adressing you do not see anymore the message in the syslog.

Hth,

Stephan

[Avinash20]

Thanks Stephan.. This is what I was expecting.. Thanks again..