Oracle Talari D6000 Installation instructions

Oracle® Talari D6000
Hardware Guide
F29965-02
April 2020

Oracle Talari D6000 Hardware Guide,
F29965-02
Copyright © 2018, 2020, Oracle and/or its affiliates.
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify,
license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.
Reverse engineering, disassembly, or decompilation of this software, unless required by law for
interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software,
any programs embedded, installed or activated on delivered hardware, and modifications of such programs)
and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end
users are "commercial computer software" or “commercial computer software documentation” pursuant to the
applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use,
reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or
adaptation of i) Oracle programs (including any operating system, integrated software, any programs
embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle
computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the
license contained in the applicable contract. The terms governing the U.S. Government’s use of Oracle cloud
services are defined by the applicable contract for such services. No other rights are granted to the U.S.
Government.
This software or hardware is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including applications that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you
shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are
used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc,
and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered
trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products,
and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise
set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be
responsible for any loss, costs, or damages incurred due to your access to or use of third-party content,
products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents
About this Guide
My Oracle Support iv
Emergency Response iv
Revision History
1 Oracle Talari D6000 Hardware Guide
Hardware and Software Requirements 1-1
Overview 1-1
Talari APN Overview 1-1
Front Panel Configuration 1-2
Rear Panel Configuration 1-2
NIC Indicator Codes 1-3
Hardware Specifications 1-4
Installing the Talari Appliance 1-4
Rack Mounting 1-4
LAN/WAN Connections 1-5
Cabling and Bypass Mode 1-5
Powering Up the Appliance 1-5
Network Deployment Options 1-5
Installation Option: Easy 1st Install 1-6
Installation Option: Manual Install 1-7
Collecting ILOM Diagnostics for D2000 and D6000 1-9
Creating a Bootable USB Drive on Linux 1-12
Creating a Bootable USB Drive on Windows 1-13
Booting with the USB Drive 1-14
iii

About this Guide
This guide describes the physical characteristics of the Oracle Talari D6000 Appliance.
It includes setting up the physical connections on front panel as well as how to mount
this appliance in a rack. The intended audience of this document is a Network
Administrator or a Network Operator.
My Oracle Support
My Oracle Support (https://support.oracle.com) is your initial point of contact for all
product support and training needs. A representative at Customer Access Support can
assist you with My Oracle Support registration.
Call the Customer Access Support main number at 1-800-223-1711 (toll-free in the
US), or call the Oracle Support hotline for your local country from the list at http://
www.oracle.com/us/support/contact/index.html. When calling, make the selections in
the sequence shown below on the Support telephone menu:
1. Select 2 for New Service Request.
2. Select 3 for Hardware, Networking and Solaris Operating System Support.
3. Select one of the following options:
•For Technical issues such as creating a new Service Request (SR), select 1.
•For Non-technical issues such as registration or assistance with My Oracle
Support, select 2.
You are connected to a live agent who can assist you with My Oracle Support
registration and opening a support ticket.
My Oracle Support is available 24 hours a day, 7 days a week, 365 days a year.
Emergency Response
If a critical service situation occurs, the Tekelec Customer Care Center offers
emergency response twenty-four hours a day, seven days a week. The emergency
response provides immediate coverage, automatic escalation, and other features to
ensure a rapid resolution to the problem.
A critical situation is defined as a problem that severely affects service, traffic, or
maintenance capabilities, and requires immediate corrective action. Critical problems
affect service or system operation, resulting in:
•Failure in the system that prevents transaction processing
•Reduction in system capacity or in system traffic-handling capability
•Inability to restart the system
•Corruption of the database
About this Guide
iv

•Inability to perform maintenance or recovery operations
•Inability to provide any required critical or major trouble notification
•Any other problem severely affecting service, capacity, traffic, and billing.
Maintenance capabilities may be defined as critical by prior discussion and
agreement with the Tekelec Customer Care Center.
About this Guide
v

Revision History
Table 1 Revision history table
Date Change
June 2019 •Initial Release
October 2019 •Oracle Branding change
March 2020 •Adds ILOM Snapshot setup and capture
procedure
•Adds Creating bootable USB drive (on
Windows and Linux) procedure
•Adds Booting with USB drive procedure
Revision History
vi

1
Oracle Talari D6000 Hardware Guide
The following sections explain how to use your Oracle Talari D6000
Hardware and Software Requirements
D6000 appliances have the following hardware and software requirements.
Hardware
D6000 appliances require a standard 19 inch (480 mm) 4-post rack for mounting.
Software
The Talari Web Console is supported in latest versions of the following web browsers:
•Microsoft IE9 - IE11
•Mozilla Firefox
•Google Chrome
Supported browsers must have cookies enabled.
Supported browsers must have JavaScript installed and enabled.
Display
A minimum screen resolution of 1024 x 960 or greater is recommended.
Overview
The D6000 is part of the D-series of Talari Appliances and intended for use in data
centers that demand high performance and physical resiliency. The D6000 supports
WAN Optimization and Easy 1st Install.
Figure 1-1 D6000
Talari APN Overview
Talari Networks is redefining WAN reliability and application performance with its
family of APN Appliances by aggregating and transforming affordable broadband links
to deliver business-class performance and reliability at consumer prices. Talari APN
Appliances (APNAs) are seamlessly added to existing networks to deliver more
1-1

bandwidth, reduced WAN operating expenses, and greater reliability than any existing
single-provider WAN.
Using our patented Adaptive Private Network technology, Talari’s solution combines
diverse, abundant, affordable IP bandwidth sources, and provides reliable, resilient
and high-quality connectivity between sites, insuring application continuity. Talari
APNAs deployed in the main office and remote offices provide a network of Conduits
between sites. Each Conduit is made of multiple WAN links and data transmitted
across the Conduits is controlled and optimized to use network resources available
across all WAN Links.
Front Panel Configuration
For more information on the front panel status indicators, please see the Oracle Server
X7-2 Service Manual.
Rear Panel Configuration
Table 1-1 Ports
1 10 Gigabit Ethernet short reach (SR) fiber
(Bypass pair with Port 2)
2 10 Gigabit Ethernet short reach (SR) fiber
(Bypass pair with Port 1)
3 10 Gigabit Ethernet short reach (SR) fiber
(Bypass pair with Port 4)
4 10 Gigabit Ethernet short reach (SR) fiber
(Bypass pair with Port 3)
5 Gigabit Ethernet copper (Bypass pair with Port
6)
6 Gigabit Ethernet copper (Bypass pair with Port
5)
7 Gigabit Ethernet copper (Bypass pair with Port
8)
8 Gigabit Ethernet copper (Bypass pair with Port
7)
MGT Dedicated network management port
9 1/10 Gigabit SFP+ (non-bypass)
10 1/10 Gigabit SFP+ (non-bypass)
Chapter 1
Front Panel Configuration
1-2

Table 1-1 (Cont.) Ports
Console RJ45 console port (115200/8-N-1). Used for
service and maintenance.
NIC Indicator Codes
All Ethernet ports on the D6000 have indicator lights for information on network activity
and link status.
Table 1-2 MGT
Indicator Location Color Meaning
Activity Left Green On: Link up
Off: No activity
Blinking: Packet
Activity
Link Speed Right Green Off: 10/100 Mbps
On: 1Gbps
Table 1-3 Ports 1 - 4
Indicator Location Color Meaning
Activity Above port Green Blinking: Packet
Activity
Table 1-4 Ports 5- 8
Indicator Location Color Meaning
Activity Left Green Off: No activity
Blinking: Packet
Activity
Link Speed Right Amber/Green Off: No activity/10
Mbps
Green: 100 Mbps
Amber: 1 Gbps
Table 1-5 Ports 9 - 10
Indicator Location Color Meaning
Activity Top Green Off: No activity
Blinking: Packet
Activity
Link Speed Bottom Amber Off: No activity
Amber: 10 Gbps
Chapter 1
NIC Indicator Codes
1-3

Hardware Specifications
The D6000 has the following hardware specifications.
Power Redundant 1200 watt power supply
100-240V
50-60 Hz
Estimated BTU Per Hour Active idle: 618 BTU/hr
50% Workload: 1140 BTU/hr
90% Workload: 1559 BTU/hr
Physical Dimensions Height 1.68” (42.6mm)
Width 18.9” (482mm)
Depth 29.02” (737mm)
Gross Weight 40 lbs (18.1kg)
Mounting Options Rack mount, rail kit (included)
System LEDs See Oracle Server X7-2 Service Manual
Link LEDs Link activity
Link speed
Operating Temperature 41°F to 95°F (5° to 35°C)
Storage Temperature -40°F to 154°F (-40°C to 68°C)
Humidity Range 10% to 90% (non-condensing) operating
environment
Network Data Interfaces 8 Gigabit Ethernet Fail-To-Wire Ports
2 1/10-Gigabit Ethernet SFP+ Ports
Other interfaces 1 Gigabit Ethernet Management Port
1 USB 3.0 port
1 RJ-45 Console Port
Installing the Talari Appliance
Rack Mounting
Prior to installing the device, adhere to the following installation guidelines:
•Ensure that there is adequate airflow in the rack. Restricted airflow can damage
the equipment.
•Leave at least 1U of vertical space between each device installed in the rack.
•The rack width and depth should allow for proper serviceability and cable
management.
•Ensure the rack is properly secured to the floor or ceiling.
•Ensure the rack is properly grounded.
•Ensure the installer is properly grounded and wearing appropriate safety
equipment.
•Always load the rack from the bottom up.
Chapter 1
Hardware Specifications
1-4

•Load the heaviest devices in the rack first.
•Make sure the rack is level and stable before pulling a device out of the rack.
•Do not move racks by yourself; at least two people are recommended to move a
rack.
•Cables should be easily identifiable.
Please refer to the Oracle® Servers X7-2 and X7-2L Installation Guide for additional
appliance specifications and detailed rackmounting instructions: https://
docs.oracle.com/cd/E72435_01/html/E72440/index.html.
LAN/WAN Connections
When connecting each Ethernet cable (LAN, WAN) to the appropriate connector on
the D6000.
•Position the cables carefully, so that they do not put strain on the connectors.
•Organize cables in bundles such that cables do not intertwine.
•Inspect the cables to make sure that the routing and bend radii are satisfactory.
Reposition cables, if necessary.
•Install cable ties in accordance with site requirements.
Cabling and Bypass Mode
If your Talari appliance is operating in bypass mode, logic used by the appliance
represents the functionality provided by a crossover cable. This may cause a loss of
the link between the Talari appliance and older network devices that do not support
Auto-MDIX when straight-through cables are used to connect the LAN and WAN ports
of the Talari appliance. In such a case, a crossover cable is required from the Talari
WAN port to the network device.
If your network devices support Auto-MDIX capability, the link should be automatically
established when in bypass mode and there should be no need for crossover cables.
Talari recommends testing and verifying this capability with the Talari appliance
powered off for proper operation.
For assistance, please contact your Talari representative, or the Talari Support team.
Powering Up the Appliance
When connecting power to the D6000:
•Plug the AC power cords into the appliance.
•Plug the AC power cords into an uninterrupted AC power source.
•The appliance will start automatically.
The D6000 uses 100 - 240 VAC.
Network Deployment Options
Before getting started, it is important to determine how the D6000 will be deployed.
Chapter 1
Powering Up the Appliance
1-5

Note:
When considering deployment options, please note that the bypass pairs will
default to Fail-To-Block until configured otherwise.
Example instructions for some of the most common deployment scenarios are
provided below:
Router (Gateway, Fail to Block)
The D6000 is deployed as the WAN gateway for the site, and bypass pair is
configured as Fail-To-Block. Use this option if you plan to use the Talari Appliance as
the edge device for the site.
Layer 2 Fail-To-Wire (Overlay)
The D6000 is deployed on the LAN side of the gateway, and bypass pair is configured
as Fail-To-Wire. Use this option if you prefer to retain existing edge devices or plan to
install an alternative edge device on the WAN side of the Talari Appliance.
MPLS & Internet Hybrid
The D6000 is deployed as an overlay for MPLS while performing routing/firewall
capabilities for internet links. Use this option if recommended by your Sales Architect,
or if you have an MPLS/Internet hybrid network and will not be using the CE Router
Replacement functionality of Oracle SD-WAN Edge.
Other Options
There are other deployment options, and our Talari Implementation team members will
assist you with planning and deploying your new appliance.
Installation Option: Easy 1st Install
For use with D6000 as a Router (Gateway, Fail to Block), Layer 2 Fail to Wire
(Overlay), MPLS & Internet Hybrid.
Easy 1st Install Site Deployment Criteria
NCN:
•Easy 1st Install can be used once the Network Control Node (NCN) has been set
up for your network.
•Active Appliance Package: The NCN must be running an active configuration
which includes the D6000 for the site being installed.
Client Side Connectivity:
•Internet, DHCP, and DNS connectivity to the management interface are required
to use Easy 1st Install. If one or more are not available, please see the instructions
for manual installation. If the management interface is connected to the LAN
segment, communication with the public Internet will be blocked and Easy 1st
Install will fail.
Chapter 1
Installation Option: Easy 1st Install
1-6

•Cable the LAN and WAN ports in accordance with the Talari configuration for the
site.
Use NCN to Upload Client Package to Registration Server
1. Log in to the Web Console of the NCN.
2. Navigate to Configuration > Easy Install.
3. Locate the Site name of the D6000 being deployed.
4. Click the Edit pencil to open the Set Serial Number window.
5. Enter the serial number of the D6000 being deployed and click the Set Serial
Number button.
The serial number may be found on the top of the D6000 above the left-hand drive
bays.
6. Observe the Upload/Activate column. Click the Upload/Activate text when it
appears.
7. Continue to observe the Upload/Activate column. Once the text reads Upload
Complete, proceed to the next section.
Deploy the Talari Appliance
1. Cable the D6000 with the provided cables.
2. Ensure that the appliance management interface is cabled for Internet
connectivity.
3. Connect the power cords to the D6000. Connect the other ends to an
appropriately grounded power source. The D6000 will power on automatically.
4. The D6000 will begin the Easy 1st Install process. Please allow up to ten minutes
for the process to complete. (From the NCN Web Console, observe the
Configuration > Easy Install page for status updates during installation.)
5. Once the Easy 1st Install process has completed, the Talari service will
automatically be enabled.
6. To access the Management IP address of the D6000 via the conduit after
deployment is complete, move the blue management cable to the LAN switch.
Installation Option: Manual Install
For use with D6000 as a Router (Gateway, Fail to Block), Layer 2 Fail to Wire
(Overlay), MPLS and Internet Hybrid
Manual Install Site Deployment Criteria
Manual (Legacy) Install requires physical access to the appliance. The end user will
require a PC which can be connected to the console port of the Talari Appliance. The
console port connects the user to the Oracle ILOM command line interface. Cable
management, LAN, and WAN ports according to the Talari configuration for site.
Pre-Deployment Requirements
The network administrator must have an active configuration which includes a client
package for this site running on the NCN. An appropriate IP address, subnet mask,
Chapter 1
Installation Option: Manual Install
1-7

and gateway for the management interface should be provided for the on-site user to
configure.
If the network administrator will have access to the new appliance once an on-site user
configures the management interface, proceed to step 10 of Deploying the Talari
Appliance. If not, the on-site user will require the client package from the running
configuration:
1. From the Web Console of the NCN, navigate to Manage Network, and then
Change Management.
2. Download the active package for the new client site.
3. Send the zipped client package to the on-site user who will be deploying the
appliance.
Deploying the Talari Appliance
1. Connect the power cords to the D6000. Connect the other ends to an
appropriately grounded power source. The D6000 will power on automatically.
2. Connect the PC directly to the console port of the D6000 and console into the
appliance using a bit rate of 115200/8-N-1.
3. Log in to Oracle ILOM as an Administrator. To enable first time login and access to
Oracle ILOM, a default Administrator account and its password are provided with
the system. To build a secure environment, change the default password
(Welcome1) for the default Administrator account (root) after your initial login. You
may change the password using the command "set /SP/users/root/ password".*
4. Enter the command "start /HOST/console", confirm, and hit enter again to access
the Talari console.
5. Log in to the appliance via the command line. To enable first time login and access
to the Talari appliance, a default administrator account and its password are
provided with the system. To build a secure environment, change the default
password (talari) for the default Administrator account (talariuser) after your initial
login.
6. Enter the command "tcon" and wait for the prompt to return.
7. Enter the command "management_ip".
8. Stage the IP Address, Subnet Mask, and Gateway IP Address for the Talari as
provided by the network administrator using the command "set interface <ip
address> <subnet mask> <gateway>". Review the staged settings, then enter the
"apply" command to activate.
9. Disconnect from the console. If the network administrator will be configuring the
appliance, no further action is required.
10. To apply the configuration package, navigate to the Talari management IP in a
web browser and log in to the Talari web console using the credentials given
above. Select Configuration > Local Change Management from the left-hand
menu.
11. Click Browse and select the .zip package provided by your network administrator,
then click Upload.
12. When the upload is complete, click Next to proceed to activation.
13. Click Activate Staged to complete the process.
Chapter 1
Installation Option: Manual Install
1-8

14. Once the activation process is complete, navigate to Manage Appliance > Enable/
Disable Services and enable the Talari service.
Collecting ILOM Diagnostics for D2000 and D6000
Enabling ILOM on your D2000 or D6000 appliance provides hardware support at the
component level by means of an ILOM snapshot. Oracle's technical support center
can analyze the snapshots and access data such as FMA reports to determine which
components require replacement in a fault situation.
To enable ILOM snapshots on your appliance:
1. Sign into SD-WAN OS and sudo to root.
talariuser@NCN-d6000:~# sudo su
bash-4.2#
2. Verify that the ILOM-to-host interconnect is disabled by observing State:disabled.
bash-4.2# ilomconfig list interconnect
Interconnect
============
State: disabled
Type: USB Ethernet
SP Interconnect IP Address: 169.254.182.76
Host Interconnect IP Address: (none)
Interconnect Netmask: 255.255.255.0
SP Interconnect MAC Address: 02:21:28:57:47:16
Host Interconnect MAC Address: 02:21:28:57:47:17
3. Enable and verify ILOM-to-host interconnect.
bash-4.2# ilomconfig enable interconnect
Set 'state' to 'enabled'
Host-to-ILOM interconnect successfully configured.
bash-4.2# ilomconfig list interconnect
Interconnect
============
State: enabled
Type: USB Ethernet
SP Interconnect IP Address: 169.254.182.76
Host Interconnect IP Address: 169.254.182.77
Interconnect Netmask: 255.255.255.0
SP Interconnect MAC Address: 02:21:28:57:47:16
Host Interconnect MAC Address: 02:21:28:57:47:17
Chapter 1
Collecting ILOM Diagnostics for D2000 and D6000
1-9

Note:
In this example:
•The Host address is 169.254.182.77
•The ILOM address is 169.254.182.76
4. Verify that you can ping the ILOM interface.
bash-4.2# ping 169.254.182.76
PING 169.254.182.76 (169.254.182.76) 56(84) bytes of data.
64 bytes from 169.254.182.76: icmp_seq=1 ttl=64 time=0.323 ms
64 bytes from 169.254.182.76: icmp_seq=2 ttl=64 time=0.218 ms
5. Enable higher layer IP protocols.
bash-4.2# ipmitool sunoem cli "set /SP/network/interconnect
allowed_services=fault-transport,http,https,ipmi,snmp,ssh"
Connected. Use ^D to exit.
-> set /SP/network/interconnect allowed_services=fault-
transport,http,https,ipmi,snmp,ssh
Set 'allowed_services' to 'fault-transport,http,https,ipmi,snmp,ssh'
[fault-transport, http, https, ipmi, ssh, snmp]
-> Session closed
Disconnected
6. Set the snapshot type to normal.
bash-4.2# ipmitool sunoem cli "set /SP/diag/snapshot dataset=normal"
Connected. Use ^D to exit.
-> set /SP/diag/snapshot dataset=normal
Set 'dataset' to 'normal'
-> Session closed
Disconnected
7. Sign into ILOM again.
bash-4.2# ssh [email protected]
Password: *******
Oracle(R) Integrated Lights Out Manager
Version 4.0.4.33 r128860
Copyright (c) 2019, Oracle and/or its affiliates. All rights reserved.
Warning: password is set to factory default.
Warning: HTTPS certificate is set to factory default.
Hostname: ORACLESP-1907XC3025
->
Chapter 1
Collecting ILOM Diagnostics for D2000 and D6000
1-10

8. In one command, initiate Snapshot and transfer the file to /tmp on host with the
talariuser login credentials.
-> set /SP/diag/snapshot dump_uri=sftp://[email protected]/tmp
Enter remote user password: ********* // Enter talariuser password
Set 'dump_uri' to 'sftp://[email protected]/tmp'
-> show /SP/diag/snapshot result
/SP/diag/snapshot
Properties:
result = Running
The process will take about 10 minutes to complete.
9. You may reissue this show command to check the status. When the result
changes from Running to Complete, exit the shell back to the host
-> show /SP/diag/snapshot result
/SP/diag/snapshot
Properties:
result = Collecting data into sftp://
[email protected]/tmp/
ORACLESP-1907XC3025_1907XC3025_2020-03-02T17-50-08.zip
Snapshot Complete.
Done.
-> exit
Connection to 169.254.182.76 closed.
bash-4.2#
The zip file will be in /tmp .
bash-4.2# ls -l /tmp/*.zip
-rw-r--r-- 1 talariuser talariuser 17879551 Mar 2 14:00 /tmp/
ORACLESP-1907XC3025_1907XC3025_2020-03-02T17-50-08.zip
bash-4.2#
10. Validate the .zip file.
bash-4.2# unzip -tq /tmp/
ORACLESP-1907XC3025_1907XC3025_2020-03-02T17-50-08.zip
No errors detected in compressed data of /tmp/
ORACLESP-1907XC3025_1907XC3025_2020-03-02T17-50-08.zip.
11. Disable the interconnect.
bash-4.2# ilomconfig disable interconnect
Set 'state' to 'disabled'
Chapter 1
Collecting ILOM Diagnostics for D2000 and D6000
1-11

Creating a Bootable USB Drive on Linux
Before starting this process, ensure that the capacity of your USB drive is at least 4
GB.
To create a bootable USB drive on Linux:
1. Download the D2000 or D6000 image from MOS.
2. Copy the image on the USB drive.
Doing this destroys all existing data on the USB drive.
3. Insert the USB drive into the computer and run the
dmesg|tail command.
[4317966.832947] usb 4-1: new SuperSpeed USB device number 39 using
xhci_hcd
[4317966.845892] usb 4-1: New USB device found, idVendor=0951,
idProduct=1666
[4317966.845893] usb 4-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[4317966.845894] usb 4-1: Product: DataTraveler 3.0
[4317966.845895] usb 4-1: Manufacturer: Kingston
[4317966.845896] usb 4-1: SerialNumber: E0D55EA57419E3C139680956
[4317966.848319] usb-storage 4-1:1.0: USB Mass Storage device detected
[4317966.848421] scsi host6: usb-storage 4-1:1.0
[4317967.863955] scsi 6:0:0:0: Direct-Access Kingston DataTraveler
3.0 PMAP PQ: 0 ANSI: 6
[4317967.864524] sd 6:0:0:0: Attached scsi generic sg4 type 0
[4317967.864606] sd 6:0:0:0: [sdd] 60604416 512-byte logical blocks:
(31.0 GB/28.9 GiB)
[4317967.864790] sd 6:0:0:0: [sdd] Write Protect is off
[4317967.864792] sd 6:0:0:0: [sdd] Mode Sense: 45 00 00 00
[4317967.864972] sd 6:0:0:0: [sdd] Write cache: disabled, read cache:
enabled, doesn't support DPO or FUA
4. In this case, the device name is "sdd" , and will be referenced by Linux as “/dev/
sdd” .
5. If Linux has been configured to auto-mount USB devices, unmount the partitions
on the drive. Run the “df” command to detect the status of the partitions of the
drive:
In this example, the second partition of /dev/sdd is mounted and must be
unmounted. In your case there may be no mounts on the USB or more.
df
Filesystem 1K-
blocks Used Available Use% Mounted on
devtmpfs
16416036 0 16416036 0% /dev
/dev/mapper/ol_lobi7u6-root 52403200
37842328 14560872 73% /
/dev/sda1 1038336
427060 611276 42% /boot
/dev/mapper/ol_lobi7u6-home 164415040
Chapter 1
Creating a Bootable USB Drive on Linux
1-12

112140980 52274060 69% /home
/dev/sdd2 2755604
2389404 222896 92% /run/media/oracle/USBBoot
6. To unmount the partition on the drive, run the command: umount /run/media/
oracle/USBBoot.
7. Run the df command again to make sure that there are no mounts matching your
USB device name ( /dev/sdd in the example.)
8. Insert the USB drive. At this point, the USB drive is ready to receive the image.
9. gunzip the downloaded USB raw image file.
gunzip
d6000v1_OS_7_0_1_0_0_GA_02282020_OS_52_GA_05022019_R8_2_1_0_0_GA_0128202
0.raw.gz
10. Burn the image, copy the USB raw image file to the USB device.
In the example, the USB device is identified as dev/sdd . This command requires
root access and is prefixed with “sudo”.
sudo cp
d6000v1_OS_7_0_1_0_0_GA_02282020_OS_52_GA_05022019_R8_2_1_0_0_GA_0128202
0.raw /dev/sdd
The USB burn process on a USB3 device can take 15 minutes. It may take a longer
time if the device or port is USB2. After the process is complete, you can remove the
USB. It is ready for use.
Creating a Bootable USB Drive on Windows
Before starting this process, ensure that the capacity of your USB drive is at least 4
GB.
To create a bootable USB drive on Windows:
1. Download the D2000 or D6000 image from MOS.
2. Download the Rufus tool. It is a standalone program and requires no installation
https://rufus.ie/.
3. Place the image on the USB drive. Doing this destroys all existing data on the
USB drive.
4. Run Rufus.
You will be prompted to allow administrator access.
5. Click Yes.
6. Click SELECT and choose the file that you downloaded from MOS. The
downloaded file is in compressed format (.gz). Do not uncompress it.
Chapter 1
Creating a Bootable USB Drive on Windows
1-13

7. Click Start.
You will be asked if it is OK to destroy all the data in the device.
8. Click Yes.
The USB burn process on a USB3 device can take 15 minutes. It may take longer if
the device or port is USB2. After the process is complete, you can remove the USB. It
is ready for use.
Booting with the USB Drive
Complete the following tasks to boot with the bootable USB drive.
See the following sections for how to create a bootable USB drive.
To boot the appliance using the bootable USB drive:
1. Connect to the serial port (#16 on back panel). It is configured at 115200 baud.
2. Insert the install USB drive into the rear of the unit (#15 on back panel).
Figure 1-2 Device Back Panel
Chapter 1
Booting with the USB Drive
1-14