Hi All
I've got some new windows nodes just defined  on two different AIX TSM
servers, and they are getting ANR8214E errors with the 127.0.0.1 address on
their overnight schedules. This is the same issue that Allen Rout posted
about on July 31 (post included below).  Now the funny thing is that I set
up a clientaction backup yesterday on these nodes, recycled the CAD Service
and the clientaction backup ran with no problem, the client then found its
next schedule and all appeared to be well, but then, last night more
ANR8214 errors.

Client 5.4.1.2 Server both AIX 5.2.4.1 (yes an upgrade is in the works)

Allen - Did you ever get a resolution to this?

Regards

Steve
Steve Harris
TSM Admin
Sydney Australia

Allen Rout posted this on July 31

>So my 'INT' TSM server has been up for working on two months.  Current
>sessions are in the 220K zone.  Yesterday, I noticed an odd pattern,
>which has evidently been happening for some time.


>07/30/07   18:00:02     ANR8214E Session open with 127.0.0.1 failed due to

>connection refusal. (SESSION: 1209)
>07/30/07   18:00:02     ANR2716E Schedule prompter was not able to contact

>client [some client name] using type 1 (127.0.0.1 1501). (SESSION: 1209)
>07/30/07   18:00:33     ANR8214E Session open with 127.0.0.1 failed due to

>connection refusal. (SESSION: 1209)
>07/30/07   18:01:03     ANR8214E Session open with 127.0.0.1 failed due to

>connection refusal. (SESSION: 1209)
>07/30/07   18:01:33     ANR8214E Session open with 127.0.0.1 failed due to

>connection refusal. (SESSION: 1209)

>Continuing every 30 seconds until midnight.

>The client in question has a perfectly normal (private) IP in its'
>node entry.

>The session quoted in the connection refusal message seems ludicrously
>low.  I'm not sure where that came from.

>Apparently the box has been doing this for months. :) Anybody have a
>clue what's happening in there?


>- Allen S. Rout