Purpose

• Unable to ping T3,T3+ and 6120 array
• Unable to telnet to T3, T3+ and 6120 array

Last Review Date

Instructions for the Reader

Troubleshooting Details

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.

1) Telnet to the array using the host name or IP address.

You should receive a login prompt. The only user available is root. You are responsible for the password.

• If you get a login prompt, but are unable to log in as root, recovery of the password will require an outage. Please contact Oracle Support to help you with the recovery.

• If telnet responds with Connection Refused, the network and name resolution is ok, but the array is not accepting requests to port 23 for telnet. Continue to Step 5.
• If telnet responds with Connection Timed Out, there is likely a problem establishing a socket on port 23, or a problem with the route to the controllers.
• If telnet responds with nodename nor servname provided, or not known, the name resolution is not correct. Retry with the IP address. If the IP address still fails, Continue to Step 2
  

Ping the array controller by IP address.

• If ping by IP works, then you have a name resolution issue on your host or network. Check the telnet again after resolving it.

• If ping by IP fails, continue to

Visually inspect the Ethernet LEDs located on the controller to see if basic Ethernet connectivity has been established.

Following table explains the LED status.

• If the VAL/ACT LED is Green “on” then you have physical connectivity. Proceed to Step 4.

• If the VAL/ACT LED is green “off”, Verify the physical connections to the network ports, and make sure the LED comes on as Green
  
  

4) Verify the IP address and network settings to the array via a serial connection.

The serial connection for T3/T3+ arrays are field only kits. The 6120 arrays came with an RJ45 connection cable, that allowed access to the serial port.

The serial connection is:

9600 Baud

8 bit

no parity

Example(on the solaris host):

# tip -9600 /dev/ttyb

Once connected, sending a carriage return, will offer you a login prompt, which you should log in with root and the password.

• If you do not know the password, the recovery will require an outage. Contact Oracle Support for help with this procedure.

• If you do not have a cable, contact Oracle Support.
  

To verify network configuration settings (IP, gateway and netmask) on array run the command set

Example:

storage-t3b # set
ip        10.1.229.133
netmask   255.255.255.0gateway   10.1.229.248
tftphost  10.1.229.21
tftpfile  t3l3_316.bin
hostname  storage-t3b
timezone
logto     /syslog (* in nvram)
loglevel  3
rarp      on
mac       00:20:f2:00:c2:1e

• If the settings are correct, Go to Step 5.

• If you require a change to the settings, use the example below to make changes to the IP, netmask, and gateway, if needed. You will need to reboot the array for the settings to take effect. Repeat Step 1 and 2 after rebooting(reset -y).

T3 :

set ip 10.1.229.134
set netmask 255.255.255.0
set gateway 10.1.229.248

5) Use the ping command from the array serial connection to ping the gateway and system you are trying to telnet from.

• If ping succeeds to the gateway but not the server, then the issue is with the gateway routing.

• If ping succeeds from the array, to the server, but no from the server to the array as in Step 2, there may be a MAC addressing issue in your route table.

• If ping fails to both gateway and server, there may be a network initialization issue. We suggest resetting the array(reset -y).

• If the issue still persists,then please call Oracle service for further assistance.


Product
Sun StorageTek T3+ Array
Sun StorageTek T3 Array
Sun StorageTek 6120 Array

Internal Comments

This document contains normalized content and is managed by the the Domain Lead
(s) of the respective domains. To notify content owners of a knowledge gap
contained in this document, and/or prior to updating this document, please
contact the domain engineers that are managing this document via the “Document
Feedback” alias(es) listed below:

[email protected]

The Knowledge Work Queue for this article is KNO-STO-MIDRANGE_DISK.


Keywords
t3,t3+,6120,6020,telnet,login,ping,normalized

This solution has no attachment