# 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
…
- 10
- 11
- 12
- 13

UNCLASSIFIED
Cherry Bomb Program Cherry Blossom Cherry Tree Upgrade Test Procedures
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 (original) master
server up. Dump the iptables rules (/sbin/iptables –L –n >
~/iptables_after_failover2.out) and the routing entries (/sbin/route >
~/routes_after_failover2.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
(original) slave server is actively replicating data from the new (original) master
server, and all verification steps pass.
2.14 Delete Flytrap Test
Description: Tests the delete Flytrap script and cleans the production server of Test
Flytrap data.
Setup: From a control terminal, establish an ssh terminal to the cb-cc master server.
Run: Stop the CT services (“~cbuser/bin/disable-server.sh”). Run the
runDeleteFlytrap.sh
(“~cbuser/CherryBlossom/CherryTree/Release/runDeleteFlytrap.sh) script on the
Test Flytrap. Start the CT services (“~cbuser/bin/enable-server.sh”). Verify the
Flytrap is no longer in the system (CW View -> Flytraps page). Have the Flytrap
Beacon/Alert. Verify the Flytrap is again in the system. Stop the CT services
(“~cbuser/bin/disable-server.sh”). Run the runDeleteFlytrap.sh
(“~cbuser/CherryBlossom/CherryTree/Release/runDeleteFlytrap.sh) script on the
Test Flytrap. Verify the Flytrap is no longer in the system (CW View -> Flytraps
page).
Pass/Fail: The test passes if the delete Flytrap script runs successfully, the
“deleted” Flytrap can beacon again successfully, and then the Flytrap can again be
deleted.
UNCLASSIFIED
12

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