Running Peakflow SP 7.

0 in a
Virtual Machine
Running Peakflow SP 7.0 in a Virtual Machine

The information contained within this document is subject to change without notice. Arbor Networks, Inc.
makes no warranty of any kind with regard to this material, including, but not limited to, the implied
warranties of merchantability and fitness for a particular purpose. Arbor Networks, Inc. shall not be liable
for errors contained herein or for any direct or indirect, incidental, special, or consequential damages in
connection with the furnishings, performance, or use of this material.

Copyright © 2013-2014 Arbor Networks, Inc. Arbor Networks, Peakflow, ArbOS, ATLAS, Pravail, Arbor
Optima, Arbor Cloud, Cloud Signaling, the Arbor Networks logo, and Arbor Networks: Smart. Available.
Secure are all trademarks of Arbor Networks, Inc. All other brand names may be trademarks of their
respective owners. Proprietary and Confidential Information of Arbor Networks, Inc.

Document Number: SP-VM-600-2014/11

November 6, 2014

2 | Arbor Networks Proprietary and Confidential Information of Arbor Networks Inc.

 Running Peakflow SP 7.0 in a Virtual Machine

Table of Contents
Introduction to Running Peakflow SP in a Virtual Machine ........................................................................... 4
Software Requirements for a Peakflow SP VM Instance .............................................................................. 4
Hardware Recommendations for a Peakflow SP VM Instance..................................................................... 5
Additional Recommendations for a Peakflow SP VM Instance .................................................................... 5
Platforms Tested with a Peakflow SP VM Instance ...................................................................................... 6
Performance Benchmarks for a Peakflow SP VMware Instance .................................................................. 7
VMware Performance benchmarks with Bonnie++ ................................................................................ 7
VMware Performance benchmarks with ApacheBench ......................................................................... 8
Performance Benchmarks for a Peakflow SP KVM Instance and Xen Instance .......................................... 9
Performance benchmarks with Bonnie++ .............................................................................................. 9
Performance benchmarks with ApacheBench ....................................................................................... 9
CLI Commands Used for Performance Benchmarks .................................................................................. 10
Installing Peakflow SP 7.0 in a VM ............................................................................................................. 11
Installing Peakflow SP 7.0 software ..................................................................................................... 11
Setting the hostname ............................................................................................................................ 11
Configuring interfaces ........................................................................................................................... 11
Enabling access to services ................................................................................................................. 12
Setting the date and time...................................................................................................................... 13
About adding an NTP server ................................................................................................................ 13
Rebooting the system ........................................................................................................................... 13
About adding a local DNS server ......................................................................................................... 13
Adding a local DNS server ................................................................................................................... 13
Adding a global DNS server on the leader appliance........................................................................... 14
Changing the administrator password .................................................................................................. 14
Installing the SSL certificate ................................................................................................................. 14
Initializing the appliance ....................................................................................................................... 14
Committing configuration changes and starting services ..................................................................... 15
Who to Contact Concerning Performance Questions ................................................................................. 15

Proprietary and Confidential Information of Arbor Networks Inc. Arbor Networks | 3

Running Peakflow SP 7.0 in a Virtual Machine

Introduction to Running Peakflow SP in a Virtual Machine

After you convert your Peakflow SP deployment to flexible licensing, you can run Peakflow SP 7.0 in a
virtual machine (VM). The ability to run Peakflow SP 7.0 in a VM allows you to dynamically scale your
deployment to add routers, to improve performance, and to monitor more of your infrastructure without
having to manage a large deployment of physical Peakflow SP appliances.

For information on converting your deployment to flexible licensing, see “Converting Your Deployment to
Peakflow Flexible Licensing” in the Peakflow SP and Threat Management System (TMS) User Guide.

Important: The leader and backup leader must be physical Peakflow SP appliances.

Arbor has tested running Peakflow SP 7.0 in a virtual machine with VMware, Xen, and KVM. This
document includes performance benchmarks for VMware, Xen, and KVM with Bonnie++ and
ApacheBench.

