Node IP address
I have a node where the IP address changed; it now differs from the TCP/IP value shown in Q NODE name F=D. The node can successfully open the BAClient GUI and I see Activity Log records that display the new IP value. I can PING the new address and TELNET to 1501 so I know the scheduler is running and network is routing. If the node uses Edit Client Preferences to change the IP on Scheduler, Prompted Mode, why does that not appear to change the TCP/IP as shown by the Q NODE command? Setting HLAddress doesn't apply because we're in ClientorServer session initiation. The node manager SAYS he's altered the IP value, maybe he hasn't? Harold Vandeventer Systems Programmer State of Kansas - Office of Information Technology Services STE 751-S 910 SW Jackson (785) 296-0631 [Confidentiality notice:] *** This e-mail message, including attachments, if any, is intended for the person or entity to which it is addressed and may contain confidential or privileged information. Any unauthorized review, use, or disclosure is prohibited. If you are not the intended recipient, please contact the sender and destroy the original message, including all copies, Thank you. ***
Re: Node IP address
After changing IP you need to restart RSM services (at least TSM Scheduler, if in use). New TCP/IP will be visible on YSM server. Grigori Solonovitch, Senior Systems Architect, IT, Ahli United Bank Kuwait, www.ahliunited.com.kw -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Vandeventer, Harold [BS] Sent: 02 05 2014 10:37 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Node IP address I have a node where the IP address changed; it now differs from the TCP/IP value shown in Q NODE name F=D. The node can successfully open the BAClient GUI and I see Activity Log records that display the new IP value. I can PING the new address and TELNET to 1501 so I know the scheduler is running and network is routing. If the node uses Edit Client Preferences to change the IP on Scheduler, Prompted Mode, why does that not appear to change the TCP/IP as shown by the Q NODE command? Setting HLAddress doesn't apply because we're in ClientorServer session initiation. The node manager SAYS he's altered the IP value, maybe he hasn't? Harold Vandeventer Systems Programmer State of Kansas - Office of Information Technology Services STE 751-S 910 SW Jackson (785) 296-0631 [Confidentiality notice:] *** This e-mail message, including attachments, if any, is intended for the person or entity to which it is addressed and may contain confidential or privileged information. Any unauthorized review, use, or disclosure is prohibited. If you are not the intended recipient, please contact the sender and destroy the original message, including all copies, Thank you. *** Please consider the environment before printing this Email. CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software.
Re: Node IP address
That's what I thought... The node manager tells me he changed the IP and I also told him to stop/start the schedule service. I'll have him send me a copy of his dsm.opt file... that'll tell if he did the change. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Grigori Solonovitch Sent: Friday, May 02, 2014 3:18 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Node IP address After changing IP you need to restart RSM services (at least TSM Scheduler, if in use). New TCP/IP will be visible on YSM server. Grigori Solonovitch, Senior Systems Architect, IT, Ahli United Bank Kuwait, www.ahliunited.com.kw -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Vandeventer, Harold [BS] Sent: 02 05 2014 10:37 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Node IP address I have a node where the IP address changed; it now differs from the TCP/IP value shown in Q NODE name F=D. The node can successfully open the BAClient GUI and I see Activity Log records that display the new IP value. I can PING the new address and TELNET to 1501 so I know the scheduler is running and network is routing. If the node uses Edit Client Preferences to change the IP on Scheduler, Prompted Mode, why does that not appear to change the TCP/IP as shown by the Q NODE command? Setting HLAddress doesn't apply because we're in ClientorServer session initiation. The node manager SAYS he's altered the IP value, maybe he hasn't? Harold Vandeventer Systems Programmer State of Kansas - Office of Information Technology Services STE 751-S 910 SW Jackson (785) 296-0631 [Confidentiality notice:] *** This e-mail message, including attachments, if any, is intended for the person or entity to which it is addressed and may contain confidential or privileged information. Any unauthorized review, use, or disclosure is prohibited. If you are not the intended recipient, please contact the sender and destroy the original message, including all copies, Thank you. *** Please consider the environment before printing this Email. CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software.
Migration, IP address change, and New Library at the same time - UPDATE
UPDATE: All of this went well. There is no issue in changing the IP of the host, just the host name apparently. Did the usual of checking out all the tapes from the old Library, migrating, changed IP address, setting up new and checking the tapes in again. It's all working. Just thought I'd let anyone who was wondering like me know. Ladies and Gents, we're going to be migrating from TSM 5.5.3 to TSM 6.2.2, along with that we'll be moving to a new Library as well. Up to this point I don't see any issues as we already use the combo we'll be putting in place at this location. The problem is we have to maintain the current TSM server's IP address. Which means that we'll need to use a temp address on the new server until after the migration is complete, shut down the old server, change IPs, and then bring up the new server. My question is has anyone here done this that would have suggestions on steps related to that? (i.e. set ip address on new server and change old, do migration, other way around, etc.). See Ya' Howard Coles Jr. John 3:16!
Re: Migration, IP address change, and New Library at the same time
The last time I changed servers, I had our network group change the name of the current server, then create a dns alias using our usual dns name to point to the old server. On the day of the switch, we simply pointed that alias to the new tsm server and all went smoothly. I insist that all my tsm clients refer to the server via dns entry, not ip address. No one even knew that I had switched servers. If your servers are tsmold.co.com and tsmnew.co.com Have a new dns entry created for tsmold.co.com maybe tsmgone.co.com. Now remove entry tsmold.co.com, create a new alias tsmold.co.com pointing to tsmgone.co.com. When you switch, simply point tsmold.co.com to tsmnew.co.com. If all your clients use dns entries, they will automagically point to the new server. If you need to get to the old server, just change the dsm.opt to point at tsmgone.co.com. Hope this helps. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Howard Coles Sent: Wednesday, February 23, 2011 5:27 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Migration, IP address change, and New Library at the same time Ladies and Gents, we're going to be migrating from TSM 5.5.3 to TSM 6.2.2, along with that we'll be moving to a new Library as well. Up to this point I don't see any issues as we already use the combo we'll be putting in place at this location. The problem is we have to maintain the current TSM server's IP address. Which means that we'll need to use a temp address on the new server until after the migration is complete, shut down the old server, change IPs, and then bring up the new server. My question is has anyone here done this that would have suggestions on steps related to that? (i.e. set ip address on new server and change old, do migration, other way around, etc.). See Ya' Howard Coles Jr. John 3:16!
Migration, IP address change, and New Library at the same time
Ladies and Gents, we're going to be migrating from TSM 5.5.3 to TSM 6.2.2, along with that we'll be moving to a new Library as well. Up to this point I don't see any issues as we already use the combo we'll be putting in place at this location. The problem is we have to maintain the current TSM server's IP address. Which means that we'll need to use a temp address on the new server until after the migration is complete, shut down the old server, change IPs, and then bring up the new server. My question is has anyone here done this that would have suggestions on steps related to that? (i.e. set ip address on new server and change old, do migration, other way around, etc.). See Ya' Howard Coles Jr. John 3:16!
Re: Tcp/ip address not correctly associated to cluster node
Cluster node just takes TCP/IP address, which has no relationship whith used management classess/copy groups. TCP/IP address is important just for communication during backup/restore operations, but not for storing data on TSM server. From: ADSM: Dist Stor Manager [ads...@vm.marist.edu] On Behalf Of Rick Adamson [rickadam...@winn-dixie.com] Sent: Friday, April 16, 2010 10:38 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tcp/ip address not correctly associated to cluster node Am I missing something, If it uses the node that actively owns the cluster instance for the shared resource backups don't you risk duplicating backup data? Since the shared data could actually be stored by each node when they own the instance. At least that has been my experience, I use a separate TSM node and services for the clustername. ~Rick Adamson Sr. Systems Engineer Jacksonville, FL. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Lee, Gary D. Sent: Friday, April 16, 2010 3:11 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tcp/ip address not correctly associated to cluster node Thanks dwight. Don't know why I didn't see that. Must be time to go home. Think the brain needs a recharge. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Dwight Cook Sent: Friday, April 16, 2010 2:54 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tcp/ip address not correctly associated to cluster node If you want to force it to use the cluster ip for the cluster node, set the tcpclientaddress in the dsm.opt file used by the cluster node client acceptor scheduler... but if those follow the cluster OK, it really shouldn't matter if they use the cluster address or the address of the server currently serving the cluster since they technically are one and the same... -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Lee, Gary D. Sent: Friday, April 16, 2010 1:43 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Tcp/ip address not correctly associated to cluster node Microsoft windows 2008, tsm client 6.2 tsmserver 5.5.4. under suse sles9 under zvm 5.3. We have a two node cluster with clustername sqltestcluster. There is one group (win 2008 no longer refers to them as groups) called sqltsmcluster. Cluster nodes are called sqltestcl01 and sqltestcl02. Sqltestcl01 and 02 back up local file resourses fine. Tried to create a cluster tsm node called sqltestcluster to match the cluster name. Defined all the schedulers, and acceptors. Services fail over correctly. However, the ip address for the cluster is never associated with tsm node sqltsmcluster. It gets its ip address as whichever node is active. Yes, there is a network name and ip address resource defined within the group sqltsmcluster. I am at a loss. Where is the link established between the tsm node_name and the tcp/ip addresss resource which moves between cluster nodes? Thanks for any help. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 = Please consider the environment before printing this Email. CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software.
Tcp/ip address not correctly associated to cluster node
Microsoft windows 2008, tsm client 6.2 tsmserver 5.5.4. under suse sles9 under zvm 5.3. We have a two node cluster with clustername sqltestcluster. There is one group (win 2008 no longer refers to them as groups) called sqltsmcluster. Cluster nodes are called sqltestcl01 and sqltestcl02. Sqltestcl01 and 02 back up local file resourses fine. Tried to create a cluster tsm node called sqltestcluster to match the cluster name. Defined all the schedulers, and acceptors. Services fail over correctly. However, the ip address for the cluster is never associated with tsm node sqltsmcluster. It gets its ip address as whichever node is active. Yes, there is a network name and ip address resource defined within the group sqltsmcluster. I am at a loss. Where is the link established between the tsm node_name and the tcp/ip addresss resource which moves between cluster nodes? Thanks for any help. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
Re: Tcp/ip address not correctly associated to cluster node
If you want to force it to use the cluster ip for the cluster node, set the tcpclientaddress in the dsm.opt file used by the cluster node client acceptor scheduler... but if those follow the cluster OK, it really shouldn't matter if they use the cluster address or the address of the server currently serving the cluster since they technically are one and the same... -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Lee, Gary D. Sent: Friday, April 16, 2010 1:43 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Tcp/ip address not correctly associated to cluster node Microsoft windows 2008, tsm client 6.2 tsmserver 5.5.4. under suse sles9 under zvm 5.3. We have a two node cluster with clustername sqltestcluster. There is one group (win 2008 no longer refers to them as groups) called sqltsmcluster. Cluster nodes are called sqltestcl01 and sqltestcl02. Sqltestcl01 and 02 back up local file resourses fine. Tried to create a cluster tsm node called sqltestcluster to match the cluster name. Defined all the schedulers, and acceptors. Services fail over correctly. However, the ip address for the cluster is never associated with tsm node sqltsmcluster. It gets its ip address as whichever node is active. Yes, there is a network name and ip address resource defined within the group sqltsmcluster. I am at a loss. Where is the link established between the tsm node_name and the tcp/ip addresss resource which moves between cluster nodes? Thanks for any help. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 =
Re: Tcp/ip address not correctly associated to cluster node
Thanks dwight. Don't know why I didn't see that. Must be time to go home. Think the brain needs a recharge. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Dwight Cook Sent: Friday, April 16, 2010 2:54 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tcp/ip address not correctly associated to cluster node If you want to force it to use the cluster ip for the cluster node, set the tcpclientaddress in the dsm.opt file used by the cluster node client acceptor scheduler... but if those follow the cluster OK, it really shouldn't matter if they use the cluster address or the address of the server currently serving the cluster since they technically are one and the same... -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Lee, Gary D. Sent: Friday, April 16, 2010 1:43 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Tcp/ip address not correctly associated to cluster node Microsoft windows 2008, tsm client 6.2 tsmserver 5.5.4. under suse sles9 under zvm 5.3. We have a two node cluster with clustername sqltestcluster. There is one group (win 2008 no longer refers to them as groups) called sqltsmcluster. Cluster nodes are called sqltestcl01 and sqltestcl02. Sqltestcl01 and 02 back up local file resourses fine. Tried to create a cluster tsm node called sqltestcluster to match the cluster name. Defined all the schedulers, and acceptors. Services fail over correctly. However, the ip address for the cluster is never associated with tsm node sqltsmcluster. It gets its ip address as whichever node is active. Yes, there is a network name and ip address resource defined within the group sqltsmcluster. I am at a loss. Where is the link established between the tsm node_name and the tcp/ip addresss resource which moves between cluster nodes? Thanks for any help. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 =
Re: Tcp/ip address not correctly associated to cluster node
Am I missing something, If it uses the node that actively owns the cluster instance for the shared resource backups don't you risk duplicating backup data? Since the shared data could actually be stored by each node when they own the instance. At least that has been my experience, I use a separate TSM node and services for the clustername. ~Rick Adamson Sr. Systems Engineer Jacksonville, FL. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Lee, Gary D. Sent: Friday, April 16, 2010 3:11 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tcp/ip address not correctly associated to cluster node Thanks dwight. Don't know why I didn't see that. Must be time to go home. Think the brain needs a recharge. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Dwight Cook Sent: Friday, April 16, 2010 2:54 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tcp/ip address not correctly associated to cluster node If you want to force it to use the cluster ip for the cluster node, set the tcpclientaddress in the dsm.opt file used by the cluster node client acceptor scheduler... but if those follow the cluster OK, it really shouldn't matter if they use the cluster address or the address of the server currently serving the cluster since they technically are one and the same... -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Lee, Gary D. Sent: Friday, April 16, 2010 1:43 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Tcp/ip address not correctly associated to cluster node Microsoft windows 2008, tsm client 6.2 tsmserver 5.5.4. under suse sles9 under zvm 5.3. We have a two node cluster with clustername sqltestcluster. There is one group (win 2008 no longer refers to them as groups) called sqltsmcluster. Cluster nodes are called sqltestcl01 and sqltestcl02. Sqltestcl01 and 02 back up local file resourses fine. Tried to create a cluster tsm node called sqltestcluster to match the cluster name. Defined all the schedulers, and acceptors. Services fail over correctly. However, the ip address for the cluster is never associated with tsm node sqltsmcluster. It gets its ip address as whichever node is active. Yes, there is a network name and ip address resource defined within the group sqltsmcluster. I am at a loss. Where is the link established between the tsm node_name and the tcp/ip addresss resource which moves between cluster nodes? Thanks for any help. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 =
What IP address does the Client use to contact the server?
We have a server that has been getting the following sporadic dsmerror.log errors: 12/19/09 14:07:02 ANS9020E Could not establish a session with a TSM server or client agent. The TSM return code is -50. 12/19/09 14:07:02 ANS1017E Session rejected: TCP/IP connection failure 12/19/09 14:13:00 ANS9020E Could not establish a session with a TSM server or client agent. The TSM return code is -50. 12/19/09 14:13:00 ANS1017E Session rejected: TCP/IP connection failure Normally, backups work just fine. We just get this in spurts. I'm thinking it's a DNS resolution problem in the ip lookup for dsm.sys:tcpserveraddress tsm4.fenetwork.com. q) Is there some way to get the BA client to list the IP address it's trying to use? The dsm.sys file: servernametsm4 schedmode prompted commmethod TCPip tcpport1800 tcpserveraddress tsm4.fenetwork.com schedlogretention 5 errorlogretention 5 tcpbuffsize64 tcpwindowsize 64 txnbytelimit 25600 nodename hpgno16p passwordaccess generate inclexcl /opt/tivoli/tsm/client/ba/bin/inclexcl.sys schedlogname /opt/tivoli/tsm/client/ba/bin/dsmsched.log errorlogname /opt/tivoli/tsm/client/ba/bin/dsmerror.log Thanks! Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
SV: [ADSM-L] What IP address does the Client use to contact the server?
Hi q) Is there some way to get the BA client to list the IP address it's trying to use? It is using tsm4.fenetwork.com. From inside tsm you can't see what ip# it resolves to, but here are a few other methods: Ping tsm4.fenetwork.com Nslookup tsm4.fenetwork.com. Or start a dsmc session (try to start at least) and use netstat -an | grep 1800 If you don't trust your name service you can use tcpserveraddress ip# instead. BUT: Session rejected looks like the client talks to the operating system on the machine that runs the TSM server, but the server isn't answering on the port (1800). The server may be down, or you have reached the maximum number of sessions. (hint: q status). Merry Christmas Anders Räntilä
Re: What IP address does the Client use to contact the server?
Richard, The rc 50 could be caused by numerous scenarios (TCPPort change, flakey cables, faulty hardware). You could run a Tracert IP/HOSTNAME_TSM_SERVER to see where there could be data loss/connectivity issue between the client and TSM server. As far as listing the specific TCP address, you could do nslookup for the TSM server or simply do q opt on the TSM server itself and check for IP address right above Server TCP/IP port number. BERTAUT TCHUISE TSM/NetApp Storage Administrator Legg Mason Technology Services *410-580-7032 btchu...@leggmason.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Richard Rhodes Sent: Wednesday, December 23, 2009 10:21 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] What IP address does the Client use to contact the server? We have a server that has been getting the following sporadic dsmerror.log errors: 12/19/09 14:07:02 ANS9020E Could not establish a session with a TSM server or client agent. The TSM return code is -50. 12/19/09 14:07:02 ANS1017E Session rejected: TCP/IP connection failure 12/19/09 14:13:00 ANS9020E Could not establish a session with a TSM server or client agent. The TSM return code is -50. 12/19/09 14:13:00 ANS1017E Session rejected: TCP/IP connection failure Normally, backups work just fine. We just get this in spurts. I'm thinking it's a DNS resolution problem in the ip lookup for dsm.sys:tcpserveraddress tsm4.fenetwork.com. q) Is there some way to get the BA client to list the IP address it's trying to use? The dsm.sys file: servernametsm4 schedmode prompted commmethod TCPip tcpport1800 tcpserveraddress tsm4.fenetwork.com schedlogretention 5 errorlogretention 5 tcpbuffsize64 tcpwindowsize 64 txnbytelimit 25600 nodename hpgno16p passwordaccess generate inclexcl /opt/tivoli/tsm/client/ba/bin/inclexcl.sys schedlogname /opt/tivoli/tsm/client/ba/bin/dsmsched.log errorlogname /opt/tivoli/tsm/client/ba/bin/dsmerror.log Thanks! Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message. IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason therefore recommends that you do not send any confidential or sensitive information to us via electronic mail, including social security numbers, account numbers, or personal identification numbers. Delivery, and or timely delivery of Internet mail is not guaranteed. Legg Mason therefore recommends that you do not send time sensitive or action-oriented messages to us via electronic mail. This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not use, copy or disclose to anyone any information contained in this message. If you have received this message in error, please notify the author by replying to this message and then kindly delete the message. Thank you.
Re: SV: [ADSM-L] What IP address does the Client use to contact the server?
Thanks for the info. The tsm server has nothing in the actlog during the time frames of the errors for this node. It DOES have sessions being started for other nodes. That's why I'm thinking it's a DNS/network problem. Per suggestions . . .I'm putting together a little script to do tests every 60s for ping, nslookup, traceroute. Thanks! rick Anders Räntilä and...@rantila.c OMTo Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager ads...@vm.marist Subject .EDU SV: [ADSM-L] What IP address does the Client use to contact the server? 12/23/2009 10:45 AM Please respond to ADSM: Dist Stor Manager ads...@vm.marist .EDU Hi q) Is there some way to get the BA client to list the IP address it's trying to use? It is using tsm4.fenetwork.com. From inside tsm you can't see what ip# it resolves to, but here are a few other methods: Ping tsm4.fenetwork.com Nslookup tsm4.fenetwork.com. Or start a dsmc session (try to start at least) and use netstat -an | grep 1800 If you don't trust your name service you can use tcpserveraddress ip# instead. BUT: Session rejected looks like the client talks to the operating system on the machine that runs the TSM server, but the server isn't answering on the port (1800). The server may be down, or you have reached the maximum number of sessions. (hint: q status). Merry Christmas Anders Räntilä - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address.
I hope it works for you. We recently upgraded to 5.5.1 server on a z/OS platform, after which most of our scheduled backups failed, apparently because of some perceived discrepancy found by reverse lookup. We added the DNSLOOKUP NO parameter as suggested by IBM support (it is undocumented for z/OS) and by itself, it did not solve our problems. We also had to restart the client acceptors on all the clients. In a few cases we had to perform manual backups before the new server software was satisfied. - Margaret Clark Systems Programmer, San Diego Data Proc4essing Corporation -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Conway, Timothy Sent: Thursday, September 18, 2008 4:20 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. TSM will populate field TCP_ADDRESS in table NODES with the numeric address of the client when it connects, so not having name lookups performed is really no loss in functionality... And now that I know about that option, it's going in next restart, because it will cut latency, which will matter for things like when an RMAN client deletes its old backups in a flurry of hundreds of separate sessions in sequence. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 1:35 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Bill, Never heard of this option. Won't this make us unable to reach ANY clients then, unless we put them in the local /etc/hosts file? That would be impractical, with 1600 clients in our environment. Or will TSM use the cached copy it saved when the client first connected in? Do you use that in your environment? Does it work seamlessly, or are there gotchas? Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bill Boyer Sent: Thursday, September 18, 2008 1:31 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Try DSNLOOKUP NO in the dsmserv.opt file. The default is YES. Bill Boyer Hang in there, retirement is only thirty years away! - ?? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 1:49 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address. Tim, We have tried this, but it doesn't help. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So the TSM scheduler seems to still know what the IP address is, but for some reason still does a DNS resolve I guess. Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Conway, Timothy Sent: Thursday, September 18, 2008 11:09 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. The simplest solution is upd node STLO-MPVADM HLA=10.52.27.204 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 9:29 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Greetings, We are running TSM 5.4.3.0 on AIX 5.3ML5. Most of our TSM clients are 5.4.x or 5.5.x. Most of our clients run schedmode prompted so the TSM server launches the schedule. We see an occasional problem where a Windows client is set up wrong in Active Directory (which feeds DNS), and the TSM scheduler won't be able to start the client scheduler. It will get errors such as: 09/18/08 05:51:12 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:52:58 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:54:44 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:56:30 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:58:16 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 06:00:01 ANR2578W Schedule WIN_PROD_0300 in domain WIN_PROD
Changing IP address of shared library controller
Because of some network changes, I need to change the IP address of the system that controls my tape robot in a shared library environment. This system is also my configuration manager. Do I just need to change the high level address that the server has for itself (using update server) and then run notify subscribers? Are there any other potential problems with changing the IP address (but not host name) of a TSM server in this environment? -- Todd D. Taft [EMAIL PROTECTED]
TSM scheduler can't reach TSM client even though it seems to know it's IP address.
Greetings, We are running TSM 5.4.3.0 on AIX 5.3ML5. Most of our TSM clients are 5.4.x or 5.5.x. Most of our clients run schedmode prompted so the TSM server launches the schedule. We see an occasional problem where a Windows client is set up wrong in Active Directory (which feeds DNS), and the TSM scheduler won't be able to start the client scheduler. It will get errors such as: 09/18/08 05:51:12 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:52:58 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:54:44 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:56:30 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:58:16 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 06:00:01 ANR2578W Schedule WIN_PROD_0300 in domain WIN_PROD for node STLO-MPVADM has missed its scheduled start up window. In looking into it, what seems to be happening is that it's forward resolve in DNS doesn't match it's reverse resolve. Here is an example: W:\nslookup stlo-mpvadm Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.smrcy.com Address: 10.52.27.204 W:\nslookup 10.52.27.204 Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.company.com Address: 10.52.27.204 W:\ Notice that the domain name of the host is different on the forward and the reverse resolve. That is a mistake. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So what is TSM's problem here? It knows the correct IP address. What difference does it make that the reverse resolve doesn't match? Or is the problem with the client? Is it not responding? The client's dsmwebcl.log and dsmerror.log show no evidence that it is getting contacted at all. The right way to fix this is to fix the Active Directory root cause, but sometimes that requires a reboot of the client which can taken a week or more to schedule. Is the schedmode setting at fault? Would changing it to polling get around this until a reboot can be scheduled? If I don't hear anything better I will try that tonight. Best Regards, John D. Schneider Lead Systems Administrator - Storage Sisters of Mercy Health Systems 3637 South Geyer Road St. Louis, MO 63127 Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] This e-mail contains information which (a) may be PROPRIETARY IN NATURE OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for the use of the addressee(s) named above. If you are not the addressee, or the person responsible for delivering this to the addressee(s), you are notified that reading, copying or distributing this e-mail is prohibited. If you have received this e-mail in error, please contact the sender immediately.
Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address.
The simplest solution is upd node STLO-MPVADM HLA=10.52.27.204 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 9:29 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Greetings, We are running TSM 5.4.3.0 on AIX 5.3ML5. Most of our TSM clients are 5.4.x or 5.5.x. Most of our clients run schedmode prompted so the TSM server launches the schedule. We see an occasional problem where a Windows client is set up wrong in Active Directory (which feeds DNS), and the TSM scheduler won't be able to start the client scheduler. It will get errors such as: 09/18/08 05:51:12 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:52:58 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:54:44 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:56:30 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:58:16 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 06:00:01 ANR2578W Schedule WIN_PROD_0300 in domain WIN_PROD for node STLO-MPVADM has missed its scheduled start up window. In looking into it, what seems to be happening is that it's forward resolve in DNS doesn't match it's reverse resolve. Here is an example: W:\nslookup stlo-mpvadm Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.smrcy.com Address: 10.52.27.204 W:\nslookup 10.52.27.204 Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.company.com Address: 10.52.27.204 W:\ Notice that the domain name of the host is different on the forward and the reverse resolve. That is a mistake. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So what is TSM's problem here? It knows the correct IP address. What difference does it make that the reverse resolve doesn't match? Or is the problem with the client? Is it not responding? The client's dsmwebcl.log and dsmerror.log show no evidence that it is getting contacted at all. The right way to fix this is to fix the Active Directory root cause, but sometimes that requires a reboot of the client which can taken a week or more to schedule. Is the schedmode setting at fault? Would changing it to polling get around this until a reboot can be scheduled? If I don't hear anything better I will try that tonight. Best Regards, John D. Schneider Lead Systems Administrator - Storage Sisters of Mercy Health Systems 3637 South Geyer Road St. Louis, MO 63127 Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] This e-mail contains information which (a) may be PROPRIETARY IN NATURE OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for the use of the addressee(s) named above. If you are not the addressee, or the person responsible for delivering this to the addressee(s), you are notified that reading, copying or distributing this e-mail is prohibited. If you have received this e-mail in error, please contact the sender immediately.
Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address.
John - The ANR8213W message is conspicuously deficient in not parenthetically including the IP address along with the network name that it's reporting, such that you don't know for certain what address the TSM server is using in making the connection attempt. With DNS awry at your location, it may be that in the last client-server interaction that an address was obtained for the next interaction, where that address is no longer valid. IBM Technote 1296826 goes into other aspects of this situation. I would not fault TSM in the missed schedule: I would not want my server to be interacting with dubious network addresses where supposedly secured host data is involved. Flakey DNS is a very bad situation, and needs to get permanently fixed there. If you have good Security people there, they should be railing on people about the ramifications of erroneous network addresses being given out by your DNS servers. You can look into the DNSLOOKUP option for your TSM server, but there remains the larger issue of bad addresses being given out in the environment in general. Richard Sims
Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address.
Tim, We have tried this, but it doesn't help. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So the TSM scheduler seems to still know what the IP address is, but for some reason still does a DNS resolve I guess. Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Conway, Timothy Sent: Thursday, September 18, 2008 11:09 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. The simplest solution is upd node STLO-MPVADM HLA=10.52.27.204 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 9:29 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Greetings, We are running TSM 5.4.3.0 on AIX 5.3ML5. Most of our TSM clients are 5.4.x or 5.5.x. Most of our clients run schedmode prompted so the TSM server launches the schedule. We see an occasional problem where a Windows client is set up wrong in Active Directory (which feeds DNS), and the TSM scheduler won't be able to start the client scheduler. It will get errors such as: 09/18/08 05:51:12 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:52:58 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:54:44 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:56:30 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:58:16 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 06:00:01 ANR2578W Schedule WIN_PROD_0300 in domain WIN_PROD for node STLO-MPVADM has missed its scheduled start up window. In looking into it, what seems to be happening is that it's forward resolve in DNS doesn't match it's reverse resolve. Here is an example: W:\nslookup stlo-mpvadm Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.smrcy.com Address: 10.52.27.204 W:\nslookup 10.52.27.204 Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.company.com Address: 10.52.27.204 W:\ Notice that the domain name of the host is different on the forward and the reverse resolve. That is a mistake. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So what is TSM's problem here? It knows the correct IP address. What difference does it make that the reverse resolve doesn't match? Or is the problem with the client? Is it not responding? The client's dsmwebcl.log and dsmerror.log show no evidence that it is getting contacted at all. The right way to fix this is to fix the Active Directory root cause, but sometimes that requires a reboot of the client which can taken a week or more to schedule. Is the schedmode setting at fault? Would changing it to polling get around this until a reboot can be scheduled? If I don't hear anything better I will try that tonight. Best Regards, John D. Schneider Lead Systems Administrator - Storage Sisters of Mercy Health Systems 3637 South Geyer Road St. Louis, MO 63127 Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] This e-mail contains information which (a) may be PROPRIETARY IN NATURE OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for the use of the addressee(s) named above. If you are not the addressee, or the person responsible for delivering this to the addressee(s), you are notified that reading, copying or distributing this e-mail is prohibited. If you have received this e-mail in error, please contact the sender immediately. This e-mail contains information which (a) may be PROPRIETARY IN NATURE OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for the use of the addressee(s) named above. If you are not the addressee, or the person responsible for delivering this to the addressee(s), you are notified that reading, copying or distributing this e-mail is prohibited. If you have received this e-mail in error, please contact the sender immediately.
Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address.
No, the problem is that the node TSM is trying to reach is stlo-mpvadm.company.com but the machine that's responding is stlo-mpvadm.smrcy.com and TSM knows there's a difference. You MUST correct the DNS problem because TSM uses it in some way to verify authentication. I've seen this a dozen or so times before. When I've seen it the worse is where they have moved the machine to a new domain, but didn't update the machine's node and domain name info. So the machine was reporting nodename.olddomain.com while the DNS was saying nodename.newdomain.com and TSM would not allow the schedule to proceed. Once we corrected the domain info, the backups proceeded normally. See Ya' Howard -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 12:49 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Tim, We have tried this, but it doesn't help. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So the TSM scheduler seems to still know what the IP address is, but for some reason still does a DNS resolve I guess. Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Conway, Timothy Sent: Thursday, September 18, 2008 11:09 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. The simplest solution is upd node STLO-MPVADM HLA=10.52.27.204 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 9:29 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Greetings, We are running TSM 5.4.3.0 on AIX 5.3ML5. Most of our TSM clients are 5.4.x or 5.5.x. Most of our clients run schedmode prompted so the TSM server launches the schedule. We see an occasional problem where a Windows client is set up wrong in Active Directory (which feeds DNS), and the TSM scheduler won't be able to start the client scheduler. It will get errors such as: 09/18/08 05:51:12 ANR8213W Session open with stlo- mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:52:58 ANR8213W Session open with stlo- mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:54:44 ANR8213W Session open with stlo- mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:56:30 ANR8213W Session open with stlo- mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:58:16 ANR8213W Session open with stlo- mpvadm.company.com timed out. (SESSION: 243) 09/18/08 06:00:01 ANR2578W Schedule WIN_PROD_0300 in domain WIN_PROD for node STLO-MPVADM has missed its scheduled start up window. In looking into it, what seems to be happening is that it's forward resolve in DNS doesn't match it's reverse resolve. Here is an example: W:\nslookup stlo-mpvadm Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.smrcy.com Address: 10.52.27.204 W:\nslookup 10.52.27.204 Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.company.com Address: 10.52.27.204 W:\ Notice that the domain name of the host is different on the forward and the reverse resolve. That is a mistake. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So what is TSM's problem here? It knows the correct IP address. What difference does it make that the reverse resolve doesn't match? Or is the problem with the client? Is it not responding? The client's dsmwebcl.log and dsmerror.log show no evidence that it is getting contacted at all. The right way to fix this is to fix the Active Directory root cause, but sometimes that requires a reboot of the client which can taken a week or more to schedule. Is the schedmode setting at fault? Would changing it to polling get around this until a reboot can be scheduled? If I don't hear anything better I will try that tonight. Best Regards, John D. Schneider Lead Systems Administrator - Storage Sisters of Mercy Health Systems 3637 South Geyer Road St. Louis, MO 63127 Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL
Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address.
Try DSNLOOKUP NO in the dsmserv.opt file. The default is YES. Bill Boyer Hang in there, retirement is only thirty years away! - ?? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 1:49 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address. Tim, We have tried this, but it doesn't help. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So the TSM scheduler seems to still know what the IP address is, but for some reason still does a DNS resolve I guess. Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Conway, Timothy Sent: Thursday, September 18, 2008 11:09 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. The simplest solution is upd node STLO-MPVADM HLA=10.52.27.204 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 9:29 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Greetings, We are running TSM 5.4.3.0 on AIX 5.3ML5. Most of our TSM clients are 5.4.x or 5.5.x. Most of our clients run schedmode prompted so the TSM server launches the schedule. We see an occasional problem where a Windows client is set up wrong in Active Directory (which feeds DNS), and the TSM scheduler won't be able to start the client scheduler. It will get errors such as: 09/18/08 05:51:12 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:52:58 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:54:44 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:56:30 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:58:16 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 06:00:01 ANR2578W Schedule WIN_PROD_0300 in domain WIN_PROD for node STLO-MPVADM has missed its scheduled start up window. In looking into it, what seems to be happening is that it's forward resolve in DNS doesn't match it's reverse resolve. Here is an example: W:\nslookup stlo-mpvadm Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.smrcy.com Address: 10.52.27.204 W:\nslookup 10.52.27.204 Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.company.com Address: 10.52.27.204 W:\ Notice that the domain name of the host is different on the forward and the reverse resolve. That is a mistake. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So what is TSM's problem here? It knows the correct IP address. What difference does it make that the reverse resolve doesn't match? Or is the problem with the client? Is it not responding? The client's dsmwebcl.log and dsmerror.log show no evidence that it is getting contacted at all. The right way to fix this is to fix the Active Directory root cause, but sometimes that requires a reboot of the client which can taken a week or more to schedule. Is the schedmode setting at fault? Would changing it to polling get around this until a reboot can be scheduled? If I don't hear anything better I will try that tonight. Best Regards, John D. Schneider Lead Systems Administrator - Storage Sisters of Mercy Health Systems 3637 South Geyer Road St. Louis, MO 63127 Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] This e-mail contains information which (a) may be PROPRIETARY IN NATURE OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for the use of the addressee(s) named above. If you are not the addressee, or the person responsible for delivering this to the addressee(s), you are notified that reading, copying or distributing this e-mail is prohibited. If you have received this e-mail in error, please contact the sender immediately. This e-mail contains information which (a) may be PROPRIETARY IN NATURE OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for the use of the addressee(s) named above. If you are not the addressee, or the person responsible
Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address.
Bill, Never heard of this option. Won't this make us unable to reach ANY clients then, unless we put them in the local /etc/hosts file? That would be impractical, with 1600 clients in our environment. Or will TSM use the cached copy it saved when the client first connected in? Do you use that in your environment? Does it work seamlessly, or are there gotchas? Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bill Boyer Sent: Thursday, September 18, 2008 1:31 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Try DSNLOOKUP NO in the dsmserv.opt file. The default is YES. Bill Boyer Hang in there, retirement is only thirty years away! - ?? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 1:49 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address. Tim, We have tried this, but it doesn't help. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So the TSM scheduler seems to still know what the IP address is, but for some reason still does a DNS resolve I guess. Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Conway, Timothy Sent: Thursday, September 18, 2008 11:09 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. The simplest solution is upd node STLO-MPVADM HLA=10.52.27.204 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 9:29 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Greetings, We are running TSM 5.4.3.0 on AIX 5.3ML5. Most of our TSM clients are 5.4.x or 5.5.x. Most of our clients run schedmode prompted so the TSM server launches the schedule. We see an occasional problem where a Windows client is set up wrong in Active Directory (which feeds DNS), and the TSM scheduler won't be able to start the client scheduler. It will get errors such as: 09/18/08 05:51:12 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:52:58 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:54:44 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:56:30 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:58:16 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 06:00:01 ANR2578W Schedule WIN_PROD_0300 in domain WIN_PROD for node STLO-MPVADM has missed its scheduled start up window. In looking into it, what seems to be happening is that it's forward resolve in DNS doesn't match it's reverse resolve. Here is an example: W:\nslookup stlo-mpvadm Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.smrcy.com Address: 10.52.27.204 W:\nslookup 10.52.27.204 Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.company.com Address: 10.52.27.204 W:\ Notice that the domain name of the host is different on the forward and the reverse resolve. That is a mistake. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So what is TSM's problem here? It knows the correct IP address. What difference does it make that the reverse resolve doesn't match? Or is the problem with the client? Is it not responding? The client's dsmwebcl.log and dsmerror.log show no evidence that it is getting contacted at all. The right way to fix this is to fix the Active Directory root cause, but sometimes that requires a reboot of the client which can taken a week or more to schedule. Is the schedmode setting at fault? Would changing it to polling get around this until a reboot can be scheduled? If I don't hear anything better I will try that tonight. Best Regards, John D. Schneider Lead Systems Administrator - Storage Sisters of Mercy Health Systems 3637 South Geyer Road St. Louis, MO
Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address.
Richard Thanks for your post. It seems odd to me too that it doesn't spell out the IP address when it tries to connect, but when you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 ... However, it may attempt to do a DNS resolve anyway, or a reverse resolve on the IP address, and that is when it gets into trouble. The DNS inconsistency only exists for this one client, and because of how Active Directory works, I will have to reboot the client to fix it, which will take a few days to plow through the bureaucracy. Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: Thursday, September 18, 2008 11:15 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. John - The ANR8213W message is conspicuously deficient in not parenthetically including the IP address along with the network name that it's reporting, such that you don't know for certain what address the TSM server is using in making the connection attempt. With DNS awry at your location, it may be that in the last client-server interaction that an address was obtained for the next interaction, where that address is no longer valid. IBM Technote 1296826 goes into other aspects of this situation. I would not fault TSM in the missed schedule: I would not want my server to be interacting with dubious network addresses where supposedly secured host data is involved. Flakey DNS is a very bad situation, and needs to get permanently fixed there. If you have good Security people there, they should be railing on people about the ramifications of erroneous network addresses being given out by your DNS servers. You can look into the DNSLOOKUP option for your TSM server, but there remains the larger issue of bad addresses being given out in the environment in general. Richard Sims This e-mail contains information which (a) may be PROPRIETARY IN NATURE OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for the use of the addressee(s) named above. If you are not the addressee, or the person responsible for delivering this to the addressee(s), you are notified that reading, copying or distributing this e-mail is prohibited. If you have received this e-mail in error, please contact the sender immediately.
Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address.
John - One last thought: A 10-net is in use there (private net - no routing). As such fussy firewall rules may be in force, which with the DNS happening may be a further impediment to reaching that TSM client through the server. Some basic network tracing (Wireshark, et al) in conjunction with a TSM server Define Clientaction simple interaction may illuminate what's going on. Richard
Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address.
I specify this on almost all my TSM servers and haven't seen any adverse effects. Bypasses the DNS issues like what you have right now. It is a documented option in the Admin Reference. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 3:35 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address. Bill, Never heard of this option. Won't this make us unable to reach ANY clients then, unless we put them in the local /etc/hosts file? That would be impractical, with 1600 clients in our environment. Or will TSM use the cached copy it saved when the client first connected in? Do you use that in your environment? Does it work seamlessly, or are there gotchas? Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bill Boyer Sent: Thursday, September 18, 2008 1:31 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Try DSNLOOKUP NO in the dsmserv.opt file. The default is YES. Bill Boyer Hang in there, retirement is only thirty years away! - ?? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 1:49 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address. Tim, We have tried this, but it doesn't help. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So the TSM scheduler seems to still know what the IP address is, but for some reason still does a DNS resolve I guess. Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Conway, Timothy Sent: Thursday, September 18, 2008 11:09 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. The simplest solution is upd node STLO-MPVADM HLA=10.52.27.204 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 9:29 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Greetings, We are running TSM 5.4.3.0 on AIX 5.3ML5. Most of our TSM clients are 5.4.x or 5.5.x. Most of our clients run schedmode prompted so the TSM server launches the schedule. We see an occasional problem where a Windows client is set up wrong in Active Directory (which feeds DNS), and the TSM scheduler won't be able to start the client scheduler. It will get errors such as: 09/18/08 05:51:12 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:52:58 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:54:44 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:56:30 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:58:16 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 06:00:01 ANR2578W Schedule WIN_PROD_0300 in domain WIN_PROD for node STLO-MPVADM has missed its scheduled start up window. In looking into it, what seems to be happening is that it's forward resolve in DNS doesn't match it's reverse resolve. Here is an example: W:\nslookup stlo-mpvadm Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.smrcy.com Address: 10.52.27.204 W:\nslookup 10.52.27.204 Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.company.com Address: 10.52.27.204 W:\ Notice that the domain name of the host is different on the forward and the reverse resolve. That is a mistake. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So what is TSM's problem here? It knows the correct IP address. What difference does it make that the reverse resolve doesn't match? Or is the problem with the client? Is it not responding? The client's dsmwebcl.log and dsmerror.log show no evidence that it is getting contacted at all. The right way to fix
Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address.
TSM will populate field TCP_ADDRESS in table NODES with the numeric address of the client when it connects, so not having name lookups performed is really no loss in functionality... And now that I know about that option, it's going in next restart, because it will cut latency, which will matter for things like when an RMAN client deletes its old backups in a flurry of hundreds of separate sessions in sequence. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 1:35 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Bill, Never heard of this option. Won't this make us unable to reach ANY clients then, unless we put them in the local /etc/hosts file? That would be impractical, with 1600 clients in our environment. Or will TSM use the cached copy it saved when the client first connected in? Do you use that in your environment? Does it work seamlessly, or are there gotchas? Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bill Boyer Sent: Thursday, September 18, 2008 1:31 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Try DSNLOOKUP NO in the dsmserv.opt file. The default is YES. Bill Boyer Hang in there, retirement is only thirty years away! - ?? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 1:49 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address. Tim, We have tried this, but it doesn't help. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So the TSM scheduler seems to still know what the IP address is, but for some reason still does a DNS resolve I guess. Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Conway, Timothy Sent: Thursday, September 18, 2008 11:09 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. The simplest solution is upd node STLO-MPVADM HLA=10.52.27.204 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 9:29 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Greetings, We are running TSM 5.4.3.0 on AIX 5.3ML5. Most of our TSM clients are 5.4.x or 5.5.x. Most of our clients run schedmode prompted so the TSM server launches the schedule. We see an occasional problem where a Windows client is set up wrong in Active Directory (which feeds DNS), and the TSM scheduler won't be able to start the client scheduler. It will get errors such as: 09/18/08 05:51:12 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:52:58 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:54:44 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:56:30 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:58:16 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 06:00:01 ANR2578W Schedule WIN_PROD_0300 in domain WIN_PROD for node STLO-MPVADM has missed its scheduled start up window. In looking into it, what seems to be happening is that it's forward resolve in DNS doesn't match it's reverse resolve. Here is an example: W:\nslookup stlo-mpvadm Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.smrcy.com Address: 10.52.27.204 W:\nslookup 10.52.27.204 Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.company.com Address: 10.52.27.204 W:\ Notice that the domain name of the host is different on the forward and the reverse resolve. That is a mistake. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So what is TSM's problem here? It knows the correct IP address. What
Re: Where to modify SMTP IP Address for TSM Operational Reporting
Mark Tivoli Storage Manager in MMC, right click and TSM Operational Reporting and then use tab E-Mail Account. /Larsa -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Jiangxi Wazi Sent: den 12 augusti 2008 16:36 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Where to modify SMTP IP Address for TSM Operational Reporting Hi, Group, Where to modify SMTP IP Address for TSM Operational Reporting? I searched old forum, they mention mentioned where to modify report recipent, but I need to modify SMTP server IP address for TSM operatinal report. Thank you, J. This communication is from a Carnegie company within the Carnegie Group. The information contained in it, including any attachment or enclosure, is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any unauthorised use, review, retransmissions, dissemination, copying or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete or shred the material immediately. Thank you. Opinions, conclusions and other information expressed in this message are not given or endorsed by my firm or employer unless otherwise indicated by an authorised representative independent of this message.
Where to modify SMTP IP Address for TSM Operational Reporting
Hi, Group, Where to modify SMTP IP Address for TSM Operational Reporting? I searched old forum, they mention mentioned where to modify report recipent, but I need to modify SMTP server IP address for TSM operatinal report. Thank you, J.
Re: IP address
Avy, If you need the name as configured on the server, just the q session command from any BA client with that IP address in its dsm.sys (or dsm.opt) file, like the following example from one of my Unix clients. The server name in this case is TSM_WAYNE_DR. wau004:/home/root dsmc q se Tivoli Storage Manager Command Line Backup/Archive Client Interface - Version 5, Release 1, Level 1.0 (C) Copyright IBM Corporation 1990, 2002 All Rights Reserved. Node Name: WAU004 Session established with server TSM_WAYNE_DR: HP-UX Server Version 5, Release 3, Level 2.0 Server date/time: 11/27/06 08:51:08 Last access: 11/27/06 08:50:04 TSM Server Connection Information Server Name.: TSM_WAYNE_DR Server Type.: HP-UX Server Version..: Ver. 5, Rel. 3, Lev. 2.0 Last Access Date: 11/27/06 08:50:04 Delete Backup Files.: No Delete Archive Files: Yes Node Name...: WAU004 User Name...: root wau004:/home/root _RS Avy Wong [EMAIL PROTECTED] .COM To Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager [EMAIL PROTECTED] Subject .EDU IP address 11/24/2006 03:52 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] .EDU hello, Can you tell me if there is a way to find out what is the server name when all I have is an ip address? is there a query to do that? Thanks. Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382 ext 28164 ** The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. **
IP address
hello, Can you tell me if there is a way to find out what is the server name when all I have is an ip address? is there a query to do that? Thanks. Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382 ext 28164 ** The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. **
Re: IP address
Avy Wong wrote: hello, Can you tell me if there is a way to find out what is the server name when all I have is an ip address? is there a query to do that? Thanks. no there is no tool, otoh, it really doesn't matter, the name configured in the client doesn't need to match anything configured on the server. Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382 ext 28164 ** The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** -- Met vriendelijke groeten, Remco Post SARA - Reken- en Netwerkdiensten http://www.sara.nl High Performance Computing Tel. +31 20 592 3000Fax. +31 20 668 3167 PGP Key fingerprint = 6367 DFE9 5CBC 0737 7D16 B3F6 048A 02BF DC93 94EC I really didn't foresee the Internet. But then, neither did the computer industry. Not that that tells us very much of course - the computer industry didn't even foresee that the century was going to end. -- Douglas Adams
Re: IP address
Use a select statement from the nodes table. select node_name,tcp_address from nodes where tcp_address='xxx.xxx.xxx.xxx' (Put in the address you have of course.) The client has to be at least TSM version 5.1 to get this, older versions will have blank for tcp_address. David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5509 [EMAIL PROTECTED] Avy Wong [EMAIL PROTECTED] 11/24/06 3:52 PM hello, Can you tell me if there is a way to find out what is the server name when all I have is an ip address? is there a query to do that? Thanks. Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382 ext 28164 ** The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** ## This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ##
TSM on Z/OS and not primary TCP/IP address space
I am trying to use a non primary TCP/IP address space for TSM. TSM is accessible via http port 1580 when I code tcpnameTCPIP in the Z/OS TSM Options file (TCPIP is the primary address space) but is not accessible if I try and use a another TCP/IP address space by coding tcpnameTCPIPT Any ideas ?? Tim Brown Systems Specialist Central Hudson Gas Electric 284 South Ave Poughkeepsie, NY 12601 Email: [EMAIL PROTECTED] Phone: 845-486-5643 Fax: 845-486-5921 Cell: 845-235-4255
IP Address Change
Hey everyone! The IP address of our library which is an STK SL8500 is changing. Will that affect our TSM server at all and will any configuration changes need to be made? Our TSM server is an AIX 5.2 with TSM v5.2.4. Thanks! Joni Moyer Highmark Storage Systems Work:(717)302-6603 Fax:(717)302-5974 [EMAIL PROTECTED]
Tr : IP Address Change
Hi, If you use the SAN to communicate between library and TSM server, there is no effect. But if you use IP you have to change the configuration. Best Regards Hassan MOURTADI SAP basis administrator - Réacheminé par Hassan MOURTADI/MOR/LDE/SLE le 26/08/2005 12:04 - Joni Moyer [EMAIL PROTECTED] Envoyé par : ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 26/08/2005 11:45 Veuillez répondre à ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU A ADSM-L@VM.MARIST.EDU cc Objet IP Address Change Hey everyone! The IP address of our library which is an STK SL8500 is changing. Will that affect our TSM server at all and will any configuration changes need to be made? Our TSM server is an AIX 5.2 with TSM v5.2.4. Thanks! Joni Moyer Highmark Storage Systems Work:(717)302-6603 Fax:(717)302-5974 [EMAIL PROTECTED]
Tr : Re: Tr : IP Address Change
Hi, I think there is no effect because you use LANFREE to backup to the library SL8500 !! Best Rgds HM - Réacheminé par Hassan MOURTADI/MOR/LDE/SLE le 26/08/2005 12:12 - [EMAIL PROTECTED] 26/08/2005 12:13 A [EMAIL PROTECTED] cc Objet Re: Tr : IP Address Change Hi! I'm not quite sure how to tell? We do have a McData director located between our TSM server and the SL8500 library. Is that what you mean? Here is how I have 2 different library configurations defined on TSM. Thanks again! Library Name: NASLIB Library Type: ACSLS ACS Id: 0 Private Category: Scratch Category: WORM Scratch Category: External Manager: Shared: No LanFree: ObeyMountRetention: Library Name: SL8500 Library Type: External ACS Id: Private Category: Scratch Category: WORM Scratch Category: External Manager: Shared: No LanFree: Yes ObeyMountRetention: Yes Joni Moyer Highmark Storage Systems Work:(717)302-6603 Fax:(717)302-5974 [EMAIL PROTECTED] [EMAIL PROTECTED] ydec.co.ma To 08/26/2005 08:10 [EMAIL PROTECTED] AM cc ADSM-L@VM.MARIST.EDU Subject Tr : IP Address Change Hi, If you use the SAN to communicate between library and TSM server, there is no effect. But if you use IP you have to change the configuration. Best Regards Hassan MOURTADI SAP basis administrator - Réacheminé par Hassan MOURTADI/MOR/LDE/SLE le 26/08/2005 12:04 - Joni Moyer [EMAIL PROTECTED] Envoyé par : ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU A [EMAIL PROTECTED] EDU 26/08/2005 11:45 cc Objet Veuillez répondre à IP Address Change ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Hey everyone! The IP address of our library which is an STK SL8500 is changing. Will that affect our TSM server at all and will any configuration changes need to be made? Our TSM server is an AIX 5.2 with TSM v5.2.4. Thanks! Joni Moyer Highmark Storage Systems Work:(717)302-6603 Fax:(717)302-5974 [EMAIL PROTECTED]
IP address selection by TSM server
I asked this before, but never got any response. I need to asked it again, since the issue has arisen, again, and I can see this escalating into a bigger problem. The TSM AIX server is multi-homed (external/public normal 10/100 connection and internal/private 10/100/1000 private subnet). A client contacts the TSM server on the public (128.172.x) connection. Then the TSM server tries to contact the client via the private, 192.168.x subnet. Is there any way to tell the TSM server to contact the client via the same IP connection that was used to contact it, unless the client has tcpclientaddress specified to use the private network ?
Re: IP address selection by TSM server
I'll take a shot . . . . Could this be a routing issue? You may have a default route setup to point to the router on the private network. All hosts not on the locally attach networks ( that are arp'able ) will have reply packets sent to the default route. If this is the case, then you will need to setup a static route for hosts/networks that are off the immediate public net. Rick Zoltan Forray/AC/VCUTo: ADSM-L@VM.MARIST.EDU [EMAIL PROTECTED]cc: Sent by: ADSM: Subject: IP address selection by TSM server Dist Stor Manager [EMAIL PROTECTED] .EDU 01/26/2005 10:48 AM Please respond to ADSM: Dist Stor Manager I asked this before, but never got any response. I need to asked it again, since the issue has arisen, again, and I can see this escalating into a bigger problem. The TSM AIX server is multi-homed (external/public normal 10/100 connection and internal/private 10/100/1000 private subnet). A client contacts the TSM server on the public (128.172.x) connection. Then the TSM server tries to contact the client via the private, 192.168.x subnet. Is there any way to tell the TSM server to contact the client via the same IP connection that was used to contact it, unless the client has tcpclientaddress specified to use the private network ? - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: IP address selection by TSM server
Hi, Somehow your AIX server thinks the client can be reached by the private network (default gateway). It seems to me to be something like a routing problem within you network. Work around can be to add some routing information in you AIX server. Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: woensdag 26 januari 2005 16:49 To: ADSM-L@VM.MARIST.EDU Subject: IP address selection by TSM server I asked this before, but never got any response. I need to asked it again, since the issue has arisen, again, and I can see this escalating into a bigger problem. The TSM AIX server is multi-homed (external/public normal 10/100 connection and internal/private 10/100/1000 private subnet). A client contacts the TSM server on the public (128.172.x) connection. Then the TSM server tries to contact the client via the private, 192.168.x subnet. Is there any way to tell the TSM server to contact the client via the same IP connection that was used to contact it, unless the client has tcpclientaddress specified to use the private network ?
Re: IP address selection by TSM server
On Jan 26, 2005, at 10:48 AM, Zoltan Forray/AC/VCU wrote: ...Is there any way to tell the TSM server to contact the client via the same IP connection that was used to contact it, unless the client has tcpclientaddress specified to use the private network ? In a multi-homed arrangement with routed and non-routed subnet usage, I would do an UPDate Node and plant the desired address in the HLAddress field. Richard Sims
TSM scheduler using the wrong IP address for a node
Hi there, we're using TSM 5.2.2.2 on AIX 5.2. The client is at 5.2.2.5, also on AIX 5.2. (Both 64 bit) I cloned a machine using mksysb. On the clone, I changed the IP address. I accidentally started the dsmcad process with an unchanged configuration. This caused the TSM server to update the information it has for that node. This was shown in a q nod tridev1 f=d. I stopped and disabled the TSM installation on the clone, and did a manual backup with the original machine. This worked fine, and both 'q nod tridev1 f=d' and select * from nodes where node_name='TRIDEV1' now show the correct IP address. However: the scheduler still insist on using the wrong IP address. Given the output of select * from nodes where node_name='TRIDEV1' below, how is this possible? NODE_NAME: TRIDEV1 PLATFORM_NAME: AIX DOMAIN_NAME: PD_TRIAS PWSET_TIME: 2003-10-29 14:27:10.00 INVALID_PW_COUNT: 0 CONTACT: COMPRESSION: CLIENT ARCHDELETE: YES BACKDELETE: NO LOCKED: NO LASTACC_TIME: 2004-04-23 09:22:21.00 REG_TIME: 2001-06-11 13:43:07.00 REG_ADMIN: MM LASTSESS_COMMMETH: Tcp/Ip LASTSESS_RECVD: 15210894 LASTSESS_SENT: 17493 LASTSESS_DURATION: +3.960900E+001 LASTSESS_IDLEWAIT: +1.43906687873968E-001 LASTSESS_COMMWAIT: +4.57724254588603E+000 LASTSESS_MEDIAWAIT: +0.00E+000 CLIENT_VERSION: 5 CLIENT_RELEASE: 2 CLIENT_LEVEL: 2 CLIENT_SUBLEVEL: 5 CLIENT_OS_LEVEL: 5.2 OPTION_SET: AGGREGATION: YES URL: http://tridev1.trias.nl:1581/ NODETYPE: CLIENT PASSEXP: KEEP_MP: NO MAX_MP_ALLOWED: 3 AUTO_FS_RENAME: NO VALIDATEPROTOCOL: NO TCP_NAME: tridev1 TCP_ADDRESS: 172.17.1.42 GUID: 05.50.1b.d0.d8.9e.11.d7.9b.74.08.63.ac.11.01.8b TXNGROUPMAX: 0 DATAWRITEPATH: ANY DATAREADPATH: ANY SESSION_INITIATION: ClientOrServer CLIENT_HLA: CLIENT_LLA: Only after executing UPD NOD TRIDEV1 HLADDRESS='172.17.1.42' LLADDRESS='1500', the scheduler used the correct address. There's also something wrong with UPDATE NODE: if you issue UPD NOD TRIDEV1 HLADDRESS='172.17.1.41' the response is Node updated, but that is in fact not the case. In the actlog an error is reported: 04/23/04 10:39:07 ANR2017I Administrator JOSKAM issued command: UPDATE NODE tridev1 hladdress=172.17.1.42 (SESSION: 26308) 04/23/04 10:39:07 ANR4739E Either the high level address ( 172.17.1.42 ), l ow level address( ? ), or both were entered in error. ( SESSION: 26308) 04/23/04 10:39:07 ANR2063I Node TRIDEV1 updated. (SESSION: 26308) You don't get to see the ANR4739E unless you look in the actlog. -- Jurjen Oskam Avoid putting a paging file on a fault-tolerant drive, such as a mirrored volume or a RAID-5 volume. Paging files do not need fault-tolerance. - 308417
Re: TCP/IP NAME TCP/IP ADDRESS
Need a little assistance on this. I issue q node f=d from the server side for a NODE_A, I get a TCP/IP NAME and TCP/IP ADDRESS that are incorrect (say NODE_B). At some point I may have connected virtually w/ the TCP/IP NAME (NODE_B) that I'm seeing, but even after I connect from the local host, NODE_A, the TCP/IP NAME and TCP/IP ADDRESS still reflect NODE_B's information. I've seen this on a few instances. What drew this to my attention is the fact that I had 8 sessions started for one archive on NODE_A and no resource definition in the dsm.sys. When I checked the dsm.sys on NODE_B, lo and behold, resource utilization is set to 10. What am I missing? Server Platform Z/os running TSM Server v5,1,6.1 NODE_A Client Platform Sun2.8 running BAclient TSMv4,2,2.1 NODE_B Client Platform Sun2.8 running BAclient TSMv4,2,1.0 Any help would be greatly appreciated. thx. Joseph - I would first check your client options files as Zlatko suggests. Do 'dsmc q opt', and check the modification datestamps on the files to see if someone induced change (TCPCLIENTAddress, NODename, DEFAULTServer). It would be unlikely, but check that no DSM_* environment variables are causing use of unexpected options files. I would also do 'netstat -i' and 'netstat -in' on those Solaris clients to verify that what they think they are matches what you think they are...that no interesting network configuration changes have transpired. If these clients perform TSM actions at distinctly different times, examine dsmaccnt.log for hostnames being what they should in there and, if not, look back to see when it apparently changed, and pursue from there. Richard Sims, BU
Re: TCP/IP NAME TCP/IP ADDRESS
RESOURceutilization is an option which can be defined in a client option set on the server. The other possibility is that Node_B is indeed connecting and is having NODename=Node_A in some dsm.sys stanza. In fact I cannot recall when address seen in Nodes table is updated - during client operations or when scheduler is connecting. Zlatko Krastev IT Consultant Wholey, Joseph (IDS DMDS) [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 20.09.2003 05:11 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:TCP/IP NAME TCP/IP ADDRESS Need a little assistance on this. I issue q node f=d from the server side for a NODE_A, I get a TCP/IP NAME and TCP/IP ADDRESS that are incorrect (say NODE_B). At some point I may have connected virtually w/ the TCP/IP NAME (NODE_B) that I'm seeing, but even after I connect from the local host, NODE_A, the TCP/IP NAME and TCP/IP ADDRESS still reflect NODE_B's information. I've seen this on a few instances. What drew this to my attention is the fact that I had 8 sessions started for one archive on NODE_A and no resource definition in the dsm.sys. When I checked the dsm.sys on NODE_B, lo and behold, resource utilization is set to 10. What am I missing? Server Platform Z/os running TSM Server v5,1,6.1 NODE_A Client Platform Sun2.8 running BAclient TSMv4,2,2.1 NODE_B Client Platform Sun2.8 running BAclient TSMv4,2,1.0 Any help would be greatly appreciated. thx.
TCP/IP NAME TCP/IP ADDRESS
Need a little assistance on this. I issue q node f=d from the server side for a NODE_A, I get a TCP/IP NAME and TCP/IP ADDRESS that are incorrect (say NODE_B). At some point I may have connected virtually w/ the TCP/IP NAME (NODE_B) that I'm seeing, but even after I connect from the local host, NODE_A, the TCP/IP NAME and TCP/IP ADDRESS still reflect NODE_B's information. I've seen this on a few instances. What drew this to my attention is the fact that I had 8 sessions started for one archive on NODE_A and no resource definition in the dsm.sys. When I checked the dsm.sys on NODE_B, lo and behold, resource utilization is set to 10. What am I missing? Server Platform Z/os running TSM Server v5,1,6.1 NODE_A Client Platform Sun2.8 running BAclient TSMv4,2,2.1 NODE_B Client Platform Sun2.8 running BAclient TSMv4,2,1.0 Any help would be greatly appreciated. thx.
Client doesn't ask for password when IP address changes?
Hello, I'm using TSM (5.1.1.0 client) on Windows XP (SP 1) to backup my PC at home. This weekend I switched from one ISP (cable) to another ISP (ADSL). This of course changed the IP address and hostname of my PC completely. The change of IP adress is clearly visible in the activity log on the server when I search for the Session started for node BLAHBLA message. When I started the backup client after the change it never asked me for the node's password, it just logged on to the server and allowed me to start a backup. I'm absolutely sure of this because I've forgotten the password so when it *had* asked me for I wouldn't have known it. I can't explain this behaviour. Shouldn't the client prompt for a password when I change to IP address or hostname? Our server is 4.2.3.2 (4.2.3.3 in a few hours) on AIX 4.3.3.0 Kind regards, Alexander -- --- Alexander Verkooijen([EMAIL PROTECTED]) Senior Systems Programmer SARA High Performance Computing
Re: Client doesn't ask for password when IP address changes?
If you had no nodename option in dsm.opt your hostname acts as nodename. Thus on hostname (not IP address) change you have to be authenticated as new node. If nodename option is defined it is used for password matching not the hostname. Either you have nodename option (and nodename/generated password pair is still valid) or your server is on open registration. Also you might changed you Internet address but your VPN address is the same. Please, please, do not tell me your TSM is open to Internet and your nodename/password is going without VPN! Zlatko Krastev IT Consultant Alexander Verkooijen [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 27.01.2003 12:45 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Client doesn't ask for password when IP address changes? Hello, I'm using TSM (5.1.1.0 client) on Windows XP (SP 1) to backup my PC at home. This weekend I switched from one ISP (cable) to another ISP (ADSL). This of course changed the IP address and hostname of my PC completely. The change of IP adress is clearly visible in the activity log on the server when I search for the Session started for node BLAHBLA message. When I started the backup client after the change it never asked me for the node's password, it just logged on to the server and allowed me to start a backup. I'm absolutely sure of this because I've forgotten the password so when it *had* asked me for I wouldn't have known it. I can't explain this behaviour. Shouldn't the client prompt for a password when I change to IP address or hostname? Our server is 4.2.3.2 (4.2.3.3 in a few hours) on AIX 4.3.3.0 Kind regards, Alexander -- --- Alexander Verkooijen([EMAIL PROTECTED]) Senior Systems Programmer SARA High Performance Computing
Re: Client doesn't ask for password when IP address changes?
Hi, Our server doesn't allow open registration. My dsm.opt contains the nodename option and the nodename hasn't changed. So that must be why the client didn't ask for the password. I always thought that changing the IP address/hostname would cause the client to prompt for the password again regardless whether the nodename had changed or not. Thanks for explaining this to me. Best regards, Alexander If you had no nodename option in dsm.opt your hostname acts as nodename. Thus on hostname (not IP address) change you have to be authenticated as new node. If nodename option is defined it is used for password matching not the hostname. Either you have nodename option (and nodename/generated password pair is still valid) or your server is on open registration. Also you might changed you Internet address but your VPN address is the same. Please, please, do not tell me your TSM is open to Internet and your nodename/password is going without VPN! Zlatko Krastev IT Consultant Alexander Verkooijen [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 27.01.2003 12:45 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Client doesn't ask for password when IP address changes? Hello, I'm using TSM (5.1.1.0 client) on Windows XP (SP 1) to backup my PC at home. This weekend I switched from one ISP (cable) to another ISP (ADSL). This of course changed the IP address and hostname of my PC completely. The change of IP adress is clearly visible in the activity log on the server when I search for the Session started for node BLAHBLA message. When I started the backup client after the change it never asked me for the node's password, it just logged on to the server and allowed me to start a backup. I'm absolutely sure of this because I've forgotten the password so when it *had* asked me for I wouldn't have known it. I can't explain this behaviour. Shouldn't the client prompt for a password when I change to IP address or hostname? Our server is 4.2.3.2 (4.2.3.3 in a few hours) on AIX 4.3.3.0 Kind regards, Alexander -- --- Alexander Verkooijen([EMAIL PROTECTED]) Senior Systems Programmer SARA High Performance Computing
Windows CAD: bind to specific IP address?
Hi there, On a Microsoft Cluster, I'd like to install the TSM client. The cluster is set up as follows: * two physical machines, CL1 and CL2 * two 'virtual' machines, NT1 and PS1 I'd like to create four TSM Client Nodes: CL1, CL2, NT1 and PS1. Both the cluster nodes CL1 and CL2, as well as the cluster resources NT1 and PS1 have their own IP address. (This means there are four IP addresses in total). What I would like to do is create four instances of the Client Acceptor Daemon. One for CL1 bound to the IP address of CL1, one for NT1 bound to the IP address of NT1, and so on. The problem is that the Client Acceptor binds to 0.0.0.0. I cannot find a way to tell the Client Acceptor to bind to a specific IP address. There is a way to tell the TSM server to connect to a specific IP address (TCPClientAddress parameter) when contacting the specific client node, but this doesn't stop the Client Acceptor on that node to still bind to all IP addresses on the machine. -- Jurjen Oskam PGP Key available at http://www.stupendous.org/
Re: TSM server buffering client IP address ?
Arnaud, Yes, the server does remember the last address the client accessed it from. After you change the client address, and reboot the client to make sure the new address is firm, you want to run some query like dsmc q sched or dsmc q ses to make the most recent contact come from the new address. - Kai. Date:Fri, 8 Mar 2002 10:49:09 +0100 From:PAC Brion Arnaud [EMAIL PROTECTED] Subject: TSM server buffering client IP address ? Hi gurus ! I'm facing the following problem : we have a client node which IP = address has been modified yesterday morning, the machine has then been = rebooted, and of course, TSM client restarted. But this morning TSM = showed me the scheduled nightly backup for this node as missed.=20 I have a test schedule, that can be started manually, to test a = connection between TSM and client node. After having been restarting = client once again, I tried to execute this schedule, and this time = obtained missed. Ping between client and sever works in both directions, so there is no = connection issue. Dsmsched log and error files don't show any problem. After several retries, I decided with our network admin to trace IP = exchanges between the two machines, and we found that after having been = restarting the scheduler, systems where using the new node IP address = for some transactions, but at a certain point, TSM tried to use the OLD = ip address of the node ! Thus our test schedule fails ! Could anybody tell me if there is any kind of buffer in TSM, that = needs a certain time to be flushed before attributing new ip addresses = to nodes, or something like this ? How does exactly works TSM node - server relation when starting a = schedule, is there any kind of explanation ? Please help me, I absolutely have no idea of what happens. The picture : TSM server v 4.1.3 on aix 4.3.3 TSM node v 3.1.0.7 on aix 4.3.3 , in a DNZ (firewall = ports and IP addresses have been verified and are opened) Thanks in advance ! Arnaud
Re: TSM server buffering client IP address ?
Arnaud, I would flush all your routing information on both of the AIX servers. There could still be some routes to the old address in there and these would need to be deleted so that the server will only use the new route. Also have you checked the /etc/hosts files on the AIX server? # netstat -rn will show you your currents routes, you can either identify the old route that is being used or flush them all by using the command # route flush You can then so the netstat -rn command to see the new routing table. HIH Steve -Original Message- From: PAC Brion Arnaud [mailto:[EMAIL PROTECTED]] Sent: 08 March 2002 09:49 To: [EMAIL PROTECTED] Subject: TSM server buffering client IP address ? This email and any files transmitted have been checked by the MessageLabs Virus Scanning Service for the presence of computer viruses. Please exercise caution when receiving any attachment(s) from unknown sources. If in any doubt, do not open any attachment and delete the message immediately. Thank you for your co-operation. _ Hi gurus ! I'm facing the following problem : we have a client node which IP address has been modified yesterday morning, the machine has then been rebooted, and of course, TSM client restarted. But this morning TSM showed me the scheduled nightly backup for this node as missed. I have a test schedule, that can be started manually, to test a connection between TSM and client node. After having been restarting client once again, I tried to execute this schedule, and this time obtained missed. Ping between client and sever works in both directions, so there is no connection issue. Dsmsched log and error files don't show any problem. After several retries, I decided with our network admin to trace IP exchanges between the two machines, and we found that after having been restarting the scheduler, systems where using the new node IP address for some transactions, but at a certain point, TSM tried to use the OLD ip address of the node ! Thus our test schedule fails ! Could anybody tell me if there is any kind of buffer in TSM, that needs a certain time to be flushed before attributing new ip addresses to nodes, or something like this ? How does exactly works TSM node - server relation when starting a schedule, is there any kind of explanation ? Please help me, I absolutely have no idea of what happens. The picture : TSM server v 4.1.3 on aix 4.3.3 TSM node v 3.1.0.7 on aix 4.3.3 , in a DNZ (firewall ports and IP addresses have been verified and are opened) Thanks in advance ! Arnaud =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | Arnaud Brion, Panalpina Management Ltd., IT Group | | Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland | | Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01 | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= _ This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify [EMAIL PROTECTED] This footnote also confirms that this message has been swept for all known viruses by the MessageLabs Virus Scanning Service. For further information please visit http://www.messagelabs.com
Re: TSM server buffering client IP address ?
Arnaud, just one possibility: Did you check your dsm.sys for a parameter like TCPCLIENTADDRESS? This could make the TSM server use the old address. Best regards, Michael ##TSM Online Help# Tcpclientaddress The tcpclientaddress option specifies a TCP/IP address if your client node has more than one address, and you want the server to contact an address other than the one that was used to make the first server contact. Use this option only if you use the prompted parameter with the schedmode option or when the schedule command is running. Syntax -TCPCLIENTAddress- client_address Parameters client_address Specifies the TCP/IP address you want the server to use to contact your client node. Specify a TCP/IP Internet domain name or a dot address. Examples Options file: tcpclienta dsmclnt.sanjose.ibm.com Command line: -tcpclientaddress=128.33.10.249 This option is valid only on the initial command line. It is not valid in interactive mode. ## PAC Brion Arnaud wrote: Hi gurus ! I'm facing the following problem : we have a client node which IP address has been modified yesterday morning, the machine has then been rebooted, and of course, TSM client restarted. But this morning TSM showed me the scheduled nightly backup for this node as missed. I have a test schedule, that can be started manually, to test a connection between TSM and client node. After having been restarting client once again, I tried to execute this schedule, and this time obtained missed. Ping between client and sever works in both directions, so there is no connection issue. Dsmsched log and error files don't show any problem. After several retries, I decided with our network admin to trace IP exchanges between the two machines, and we found that after having been restarting the scheduler, systems where using the new node IP address for some transactions, but at a certain point, TSM tried to use the OLD ip address of the node ! Thus our test schedule fails ! Could anybody tell me if there is any kind of buffer in TSM, that needs a certain time to be flushed before attributing new ip addresses to nodes, or something like this ? How does exactly works TSM node - server relation when starting a schedule, is there any kind of explanation ? Please help me, I absolutely have no idea of what happens. The picture : TSM server v 4.1.3 on aix 4.3.3 TSM node v 3.1.0.7 on aix 4.3.3 , in a DNZ (firewall ports and IP addresses have been verified and are opened) Thanks in advance ! Arnaud =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | Arnaud Brion, Panalpina Management Ltd., IT Group | | Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland | | Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01 | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -- Michael Bartl, Dipl. Inform. (FH) mailto:[EMAIL PROTECTED] Backup Services, IT Germany/Austria Tel: +49-89-92699-806 Cable Wireless Deutschland GmbH. Fax: +49-89-92699-302 Landsberger Str. 155, D-80687 Muenchen http://www.cw.com/de
TSM kills IP address on NT4 clients
Hello everybody, I thought maybe one of you could have experienced the following problems with TSM and NT4 clients, and maybe you can help us out with them, I sure hope so. We are trying to make archives of our NT4 clients and although some come out with a state of succes, others loose their connection with the TSM server. I know, this ain´t all that bad since these sessions are re-established, but because of this some of these clients take too long to complete (eg. 12 hours to complete a 5 Gb archive). The DSMerror.log files all show a lot of entries like: 21-11-2001 21:51:19 sessRecvVerb: Error -50 from call to 'readRtn'. All I could find on this problem was to update the drivers on the NIC´s and to adjust the settings like Duplex mode and the speed (100Mb) to match. Still, this problem persists. We made a serperate network so TSM and the Clients would not be confronted with other requests, but without succes. Other failing clients even loose their IP address during and after the archive session. Although the properties of the IP address shows up like it should on NT we can´t ping it anymore, leaving no other option then rebooting the machine. This is an example of what we see in the dsmerror.log on these clients 21-11-2001 21:22:44 ANS1810E TSM session has been reestablished. 22-11-2001 04:31:05 sessRecvVerb: Error -50 from call to 'readRtn' 22-11-2001 07:39:49 sessSendVerb: Error sending Verb, rc: -50 22-11-2001 07:39:49 ANS1809E Session is lost; initializing session reopen procedure. 22-11-2001 07:39:49 ANS1809E Session is lost; initializing session reopen procedure. 22-11-2001 07:40:14 TcpOpen: TCP/IP error connecting to server. 22-11-2001 07:40:14 sessOpen: Failure in communications open call. rc: -50 22-11-2001 07:41:05 TcpOpen: TCP/IP error connecting to server. 22-11-2001 07:41:05 sessOpen: Failure in communications open call. rc: -50 22-11-2001 07:41:56 TcpOpen: TCP/IP error connecting to server. The catch in all of this is that we can schedule an archive for two clients to run and no problems seem to appear and the archive/backup sessions completes in a short amout of time, like it should. If we update the schedule to make an archive for 4 or more clients all mentioned above seems to apply. Some background information: We are using the following components: AIX (ver. 4.3) with TSM (ver. 4.2) NT 4 with servicepack 4 and 6a clients 100 Mbit Ethernet connections (100mb/full duplex configured) Avaya P333t switch (all ports are 100mb/full duplex configured) The Maxsessions parameter is configured 40. Our goal is to make archives of 18 clients on a weekly basis, Can anyone please supply me with a hint on how I can reach my goal? Thanks in advance, Robin van der Vliet = Dit bericht is uitsluitend bestemd voor de geadresseerde en kan vertrouwelijke informatie bevatten. Gebruik door derden of openbaarmaking van dit bericht zonder toestemming van DAS Rechtsbijstand of de geadresseerde is niet toegestaan en kan onrechtmatig zijn. Aansprakelijkheid voortvloeiende uit onvolledige of niet tijdige ontvangst van dit bericht is uitgesloten. Indien dit bericht u per ongeluk bereikt, verzoeken wij u vriendelijk ons daarvan direct in kennis te stellen en het bericht te wissen. Dit bericht en eventuele bijlagen zijn gescand op de ons bekende virussen. Wij adviseren u alle berichten en bijlagen op virussen te scannen voor ze te openen. =
Change of IP Address in ADSM Server and ADSM Clients
Hi all, We currently have ADSM Version 3, Release 1, Level 2.5 on AIX 4.3.3.0 platform. We are planning to change the IP addresses for the ADSM server and its 2 clients. In line to this, will there be necessary changes in configuration after the changes in IP addresses are made? Thanks... Bryan
Re: saving IP address
If you are using SCHEDMODE PROMPTED backup mode then you will need to change the TCPCLIENTADDRESS in your options file. Then re-start the scheduler. At 12:11 PM 8/2/01 -0400, you wrote: I've had my admins both stop and start the scheduler service and login from the desktop and drill down in the backup screen but its still keeping theIP address. David Longo [EMAIL PROTECTED]@VM.MARIST.EDU on 08/02/2001 11:50:31 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: saving IP address You can't actually delete it. In this case on the client at the new IP start the services and for good measure on the client do say a dsmc and then a q ses. This should give the server the new IP and it then stores it in it's list to use to contact to run schedule. David Longo [EMAIL PROTECTED] 08/02/01 11:41AM Can anyone tell me how to flush out old IP addresses TSM must be storing when it tries to contact a client for a scheduled event. I have a AIX server trying to contact an NT client but the IP address has cahnged recently and TSM is timing out trying to contact the client at its old address. TIA Jim MMS health-first.org made the following annotations on 08/02/01 11:55:28 -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. == -- Rick SaylorAustin Community College Voice: (512)223-7511 Senior Systems Programmer 5930 Middle Fiskville Rd. Fax: (512)223-7156 Information Services Austin, Texas 78752-4331
Re: saving IP address
restart the TSM scheduler service on NT. TSM remembers the IP address used when the client first contacts it. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of James healy Sent: Thursday, August 02, 2001 11:41 AM To: [EMAIL PROTECTED] Subject: saving IP address Can anyone tell me how to flush out old IP addresses TSM must be storing when it tries to contact a client for a scheduled event. I have a AIX server trying to contact an NT client but the IP address has cahnged recently and TSM is timing out trying to contact the client at its old address. TIA Jim
saving IP address
Can anyone tell me how to flush out old IP addresses TSM must be storing when it tries to contact a client for a scheduled event. I have a AIX server trying to contact an NT client but the IP address has cahnged recently and TSM is timing out trying to contact the client at its old address. TIA Jim
Re: saving IP address
I've had my admins both stop and start the scheduler service and login from the desktop and drill down in the backup screen but its still keeping theIP address. David Longo [EMAIL PROTECTED]@VM.MARIST.EDU on 08/02/2001 11:50:31 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: saving IP address You can't actually delete it. In this case on the client at the new IP start the services and for good measure on the client do say a dsmc and then a q ses. This should give the server the new IP and it then stores it in it's list to use to contact to run schedule. David Longo [EMAIL PROTECTED] 08/02/01 11:41AM Can anyone tell me how to flush out old IP addresses TSM must be storing when it tries to contact a client for a scheduled event. I have a AIX server trying to contact an NT client but the IP address has cahnged recently and TSM is timing out trying to contact the client at its old address. TIA Jim MMS health-first.org made the following annotations on 08/02/01 11:55:28 -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ==
Re: Change IP Address
Hi If u are using IP address as server name in any of ur adsm client in dsm.sys file. Or any other applications as websphere .Pl reflect the changes accordingly. Pl see that since u are changing mask and default gateway,then ur server in on different network if I am right. Pl see that what is average round trip time of ur packet from any of ur present clients. See netstat -D o/p i.e packets are getting dropped on network or netstat -i any collisions/jaggering. Because now u have to cross router to reach the other end u need to be sure that their are no bottle necks on network. If u get error mail me I will let u know to tune ur network. -Original Message- From: Gill, Geoffrey L. [mailto:[EMAIL PROTECTED]] Sent: Monday, July 02, 2001 5:22 PM To: [EMAIL PROTECTED] Subject: Change IP Address For the AIX crowd out there, I need to change the IP address on my ADSM server this weekend. I want to know if there are any pitfalls I should look out for. It's not just an IP change on the same network, I'll be changing the IP, NETMASK and Default Gateway. Questions: Since I'm not totally AIX literate yet is there a command line command I can use that will do all 3 at once? Should I plan on rebooting the box after this change? Thanks for the help. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (888) 997-9614
Re: Change IP Address
PL also see ifconfig cmd line syntax. balanand pinni -Original Message- From: Gill, Geoffrey L. [mailto:[EMAIL PROTECTED]] Sent: Monday, July 02, 2001 5:22 PM To: [EMAIL PROTECTED] Subject: Change IP Address For the AIX crowd out there, I need to change the IP address on my ADSM server this weekend. I want to know if there are any pitfalls I should look out for. It's not just an IP change on the same network, I'll be changing the IP, NETMASK and Default Gateway. Questions: Since I'm not totally AIX literate yet is there a command line command I can use that will do all 3 at once? Should I plan on rebooting the box after this change? Thanks for the help. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (888) 997-9614
Re: Change IP Address
Geoff Gill wrote: I need to change the IP address on my ADSM server this weekend. I want to know if there are any pitfalls I should look out for. It's not just an IP change on the same network, I'll be changing the IP, NETMASK and Default Gateway. Your clients need to know how to contact the server at the new address. You may already have that under control, but since you didn't mention it, I'll assume it slipped your mind. Do your clients' option files contain A. TCPSERVERADDRESS xxx.xxx.xxx.xxx, OR B. TCPSERVERADDRESS something.or.other.com ? - If A, then you need to update every client's option file and restart their schedulers - If B, then you need to make sure the DNS is changed, and that the changes will propagate to the clients within a reasonable time Contact your local DNS guru for more info. - If a mixture of A and B, then both apply, and also you may want to tidy up a little All of the above applies regardless of whether you're running in prompted mode or polling mode. (In prompted mode the A clients may or may not keep working after the chance, but they would fail the next time they were restarted.) I'll leave the other questions to those who actually know AIX. Questions: Since I'm not totally AIX literate yet is there a command line command I can use that will do all 3 at once? Should I plan on rebooting the box after this change?
Re: Change IP Address
Gill - I've done this (albeit not on a TSM server), and, although there might be a command you could enter at the command line to make these changes, you can also easily do this using smit. If you enter 'smit tcpip', then select 'Minimum Configuration Startup', then select your network interface from the list, you'll be able to change the host's IP address, network mask, default gateway address - even your name server's IP address. And, if you change 'Start Now' to 'Yes', I don't think you'll need to IPL the box. A couple of caveats, though (from experience) - after you make the changes in smit, check your /etc/hosts /etc/resolv.conf files. smit seems to not clean up the old entries in these files and instead just adds the new entries. You'll want to remove the reference in /etc/hosts to the host's old IP address, and, if you changed name servers, remove the reference to the old name server in /etc/resolv.conf. Not doing this can cause you grief (in my case, NIS freaked out). I hope this helps! Good luck. Tom Tracy Sr. Database Administrator ( AIX Systems Administrator TSM Administrator.) NTRS, LLC [EMAIL PROTECTED] From: Gill, Geoffrey L. [EMAIL PROTECTED] on 07/02/2001 06:22 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: (bcc: Tom Tracy/ATL/NTRS) Subject: Change IP Address For the AIX crowd out there, I need to change the IP address on my ADSM server this weekend. I want to know if there are any pitfalls I should look out for. It's not just an IP change on the same network, I'll be changing the IP, NETMASK and Default Gateway. Questions: Since I'm not totally AIX literate yet is there a command line command I can use that will do all 3 at once? Should I plan on rebooting the box after this change? Thanks for the help. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (888) 997-9614
Re: Change IP Address
Your clients need to know how to contact the server at the new address. You may already have that under control, but since you didn't mention it, I'll assume it slipped your mind. Lesley, Thanks for the heads up on those other changes. Yes I did take all into consideration. I've forced everyone to use the dns name and made sure they restart their scheduler, been working on that one for a couple of weeks. This way if the IP changes again I won't have this problem. Then again I could be forced to change the name in the future so what the hell.. Actually about 1/4 of the servers are using IP so the change won't be too hard. Thanks again, Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (888) 997-9614
Re: Change IP Address
Then again I could be forced to change the name in the future so what the hell.. If you do have to change the server name, perhaps you could use a CNAME, also known as a DNS alias. For instance my test server is called nzwnstsm10002.ems.itf.nz.eds.com (how's that for a mouthful!) there is an alias called tsm set up in the zone where the clients live so that the client option file has tcpserveraddress tsm. And in a production zone, the tsm alias points to the appropriate production server. This is Good Stuff because it means I can have the same option file everywhere, which makes it really easy to roll out more clients. It's also in keeping with traditional practice of having www pointing at web servers, ftp pointing at ftp servers and so forth. Anyway, good luck for the change. -- Lesley Walker Unix Engineering, EDS New Zealand [EMAIL PROTECTED] I feel that there is a world market for as many as five computers Thomas Watson, IBM corp. - 1943
Change IP Address
For the AIX crowd out there, I need to change the IP address on my ADSM server this weekend. I want to know if there are any pitfalls I should look out for. It's not just an IP change on the same network, I'll be changing the IP, NETMASK and Default Gateway. Questions: Since I'm not totally AIX literate yet is there a command line command I can use that will do all 3 at once? Should I plan on rebooting the box after this change? Thanks for the help. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (888) 997-9614
Re: client and server IP address in different schedule mode
Philip, When you set the client to Prompted mode you have to put in a line TCPCLIENTADDRESS xx.xx.xx.xx in the Options file on the client. If the schedule mode is set to prompted thru' option set then we don't have to do anything. If not then add another line SCHEDMODE PROMPTED in the options file on the client. Let me know what happens. Rajesh Oak -- On Wed, 30 May 2001 11:48:02 Phillip Guan wrote: Hi all, I would like to know whether there is difference between schedule polling and prompt mode in terms of server and client IP address. The scenario is: We changed the schedule mode to be prompt but the server cannot contact the client; but the client can contact the server. We found the server try to contact client with a IP address which is not that client's. But it worked before, I guess it was set to polling mode. If client schedule set to polling mode, will it contact server with one IP address (if there are multiple IP addresses on this client) and server ALWAYS use it as the client IP address? Will it overwrite the IP which is known on server when the client contact server at the first time? Thanks in advance for your help. Regards, Phillip Guan Get 250 color business cards for FREE! http://businesscards.lycos.com/vp/fastpath/
Re: client and server IP address in different schedule mode
I have found it will contact the last IP address that contacted it from that particular node. If a test system contacts the server as the nodename unixadm1 just before the scheduled back, it will go to this client to start the backup. Look in the actlog for the nodename and make sure all contacts are from the same IP address. Jeff Bach Home Office Open Systems Engineering Wal-Mart Stores, Inc. WAL-MART CONFIDENTIAL -Original Message- From: Phillip Guan [SMTP:[EMAIL PROTECTED]] Sent: Wednesday, May 30, 2001 1:48 PM To: [EMAIL PROTECTED] Subject:client and server IP address in different schedule mode Hi all, I would like to know whether there is difference between schedule polling and prompt mode in terms of server and client IP address. The scenario is: We changed the schedule mode to be prompt but the server cannot contact the client; but the client can contact the server. We found the server try to contact client with a IP address which is not that client's. But it worked before, I guess it was set to polling mode. If client schedule set to polling mode, will it contact server with one IP address (if there are multiple IP addresses on this client) and server ALWAYS use it as the client IP address? Will it overwrite the IP which is known on server when the client contact server at the first time? Thanks in advance for your help. Regards, Phillip Guan ** This email and any files transmitted with it are confidential and intended solely for the individual or entity to whom they are addressed. If you have received this email in error destroy it immediately. **
Re: General *SM database/ IP address question
Hi Andy, David, This info is kept in the summary table on Tsm3.7 servers. Here is an example of of a select * from summary query: (Note the address field). START_TIME: 2000-11-20 19:05:55.00 END_TIME: 2000-11-20 19:35:38.00 ACTIVITY: BACKUP NUMBER: 274 ENTITY: LEGALJHB COMMMETH: Tcp/Ip ADDRESS: 10.0.8.34:2177 SCHEDULE_NAME: EXAMINED: 2977 AFFECTED: 2977 FAILED: 0 BYTES: 638352864 IDLE: 99 MEDIAW: 0 PROCESSES: 1 SUCCESSFUL: YES Cheers Christo Actually this info isn't in the NODES table, either. The TSM server stores the IP addresses for nodes using the PROMPTED scheduling mode only, so the server knows which address to prompt when it is time to run scheduled events. However, the table in which this data resides has not been externalized, so it can not be accessed by any QUERY or SELECT statement. Regards, Andy Andy Raibeck IBM/Tivoli Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." I am sory to correct you, but there is a field in the nodes table that stores the hex IP address of the client. Keith Davey On Mon, 18 Dec 2000, Williams, Tim wrote: I don't think that it really 'stores' that information, per se. IT, is however logged in the activity log q actlog.search=etc (help q actlog) hope this helps... David Longo [EMAIL PROTECTED] 12/18/2000 02:24 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED]@SMTP@Exchange To: [EMAIL PROTECTED]@SMTP@Exchange cc: Subject:General *SM database/ IP address question When you register a node name and the node first contacts the *SM Server, the server stores the IP address of the client. Where is this IP address stored on the server? David B. Longo Systems Administrator Health First, Inc. I/T 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED]
Re: General *SM database/ IP address question
Hi Christo,
Thank you for pointing this out. I stand corrected. :-)
Please note, though, that the information is not kept permanently, and will
expire after the number of days specified by the Activity Summary Retention
Period (via SET SUMMARYRETENTION). So it may not be complete.
Best regards,
Andy
Andy Raibeck
IBM/Tivoli
Tivoli Storage Manager Client Development
e-mail: [EMAIL PROTECTED]
"The only dumb question is the one that goes unasked."
Christo Heuër [EMAIL PROTECTED]@VM.MARIST.EDU on 12/19/2000 02:31:40
Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED]
Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: General *SM database/ IP address question
Hi Andy, David,
This info is kept in the summary table on Tsm3.7 servers. Here is an
example
of of a select * from summary query: (Note the address field).
START_TIME: 2000-11-20 19:05:55.00
END_TIME: 2000-11-20 19:35:38.00
ACTIVITY: BACKUP
NUMBER: 274
ENTITY: LEGALJHB
COMMMETH: Tcp/Ip
ADDRESS: 10.0.8.34:2177
SCHEDULE_NAME:
EXAMINED: 2977
AFFECTED: 2977
FAILED: 0
BYTES: 638352864
IDLE: 99
MEDIAW: 0
PROCESSES: 1
SUCCESSFUL: YES
Cheers
Christo
Actually this info isn't in the NODES table, either. The TSM server
stores
the IP addresses for nodes using the PROMPTED scheduling mode only, so
the
server knows which address to prompt when it is time to run scheduled
events. However, the table in which this data resides has not been
externalized, so it can not be accessed by any QUERY or SELECT statement.
Regards,
Andy
Andy Raibeck
IBM/Tivoli
Tivoli Storage Manager Client Development
e-mail: [EMAIL PROTECTED]
"The only dumb question is the one that goes unasked."
I am sory to correct you, but there is a field in the nodes table that
stores the hex IP address of the client.
Keith Davey
On Mon, 18 Dec 2000, Williams, Tim wrote:
I don't think that it really 'stores' that information, per se.
IT, is however logged in the activity log
q actlog.search=etc (help q actlog)
hope this helps...
David Longo [EMAIL PROTECTED]
12/18/2000 02:24 PM
Please respond to "ADSM: Dist Stor Manager"
[EMAIL PROTECTED]@SMTP@Exchange
To: [EMAIL PROTECTED]@SMTP@Exchange
cc:
Subject:General *SM database/ IP address question
When you register a node name and the node first contacts the
*SM
Server, the server stores the IP address of the client. Where is this
IP
address stored on the server?
David B. Longo
Systems Administrator
Health First, Inc. I/T
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH 321.434.5536
Pager 321.634.8230
Fax:321.434.5525
[EMAIL PROTECTED]
Re: General *SM database/ IP address question
TSM started storing this information in the adsm.nodes table in version 3.7.
This information was not available via the adsm.nodes table in 3.1.
Alex Paschal
Storage Administrator
Freightliner, LLC
(503) 745-6850 phone/vmail
-Original Message-
From: Andy Raibeck [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 19, 2000 6:23 AM
To: [EMAIL PROTECTED]
Subject: Re: General *SM database/ IP address question
Hi Christo,
Thank you for pointing this out. I stand corrected. :-)
Please note, though, that the information is not kept permanently, and will
expire after the number of days specified by the Activity Summary Retention
Period (via SET SUMMARYRETENTION). So it may not be complete.
Best regards,
Andy
Andy Raibeck
IBM/Tivoli
Tivoli Storage Manager Client Development
e-mail: [EMAIL PROTECTED]
"The only dumb question is the one that goes unasked."
Christo Heuër [EMAIL PROTECTED]@VM.MARIST.EDU on 12/19/2000 02:31:40
Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED]
Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: General *SM database/ IP address question
Hi Andy, David,
This info is kept in the summary table on Tsm3.7 servers. Here is an
example
of of a select * from summary query: (Note the address field).
START_TIME: 2000-11-20 19:05:55.00
END_TIME: 2000-11-20 19:35:38.00
ACTIVITY: BACKUP
NUMBER: 274
ENTITY: LEGALJHB
COMMMETH: Tcp/Ip
ADDRESS: 10.0.8.34:2177
SCHEDULE_NAME:
EXAMINED: 2977
AFFECTED: 2977
FAILED: 0
BYTES: 638352864
IDLE: 99
MEDIAW: 0
PROCESSES: 1
SUCCESSFUL: YES
Cheers
Christo
Actually this info isn't in the NODES table, either. The TSM server
stores
the IP addresses for nodes using the PROMPTED scheduling mode only, so
the
server knows which address to prompt when it is time to run scheduled
events. However, the table in which this data resides has not been
externalized, so it can not be accessed by any QUERY or SELECT statement.
Regards,
Andy
Andy Raibeck
IBM/Tivoli
Tivoli Storage Manager Client Development
e-mail: [EMAIL PROTECTED]
"The only dumb question is the one that goes unasked."
I am sory to correct you, but there is a field in the nodes table that
stores the hex IP address of the client.
Keith Davey
On Mon, 18 Dec 2000, Williams, Tim wrote:
I don't think that it really 'stores' that information, per se.
IT, is however logged in the activity log
q actlog.search=etc (help q actlog)
hope this helps...
David Longo [EMAIL PROTECTED]
12/18/2000 02:24 PM
Please respond to "ADSM: Dist Stor Manager"
[EMAIL PROTECTED]@SMTP@Exchange
To: [EMAIL PROTECTED]@SMTP@Exchange
cc:
Subject:General *SM database/ IP address question
When you register a node name and the node first contacts the
*SM
Server, the server stores the IP address of the client. Where is this
IP
address stored on the server?
David B. Longo
Systems Administrator
Health First, Inc. I/T
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH 321.434.5536
Pager 321.634.8230
Fax:321.434.5525
[EMAIL PROTECTED]
Re: General *SM database/ IP address question
The IP address of the client isn't stored on the server. Well, not really. In the case of Server Prompted scheduling, the IP address is cached, but only so the server can talk to the client at schedule time. Except for that, the server never contacts the client first. The client always initiates the communication. Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs CO 80949-1313 (719) 531-5926 Fax: (240) 539-7175 Email: [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of David Longo Sent: Monday, December 18, 2000 1:24 PM To: [EMAIL PROTECTED] Subject: General *SM database/ IP address question When you register a node name and the node first contacts the *SM Server, the server stores the IP address of the client. Where is this IP address stored on the server? David B. Longo Systems Administrator Health First, Inc. I/T 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED] [EMAIL PROTECTED] 12/18/00 10:44AM Hi All, I am upgrading HP-UX11.0 ADSM client from v3.1 to v3.7.2 connectAgent v2.1.7 to TDP Oracle v2.1.10. (AIX ADSM Server v3.1.2.57) After upgrade, dsmc can be invoked and backup/restore is working, however the following message is displayed in dsmerror.log once dsmc is invoked. 12/18/00 23:19:00 shl_load() of /opt/tivoli/tsm/client/ba/bin/plugins/libPiIMG.sl failed, errno: 215 IBM support suggests the uninstall of old ADSM client is not clean, so I swremove the 3.7.2 client TDP Oracle; also manually remove the /usr/adsm /usr/adsmagent old directories and swinstall TSM 3.7.2 client and TDP Oracle again. But there is still the same error message in dsmerror.log when invoking dsmc. Anyone encounters this before? Thanks in advance. Regards, Eric Tang
General *SM database/ IP address question
When you register a node name and the node first contacts the *SM Server, the server stores the IP address of the client. Where is this IP address stored on the server? David B. Longo Systems Administrator Health First, Inc. I/T 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED] [EMAIL PROTECTED] 12/18/00 10:44AM Hi All, I am upgrading HP-UX11.0 ADSM client from v3.1 to v3.7.2 connectAgent v2.1.7 to TDP Oracle v2.1.10. (AIX ADSM Server v3.1.2.57) After upgrade, dsmc can be invoked and backup/restore is working, however the following message is displayed in dsmerror.log once dsmc is invoked. 12/18/00 23:19:00 shl_load() of /opt/tivoli/tsm/client/ba/bin/plugins/libPiIMG.sl failed, errno: 215 IBM support suggests the uninstall of old ADSM client is not clean, so I swremove the 3.7.2 client TDP Oracle; also manually remove the /usr/adsm /usr/adsmagent old directories and swinstall TSM 3.7.2 client and TDP Oracle again. But there is still the same error message in dsmerror.log when invoking dsmc. Anyone encounters this before? Thanks in advance. Regards, Eric Tang
Re: General *SM database/ IP address question
I don't think that it really 'stores' that information, per se. IT, is however logged in the activity log q actlog.search=etc (help q actlog) hope this helps... David Longo [EMAIL PROTECTED] 12/18/2000 02:24 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED]@SMTP@Exchange To: [EMAIL PROTECTED]@SMTP@Exchange cc: Subject:General *SM database/ IP address question When you register a node name and the node first contacts the *SM Server, the server stores the IP address of the client. Where is this IP address stored on the server? David B. Longo Systems Administrator Health First, Inc. I/T 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED] [EMAIL PROTECTED] 12/18/00 10:44AM Hi All, I am upgrading HP-UX11.0 ADSM client from v3.1 to v3.7.2 connectAgent v2.1.7 to TDP Oracle v2.1.10. (AIX ADSM Server v3.1.2.57) After upgrade, dsmc can be invoked and backup/restore is working, however the following message is displayed in dsmerror.log once dsmc is invoked. 12/18/00 23:19:00 shl_load() of /opt/tivoli/tsm/client/ba/bin/plugins/libPiIMG.sl failed, errno: 215 IBM support suggests the uninstall of old ADSM client is not clean, so I swremove the 3.7.2 client TDP Oracle; also manually remove the /usr/adsm /usr/adsmagent old directories and swinstall TSM 3.7.2 client and TDP Oracle again. But there is still the same error message in dsmerror.log when invoking dsmc. Anyone encounters this before? Thanks in advance. Regards, Eric Tang
Re: General *SM database/ IP address question
It is stored in the Nodes table in the TSM server Database On Mon, 18 Dec 2000, David Longo wrote: When you register a node name and the node first contacts the *SM Server, the server stores the IP address of the client. Where is this IP address stored on the server? David B. Longo Systems Administrator Health First, Inc. I/T 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED] [EMAIL PROTECTED] 12/18/00 10:44AM Hi All, I am upgrading HP-UX11.0 ADSM client from v3.1 to v3.7.2 connectAgent v2.1.7 to TDP Oracle v2.1.10. (AIX ADSM Server v3.1.2.57) After upgrade, dsmc can be invoked and backup/restore is working, however the following message is displayed in dsmerror.log once dsmc is invoked. 12/18/00 23:19:00 shl_load() of /opt/tivoli/tsm/client/ba/bin/plugins/libPiIMG.sl failed, errno: 215 IBM support suggests the uninstall of old ADSM client is not clean, so I swremove the 3.7.2 client TDP Oracle; also manually remove the /usr/adsm /usr/adsmagent old directories and swinstall TSM 3.7.2 client and TDP Oracle again. But there is still the same error message in dsmerror.log when invoking dsmc. Anyone encounters this before? Thanks in advance. Regards, Eric Tang
Re: General *SM database/ IP address question
I am sory to correct you, but there is a field in the nodes table that stores the hex IP address of the client. Keith Davey On Mon, 18 Dec 2000, Williams, Tim wrote: I don't think that it really 'stores' that information, per se. IT, is however logged in the activity log q actlog.search=etc (help q actlog) hope this helps... David Longo [EMAIL PROTECTED] 12/18/2000 02:24 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED]@SMTP@Exchange To: [EMAIL PROTECTED]@SMTP@Exchange cc: Subject:General *SM database/ IP address question When you register a node name and the node first contacts the *SM Server, the server stores the IP address of the client. Where is this IP address stored on the server? David B. Longo Systems Administrator Health First, Inc. I/T 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED] [EMAIL PROTECTED] 12/18/00 10:44AM Hi All, I am upgrading HP-UX11.0 ADSM client from v3.1 to v3.7.2 connectAgent v2.1.7 to TDP Oracle v2.1.10. (AIX ADSM Server v3.1.2.57) After upgrade, dsmc can be invoked and backup/restore is working, however the following message is displayed in dsmerror.log once dsmc is invoked. 12/18/00 23:19:00 shl_load() of /opt/tivoli/tsm/client/ba/bin/plugins/libPiIMG.sl failed, errno: 215 IBM support suggests the uninstall of old ADSM client is not clean, so I swremove the 3.7.2 client TDP Oracle; also manually remove the /usr/adsm /usr/adsmagent old directories and swinstall TSM 3.7.2 client and TDP Oracle again. But there is still the same error message in dsmerror.log when invoking dsmc. Anyone encounters this before? Thanks in advance. Regards, Eric Tang
General *SM database/ IP address question
Actually this info isn't in the NODES table, either. The TSM server stores the IP addresses for nodes using the PROMPTED scheduling mode only, so the server knows which address to prompt when it is time to run scheduled events. However, the table in which this data resides has not been externalized, so it can not be accessed by any QUERY or SELECT statement. Regards, Andy Andy Raibeck IBM/Tivoli Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." I am sory to correct you, but there is a field in the nodes table that stores the hex IP address of the client. Keith Davey On Mon, 18 Dec 2000, Williams, Tim wrote: I don't think that it really 'stores' that information, per se. IT, is however logged in the activity log q actlog.search=etc (help q actlog) hope this helps... David Longo [EMAIL PROTECTED] 12/18/2000 02:24 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED]@SMTP@Exchange To: [EMAIL PROTECTED]@SMTP@Exchange cc: Subject:General *SM database/ IP address question When you register a node name and the node first contacts the *SM Server, the server stores the IP address of the client. Where is this IP address stored on the server? David B. Longo Systems Administrator Health First, Inc. I/T 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED] [EMAIL PROTECTED] 12/18/00 10:44AM Hi All, I am upgrading HP-UX11.0 ADSM client from v3.1 to v3.7.2 connectAgent v2.1.7 to TDP Oracle v2.1.10. (AIX ADSM Server v3.1.2.57) After upgrade, dsmc can be invoked and backup/restore is working, however the following message is displayed in dsmerror.log once dsmc is invoked. 12/18/00 23:19:00 shl_load() of /opt/tivoli/tsm/client/ba/bin/plugins/libPiIMG.sl failed, errno: 215 IBM support suggests the uninstall of old ADSM client is not clean, so I swremove the 3.7.2 client TDP Oracle; also manually remove the /usr/adsm /usr/adsmagent old directories and swinstall TSM 3.7.2 client and TDP Oracle again. But there is still the same error message in dsmerror.log when invoking dsmc. Anyone encounters this before? Thanks in advance. Regards, Eric Tang
IP Address
Could anyone tell me what command I would use to display an ip address for a client, using only the node name.
Re: IP Address
Which Operating system ? Ramesh -Original Message- From: Diane Geils [mailto:[EMAIL PROTECTED]] Sent: Friday, November 03, 2000 10:33 AM To: [EMAIL PROTECTED] Subject: IP Address Could anyone tell me what command I would use to display an ip address for a client, using only the node name.
Re: IP Address
You could use the ping command and the node name. Once you do the ping it should return with the IP address for that node name. ex. ping mars Bill Wheeler AIX Administrator La-Z-Boy Incorporated [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: Diane Geils [mailto:[EMAIL PROTECTED]] Sent: Friday, November 03, 2000 10:33 AM To: [EMAIL PROTECTED] Subject: IP Address Could anyone tell me what command I would use to display an ip address for a client, using only the node name.
Re: IP Address
Check your activity log... (query actl)... usually when a session is established, the IP address of the node is displayed in the activity log... 11/03/00 11:31:58 ANR0406I Session 958 started for node MIFS00 (NetWare) (Tcp/Ip xxx.xxx.xxx.xxx(1080)). 11/03/00 11:31:59 ANR0403I Session 958 ended for node MIFS00 (NetWare). 11/03/00 11:42:23 ANR0407I Session 959 started for administrator SGG (WebBrowser) (HTTP xxx.xxx.xxx.xxx(1998)). I have placed "xxx" in place where my ip addresses showed (for security reason for my client). Serge Gaudet, CMI Consultant Bill Wheeler Bill.Wheeler@LA-To: [EMAIL PROTECTED] Z-BOY.COM cc: Sent by: "ADSM: Subject: Re: IP Address Dist Stor Manager" [EMAIL PROTECTED] .EDU 03/11/2000 11:03 AM Please respond to "ADSM: Dist Stor Manager" You could use the ping command and the node name. Once you do the ping it should return with the IP address for that node name. ex. ping mars Bill Wheeler AIX Administrator La-Z-Boy Incorporated [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: Diane Geils [mailto:[EMAIL PROTECTED]] Sent: Friday, November 03, 2000 10:33 AM To: [EMAIL PROTECTED] Subject: IP Address Could anyone tell me what command I would use to display an ip address for a client, using only the node name.
Re: IP Address
Hi Diane, There does not need to be any association between an ADSM client's node name and the client IP address. It might help to thing of the node name as the client's ADSM login name. That being said, there is often information in the activity log which connects node name to IP address. Jim -- From: Diane Geils[SMTP:[EMAIL PROTECTED]] Reply To: ADSM: Dist Stor Manager Sent: Friday, November 03, 2000 10:33 AM To: [EMAIL PROTECTED] Subject: IP Address Could anyone tell me what command I would use to display an ip address for a client, using only the node name.
