SUMMARY: Strange behavior of V5 TruCluster with patch 3

From: Kazuro FURUKAWA <kazuro.furukawa_at_kek.jp>
Date: Fri, 28 Sep 2001 19:43:49 +0900

Dear Admins,

Our strange problem long time ago in May 2001 was solved by a recent patch.
  -----
  C122.02 Network superpatch
  TruCluster Server V5.1
          Patch C122.02
                  ./usr/opt/TruCluster/sys/clua.mod
                          CHECKSUM: 62810 492
                          SUBSET: TCRBASE510
  TCRPATC0012202510
  This patch fixes problem where a rebooted node will not be able to send
    messages to the cluster alias.
  -----

The patch seems to have been released in August. Somehow, it did
not reach us untill yesterday.

>>> On Sat, 12 May 2001 10:43:37 JST, Kazuro FURUKAWA <kazuro.furukawa_at_kek.jp> wrote;
> We're experiencing some odd behavior with V5.1 TruCluster after the
> patch T64V51AS0003-20010413 was applied by Compaq support (even after
> another reboot).
>
> Here is the cluster configuration.
> node name ether fddi memchan
> alias C C,C0 C1
> 1 A A0 A1 Am
> 2 B B0 B1 Bm
>
> First, we noticed that rsh from B to B hangs, while ftp from B to B
> works. Then we found these interesting symptoms while we are waiting
> for a timing to reboot.
>
> 0) almost all network activities are working well. for example
> any access from A to Ax works. (Ax means A0, A1, Am or localhost)
> 1) rsh, rlogin, telnet from B to Bx hangs. (Ctrl-C can kill it.)
> (Here Bx means B0, B1, Bm or localhost)
> 1') ping from B to Bx works.
> 2) ping from B to C0 or C gets no reply.
> 2') ping from B to C1 works.

(Long original message truncated)
Message-id: <200105120143.KAA0000003913_at_lychee.kek.jp>
Message-id: <200105210901.SAA0000009712_at_lychee.kek.jp>

Cheers.
-----
Kazuro FURUKAWA <kazuro.furukawa_at_kek.jp>
 Linac, High Energy Accelerator Research Organization (KEK), Japan
Received on Fri Sep 28 2001 - 10:44:41 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:42 NZDT