This chapter describes the utilities available on Oracle Big Data Appliance. Most of the utilities are for monitoring the health of the hardware and the network.
Checks the health of a CDH cluster, including the software, hardware, and network, and logs the results in a file in the /tmp directory.
To also run the CDH cluster health checks, enter the Cloudera Manager admin password in response to the prompt. If you do not enter the password, then these checks are skipped.
Syntax
bdacheckcluster
Notes
If the cluster is protected by Kerberos authentication, then you must obtain a ticket for the hdfs user before running bdacheckcluster.
Example
This example shows the output from the utility:
# bdacheckcluster INFO: Logging results to /tmp/bdacheckcluster_1373393815/ Enter CM admin password to enable check for CM services and hosts Press ENTER twice to skip CM services and hosts checks Enter password: password Enter password again: password SUCCESS: Mammoth configuration file is valid. SUCCESS: hdfs is in good health SUCCESS: mapreduce is in good health SUCCESS: oozie is in good health SUCCESS: zookeeper is in good health SUCCESS: hive is in good health SUCCESS: hue is in good health SUCCESS: Cluster passed checks on all hadoop services health check SUCCESS: bda1node01.example.com is in good health SUCCESS: bda1node02.example.com is in good health SUCCESS: bda1node03.example.com is in good health . . . SUCCESS: Cluster passed checks on all hosts health check SUCCESS: All cluster host names are pingable SUCCESS: All cluster hosts passed checks on last reboot INFO: Starting cluster host hardware checks SUCCESS: All cluster hosts pass hardware checks INFO: Starting cluster host software checks SUCCESS: All cluster hosts pass software checks SUCCESS: All ILOM hosts are pingable SUCCESS: All client interface IPs are pingable SUCCESS: All admin eth0 interface IPs are pingable SUCCESS: All private Infiniband interface IPs are pingable SUCCESS: All cluster hosts resolve public hostnames to private IPs . . . INFO: Checking local reverse DNS resolve of private IPs on all cluster hosts SUCCESS: All cluster hosts resolve private IPs to public hostnames SUCCESS: 2 virtual NICs available on all cluster hosts SUCCESS: NTP service running on all cluster hosts SUCCESS: At least one valid NTP server accessible from all cluster servers. SUCCESS: Max clock drift of 0 seconds is within limits SUCCESS: Big Data Appliance cluster health checks succeeded
Checks the hardware profile of the server.
Syntax
bdacheckhw
Usage Notes
See "Configuring the Oracle Big Data Appliance Servers" for tips about using this utility.
Example
This example shows the output from the utility:
# bdacheckhw
SUCCESS: Found BDA v2 server : SUN FIRE X4270 M3
SUCCESS: Correct processor info : Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz
SUCCESS: Correct number of types of CPU : 1
SUCCESS: Correct number of CPU cores : 32
SUCCESS: Sufficient GB of memory (>=63): 63
SUCCESS: Correct BIOS vendor : American Megatrends Inc.
SUCCESS: Sufficient BIOS version (>=08080102): 18021300
SUCCESS: Recent enough BIOS release date (>=05/23/2011):06/19/2012
SUCCESS: Correct ILOM major version : 3.1.2.12
SUCCESS: Sufficient ILOM minor version (>=74388): 74388
SUCCESS: Correct number of fans : 4
SUCCESS: Correct fan 0 status : ok
SUCCESS: Correct fan 1 status : ok
.
.
.
SUCCESS: Big Data Appliance hardware validation checks succeeded
Checks the InfiniBand cabling between the servers and switches of a single rack, when entered with no options.
Run this command after connecting as root to any server.
Syntax
bdacheckib [parameter]
Parameters
The same as running without options except that the network must still be configured with the factory default settings. You can use this option as soon as Oracle Big Data Appliance arrives at the site, even before the switches are configured.
Verifies that the InfiniBand switch-to-switch cabling among multiple racks is correct. To create json_file, see the -g option.
Generates a sample JSON file named sample-multi-rack.json. Use this file as an example of the format required by the -m option.
Usage Notes
The network must be configured with custom settings as described by /opt/oracle/bda/network.json.
Examples
This example checks the switch-to-server InfiniBand cables:
[root@node01 network]# bdacheckib
LINK bda1sw-ib3.15A ... bda1node02.HCA-1.2 UP
LINK bda1sw-ib3.15B ... bda1node01.HCA-1.2 UP
LINK bda1sw-ib3.14A ... bda1node04.HCA-1.2 UP
LINK bda1sw-ib3.14B ... bda1node03.HCA-1.2 UP
.
.
.
The next example generates the JSON file and shows the output.
[root@bda1node01 bda]# bdacheckib -g [root@bda1node01 bda]# cat sample-multi-rack.json # This json multirack spec is generated. The array elements are sorted # alphabetically. A properly arranged json spec representing racks from left to right # can be used as input to bdacheckib (bdacheckib -m multi-rack.json) # Note commas separating rack elements are optional. [ {"SPINE_NAME": "bda1sw-ib1", "LEAF1_NAME": "bda1sw-ib2", "LEAF2_NAME": "bda1sw-ib3"} {"SPINE_NAME": "bda2sw-ib1", "LEAF1_NAME": "bda2sw-ib2", "LEAF2_NAME": "bda2sw-ib3"} {"SPINE_NAME": "dm01sw-ib1", "LEAF1_NAME": "dm01sw-ib2", "LEAF2_NAME": "dm01sw-ib3"}
The final example checks all the racks on the InfiniBand network using the edited JSON file created in the previous example:
# bdacheckib -m sample-multi-rack.json
Rack #1 leaf to spines topology check
leaf: bda1sw-ib2
expected 2 links to rack 1, found 4 OK
expected 2 links to rack 2, found 4 OK
expected 2 links to rack 3, found 3 OK
expected 2 links to rack 4, found 3 OK
leaf: bda1sw-ib3
expected 2 links to rack 1, found 3 OK
expected 2 links to rack 2, found 4 OK
expected 2 links to rack 3, found 3 OK
expected 2 links to rack 4, found 3 OK
.
.
.
Rack #1 cabling details
leaf: bda1sw-ib2
LINK ... to rack2 ......... UP
LINK ... to rack2 ......... UP
LINK ... to rack1 ......... UP
LINK ... to rack1 ......... UP
LINK ... to rack3 ......... UP
LINK ... to rack3 ......... UP
LINK ... to rack4 ......... UP
LINK ... to rack4 ......... UP
.
.
.
Checks whether the network configuration is working properly.
Syntax
bdachecknet
Usage Notes
Run this command after connecting as root to any server.
Example
This example shows the output from the utility:
[root@node01 network]# bdachecknet
bdachecknet: do basic sanity checks on /opt/oracle/bda/network.json
bdachecknet: warning: bda deploy /opt/oracle/bda/network.json check odd nr of elements 7
bdachecknet: passed
bdachecknet: checking for networkexpansion.json
bdachecknet: ping test private infiniband ips (bondib0 40gbs)
.
.
.
Checks the software profile of a server.
Syntax
bdachecksw
Usage Notes
See "Configuring the Oracle Big Data Appliance Servers" for tips about using this utility.
Example
This example shows the output from the utility:
# bdachecksw
SUCCESS: Correct OS disk s0 partition info : 1 ext3 raid 2 ext3 raid 3 linux-swap 4 ext3 primary
SUCCESS: Correct OS disk s1 partition info : 1 ext3 raid 2 ext3 raid 3 linux-swap 4 ext3 primary
SUCCESS: Correct data disk s2 partition info : 1 ext3 primary
SUCCESS: Correct data disk s3 partition info : 1 ext3 primary
SUCCESS: Correct data disk s4 partition info : 1 ext3 primary
SUCCESS: Correct data disk s5 partition info : 1 ext3 primary
SUCCESS: Correct data disk s6 partition info : 1 ext3 primary
SUCCESS: Correct data disk s7 partition info : 1 ext3 primary
SUCCESS: Correct data disk s8 partition info : 1 ext3 primary
SUCCESS: Correct data disk s9 partition info : 1 ext3 primary
SUCCESS: Correct data disk s10 partition info : 1 primary
SUCCESS: Correct data disk s11 partition info : 1 primary
SUCCESS: Correct software RAID info : /dev/md2 level=raid1 num-devices=2 /dev/md0 level=raid1 num-devices=2
SUCCESS: Correct mounted partitions : /dev/mapper/lvg1-lv1 /lv1 ext4 /dev/md0 /boot ext3 /dev/md2 / ext3 /dev/sd4 /u01 ext4 /dev/sd4 /u02 ext4 /dev/sd1 /u03 ext4 /dev/sd1 /u04 ext4 /dev/sd1 /u05 ext4 /dev/sd1 /u06 ext4 /dev/sd1 /u07 ext4 /dev/sd1 /u08 ext4 /dev/sd1 /u09 ext4 /dev/sd1 /u10 ext4
SUCCESS: Correct matching label and slot : symbolic link to `../../sda4'
SUCCESS: Correct matching label and slot : symbolic link to `../../sdb4'
.
.
.
SUCCESS: Correct Linux kernel version 2.6-39-400.200 series : Linux 2.6.39-400.2 14.3.el6uek.x86_64
SUCCESS: Correct Java Virtual Machine version : HotSpot(TM) 64-Bit Server 1.7.0_ 25
SUCCESS: Correct puppet version : 2.6.11
SUCCESS: Correct MySQL version : 5.5.35
SUCCESS: All required programs are accessible in $PATH
SUCCESS: All required RPMs are installed and valid
SUCCESS: Correct bda-monitor status : bda monitor is running
SUCCESS: Big Data Appliance software validation checks succeeded
Synchronizes the time of all servers in a cluster.
Syntax
bdaclustersynctime
Usage Notes
To use this utility, you must log in as root to the first server in the node. Passwordless ssh must also be set up for the cluster. See the -C parameter for "setup-root-ssh."
This utility creates a log file named bdaclustersynctime.log in the directory identified in the output.
Example
The following example successfully runs bdaclustersynctime:
# bdaclustersynctime
INFO: Logging results to /tmp/bdacluster_1373485952/
SUCCESS: Mammoth configuration file is valid.
SUCCESS: All cluster host names are pingable
SUCCESS: NTP service running on all cluster hosts
SUCCESS: At least one valid NTP server found
SUCCESS: No errors found syncing date and time on all nodes
SUCCESS: Max clock drift of 0 seconds is within limits
SUCCESS: Sync date and time of cluster succeeded
The Oracle Big Data Appliance Command-Line Interface (bdacli) queries various configuration files to return information about the rack, cluster, server, InfiniBand network, and software patches.
The bdacli utility also adds and removes patches and optional services. It can migrate critical services between critical nodes, and add and remove servers from a cluster.
The bdacli utility displays usage information if no parameters are included on the command line or the values are undefined.
Syntax
bdacli action [parameters]
Actions
Displays general usage information for bdacli, a list of actions, and a list of supported parameters for the getinfo action.
Adds or removes a software patch on Oracle Big Data Appliance that matches patch_number. You must log in as root to use add or remove.
Enables you to administer the nodes in a cluster in response to a failing server.Table 13-1 describes the parameters.
Table 13-1 bdacli admin_cluster parameters
| Parameter | Description |
|---|---|
|
|
Removes the specified node from the cluster and decommissions the server in Cloudera Manager. It also updates the Mammoth files. You can decommission a failing, noncritical node. Note that critical services on the node must be moved first. This parameter is for temporarily removing a node from a cluster for maintenance and is not a method to delete a node from a cluster. |
|
|
Removes the node from the list of decommissioned nodes, and recommissions the server in Cloudera Manager. Use this command after decommissioning and repairing a failing server. |
|
|
Moves the services from a critical node to a noncritical node, and decommissions the failing server in Cloudera Manager. You specify the name of the failing critical node, and the utility selects the noncritical node for the migration. When migration is complete, the new node has all of the functionality of the original critical node. You can only migrate a critical node, and should do so only when it is failing. Note: In Oracle Big Data Appliance 4.8, migration does not support Oracle Big Data SQL. If Oracle Big Data SQL is installed, disable it first, run the migration, and then re-enable Oracle Big Data SQL.Use |
|
|
Restores a server to the cluster as a noncritical node, and recommissions the server in Cloudera Manager. Use this command after migrating the services of a critical node and repairing the failing server. |
Enables or disables an optional software component on Oracle Big Data Appliance. You must log in as root to use enable or disable.
Table 13-2 describes the component parameters.
Table 13-2 bdacli enable or disable Service Parameters
| Parameter | Description |
|---|---|
|
|
Auto Service Request |
|
|
Oracle Audit Vault and Database Firewall plugin |
|
|
Oracle Big Data Connectors |
|
|
Oracle Big Data SQL |
|
|
Oracle Enterprise Manager Cloud Control agent |
|
|
Disable existing eCryptfs encryption. |
|
|
HDFS Transparent Encryption on the cluster. Respond Yes or No to a prompt to set up Key Trustee Servers on the BDA. If you respond No, you are further prompted for the addresses of the Active and Passive Key Trustee Servers, as well as the Key Trustee organization and authorization code. If you respond Yes, the Key Trustee Servers are set up on Oracle Big Data Appliance in a predetermined configuration. Kerberos is required. See Document 2111343.1 in My Oracle Support for important prerequisites and procedure details. After the initial configuration, starting/stopping the KMS/KTS servers can be done only through Cloudera Manager. Mammoth does not have direct access to edge nodes and therefore cannot set up or detect KMS services on these nodes. Customers can set up KMS services on edge nodes themselves. These must exist same cluster as the services that require access to the Key Trustee Servers. See Cloudera’s description of this architecture. |
|
|
Active Directory Kerberos. Also prompts the user to choose whether or not to enable the features Encrypt Hadoop Services and Encrypt HDFS Data Transport. The Note that there are important preliminary steps. See MOS (My Oracle Support) documents 2013585.1 and 2029378.1. |
|
|
MIT Kerberos. Also prompts the user to choose whether or not to enable the features Encrypt Hadoop Services and Encrypt HDFS Data Transport. The disable option disables these services as well as MIT Kerberos. This parameter does not control Active Directory Kerberos. See |
|
|
HTTPS for Cloudera Manager, Hue, and Oozie. There is no disable option. Kerberos is required. |
|
|
Encryption of data transfer between DataNodes and clients, and among DataNodes. Kerberos is required. |
|
|
HTTPS encryption and Kerberos authentication for HDFS and YARN, also enables encrypted web shuffling for YARN. Data spills to non-HFDS disk storage from Spark shuffle, MapReduce intermediate files, map and reduce operations, and Impala SQL are also encrypted. Kerberos is required. |
|
|
Apache Sentry authorization |
Note:
If HDFS Transparent Encryption is disabled, data stored in the HDFS Transparent Encryption zones in the cluster will remain encrypted and therefore inaccessible. To restore access to the data, re-enable HDFS Transparent Encryption using the same key provider.
Starts, stops, restarts, or returns the current status of a service on a cluster or a specific node.
Table 13-3 describes the service parameters.
Table 13-3 BDACLI start, stop, and restart Parameters
| Parameter | Description |
|---|---|
|
|
Oracle Big Data SQL on all nodes of the cluster |
|
|
Oracle Big Data SQL on a specified node of the cluster. Use |
Reconfigures the network (or networks) within the specified scope. The network configuration will set the IP addresses, subnets, domain and DNS. In the case of a virtual adapter such as client network or private network, the VNICs are deleted and recreated with the new IP addresses.
Requires root privileges.
Examples:
bdacli reset server admin_network bdacli reset cluster client_network bdacli reset cluster private_network bdacli reset server all_networks
Table 13-4 BDACLI reset Scope Parameters
| Scope Parameter | Description |
|---|---|
|
|
The action is performed for the node where the command is being executed. |
|
|
The action is performed for all the nodes in the cluster. |
|
|
The action is performed for all the nodes in the rack. |
Table 13-5 BDACLI reset Network Parameters
| Network Parameter | Description |
|---|---|
|
|
Reconfigures the admin network interface |
|
|
Reconfigures the client |
|
|
Reconfigures client |
|
|
Reconfigures all networks (admin, client and private) to what is specified in the corresponding network files. |
Returns a list of getinfo parameters. If you include a parameter name in the command, then getinfo returns information about that system component:
InfiniBand parameters: The bdacli command queries the InfiniBand fabric. See "InfiniBand Parameters".
Rack parameters: Describes a physical Oracle Big Data Appliance rack. The bdacli command queries the current network.json configuration file for the rack where the command executes. See "Rack Parameters".
Cluster parameters: Describes a logical Oracle Big Data Appliance cluster. The bdacli command queries the current config.json file for the Hadoop cluster where the command executes. See "Cluster Parameters".
Server parameters: Describes a server. The bdacli command queries the operating system of the server where the bdacli command executes. See "Server Parameters".
One-off patch parameters: Provides information about one-off patches. See "One-Off Patch Parameters".
Parameter names that end with an "s" return lists. Boolean parameters return a string of either true or false.
InfiniBand Parameters
Table 13-6 describes the InfiniBand parameters for bdacli getinfo.
Table 13-6 InfiniBand Parameters
| Parameter | Returns |
|---|---|
|
|
A list of all Oracle Big Data Appliance servers on the InfiniBand fabric. The list contains the unqualified client host names, which are sorted alphabetically. The list can include servers in multiple racks that are cabled together. |
|
|
Lists the switches on the InfiniBand fabric, including the switch name, Globally Unique Identifier (GUID), and type ( |
Rack Parameters
Table 13-7 describes the rack parameters for bdacli getinfo.
Table 13-7 Rack Parameters
| Parameter | Returns |
|---|---|
|
|
The administrative network domain name for the rack, such as |
|
|
The client network domain name for the rack, such as |
|
|
The IP addresses of the three InfiniBand switches in the rack in this order: spine switch, first leaf switch (upper), second leaf switch (lower) |
|
|
The unqualified names of the three InfiniBand switches in the rack in this order: spine switch, first leaf switch (upper), second leaf switch (lower). For example, bda1sw-ib1, bda1sw-ib2, and bda1sw-ib3. |
|
|
An ordered list of IP addresses of all Oracle ILOMs in the rack, starting with the lowest server |
|
|
An ordered list of host names of all Oracle ILOMs in the rack, such as bda1node01-ilom and bda1node02-ilom, starting with the lowest server |
|
|
The IP address of the Cisco Ethernet switch |
|
|
The host name of the Cisco Ethernet switch, such as bda1sw-ip |
|
|
The name of this rack, such as bda1 |
|
|
An ordered list of IP addresses of PDUs in the rack, starting with PDU-A |
|
|
An ordered list of unqualified names of PDUs in the rack, starting with PDU-A (such as bda1-pdua and bda1-pdub) |
|
|
The rack serial number |
|
|
An ordered list of IP addresses on the administrative network of all servers in the rack, starting with the lowest server |
|
|
An ordered list of host names on the administrative network of all servers in the rack (such as bda1node01-adm, bda1node02-adm, and so forth) starting with the lowest server |
|
|
An ordered list of IP addresses on the client network of all servers in the rack, starting with the lowest server |
|
|
An ordered list of host names on the client network of all servers in the rack (such as bda1node01, bda1node02, and so forth) starting with the lowest server |
|
|
A list of IP addresses for ILOM devices in the rack |
|
|
The unqualified names of the ILOM devices in the rack (such as bda1node01-priv, bda1node02-priv, and so forth) |
Cluster Parameters
The following tables describe the cluster parameters:
Table 13-8 describes the general cluster parameters for bdacli getinfo.
Table 13-8 General Cluster Parameters
| Parameter | Returns |
|---|---|
|
|
|
|
|
|
|
|
The version of Cloudera's Distribution including Apache Hadoop installed on this cluster, such as |
|
|
The Cloudera Manager address, including the server name and port number, such as |
|
|
The version of Cloudera Manager running on this cluster, such as |
|
|
|
|
|
The name of the cluster, such as |
|
|
The edition of Oracle NoSQL Database installed on this cluster ( |
|
|
The version of Oracle NoSQL Database installed on the cluster. |
|
|
The unqualified host name of the server that hosts the puppet master. The Mammoth utility was deployed from this host, and any reconfiguration of the cluster must be done while logged in to that server. |
|
|
The type of cluster, either |
|
|
The software version installed on this cluster by the Mammoth utility, such as 3.1.0. |
Table 13-9 describes the cluster parameters related to Oracle Big Data Connectors for bdacli getinfo.
Table 13-9 Oracle Big Data Connectors Status Parameters
| Parameter | Returns |
|---|---|
|
|
|
|
|
|
|
|
The version of Oracle Data Integrator agent installed on the cluster. |
|
|
The version of Oracle R Advanced Analytics for Hadoop installed on the cluster |
|
|
The version of Oracle Loader for Hadoop installed on the cluster |
|
|
The version of Oracle SQL Connector for HDFS installed on the cluster |
|
|
The version of Oracle XQuery for Hadoop installed on the cluster |
Table 13-10 describes the cluster network parameters for bdacli getinfo.
Table 13-10 Cluster Network Parameters
| Parameter | Returns |
|---|---|
|
|
A list of Each entry is on a separate line with three parts: the InfiniBand IP address, the full client host name, and the short client host name. |
|
|
An ordered list of IP addresses for the Oracle ILOMs in the servers, starting with the first node in the cluster |
|
|
A list of unqualified host names on the administrative network for the Oracle ILOMs in the servers, in order starting with the first server in the cluster |
|
|
The IP addresses on the client network of all nodes in this cluster |
|
|
The host names on the client network of all nodes in the cluster, such as |
Table 13-11 describes the cluster security parameters for bdacli getinfo.
Table 13-11 Cluster Security Parameters
| Parameter | Returns |
|---|---|
|
|
The name of the Oracle Audit Vault and Database Firewall administration user. Returns an error if Audit Vault is not configured for this cluster. |
|
|
|
|
|
The port number that the Audit Vault server listens on. Returns an error if Oracle Audit Vault and Database Firewall is not configured on this cluster. |
|
|
The IP address of the Audit Vault server. Returns an error if Oracle Audit Vault and Database Firewall is not configured on this cluster. |
|
|
The database service name for the Audit Vault server. Returns an error if Oracle Audit Vault and Database Firewall is not configured on this cluster. |
|
|
|
|
|
|
|
|
|
|
|
A list of key distribution center (KDC) hosts external to Oracle Big Data Appliance. Returns an error if Kerberos is not enabled. |
|
|
|
|
|
The Kerberos realm for the cluster. Returns an error if Kerberos is not enabled. |
|
|
|
Server Parameters
Table 13-12 describes the server parameters for bdacli getinfo.
Table 13-12 Server Parameters
| Parameter | Returns |
|---|---|
|
|
|
|
|
The name of this server on the client network, such as bda1node01. |
|
|
The version of Oracle Linux on this server, such as 6.4. |
One-Off Patch Parameters
Table 13-13 describes the one-off patch parameters for bdacli getinfo.
Table 13-13 One-Off Patch Parameters
| Parameter | Returns |
|---|---|
|
|
A list of valid patches available for installation. A valid patch has a directory under |
|
|
A list of patches already installed. An installed patch has a directory in both |
See Also
"Changing the Configuration of Optional Software" for more information about the optional services.
Examples
The following commands provide information about the optional software on the cluster:
# bdacli getinfo cluster_bdc_installed true # bdacli getinfo cluster_odi_version 11.1.1.7.0 # bdacli getinfo cluster_hdfs_encryption_enabled true
The following command lists all switches on the current InfiniBand fabric. In this example, three Oracle Big Data Appliance racks are on the fabric with the standard hardware configuration of one spine switch and two gateway switches each.
$ bdacli getinfo ib_switches
bda1sw-iba0 00:21:28:6c:c8:af:a0:a0 36P
bda1sw-ibb0 00:21:28:46:9e:3b:a0:a0 36P
bda1sw-ibs0 00:21:28:6c:c8:ae:a0:a0 36P
bda2sw-ib1 00:21:28:46:98:d3:a0:a0 36P
bda2sw-ib2 00:21:28:de:ae:4a:c0:a0 GTW
bda2sw-ib3 00:21:28:c3:70:9a:c0:a0 GTW
bda3sw-ib1 00:21:28:46:90:ee:a0:a0 36P
bda3sw-ib2 00:21:28:df:34:8a:c0:a0 GTW
bda3sw-ib3 00:21:28:df:0f:0a:c0:a0 GTW
bda4sw-ib1 00:21:28:e8:af:23:a0:a0 36P
bda4sw-ib2 00:10:e0:0c:48:a0:c0:a0 GTW
bda4sw-ib3 00:21:28:f4:82:ce:c0:a0 GTW
This example installs patch 1234:
$ bdacli add patch 1234
Uses network time protocol (NTP) to synchronize the time of all units in the cluster.
Syntax
bdaclustersynctime
Usage Notes
You must be logged in as the root user.
Example
The following example shows that the cluster is synchronized.
# bdaclustersynctime
INFO: Logging results to /tmp/bdacluster_1399300113/
SUCCESS: Mammoth configuration file is valid.
SUCCESS: All cluster host names are pingable
SUCCESS: NTP service running on all cluster hosts
SUCCESS: At least one valid NTP server found
SUCCESS: No errors found syncing date and time on all nodes
SUCCESS: Max clock drift of 0 seconds is within limits
SUCCESS: Sync date and time of cluster succeeded
Collects diagnostic information about an individual server for Oracle Support.
Syntax
bdadiag [parameter]
Parameters
Downloads diagnostics from Cloudera Manager. You must know the Cloudera Manager admin password to use this parameter.
Collects the output of a complete Hadoop Distributed File System (HDFS) fsck check.
Gathers ILOM data using ipmitool. You cannot use ilom in the same command as snapshot.
Collects Oracle OS Watcher logs, which include historical operating system performance and monitoring data. The output can consume several hundred megabytes of disk space.
Collects ILOM snapshot data over the network, and provides most useful output than the ilom option. You must know the server root password to use this parameter. You cannot use snapshot in the same command as ilom.
Return Value
The name of the compressed file in the /tmp directory where bdadiag stored the data. The file name has the form bdadiag_server-name_server-serial-number_date.tar.bz2.
The logs are organized in subdirectories, including the following:
asr ilom install messages net raid sysconfig
Usage Notes
You must be connected to the server as root.
The optional parameters instruct bdadiag to collect additional diagnostics. You can enter the options together on the command line to collect the most information.
You run bdadiag at the request of Oracle Support and associate it with an open Service Request (SR). See the Oracle Big Data Appliance Software User's Guide for details about providing diagnostics to Oracle Support.
Example
This example shows the basic output from the utility:
# bdadiag
Big Data Appliance Diagnostics Collection Tool v4.0.0
Gathering Linux information
Skipping ILOM collection. Use the ilom or snapshot options, or login to ILOM over the network and run Snapshot separately if necessary.
Generating diagnostics tarball and removing temp directory
===========================================================================
Done. The report files are bzip2 compressed in /tmp/bdadiag_bda1node0101_12 16FM5497_2014_01_18_06_49.tar.bz2
===========================================================================
The next example shows the additional output from the cm option.
# bdadiag cm Big Data Appliance Diagnostics Collection Tool v4.0.0 Getting Cloudera Manager Diagnostics Password for the Cloudera Manager admin user is needed Enter password: password Enter password again: password Passwords match Waiting for Cloudera Manager ... Succeeded. Output in : /opt/oracle/BDAMammoth/bdaconfig/tmp/cm_commands.out Collecting diagnostic data ... { "startTime" : "2014-09-07T14:18", "endTime" : "2014-09-06T14:18" } Succeeded. Output in : /opt/oracle/BDAMammoth/bdaconfig/tmp/cm_commands_collectD iagnosticData.out Command ID is 526 ..... Command 526 finished after 30 seconds Operation completed successfully Diagnostic data successfully collected Can be downloaded from URL http://bda1node03.example.com:7180/cmf/command/526/download Downloading diagnostic data ... Original Cloudera Manager Diagnostics Bundle Name : 3609df48-4930-11e1-9006-b8ac6f8061c1.cluster1.20140907-18-59.support-bundle.zip Data successfully downloaded and placed in /tmp/bdadiag_bda2node01_1408NM50AE_2014_09_07_14_18/3609df48-4930-11e1-9006-b8ac6f8061c1.AK00198532.cluster1.20140907-18-59.support-bundle.zip Gathering Linux information . . .
The next example shows the additional output from the snapshot option:
# bdadiag snapshot Big Data Appliance Diagnostics Collection Tool v4.0.0 Please enter Host OS root password required for snapshot: password Gathering Linux information Gathering ILOM Snapshot data - please be patient, this may take a long time snapshot running: Tue Sep 2 13:42:28 PDT 2014 snapshot running: Tue Sep 2 13:43:21 PDT 2014 snapshot running: Tue Sep 2 13:44:32 PDT 2014 snapshot running: Tue Sep 2 13:45:35 PDT 2014 snapshot running: Tue Sep 2 13:46:31 PDT 2014 snapshot running: Tue Sep 2 13:47:43 PDT 2014 snapshot running: Tue Sep 2 13:48:47 PDT 2014 Snapshot Collection completed. Generating diagnostics tarball and removing temp directory ============================================================================== Done. The report files are bzip2 compressed in /tmp/bdadiag_bda1node01_1143FMM06E_2014_09_02_14_40.tar.bz2 ==============================================================================
Creates a diagnostic bundle for the cluster.
Syntax
bdadiagcluster
Usage Notes
You must be logged in as the root user. To include the diagnostics provided by Cloudera Manager, you must provide the Cloudera Manager password twice when prompted for it.
Example
The following example creates a bundled zip file from the diagnostic zip files creates on the servers in a six-node cluster. It does not include the Cloudera Manager diagnostics.
# bdadiagcluster Enter CM admin password to run dumpcluster Press ENTER twice to skip CM services and hosts checks Enter password: Enter Enter password again: Enter INFO: Starting Big Data Appliance diagnose cluster at Mon May 5 07:34:03 2014 INFO: Logging results to /tmp/bdadiagcluster_1399300440.log SUCCESS: Created BDA diagcluster zipfile on node bda01node01 SUCCESS: Created BDA diagcluster zipfile on node bda01node02 SUCCESS: Created BDA diagcluster zipfile on node bda01node03 SUCCESS: Created BDA diagcluster zipfile on node bda01node04 SUCCESS: Created BDA diagcluster zipfile on node bda01node05 SUCCESS: Created BDA diagcluster zipfile on node bda01node06 SUCCESS: bdadiagcluster_1399300440.zip created INFO: Big Data Appliance diagnose cluster complete at Mon May 5 07:34:48 2014 INFO: Please get the Big Data Appliance cluster diagnostic bundle at /tmp/bdadiagcluster_1399300440.zip
Deploys the HDFS, MapReduce, and Hive client configuration files from Cloudera Manager.
Syntax
bdagetclientconfig
Usage Notes
You must be connected to the server as root.
To deploy a new client configuration to all nodes of the cluster, use the dcli -C command.
Example
This example shows the output from one node in the cluster:
# bdagetclientconfig
bdagetclientconfig : Download and deploy HDFS, Map-Reduce and Hive client configuration files
Logging to /tmp/bdagetclientconfig-1368541073.out
Downloading HDFS and Map-Reduce client configuration zipfile
Downloading Hive client configuration zipfile
Deploying HDFS, Map-Reduce and Hive client configurations
Successfully downloaded and deployed HDFS, Map-Reduce and Hive client configurations !
Returns information about an individual server.
If you need to contact Oracle Support about an issue with Cloudera's Distribution including Apache Hadoop, then run this command first.
Syntax
bdaid
Usage Notes
You must be connected to the server as root.
Example
This example shows the output from the utility:
# bdaid
Server Hostname : bda1node09
Rack Serial Number : AK00023713
Server Serial Number : 1137FMM06Y
Appliance Name : bda1
The client network bondeth0 and its slaves eth8 and eth9 .
The private network bondib0 and its slaves ib0 and ib1.
For releases Oracle Big Data Appliance 4.7 and greater, bdaibstatus replaces bdacheckvnics, which provided similar functionality.
Run this command after connecting as root to any server.
Syntax
bdaibstatus [-bsgpch]
Parameters
Brief. No heading.
Test the passive network interface also. Temporarily make each passive slave interface active, ping the gateway from the slave, and then return the slave to passive mode.
Bring down the primary interface if both of the following are true:
The primary interface is bad (fails to ping the gateway).
The non-primary interface is good (successfully pings the gateway).
This parameter includes an implicit -s.
Example
[root@node01 network]# bdaibstatus
host if status actv primary pkey
============== === ====== ==== ======== =======
bdanode01 ib0 up yes yes NO
bdanode01 ib1 up no no NO
host if status actv primary switch gw port ping gw vlan
============== === ====== ==== ======= ====================== ========= ======= ======
bdanode01 eth9 up yes yes bdasw-ib3 0A-ETH-1 yes N/A
Validates the hardware and software on a server by running bdacheckhw, and then bdachecksw.
Syntax
bdaimagevalidate [startup]
Parameters
Regenerates the bda_reboot_status and BDA_REBOOT_* files in /root, in addition to performing the validation checks. Use this parameter if the checks fail after restarting the server, such that either BDA_REBOOT_FAILED or BDA_REBOOT_WARNINGS exist, and the issue is resolved. Do not use this parameter for the initial set of checks, that is, if /root/bda_reboot_status does not exist.
Example
# bdaimagevalidate
SUCCESS: Found BDA v3 server : SUN SERVER X4-2L
SUCCESS: Correct processor info : Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz
SUCCESS: Correct number of types of CPU : 1
SUCCESS: Correct number of CPU cores : 32
SUCCESS: Sufficient GB of memory (>=63): 63
SUCCESS: Correct BIOS vendor : American Megatrends Inc.
SUCCESS: Sufficient BIOS version (>=08080102): 26010600
SUCCESS: Recent enough BIOS release date (>=05/23/2011):07/08/2013
SUCCESS: Correct ILOM major version : 3.1.2.32
SUCCESS: Sufficient ILOM minor version (>=82440): 82440
.
.
.
SUCCESS: Correct bda-monitor status : bda monitor is running
SUCCESS: Big Data Appliance software validation checks succeeded
SUCCESS: All Big Data Appliance validation checks succeeded
Displays the server name and IP address.
Syntax
bdanodedesc
Example
This example shows that the user is logged in to a BDA server named bda1node03 with an IP address of 192.168.40.61:
$ bdanodedesc
bda1node03 BDA 192.168.40.61 HCA-
Re-creates the virtual network interface cards (VNICs) for all servers in the rack and spreads them across the available 10 GbE ports.
Syntax
bdaredoclientnet
Usage Notes
Log in to server 1 and change to the /opt/oracle/bda/network directory to run this utility.
You must run this utility after changing the number of 10 GbE connections to a Sun Network QDR InfiniBand Gateway switch. See "Changing the Number of Connections to a Gateway Switch".
The bdaredoclientnet utility performs the following subset of tasks done by the networksetup-two script during the initial configuration of Oracle Big Data Appliance:
Verifies that the administrative network is working, the InfiniBand cabling is correct, and the InfiniBand switches are available
Determines how many 10 GbE connections are available and connects them to the InfiniBand Gateway switches
Deletes all VNICs and re-creates them
Connects to each server and updates the configuration files
Restarts the client network and verifies that it can connect to each server using the newly configured client network
Example
The following example shows the output from the bdaredoclientnet utility:
# cd /opt/oracle/bda/network # bdaredoclientnet bdaredoclientnet: do basic sanity checks on /opt/oracle/bda/network.json bdaredoclientnet: warning: bda deploy /opt/oracle/bda/network.json check odd nr of elements 7 bdaredoclientnet: passed bdaredoclientnet: checking for networkexpansion.json src/query_smp.c:196; umad (DR path slid 0; dlid 0; 0,1,13,34,20 Attr 0xff90:1) bad status 110; Connection timed out src/query_smp.c:196; umad (DR path slid 0; dlid 0; 0,1,13,31,20 Attr 0xff90:2) bad status 110; Connection timed out bdaredoclientnet: ping servers by name on admin network bdaredoclientnet: ping servers by name on admin network bdaredoclientnet: passed bdaredoclientnet: verify infiniband topology bdaredoclientnet: passed bdaredoclientnet: start setup client network (10gigE over Infiniband) bdaredoclientnet: ping both gtw leaf switches bdaredoclientnet: passed bdaredoclientnet: verify existence of gateway ports bdaredoclientnet: passed bdaredoclientnet: removing existing eoib setup for this server Shutting down interface bondeth0: [ OK ] Shutting down interface bondib0: [ OK ] Shutting down interface eth0: [ OK ] Shutting down loopback interface: [ OK ] Disabling IPv4 packet forwarding: net.ipv4.ip_forward = 0 [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface bondib0: [ OK ] Bringing up interface eth0: [ OK ] bdaredoclientnet: ping server ips on admin network bdaredoclientnet: passed bdaredoclientnet: ping servers by name on admin network bdaredoclientnet: passed bdaredoclientnet: test ssh server ips on admin network hello from bda1node02.example.com hello from bda1node03.example.com . . . bdaredoclientnet: passed bdaredoclientnet: check existence of default vlan for port 0A-ETH-1 on bda1sw-ib2 bdaredoclientnet: use existing default vlan for port 0A-ETH-1 on bda1sw-ib2 bdaredoclientnet: check existence of default vlan for port 0A-ETH-1 on bda1sw-ib3 bdaredoclientnet: use existing default vlan for port 0A-ETH-1 on bda1sw-ib3 bdaredoclientnet: passed bdaredoclientnet: apply eoib on each server bdaredoclientnet: wait a few seconds for the network to restart on 10.111.22.001 bdaredoclientnet: wait a few seconds for the network to restart on 10.111.22.002 . . . check and delete vNIC for bda1node02 on switch bda1sw-ib2 vNIC ID 757 deleted IO Adapter for vNIC deleted check and delete vNIC for bda1node02 on switch bda1sw-ib3 check and delete vNIC for bda1node02 on switch bda1sw-ib2 check and delete vNIC for bda1node02 on switch bda1sw-ib3 vNIC ID 707 deleted IO Adapter for vNIC deleted create vNIC eth9 bda1node02 on switch bda1sw-ib3 vNIC created create vNIC eth8 bda1node02 on switch bda1sw-ib2 vNIC created . . . bdaredoclientnet: ping server ips on client network bdaredoclientnet: passed bdaredoclientnet: test ssh server ips on client network hello from bda1node02.example.com hello from bda1node03.example.com . . . bdaredoclientnet: passed bdaredoclientnet: end setup client network
Returns the serial numbers and media access control (MAC) addresses for most components of the Oracle Big Data Appliance server that you are connected to.
Syntax
bdaserials
Example
This example shows the output from the utility:
# bdaserials
Rack serial number : AK00023713
System serial number : 1137FMM0BY
System UUID : 080020FF-FFFF-FFFF-FFFF-7E97D6282100
Motherboard serial number : 0338MSL-1131BA2194
Chassis serial number : 1137FMM0BY
Memory serial numbers : 87948175 87949173 87948163 8794816B 87948130 87948176
Infiniband HCA serial number : 1388FMH-1122501437
Disk controller serial number : SV11713731
Hard disk serial numbers :
SEAGATE ST32000SSSUN2.0T061A1125L6M89X
SEAGATE ST32000SSSUN2.0T061A1125L6LFH0
SEAGATE ST32000SSSUN2.0T061A1125L6M94J
SEAGATE ST32000SSSUN2.0T061A1125L6LLEZ
SEAGATE ST32000SSSUN2.0T061A1125L6M5S2
SEAGATE ST32000SSSUN2.0T061A1125L6LSD4
SEAGATE ST32000SSSUN2.0T061A1127L6M58L
SEAGATE ST32000SSSUN2.0T061A1127L6R40S
SEAGATE ST32000SSSUN2.0T061A1125L6M3WX
SEAGATE ST32000SSSUN2.0T061A1125L6M65D
SEAGATE ST32000SSSUN2.0T061A1127L6NW3K
SEAGATE ST32000SSSUN2.0T061A1127L6N4G1
MAC addresses :
bondeth0 Ethernet : CE:1B:4B:85:2A:63
bondib0 InfiniBand : 80:00:00:4A:FE:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00
bond0 Ethernet : 00:00:00:00:00:00
eth0 Ethernet : 00:21:28:E7:97:7E
eth1 Ethernet : 00:21:28:E7:97:7F
eth2 Ethernet : 00:21:28:E7:97:80
eth3 Ethernet : 00:21:28:E7:97:81
eth8 Ethernet : CE:1B:4B:85:2A:63
eth9 Ethernet : CE:1B:4C:85:2A:63
ib0 InfiniBand : 80:00:00:4A:FE:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00
ib1 InfiniBand : 80:00:00:4B:FE:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00
Turns off swapping by the operating system.
Syntax
bdaswapoff
Usage Notes
The bdaswapoff utility disables both swap partitions on a server, which disables all swapping by the operating system. This state persists when the server restarts; you must run bdaswapon to restore swapping. Swapping is turned off by default to improve performance and to allow high availability if a disk fails.
Use bdaswapoff instead of the Linux swapoff utility.
See Also
Example
This example turns off swapping:
# bdaswapoff #
Turns on paging and swapping by the operating system.
Syntax
bdaswapon
Usage Notes
Swapping is turned off by default to improve performance and the ability to recover from disk failure.
Use bdaswapon instead of the Linux swapon utility.
See Also
Example
This example turns on swapping:
# bdaswapon
Filename Type Size Used Priority
/dev/sda3 partition 12287992 0 1
/dev/sdb3 partition 12287992 0 1
Updates the firmware of a particular component of a server, such as a replacement disk drive.
Syntax
bdaupdatefw parameter
Parameters
Updates the LSI disk firmware for the specified disk (N). Each server has 12 disks, which are numbered from 0 to 11.
Specifies the file path to the firmware. If the path is omitted, then bdaupdatefw uses the default firmware for the specified component from /opt/oracle/bda/firmware.
Displays syntax and usage information for bdaupdatefw.
Updates the Oracle ILOM firmware.
Updates the LSI disk controller firmware.
Updates the firmware for the Mellanox host channel adapter (InfiniBand card).
Usage
This utility is typically run by Oracle field engineers when installing or replacing hardware components, which may not be factory-installed with a supported firmware version. During a software installation, Mammoth copies the currently supported firmware to Oracle Big Data Appliance. The bdaupdatefw command uses those files when they are needed to update the firmware of a server component.
You can update one firmware package in a single command. Thus, you can specify only one of the following parameters: -d, -i, -l, or -m.
Caution:
Only use the firmware provided in a Mammoth bundle. Do not attempt to install firmware downloaded from a third-party site. Doing so may result in the loss of warranty and support.
Examples
This example shows the output from a command to update the Oracle ILOM firmware. To perform the update, you must execute the ipmiflash command provided in the output.
# bdaupdatefw -i
[INFO:GENERAL] No firmware file specified. Using default firmware file - /opt/or
acle/bda/firmware/ILOM-3_2_0_r74388-Sun_Fire_X4270_M3.pkg
[INFO:GENERAL] Updating ILOM firmware with the firmware file /opt/oracle/bda/fir
mware/ILOM-3_2_0_r74388-Sun_Fire_X4270_M3.pkg
[INFO:GENERAL] Original version is: 3.1.2.12 r74388
[INFO:GENERAL]
[INFO:GENERAL] Please run the following command and enter the root password
[INFO:GENERAL] for the ILOM when requested
[INFO:GENERAL]
[INFO:GENERAL] Note that this command will shutdown the server after flashing.
[INFO:GENERAL] You will need to login to the ILOM to power on the server afterwa
rds.
[INFO:GENERAL]
[INFO:GENERAL] ipmiflash -v -I lanplus -H 10.133.46.218 -U root write /opt/oracl
e/bda/firmware/ILOM-3_1_2_12_r74388-Sun_Fire_X4270_M3.pkg
[INFO:GENERAL]
Lists all InfiniBand connections in the InfiniBand network.
Syntax
iblinkinfo
Usage Notes
Run this command as root from any server.
Example
This example shows two Oracle Big Data Appliances and one Oracle Exadata Database Machine on the InfiniBand network:
[root@bda1node01 network]# iblinkinfo
Switch 0x002128df348ac0a0 SUN IB QDR GW switch bda1sw-ib2 10.133.43.36:
149 1[ ] ==( 4X 10.0 Gbps Active/ LinkUp)==> 130 2[ ] "SUN IB QDR GW switch bda1sw-ib2 10.133...
149 2[ ] ==( 4X 10.0 Gbps Active/ LinkUp)==> 127 1[ ] "SUN IB QDR GW switch bda1sw-ib2 10.133...
149 3[ ] ==( 4X 10.0 Gbps Active/ LinkUp)==> 111 2[ ] "SUN IB QDR GW switch bda1sw-ib2 10.133...
149 4[ ] ==( 4X 10.0 Gbps Active/ LinkUp)==> 109 1[ ] "SUN IB QDR GW switch bda1sw-ib2 10.133...
149 5[ ] ==( 4X 10.0 Gbps Active/ LinkUp)==> 143 1[ ] "bda1node02 BDA 192.168.41.20 HCA-1" ( )
149 6[ ] ==( 4X 10.0 Gbps Active/ LinkUp)==> 137 1[ ] "bda1node01 BDA 192.168.41.19 HCA-1" ( )
149 7[ ] ==( 4X 10.0 Gbps Active/ LinkUp)==> 141 1[ ] "bda1node04 BDA 192.168.41.22 HCA-1" ( )
149 8[ ] ==( 4X 10.0 Gbps Active/ LinkUp)==> 123 1[ ] "bda1node03 BDA 192.168.41.21 HCA-1" ( )
149 9[ ] ==( 4X 10.0 Gbps Active/ LinkUp)==> 151 1[ ] "bda1node06 BDA 192.168.41.24 HCA-1" ( )
149 10[ ] ==( 4X 10.0 Gbps Active/ LinkUp)==> 112 1[ ] "bda1node05 BDA 192.168.41.23 HCA-1" ( )
149 11[ ] ==( 4X 10.0 Gbps Active/ LinkUp)==> 139 1[ ] "bda1node07 BDA 192.168.41.25 HCA-1" ( )
149 12[ ] ==( Down/Disabled)==> [ ] "" ( )
149 13[ ] ==( Down/Disabled)==> [ ] "" ( )
149 14[ ] ==( 4X 10.0 Gbps Active/ LinkUp)==> 85 9[ ] "SUN DCS 36P QDR dm01sw-ib1 10.133.40.203" ( )
149 15[ ] ==( Down/Disabled)==> [ ] "" ( )
.
.
.
Displays a history of operating system upgrades.
Syntax
imagehistory
Example
This example shows that the appliance was imaged with version 3.1.0 with an upgrade to 4.0.0
$ imagehistory
Big Data Appliance Image History
IMAGE_VERSION : 3.1.0
IMAGE_CREATION_DATE : Tue Jun 24 06:44:22 UTC 2014
IMAGING_START_DATE : Sat Aug 30 18:15:01 UTC 2014
IMAGING_END_DATE : Sat Aug 30 14:59:39 EDT 2014
DEPLOYMENT_VERSION : 4.0.0
DEPLOYMENT_START_DATE : Sat Aug 30 15:18:07 EDT 2014
DEPLOYMENT_END_DATE : Sat Aug 30 16:39:07 EDT 2014
Displays information about the Oracle Big Data Appliance operating system image currently running.
Syntax
imageinfo
Example
This example identifies the 4.0.0 image:
$ imageinfo
Big Data Appliance Image Info
IMAGE_CREATION_DATE : Sat Aug 30 13:55:26 EDT 2014
IMAGE_LABEL : BDA_MAIN_LINUX.X64_140829
IMAGE_VERSION : 4.0.0
LINUX_VERSION : Oracle Linux Server release 5.8
KERNEL_VERSION : 2.6.39-400.215.9.el5uek
BDA_RPM_VERSION : bda-4.0.0-1.el5
OFED_VERSION : OFED-IOV-1.5.5-2.0.0088
JDK_VERSION : jdk-1.7.0_65-fcs
HADOOP_VERSION : 2.3.0-cdh5.1.0
Shows the Ethernet bridge ports with active links.
Syntax
listlinkup
Usage Notes
Run this command after connecting as root to a Sun Network QDR InfiniBand Gateway switch.
Example
This example shows three active ports (0A-ETH-1, 0A-ETH-3, and 0A-ETH-4) out of the eight available ports on switch bda1sw-ib3:
[root@bda1sw-ib3 ~]# listlinkup | grep Bridge
Bridge-0 Port 0A-ETH-1 (Bridge-0-2) up (Enabled)
Bridge-0 Port 0A-ETH-2 (Bridge-0-2) down (Enabled)
Bridge-0 Port 0A-ETH-3 (Bridge-0-1) up (Enabled)
Bridge-0 Port 0A-ETH-4 (Bridge-0-1) up (Enabled)
Bridge-1 Port 1A-ETH-1 (Bridge-1-2) down (Enabled)
Bridge-1 Port 1A-ETH-2 (Bridge-1-2) down (Enabled)
Bridge-1 Port 1A-ETH-3 (Bridge-1-1) down (Enabled)
Bridge-1 Port 1A-ETH-4 (Bridge-1-1) down (Enabled)
Makes password-encrypted data accessible after the server is restarted. Until you run this utility and enter the correct password, the data is unreadable.
Syntax
mount_hadoop_dirs
Example
This example shows the prompt for entering the password:
$ mount_hadoop_dirs Enter password to mount Hadoop directories: password
Removes passwordless SSH previously established by the setup-root-ssh command.
Syntax
remove-root-ssh [-C | -c | -g | -j] [-p] remove-root-ssh -h
Parameters
Targets all servers in the cluster, using the list of servers in /opt/oracle/bda/cluster-hosts-infiniband.
Targets the servers specified as host1, host2, and so forth, on the command line.
Targets a user-defined set of servers listed in groupfile. You can enter either server names or IP addresses in the file, one per line.
Specifies the range of servers in a starter rack [1-6] or a starter rack with additional servers [1-12]. This parameter is required in the 2.2.x base image when the utility is used before network configuration.
Displays Help.
Specifies the root password on the command line.
Oracle recommends that you omit this parameter. You will be prompted to enter the password, which the utility does not display on your screen.
Usage Notes
You must know the root password to use this command.
If you do not specify the target servers, then remove-root-ssh uses all servers in the rack.
See Also
Example
This example shows passwordless SSH being removed:
# remove-root-ssh
calling /opt/oracle/bda/bin/dcli -c 192.168.42.37,192.168.42.38,192.168.42.39 --unkey
192.168.42.37: ssh key dropped
192.168.42.38: ssh key dropped
192.168.42.39: ssh key dropped
remove-root-ssh succeeded
Resets the boot order of the server to the factory defaults, as specified in the BIOS. By doing so, it clears any ILOM booting overrides.
Syntax
reset-boot-order
Example
The following example resets the boot order of the current server:
# reset-boot-order
Set Boot Device to none
Cleared ILOM boot override - Boot device: none
Found BDA v1 Hardware - setting boot order using biosconfig
Copyright (C) SUN Microsystems 2009.
BIOSconfig Utility Version 2.2.1
Build Date: Aug 24 2009
Build Time: 09:01:30
BIOSconfig Specification Version 2.4
Processing Input BIOS Data....
Success
Found USB device name : USB:02.82;01 Unigen PSA4000
.
.
.
BIOSconfig Specification Version 2.4
Processing Input BIOS Data....
Success
New BIOS boot order :
USB:02.82;01 Unigen PSA4000
RAID:Slot0.F0:(Bus 13 Dev 00)PCI RAID Adapter
PXE:IBA GE Slot 0100 v1331
PXE:IBA GE Slot 0101 v1331
PXE:IBA GE Slot 0700 v1331
PXE:IBA GE Slot 0701 v1331
Establishes passwordless SSH for the root user.
Syntax
setup-root-ssh [-C | -c | -g | -j] [-p] setup-root-ssh -h
Parameters
Targets all servers in the cluster, using the list of servers in /opt/oracle/bda/cluster-hosts-infiniband.
Targets the servers specified as host1, host2, and so forth, on the command line.
Targets a user-defined set of servers listed in groupfile. You can enter either server names or IP addresses in the file, one per line.
Specifies the range of servers in a starter rack [1-6] or a starter rack with additional servers [1-12]. This parameter is required in the 2.2.x base image when the utility is used before network configuration.
Displays Help.
Specifies the root password on the command line.
Oracle recommends that you omit this parameter. You will be prompted to enter the password, which the utility does not display on your screen.
Usage Notes
You must know the root password to use this command.
If you do not specify the target servers, then setup-root-ssh uses all servers in the rack.
See Also
Example
This example shows passwordless SSH being set up for root:
# setup-root-ssh Enter root password: password spawn /opt/oracle/bda/bin/dcli -c 192.168.42.37,192.168.42.38... -k root@192.168.42.37's password: root@192.168.42.38's password: . . . 192.168.42.37: ssh key added 192.168.42.38: ssh key added . . . setup-root-ssh succeeded
Shows the device location of an inserted USB drive as it is known to the operating system, such as /dev/sdn.
Syntax
showusb
Lists the VLANs configured on the switch.
Syntax
showvlan
Usage Notes
Run this command after connecting as root to a Sun Network QDR InfiniBand Gateway switch.
Example
This example shows the default VLAN, which has an ID of 0, on switch bda1sw-ib3:
# showvlan
Connector/LAG VLN PKEY
------------- --- ----
0A-ETH-1 0 ffff
0A-ETH-2 0 ffff
0A-ETH-3 0 ffff
0A-ETH-4 0 ffff
1A-ETH-1 0 ffff
1A-ETH-3 0 ffff
1A-ETH-4 0 ffff
Lists the virtual network interface cards (VNICs) created for the switch.
Syntax
showvnics
Usage Notes
Run this command after connecting as root to a Sun Network QDR InfiniBand Gateway switch.
Example
This example shows the VNICs created in a round-robin process for switch bda1sw-ib3:
# showvnics
ID STATE FLG IOA_GUID NODE IID MAC VLN PKEY GW
--- ----- --- ----------------- -------------------------------- ---- ----------------- --- ---- --------
561 UP N 0021280001CF4C23 bda1node13 BDA 192.168.41.31 0000 CE:4C:23:85:2B:0A NO ffff 0A-ETH-1
564 UP N 0021280001CF4C53 bda1node16 BDA 192.168.41.34 0000 CE:4C:53:85:2B:0D NO ffff 0A-ETH-1
567 UP N 0021280001CF4B58 bda1node01 BDA 192.168.41.19 0000 CE:4B:58:85:2A:FC NO ffff 0A-ETH-1
555 UP N 0021280001CF2A5C bda1node07 BDA 192.168.41.25 0000 CE:2A:5C:85:2B:04 NO ffff 0A-ETH-1
552 UP N 0021280001CF4C74 bda1node04 BDA 192.168.41.22 0000 CE:4C:74:85:2B:01 NO ffff 0A-ETH-1
558 UP N 0021280001CF179B bda1node10 BDA 192.168.41.28 0000 CE:17:9B:85:2B:07 NO ffff 0A-ETH-1
.
.
.