# Vault 7: Projects

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

### Cherry Blossom

# CherryBomb -- CherryBlossom - CherryTree Upgrade Test Procedures (CDRL-14b)

8 August, 2012

- 1
- 2
…
- 9
- 10
- 11
- 12
- 13

UNCLASSIFIED
Cherry Bomb Program Cherry Blossom Cherry Tree Upgrade Test Procedures
Run: Verify the databases and the copy data on the cb-cc master and slave are in
sync.
Pass/Fail: The test passes if the databases and the copy data on the cb-cc master
and slave are in sync.
2.12 cb-cc Server Failover and Failure Recovery/Resynchronization
After Server Failover Test
Description: Tests the cb-cc server failover procedure and
recovery/resynchronization of cb-cc server data after a failover event.
Setup: From a control terminal, establish ssh terminals to the cb-cc master and
slave servers.
Run: Follow the Failover and Server Recovery instructions in the CB Installation
Guide. Verify that failover successfully occurs. Verify that at least one GTR Test
Flytrap has beaconed through each PoP. Verify the new slave is actively replicating
data from the new master server (i.e., repeat the “Database Replication Test”). Verify
that the sponsor SNMP monitoring system is reporting the cb-cc new master server
up. Dump the iptables rules (/sbin/iptables –L –n > ~/iptables_after_failover.out) and
the routing entries (/sbin/route > ~/routes_after_failover.out) and compare to the
respective *_before_reboot files (on the previous cb-cc master). Verify that the
server role is “master” by running the /usr/local/bin/check_cb_role script. Verify
mysql by running the /usr/local/bin/check_cb_mysql script (should report “master”,
mysql up with no errors). Verify CherryTree by running the
/usr/local/bin/check_cherrytree.sh script (should report “CherryTree OK”). Verify
CherryWeb by running the /usr/local/bin/check_cherryweb.sh script (should report
“CherryWeb OK”). Verify no errors were reported to the log files during startup
(visually inspect /var/log/cherrytree/CherryTree.log,
/var/log/cherrytree/CherryTree_error.log,
/var/log/cherryweb/CherryWeb.log for errors).
Pass/Fail: The test passes if the server failover happens successfully, GTR Test
Flytraps have beaconed to the “new” master server through all PoPs, and the new
slave server is actively replicating data from the new master server, and all
verification steps pass.
2.13 cb-cc Server Failover and Failure Recovery/Resynchronization
After Server Failover Test II (Failover to Original Master)
Description: Tests the cb-cc server failover procedure and
recovery/resynchronization of cb-cc server data after a failover event (really to just
restore the original master server to the role of master).
Setup: From a control terminal, establish ssh terminals to the cb-cc master and
slave servers.
UNCLASSIFIED
11

- 1
- 2
…
- 9
- 10
- 11
- 12
- 13