Re: TOP Network Interface Port of a Sun Ultra 30

On 2008-08-19, Barry L. Bond <barry@xxxxxxxxxxxxxxxxxxx> wrote:

Hi Don!

Okay! It is Tuesday morning. My hurricane shutters are up. We have
water up. And, we were already ready in every other matter, batteries,
two lanterns for our bathroom/whatever, etc.

And, there is no work today! :-)

And, at the moment, we have electricity!

So, you can imagine what I'm doing! :-D

I'll still be interrupted, from time to time, but I should have a
decent amount of time to give this, today!

Hmm ... since these posts are covering a lot beyond the Sun
hardware, perhaps you should try moving this to e-mail. My email
address is valid -- but I don't know whether you fall into the IP ranges
in Road Runner which I have blocked because of spam.

Also -- don't try sending attachments to me. I have anything
over 30K total e-mail size blocked -- before I can even see who it is
from, so I can't special case your address.

for a reconfigure boot. But the "touch /reconfigure then reboot" is
what I first learned to do with Solaris 2.x (The System 5 flavors).

And, this is exactly what I did.

I pulled the PCI card that was in there, completely out. I then put
the new card in the same slot (with the metal panel on the back already
out) and put the old one in the same electrostatic bag.

I booted, and then I did a "touch /reconfigure".

The next time I booted, here is what I got. (Again, be cautious,
though I type fairly quickly and accurately, being a software engineer,
there may be a couple of mistakes...)

<<>>
Sun Ultra 3 UPA/PCI (UltraSPARC-II 248MHz), Keyboard Present
OpenBoot 3.9, 128 MB memory installed, Serial #XXXXXXX.
Ethernet address X:X:XX:XX:XX:XX, Host ID: XXXXXXX.

[ ... ]

Can't find driver for console framebuffer

Hmm ... do you use a console framebuffer at all?

configuring IPv4 interfaces:

hme0ip_rput_dlpi(hme1): DL_ERROR_ACK for DL_ATTACH_REQ(11), errno 8, unix 0
ip_rput_dlpi(hme1): DL_ERROR_ACK for DL_BIND_REQ(1), errno 3, unix 0
ip_rput_dlpi(hme1): DL_ERROR_ACK for DL_PHYS_ADDR_REQ(49), errno 3, unix 0
ip_rput_dlpi(hme1): DL_ERROR_ACK for DL_UNBIND_REQ(2), errno 3, unix 0
ip_rput_dlpi(hme1): DL_ERROR_ACK for DL_DETACH_REQ(12), errno 3, unix 0
ifconfig: SIOCSLIFNAME for ip: hme1: no such interface
ifconfig: SIOCGLIFNETMASK: hme1: no such interface
hme1.

O.K. This must be the BugID, since your QFE should have been
hme1 through hme4.

The line from the FEH says specifically:

3) The Ultra 30 requires DC21153 Revision C. See BugID 4094903

Going to the Sun site, I did a search on "bug 4094903" and came
up with:

<http://onesearch.sun.com/search/onesearch/index.jsp?col=support-all&cs=false&rt=true&reslang=en&x=0&y=0&qt=bug+4094903>

but when I try to follow the links, it says that I need to be registered
to read those. But the description says:


======================================================================
Ultra 30 and Netra T1 200 don't power up with PCI_QFE cards
======================================================================

and your system does power up, which suggests that it is not the problem
that the BugID speaks about.

Hostname: canaan

[ ... ]

IP Filter: detaching [hme0,0] - IPv4
IP Filter: v3.4.20 detached
IP Filter: attach to [hme0,0] - IPv4
IP Filter: v3.4.20 attaching complete.
Set 0 now inactive

Since hme0 is zapped -- yes.

[ ... ]

Setting netmask of hme0 to 255.255.255.0
SUNW,hme0 : No response from Ethernet network : Link down -- cable problem?

No -- interface problem. :-)

Setting default IPv4 interface for multicast: add net 224.0/4: gateway canaan

[ ... ]

canaan console login:

