| ARRIS Enterprises, Inc. Confidential Information | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
kreatv-option-ntp_bcm15This IIP has been deprecated. Please use kreatv-option-timeman instead. This package enables NTP (Network Time Protocol) support. For more information about the NTP daemon/client (ntpd) used in the ARRIS STB please read www.ntp.org. There are 5 different "modes" for this iip. 4 are represented by a main parameter each, and they should not be mixed together. The 5th mode, Server mode, is enabled if neither of these parameter are set. The 4 main mode parameters are:
Server mode (none of the main mode parameters are set):All parameter available for the NTP daemon/client can be passed though via iip parameters, i.e kreatv-option-ntp:<option>=<string>,... For detailed information about configuration options please read Server Options. The first server option will be used for setting the system time at boot time before the NTP daemon is started. This is needed since the NTP daemon will exit if the difference is too large between the system clock and the time received. A simple example of this option is: kreatv-option-ntp:server=0.pool.ntp.org,server=1.pool.ntp.org,server=2.pool.ntp.org "dhcp" mode:ntpdhcp.sh will be copied into rc.sysinit file and run at startup. This file can get ntp server from DHCP server. There is one optional parameter that can be used to configure NTP. 1. ntpsh: when set to true (default): ntp.sh will be copied into the rc.sysinit file and run at startup. when set to false: ntp.sh will not be copied into the rc.sysinit file and will not run at startup. "configurable" mode:There are 5 main parameters used to configure NTP, its default value is specified by some information object.
The ntpinfo.sh file can check these specific objects to configure ntp.conf. The object value can be configured using kreatv-option-is-default, for example: If the server_object value is empty, default_server will be used, e.g default_server=timehost.cig.mot.com. Options for getting time by ntpdate The STB will try to connect to the first NTP server 'ntp_retry_attempts' times. There will be an 'ntp_retry_interval' seconds delay between requests. If the first server can not be reached the STB will try the next NTP server for 'ntp_retry_attempts' times. And so on with other servers from the list. If none of the servers can be reached then the STB boots without time information and connection attempts will be repeated every 'kreatv-option-timeman::time_sync_interval' seconds. "dynamic_client" mode:The NTP server list (dynamically created by the NTP Client device) is determined by a specific algorithm executed on some KreaTV-based STBs. The NTP Server IP Addresses are gathered and put into a table (in a user defined priority order). That table is traversed by the NTP Client using the current valid NTP Server IP Address taken from the table. Then specific processing will occur based on the response coming back from the NTP server upon a time request. If an error occurs, a defined number of retries will occur. If all retries are exhausted, the next IP Address in the table will be used, and so on. This algorithm will repeat itself forever going back to the beginning of the table when the end of the table is reached. If the NTP Server Address information changes, the NTP Client device will receive a notification and will rebuild the table based on the new NTP Server information. "dynamic_server" mode:The STB acts as an NTP server to serve the NTP clients (see Dynamic Client Option). It gets time from atsc headend, which means it should work with kreatv-option-atsctime. Parameters
Details
|
