Us too. We have always forced all clients to use polling sched mode, and
have never had to hassle with IP addresses. DHCP and VLANs came and it
was no problem. Our client node administrators have always been happy
that we have always said that TSM backup is independent of IP address.

We use other methods to detect two+ machines backing up to one nodename,
specifically if the GUID changes repeatedly.

Roger Deschner      University of Illinois at Chicago     rogerd AT uic DOT edu
=============== Klein bottle for rent -- inquire within. ===============


On Fri, 24 May 2013, Karel Bos wrote:

>Hi,
>
>One of the nice things of having all clients in polling sched mode is no need 
>to admin ip stuff, even when the clients ip changes without restarting tsm 
>services (or manual contact the tsm server).
>
>Kind regards,
>Karel
>
>----- Oorspronkelijk bericht -----
>Van: Zoltan Forray <zforray AT VCU DOT EDU>
>Verzonden: donderdag 23 mei 2013 18:13
>Aan: ADSM-L AT VM.MARIST DOT EDU
>Onderwerp: [ADSM-L] Clients using DHCP vs Fixed IP addresses
>
>Up until now, we have always assigned fixed IP addresses to all TSM
>clients/nodes.
>
>Now they want to reconfigure all backup networking to use VLANs and have
>asked the question, "do the clients need to be fixed IP addresses or can
>they be dynamically assigned from a specific DHCP server?"
>
>Is this do-able?  How does it effect scheduling? What configuration changes
>would be needed (SCHEDMODE?  SESSIONINITIATION?)
>
>How do most folks manage backup scheduling and client addressing?
>
>--
>*Zoltan Forray*
>TSM Software & Hardware Administrator
>Virginia Commonwealth University
>UCC/Office of Technology Services
>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
>