rx 6600_hpux reboot

[mrmo07]

HI,

i wanna know, can ip conflict reboot rx6600 server automatically?

Regards,

Mrmo07

[V. Nyga]

As far as I can remember (it's some years back) - I had the case that both ws just hung as soon as the second ws was in the network. No automatic reboot.

V.

[Steven E. Protter]

Shalom,

I've worked with rx class servers for over 6 years now. Never once did the system boot merely due to an I/O conflict.

Something else happened. Take a look at /var/adm/syslog/syslog.log

SEP

[Pete Randall]

Uhhh, there's a big difference between an ip conflict and an I/O conflict - but neither should cause a reboot. 

Still a good idea to check syslog, shutdown.log, etc.

[Steven E. Protter]

Shalom again,

Even an I/O conflict should not boot the box.

HPMC

High Priority Machine Check -caused by the loss of say a CPU will boot the box.

Application fault can boot the box.

OS fault can cause this.

I'd recommend checking:

crashconf -v

/etc/rc.config.d/savecrash # to see if the system is saving crashes and where they might be.

SEP

[Torsten.]

I have never seen a reboot because of this, but very strange things may happen ...

[Mel Burslan]

Does this server a cluster (as in MC ServiceGuard) member ? If so, even though I have not seen an IP conflict inducing a TOC and shutting down a server, I have seen stranger things happen. So, it is something good to know if it is clustered or not.

But I agree with the general consensus, IP address conflicts, generally hang the system, who has the duplicate IP address, earlier in the fray but, causing a shutdown/reboot is not something I have heard before.