> -----Original Message-----
> From: centos-bounces@xxxxxxxxxx [mailto:centos-bounces@xxxxxxxxxx] On
> Behalf Of Angelo Machils
> Sent: Monday, April 25, 2005 2:43 PM
> To: centos@xxxxxxxxxx
> Subject: RE: losing NFS connection
> >>
[snip]
> >
> >Just a thought but have you hard-coded speed and duplex all the way
> >through? Don't trust auto-negotiation.
>
> I have opened the firewall on the server all the way for the client
(and
> also the other way around) but it makes no difference. After a while I
> see these messages again in the /var/log/messages on the client:
> Apr 25 21:38:02 solaris kernel: RPC: garbage, exit EIO
> Apr 25 21:38:33 solaris last message repeated 70 times
> Apr 25 21:39:34 solaris last message repeated 122 times
> Apr 25 21:40:01 solaris last message repeated 55 times
> Apr 25 21:40:01 solaris crond(pam_unix)[4701]: session opened for user
> root by (uid=0)
> Apr 25 21:40:01 solaris crond(pam_unix)[4701]: session closed for user
> root
> Apr 25 21:40:02 solaris kernel: RPC: garbage, exit EIO
> And this keeps repeating...... No entries on the server though.....
>
> Which file do I have to edit in order to set the NIC into fixed state.
I
> know that I can use mii-tool to check and set, but is this permanent,
> even after a reboot?
It varies but mii-tool changes will be lost on reboot. There are several
ways of getting around that from simplest to hardest --
- Add '/sbin/mii-tool -F 100baseTx-FD' to /etc/rc.local
- Add '/sbin/mii-tool -F 100baseTx-FD ${DEVICE}' to
/etc/sysconfig/network-scripts/ifup-post
- research your card driver and add the appropriate arguments in
/etc/modules.conf.
I almost always opt for the first option. As has been previously noted,
you must make sure that the switch, hub or router that you are connected
to is also forced to the same speed and duplex.
--
Marc