Aug 19 08:13:06 canaan hme: SUNW,hme0 : No response from Ethernet network : Link down -- cable problem?
Aug 19 08:14:21 canaan last message repeated 5 times
Aug 19 08:14:24 canaan apcupsd[240]: Master not responding.
Aug 19 08:14:36 canaan hme: SUNW,hme0 : No response from Ethernet network : Link down -- cable problem?
IP Filter: attach to [hme0,0] - IPv4

Did you change the names of the /etc/hostsname.hme? to point to
hme1 and hme2?

Try the following from a booted system:

# prtdiag -v | grep 'hme'

I did the same on my Sun Blade 2000 (which uses the 'eri' interface, not
the 'hme' and got:


======================================================================
Katana:csu 20:41:05 # prtdiag -v | grep 'eri'
pci 33 +s/system-board ebus/se (serial)
okay /pci@8,700000/ebus@5/serial@1,400000
pci 33 +s/system-board pci108e,1101 (network) SUNW,pci-eri
======================================================================

So you should see five of these -- one for the hme0 in the system board,
and the other four from the qfe card.

Also -- there is this other line from the FEH:

3) Quad FastEthernet hardware uses the SUNWqfed device driver

Does your system show something to a "man qfe"? Solaris 10
does, and perhaps your Solaris 8 (IRRC) man page can show you something
to enable it again.

And there should be a /dev/qfe entry if the system recognized it
and installed it. (Hmm ... is it possible that you'll have to go back
to the install CD-ROMs to find the driver for it? Even in a system
running Solaris 2.6 (with a single port hme board in it which once had
an Sbus qfe board) I find:

======================================================================
lrwxrwxrwx 1 root root 29 May 14 2007 /dev/hme -> ../devices/pseudo/clone@0:hme
lrwxrwxrwx 1 root root 29 May 15 2007 /dev/qfe -> ../devices/pseudo/clone@0:qfe
======================================================================

And try:

ifconfig -a

and see what it lists. On the Solaris 2.6 system in question it came up with:


======================================================================
lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232
inet 127.0.0.1 netmask ff000000
hme0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
inet 10.0.0.21 netmask ffffff00 broadcast 10.0.0.255
le0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
inet 72.244.230.21 netmask ffffff00 broadcast 72.244.230.255
======================================================================

where 'lo0' is the loopback pseudo-interface, the 'le0' is the built-in
10BaseT only interface, and the 'hme0' is of course the single hme
board. Here is the only system which I have which is running a PCI qfe
board:

======================================================================
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33168
groups: lo
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x7
hme0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu1500
lladdr 08:00:20:a4:ec:69
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet 10.0.0.50 netmask 0xffffff00 broadcast 10.0.0.255
inet6 fe80::a00:20ff:fea4:ec69%hme0 prefixlen 64 scopeid 0x1
hme1: flags=8063<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
lladdr 00:03:ba:22:3a:44
groups: egress
media: Ethernet autoselect (10baseT half-duplex)
status: active
inet 72.244.230.50 netmask 0xffffff00 broadcast 72.244.230.255
inet6 fe80::203:baff:fe22:3a44%hme1 prefixlen 64 scopeid 0x2
hme2: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:03:ba:22:3a:45
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet 10.4.14.50 netmask 0xffffff00 broadcast 10.4.14.255
inet6 fe80::203:baff:fe22:3a45%hme2 prefixlen 64 scopeid 0x3
hme3: flags=8063<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
lladdr 00:03:ba:22:3a:46
media: Ethernet autoselect (none)
status: no carrier
inet 10.42.50.50 netmask 0xffffff00 broadcast 10.42.50.255
inet6 fe80::203:baff:fe22:3a46%hme3 prefixlen 64 scopeid 0x4
hme4: flags=8063<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
lladdr 00:03:ba:22:3a:47
media: Ethernet autoselect (none)
status: no carrier
inet 10.123.123.50 netmask 0xffffff00 broadcast 10.123.123.255
inet6 fe80::203:baff:fe22:3a47%hme4 prefixlen 64 scopeid 0x5
enc0: flags=0<> mtu 1536
pflog0: flags=141<UP,RUNNING,PROMISC> mtu 33168
groups: pflog
======================================================================

The output of "ifconfig -a" is a little different, because this system
(a Sun Ultra-5) is running OpenBSD instead of Solaris.

[ ... ]

Does that serial hub have RJ-45 connectors (the 8-pin version of
the modular phone connectors) for the serial ports? You got the hub,
and a bunch of RS-232 connectors with RJ-45 connectors in their backs?

Yes. Exactly. :-) RJ-45 connectors. A couple of the adapters have
little Ethernet cables, but most do not... (strange, but okay...)

