Hi Mark, Yes, I did. After the problem originally occurred. Both OSA interfaces were 'dead'.
And I tried again after I reviewed the interface files after going through Ursula's procedures. After reboot, both were 'dead' again. I had to go through Ursula's procedures again to get it back. Right now, only one OSA interface is 'active', meaning that I can connect to it and it will answer a ping. The other is non-responsive. I'm not sure where to go next. When I look at the Network Device through Yast, everything looks correct. But there is something somewhere. I just haven't found it yet. Not knowing where to look, or what to look for, doesn't help much, either. Dave Dave Stuart Prin. Info. Systems Support Analyst County of Ventura, CA 805-662-6731 david.stu...@ventura.org >>> "Mark Post" <mp...@novell.com> 7/22/2009 9:34 AM >>> >>> On 7/22/2009 at 12:22 PM, David Stuart <david.stu...@ventura.org> wrote: > Ursula, > > The config files you pointed out exist for both OSA ports. But I am not > sure what should be in them. Besides the ip address and netmask. I have > pasted the files for one of the OSA interfaces below. Sorry for my > ignorance, but what am I looking for? What should be in the config file? Both of those look fine. By any chance did you try rebooting the system after your network dropped? Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
