Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
Adding systems
Cisco TMS Administration Guide
Page 14 of 39
Configuring the DHCP server
If you are using a Windows 2000/2003 DHCP server, add the following settings in the
DHCP Manager
DHCP Manager
You can create the 242 option by redefining an existing global option. To do this, highlight the global
option in the “Unused” list and click Add in the DHCP manager. Once you have defined a vendor-
specific option, you can select it for use by the vendor class by moving the option to the “Configured”
list, and defining its value which should be the IP or the DNS name of the Cisco TMS server.
option in the “Unused” list and click Add in the DHCP manager. Once you have defined a vendor-
specific option, you can select it for use by the vendor class by moving the option to the “Configured”
list, and defining its value which should be the IP or the DNS name of the Cisco TMS server.
If you are using IS C’ s DHCP-server, put the following statements in dhcpd.conf.
1. Define option 242:
option loc al-tms-ip code 242 = ip-address;
2. Define the value in the subnet of pool section:
option loc al-tms-ip < IP address>;
If the systems are not using DHCP, they need to be able to respond to the SNMP broadcast
messages that Cisco TMS will send out on set intervals. This interval is configurable in
Admini strative Tool s > Configuration > Network Settings > TMS Services >SNMP Broadca st
Interval (in minutes).
messages that Cisco TMS will send out on set intervals. This interval is configurable in
Admini strative Tool s > Configuration > Network Settings > TMS Services >SNMP Broadca st
Interval (in minutes).
Note: The Cisco 150 MXP with L1. 1 and L1.2 is configured to request the DHCP for option 173. It is
therefore advised to either upgrade the endpoints to newer software, or to configure both the option
242 and 173 on the DHCP server until the endpoints are upgraded.
therefore advised to either upgrade the endpoints to newer software, or to configure both the option
242 and 173 on the DHCP server until the endpoints are upgraded.
Persistent settings
Persistent settings allow the administrator to enforce settings on systems throughout the net work.
These persistent settings can be specified during pre-registration or after the system has been added
to Cisco TMS (via the Persi stent settings tab in Navigator).
These persistent settings can be specified during pre-registration or after the system has been added
to Cisco TMS (via the Persi stent settings tab in Navigator).
The persistent settings will be set on the endpoint every time Cisco TMS receives a boot event from
the endpoint; either via SNMP or HTTP. The Persistent setting templat e is also set on the system at
the same time every day. This time is based on the first time the template was set on the system and
is configurable when editing the template in the System s > Provi sioning > Configuration
Templates page.
the endpoint; either via SNMP or HTTP. The Persistent setting templat e is also set on the system at
the same time every day. This time is based on the first time the template was set on the system and
is configurable when editing the template in the System s > Provi sioning > Configuration
Templates page.
To view a log of the daily updates go to System s > Provi sioning Activity Status. You will see that
there are 2 types of ent ries; the first will be when the template has been set on the system and this will
have no recurrence set. As the second entry you will see the templat e again but the recurrence will be
set to every day. If you click on this description, you will see a log of all transactions for this template.
there are 2 types of ent ries; the first will be when the template has been set on the system and this will
have no recurrence set. As the second entry you will see the templat e again but the recurrence will be
set to every day. If you click on this description, you will see a log of all transactions for this template.
There are four persistent settings, and three of them allow you to set a persistent System Name,
H323 Id, E164 Alia s and SIP URI. The last setting gives you the option to pick a predefined template
that will be set on the endpoint after every system boot. The template can typically include settings like
Auto ans wer on, Microphone off and Volume 7.
H323 Id, E164 Alia s and SIP URI. The last setting gives you the option to pick a predefined template
that will be set on the endpoint after every system boot. The template can typically include settings like
Auto ans wer on, Microphone off and Volume 7.
Swap a system in Cisco TMS
Systems get an id (Cisco TMS System Id) when they are first added to Cisco TMS. This id is used as
the reference for the systems in booking, reporting, event, permissions etc. It is therefore important to
retain the id, even if a system gets swapped (because of theft, upgrade, hardware failure etc). A
system should therefore never be purged from Cisco TMS. It may be deleted from a folder since the
data for the system will still be in the database, but it should not be purged unless you are 100%
confident that a new system should take over this system’s roles.
the reference for the systems in booking, reporting, event, permissions etc. It is therefore important to
retain the id, even if a system gets swapped (because of theft, upgrade, hardware failure etc). A
system should therefore never be purged from Cisco TMS. It may be deleted from a folder since the
data for the system will still be in the database, but it should not be purged unless you are 100%
confident that a new system should take over this system’s roles.
If a system in Cisco TMS is out of order, or awaiting a swap, it can be set to Not Allow Book ings. This
is done in the Connection tab in Systems > Navigator. By doing this you can avoid any one booking
the system while it is unavailable.
is done in the Connection tab in Systems > Navigator. By doing this you can avoid any one booking
the system while it is unavailable.