This document provides the following:

• Software Requirements for a Peakflow SP VM Instance
• Hardware Recommendations for a Peakflow SP VM Instance
• Additional Recommendations for a Peakflow SP VM Instance
• Platforms Tested with a Peakflow SP VM Instance
• Performance Benchmarks for a Peakflow SP VMware Instance
• Performance Benchmarks for a Peakflow SP KVM Instance and Xen Instance
• CLI Commands Used for Performance Benchmarks
• Installing Peakflow SP 7.0 in a VM
• Who to Contact Concerning Performance Questions

Software Requirements for a Peakflow SP VM Instance

The following are the software requirements for installing Peakflow SP 7.0 in VMware virtual machine:
• VMware vSphere Hypervisor software (formerly known as ESXi), version 5.0, 5.1, or 5.5.
For more information, see http://www.vmware.com/products/vsphere-hypervisor/overview.html.
• VMware vSphere Client software, version 5.0, 5.1, or 5.5.
Arbor has tested installing Xen on the Xen Cloud Platform version 1.6.10-61809c and installing KVM on
QEMU version 1.4.2. Xen and KVM should work on a wide variety of platforms in addition to the ones on
which it was tested by Arbor.

Note: Peakflow SP should run on other versions of the above hypervisors as well. Arbor will periodically
test and update support for newer versions of hypervisors as they are released. We make every effort to
support our product on any version of a supported hypervisor. If problems arise due to an issue specific to
an unsupported hypervisor version, we may add support for that version in a future software release.

4 | Arbor Networks Proprietary and Confidential Information of Arbor Networks Inc.

 Running Peakflow SP 7.0 in a Virtual Machine

Hardware Recommendations for a Peakflow SP VM Instance

Arbor makes the following hardware recommendations for a Peakflow SP VM instance:

Hardware Minimum Maximum Additional Information

Core allocation 4 32 Arbor has tested and recommends a Peakflow SP VM

instance with 4 to 32 cores. An instance of 4 cores is only
recommended if the load is expected to be light.
Important: With Xen, the maximum number of cores is 15.
Flow processing does not work with 16 or more cores,

Memory allocation 8 GB 16 GB The Peakflow SP VM instance should have a memory

allocation of either 8 GB of RAM or 16 GB of RAM. Arbor
strongly recommends against other memory allocations. A
memory allocation of more than 16 GB of RAM is not
supported. If more than 16 GB of RAM is allocated, it will not
be used.

Disk allocation (user 100 GB none For an appliance that has the user interface role, the
interface role) Peakflow SP VM instance should have a minimum of 100 GB
of disk space.

Disk allocation (traffic 500 GB none For an appliance that has the traffic and routing analysis role,
and routing analysis the Peakflow SP VM instance should have a minimum of 500
role) GB of disk space. If it is a temporary appliance, it only needs
a minimum of 100 GB of disk space.

Network interfaces 1 10 Each Peakflow SP VM instance should have its own 1 Gb

interface because Peakflow SP can be a network intensive
application.
Important: Do not configure more than two Peakflow SP VM
instances to share a network interface, especially if they are
flow collectors.

Additional Recommendations for a Peakflow SP VM Instance

Arbor makes the follow recommendations concerning a Peakflow SP VM instance:
• Time service
NTP should be enabled on the VM host server that has a Peakflow SP VM instance because
Peaklfow SP in a VM syncs time automatically to the VM host server. The time on the host needs to
be in sync within seconds of the deployment leader and other deployment appliances for the stable
and accurate functioning of Peakflow SP.
• Storage device
Each Peakflow SP VM instance should have its own storage device, whether it is a spinning media
hard drive or a solid-state drive (SSD). If a Peakflow SP VM instance must share a disk with another
VM instance, the disk should be an SSD. Because Peakflow SP can be quite disk intensive, multiple
Peakflow SP VM instances that share a single read-write head on a spinning media hard drive will not
perform well.
• VM server load
The VM server that hosts Peakflow SP VM instances should not be an over-provisioned VMware
server, especially with regard to memory.

