Hi guys,
For the record: the issue below was caused by a misconfigured API client. On
one cluster node it was using the hosts IP address as tcpcerveraddress, on the
other one it used tcpserveraddress localhost. After setting them both to
localhost the database backup was working again on both nodes.
Kind regards,
Eric van Loon
Air France/KLM Storage Engineering
From: Loon, Eric van (ITOPT3) - KLM
Sent: donderdag 25 januari 2018 13:58
To: ADSM-L <ADSM-L AT VM.MARIST DOT EDU>
Subject: Backup db chalenges with 7.1.8
Hi guys,
I'm facing a new challenge because of the security enhancement in 7.1.8. In the
past I installed 7.1.7 servers on a cluster configuration, which was working
without any issues. With 7.1.8 TSM starts checking the GUID of the
$$_TSMDBMGR_$$ node used and this changes as soon as the server switches to the
other cluster node. This causes the backup to fail:
ANR0406I Session 49 started for node $$_TSMDBMGR_$$ (DB2/Linux) (SSL
10.70.11.118(58814)).
ANR2987W Session ended because of machine GUID or local host IP address
mismatch.
ANR3259W Session 49 for node $$_TSMDBMGR_$$ (DB2/Linux) refused -
$$_TSMDBMGR_$$ node from an untrusted system is not allowed.
ANR0403I Session 49 ended for node $$_TSMDBMGR_$$ (DB2/Linux).
I found the circumvention to specify the parameter DBMTRUSTEDGUIDIGNORE YES in
the dsmserv.opt, but that looks more like a fix than a solution...
How should one solve this issue properly?
Thanks for any help in advance!
Kind regards,
Eric van Loon
Air France/KLM Storage Engineering
********************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain confidential and
privileged material intended for the addressee only. If you are not the
addressee, you are notified that no part of the e-mail or any attachment may be
disclosed, copied or distributed, and that any other action related to this
e-mail or attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately by return
e-mail, and delete this message.
Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
employees shall not be liable for the incorrect or incomplete transmission of
this e-mail or any attachments, nor responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
Airlines) is registered in Amstelveen, The Netherlands, with registered number
33014286
********************************************************
|