If so, it was probably assumed that you would either:

1) Purchase pre-made ethernet cables of lengths appropriate for
your needs.

or

2) Get some 8-conductor phone type ribbon cable, some crimp-on
RJ-45 connectors, and a crimping tool, and make your own to
the length needed. (This is what *I* would do, and I already
have all of the above-mentioned items. ;_)

Again, exactly. Oh, Don, the way I used to be was I made a lot of my
own cables, especially serial cables. But, I just have NO TIME for "home
stuff" right now! Between my job with what ITT calls an "aggressive
schedule" and needing to help my mother more, I even said I didn't have 5
free seconds in the typical week before the lightning strike! :-O

With the 8-conductor parallel phone cable and a good crimper and
terminals it takes only moments to cut to length, strip, and crimp.
(You only strip off the outer jacket, leaving eight parallel insulated
conductors, and the pins bite through the insulation when you crimp.

Actually, two different guys at Best Buy indicated a kit with 250' of
cable and a crimper, and suggested that may be better. However, it would
have taken more time, and I just don't have that right now! :-(

Depending on the crimper -- and on whether the wire is parallel
conductor phone wire, or twisted pair for ethernet -- it could be very
easy and quick (with the parallel wires) or tedious (with the twisted
pair, which you have to untwist a length, comb out the wires in parallel
in the proper order (which is weird for ethernet connections, where the
only pins which matter are 1&2 (as a pair), and 3&6 (as another pair)
and for your RS-232 application, you mostly care that the wires connect
to the same pins on both ends. :-)

The best crimper in my experience is the one made by AMP, which
includes both a cut-off-square feature, and a strip-to-the-right-length
feature for the parallel conductor ribbon cable.

Today, in the several different times my mother and I were home,
between trips out for various things, I started one thing from the
lightning strike that hadn't been done yet: the stereo receiver box.

O.K. Did you check to see whether it was just a fuse? Though
the electronics in a receiver box would be fairly sensitive to lightning
damage -- and more so if it were connected to an external antenna.

Yes, I did. I looked in the manual and carefully looked over the
back of it. There was none that I could see.

Hmm ... does it have a captive power cord, or one of the
plug-into-a-receptacle-on-the-back style? if the latter, look closely
at that. If it is more than just barely big enough for the connector,
you may see a pair of edge lines which hint that with the cord unplugged
you can get a small screwdriver or a knife blade under it and pull out a
fuse holder.

[ ... ]

I do disconnect antennas, especially if we're getting reasonably
close lightning.

Good!

Somewhat surprisingly, rain and wind with hurricanes don't often
really have much in the way of lightning. We have "regular" thunderstorms
(several times a week, this time of year) that are HORRIBLE with
lightning.

Interesting.

Actually, my TV antenna is in my attic. None of our three TVs appear
to have any "post lightning-strike" problems.

O.K. That helps -- unless it attracts lighting through the
roof, in which case you get a fire. :-(

I mounted the antenna in the attic, and ran my coax down to wall
plates I had drilled. (I used to have time for that type of thing!) :-O

My outside things are a scanner antenna and an antenna for my
Heathkit GC-1000, and another mast is mounted on the mast that has the
scanner antenna (which is right at the back of the house), and at the top
of it is... er... WAS the wind sensor. :-D

As long as that tower is well grounded, it will probably pull
the lightning away from the house

[ ... ]

The antenna for my Heathkit GC-1000 is a long wire. I have a mast,
but this mast is at the very back of my yard and not close to the house.
And, the other end is connected to a mast which is mounted to the side of
my house and sticks up about five feet. And, the single long wire goes
between these two masts.

GC-1000? A general communications receiver? I'm trying to
remember when Heathkit folded.

[ ... ]

The GC-1000 is something I purchased in the early 1980's, and it's
been great, though it died a few months ago, and I haven't done anything
about it yet.

Early 80's? Then solid state, not tube based I guess?

[ ... ]

I do not currently have a working GC-1000 (and it's SO OLD...)...

But you should have good documentation for it, if you kept all
of the kit instructions.

[ ... ]

But, anyway, that is a summary of my antenna situation.

More than I needed to know for this purpose.

The scanner antenna is attached to the edge of my roof, about five or
six FEET from the entertainment center. On top of that is the mast that
had the wind anemometer on top of it.

And how well grounded is that?

I suspect that the anemometer was the point of direct hit by
the lighting, and the path into everything else. Mine has a heavy (8
gauge) wire going down the chimney to a separate ground stake. Still
not enough to keep it from frying the RS-232 port on the computer which
was watching it at the time.

Wow, and as you say, ouch!

It was a Windows/MS-DOS box. Long gone.

I have a ground cable attached to a ground rod beside my house which
is run up into the attic. The TV and another, though smaller, wire from
the inside connection of the wind anemometer where it connects to the
junction box is attached to it.

How heavy a ground wire? With lightning, I'm not *really*
comfortable even with the solid 8 gauge copper wire.

I hope it turns aside. I gather that you are somewhere in
Florida? Usually, by the time hurricanes make it up here (near
Washington DC) things are pretty mild, except for a lot more rain than
usual.

Yes. I'm east of Orlando, and about 40 miles from the eastern coast
of Florida.

The projected paths mostly pass North of you -- except for one.
:-(

I'll be looking through my sysadmin manuals and trying to figure out
what I can do with this new card! :-) (I know, you're going to remind me
about that BugID...) :-/

And I *think* that it is not the BugID in particular, since the
system did power up, but perhaps a lack of a driver for it. If the
system sees it, it should show up all the ports in the output of

ifconfig -a

and this may tell you what hme names it has been allocated. You may
have to rename the /etc/hostname.hme? files again to reach them.

Good Luck,
DoN.

--
Email: <dnichols@xxxxxxxxxxx> | Voice (all times): (703) 938-4564
(too) near Washington D.C. | http://www.d-and-d.com/dnichols/DoN.html
--- Black Holes are where God is dividing by zero ---
.

Relevant Pages

  • Re: FAQ: rec.audio.* Wire 2/99 (part 8 of 13)
    ... speaker cables and equipment ... thanks to Steve Lampen of Belden Wire & Cable Co. ... signals into audible signals. ... What can I use for budget speaker connectors? ...
    (rec.audio.opinion)
  • Re: Tech: TZ
    ... the playfield that was not connected. ... linkage hits when the UR flipper isn't activated. ... Now, as to a brn/red wire, according to the book, Brn-Red is the ... * Replaced normal burned out GI connectors on driver board. ...
    (rec.games.pinball)
  • Re: Gottlieb System 1 Adventures with Sinbad
    ... hole to thread the wire through then solder. ... Trying to figure out what connectors you're talking about though, ...
    (rec.games.pinball)
  • Re: Lightning Protection questions
    ... It's not that lightning wants to go straight. ... The concept is called wire impedance. ... the cloud will arc to water? ... only feet from the grounding plate, then lightning will still go to ...
    (rec.boats.cruising)
  • Re: Lightning protection
    ... Lightning is not some DC ... >> that of the surge arrester will be impressed across the ... I wonder why they specify insulated wire. ... An external ground wire would be easy to inspect and less likely to be ...
    (sci.electronics.repair)
Loading