Proprietary and Confidential Information of Arbor Networks Inc. Arbor Networks | 5

Running Peakflow SP 7.0 in a Virtual Machine

• VMware vMotion
You can use vMotion to move a Peakflow SP VM instance to another VM host server. Arbor
recommends that you stop Peakflow SP services on the VM instance before you move the VM
instance.
Important: Both VM instances must use the same network name.
• VMware provisioning options
When configuring the VMware settings, use the default settings except for the following settings:
Setting Selection
Network adapter E1000
OS Other Linux 32-bit
Storage Thick Provisioned Lazy Zeroed

Platforms Tested with a Peakflow SP VM Instance

Arbor has tested Peakflow SP VMware instances on the following vendor platforms:

Vendor and Model CPU Cores RAM Storage NICs

Cisco UCSB-B200-M3 2x E5-2650 @ 2GHz 16 64 GB 8x 120GB SSD SATA 4x 10G SFP+

Dell PowerEdge R720 2x E5-2609 @ 2.4 GHz 8 16 GB 8x 120GB SSD SATA 6x 1G copper
2x E5-2670 @ 2.6 GHz 16 32 GB 8x 120GB SSD SATA 6x 1G copper

HP ProLiant DL380p Gen8 2x E5-2620 @ 2GHz 12 64 GB 4x 480GB SSD SATA 12x 1G copper
4x 1TB 7.2K SAS 12x 1G copper

Note: Arbor has tested Peakflow SP Xen and KVM instances only on Cisco UCSP-B200-M3.

6 | Arbor Networks Proprietary and Confidential Information of Arbor Networks Inc.

 Running Peakflow SP 7.0 in a Virtual Machine

Performance Benchmarks for a Peakflow SP VMware Instance

VMware Performance benchmarks with Bonnie++
Bonnie++ is a disk and file system benchmark. It gives an indication of the data storage performance for
all appliance roles in VMs.

Note: The performance benchmark numbers are for VMware 5.0. The numbers may vary slightly between
versions of VMware.

Note: In the following table, the text for the minimum and maximum values for each of the benchmarks is
underlined and the text is red for the minimum values and green for the maximum values.

Expected Sequential Output Sequential Input Sequential Random

Vendor and Flow Per Block Per Block Create Create
Cores Performance /sec /sec
Model Character K/sec Character K/sec
K/sec K/sec
SP 6000 Appliance 16 200,000 42,644 572,473 57,817 1,368,147

SP 5500 Appliance
(serial number 8 80,000 71,786 181,407 69,745 320,665 30,226
begins with AZLH)

SP 5500 Appliance
(serial number 2 20,000 41,188 59,308 30,543 39,961 15,596 22,423
begins with AZLR)

4 35,000 15,057 45,295 59,427 75,033 14,050

Cisco 8 50,000 15,221 45,639 59,105 70,133 7,006 25,428

UCSB-B200-M3
16 100,000 31,557 45,414 57,079 67,934 7,131
(7200 RPM
Spindle Drive) 24 150,000 45,101 46,173 57,991 67,834 14,750 22,318

32 200,000 20,473 43,971 55,563 62,178 13,410

4 35,000 59,157 725,311 77,330 694,619 25,197 12,876

8 50.000 56,866 800,590 80,014 1,126,181 13,581 18,371

Dell
PowerEdge R720 16 100,000 62,686 695,063 79,450 805,461 13,581 12,234
(SSD Drive)
24 150,000 59,278 838,433 79,198 855,072 29,845

32 200,000 60,502 758,543 78,386 725,967 29,450 29,667

4 35,000 46,793 439,196 60,524 732,695 31,872

