| Asset ID: |
1-71-1008327.1 |
| Update Date: | 2011-05-19 |
| Keywords: | |
Solution Type
Technical Instruction Sure
Solution
1008327.1
:
How to validate Sun StorageTek[TM] 2500, Sun Storage[TM] 6000, and Flexline Array Controller Out of Band Communication
| Related Items |
- Sun Storage 6180 Array
- Sun Storage 6580 Array
- Sun Storage Flexline 280 Array
- Sun Storage 6780 Array
- Sun Storage 2540 Array
- Sun Storage 2510 Array
- Sun Storage 6140 Array
- Sun Storage Flexline 380 Array
- Sun Storage 2530 Array
- Sun Storage Flexline 240 Array
- Sun Storage 6130 Array
|
| Related Categories |
- GCS>Sun Microsystems>Storage - Disk>Modular Disk - 6xxx Arrays
- GCS>Sun Microsystems>Storage - Disk>Modular Disk - 2xxx Arrays
- GCS>Sun Microsystems>Storage Software>Datacenter Disk Device Software
- GCS>Sun Microsystems>Storage - Disk>Modular Disk - Flexline FLX FLA FLC Arrays
|
PreviouslyPublishedAs
211394
Applies to:
Sun Storage 2540 Array - Version: Not Applicable and later [Release: N/A and later ]
Sun Storage 6130 Array - Version: Not Applicable and later [Release: N/A and later]
Sun Storage 2530 Array - Version: Not Applicable and later [Release: N/A and later]
Sun Storage 2510 Array - Version: Not Applicable and later [Release: N/A and later]
Sun Storage 6140 Array - Version: Not Applicable and later [Release: N/A and later]
All Platforms
Goal
The purpose of this document is to identify whether a SANtricity,
Common Array Manager, or other management capable software for the
2500, 6000, and Flexline array family can communicate properly with
each RAID Controller's IP based management port.
Symptoms include but are not limited to:
- Unresponsive array in Sun StorageTek SANtricity(SANtricity)
- Array Communication Out of Band event in Sun StorageTek Common Array Manager(CAM)
- Cannot Register Array in CAM
Solution
Please validate that each troubleshooting step below is true for your environment. Each step will provide instructions via a link to a document, for validating the step and taking corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not skip a step.
A. Verify that you can communicate with the array controllers. Using Common Array Manager, you can use the service command to validate the communication. All commands are out of the following platform dependent directories: Solaris: /opt/SUNWsefms/bin/
Windows: C:\Program Files\Sun\Common Array Manager\Component\fms\bin
Linux: /opt/sun/private/fms/bin
service -d <array_name> -c contact -t < a | b >
# ./ras_admin device_list
Monitored On Device Type IP Address WWN Active ASR
------------ --------------- ---- ------------ ---------------- ------ ---
mycamhost my6180 6180 10.30.16.158 200400a0b8168e11 Y N
# ./service -d my6180 -c contact -t a
Executing the contact command on my6180
Completion Status: Controller A was successfully contacted
# ./service -d my6180 -c contact -t b
Executing the contact command on my6180
- If you are using SANtricity Storage Manager, go to Step B.
- If you are able to contact all controllers in the array, then you have validated communication, and no further work is required.
- If you are unable to contact one or both controllers, continue to Step B.
B. Telnet to the controller IP on port 2463 Telnet to both A and B Controllers on port 2463. For arrays that are running firmware 06.70.54.11 or lower, a normal telnet connection will last a full sixty(60) seconds. This can include the following arrays: - Sun StorEdge 6130
- Sun StorageTek 6140
- Sun StorageTek 6540
- Sun StorageTek 2510
- Sun StorageTek 2530
- Sun StorageTek 2540
- StorageTek Flexline 240
- StorageTek Flexline 280
- StorageTek Flexline 380
For arrays that are running firmware 07.10.25.10 or above, a normal telnet connection will last a full five minutes(600 seconds). This can include the following arrays: - Sun StorageTek 6140
- Sun StorageTek 6540
- Sun StorageTek 2510
- Sun StorageTek 2530
- Sun StorageTek 2540
- Sun Storage 6180
- Sun Storage 6580
- Sun Storage 6780
- StorageTek Flexline 380
NOTE 1: It is not absolutely necessary to know the firmware of an
array. It is important to understand that if the telnet session lasts
longer than 60s, you continue to time the array connection until
completion.
Example: # time telnet 2463
Trying ...
Connected to .
Escape character is '^]'.
^]
telnet> q
Connection to closed.
0.0u 0.0s 0:59 0% 0+0k 0+0io 0pf+0w
#
- If both controllers show that they can connect for a full 60 or 600 seconds, that the arrays are capable of establishing a connection via the management interface. Check that the management software can communicate with the array. Reference <Document 1007046.1>: Troubleshooting Sun StorageTek[TM], Sun StorEdge[TM], and Sun Storage[TM] Management Communication Faults with Arrays
- If one controller maintains a full 60 second connection and the other cannot, this indicates that the controller that cannot communicate may be either Offline, or not have a network connection to it. Check that the management software can register the array using the IP address of the controller that can establish a connection on port 2463, and check the status of the alternate. <Document 1007046.1>: Troubleshooting Sun StorageTek[TM], Sun StorEdge[TM], and Sun Storage[TM] Management Communication Faults with Arrays
- If both controllers cannot stay connected for a full 60 seconds, this indicates that both of the controllers are going through a boot cycle/loop. Please go to Step J.
- If you get the Connection refused, this means that there is a route to the array, but the management service on the controller is not listening. Go to Step D
- If you get nodename nor servname provided, or not known, you do not appear to have a route to the IP specified. Go to Step C.
C. Check whether you can Ping the array controller IP Use ping from the management host to ping each array controller IP address. Example: # ping
is alive
#
- If you can ping an array controller, this my indicate that either the port 2463 is blocked, or is not listening on the controller. Please continue to Step J
- If you cannot ping either array controller, continue to Step D
D. Validate the RAID Controller FAULT LED
Using the location table above, validate whether the fault LED is on or off for a given controller. Observe the LED for approximately 2 minutes, to ensure that the fault
status is stable.
For 6130, FLX240, FLX280, D-Series, B-Series, and 2500 Storage Arrays:
- If the Amber LED is lit for a full two minutes, this indicates that the controller in question is in an offline status. Go to Step J.
- If the Amber LED is lit, but cycles between Off and On states this indicates that the controller in question may be continually rebooting, and require service intervention. Go to Step J.
- If the Amber LED is off, go to Step E.
For 6140, 6540, 6180, 6580, and 6780:
- If the Amber LED is lit for a full two minutes, this indicates that the controller in question is in an offline status. Go to Step J.
- If the Amber LED is lit, but cycles between Off and On and the seven-segment tray ID is constantly changing, this indicates that the controller in question may be continually rebooting, and require service intervention. Go to Step J.
- If the Amber LED is off, go to Step E.
E. Validate Physical Network Link Check the Ethernet cables to ensure that there is no visible damage and that they are securely connected. Check that link LEDs on Network ports are Lit and Green. - If physical connection is good, continue to Step F.
- After doing one of the following repeat Steps A through E:
- Replace Cable
- Swap port on Ethernet Router/HUB/Switch
- Directly connect using a Cross-Over Cable.
NOTE 2: Do not change ethernet ports on the array. Each one uses its own IP address, and may not be set properly for your LAN.
F. Validate that Ethernet Switch/Router is set to Auto Negotiate The how to for this differs based on Ethernet switch model and vendor. Contact your switch/router vendor for documentation and support on this.
- If auto-negotiate is set, continue to Step G
- If auto-negotiate is not set, set it on your switch, and reset the network link(cable pull is fine), and repeat Steps A through F.
G. Validate Array Network Settings For arrays running 06.16.81.10 or later, the array has a Service Menu which is accessible via the serial port on the array.
Use this serial connection to access the service interface, and check:
- DHCP Setting ON or OFF
- Netmask
- IP Add
Sun StorageTek 6140 Array
- Gateway IP Address
- For 2500 Arrays, Reference Sun StorageTek 2500 Series Array Hardware Installation Guide.
- For
6130/FLX240/FLX280 Arrays, there was no service menu until after
06.16.81.10. The serial settings are: 19200 baud, 8-bit, No Parity, 1
stop bit, No flow control. The menu is identical to any of the arrays
in this list.
- For 6140 Arrays, Reference Sun StorageTek 6140 Array Getting Started Guide.
- For 6540/FLX380 Arrays, Reference Sun StorageTek 6540 Array Hardware Installation Guide.
- For 6580/6780 Arrays, Reference Hardware Installation Guide for Sun Storage 6580 and 6780 Arrays.
- For 6180 Arrays, Reference Sun Storage 6180 Array Hardware Installation Guide.
NOTE 3: For 6140, 6180, 6540, 6580, 6780 and FLX380 Arrays, Network Port 1 is the INNER MOST port on the controller. Port 2 is the OUTER MOST port on the controller.
NOTE 4: The 6130/FLX240/FLX280 uses an RS232 Null Modem Cable.
- If your array has firmware below 06.16.81.10, go to Step J
- If you are using DHCP, continue to Step H.
- If your network settings are wrong, change your network settings as necessary to work on your LAN, and repeat Steps A through D.
- If
a gateway is set, make sure that you can ping the gateway address from
the management host. If you cannot, correct this issue, and go to Step A.
- If no changes were made and the port settings are correct, or if you cannot get a serial connection, go to Step I.
H. Validate your DHCP server Verify that your
DHCP server does not require the array to release and renew its IP
address. If it does, you will want to either: - Set a static IP on the controller
- Set a static IP on the DHCP server
- Get
used to having to finding a specific IP range and registering an array
every time you need to monitor it. The management software has no way
to pick up the new IP address that the DHCP server provided it. DHCP
was originally intended as a way to discover an array for the first
time without setting up
a private LAN, as the controllers will use BOOTP by default at startup.
- If you changed your IP to static and made new settings, repeat Step A.
- If you have a dynamic IP, repeat Step A using the current IP table from your DHCP server.
- If you are using the dynamically assigned IP for Steps A through C, go to Step I.
- If you are not using DHCP, go to Step I.
I. Verify that you are not running into Sun Alert 240105 Review Sun Alert <Document 1019498.1>: Sun
StorageTek 25x0 and 6140 Arrays may send wrong Network packets, causing
the Sun StorageTek Common Array Manager (CAM) Host to Lose the Network
Connection to the Array
- If you are under the
affected products list, please attempt to either clear the ARP table
for the network port(s) the controller(s) is/are plugged into, or
reboot the network switch, and repeat Step A.
- If you are not under the affected products list, of the Sun Alert, continue to Step J.
J. Data Collection Please collect and compile the following information: - Results of Step A for both controllers
- Results of Step B for both controllers
- Results of Step C for both controllers
- Results of Step D for both controllers
- Results of Step F for both controllers
- IP address, netmask, and gateway setting of management host
- IP address, netmask, and gateway setting of Controller A
- IP address, netmask, and gateway setting of Controller B
- Which Network port is connected to the LAN from each controller
- Array Model
Attachments
This solution has no attachment
|
