Sun Storage 3000 and T3 Arrays: Troubleshooting Serial and Network Management Port Connections

Asset ID:	1-75-1012660.1
Update Date:	2017-10-05
Keywords:

Solution Type Troubleshooting Sure

Solution 1012660.1 : Sun Storage 3000 and T3 Arrays: Troubleshooting Serial and Network Management Port Connections

Applies to:

Sun Storage 3310 Array - Version Not Applicable and later
Sun Storage 3320 SCSI Array - Version Not Applicable and later
Sun Storage 3510 FC Array - Version Not Applicable and later
Sun Storage T3 Array - Version All Versions and later
Sun Storage 3511 SATA Array - Version Not Applicable and later
All Platforms

Purpose

The troubleshooting steps below will help you understand some of the common problems that occur with arrays when connecting to the serial or network management interfaces. This document is relevant for the following arrays:

Sun Storage T3 Array
Sun Storage T3+ Array
Sun Storage 3310 Array
Sun Storage 3320 Array
Sun Storage 3510 Array
Sun Storage 3511 Array

Arrays in the Sun Storage T3 family are also sometimes referred to as Sun Storage T300 Arrays.

Please validate whether each statement under the steps below is true for your environment. These steps will hyperlink you to relevant content that will tell you how to fix the symptom if it is true for your environment. The listed symptoms are ordered in the most appropriate sequence to isolate the issue and be certain about the related fix. Please do not skip a step.

Troubleshooting Steps

Symptoms

Unable to ping array
Unable to telnet to array
Unable to access array's serial port

This document is linked from:

<Document 1012673.1> Troubleshooting Sun StorEdge[TM] T3 Configuration

<Document 1005313.1> Sun Storage 3000 Arrays: Troubleshooting Configuration Problems

<Document 1011431.1> Troubleshooting Sun Storage 3000 Array Series Hardware

Step 1: Verify if there is a connection between array and host by using ping and telnet commands.

Example:

# ping 10.1.229.133 (IP address of controller)
# telnet 10.1.229.133 (IP address of controller)

Step 2: Connect to the array via serial port.

Example on Solaris host:

T3 & T3+ # tip -9600 /dev/ttyb

3000 Array # tip -38400 /dev/ttyb

The T3 requires a specific cable for serial port connection. Refer to <Document 1008662.1> Sun StorEdge T3 & T3+: Serial port pinouts for specific serial cable pinout diagrams.

Step 3: Verify network configuration settings (IP, gateway and netmask) on the array.

On a T3 array use the set command to check network settings.

Example:

storage-t3b # set
ip        10.1.229.133
netmask   255.255.255.0
gateway   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

For the 3000 series arrays use the sccli> show network command in-band to display network settings, or use the firmware menu to show or configure network parameters.

Example:

sccli> show network-parameters

ip-address: 129.153.49.188

netmask: 255.255.255.0

gateway: 129.153.49.254

mode: static

Sun Storage 3000 Array's Main Menu:

Select view and edit Configuration Parameters and press <enter>

Select Communication Parameters and press <enter>

Select Internet Protocol(TCP/IP) and press <enter>

Press <enter> on lan0

Select Set IP Address and press <enter>

Address, NetMask and Gateway are shown --> go back with ESC when you do not want to change anything

Below are examples of how to make changes to the IP, netmask, and gateway, if needed.

T3 Array:

set ip 10.1.229.134
set netmask 255.255.255.0
set gateway 10.1.229.248

3000 Arrays:

via sccli:

sccli> configure network-interface lan0 ip-address 129.153.49.189 netmask 255.255.255.0 gateway 129.153.49.254

via Main Menu:

Select view and edit Configuration Parameters and press <enter>

Select Communication Parameters and press <enter>

Select Internet Protocol(TCP/IP) and press <enter>

Press <enter> on lan0

Select Set IP Address and press <enter>

Enter IP Address, NetMask and Gateway

Changes for 3000 arrays will not take effect until the controller is reset.

Step 4: Verify that network connections on arrays are working by using ping and telnet commands.

Step 5: Verify that the link status LED on the back of the controller is green. If the LED is not active, it indicates an invalid link. The connectivity of the network needs to be verified.

Previously Published As
86541

Attachments

This solution has no attachment