Re: Message ANR0481W, ANS1809W, ANS1810E: Session lost
On Apr 13, 2007, at 5:11 AM, Gerd Becker wrote: Hello *SM*ers, since we changed our network interface on the tsm server (IBM P630, AIX5.3) to Gigabit Eth, we get very often the error ANR0481W, Session lost. On the Client Error Log we get the message ANS1809W, ANS1810E very often. On the server side the option for commtimeout is 3600 and idletimeout is 60. Has anyone an idea what the problem my be? Can I increase commtimeout to 7200 and idletimeout to 120? Some further thoughts on this... We don't know what networking you had before, but probably 100 Mbps: Did the introduction of gige substantially improve the elapsed time of your backups - or are they actually taking longer now? Taking longer definitely points to networking problems. Also, where backups take longer, the RESOURceutilization value which is in effect may result in Producer sessions timing out while Consumer sessions struggle over a longer period of time to pump data through the problematic pipe. The termination of a Producer session is not inherently bad, as the TSM client will start one afresh (ANS1810E) when the Consumer session has concluded its backup work, when session summary statistics need to be conveyed to the TSM server for it to log as ANE messages in the Activity Log. If you perform Query SEssion through the backups period and continue to see viable client sessions continually feeding data to the server, then you have good Consumer sessions going on; and you may also see companion Producer sessions for that node, and possibly see them disappear over time, as they idle timeout. You can do 'Query Node F=D' to inspect session values and get a quick sense of where delays were in the last backup session, or run a report on your TSM accounting records for before the gige change and then after, to see if any dramatic wait time changes. Richard Sims
Re: Message ANR0481W, ANS1809W, ANS1810E: Session lost
On Apr 13, 2007, at 5:11 AM, Gerd Becker wrote: Hello *SM*ers, since we changed our network interface on the tsm server (IBM P630, AIX5.3) to Gigabit Eth, we get very often the error ANR0481W, Session lost. On the Client Error Log we get the message ANS1809W, ANS1810E very often. On the server side the option for commtimeout is 3600 and idletimeout is 60. Has anyone an idea what the problem my be? Can I increase commtimeout to 7200 and idletimeout to 120? Best regards gerd w. becker, emprise Gerd - Your timeout values look sufficient to me - and if they were good for processing before this change, then they probably are still good, unto themselves. I would suspect the network change, which may have been introduced into the environment without adequate testing or configuration guidance to those using it. I would pursue TCP load testing outside of TSM, looking for anomalies in operation, as well as conferring with your networking people. Note that the TSM Messages manual says of ANS1809W: "Frequent occurrences of the ANS1809W message can indicate a problem with the network. If this message is repeatedly found in the dsmerror.log, investigate possible networking trouble, such as a failing network interface card or router problem. One common problem is the media speed of the network adaptors: If the network adaptors are set to ′′auto-negotiate′′, try changing them to ′′100% fullduplex ′′." [Note that with gige, you may be forced to use autonegotiation rather than fixed settings; but perform quality assurance tests nonetheless.] Richard Sims
Message ANR0481W, ANS1809W, ANS1810E: Session lost
Hello *SM*ers, since we changed our network interface on the tsm server (IBM P630, AIX5.3) to Gigabit Eth, we get very often the error ANR0481W, Session lost. On the Client Error Log we get the message ANS1809W, ANS1810E very often. On the server side the option for commtimeout is 3600 and idletimeout is 60. Has anyone an idea what the problem my be? Can I increase commtimeout to 7200 and idletimeout to 120? Best regards gerd w. becker, emprise
