ADSM-L

Re: [ADSM-L] Problem logging in to administrator ID with DHCP node

2015-06-03 10:39:30
Subject: Re: [ADSM-L] Problem logging in to administrator ID with DHCP node
From: Andrew Raibeck <storman AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 3 Jun 2015 10:38:02 -0400
Hi Zoltan,

Yes, you  have the right APAR and fix level. That APAR is not platform
specific, it covers all UNIX, Linux, and Windows platforms.

We are working on getting the "paperwork" updated appropriately.

Best regards,

- Andy

____________________________________________________________________________

Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead |
storman AT us.ibm DOT com

IBM Tivoli Storage Manager links:
Product support:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager

Online documentation:
http://www.ibm.com/support/knowledgecenter/SSGSG7/welcome
Product Wiki:
https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storage%20Manager

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2015-06-02
10:20:14:

> From: Zoltan Forray <zforray AT VCU DOT EDU>
> To: ADSM-L AT VM.MARIST DOT EDU
> Date: 2015-06-02 10:22
> Subject: Re: Problem logging in to administrator ID with DHCP node
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> As suspected, upgrading the client to 7.1.2.1 has resolved the problem
with
> administrator login.  So, I am pretty sure it is related to IT08705
> <http://www.ibm.com/support/docview.wss?uid=swg1IT08705> but I can not
> confirm since I can't find the APAR record.  So it seems this problem
> effects Windows as well as AIX clients.
>
> On Tue, Jun 2, 2015 at 8:19 AM, Zoltan Forray <zforray AT vcu DOT edu> wrote:
>
> > BTW, I was looking through the 7.1.2.1 fixlist and found this entry
> > "IT08705 - 7.1.2 WEB CLIENT LOGIN AUTHENTICATION FAILURE POP-UP
MESSAGE,
> > ANS3004E IN DSMERROR.LOG".
> >
> > While it says it is for AIX, it sounds very close to my problem.
> > Unfortunately, someone seems to have pulled the APAR since the link to
the
> > APAR page 404's and Googling for that APAR only sends me back to the
> > fixlist page.
> >
> > Can someone from IBM look into/comment on this?
> >
> > On Tue, Jun 2, 2015 at 8:02 AM, Zoltan Forray <zforray AT vcu DOT edu> 
> > wrote:
> >
> >> Thank you for the suggestion.
> >>
> >> Back a while ago, I asked, here, if there are any issues with using
DHCP
> >> (vs fixed IP addresses) for the clients to backup and was told that
this
> >> was the way pretty much everyone did it.  So far we have not had any
issues
> >> with the backups on any other clients we have converted to DHCP. This
is
> >> the first problem and I think it is related to the client and the web
> >> interface.
> >>
> >> On Tue, Jun 2, 2015 at 12:48 AM, Karel Bos <tsm.wad AT gmail DOT com> 
> >> wrote:
> >>
> >>> Hi,
> >>>
> >>> Compare q no f=d output of the node with the current ip address of
that
> >>> node. Some of the registered ip's of that node might have not been
> >>> updated.
> >>>
> >>> Having dhcp enabled on your backup clients and having them switch ips
> >>> constantly will cause issues for tsm server to tsm client
communications
> >>> even when running in polling mode.
> >>> Op 1 jun. 2015 22:27 schreef "Zoltan Forray" <zforray AT vcu DOT edu>:
> >>>
> >>> > We are migrating our TSM infrastructure to DHCP assignments for the
> >>> client
> >>> > nodes/servers.  Up until no everything seems to have worked OK.
> >>> >
> >>> > Now we moved a bunch of CIFS backups to DHCP and having problems
> >>> logging in
> >>> > to an administrator ID via the WEB client on the box.
> >>> >
> >>> > Every attempt to login produces "invalid password" for the
> >>> administrator,
> >>> > no matter how many times we reset the password. Logging in as this
same
> >>> > admin ID via a different interface work with no problem.  The admin
ID
> >>> has
> >>> > full privileges.
> >>> >
> >>> > The config is this.  The connection from this node server to the
TSM
> >>> server
> >>> > is DHCP / 172 range.  The webport connection to the box is a fixed
> >>> private
> >>> > 192.168 address. The client is 7.1.2.0
> >>> >
> >>> > Any thoughts?
> >>> >
> >>> > --
> >>> > *Zoltan Forray*
> >>> > TSM Software & Hardware Administrator
> >>> > Xymon Monitor Administrator
> >>> > Virginia Commonwealth University
> >>> > UCC/Office of Technology Services
> >>> > www.ucc.vcu.edu
> >>> > zforray AT vcu DOT edu - 804-828-4807
> >>> > Don't be a phishing victim - VCU and other reputable organizations
will
> >>> > never use email to request that you reply with your password,
social
> >>> > security number or confidential personal information. For more
details
> >>> > visit http://infosecurity.vcu.edu/phishing.html
> >>> >
> >>>
> >>
> >>
> >>
> >> --
> >> *Zoltan Forray*
> >> TSM Software & Hardware Administrator
> >> Xymon Monitor Administrator
> >> Virginia Commonwealth University
> >> UCC/Office of Technology Services
> >> www.ucc.vcu.edu
> >> zforray AT vcu DOT edu - 804-828-4807
> >> Don't be a phishing victim - VCU and other reputable organizations
will
> >> never use email to request that you reply with your password, social
> >> security number or confidential personal information. For more details
> >> visit http://infosecurity.vcu.edu/phishing.html
> >>
> >
> >
> >
> > --
> > *Zoltan Forray*
> > TSM Software & Hardware Administrator
> > Xymon Monitor Administrator
> > Virginia Commonwealth University
> > UCC/Office of Technology Services
> > www.ucc.vcu.edu
> > zforray AT vcu DOT edu - 804-828-4807
> > Don't be a phishing victim - VCU and other reputable organizations will
> > never use email to request that you reply with your password, social
> > security number or confidential personal information. For more details
> > visit http://infosecurity.vcu.edu/phishing.html
> >
>
>
>
> --
> *Zoltan Forray*
> TSM Software & Hardware Administrator
> Xymon Monitor Administrator
> Virginia Commonwealth University
> UCC/Office of Technology Services
> www.ucc.vcu.edu
> zforray AT vcu DOT edu - 804-828-4807
> Don't be a phishing victim - VCU and other reputable organizations will
> never use email to request that you reply with your password, social
> security number or confidential personal information. For more details
> visit http://infosecurity.vcu.edu/phishing.html
>