Installation Guide

NOTE: If you are using the Keyston python CLI, use this command: export
no_proxy=SERVER_IP[,IP,...]
If you are using curl, use this command: --noproxy ${SERVER_IP}
8.6 Local Keystone server installation failure
8.6.1 Problem description
Keystone server verification is done during the controller service startup. While the controller can
start without keystone being configured or running, the controller service unsuccessfully attempts
to verify the Keystone server.
8.6.2 Solution
Examine the following log for entries indicating Keystone server installation problems:
/var/log/sdn/virgo/stdout.log.
8.7 NTP not operating
8.7.1 Problem description
You observe either of the following:
• There are significant time differences between controllers or between the controller and other
appliances on the network.
• Running ntpdc -c peers does not output a list of one or more NTP time servers similar to
the following:
remote local st poll reach delay offset disp
=======================================================================
=clock.example.net 192.0.2.105 16 64 0 0.000000 0.000000 3.99217
=myco.altopt.ca 192.0.2.137 16 64 0 0.000000 0.000000 3.99217
8.7.2 Solution
NTP may not be configured with any valid time servers, or configured time servers are not
responding.
Do one of the following:
• Uninstall, then reinstall the controller, then see “Verifying the NTP configuration” (page 16).
• Contact your System Administrator.
8.8 Wrong provider type (PKI) on the Keystone server
8.8.1 Problem description
Controller authentication fails due to a Keystone server problem. A possible problem source is that
the Keystone server is configured with the PKI provider type instead of the UUID provider type.
8.8.2 Solution
Verify that the keystone configuration file has the provider type set to UUID by examining the file
at /etc/keystone/keystone.conf on the machine hosting the Keystone server. This file
should include the following line in the [token] section of the keystone.conf file.
provider=keystone.token.providers.uuid.Provider
In the controller installation with a local Keystone server, entering the UUID provider type is done
during the installation process. (See Step 2 in section “Configuring a user on a local Keystone
8.6 Local Keystone server installation failure 23