HP
8 50,000 42,438 395,084 53,058 611,774 29,438 24,802
ProLiant DL380p
Gen8 16 100,000 45,163 408,767 60,975 949,122
(SSD Drive)
24 150,000 46,010 531,412 53,486 825,985 21,517 16,707

Proprietary and Confidential Information of Arbor Networks Inc. Arbor Networks | 7

Running Peakflow SP 7.0 in a Virtual Machine

VMware Performance benchmarks with ApacheBench

ApacheBench is a performance benchmark for the Apache web server. It gives an indication of CPU
performance of a VM for all appliance roles and overall performance of a VM that has the user interface
role.

Note: The performance benchmark numbers are for VMware 5.0. The numbers may vary slightly between
versions of VMware.

Note: In the following table, the text for the minimum and maximum values for each of the benchmarks is
underlined and the text is red for the minimum values and green for the maximum values.

Vendor and Cores Expected Flow Request Transfer Total Request Rate
Model Performance Completed
SP 6000 Appliance 16 200,000 37,790 8,842,860 62.98

SP 5500 Appliance
(with a serial
8 80,000 39,433 9,227,322 65.72
number that begins
with AZLH)

SP 5500 Appliance
(with a serial 2 20,000 6,893 1,612,962 11.48
number that begins
with AZLR)

4 35,000 34,472 8,066,448 57.45

Cisco 8 50,000 34,406 8,051,004 57.34

UCSB-B200-M3
16 100,000 43,576 10,196,784 72.63
(7200 RPM Spindle
Drive) 24 150,000 42,576 9,962,784 70.96

32 200,000 42,774 10,009,116 71.29

4 35,000 43,942 10,282,428 73.24

8 50,000 43,279 10,127,286 72.13

Dell
PowerEdge R720 16 100,000 50,000 11,700,000 91.52
(SSD Drive)
24 150,000 50,000 11,700,000 91.47

32 200,000 50,000 11,700,000 90.48

4 35,000 33,002 7,722,468 55.00

HP
8 50,000 32,622 7,633,548 54.37
ProLiant DL380p
Gen8 16 100,000 41,421 9,692,514 69.03
(SSD Drive)
24 150,000 39,836 9,321,624 66.39

8 | Arbor Networks Proprietary and Confidential Information of Arbor Networks Inc.

 Running Peakflow SP 7.0 in a Virtual Machine

Performance Benchmarks for a Peakflow SP KVM Instance and Xen

Instance
Performance benchmarks with Bonnie++
Bonnie++ is a disk and file system benchmark. It gives an indication of the data storage performance for
all appliance roles in VMs.

Sequential Output Sequential Input Sequential Random

Expected Create Create
VM Cores Flow Per Block Per Block
Character K/sec Character K/sec /sec /sec
Performance
K/sec K/sec
4 35,000 59,157 725,311 77,330 694,619 25,197 12,876

VMware 8 50,000 75,532 714,090 77.143 1,222,560 28,807 29,728

16 100,000 62,686 695,063 79,450 805,461 13,581 18,371

4 35,000 57,215 540,658 49,375 215,304 16,148

KVM 8 40,000 35,194 37,989 40,370 68,510 12,010

16 50,000 57,148 490,268 70,883 301,057 14,132 24,606

4 25,000 53,986 629,850 86,700 514,338 25,269 19,900

Xen 8 40,000 33,330 50,068 47,425 101,280 9,759 20,284

15 40,000 32,103 40,271 41,665 83,888 9,055

Performance benchmarks with ApacheBench

ApacheBench is a performance benchmark for the Apache web server. It gives an indication of CPU
performance of a VM for all appliance roles and overall performance of a VM that has the user interface
role.

Cores Expected Request Transfer Total Request Rate

VM Flow Completed
Performance
4 35,000 43,942 10,282,428 73.24

VMware 8 50,000 43,891 10,270,494 73.15

16 100,000 43,279 10,127,286 72.13

