Administrator Guide

Table 22. Parameters for a xen.ini File (continued)
Parameter Description
CCMEnable={yes, no}
[CCMServer=<server_address>[:port]]
[GroupPrefix=<prefix>]
[GroupKey=<hashkey>]
[MQTTServer=<mqtt_address>[:<mqtt_port>]]
[AdvancedConfig={
no, yes}]
[CCMDefault={
no, yes}]
[Override={no, yes}]
[CAValidation=(yes, no)]
[Discover=(yes, no)]
[IgnoreMqtt=(yes,
no)]
Default is no.
CCMEnable — Yes/no option to enable the Cloud Client Manager
CCMServer — Specifies a IP address or URL address for the Cloud
Client Manager server. Default protocol is HTTPS. If "http://" or
"https://" does not exist, default port is 443. Once specified, it is
saved in the non-volatile memory. Default port is 80.
For example, CCMEnable=yes CCMServer=http://xxx:8080.
GroupPrefix and GroupKey — The options GroupPrefix and
GroupKey compose the group code of the Cloud Client Manager
server. Once specified, it is saved in the non-volatile memory.
MQTTServer — Specifies a IP address or URL address for the
MQTT server and MQTT port after the : (colon). Once specified, it
is saved in the non-volatile memory. Default MQTT port is 1883.
AdvancedConfig — Default is no. Yes/no option to enable the
Cloud Client Manager server and MQTT server fields in the GUI. If
AdvancedConfig=yes is specified, the Cloud Client Manager server
and MQTT server fields in the Cloud Client Manager UI will be
enabled. See also "PRIVILEGE=[None, Low, High] [LockDown= {no,
yes}] [HideSysInfo={no, yes}] [HidePPP={no, yes}] [HidePN={no,
yes}] [EnableNetworkTest={no, yes}]."
CCMDefault — Default is no.
Yes/no option to enable the Configure Cloud management dialog
will display during boot up. If CCMDefault=yes is specified and
both the CCMServer and GroupKey are NULL, the Configure Cloud
management dialog will display during boot up. Input group code
to connect to the default Cloud Client Manager server and default
MQTT server (us1-pns.cloudclientmanager.com).
Override — Default is no. Yes/no option to allow a groupkey from
the INI file to override the previous groupkey. If Override=yes is
specified, the groupkey from the INI file will override the previous
groupkey. Groupkey priority policy is listed as below:
The Groupkey can technically be applied in many places. Below are
the different places you can configure the group key in order of
priority that is if #1 is defined it will override #2 etc.
1. Local GUI configuration or groupkey received from CCM in a
Group Change command
2. Defined in INI file "ccmenable=yes groupkey=xxxx"
3. DHCP Option Tag #199
The Groupkey assigned in DCHP option #199 and INI parameter are
only used for "first time deployment" that is they only take effect,
if CCM is currently disabled,or if CCM is enabled but group-key is
NULL.
● If DCHP is defined and CCM is enabled or not NULL: The CCM
Group key in the DHCP is ignored since it is configured manually
in local UI or from CCM group change.
● If INI is defined and CCM is enabled or not NULL: The CCM
Group key in the INI is ignored since it is configured manually in
local UI or from CCM group change.
Creating and Using xen.ini Files
169