# Vault 7: Projects

This publication series is about specific projects related to the Vault 7 main publication.

### Cherry Blossom

# CherryBlossom -- Installation Guide

19 July, 2012

- 1
- 2
…
- 14
- 15
- 16
- 17
- 18
…
- 20
- 21

SECRET//20350112
8 (U) CB Server Troubleshooting
(U) This section describes some basic troubleshooting related to the CB servers.
(U) Please contact appropriate CB staff before making permanent (i.e., persistent through
a reboot) changes to any CB server. Note that appropriate Points of Contact are listed in
section 3.
8.1 (U) CB Server Log Files
(U) The CherryTree and CherryWeb server applications write diagnostic log information
to log files.
(U) CherryTree writes log files in the /var/log/cherrytree/ directory. CherryTree.log is the
main informational log. CherryTree_error.log is the error log. Authentication.log logs
CherryTree authentication failures.
(U) CherryWeb, writes log files in the /var/log/cherryweb/ directory. CherryWeb.log is
the main informational log.
8.2 (U) Troubleshooting CB Server (Backend) Issues
(U) The health and status of the CB servers are monitored by the sponsor-maintained
SNMP Monitoring system (see section 7 for more details). The first step to
troubleshooting the CB servers is to check CB server status using the SNMP Monitoring
system (seek assistance from the appropriate sponsor staff if necessary). The most critical
server to the CB system is the CB Master server (also referred to as the CB-CC Master in
the network diagram of section 7). This is the CB server that currently holds the “CB CC
Service IP” (see section 5.2). This is the CB server that runs the Cherry Tree and Cherry
Web services, accepts beacons and other communications from Flytraps, and manages
the CB database. If the SNMP Monitoring system is reporting that the CB Master server
is down, then the first troubleshooting step is to determine whether the issue is related to
either:
1. The CB server, or
2. The network infrastructure, including firewalls, switches, routers, and gateways.
(S) For most or all of the troubleshooting steps, you will need an Icon (formerly Genesis)
terminal and a “root” console terminal to the CB Server (see 5.4). The network diagram
of section 7 is also extremely helpful for troubleshooting.
8.2.1 (U) Network Connectivity/Ping Diagnostic
(U) From “root” console (see 5.4), attempt to ping the CB Master Server (i.e., ping the
CB Service IP of 5.2). If you can ping the Master server, then at least the Master server’s
ethernet interface is up, and the server’s OS is functional – go to section 8.2.2. If you
cannot ping the Master server’s CB Service IP, then ping the Master server’s “Persistent”
IP address (see the network diagram of 5.1). If you cannot ping the Master server’s
Persistent IP, then the most likely problems are:
SECRET//20350112
16

- 1
- 2
…
- 14
- 15
- 16
- 17
- 18
…
- 20
- 21