12. Verify Contrail plugin

To verify your installation after deployment, perform the basic checks described below.

1. Verify that Contrail services are running.

   1. Login to the Contrail controller node and run contrail-status command. All services should be in “active” state:

      # contrail-status
          == Contrail Control ==
          supervisor-control:           active
          contrail-control              active
          contrail-control-nodemgr      active
          contrail-dns                  active
          contrail-named                active
      
          == Contrail Analytics ==
          supervisor-analytics:         active
          contrail-analytics-api        active
          contrail-analytics-nodemgr    active
          contrail-collector            active
          contrail-query-engine         active
          contrail-snmp-collector       active
          contrail-topology             active
      
          == Contrail Config ==
          supervisor-config:            active
          contrail-api:0                active
          contrail-config-nodemgr       active
          contrail-device-manager       active
          contrail-discovery:0          active
          contrail-schema               active
          contrail-svc-monitor          active
          ifmap                         active
      
          == Contrail Web UI ==
          supervisor-webui:             active
          contrail-webui                active
          contrail-webui-middleware     active
          == Contrail Database ==
          supervisor-database:          active
          contrail-database             active
          contrail-database-nodemgr     active
          kafka                         active
      

2. Verify the list of peers and peering status

   1. Login to Contrail web UI
   2. Go to Monitor -> Control nodes
   3. Choose any and select a Peers tab. You should see your compute nodes (vRouters) and external router in a list of peers with status Established

   

3. Verify that external router has been provisioned correctly:

   1. Login to Contrail web UI
   2. Go to Configure -> Infrastructure -> BGP routers.
   3. Verify the IP address of the router

   

   1. Use health checks in Fuel web UI, also called OSTF tests.

12.1. Run OSTF tests

12.1.1. Prerequisites for OSTF

1. OSTF tests require two pre-defined networks created - net04 and net04_ext. The networks are created by Fuel during deployment. This section includes instructions how to create them if they were accidentally deleted. Floating IP addresses from net04_ext should be accessible from Fuel master node.
2. Three tests from Functional tests set require floating IP addresses. They should be configured on external router, routable from Fuel master node and populated in the Openstack with Contrail environment.
3. HA tests require at least three Openstack controllers.
4. Platform services functional tests. require Ceilometer and MongoDB.

12.1.2. Configure OSTF networks and floating IPs

To configure OSTF networks and floating IPs:

1. Go to Contrail web UI Configure -> Networking -> Networks

2. Create network net04

   

3. Create network net04_ext.

   

   It should be marked as shared and external

   

   And have same route target as configured in an external router

   

4. Allocate floating IP addresses from net04_ext

   1. Go to Contrail WebUI Configure -> Networking -> Manage Floating IPs

      

5. Start OSTF tests.

See also

Fuel user-guide.

12.2. Troubleshooting

To troubleshoot:

1. Verify output of the contrail-status command.
2. Verify the logs for corresponding serivice:
   • Contrail logs are located in /var/log/contrail/ directory, and log names match with contrail service name.
   • Cassandra logs are located in /var/log/cassandra/
   • Zookeeper logs are in /var/log/zookeeper/