- This topic has 4 replies, 3 voices, and was last updated 2 years, 11 months ago by
.
-
Posts
-
Hi all,
we’ve got 100+ 5070s spread over different locations, which are all connected to the datacenter via s2s vpn. As we currently rebuild our core infrastructure, we’ve set up a brand new WMS Server, recreated all the policies/configs (no Pro version at hand) and added some new TCs.
Now we’re wondering, how to move all the existing TCs from the old WMS (local hostname) to the new one (completely different network, fqdn via wan only). Is there a way to add parameters to the old WMS’ configs, that tell the TCs to connect to the new one, next time they start up?
Tried to find some info in this forum, but wasn’t lucky yet.
Would be great if anyone could help us out.
Cheers
Jay
It depends on the ThinOS version.
When you are using ThinOS 8 you can use the Advanced section of the policy and add
CCMEnable=Yes CCMServer=newserver GroupPrefix=defa GroupKey=newgroup AdvancedConfig=yes Override=yes CAValidation=no Discover=no
If you are using ThinOS 9 then you can use the policy at Services-WMS Settings.CG
If you’re using WES, let us know, I’m about to go through a similar exercise.
Thanks for your quick reply!
We are using 8.6. So we tried adding your parameters to the following section (roughly translated from german): “advanced device configuration -> advanced” (doing this one statement per line). Turned out this didn’t work, as the TC says “statement XYZ not supported”.
So next we tried creating an move_all_tc_to_new_wms.ini file, adding your parameters, uploading it to WMS and pointing to it in: “advanced device configuration -> ini group settings”.
This resulted in TC saying “wms agent error: invalid group token”, being followed by “wms server not found” and “statement XYZ not supported”. URL and key are correct (if “key” equals “token” and is the part after “defa-“).I guess we`re still doing something wrong. Additionally the TC we tried this procedure with is now unregistered from the old WMS and we can’t access the full admin menu to to a full reset. Do we now have to use a merlin image to do a full reset?
J
Use the Advanced Section and put everything in one single line.
If you want to split it, then let all lines end with ” \”, except of the last one.
Example:CCMEnable=Yes CCMServer=newserver \
GroupPrefix=defa GroupKey=newgroup \
AdvancedConfig=yes Override=yes CAValidation=no \
Discover=noCG
- You must be logged in to reply to this topic.