Windows 7 DHCPv6 T1 & T2 behaviour

[Henri Wahl]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi list,

does anybody have Windows 7 clients using statful DHCPv6 on the LAN?
If so, how do they behave regarding T1 and T2 values in your network?

I ask because I configured pretty small values, T1=300 and T2=450 for
a valid lifetime of 86400 and a preferred lifetime of 64800. After the
whole setup running stable for months I decided to raise T1 and T2 to
decrease load on the DHCPv6 server.

I started with T1=3600 and T2=5400, but now I found that clients,
after they reached T1 and asked for RENEW, got the addresses renewd by
the server but instantly seem to forget their renewed address so they
only keep their link-local address. This was no problem with shorter T1.

Is this behaviour known? Any real-life recommendation for T1 and T2?

Best regards
Henri

- -- 
Henri Wahl

IT Department
Leibniz-Institut fuer Festkoerper- u.
Werkstoffforschung Dresden

tel: +49 (3 51) 46 59 - 797
email: h.wahl at ifw-dresden.de
https://www.ifw-dresden.de

Nagios status monitor Nagstamon:
https://nagstamon.ifw-dresden.de

DHCPv6 server dhcpy6d:
https://dhcpy6d.ifw-dresden.de

IFW Dresden e.V., Helmholtzstrasse 20, D-01069 Dresden
VR Dresden Nr. 1369
Vorstand: Prof. Dr. Manfred Hennecke, Dr. h.c. Dipl.-Finw. Rolf Pfrengle
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlR8b80ACgkQnmb3Nh+6CUL8HgCbBLrw6UFvG1G8+riBRgxbQ6Yc
+XkAn29VlCYBaFa5sQGuiD7/7y4XCjJP
=H/P5
-----END PGP SIGNATURE-----