Table of Contents
Advertisement
Quick Links
Advertisement
Table of Contents
Troubleshooting
Related Manuals for Hitachi Hyper Scale-Out
Summary of Contents for Hitachi Hyper Scale-Out
- Page 1 Hyper Scale-Out Platform Maintaining and Troubleshooting MK-94HSP006-03...
- Page 2 “Materials” mean text, data, photographs, graphics, audio, video and documents. Hitachi reserves the right to make changes to this Material at any time without notice and assumes no responsibility for its use. The Materials contain the most current information available at the time of publication.
-
Page 3: Table Of Contents
Response..........5 Contents Hyper Scale-Out Platform Maintaining and Troubleshooting... - Page 4 A Port usage ..........31 Contents Hyper Scale-Out Platform Maintaining and Troubleshooting...
-
Page 5: Preface
• Basic understanding of networking, as well as site-specific network knowledge If you need a high level overview of the Hyper Scale-Out Platform, we recommend reading the following documents: • Introducing Hitachi Hyper Scale-Out Platform provides an overview of the HSP components, architecture, and product features. -
Page 6: Product Version
Product version This document revision applies to Hyper Scale-Out Platform 1.2 or later. Release notes Read the release notes before installing and using this product. The release notes may contain requirements or restrictions that are not fully described in this document or updates or corrections to this document. -
Page 7: Conventions For Storage Capacity
Getting help Hitachi Data Systems Support Portal is the destination for technical support of products and solutions sold by Hitachi Data Systems. To contact technical support, log on to Hitachi Data Systems Support Connect for contact information: https://support.hds.com/en_us/contact-us.html. Hitachi Data Systems Community... -
Page 8: Comments
Please send your comments on this document to: hsp.documentation.comments@hds.com Include the document title, number, and revision, and refer to specific sections and paragraphs whenever possible. All comments become the property of Hitachi Data Systems. Thank you! • viii Preface Hyper Scale-Out Platform Maintaining and Troubleshooting... -
Page 9: Accessing The Health Of An Hsp Cluster
Monitoring alert conditions using the management interfaces • Monitoring the run state of HSP resources Overview The storage management aspects of the Hyper Scale-Out Platform are designed for: • Self-healing—failed internal services are restarted automatically. If these services fail to restart after a period of time, the node is... -
Page 10: Visually Monitoring Cluster Node Health
Power button with LED Blue on: System power on Off: System power off Amber blinking: DC off and fault Amber and blue blinking: DC on and fault Accessing the health of an HSP cluster Hyper Scale-Out Platform Supporting and Troubleshooting... - Page 11 LED that indicates drive activity. If the red LED is illuminated, this indicates a disk drive failure. The HSP software reports an alert condition for disk failures. Accessing the health of an HSP cluster Hyper Scale-Out Platform Supporting and Troubleshooting...
-
Page 12: Monitoring Alert Conditions Using The Management Interfaces
SMTP configuration in HSP. Consult the documentation for the interface you are using to manage your HSP cluster (API, CLI, or GUI) for details. Accessing the health of an HSP cluster Hyper Scale-Out Platform Supporting and Troubleshooting... -
Page 13: Using The Management Console
Date and time that the alert condition was raised. Description describing the administrative action resolution string that should be considered to correct or clear the alert condition. alert-name string Name of the alert condition. Accessing the health of an HSP cluster Hyper Scale-Out Platform Supporting and Troubleshooting... -
Page 14: Monitoring The Run State Of Hsp Resources
IP that is not allowing its use. Make sure there are no GET https://<cluster-ip>/hspapi/v2// other devices on the network using this IP hspapi/ip-addresses/list address. Accessing the health of an HSP cluster Hyper Scale-Out Platform Supporting and Troubleshooting... - Page 15 Run state for a virtual machine instance can be: • UP—Instance is running. VM instance hspadm vm-instance list • DOWN—Instance or template deploying the instance has been shut down. GET https://<cluster-ip>/hspapi/v2/vm- instances/list Accessing the health of an HSP cluster Hyper Scale-Out Platform Supporting and Troubleshooting...
- Page 16 • UP—VM Volume has been added and VM volume available for use. hspadm vm-volume list • ERROR—The underlying disk to which the VM volume is associated has failed. GET https://<cluster-ip>/hspapi/v2/vm- volumes/list Accessing the health of an HSP cluster Hyper Scale-Out Platform Supporting and Troubleshooting...
-
Page 17: Adding And Replacing Hardware Components
Adding and replacing hardware components Hyper Scale-Out Platform (HSP) is an appliance solution. As such, few parts are customer serviceable or replaceable—most hardware defects or failures result in the field replacement of parts or the larger assembly. Before performing maintenance any maintenance task: •... - Page 18 This chapter covers: • Increasing storage capacity by adding nodes • Replacing a failed node • Replacing a failed power supply on a node • Replacing one or more failed disks Adding and replacing hardware components Hyper Scale-Out Platform Supporting and Troubleshooting...
-
Page 19: Increasing Storage Capacity By Adding Nodes
Step 1: Installing the outer rails on the rack • 1. Press upward on the locking tab at the rear end of the middle rail. 2. Push the middle rail back into the outer rail. Adding and replacing hardware components Hyper Scale-Out Platform Supporting and Troubleshooting... -
Page 20: Step 2: Installing The Node On The Rack
4. Depress the locking tabs of both sides at the same time and push the chassis all the way into the rear of the rack. 5. Use screws to secure the chassis handles to the front of the rack. Adding and replacing hardware components Hyper Scale-Out Platform Supporting and Troubleshooting... -
Page 21: Step 3: Cabling The Nodes
Red cables go into the top switch in rack unit 42 and are plugged into the left 40 GbE port on each node. • Blue cables go into the bottom switch in rack unit 41 and are plugged into the right 40 GbE port on each node. Adding and replacing hardware components Hyper Scale-Out Platform Supporting and Troubleshooting... - Page 22 Important: Be sure to properly seat each Ethernet cable at both ends. There is an audible click when the cables are properly seated. Cabling will look similar to the following as you cable the additional nodes: Adding and replacing hardware components Hyper Scale-Out Platform Supporting and Troubleshooting...
- Page 23 Adding and replacing hardware components Hyper Scale-Out Platform Supporting and Troubleshooting...
-
Page 24: Step 4: Connecting The Power Cables
3. Gather the power cable slack on the left side of the rack and zip tie the node’s power cables to the rack using the rack mount hole immediately above the server rail kit. Adding and replacing hardware components Hyper Scale-Out Platform Supporting and Troubleshooting... -
Page 25: Step 5: Power On The Nodes
1. Press the power button on the node control panel. 2. On the back of the node, verify that the LED lights on both power supplies and both boot drives are displaying green. Adding and replacing hardware components Hyper Scale-Out Platform Supporting and Troubleshooting... -
Page 26: Replacing A Failed Node
Step 2: Installing the replacement node Follow the steps in “Increasing storage capacity by adding nodes” on page 2-11 to install the replacement node. Adding and replacing hardware components Hyper Scale-Out Platform Supporting and Troubleshooting... -
Page 27: Replacing A Failed Power Supply On A Node
$ hspadm node edit --name Node007 --maintenance-mode y 2. Run the hspadm command to shut down the node with the failed power supply. For example: $ hspadm node shutdown --name Node007 Adding and replacing hardware components Hyper Scale-Out Platform Supporting and Troubleshooting... -
Page 28: Step 2: Remove And Replace The Power Supply
7. Press the power button on the node control panel. 8. On the back of the node, verify that the LED lights on both power supplies and both boot drives are displaying green. Adding and replacing hardware components Hyper Scale-Out Platform Supporting and Troubleshooting... -
Page 29: Step 3: Take The Node Out Of Maintenance Mode
2. Run the hspadm command to take the node out of maintenance mode. For example: $ hspadm node edit --name Node007 --maintenance-mode n Using the Management API HTTP request syntax POST https://<cluster-ip>:<port>/hspapi/nodes/<node-id> and specify the following in the POST payload: “maintenance-mode”: False Adding and replacing hardware components Hyper Scale-Out Platform Supporting and Troubleshooting... -
Page 30: Replacing One Or More Failed Disks
You may swap a complete and intact set of drives from one node, however, because this task requires manually importing them via bios or command line, it should only be accomplished with the assistance of Hitachi Support personnel. To replace a 3.5” HDD disk 1. -
Page 31: Troubleshooting
Troubleshooting This chapter describes some methods of identifying and fixing some basic issues you might encounter using the Hyper Scale-Out Platform: • Hardware troubleshooting • Alert troubleshooting • Network troubleshooting • Virtual machine troubleshooting Troubleshooting Hyper Scale-Out Platform Supporting and Troubleshooting... -
Page 32: Hardware Troubleshooting
• A node only scans for new drives once an hour, so if you have replaced/inserted a drive, it remains in an error state until the next scanning occurs. Troubleshooting Hyper Scale-Out Platform Supporting and Troubleshooting... -
Page 33: Alert Troubleshooting
Initiate fsck on the file system and contact Customer Support if error fsck is unsuccessful File system is running out of free Remove files or increase the size of the file system space Troubleshooting Hyper Scale-Out Platform Supporting and Troubleshooting... -
Page 34: Network Troubleshooting
NIC. Cluster or nodes are not getting an IP address For example: Nodes are not cabled properly admin@Node003:~$ node_check --nic Testing eth0 Testing eth2 Testing eth3 No Ethernet errors detected Troubleshooting Hyper Scale-Out Platform Supporting and Troubleshooting... - Page 35 8980 bytes from 192.169.0.10: icmp_req=7 ttl=64 time=0.195 ms 8980 bytes from 192.169.0.10: icmp_req=8 ttl=64 time=0.184 ms 8980 bytes from 192.169.0.10: icmp_req=9 ttl=64 time=0.202 ms 8980 bytes from 192.169.0.10: icmp_req=10 ttl=64 time=0.198 ms Continued... Troubleshooting Hyper Scale-Out Platform Supporting and Troubleshooting...
- Page 36 64 bytes from 172.20.128.1: icmp_req=4 ttl=255 time=1.30 ms 64 bytes from 172.20.128.1: icmp_req=5 ttl=255 time=1.18 ms --- 172.20.128.1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 402ms rtt min/avg/max/mdev = 1.182/1.629/2.334/0.402 ms No Ethernet errors detected Troubleshooting Hyper Scale-Out Platform Supporting and Troubleshooting...
-
Page 37: Virtual Machine Troubleshooting
Virtual machine troubleshooting Troubleshooting Hyper Scale-Out Platform Supporting and Troubleshooting... - Page 38 Troubleshooting Hyper Scale-Out Platform Supporting and Troubleshooting...
-
Page 39: A Port Usage
4001 tcp/udp nlockmgr 4002 tcp/udp statd 5900, 5910 VNC server for virtual machines 8000, 80 tcp (http) API/GUI 8443, 443 tcp (http) API/GUI 8080 tcp (http) Swift proxy server 8888 tcp (http) Ganglia graphs Hyper Scale-Out Platform Supporting and Troubleshooting... - Page 40 Hyper Scale-Out Platform Supporting and Troubleshooting...
- Page 41 Hyper Scale-Out Platform Maintaining and Troubleshooting...
- Page 42 Hitachi Data Systems Corporate Headquarters 2845 Lafayette Street Santa Clara, California 95050-2639 U.S.A. www.hds.com Regional Contact Information Americas +1 408 970 1000 info@hds.com Europe, Middle East, and Africa +44 (0)1753 618000 info.emea@hds.com Asia Pacific +852 3189 7900 hds.marketing.apac@hds.com MK-94HSP006-03...