topic Re: Strange hyperfabric problem in Operating System - HP-UX

Strange hyperfabric problem

Bruno Bossier_1 — Mon, 20 Sep 2004 08:46:13 GMT

When I run clic_shutdown, it stops the hyperfabric management daemon, but also unplumbs the hyperfabric interfaces (clic0 and clic1 in my case). When I run clic_start it only starts the hyperfabric management daemon, but does not plumb and configure the clic interfaces. When one of the 2 nodes in my cluster was rebooted or when I ran clic_shutdown on one of the 2 nodes, I have to run :

1. clic_shutdown on both nodes
2. clic_start on both nodes
3. /sbin/init.d/net start on both nodes

in this specific order.

This is very anoying. Any ideas ?

Bruno

Re: Strange hyperfabric problem

Steven E. Protter — Tue, 21 Sep 2004 10:56:16 GMT

You might want to look ata the code of clic_shutdown and see if its doing something to that causes the network to go down.

what does ifconfig lan0 or ifconfig lan1 show while its down.

Are these inerfaces acting as a NIC or as SCSI devices to access storage?

SEP+

Re: Strange hyperfabric problem

Shine_5 — Tue, 21 Sep 2004 12:47:17 GMT

Hello

This is because a new field has been added to the Hyperfabric configuration
file /etc/rc.config.d/clic_global_conf to enable HMP. This field may be missing in
the Hyperfabric software .

Solution : -
If the error coours, reconfigure HyperFabric, using clic_init -c. This will
rebuild a correct configuration file.

Shine

Re: Strange hyperfabric problem

Bruno Bossier_1 — Fri, 24 Sep 2004 05:29:43 GMT

If you are refering to the field BCOMPAT_ENABLED, then these are both set to N.

Bruno

Re: Strange hyperfabric problem

Bruno Bossier_1 — Fri, 24 Sep 2004 05:36:44 GMT

- clic_shutdown indeed executes an ifconfig unplumb on all hyperfabric interfaces

- clic_start calls /sbin/init.d/net start to plumb the hyperfabric interfaces

This seems to be OK. It's just that when you ran clic_shutdown on one node, you also need to run clic_shutdown on the other node and then run clic_start on the 2 nodes.

Bruno