IsilonSD nodes show "SCSI Bus Error" on the VM Console
Summary: Upon deploying a new node a IsilonSD node may scroll "SCSI Bus Error" on the console
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
When deploying a new node using the management server for IsilonSD it may appear "hung" at deploying. This will (after hours) timeout, you can stop it by refreshing the Management Server web page. If you open the VMs console you may see SCSI Bus Errors as seen in the screen shot below.
Cause
This may be caused by numerous issues, some are outlined below.
- A network issue between the new node and other nodes in the cluster (specifically the primary join node traditionally the lowest LNN)
- A connection (Network, SCSI, or FC) between the VM and its underlying storage
- Not enough internal IPs in cluster to allocate to the new node
Resolution
For resolving issues 1 and 2 please engage your VMWare or the underlying storage support team for review of the network or storage devices. Often we have seen a simple cable connection or misconfiguration between hosts or vSwitchs as the cause.
For issue 3, look at he clusters internal IPs to make sure there are enough unallocated. One method is :
For issue 3, look at he clusters internal IPs to make sure there are enough unallocated. One method is :
On the Existing cluster
#isi config
>> status
Example below shows no unallocated (Free) IPs:
Example shows adding 1 IP to the cluster above:
#isi config
>> status
Example below shows no unallocated (Free) IPs:
Isilon OneFS v8.1.2.0
UpgradeTest-1# isi config
Welcome to the Isilon IQ configuration console.
Copyright (c) 2001-2018 EMC Corporation. All Rights Reserved.
Enter 'help' to see list of available commands.
Enter 'help <command>' to see help for a specific command.
Enter 'quit' at any prompt to discard changes and exit.
Node build: Isilon OneFS v8.1.2.0 B_8_1_2_016(RELEASE)
Node serial number: <SerNu>
UpgradeTest >>> status
Configuration for 'UpgradeTest'
Local machine:
----------------------------------+-----------------------------------------
Node LNN : 1 | Date : 2021/04/08 14:38:52 EDT
----------------------------------+-----------------------------------------
Interface : vmx1 | MAC : <MAC>
IP Address : <IP> | MAC Options : 10Gbase-T
----------------------------------+-----------------------------------------
Network:
----------------------------------+-----------------------------------------
JoinMode : Automatic
Interfaces:
----------------------------------+-----------------------------------------
Interface : int-a | Flags : enabled_ok cluster_traffic
Netmask : 255.255.255.0 | MTU : 1500
----------------+-----------------+------------------+----------------------
Low IP | High IP | Allocated | Free
----------------+-----------------+------------------+----------------------
10.10.250.1 | 10.10.250.4 | 4 | 0
----------------+-----------------+------------------+----------------------
UpgradeTest >>>
To add additional IPs you can use the "iprange" command within "isi config"
Example shows adding 1 IP to the cluster above:
UpgradeTest >>> iprange
Interface int-a IP Ranges:
10.10.250.1-10.10.250.4
UpgradeTest >>> iprange int-a 10.10.250.1-10.10.250.5
IP range 10.10.250.1-10.10.250.5 added to int-a.
UpgradeTest >>> commit
Commit succeeded.
UpgradeTest-1# At this point attempt a new node add. Note: you will need to remove the failed node from management server first by selecting it and using the trash can icon:
Article Properties
Article Number: 000185108
Article Type: Solution
Last Modified: 05 Aug 2021
Version: 3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.