| InfoDoc ID | Synopsis | Date | ||
| 24636 | StorEdge T3 General FAQs | 4 Jan 2001 |
| Status | Issued |
| Description |
- T3 General Questions -
Q.A. The quick answer is that the workgroup is just one tray and the Enterprise is two trays, or a "partner group." See the comparison table below for a more complete summary.
Q. What hosts can I hook up a T3 to?
A. E10000, E3x00-E6x00, E220R, E420R, E250, E450, U60, U80.
Q. What is the maximum number of T3's I can hook up to each host?
A. See the Host Platform Support Table below. It also contains the supported host bus adapters.
Q. What version of Solaris do I need for the T3?
A. Solaris 2.6, 7, or 8. Plus all appropriate patches of course.
Q. What do I do if I have forgotten the password on my T3?
A. If you have forgotten the password on the T300 storage system, you can do the following to gain access:
- Stop all I/O going to the T3(s).
- Connect console cable to a terminal and power off all units (both trays in a partner group).
- Power master unit back on (leave alternate master off) and interrupt the boot process by hitting RETURN when you see this message:
"hit the RETURN key within X seconds to cancel..."
Note: If you leave the alternate master on, it will continue to boot. Eventually it will assume there is a problem with the master that was interrupted, disable it, and make itself the master. Not good.
- At the "T3-EP" prompt, use the 'set passwd' command to view (and memorize...) the password.
- Type 'reset' to reboot, and immediately power on the alternate master (if present).
- If you choose, you can change the password after it boots with the 'passwd' command.
Q. What output is required to troubleshoot the T3?
A. Here is a list of commands that will give a wealth of information on a T3's setup.
ver
fru stat
fru list
vol stat
vol list
vol mode
set
sys list
port list
port listmap
/syslog file
/syslog.OLD file
/var/adm/messages{.t300} off of the data host
.loop stat
.disk pathstat u1d1-9 (and u2d1-9 if present)
For battery related issues, get these also:
id read u{1|2}pcu{1|2}
refresh -s Q. What are the pinouts for the T3's serial cable?
A. See page A-4 in the T3 Installation, Operation, and Service Manual for a better explanation (pinouts for other cables too). This is also provided in the Serial Port Pinouts Table below.
Q. Can 18-GB, 36-GB, and 73-GB drives be mixed in a single array?
A. No, there are currently no plans to support drive mixing. However, you CAN mix 36GHH with 36GLP drives. Just remember that this will complicate your disk firmware updates for arrays with multiple drive types present. This is because you can only upgrade firmware for one drive type at a time. So you should attempt to minimize mixing where possible.
Q. Can 18-GB, 36-GB, and 73-GB trays be mixed in the same partner group?
A. No, there are currently no plans to support mixing different array capacities in a partner group.
Q. Can Sun StorEdge A5X00/A3500/A1000/D1000 arrays and Sun StorEdge T3 arrays be connected to the same host system?
A. Yes, the Sun StorEdge T3 array has been tested with various combinations of the above listed Sun storage systems.
Q. Can FC-AL hubs be used with the Sun StorEdge T3 arrays? How many arrays can be connected to a single hub?
A. Yes, up to four Sun StorEdge T3 arrays can be attached to the Sun 7-port hub. BUT...there was a problem where DMP is not working properly with T3's and hubs. This stems from both a controller firmware and a Veritas problem. Patch
Q. Can FC-AL hubs and Alternate Pathing 2.3.1 be used with the StorEdge T3 arrays?
A. No, FC-AL hubs and AP are not currently supported with StorEdge T3 arrays. A later release of AP software will provide this support..
Q. Can both Sun StorEdge A5X00 arrays and Sun StorEdge T3 arrays be connected on the same Fibre Channel loop/hub?
A. No, mixing of Sun StorEdge A5X00 and T3 arrays on the same Fibre Channel loop/hub is not supported.
Q. Can I hook the T3 to a switch?
A. No, switches are not currently supported.
Q. How many Fibre Channel host connections are on each Sun StorEdge T3 array?
A. There is a single 100 MB/sec. host connection on each array. Every array MUST be connected to a host bus adapter (HBA), an FC-AL hub, or an on-board FC-AL socket of the SBus or graphics I/O boards.
Q. Does the Sun StorEdge T3 array have multi-host support? If so, how many hosts/initiators?
A. There is currently a limitation of TWO initiators per loop for the Sun StorEdge T3 for the workgroup (single tray) and a SINGLE initiator limitation for Sun StorEdge T3 for enterprise (paired arrays) configurations. This limitation applies to both FC-AL hub and switch configurations.
Q. Can I convert two T3 Workgroup trays into one T3 Enterprise partner group and vice versa?
A. The short answer is yes. The longer answer is it really isn't supported to turn two WG bricks into an ES partner group. Having said that, both procedures are documented.
So you can convert a single ES unit into two WG bricks. That would leave you with some unused UIC cables that you could potentially convert two WG trays into an ES with. Check out the source below for details on both procedures.
Page 25 T3 Configuration Guide
Q. Are Long-Wave GBICs supported on the Sun StorEdge T3 array?
A. No, there are currently no plans to support the Long-Wave GBIC on the Sun StorEdge T3 array.
Q. What is the maximum distance supported between the host and the array?
A. The Sun StorEdge T3 array supports a 500-meter distance between host and array using 50/125-micron multi-mode Fibre Channel cables.
Q. Where is the "hosts" file for Component Manager kept?
A. /etc/opt/SUNWesm/mo/hosts holds the name and IP info for the T3(s).
Q. What are the default values for T3 parameters?
A. Here is a brief list in the Default Settings Table below.
Q. How many Sun StorEdge T3 trays will fit in the Sun StorEdge 72-inch cabinet?
A. Eight Sun StorEdge T3 for the workgroup OR eight Sun StorEdge T3 for the enterprise trays will fit in the Sun StorEdge 72-inch cabinet.
- Eight Sun StorEdge T3 arrays for the workgroup consume 32 RUs (rack units) using eight 4U rackmount rails.
- Eight Sun StorEdge T3 arrays for the enterprise consume 28 RUs (rack units) using four 7U rackmount rails.
The T3 Rackmount Placement Matrix may be a helpful resource in this area.
Q. Can I mix Sun StorEdge A5000/A3500/A1000/D1000 arrays and Sun StorEdge T3 arrays in a Sun StorEdge 72-inch expansion cabinet?
A. No, only the Sun StorEdge T3 arrays can be configured together in a Sun StorEdge expansion cabinet at this time.
Q. How about mixing the T3(s) with an Exx00 host in the 72-inch cabinet?
A. This is possible. Check out the following links for some guidelines.
- Rackmount Placement Matrix
Q. During T3 bootup, firmware status numbers like this appear:
......
Initializing QLCF Components
Initializing Loop 1 ISP2100...firmware status 3
Detecting 20 FC-AL ports on loop 1
Initializing Loop 2 ISP2100...firmware status 3
Detecting 20 FC-AL ports on loop 2
......
What does the 3 mean? What else might it show?
A. 3 is good! See the Status Table below for the firmware status indicators.
| T3 Enterprise vs. Workgroup Comparison | ||
| T3 Enterprise | T3 Workgroup | |
| * Dual RAID controllers | * Single RAID controller | |
| * RAID Levels 0,1,and 5 | * RAID Levels 0,1,and 5 | |
| * 2 to 4 LUNs per pair | * 1 or 2 LUNs | array | |
| * StorEdge Component Manager 2.1 | * StorEdge Component Manager 2.1 | |
| * Sun Remote Services (SRS) 2.0 ready | * Sun Remote Services (SRS) 2.0 ready | |
| * 2-year Gold-level warranty | * Standard warranty | |
| * Sun StorEdge ArrayStart installation | * Customer installed | |
| * Veritas Volume Manager software | ||
| Platform Support Matrix w/Maximum Connections | ||||||
| Platform | Max T3 Direct-Attach | 18/36/73GB Disk | Max T3 Hub-Attached | 18/36/73GB Disk | Max TB | Host Bus Adapter | ||
| U60 | 4 | 0 | 2.6 TB | X6729A | ||
| U80 | 4 | 0 | 2.6 TB | X6729A | ||
| 220R | 3 | 0 | 1.9 TB | X6729A | ||
| E250 | 4 | 0 | 2.6 TB | X6729A | ||
| 420R | 3 | 0 | 1.9 TB | X6729A | ||
| E450 | 8 | 0 | 5.2 TB | X6729 | ||
| E3x00 | 16 | 64 | 42 TB | X6730A | ||
| E4x00 | 16 | 64 | 42 TB | X6730A | ||
| E5x00 | 16 | 64 | 42 TB | X6730A | ||
| E6x00 | 16 | 64 | 42 TB | X6730A | ||
| E10000 | 64 | 256 | 169 TB | X6730A | ||
| RS-232 Serial Port Female Connector (RJ11-6) | ||||
________ | |||||| | |_123456_| [ ] [____] |
PIN | FUNCTION | ||
| 1 | GND | |||
| 2 | Reserved | |||
| 3 | Reserved | |||
| 4 | GND | |||
| 5 | RXD | |||
| 6 | TXD | |||
The default Sun StorEdge T3 Volume Configuration as shipped from the factory is 9 drive RAID 5 with no standby disk. The volume is configured as follows:
Here are the rest of the default settings
| System Default Settings | ||||
| Sys Parameter | Default | Variables | ||
| blocksize | 64k | [16k | 32k | 64k] | ||
| cache | auto | [auto | writebehind | writethrough | off] | ||
| mirror | auto | [auto | off] | ||
| mp_support | none | [rw | none] Multi-pathing support | ||
| rd_ahead | on | Set to off to always perform datablock read ahead | ||
| recon_rate | med | [high | med | low] Reconstruction rate | ||
| memsize | 32 | Set by controller, read-only. In MBytes | ||
| cache memsize | 256 | Set by controller, read-only. In MBytes | ||
| Volume Default Setting | ||||
| Parameter | Default | Variables | ||
| init [rate n] | 16 | [1-16] 1 is lowest, 16 is highest | ||
| verify [rate n] | 1 | [1-8] Rate parameter refers to host interleave factor (contention with host I/Os). Default is 1. There is currently no feature that spawns a 'vol verify' process. | ||
| Boot Default Settings | ||||
| Parameter | Default | Variables | ||
| bootmode | auto | [auto | tftp | none] | ||
| bootdelay | 3 | Number of seconds | ||
| sn | {number} | Serial number | ||
| ip | 0.0.0.0 | Unit IP address | ||
| netmask | 255.255.255.0 | Unit netmask | ||
| gateway | 0.0.0.0 | Network gateway IP address | ||
| tftphost | 0.0.0.0 | IP address of tftp server | ||
| tftpfile | {value} | Boot code file identification number (39 char max) | ||
| hostname | {machinename} | Name of T3 host machine (39 char max) | ||
| vendor | {vendorname} | Name of manufacturer or vendor | ||
| model | {modelnumber} | Controller model number (set at EP level) | ||
| revision | 0{nnnn} | Controller EP revision (EP writes this value) | ||
| logto | * | [1 | * | filename] where: | 1=Forces logging to serial console | *=Directs logging daemon to direct logging as specified in the /etc/syslog.conf file. | ||
| loglevel | 3 | [0 | 1 | 2 | 3 | 4] where: | 0=No logging at all | 1=Error messages only | 2=Warning and higher messages | 3=Notice and higher messages | 4=All message levels including info | ||
| rarp | on | [on | off] | ||
| mac | {n:n:n:n:n:n} | Controller MAC address. Set by firmware | ||
| ISP Status Table | |||
| Status | Definition | ||
| 0 | ISP is waiting for configuration process to complete | ||
| 1 | ISP is waiting for ALPA assignment | ||
| 2 | ISP is waiting for port login | ||
| 3 | ISP is ready and optimal | ||
| 4 | ISP has lost loop synchronization | ||
| 5 | ISP has experienced an unrecoverable error | ||
| 6 | Reserved | ||
| 7 | ISP is not participating on the loop | ||
INTERNAL SUMMARY:
email address: charles.price@central.sun.com
SUBMITTER: Charles Price PATCH ID: 109115 APPLIES TO: Hardware, Storage ATTACHMENTS: