TMS Persistent Settings

[Darrel_h1]

We are in the process of dual-purposing one C40 on a multi-classification system. When changing from one class to the other, the system is wiping the IPs, such as gatekeeper and SNMP address, and rebooting. Upon reconnection, we were intending for TMS to discover the C40 and push the persistent settings. This is not happening. When the codec comes back online, it is pulling it's reserved IP from the network, TMS is acknowledging the device is back online, but it's not forcing the settings. I have verified that the "Apply on System Boot" option is on under the Configuration Template settings. Also, when I manually enforce the settings the codec accepts them with no issues. Any ideas why they're not being pushed upon reboot? Thanks for your help. Oh, and we're using TMS Version 14.1.1.

[Patrick Sparkman]

Did you apply the configuration template to the C40 to be persistent.

You can do this by:

1. Systems Navigator > C40 > Settings > Persistent Settings > Persistent Template
   • Choose the template  you want applied.
2. Systems Navigator > Configuration Templates > template > Set on Systems
   • Select the Persistent tab on the right before bringing over the C40 from the left.

[Darrel_h1]

Thanks for the reply Patrick.

I guess I should have mentioned that before. Yes, I did add it to the persistent settings tab. This is verified by checking the Persistent Settings menu under the device settings tab.

[Patrick Sparkman]

Because you mention SNMP, it sounds as you might be clearing be the TMS feedback address, which would mean that TMS won't register a boot signal from the C40 and apply the template.  Check the TMS logs for the C40, do you see a "Boot" event under the feedback log.

What all settings are you clearing before you do the reboot?

Have you tried to simply reboot the C40 without clearing anything, that way TMS will simply update the setting that's already there?

[Darrel_h1]

I do see the "Boot" Event Type register in the C40 TMS log upon restart, which is what initially confused me about this issue. TMS is seeing the device boot, the persistent setting is set to occur on boot, but then it does nothing.

The only settings we are clearing are the IPs associated with IPv4, Gatekeeper Address, SNMP Host 1 Address and the External Manager Address. Because of the classification concern, we have to wipe all of the IPs.

Just restarting the C40 does retain all of it's settings, so I'm fairly certain it's not an issue with the codec. Unfortunately, we can't leave it like this though. As I stated before, we have to wipe the IPs.

[Patrick Sparkman]

I just restarted a C40 with a persistent template and TMS registered a boot event and updated the C40 per the template, this can be seen in the Feedback log and the Configuration Template Activity Status page in TMS, the only thing changed was the H323 Gatekeeper Address.

I then restarted the C40 clearing similar settings as you, and TMS did not register a boot event, this is because the External Manager Address was cleared, hence the codec doesn't know to send feedback events such to TMS.

If you are seeing a boot event in the feedback log, do you see anything for the conference template activity status?

Another option instead of using TMS configuration templates, is to use the persistent settings feature built into the codecs themselves.  You configure the codec with default settings that you want to use whenever it is restarted, and then turn on the persistent settings feature, any changes then made will be reset after a reboot.  You can read more about it in the C40 Admin Guide on pg 49.

[Darrel_h1]

Thanks for all of your insight Patrick, I definitely tried a few of the things mentioned however, what ultimately fixed the issue was utilizing DHCP Option 242. TMS is now pushing the configurations to the codec with no issues. Again, thanks for your help.