v440 can't see T3s 2

[maximusGeek]

I have a v440 with 2gb HBA's and 2 T3s but I can't see them in format.

SAN 4.4.11 installed
Solaris 9 9/05 HW

My understanding is I can use the 2GB HBA's with the T3's as long as I am using a recent version of the SAN foundation.

Any suggestions?

 

[djr111]

I ran into this years back.

Do you have these 2 pkgs loaded. In addition to the SUNWsan pkg.

SUNWqlc,SUNWqlcx

You can probably get these off the Solaris CD/DVD



hope this help
-David

 

[maximusGeek]

Yes, I do

Sun Microsystems Inc. SunOS 5.9 Generic May 2002
# pkginfo SUNWqlc
system SUNWqlc Qlogic ISP 2200/2202 Fibre Channel Device Driver
# pkginfo SUNWqlcx
system SUNWqlcx Qlogic ISP 2200/2202 Fibre Channel Device Driver (64 bit)

 

[cndcadams]

bjensen210;

Have you done a prtdiag -v to see if the HBA's are seen by the OS. If the t3's were not configured with luns from the vendor then you will not see them under format. I am not sure if SAN software will recognize them if no configuration either as I did not have a need to run the SAN software on my test beds.

How are you configuring the units, partner pair or individual?

What you can try is;

Make sure you plug ethernet cable in.

On the T3 there is a pull out tab located on the left inside of the chassis. There is a mac address for the T3 on that tab. Put the mac address and give it a name in /etc/ethers, then edit /etc/hosts and give it ip address and name which you put into etc/ethers. Power on the T3, wait a little bit and then see if you can telnet to the T3. login is root and there hopefully is no password.

Or if you received all kit parts for the t3 (if this is t3+ is has an rj45 port) there should be a 6 pin cable with mod-taps. Attach the 6 pin cable to the t3 com port and the mod-tap to serial port on your server and run tip hardwire. Power on the T3 and see if you get output.



Below doc is something I put together for a class I was teaching, some of the doc would not show up correctly so if you email me at cndcadams@aol.com I will email you back the word doc that shows the pin outs for the com port.

T3 Server Setup for Communications
Thru the Ethernet Port

Step 1 configuring the host to recognize the T3 thru the ethernet port.

1) Locate the T3 Mac address. You will find the address on a pull-out tab located on the front left side of the T3. (EX MAC 00:20:f2:00:4E:2B)

2) On your host system edit (vi) the /etc/ethers file and add an entry for the T3 (must include T3 mac/ether address and T3 name which you supply).

3) On your host system edit (vi) the /etc/hosts file and assign and IP address and T3 name for the T3. The name needs to be the same as in /etc/ethers.

4) Run command ps –eaf | grep rarpd. This is the RARP daemon. If it is not running execute the following command

a. /usr/sbin/in.rarpd –a & <return>
5) Plug Ethernet cable into T3 and hub/router/switch, which is on the same subnet as your host.

Step 2 Gaining access to the T3

1) Power on the T3, allow time for unit to boot up (2 minutes tops)

2) On the host run the following command
a. telnet (name you gave to your t3) <return>

3) You should be at the login prompt for the T3




T3 Administration Thru the Com Port

Step 1 Cables and adaptor information

1) Connecting to T3 com (serial) port. Used with tip hardwire command for both
low level and OS level administration and troubleshooting.
The T3 controller card has an RS-232 serial port connector (RJ11-6). A standard serial
cable is used to connect the controller service interface to a dumb terminal or computer
serial port with terminal emulation.


The T3 is receiving on pin 5, transmits on pin 6, and ground is pin 1
The Sun System Serial port (ex.. E4500) receives on pin 3, transmits on pin 2, and ground is pin 7

We have the straight thru cable connected to the T3 RJ11-6 port, on the other end it is connected to the RJ11-6 port on the Adaptor which is connected to the serial port B on the Sun server. The cable setting for the Mod Tap are below (Be aware that the straight thru cable wire colors do not correspond to the wire colors Inside the Mod Tap (DB25/RJ11-6 adaptor).

T3 com portPin 6 Transmit5 Receive4321 Ground Mod Tap DB25 Adaptor with RJ11-6 connector Pin6 White goes to pin 35 Black goes to pin 24 Red none3 Green none2 Yellow none1 Blue goes to pin 7

REF for Pin outs for most Sun Microsystems Computers

http://www.stokely.com/unix.serial.port.resources/A-B-Ycablepinout.html

2) Once cables are attached run the following command on the host system;
a. tip hardwire <return>

3) Power on the T3 and you will see the bootup, if the system is up and running you will be at either the login prompt or T3 CLI interface.

4) If the T3 does not boot you can set it up to boot from tftp. (You will need to configure a TFTP Boot server for this).

Configuring a TFTP Boot Server

Step 1 Configuring the Boot Server.

1) cd /

2) mkdir /tftpboot

3) chmod 755 /tftpboot

4) Download the latest T3 patch(109115-17 as of 5/22/05) from Sun to /tftpboot directory

5) Uncompress the patch if a .Z, then tar xvf the patch.tar file

6) cd into the patch directory(ex. cd /tftpboot/109115-17) just created and cp the latest firmware (v1184.bin) back to the /tftpboot directory.

7) chmod 444 /tftpboot/firmware_file (ex. chmod 444 /tftpboot/v1184.bin

8) Edit the /etc/inetd.conf file, uncomment the following line to enable the tftp boot server (remove the # at the start of line):
a. tftp dgram udp wait root /usr/sbin/in.tftpd in.tftpd –s /tftpboot
9) Restart the inetd daemon.
a. ps –ef | grep –I inetd
b. kill –HUP process #

10) Locate the T3 Mac address. You will find the address on a pull-out tab located on the front left side of the T3. (EX MAC 00:20:f2:00:4E:2B)

11) On your host system edit (vi) the /etc/ethers file and add an entry for the T3 (must include T3 mac/ether address and T3 name which you supply).

12) On your host system edit (vi) the /etc/hosts file and assign and IP address and T3 name for the T3. The name needs to be the same as in /etc/ethers.

13) On your host system edit (vi) the /etc/hosts file and assign and IP address and T3 name for the T3. The name needs to be the same as in /etc/ethers

14) Run command ps –eaf | grep rarpd. This is the RARP daemon. If it is not running execute the following command

a. usr/sbin/in.rarpd –a & <return>

15) Attach the serial cable to the RS-232 port on the Sun StorEdge T3 Array, and establish a tip hardwire session so that you can monitor the tftpboot process.

16) Power cycle the T3 Array and , during the EPROM boot delay (three seconds), press the Return Key to access the EPROM prompt.

a. T3-EP>

17) Using the set command, change the configuration to match the following;
a. T3-EP>set bootmode tftp
b. T3-EP>set tftphost server_ip
c. T3-EP>set tftpfile t3-fimware-file (ex. set tftpfile v1184.bin)
d. T3-EP>set ip t3_ip_address(you assigned this)

18) Type boot at the T3-EP>prompt. The T3 should start booting the firmware file.

19) Once the T3 has booted, login is root with no password. You will then need to set a root password. Command as follows on T3

a. T3:/:<1>passwd root (it will prompt you for the old password hit enter, then new password, assign a password).

20) On your boot server cd to /tftpboot/T3patch# <return> (ex. /tftpboot/109115-17)
a. Execute the t3.sh script, you will be prompted for system name, then login and password. Take default file for loading. This script will download all firmware files etc to the T3.

21) You will need to place a copy of the RAID controller firmware in the system area reserved on all the disks in the master controller unit of the T3, enter:
a. T3:/:<1>boot –i t3_firmware_file (ex. boot –I v1184.bin)
b. T3:/:<1>set bootmode auto
c. T3:/:<1>reset –y

22) T3 will reboot and boot off the latest firmware.



Thank you;

Christopher J. Adams

 

[KenCunningham]

That, sir, deserves a star for effort and detail even if it doesn't resolve the issue!!

I don't mind people who aren't what they seem. I just wish they'd make their mind up.

 

[maximusGeek]

Thank you for your detailed responce. I feel bad that I did not post again sooner but they problem has been resoved. The operator at my remote site re-seated everything and now I can see my RAIDs.