Hi all,


Just got three new T3s and set them up to run off my E3500. Configured

all the T3s through telnet just fine (I think). Basically all are set
up as RAID 5 volumes. I've got each one of them assigned to different
ports (3,4,5). Problem is when I try to find them over the fiber
connection the 3500 doesn't see them. All volumes on the t3s are
mounted (a la: vol mount volname from the telnet connection to the
T3s).


A bit about the config:


The E3500 does not have internal connections for the internal drives.
The machine, while it has internal drives, basically is from what I
understand a small two controller disk array that is run out the back
and back into the back of the machine into the I/O Board. So, lacking
additional GBICs on this box, I've got the internal drives coming out
of the back of the box and going into a fiber hub. Each of the T3s are

also plugged into the hub. The hub has dual lines coming out of it and

into the two GBICs on the E3500's I/O board. All lights on the T3s are

green. Lights on the back of the hub are all green.


The internal drives are managed using DiskSuite 4.1 (I think that's the

rev) and the root volumes are mirrored and a total of six drives are
RAID 5. All is working fine there even with the clugy way I put it
through the hub.


So, the box is up and running off of the internal drives through the
hub. However, I can't, for the life of me, figure out why the 3500
isn't seeing the T3s.


Here's what I've done so far (post a reboot -rv from OK prompt):
1) mkdir /dev/es
2) luxadm insert


-- No new devices


3) luxadm probe


-- Finds the internal Fiber drives just fine


4) format


-- Finds the internal Fiber drives just fine


5) ls -rtl /dev/rdsk


-- Turns up nothing new


6) I've reconfigured the devices directory as root:
drvconfig
devlinks
-- No Dice
devfsadm
-- No Dice


The thing that smells fishy is some messages that I'm getting during
the boot cycle that may or may not be related. I'm just getting to
know the hardware and if anyone has some pointers, I'd much appreciate
them. The strange messages I'm getting at boot are (copied from
/var/adm/messages):
Jun 23 16:37:13 jake socal: [ID 403145 kern.info]
ID[SUNWssa.socal.link.5010] socal0: port 0: Fibre Channel is OFFLINE
Jun 23 16:37:13 jake socal: [ID 403145 kern.info]
ID[SUNWssa.socal.link.5010] socal0: port 1: Fibre Channel is OFFLINE
Jun 23 16:37:13 jake socal: [ID 403145 kern.info]
ID[SUNWssa.socal.link.6010] socal0: port 0: Fibre Channel Loop is
ONLINE
Jun 23 16:37:13 jake socal: [ID 403145 kern.info]
ID[SUNWssa.socal.link.6010] socal0: port 1: Fibre Channel Loop is
ONLINE
Jun 23 16:37:13 jake scsi: [ID 243001 kern.info]
/sbus@2,0/SUNW,socal@d,10000/s*f@1,0 (sf1):
Jun 23 16:37:13 jake ELS 0x3 recvd from target 0x7d
Jun 23 16:37:13 jake scsi: [ID 243001 kern.info]
/sbus@2,0/SUNW,socal@d,10000/s*f@0,0 (sf0):
Jun 23 16:37:13 jake ELS 0x3 recvd from target 0x7c
Jun 23 16:37:13 jake scsi: [ID 243001 kern.info]
/sbus@2,0/SUNW,socal@d,10000/s*f@1,0 (sf1):
Jun 23 16:37:13 jake ELS 0x3 recvd from target 0x7d
Jun 23 16:37:13 jake scsi: [ID 243001 kern.info]
/sbus@2,0/SUNW,socal@d,10000/s*f@0,0 (sf0):
Jun 23 16:37:13 jake ELS 0x3 recvd from target 0x7c
Jun 23 16:37:13 jake scsi: [ID 243001 kern.info]
/sbus@2,0/SUNW,socal@d,10000/s*f@1,0 (sf1):
Jun 23 16:37:13 jake ELS 0x3 recvd from target 0x7d
Jun 23 16:37:13 jake scsi: [ID 243001 kern.info]
/sbus@2,0/SUNW,socal@d,10000/s*f@0,0 (sf0):
Jun 23 16:37:13 jake ELS 0x3 recvd from target 0x7c
Jun 23 16:37:13 jake scsi: [ID 243001 kern.info]
/sbus@2,0/SUNW,socal@d,10000/s*f@1,0 (sf1):
Jun 23 16:37:13 jake ELS 0x3 recvd from target 0x7d
Jun 23 16:37:13 jake scsi: [ID 243001 kern.info]
/sbus@2,0/SUNW,socal@d,10000/s*f@0,0 (sf0):
Jun 23 16:37:13 jake ELS 0x3 recvd from target 0x7c
Jun 23 16:40:51 jake smt: [ID 272566 kern.notice] smt0: nf FDDI driver
is not active. Initialization of this driver cannot be completed.
Jun 23 16:40:52 jake krtld: [ID 995402 kern.notice]
/platform/sun4u/kernel/drv/spa*rcv9/rmclomv: undefined symbol
'pmugpio_watchdog_pat'
Jun 23 16:40:52 jake krtld: [ID 472681 kern.notice] WARNING: mod_load:
cannot load module 'rmclomv'
Jun 23 16:40:52 jake krtld: [ID 995402 kern.notice]
/platform/sun4u/kernel/drv/spa*rcv9/rmcadm: undefined symbol
'pmugpio_reset'
Jun 23 16:40:52 jake krtld: [ID 472681 kern.notice] WARNING: mod_load:
cannot load module 'rmcadm'
Jun 23 16:44:14 jake smt: [ID 272566 kern.notice] smt0: nf FDDI driver
is not active. Initialization of this driver cannot be completed.
Jun 23 16:44:15 jake krtld: [ID 995402 kern.notice]
/platform/sun4u/kernel/drv/spa*rcv9/rmclomv: undefined symbol
'pmugpio_watchdog_pat'
Jun 23 16:44:15 jake krtld: [ID 472681 kern.notice] WARNING: mod_load:
cannot load module 'rmclomv'
Jun 23 16:44:15 jake krtld: [ID 995402 kern.notice]
/platform/sun4u/kernel/drv/spa*rcv9/rmcadm: undefined symbol
'pmugpio_reset'
Jun 23 16:44:15 jake krtld: [ID 472681 kern.notice] WARNING: mod_load:
cannot load module 'rmcadm'
Jun 23 16:46:12 jake smt: [ID 272566 kern.notice] smt0: nf FDDI driver
is not active. Initialization of this driver cannot be completed.
Jun 23 16:46:12 jake krtld: [ID 995402 kern.notice]
/platform/sun4u/kernel/drv/spa*rcv9/rmclomv: undefined symbol
'pmugpio_watchdog_pat'
Jun 23 16:46:12 jake krtld: [ID 472681 kern.notice] WARNING: mod_load:
cannot load module 'rmclomv'
Jun 23 16:46:12 jake krtld: [ID 995402 kern.notice]
/platform/sun4u/kernel/drv/spa*rcv9/rmcadm: undefined symbol
'pmugpio_reset'
Jun 23 16:46:12 jake krtld: [ID 472681 kern.notice] WARNING: mod_load:
cannot load module 'rmcadm'


Help? Please!


Thanks in advance.


sar