topic Re: SG Not Starting after IP Change in Operating System - HP-UX

SG Not Starting after IP Change

brian_31 — Tue, 02 Nov 2004 10:19:35 GMT

Team:

I did the ip/subnet chages on 2 servers with identical configuration. These are single node clusters (no failover). On the 1st machine the SG came up fine. On the second this is the error that comes up...
cmcld: Aborting! Failed to communicate with DLPI..
checkconf and applyconf no errors..What could cause this?

Thanks

Brian.

Re: SG Not Starting after IP Change

Sridhar Bhaskarla — Tue, 02 Nov 2004 10:23:58 GMT

Hi Brian,

Did you re-apply the cluster and package configuration?. Check your and 'netstat -in' to ensure that the interfaces show up correctly. DO you see any more errors in syslog.log?. Post them.

-Sri

Re: SG Not Starting after IP Change

Steve Steel — Tue, 02 Nov 2004 10:27:51 GMT

Hi

Definately lan problem

Unused interface declared or declared interface not connected . check cables

Could also be a patch problem .Make sure you have late evrsion of SG and good patch level

Steve STeel

Re: SG Not Starting after IP Change

Geoff Wild — Tue, 02 Nov 2004 10:31:15 GMT

May be a patch issue...

Check the following posts:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=30354

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=687270

Rgds...Geoff

Re: SG Not Starting after IP Change

brian_31 — Tue, 02 Nov 2004 10:43:50 GMT

Team:

Looks like a LAN issue. Got around it by defining another interface. But now the cluster comes up but not the package. It says the function add_ipaddress fails. So looks like it is not able to add or remove the SG[IP] to the subnet. what could be the issue?

Thanks

Brian.

Re: SG Not Starting after IP Change

Sridhar Bhaskarla — Tue, 02 Nov 2004 10:47:30 GMT

Hi Brian,

Is the interface ok? Can you be able to ping to other systems in the same subnet through the new interface?. Ensure that the subnet you specified in your package control file matches with the subnet on the interface. With non-default subnetmasks, finding the subnet can be trickier. 'netstat -in' will show correct subnet.

-Sri