SEO

#1 (**permalink**) 01-16-2008, 12:52 PM

Not that I hate doing this but sometimes the docs from Sun give me a
headache trying to do the simpliest thing.

As short as I can make this, have an e4500 with the gbic option on the
501-3060, adapters, fiber cable, box runs Solaris 8.

Picked up an A5200, never seen one before. Never used one.

Hooked everything up, ran devfsadm on the e4500, did something, syslog shows
lines like this:

Jul 12 15:56:13 e4500 socal: [ID 139058 kern.info] sf0 at socal0:
socal_port 0
Jul 12 15:56:13 e4500 genunix: [ID 936769 kern.info] sf0 is
/sbus@2,0/SUNW,socal@d,10000/sf@0,0

(along with socal_port 1,2,3)

But now the stupid question, what next?

The luxadm just comes back with "No Network Array enclosures found in
/dev/es" and format sees nothing new (no surprise).

Reboot needed?

Beleive it or not, after this I can deal with the loops, raid, disk manager
and other things, but it seems I'm missing something obvious to get past the
starting line.

-bruce
bje@ripco.com

#2 (**permalink**) 01-16-2008, 12:52 PM

> But now the stupid question, what next?
>
> The luxadm just comes back with "No Network Array enclosures found in
> /dev/es" and format sees nothing new (no surprise).

Do you have a link status light on the FC-AL card?

If not, swap round the connectors, and try again...

S.

--
Steven Hill

"Neca eos omnes. Deus suos agnoscet."

#3 (**permalink**) 01-16-2008, 12:52 PM

Bruce Esquibel <bje@ripco.com> wrote:
> Picked up an A5200, never seen one before. Never used one.
>
> Hooked everything up, ran devfsadm on the e4500, did something, syslog shows
> lines like this:
>
> But now the stupid question, what next?
>
> The luxadm just comes back with "No Network Array enclosures found in
> /dev/es" and format sees nothing new (no surprise).
>
> Reboot needed?

Yes. Solaris generally has issues when you connect the first FC-AL array
like an A5200 to a host. A "boot -r" will geneally sort things out.

Scott

#4 (**permalink**) 01-16-2008, 12:53 PM

Scott Howard (scott@hunterlink.net.au) wrote:

: Yes. Solaris generally has issues when you connect the first FC-AL array
: like an A5200 to a host. A "boot -r" will geneally sort things out.

Well, that didn't help, did an early morning reboot and same results.

But I do have it figured out.

Turns out was a hole problem, had the cable going into the wrong hole on the
e4500.

We bought that thing used and never did figure out what was jammed into the
thing. It came with these db9 (sort of) to fiber adapters, with labels
saying something like RAID-1(A) and RAID-2(B).

Anyway, long story short, there is a JNI FC64-1063 card in each card along
with those adapters which are marked MDB 9-6-1.

Tis not where the A5200 plugs into.

Using a regular 370-2303-03 it works fine.

I'd guess that JNI/MDB combo is some kind of high-performace fiber thing,
but although several web pages have it for Solaris, don't really see what
drivers or software is needed to enable it/them.

So thanks to those who replied and emailed, appreciate it.

-bruce
bje@ripco.com

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

stupid e4500 and a5200 question