From: Marcin Wrobel (wrobelma@idea.net.pl)
Date: Thu Aug 22 2002 - 03:02:18 EDT
Ok, starting from begining ...
Machines: Two ES40 in ASE cluster
System: Tru64 4.0F
Systems were working fine until i realized that I cannot create an outgoing
connection from server to somewere else e.g. computer in same LAN and LAN's
gateway except second server in the cluster (but this was working over the
other set of net cards connected directly with each other between servers),
even ping wasn't working. From outside everything worked fine and I could
leave it this way but this was an accident to happen so I deciceded to get
on the bottom of this. I saw that the ASE manager which watched over both
servers through one net card connected to LAN, second net card connected
directly to second net card on second server, and over the common SCSI bus,
did not detected any errors. I have tried restarting different net daemons,
and other things but nothing seemed to work. So I decideded reboot is
necessary so I moved ASE services to second machine and booted first one.
After a boot everything was working as it should be but the ASE manager on a
second machine didn't register member down, so my first server was unable to
become again a member of ASE and I couldn't move services from second server
to working first one. Only one solution remained. Shutdown of everything on
second server and it's boot. So I did it, and it worked fine, oracle and all
apps went up and running.
Everything works now fine except minimum of two commands that I know
concerning network on second server.
1. netstat - regardless of given parameter it returns one answer:
# netstat -n
no namelist
# netstat -an
no namelist
....
2. arp - regardless of given parameter it returns one answer:
# arp -a
arp: bad namelist
I depend on information returned by netstat a lot so it's lack is making me
havy time.
Ifconfig works fine, and all possible connections and protocols work also
fine so it's not critical.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
If anyone has a clue I would appreciate some help a lot.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
And another more simple question, after a reboot I get in /var/adm/messages
info :
Jul 31 13:44:22 osiw1 vmunix: tu0: link up: negotiated 100BaseTX: full
duplex
Jul 31 13:44:36 osiw1 vmunix: tu0: link up: negotiated 100BaseTX: full
duplex
Jul 31 15:00:14 osiw1 vmunix: tu0: transmit FIFO underflow: threshold raised
to: 256 bytes
Jul 31 15:00:17 osiw1 vmunix: tu0: link up: negotiated 100BaseTX: full
duplex
Aug 1 13:55:35 osiw1 vmunix: tu0: transmit FIFO underflow: threshold raised
to: 512 bytes
Aug 1 13:55:38 osiw1 vmunix: tu0: link up: negotiated 100BaseTX: full
duplex
It goes in time up to 1024 bytes and after that its desides to bypass FIFO
and works fine without it until next reboot,
when it starts all over again. At each switch is a few seconds of blackout
in network availability which results in many alerts by users and disturbs
applications and other connected to the database systems.
If someone knows how to turn this FIFO of set it at boot time I would also
appreciate a lot.
Thanks for any help,
System / DB Administrator
Marcin Wróbel, Poland.
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:50 EDT