4 35,000 47,754 11,174,436 79.59

KVM 8 40,000 27,636 6,466,824 46.06

16 50,000 50,000 11,700,000 97.07

4 25,000 46,947 10,985,598 78.24

Xen 8 40,000 30,016 7,023,744 50.03

15 40,000 41,040 9,603,360 68.40

Proprietary and Confidential Information of Arbor Networks Inc. Arbor Networks | 9

Running Peakflow SP 7.0 in a Virtual Machine

CLI Commands Used for Performance Benchmarks

The following CLI commands were used to generate the performance benchmarks:

Command Description
/ system benchmark run This command starts the benchmarking with the
apachebench and bonnie++ systems.
/ system benchmark show This command displays whether any benchmark tests
are running and when the last benchmark test was run.
/ system benchmark stop This command stops a benchmark test that is in
progress.
benchmark_raw This command is run from shell and produces the test
results in CSV format after benchmarks are run.

Note: Benchmarks should be generated without services running.

The benchmark-raw command produces comma-separated output. The comma-separated output will
have values that correspond to the entries in the following text:
<date>, <Arbos Version>, <Serial Number>, bonnie, <bonnie file size for IO
tests>, <sequential output: per character; K/s>, <sequential output: per
character; %cpu>, <sequential output: block; K/s>, <sequential output: block;
%cpu>, <sequential output: reqrite; K/s>, <sequential output: rewrite; %cpu>,
<sequential input: per character; K/s>, <sequential input: per character;
%cpu>, <sequential input: block; K/s>, <sequential input: block; %cpu>,
<random seeks; /sec>, <random seeks; %cpu>, <number of files for creation
test>, <sequential create: create; /sec>, <sequential create: create; %cpu>,
<sequential create: read; /sec>, <sequential create: read; %cpu>, <sequential
create: delete; /sec>, <sequential create: delete; %cpu>, <random create:
create; /sec>, <random create: create; %cpu>, <random create: read; /sec>,
<random create: read; %cpu>, <random create: delete; /sec>, <random create:
delete; %cpu>, ab, <test time; sec>, <requests completed>, <requests failed>,
<write errors>, <total bytes transferred>, <html bytes transferred>, <request
rate; /sec>, sysinfo, <total memory; MB>, <disk size; GB>, <number of
processors>, <number of cores per processor>, <processor speed; MHz>

To show what each entry in the comma-separated output stands for, you can import the preceding text
into a spreadsheet program along with the comma-separated output. Fields in the < > brackets change,
while the values “bonnie,” “ab,” and “sysinfo” are static fields. The format for the fields in the < > brackets
is “test type: subtype; units.”

10 | Arbor Networks Proprietary and Confidential Information of Arbor Networks Inc.

 Running Peakflow SP 7.0 in a Virtual Machine

Installing Peakflow SP 7.0 in a VM

The following sections describe how to install Peakflow SP 7.0 in a VM. The following table describes the
CLI command syntax used in these sections:

CLI Command Syntax Description

Command Items that you must type as shown.

variable Placeholder for which you must supply a value.

Installing Peakflow SP 7.0 software

To install Peakflow SP 7.0 software:
1. Provision a VM that has 4 to 32 cores.
Note: With Xen, the VM must have less than 16 cores.
For performance benchmarks for VMware, KVM, and Xen, see Performance Benchmarks for a
Peakflow SP VMware Instance and Performance Benchmarks for a Peakflow SP KVM Instance and
Xen Instance.
2. Configure the VM to mount and boot from the SP VM ISO.
Note: VMware and KVM use the same ISO, while Xen uses a different ISO.
3. Connect to the VM’s VGA console.
4. Power on the VM.
5. To start the boot menu, press any key when you see the message, “Press any key to continue.”
6. At the boot menu, select (re)install (VGA).

A warning message appears that states installing removes all data.

7. To confirm that you want to begin the installation process, type y when prompted, and then press
ENTER.

