hey guys, we have hit the issue described in Richard Hicks blog here - we have two DA servers in a load balanced cluster using a hardware load balancer. The New-NetRoute command as described in his blog works fine for the first server, eveything is happy and DA functions normally. The second server in the cluster, built with the same base OS, in the same subnet on the next IP address along for external and internal network cards, doesnt work.
The Client IPv6 prefix is published OK but on restarting the server or just the RaMgmtSvc service, the published route is removed. I've tried using PoSH and also the old way with netsh, the route is published fine with both. Restarting the service removes the route, so everytime I load the console it tells me the client prefix isnt published, when it is .... it just doesnt know about it yet as I need to restart the service... and well you get the idea.
Is this a bug? Time to log a call with Microsoft?