Initial setup and configuration
In this chapter, we describe how to configure an IBM COS solution from the beginning to the point where you will be able to use the system with your application.
5.1 Information needed for installation
This section provides configuration steps for IBM COS appliances: Manager, Accesser and Slicestor. These steps will apply to both virtual Manager and Accesser appliances and physical Manager, Accesser and Slicestor appliances (nodes).
5.1.1 Required information
For installation and configuration the following information is required:
•Manager:
– Hostname
– Data channel information:
• Data channel IP address
• Data channel netmask address
• Data channel gateway address
– NTP (Network Time Protocol) servers
– DNS (Domain Name System) servers
•Accesser appliance:
– Hostname
– Data channel information:
• Data channel IP address
• Data channel netmask address
• Data channel gateway address
•Slicestor appliance:
– Hostname
– Data channel information:
• Data channel IP address
• Data channel netmask address
• Data channel gateway address
|
Important: It is possible for the Manager, Accesser, and Slicestor appliances to have different values for any of the information above. The specific information is based on your network location and physical locations.
|
5.1.2 Optional information
The following informational is optional and not required for all appliances:
•Maximum transmission unit (MTU) size for each network channel (defaults to 1500)
•Bonding requirements for all channels: requires Link Aggregation Control Protocol (LACP) enabled switch
– Bonding (Yes/No)
– Bonding type (Active-Active or Active-Passive)
•Management channel information:
– Management channel IP address
– Management channel netmask address
– Management channel gateway address
•Client channel information:
– Client channel IP Address
– Client channel netmask address
– Client channel gateway address
•Organization name
•Appliance location:
– City
– State
– County
•Intelligent Platform Management Interface (IPMI) information:
– IPMI IP address
– IPMI netmask address
– IPMI gateway address
|
Important: It is possible for the Manager, Accesser, and Slicestor appliances to have different values for any of the information above. The specific information is based on your network location and physical locations.
|
5.2 Example information
For the installation and configuration in the rest of this chapter, the following information is used:
•Manager:
– Hostname: icospdcman01
– Data channel information:
• Data channel IP address: 10.69.70.100
• Data channel netmask address: 255.255.255.0
• Data channel gateway address: 10.69.70.1
– NTP Server: 10.69.70.10
– DNS Server: 10.69.70.11
•Accesser appliance:
– Hostname: icospdcacc01
– Data channel information:
• Data channel IP address: 10.69.70.110
• Data channel netmask address: 255.255.255.0
• Data channel gateway address: 10.69.70.1
•Slicestor appliance:
– Hostname: icospdcsli01
– Data channel information:
• Data channel IP address: 10.69.70.130
• Data channel netmask address: 255.255.255.0
• Data channel gateway address: 10.69.70.1
This chapter does not cover the configuration of any of the optional information. More information about configuration can be found on IBM Knowledge Center for COS:
|
Note: You can select your current version of the IBM COS software on the top of the page (Change version or product).
|
5.3 Step 1: Installing the solution
This section discusses the steps for installing the solution.
5.3.1 Physical appliance
This section does not cover how to rack a physical appliance. More information about racking an appliance can be found on IBM Knowledge Center for COS:
You can select your current version of the IBM COS software on the top of the page (Change version or product). Then select the manual of the specific appliance that you need to rack.
5.3.2 Virtual appliance
This section does not cover how to import a virtual appliance into VMware. See “Deploy the OVA template” on page 62 for detailed information about how to import an Open Virtual Appliance (OVA).
5.3.3 Container appliance
This section does not cover how to install a container infrastructure or the installation and configuration of the Manager or Accesser container. See 4.6, “Appliance containers on Docker” on page 63 the for detailed information about how to accomplish this.
5.4 Step 2: Installing IBM Cloud Object Storage Appliance software
Installation of the IBM COS Appliance software requires console access to the appliance and the installation software.
|
Important: The term IBM COS appliance software and the term ClevOS are interchangeable. The term ClevOS is the original name of the appliance software and is still used in the IBM COS manuals at the following link:
|
Console access to the appliance is achieved by connecting a monitor and keyboard, KVM switch, or KVM device to the appropriate connections on rear of the appliance.
If IPMI is configured on the system, it is possible to connect to the appliance via the IPMI interface and open a console on the system.
The IBM COS appliance installation software is provided by IBM upon purchase of the software. Contact your sales team for a copy of the software. Complete the following steps:
1. For installation purposes the file you need is in the format:
clevos-a.bb.cc.ddd-allinone-usbiso.iso
where a.bb.cc.ddd references the specific version. Contact your sales team or IBM support to determine which version you should install. You want to make sure that you have the allinone-usbiso file. This contains the code for the Manager, Accesser, and Slicestor appliances on the same installation media.
|
Attention: Some IBM COS appliances come with the IBM COS appliance software preinstalled. Review the version that is preinstalled to determine its release date. If the preinstalled version is within 3 months of the version recommended by IBM support or sales, you can configure the IBM COS appliances without installing the recommended version. IBM advises you to upgrade to the recommended version before using the solution.
|
After obtaining the ISO installation media, copy the ISO file to a thumbdrive that is at least 8 GB large. This can be accomplished on your laptop or desktop computer with any image burning software. An open source imaging software, Balena Etcher (https://www.balena.io/etcher/), is available for Mac, Windows, and Linux, and is known to work with the IBM COS appliance software.
2. After connecting to the console and connecting the USB thumbdrive, you need to start the system from the USB thumbdrive. During the boot process, every time you see the white IBM splash screen, press F11. Eventually, you will be prompted with a blue startup screen with options. At the bottom of the list, choose the USB thumb drive to start from and press Enter.
3. You know you have selected the correct drive when you are presented with the following screen (Figure 5-1 on page 76).
Figure 5-1 IBM COS appliance installation boot screen
4. Next you are prompted with the following screen, as shown in Example 5-1.
Example 5-1 IBM COS appliance installation screen
*********************************************
IBM Cloud Object Storage System (r) Installer
*********************************************
#1. Perform automatic installation
#2. Perform manual installation
#3. Reboot
Choose Action: (1-3):
5. For an initial install, select 1 and press Enter.
6. Next, you are prompted for what type of install you want. See Example 5-2.
Example 5-2 IBM COS appliance installation erase disk choice
*********************************************
IBM Cloud Object Storage System (r) Installer
*********************************************
#1. OS Disk Only (Erase only OS disk and install)
#2. Factory Install (Erase all disks and install)
Choose Action: (1-2):
7. For an initial install, select 2 and press Enter.
You are prompted to erase all disks. On a Slicestor this includes all data disks. See Example 5-3.
Example 5-3 Erasing all the disks
WARNING: This option will erase all disks attached to the system.
Enter ‘erase’ (no quotes) to confirm. Other input will cancel:
8. For an initial install, type erase and press Enter.
You are prompted about which type of appliance you are installing. See Example 5-4.
Example 5-4 Choosing which appliance image to install
*********************************************
IBM Cloud Object Storage System (r) Installer
*********************************************
#1. CLEVOS-3.14.3.65-ACCESSER
#2. CLEVOS-3.14.3.65-MANAGER
#2. CLEVOS-3.14.3.65-SLICESTOR
Choose Action: (1-3):
9. Select 1, 2, or 3 (depending on which appliance you are on) and press Enter.
10. The installer then performs the following steps:
a. Partition and format drives
b. Copy files and verify integrity of the installation
c. Perform some other checks
d. Restart the appliance
11. After the appliance restarts, you see the BIOS screen. At that time, you can remove the USB thumbdrive.
12. Eventually, you see the boot screen, as shown in Figure 5-2.
Figure 5-2 IBM COS appliance boot screen
13. After the appliance completely starts, you see the following screen (Example 5-5):
Example 5-5 IBM COS appliance CLI login screen
IBM Cloud Object Storage
Appliance - ClevOS 3.14.3.65 tty1
Slicetor login:
The appliance has been completely installed.
5.5 Step 3: Appliance configuration
This section describes how to complete the initial configuration of the appliance after the installation of the IBM COS appliance software. The default username and password is the same for all appliances after the initial install. The default username is localadmin. The default password is password.
At the login prompt, type in the default username and password.
|
Important: SSH access is disabled by default on all IBM COS appliances. To enable SSH access to the appliance, change the default password for the user localadmin. IBM advises that you change the password as soon as possible.
|
5.5.1 Manager
Perform the following steps for the Manager configuration:
1. After logging into the Manager, you should see the following prompt (Example 5-6):
Example 5-6 Manager appliance default prompt
manager#
2. Next, run the port list command to determine which ethernet ports are available to you. See Example 5-7.
Example 5-7 Listing the available ports on the Manager
manager# port list
PORT ADDRESS MAX SPEED STATUS
eth0 d2:8a:ba:26:9c:86 Unknown disconnected
3. On your appliance, you see more than one port. The names of the port might be different as well. Identify which port your ethernet cable is connected to.
4. Next, type edit to begin configuring the appliance, and type all of the configuration information. See the output in Example 5-8.
Example 5-8 Setting the required information for a Manager
manager# edit
manager (working)# channel data port eth0
manager (working)# channel data ip 10.69.70.100
manager (working)# channel data netmask 255.255.255.0
manager (working)# channel data gateway 10.69.70.1
manager (working)# system hostname icospdcman01
manager (working)# system ntpservers 10.69.70.10
manager (working)# system dns 10.69.70.11
manager (working)#
5. Now, save and activate the appliance configuration, as shown in Example 5-9.
Example 5-9 Activating the Manager configuration
manager (working)# activate
Please wait, this may take a few minutes....
check OK
activate OK
icospdcman01#
6. The prompt changes to the hostname. If you do not receive any errors, you should be fine. You can test your network connection to see if you can ping the appliance’s gateway as shown in Example 5-10.
Example 5-10 Testing the Manager network configuration
icospdcman01# ping -c 10 10.69.70.1
PING 10 10.69.70.1 (10 10.69.70.1) 56(84) bytes of data.
64 bytes from 10 10.69.70.1: icmp_seq=1 ttl=64 time=0.255 ms
64 bytes from 10 10.69.70.1: icmp_seq=2 ttl=64 time=0.394 ms
64 bytes from 10 10.69.70.1: icmp_seq=3 ttl=64 time=0.345 ms
64 bytes from 10 10.69.70.1: icmp_seq=4 ttl=64 time=0.417 ms
64 bytes from 10 10.69.70.1: icmp_seq=5 ttl=64 time=1.03 ms
64 bytes from 10 10.69.70.1: icmp_seq=6 ttl=64 time=11.7 ms
64 bytes from 10 10.69.70.1: icmp_seq=7 ttl=64 time=1.9 ms
64 bytes from 10 10.69.70.1: icmp_seq=8 ttl=64 time=0.615 ms
64 bytes from 10 10.69.70.1: icmp_seq=9 ttl=64 time=0.400 ms
64 bytes from 10 10.69.70.1: icmp_seq=10 ttl=64 time=0.398 ms
--- 10 10.69.70.1 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9133ms
rtt min/avg/max/mdev - 0.255/1.752/11.764/3.370 ms
7. Now you can proceed to configure the Accesser and Slicestor appliances.
5.5.2 Accesser
Perform the following steps for the Accesser appliance configuration:
1. After logging into the Accesser appliance, you should see the following prompt (Example 5-11):
Example 5-11 Accesser appliance default prompt
accesser#
2. Run the port list command to determine which ethernet ports are available to you. See Example 5-12.
Example 5-12 Listing the available ports on an Accesser appliance
accesser# port list
PORT ADDRESS MAX SPEED STATUS
eth0 d2:8a:ba:26:9c:86 Unknown disconnected
3. On your appliance, you see more than one port. The names of the port might be different as well. Identify which port your ethernet cable is connected to.
4. Type edit to begin configuring the appliance, and type all of the configuration information. See Example 5-13.
Example 5-13 Setting the required information for an Accesser appliance
accesser# edit
accesser (working)# channel data port eth0
accesser (working)# channel data ip 10.69.70.110
accesser (working)# channel data netmask 255.255.255.0
accesser (working)# channel data gateway 10.69.70.1
accesser (working)# system hostname icospdcacc01
accesser (working)# system dns 10.69.70.11
accesser (working)# manager ip 10.69.70.100
ERROR: couldn’t retrieve manager certificate: curl returned exit code 7
Automatically accept the manager certificate when it is available? [y/N]: y
Enter prefix of manager fingerprint to verify (press enter to skip)
>
accesser (working)#
5. You see that curl returned an error attempting to retrieve the manager certificate. This is normal because you have not activated the network yet. Now, save and activate the appliance configuration. See Example 5-14.
Example 5-14 Activating the Accesser configuration
accesser (working)# activate
Please wait, this may take a few minutes....
check OK
activate OK
icospdcacc01#
6. Notice that the prompt has changed to the hostname. If you don’t receive any errors then you should be fine. You can test your network connection to see if you can ping the appliance’s gateway, as shown in Example 5-15.
Example 5-15 Testing the Accesser appliance network configuration
icospdcacc01# ping -c 10 10.69.70.1
PING 10 10.69.70.1 (10 10.69.70.1) 56(84) bytes of data.
64 bytes from 10 10.69.70.1: icmp_seq=1 ttl=64 time=0.255 ms
64 bytes from 10 10.69.70.1: icmp_seq=2 ttl=64 time=0.394 ms
64 bytes from 10 10.69.70.1: icmp_seq=3 ttl=64 time=0.345 ms
64 bytes from 10 10.69.70.1: icmp_seq=4 ttl=64 time=0.417 ms
64 bytes from 10 10.69.70.1: icmp_seq=5 ttl=64 time=1.03 ms
64 bytes from 10 10.69.70.1: icmp_seq=6 ttl=64 time=11.7 ms
64 bytes from 10 10.69.70.1: icmp_seq=7 ttl=64 time=1.9 ms
64 bytes from 10 10.69.70.1: icmp_seq=8 ttl=64 time=0.615 ms
64 bytes from 10 10.69.70.1: icmp_seq=9 ttl=64 time=0.400 ms
64 bytes from 10 10.69.70.1: icmp_seq=10 ttl=64 time=0.398 ms
--- 10 10.69.70.1 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9133ms
rtt min/avg/max/mdev - 0.255/1.752/11.764/3.370 ms
7. Now you can move on to configuring the rest of your Accesser and Slicestor appliances.
5.5.3 Slicestor
Perform the following steps for the Slicestor appliance configuration:
1. After logging into the Slicestor appliance, you should see the following prompt (Slicestor):
Example 5-16 Slicestor appliance default prompt
slicestor#
2. Run the port list command to determine which ethernet ports are available to you. See Example 5-17 on page 82.
Example 5-17 Listing the available ports on an Accesser appliance
slicestor# port list
PORT ADDRESS MAX SPEED STATUS
eth0 d2:8a:ba:26:9c:86 Unknown disconnected
3. On your appliance, you see more than one port. The names of the port might be different as well. Please identify which port your ethernet cable is connected to.
4. Type edit to begin configuring the appliance, and type all of the configuration information. See Example 5-18.
Example 5-18 Setting the required information for a Slicestor appliance
slicestor# edit
slicestor (working)# channel data port eth0
slicestor (working)# channel data ip 10.69.70.130
slicestor (working)# channel data netmask 255.255.255.0
slicestor (working)# channel data gateway 10.69.70.1
slicestor (working)# system hostname icospdcslc01
slicestor (working)# system dns 10.69.70.11
slicestor (working)# manager ip 10.69.70.100
ERROR: couldn’t retrieve manager certificate: curl returned exit code 7
Automatically accept the manager certificate when it is available? [y/N]: y
Enter prefix of manager fingerprint to verify (press enter to skip)
>
accesser (working)#
5. Notice that curl returned an error attempting to retrieve the manager certificate. This is normal because you have not activated the network yet. Now, save and activate the appliance configuration as shown in Example 5-19.
Example 5-19 Activating the Slicestor appliance configuration
slicestor (working)# activate
Please wait, this may take a few minutes....
check OK
activate OK
icospdcslc01#
6. Notice that the prompt has changed to the hostname. If you don’t receive any errors then you should be fine. You can test your network connection to see if you can ping the appliance’s gateway. See Example 5-20.
Example 5-20 Testing the Slicestor network configuration
icospdcslc01# ping -c 10 10.69.70.1
PING 10 10.69.70.1 (10 10.69.70.1) 56(84) bytes of data.
64 bytes from 10 10.69.70.1: icmp_seq=1 ttl=64 time=0.255 ms
64 bytes from 10 10.69.70.1: icmp_seq=2 ttl=64 time=0.394 ms
64 bytes from 10 10.69.70.1: icmp_seq=3 ttl=64 time=0.345 ms
64 bytes from 10 10.69.70.1: icmp_seq=4 ttl=64 time=0.417 ms
64 bytes from 10 10.69.70.1: icmp_seq=5 ttl=64 time=1.03 ms
64 bytes from 10 10.69.70.1: icmp_seq=6 ttl=64 time=11.7 ms
64 bytes from 10 10.69.70.1: icmp_seq=7 ttl=64 time=1.9 ms
64 bytes from 10 10.69.70.1: icmp_seq=8 ttl=64 time=0.615 ms
64 bytes from 10 10.69.70.1: icmp_seq=9 ttl=64 time=0.400 ms
64 bytes from 10 10.69.70.1: icmp_seq=10 ttl=64 time=0.398 ms
--- 10 10.69.70.1 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9133ms
rtt min/avg/max/mdev - 0.255/1.752/11.764/3.370 ms
7. Now you can move on to configuring the rest of your Accesser and Slicestor appliances.
5.6 Step 4 - Manager GUI configuration
After you have installed ClevOS on all of your appliances, you need to perform a GUI configuration. This GUI configuration is accomplished through the Manager GUI.
For the rest of the chapter, the following IBM COS environment, as shown in Figure 5-3, is assumed.
Figure 5-3 Example solution
5.6.1 Initial login
Perform the following steps for initial login:
1. Open a web browser and go to the Manager using the following URL:
https://icospdcman01
|
Tip: You can use either the IP address or the hostname to log into the Manager GUI. The hostname is only available if you have entered the hostname into your organization’s DNS server.
|
You are presented with the following screen (Figure 5-4).
Figure 5-4 Default HTTPS certificate error
2. You need to accept the default HTTPS certificate generated by IBM COS in order to continue.
|
Note: The steps regarding how to accept a user-generated certificate into a specific browser is out of the scope of this document. Refer to the documentation of your browser for information about how to do this.
|
3. After accepting the certificate you are presented with the login screen. See Figure 5-5.
Figure 5-5 Manager GUI login screen
4. Log into IBM COS using the default username and password.
|
NOTE: The default username is admin. The default password is password. You are prompted as part of the initial setup to change the password for the admin user. IBM recommends that you change the admin password.
|
5. Next you are presented with the End User License Agreement. See Figure 5-6.
Figure 5-6 Accept License Agreement
6. Select the box titled I have read and agreed to the terms provided in the IBM and non-IBM license agreements (required for acceptance).
7. Type your initials in the box to the right of Print Name (License Acceptor).
8. Click the Accept IBM & non-IBM Licenses button.
5.6.2 Creating a new system
The next step is create a new system:
Figure 5-7 Create a new system
Figure 5-8 Change administrator password
3. Choose a new password, confirm it, and select the Save and Continue button.
5.6.3 Creating a site
Next you will be prompted to create a site where you can place appliances. A site in IBM COS is a logical representation of a physical site. You can create additional sites later and move appliances between sites. See Figure 5-9.
Figure 5-9 Creating a site.
Type in the name of the site that you want to create and select the Finish button.
5.6.4 Accept pending devices
The next step is to accept all of the appliances that you have configured into the system:
1. At the top of the main screen, you should see the following prompt (Figure 5-10). Click the see below link.
Figure 5-10 Devices pending approval notification
2. Next you see a list of all devices pending. See Figure 5-11.
Figure 5-11 Devices pending approval
3. Select all of the devices and then click the Bulk Approve / Deny button.
|
Note: The number of pending appliances various from installation to installation and is based on your specific architecture. You need to make sure that the number of appliances that you installed and configured previously show up in this list.
|
4. Next you need to approve all of the devices. See Figure 5-12.
Figure 5-12 Bulk device registration
5. You need to assign the devices to a site. Select all of the appliances and assign them to the site you created previously. See Figure 5-13 on page 90.
Figure 5-13 Assign devices to a site
6. Next you can create an alias for each appliance. This is optional. See Figure 5-14.
Figure 5-14 Bulk device alias
7. Click the Save button.
5.6.5 Creating a storage pool
The next step is to create a storage pool.
Figure 5-15 Creating a storage pool
2. Complete the following substeps, as shown in Figure 5-16:
a. Type in the name of the storage pool in the box.
b. Select the width of the storage pool based on the IDA of the solution.
c. Always select Packed Storage.
d. Select all of the devices that should be part of the storage pool.
e. Click the Save button.
Figure 5-16 Naming a storage pool
5.6.6 Create vault
The next step is to create a vault:
1. From the main screen, click the Create Vault link.
Figure 5-17 Creating a vault
2. Next, type in your vault name in the box provided. Then set the Width, Threshold (Read Threshold), and Write Threshold based on the IDA that you have designed the system for.
3. For Options, leave the defaults.
4. For Quotas, leave the defaults.
5. For Advanced Index Settings, leave the defaults.
For more information on the IDA, please see the following website:
|
Attention: When running in CD mode, instead of setting a user-defined IDA, you are presented with two or more radio buttons, which enables you to choose between a system with better performance or a system with more storage available.
|
Figure 5-18 Create Standard Vault
5.6.7 Create access pool
The next step is to create an access pool:
Figure 5-19 Create Access Pool link
2. Next, type in the name of the vault in the box provided. Leave the API type as Cloud Object Storage. That is the default API and is compatible with the S3 API. See Figure 5-20.
Figure 5-20 Create New Access Pool screen
3. Next, select the box next to all of Accessers in your environment. This creates an Access pool for all Accessers. See Figure 5-21.
The access pool that was just created represents a many to many relationship between Accesser appliances and buckets. For more information about the access pool, see IBM Cloud Object Storage Concepts and Architecture: System Edition, REDP-5537.
Figure 5-21 Select Accessers for access pool
4. In the deployment section, select your storage pool, Standard Type for the Item Type, and check the box next to the vault that you created earlier, as shown in Figure 5-22.
Figure 5-22 Select deployment options for access pool
5. Click the Save button.
5.6.8 Enable Access Key Authentication
Enabling Access Key Authentication will enable an end user to use an Access Key and Secret Key to authenticate for vault access in IBM COS. This is the standard access for object storage in general:
1. From the main screen, select the Security tab. Then select the Configure button on the Vault Access Authentication bar. See Figure 5-23.
Figure 5-23 Configure Vault Access Authentication
2. Select the check box next to the Enable access key authentication and select the Update button. See Figure 5-24.
Figure 5-24 Enable Authentication Mechanisms
5.6.9 Creating a user
The next step is to create a user which can be used to store data in IBM COS:
1. From the main screen, select the Security tab.
Figure 5-25 Creating an account
3. In the General section, type in the Name of the user. This is the username that will be displayed in IBM COS. See Figure 5-26.
Figure 5-26 Name of user
4. In the Authentication section, clear the box. This will disable the user’s ability to authenticate with a username and password. See Figure 5-27.
Figure 5-27 Disable username and password authentication
5. In the Roles section, make sure that none of the check boxes are selected. If you select any box, you give the corresponding IBM COS roles to the user. For a user who needs only the ability to access the system for storage, none of these roles are required. See Figure 5-28.
Figure 5-28 Account roles
6. In the Vault Access section, you should be in the No Access tab. Select the box next to the vault that you created earlier and then select the Move to Read/Write button. This gives the user read and write access to the vault. See Figure 5-29.
Figure 5-29 User Vault Access
7. For the Device Access tab, make sure that the No Access buttons are selected.
8. For the Site Access tab, leave the defaults.
9. Select the Save button.
5.6.10 Generate Access Key ID
The next step is to generate an Access Key ID for the user to manage objects within IBM COS.
|
Note: The default authentication method for S3 is Access Key ID and Secret Key authentication.
|
1. From the main screen, select the Security tab.
2. From the Security tab, select the username of the account that you created.
Figure 5-30 Access Key Authentication
Figure 5-31 Generate Access Keys
5. A new Access Key ID and Secret Access Key have been generated. Record these for use later on.
6. You can exit out of this screen by selecting the IBM CLOUD OBJECT STORAGE text in the upper left hand corner of your web browser.
5.7 Step 5: Verify the solution
If you’ve successfully completed all of the steps in the previous section, you should have a fully functional IBM COS system with a vault created, and a user with the correct permissions to manage data in IBM COS.
5.7.1 Programs to verify and test IBM Cloud Object Storage
There are several open-source or free programs that you use to access IBM COS:
•Cyberduck - https://cyberduck.io/ (Available for Windows and Mac)
•S3 Browser - http://s3browser.com/ (Available for Windows)
•AWS CLI - https://aws.amazon.com/cli/ (Available for Windows, Mac, and Linux)
|
Important: Most free programs that are available to access IBM COS are bandwidth limited by design. Review the program to see if it limits bandwidth utilization. Do not use a free program that limits bandwidth utilization to test the performance of IBM COS. In the previous list, both Cyberduck and S3 Browser limit bandwidth utilization in the free version. The AWS CLI does not limit bandwidth utilization.
|
The rest of this document uses the AWS CLI on Linux to show how to access IBM COS from the command line.
Additionally, we use HTTP instead of HTTPS in this guide.
The instructions on how to install AWS CLI on your instance of Linux are not covered in this document. Instructions about how to install the AWS CLI can be found at the following link:
5.7.2 Configure AWS CLI
To configure the AWS CLI, complete the following steps:
1. Run the following command (Example 5-21).
Example 5-21 Configure the AWS CLI
[root@linux ~]# aws configure
AWS Access Key ID [None]: rQpHeqhFPPUMAazJbe3T
AWS Secret Access Key [None]: MJ2SepQvnXGoYKmHtnqKrZQWz79P0dWSJH1JNTzO
Default region name [None]:
Default output format [None]:
2. Type in the Access Key ID and Secret Access Key from the user you have already created.
3. Leave the Default region name blank. Leave the Default output format blank.
5.7.3 Uploading an object
To upload an object, run the following command using the IP address of an Accesser appliance and vault that you previously created. See Example 5-22.
Example 5-22 Uploading a file
[root@linux ~]# aws --endpoint-url http://10.69.70.110 s3 cp testfile s3://pdc_vault_01
upload: ./testfile to s3://pdc_vault_01/testfile
[root@linux ~]#
You have now uploaded the file testfile to IBM COS as an object. The manager GUI should now show that Raw Space and Usable Space have increased for your vault. The amount of increase will depend on the size of testfile.
|
Note: This command assumes that the testfile file already exists on your Linux server.
|
5.7.4 Listing objects
To list objects in your bucket, run the following command using the IP address of an Accesser appliance and vault that you have previously created. See Example 5-23.
Example 5-23 Listing objects in a bucket
[root@linux ~]# aws --endpoint-url http://10.69.70.110 s3 ls s3://pdc_vault_01
2019-05-01 16:42:30 1073741824 testfile
[root@linux ~]#
The output should list the object testfile.
5.7.5 Downloading an object
To download an object, run the following command using the IP address of an Accesser appliance and vault that you previously created. See Example 5-24.
Example 5-24 Downloading an object
[root@linux ~]# aws --endpoint-url http://10.69.70.110 s3 cp s3://pdc_vault_01/testfile testfile_new
download: s3://pdc_vault_01/testfile to ./testfile_new
[root@linux ~]#
You have now downloaded the object testfile in IBM COS to the file testfile_new on your Linux server.
|
Note: This command assumes that the testfile_new file did not previously exist on your Linux server.
|
5.7.6 Deleting an object
To delete an object in IBM COS, run the following command using the IP address of an Accesser appliance and vault that you previously created. See Example 5-25.
Example 5-25 Deleting an object
[root@linux ~]# aws --endpoint-url http://10.69.70.110 s3 rm s3://pdc_vault_01/testfile
delete: s3://pdc_vault_01/testfile
[root@linux ~]#
You have now deleted the object testfile in IBM COS. The manager GUI should now show that Raw Space and Usable Space have decreased for your vault. The amount of decrease depends on the size of testfile.
|
Note: The deletion of files in IBM COS can take a while to complete. The decrease of space might take some time to show up in the Manager GUI.
|
Additionally, you can list the objects in your vault using the previous list command to see if it is removed.
5.7.7 For more information
For more information, please see the AWS CLI S3 Developer Guide on IBM Knowledge Center for COS:
|
Note: You can select your current version of the IBM COS software on the top of the page (Change version or product).
|
5.8 Basic installation troubleshooting
The following sections contain some of the most common errors or issues that you might have during the installation and initial configuration of IBM COS.
5.8.1 Networking issues
Networking related issues are the most common cause of problems during an installation and configuration of IBMN COS. If one or more of your appliances is unable to communicate with IBM COS or any part of you network, it is almost always related to networking.
The basic networking rule of IBM COS is that the Manager needs to be able to communicate with every other appliance. The Slicestors need to communicate with every other appliance. Every Accesser needs to be able to communicate with every Slicestor and the Manager appliance.
If the appliance cannot communicate (for example, ping) with its gateway, check one or more of the following items:
•Network settings: Review the network settings that you have typed into the appliance. It is very easy to make a mistake in typing in the settings.
•Firewall: Verify that your network allows pings.
•Network cable: Verify that the network cable between the appliance and your network switch is connected and is valid.
•Network port: Verity that the network port(s) on the switch are on and active. Some switches require a manual configuration to become active and some do not.
•VLAN tagging: Make sure that VLAN tagging is turned off. IBM COS does not support VLAN tagging.
•Access ports: Ensure that all ports on the switch are defined as access ports.
•Switch configuration: If you are bonding more than one interface, verify that your switch supports LACP and that is has been configured correctly
If the appliance cannot communicate with appliances in remote sites, please check one or more of the following items:
•Verify that the local site and remote site can communicate and that it is enabled.
•Verify that the local site and remote site can ping each other.
•Verify that all of the correct firewall ports have been opened.
If the appliance does not show up in the Manager GUI as a pending device, please check one or more of the following items:
•Verify that you have set the Manager with the correct IP address from the command line.
•Ping the manager.
5.8.2 Installing IBM Cloud Object Storage
These are the kind of issues that you might see when you are trying to install IBM COS:
•Issue: You cannot boot from the USB key
– Answer: The USB key is not correctly installed with IBM COS. Reimage the USB key and try in another appliance.
– Answer: You need to press F11 when the IBM logo appears on the screen.
•Issue: The appliance boots with the wrong image (for example Slicestor appliance boots with Accesser the appliance image).
– Answer: Reinstall the appliance with the correct image.
5.8.3 Pending appliances
These are the kind of issues that you might see when you are accepting appliances into IBM COS:
•Issue: The appliance is rejected instead of being accepted into IBM COS
– Answer: You have to reinstall IBM COS on the appliance.
•Issue: The appliance is deleted instead of being accepted into IBM COS
– Answer: You have to reinstall IBM COS on the appliance.
•Issue: The appliances do not show up in the list of appliances to accept:
– Answer: This is usually caused by a network issue. Review the earlier section on Networking issues.
5.8.4 S3 API issues
These are the kinds of issues that you might see when trying to connect to IBM COS externally:
•Issue: Cannot connect to device
– Answer: Validate that you are using the correct IP address and port of the Accesser appliance.
•Issue: Cannot authenticate
– Answer: Validate that you enabled Access Key ID authenticate in the Manager GUI.
•Issue: Cannot list directory
– Answer: Validate that you have created the vault.
– Answer: Validate that you have deployed the vault to the Accesser through an access pool.
– Answer: Validate that you have the correct rights to the vault.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.