Sun Storage 6580 Array
 
Sun Storage Flexline 240 Array
 
Sun Storage Flexline 380 Array
 
Sun Storage 2540-M2 Array
 
Sun Storage Flexline 280 Array
 
Sun Storage 6130 Array
 
Sun Storage 6180 Array
 
Sun Storage 2540 Array
 
Sun Storage 6540 Array
 
Sun Storage 2510 Array
 
Sun Storage 6780 Array
 
Sun Storage 2530 Array
 
Sun Storage 2530-M2 Array
 
Sun Storage Flexline 210 Array
 
Sun Storage 6140 Array
 

PLA-Support>Sun Systems>DISK>Arrays>SN-DK: 6130
 
.Old GCS Categories>Sun Microsystems>Storage - Disk>Modular Disk - 6xxx Arrays
 
.Old GCS Categories>Sun Microsystems>Storage - Disk>Modular Disk - 2xxx Arrays
 

Establishing a serial connection to an array controller is commonly used to clear array passwords and to view or set IP addresses on the controllers.  It can also be used by trained service personnel to repair problems in an array that cannot be resolved in any other fashion.

In this Document

Goal

Fix

References

Applies to:

Goal

The purpose of this document is to provide additional information on how to establish a serial connection to one of the following array controller:

Fix

Establishing a working serial connection from a terminal to an array controller can involve many factors:

• The connector on the array controller.
• Software program used to establish the serial connection.
• Terminal used.
• Cabling.

Since each of these factors can have multiple answers, the number of different combinations possible will not all be covered in this document.  This document will cover two of the most commonly used software programs.  If you are using something not covered here, you should be able to adapt what is provided to get a working connection.

1. Connector Type.
   
   There are two types of connectors on the controllers:
   
   
   • PS2/Mini-DIN
   • DB9
   
   The PS2/Mini-DIN will be found on the 25x0, 25x0-M2, 6140 and 6180 arrays. The DB9 will be found on the FLXxx0, 6130, 6540 and 6x80 arrays. Reference <Document 1021066.1> Verify Sun Storage Array Array Type via the User Interface to determine your array type if you are unsure.
   
   
2. Software Programs.
   
   This document uses examples of tip (for Unix) and HyperTerminal (for Windows) but whatever program you are using you will need to configure the following values:
   
   
   • Baud rate = 38400
   • Data bits = 8
   • Parity = None
   • Stop bits = 1
   • Flow Control = None
   
   
   Note:  Serial port baud rates range from 300 to 38400 at standard increments.  Depending on the controller type, the default is either 9600 or 19200.  38400 is what this document recommends.
   
   
   While these values are fairly standard, you should confirm and if necessary update them.  If you are using HyperTerminal in Windows, these values can be set and saved in the GUI as a new connection.  If you are using the tip utility in Unix these are the default settings used for the hardwire entry in /etc/remote.
   
   Next you want to make sure you are using the proper port.  In HyperTerminal these are values like COMM1, COMM2, etc. Check your terminal documentation for the proper location.  If you are using a USB port, you will have to go to the Device Manager to see which COMM port is associated with the USB port you are using.  If you are using tip, the port is defined in the /etc/remote file.
   
   Lastly, the Software Program used is the most common factor to determine how you send a break sequence. While some Software Programs (PuTTY) have a menu option to send a break, others rely on a specific keystroke combination like ~# (~ and #) in tip.
   
   
   Note:  Again, this document should not be interpreted to imply that Oracle supports these programs.  Issues with these programs should be addressed to the appropriate parties.
    
3. Terminal Used.
   
   The type of terminal used may also influence the correct keystroke sequence to send a break. Typically laptops will use Control+Break, but others are Function+Break. And if you are using a newer model laptop, you may have to use a USB port for the serial connection as serial ports are becoming less and less of an option with newer equipment.
4. Cabling.
   
   At its most basic, the cable connecting your terminal to the controller is a NULL Modem cable. The exact cable you use will depend on the connectors you have at both the controller and terminal ends. 
   
   For controllers with a DB9 connector on them, you can pick up a standard NULL Modem cable from any electronics hardware store. Depending on what connector your terminal uses you may also have to use an adapter. This adapter should be "straight-through" in that it does not cross wire any of the pins. DTR (Data Terminal Ready) goes to DTR etc.
   
   If you have an array that has a PS2/Mini-DIN connector, it comes with a cable (530-3544-01) with a PS2/Mini-DIN on one end and an RJ45 on the other.  This cable is typically not readily available at electronics hardware stores.  There were also some of these cables in which the wiring was reversed on the RJ45 end turning it from a straight-through cable into a NULL Modem.  If you look at the RJ45 end with the connector pointing towards you and the gold connectors facing up, the straight-through cable will have the orange wires on the right.  a NULL Modem cable will have the orange wires on the left. All of the cables come with 2 RJ45 to DB9 adapters, 530-3500-01 (silver) and 371-1107-01 (black). The silver adapter is a straight-through and the black adapter is a NULL Modem. In order to make the proper combination a NULL Modem, you need to combine a straight-through (cable or adapter) with a NULL Modem (cable or adapter).
5. Making the Connection.
   
   Make the physical connection between the terminal and the controller using the cable based on step 4. Windows users should start the HyperTerminal program and send a break sequence. Unix users should execute "tip hardwire" from a terminal window and will get a "connected" response. The next step is to send a break sequence to the controller. If the baud rate currently set on the controller does not match the baud rate you are using, you will see a lot of scrambled characters - do not panic.  Continue to send break sequences every couple of seconds until you see something like the following:
   
   Press the space bar within 5 seconds: <S> for Service Interface. <BREAK> for baud rate
   
   
   When you press the space bar (within the allotted 5 seconds) it will set the baud rate to match your terminal.  If you fail to do so in the allotted time, go back to sending break sequences and the controller will cycle through the baud rates until you see the above message a second time.

This section is Internal Only
If you are wanting to access the shell, after setting the baud rate, send another break sequence.  When you see the prompt to type S for the Service Interface, instead hit the escape key.  For controllers running 6.x firmware, you will be prompted for the shell password.  For 7.x you will be first prompted for a user and then the shell password.  This information is beyond the scope of this document and if you need to access the shell, you should contact an L2 Engineer for assistance.

References

This solution has no attachment