8. To initialize the disk, type y, and then press ENTER.

9. When prompted to install the ArbOS software package, type y, and then press ENTER.
10. When prompted to install the Peakflow SP appliance software, type y, and then press ENTER.

Setting the hostname

To set the hostname:
• Type a hostname for the appliance, and then press ENTER.

Configuring interfaces
To configure interfaces:
1. Determine if you are using the listed interface.
2. If you are not using the interface, press ENTER.
3. If you are using the interface, do the following:
a. Type an IP_address for the listed interface, and then press ENTER.
b. Type a netmask for the interface, and then press ENTER.

Proprietary and Confidential Information of Arbor Networks Inc. Arbor Networks | 11

Running Peakflow SP 7.0 in a Virtual Machine

c. At the media type prompt, press ENTER.

4. Repeat Step 1 through Step 3 for each interface on the appliance.
5. Type the IP_address of the default route gateway, and then press ENTER.

Enabling access to services

When you configure the access to services, you can press ENTER to bypass a setting. All of these settings
can be configured later using the Web UI or a CLI command.

To enable access to services:

1. At the BGP access prompt, press ENTER to skip configuring BGP access to the appliance.
You can configure BGP access to the appliance in the Web UI when you configure routers.
2. At the Cloud Signaling access prompt, press ENTER to skip configuring Cloud Signaling access to the
appliance.
You can configure Cloud Signaling access to the appliance in the Web UI when you configure a
managed object.
3. At the FTP access prompt, do one of the following:
 If you need to copy files from an FTP server, type the CIDR_block from which you want to allow
FTP access to the appliance, and then press ENTER.
 If you do not need to copy files from an FTP server, press ENTER.
4. At the HTTP access prompt, type the CIDR_block from which you want allow HTTP access to the
appliance, and then press ENTER.
5. At the HTTPS access prompt, do one of the following:
 If you are configuring an appliance that has the user interface role, then type the CIDR_block of a
network from which you want to enable HTTPS access, and then press ENTER.
 If you are configuring an appliance that has the traffic and routing analysis role or the data
storage role, then press ENTER.
6. Repeat Step 5 for each network from which you want to enable HTTPS access.
7. At the OSPF access prompt, press ENTER to skip configuring OSPF access.
8. At the ping access prompt, type the CIDR_block from which you want to allow ping access to the
appliance, and then press ENTER.
9. Repeat Step 8 for each network from which you want to enable ping access.
10. At the SNMP access prompt, type the CIDR_block from which you want to allow SNMP queries to the
appliance, and then press ENTER.
11. If the SPCOMM access prompt appears, press ENTER to deny all SPCOMM access to the appliance.
Note: Configurations that you perform later (bootstrap command) will automatically add SPCOMM
access as needed.
12. At the telnet access prompt, type the CIDR_block of a network from which you want to allow telnet
access to the appliance, and then press ENTER.
Note: Arbor does not recommend using telnet for CLI access, because it is an insecure protocol; you
should use SSH instead. Add networks to the telnet access list only if you will later enable telnet
access.

12 | Arbor Networks Proprietary and Confidential Information of Arbor Networks Inc.

 Running Peakflow SP 7.0 in a Virtual Machine

13. If the TFTP access prompt appears, press ENTER to skip configuring TFTP access.
TFTP is not supported.
14. If the VRRP access prompt appears, press ENTER to skip configuring VRRP access.
Peakflow SP does not support VRRP.
15. At the SSH access prompt, type the CIDR_block of the network from which you want to enable SSH
access, and then press ENTER.
16. Repeat Step 15 for each network from which you want to enable SSH access.

Setting the date and time

To set the date and time:
• Type the date in the format mmddHHMMyyyy.SS (month, day, hour, minute, year, second), and then
press ENTER.

About adding an NTP server

You must enable NTP on the VM host server because you cannot do this on the VM. When the NTP
prompt appears, press ENTER to skip enabling NTP.

