Don't worry. 192.168.*.* addresses are typically assigned locally by
something like DHCP. They are not exposed outside your local network. In
fact they can't be, because each of us has our own set of 192.168
addresses. Most home routers use this address range. This is quite
normal. Read
Hi to all
Using TSM for VE 7.1.1 to back up our VMware environment , using for now two
virtual proxy machine, datamover node (vmprox1 vmproxy2). I configure the
schedulers thru TSM for VMware UI gui.
Some VM’s are scheduled thru vmproxy1 and some VM’s are scheduled thru vmproxy2
. I tried to
Check if your actlog has any ANR1639I messages. This is thrown when the TSM
server detects an IP address change on a node.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Thomas
Denier
Sent: Wednesday, November 05, 2014 11:45 AM
To:
Hello All:
We've been using TSM 7.1.1 ever since it was released, and we are seeing
some strange behavior.
The name of the VMs are picked up properly, but the drives have this
strange designation in the form of: \\?\vstor2\mntapi20-shared-
Worse, each of the VM's drives show up as
As far as I know is the content of the address field reported by the
client node and not resolved by the tsm server.
You are sure non of your clients is behind a NAT or uses these addresses
locally ?
On 11/06/2014 01:08 PM, Rhodes, Richard L. wrote:
Check if your actlog has any ANR1639I
It's easy to find this out from the admin cli. Just do a q sched * *
nodes=datamover That will show all schedules associated with a given
node.
ie:
tsm: TSMSKq sched * * nodes=stnsvpmover02
Domain * Schedule NameAction Start Date/Time
Duration Period
Hi,
you can look up in the SUMMARY_EXTENDED table which VMs are backed up by
the specific node with a specific schedule:
tsm: ZEUSSERVselect SUB_ENTITY from summary_extended where
ENTITY='MY_DATAMOVER_NODE' and SUB_ENTITY'' and
SCHEDULE_NAME='SCHEDULENAME'
SUB_ENTITY: MZ_VM_1
SUB_ENTITY:
A traceroute from the TSM server shows a typical route to one of my employer's
core routers. There is no output after that. In particular, there are not lines
with asterisks indicating timeouts.
I don't have logon access to the two clients, and I don't see how running
tracerte commands on the
The two clients are connecting to the TSM server regularly with distinct
addresses in the appropriate subnet. Even if misconfiguration of the IP stacks
on the clients produced 192.168 addresses sometime in the past, TSM should have
replaced the 192.168 addresses in the Nodes table with the
The /etc/hosts file defines, 'localhost', names for the addresses of the
various network interfaces on the TSM server, and some special IP Version 6
addresses (which should be irrelevant, since my employer is still using only IP
Version 4).
Thomas Denier
Thomas Jefferson University Hospital
A tcpclientaddress option with a 192.168 address would cause the TSM central
scheduler to attempt to open a connection to that 192.168 address when the time
came to run a scheduled backup. When the central scheduler tries to request a
backup of either of the clients involved in the problem TSM
A laptop at someone's home would only be able to connect to the TSM server
using a VPN tunnel. I have a home network that uses 192.168 addresses, and
recently had occasion to use VPN to open an administrator session to the TSM
server. I checked the origin address the TSM server reported for
I found two ANR1639I messages within the last five days. Neither involved a
node with a 192.168 address in the Nodes table. One showed a change of GUID,
and the other showed an IP address change, with both old and new addresses in
legitimate on-campus subnets.
Thomas Denier
Thomas Jefferson
We have recently changed from PVU based licensing to the Unified/Terabyte based
licensing model on TSM.
What do I need to do on the TSM system itself to update the licensing? Is there
a file that needs to be updated or a command that needs to be run?
When I run q lic it is still showing the
Hi Paul,
There is nothing you need to change with regard the TSM Server to reflect
the change in licensing. What you will need to do periodically (say
monthly, quarterly) will be to run the appropriate IBM provided TB macro
which will report your TB usage so you can ensure that the TSM Server is
15 matches
Mail list logo
