Unix Technical Forum

Re: E450 / Solaris 2.7 network problems

This is a discussion on Re: E450 / Solaris 2.7 network problems within the Sun Solaris Hardware forums, part of the Solaris Operating System category; --> Andrew Tyson wrote: > > Hi, > > Recently (in the last week or so) an unusual network issue ...


Go Back   Unix Technical Forum > Unix Operating Systems > Solaris Operating System > Sun Solaris Hardware

Register FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 01-16-2008, 11:09 AM
Griff Miller
 
Posts: n/a
Default Re: E450 / Solaris 2.7 network problems

Andrew Tyson wrote:
>
> Hi,
>
> Recently (in the last week or so) an unusual network issue has affected an
> E450 at my work.


Andrew, the first thing to check is to make sure the autonegotiation settings
agree on both ends of the wire. Make sure that both the E450 and Cisco
are set to autonegotiate 10/100 and half/full-duplex, OR hardwire both
ends to the same settings. I prefer the former, myself (auto).

Also, check to see if there are patches in Solaris 7 for the hme driver.
The recommended cluster may not include them.

Good luck!

--
Griff Miller II | |
Manager of Information Technology | If you're too open-minded, |
Positron Corporation | your brains might fall out. |
griff.miller@positron.com | |
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 01-16-2008, 11:10 AM
Andrew Tyson
 
Posts: n/a
Default Re: E450 / Solaris 2.7 network problems

> Andrew, the first thing to check is to make sure the autonegotiation
settings
> agree on both ends of the wire. Make sure that both the E450 and Cisco
> are set to autonegotiate 10/100 and half/full-duplex, OR hardwire both
> ends to the same settings. I prefer the former, myself (auto).
>
> Also, check to see if there are patches in Solaris 7 for the hme driver.
> The recommended cluster may not include them.


Griff,

We actually went through all this ..played with /dev/hme settings, installed
patches ... to no avail.

In the end a kind soul hit the nail on the head. The problem turned out
being a
reverse DNS issue with DHCP allocated machines on our LAN. Updating
/etc/resolv.conf and including the local DNS host fixed the problem. The
wierd
thing was that the file had not been changed for months, and suddenly the
problem
appeared. We think that it may be related to some change with the DNS from
our
ISP.

Thanks and regards,
Andrew


Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 04:41 AM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.2.0
www.UnixAdminTalk.com