Rebooting the system

To reboot the system:
1. When you are prompted to reboot the system, type y, and then press ENTER.
2. After the appliance restarts, log on to the system by using the administrator user name (admin) and
password (arbor).
To change the administrator password, see Changing the administrator password.

About adding a local DNS server

On a leader appliance, you can add a DNS server to a local or global configuration. On a non-leader
appliance, you can only add a DNS server to a local configuration. When a DNS server is added to a local
configuration, Peakflow SP associates the DNS server with the individual appliance. A local DNS
configuration takes precedence over a global DNS configuration.

For additional information about adding DNS servers, see:

• “Configuring DNS Servers” in the Peakflow SP and Threat Management System (TMS) Advanced
Configuration Guide.
• “Configuring Network Services” in the Peakflow SP and Threat Management System (TMS) User
Guide.

Adding a local DNS server

To add a local DNS server:
• Type / services dns server add IP_address, and then press ENTER.
where:
IP_address = IP address of the DNS server

Proprietary and Confidential Information of Arbor Networks Inc. Arbor Networks | 13

Running Peakflow SP 7.0 in a Virtual Machine

Adding a global DNS server on the leader appliance

To add a global DNS server on the leader appliance:
• Type / services dns server add IP_address global, and then press ENTER.
where:
IP_address = IP address of the DNS server

Changing the administrator password

To change the administrator password:
1. Type / services aaa local password admin interactive, and then press ENTER.
2. Type the new_password, and then press ENTER.
3. Type the new_password again, and then press ENTER.

Installing the SSL certificate

SSL Web server certificates keep information private while in transit between your Web server and Web
browsers. You can install SSL Web server certificates from external authorities (such as RSA or
VeriSign). You can also use Arbor’s certificate packages. Arbor provides a default certificate package to
new customers. When you require a new certificate, you can request a new certificate from Arbor or
acquire a new certificate package from a different authority.

Important: If you upload external certificate files, make sure they are properly formatted and the lines are
terminated with UNIX-style newline characters.

Important: Peakflow SP does not support password-protected certificates.

Note: Using a certificate to install an appliance is optional.

To install the certificate:

1. Type / system files copy URL disk:, and then press ENTER.
where:
URL = the shared network resource where the certificate is located. (It can be either an HTTP or
FTP location.)
2. After the download is complete, type / system files install disk:file_name, and then press ENTER.
where:
file_name = the file name of the certificate package

Initializing the appliance

To initialize the appliance:
1. After the import of the SSL certificate is complete, type / services sp bootstrap nonleader
IP_address zone_secret role, and then press ENTER.
where:
IP_address = the IP address of the appliance
zone_secret = the word or phrase that is used by all appliances in the deployment for internal
communication
role = the role to assign to the appliance

14 | Arbor Networks Proprietary and Confidential Information of Arbor Networks Inc.

 Running Peakflow SP 7.0 in a Virtual Machine

Type bi for the data storage role, cp for the traffic and routing analysis role, or pi for the user
interface role.
Note: For information about appliance roles, see "Introduction to SP Appliances" in the Peakflow
SP and Threat Management System (TMS) User Guide.
2. To delete the existing alert and mitigation database, type y, and then press ENTER.

Committing configuration changes and starting services

To commit configuration changes and start services:
1. Do one of the following:
 If the Commit (and activate) configuration? prompt appears, type y, and then press
ENTER.

 Type config write, and then press ENTER to save the configuration.
2. To start the appliance, type / services sp start, and then press ENTER.

Who to Contact Concerning Performance Questions

If you have questions about the performance of a Peakflow SP VM instance, use one of the following
methods to contact Arbor Customer Support:

Method Contact Details

Telephone US toll free 1 877 272 6721
Worldwide +1 781 362 4301

Web http://support.arbor.net/

Email [email protected]

Proprietary and Confidential Information of Arbor Networks Inc. Arbor Networks | 15