Ans1568e Tcpcadaddress

denisl

ADSM.ORG Member
Joined
Sep 12, 2002
Messages
113
Reaction score
0
Points
0
Website
Visit site
Anyone know why this option is needed? I thought is was needed for multi NIC hosts but I'm getting this error on a server with one ip address. Client is zLinux RHEL04.

This is the one option in the dsm.sys that is unique to the node which makes it very difficult to have a common dsm.sys file....

Any info on this option (other then what's in the readme) would be greatly appreciated.. thx.

Code:
04/20/2007 11:37:59 ANS1568E The CAD attempted to register it's tcpport and tcpip address without using the TCPCADADDRESS option.
04/20/2007 11:37:59 ANS1570E Registering this instance of the Cad with the server failed. Cad process continues.
[root@rhel026 bin]# ifconfig -a
hsi0      Link encap:Ethernet  HWaddr 00:00:00:00:00:00  
          inet addr:146.125.16.162  Bcast:146.125.16.191  Mask:255.255.255.192
          inet6 addr: fe80::ff:f100:0/64 Scope:Link
          UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:238261 errors:0 dropped:0 overruns:0 frame:0
          TX packets:209351 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:117573872 (112.1 MiB)  TX bytes:141988864 (135.4 MiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:395 errors:0 dropped:0 overruns:0 frame:0
          TX packets:395 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:46484 (45.3 KiB)  TX bytes:46484 (45.3 KiB)

sit0      Link encap:IPv6-in-IPv4  
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
 
Here is my dsm.sys on a SUSE 9.3 server:

SErvername TSM-SERVER
COMMMethod TCPip
TCPPort 1500
TCPServeraddress 192.168.2.245
NOdename linux00
Exclude "/opt/tivoli/tsm/log/dsmsched.log"
COMMRESTARTDURATION 15
ERRORLOGRETENTION 5 D
MAXCMDRETRIES 6
RETRYPERIOD 10
SCHEDLOGNAME "/opt/tivoli/tsm/log/dsmsched.log"
ERRORLOGNAME "/opt/tivoli/tsm/log/dsmerror.log"
SCHEDLOGRETENTION 5 D
SCHEDMODE PROMPTED
PASSWORDACCESS GENERATE

As you can see, I don't have TCPCLIENTADDRESS entered BUT TCPSERVERADDRESS is. Note that nodename is defined so my TSM server can see it through piped services.

Also, look if the TSM server can see the node from an IP viewpoint. The subnet must be visible from each other.

By default, dsmcad uses the node TCP/IP address via port 1581.

Try entering the nodename in dsm.sys and see if the error disappears. If not try adding an entry: TCPCLIENTADDRESS 146.125.16.162 in your dsm.sys. Don't forget to restart the TSM scheduler to affect the changes.
 
I wasn't even aware there was an option to attach an address to the CAD service, TCPCADADDRESS.

Please let us know if Moons-buddys suggestion fixed the issue.
 
Using TCPCADADDRESS fixes it but I hate the fact that I have to have a customized dsm.sys file for each server. We have well over 1000 nodes and standardization is critical to management.
 
The tpccadaddress option specifies a TCP/IP address for dsmcad. Normally, this option is not needed. Use this option only if your client node has more than one TCP/IP address, or if TCP/IP is not the default communication method

If you only have one NIC and it uses 1 IP address (assuming you are using TCP/IP for the comm method here) - then there is another reason you would need to use this - and you need to figure it out.
It would be a waste to add this to all nodes just to find out something else could fix it.

If this was working before without the tpccadaddress option, I suggest you check with your network team to be sure there is nothing weird going on...
 
Last edited:
Back
Top