SUMMARY:wierd LAT problem
From: dominic christopher (dominicfree_at_yahoo.com)
Date: 06/25/03
- Previous message: MMP Rupp Wolfgang: "WindowMaker and mouse settings"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 25 Jun 2003 02:49:42 -0700 (PDT) To: tru64managers <tru64-unix-managers@ornl.gov>
Hello MAnagers,
Thanks to ,Phil ,Selden & Dr T.Blinn for following
suggestions .
The Problem:
A AS300 Asplaserver , with Tru64 4.0F , had a
CPU panic problem , so i changed the Motherboard.
Note: i just replaced the motherboard& RAM, taking
care to restore the SRM variables .
Before replacing the mother board , Dumb terminals
connected to DEC90l+ terminal servers on this
network
could just connect to this AS300 using lat command
at
terminal server prompt , "c hostname" .
I now get a "service unavailable " message .
Now i can connect to all other servers using the
same dumb terminal and 90l+.
The said AS300 is accessible through telnet ,and
from IP based terminal servers .
Suspecting a LAT config issue on the AS300 , i
checked the LAT service using the latcp -d command
lat is running , inittab is OK , rc.config is OK.
LAt subsets are OK .
Using latsetup i just undid and redid the lat config
but no luck.
Is there anything else i'm missing
Dominic
When you run tcpdump on another system can you
see any LAT packets
coming out of the AS300, it should be
broadcasting a LAT 'id' packet to
advertise its LAT service.
If it is broadcasting then check things like
group.
Phil
I'd guess that the terminal servers have cached the
previous
MAC address associated with the LAT service on the
system and
your system's MAC address has changed.
Most motherboards have a removable plug-in ROM that
contains the Ethernet hardware (MAC) address.
I don't know if the AS300 does. It's a little late
now,
but you should see if you can exchange that address
chip between the two systems.
Alternatively, have you tried resetting one of the
terminal servers
to see if that solves the problem? I suspect it will.
I hope this helps a little.
Selden
Is the Ethernet on the motherboard on
that system? If so,
you've changed the Ethernet address, and
the terminal server
may well know the hard Ethernet address.
Just a guess, but..
- Dr T.Blinn
Conclusion :
It was possibly a MAC address issue , since i had
changed
the Riserboard along with the motherboard ,and the
riser
board contains the ethernet cktry with the MAC address
.
Moreover since the motherboard & riser board were a
few
minutes earlier associated with a different LAT
service
the 90l+ terminal servers ,coukld have taken time to
relearn the change.
__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
- Previous message: MMP Rupp Wolfgang: "WindowMaker and mouse settings"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
