Technical data

System Licensing

Configure Time Services From the CLI

We recommend that you configure controllers to synchronize their system clock with

a Network Time Protocol (NTP) server. This ensures the system time is accurate and

standardized with other systems. Accurate and standardized system time is impor-

tant for alarms, traces, syslog, and applications such as cryptography that use time-

stamps as a parameter for key management and lifetime control. An accurate clock

is also necessary for intrusion detection, isolation and logging, as well as network

monitoring, measurement, and control.

During the initial system configuration, the setup script prompts for an IP address of

an NTP server. If you do not supply an IP address of an NTP server at that time, or if

you wish to change an assigned server at a later time, you can use the ntp server

followed by the ntp sync commands.

 To set up automatic periodic synchronizing with the configured NTP server, use

the command start-ntp.

There are several NTP servers that can be designated as the time server. The site

www.ntp.org provides a list of servers that can be used.

To set a server as an NTP server, use the command:

ntp server ip-address

where ip-address is the IP address of the NTP server providing clock synchronization.

Configure a Controller Index with the CLI

To configure a controller index from CLI, using the following commands

ramecntrl(0)# configure terminal

ramecntrl(0)(config)# controller-index 22

ramecntrl(0)(config)# exit

Note that changing the index causes a controller to reboot.

System Licensing

Licensing is embedded in controller firmware and is enabled with a Meru-generated

license file tied to that specific controller. Obtain these licensing files from

www.merunetworks.com/license.

Note:

If you choose not to use a NTP server to synchronize the system clock, the

system time can be set manually with the calendar set command.