Hi,
For so far as I know SAN is used to transfer data, LAN is used for
communicating between TSM server(s)/Agents. So, if there is a problem in
your LAN configuration the communication between Server(s)/Agent can be
interrupted. It happend in our case a couple of times. After some
investigation it turn out to be a hardware problem on a switch port.
Regard,
Karel
> -----Oorspronkelijk bericht-----
> Van: Sebastian Szumczyk [mailto:Sebastian.Szumczyk AT INGNN DOT PL]
> Verzonden: dinsdag 1 juli 2003 11:08
> Aan: ADSM-L AT VM.MARIST DOT EDU
> Onderwerp: ODP: Error logs - storage agents
>
>
> Karel,
> Thx for so quick reply but let me explain sth. I have got a
> problem with SAN
> not LAN clients. The difference is, that SAN switch doesn't
> allow me to
> change duplex and network speed values. SAN configuration is
> based on Dell
> EMC2 and 56F Switch. TSM ver. 5.1 is configured on AIX 5.1. I
> haven't got
> any network problems, no delays or interruption with
> communication through
> SAN.
> U descibed that this problem could be caused but "not so stable
> communication". Can u describe it, cause I got a problem with
> understanding
> what u exactly mean? WAN can cause such a problems, but SAN
> works a "little
> bit" in a different way.
> Waiting for reply,
> Sebastian
>
> -----Wiadomość oryginalna-----
> Od: Karel Bos [mailto:Karel.Bos AT NUON DOT COM]
> Wysłano: 1 lipca 2003 09:52
> Do: ADSM-L AT VM.MARIST DOT EDU
> Temat: Re: Error logs - storage agents
>
>
> Hi,
>
> ANR3605E Unable to communicate with storage agent.
> Explanation: The database server was attempting to
> communicate with the
> storage agent but was unable to do so.
> System Action: The database server operation fails.
> User Response: Check the configuration of the storage agent
> and server to
> ensure that communication parameters are correct
>
> ANR0479W Session session number for server server name
> (server platform)
> terminated - connection with server severed.
> Explanation: If server A has opened a connection with server
> B, server B's
> session is ended because the communications link has been closed by a
> network error or by server A's program.
> System Action: Server A continues operation.
> User Response: If server B halts operation or in some way stops
> communicating with server A, this message will be displayed
> on server A
> indicating that the connection was closed suddenly by server
> B. A network
> failure can also cause this message to be displayed. If a
> large number of
> these messages occur simultaneously, check the network for failure and
> correct any problems
>
> As you can see both error messages point to failures to
> communicate. It
> looks like the network connection between both machines is
> not that stable.
> So you are back to basics. Look if the network is configured
> correctly (no
> auto but 10/100 mb full/half duplex on the network speed), look at the
> switch setting and let things match. This should make live
> much easier.
>
> Regard,
>
> Karel
> p.s. It helps if the config specs (TSM Server OS, TSM Server
> Levels etc.)
> are mentioned.
>
>
> > -----Oorspronkelijk bericht-----
> > Van: Sebastian Szumczyk [mailto:Sebastian.Szumczyk AT INGNN DOT PL]
> > Verzonden: dinsdag 1 juli 2003 9:39
> > Aan: ADSM-L AT VM.MARIST DOT EDU
> > Onderwerp: Error logs - storage agents
> >
> >
> > Hi,
> > Plenty of times a day I receive error logs from TSM according
> > to Storage
> > Agents sessions. For insance :
> >
> > "2003-07-01 07:39:19 ANR3605E Unable to communicate with
> > storage agent.
> > 2003-07-01 07:39:20 ANR0479W Session 67 for server
> > STA_ORNELLA (Windows)
> > terminated - connection with server severed"
> >
> > It fills up the TSM logs (100 lines a day), so it's going to be very
> > dificult to find interested me entries. If u know what is it
> > and how to
> > solve the problem I will be appreciate.
> > Regards,
> > Sebastian
> >
>
|
