TMS "Replace System"

[Anthony Thomson]

Why won't TMS allow you to replace a system with one that has the same IP address?

I find this frequently in environments where addresses are statically assigned to endpoints.  A unit dies, it gets replaced with a unit that has the same IP address.  TMS won't let you do that.  So you end up re-adding the endpoint as a new one, and having to configure it from scratch, and losing the call history of the first one.  You lose the history, and the ease-of-replacement functionality of TMS porting over the settings to the new unit.

This, despite the units being set explicitly to be tracked by MAC address, rather than IP address.  Does it behave differently if set to track by Hostname?

Thanks.

[Steve Kapinos]

Patrick Sparkman wrote:
In my experience the provisioning request happens as soon as you fill in the address details, it starts trying to send feedback, no reboot is required.  A reboot might be required for the IP, just depends, I've seen sometimes that a codec might not take and use the new IP right away.

Its why I italicized 'change' - you must change the value and then it will attempt a register request immediately.  Simply issuing the command again won't trigger it. 

Booting also works because simply... the register request is always done as part of the bootup

TMS has several passive discovery methods... but externalmanager register is the simpliest and most consistent across the various TMS releases.

[Patrick Sparkman]

Steve Kapinos wrote:
Its why I italicized 'change' - you must change the value and then it will attempt a register request immediately.  Simply issuing the command again won't trigger it. 

Sorry, didn't catch the "change" part of the message.  I was just implying that in my experience with setting up new systems out of the box, the provisioning information is blank so there wouldn't be a change, just new data, and when you input the TMS server into the endpoint, it starts contacting the server right then.

Steve Kapinos wrote:
 
TMS has several passive discovery methods... but externalmanager register is the simpliest and most consistent across the various TMS releases.

This is what we do when we want to add new systems into TMS most of the time, all of our endpoints are setup with static addresses, so we have to log into the endpoint anyway to setup the IP, so what's a few extra steps to do setup provisioning to TMS while were at it.