Dave,
after reboot your OSA interfaces can be 'dead', because
1. problem in OSA-device configuration
2. just a missing gateway
After reboot invoke from the HMC-console
lsqeth -p
to check if OSA-devices are available and
route
to check if the default gateway is defined.
And what
Thanks Ron,
I have the integrated ascii console working now.
Dave
Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
805-662-6731
david.stu...@ventura.org
Ron Foster at Baldor-IS rfos...@baldor.com 7/21/2009 11:29 AM
Dave,
The HMC ASCII Console is enabled inside
Dave,
you can try to setup a qeth device manually at your HMC console using
these steps:
1. Check with lscss, if the subchannel triplet (0.0., 0.0.xxxy,
0.0.xxxz) of your OSA-device is available.
2. Define the ccwgroup device with:
echo 0.0.,0.0.xxxy,0.0.xxxz
On Wed, Jul 22, 2009 at 10:19 AM, Ursula Braunubr...@linux.vnet.ibm.com wrote:
4. Activate the network interface:
ifconfig eth0 ip.ad.dr.es netmask aa.bb.cc.dd
Don't forget the default route if your PC is not on the same subnet as
the Linux guest (in most real world situations it is not)
Thanks Ursula,
I managed to get one of the connections back up and working.
The echo in step 2 failed with a message -bash: echo: write error: Invalid
argument. But I went ahead with step 3, echo 1 ... /online, and then step 4,
ifconfig eth0, and then added the default route as suggested
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
On 7/22/2009 at 11:48 AM, David Stuart david.stu...@ventura.org wrote:
-snip-
Not being all that familiar with linux, or having the time to work with it
and really learn it, I have a tendency to use Yast(2). However, I apparently
shouldn't use Network Manager...
Absolutely. As it is
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
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
On 7/22/2009 at 12:44 PM, David Stuart david.stu...@ventura.org wrote:
Hi Mark,
Yes, I did. After the problem originally occurred. Both OSA interfaces
were 'dead'.
Have you gone back into YaST to switch from Network Manager to traditional
mode?
Mark Post
Mark,
I think so. Now when I go in to Yast, Network Devices, Network Card, it shows
Traditional Method with ifup as the management selection.
If I look at the interfaces through there, they look correct. However, I can
only seem to get one interface active at any given time. And it's not
David,
When you say, you have to connect to the system via the HMC, are you
talking about the operating systems messages interface or the ASCII
console interface?
You say both ports. This implies more than one interface. What is your
default route set to in /etc/sysconfig/network/routes? Is
and the operation of it,but do you have an
HMC from which you reboot/ipl from?
You should be able to go to it and activate the osa cards.
Good Luck
Mace
--- On Tue, 7/21/09, Ron Foster at Baldor-IS rfos...@baldor.com wrote:
From: Ron Foster at Baldor-IS rfos...@baldor.com
Subject: Re: OSA/Express
Hi Ron,
I am using the HMC, Operating System Messages, which limits what you can do.
I'll check out the ascii console.
Yes, I have two ports. I have two OSA/Express cards in the System. One port
on each card is ethernet, the other is OSA-ICC. The ethernet ports on both
cards are shared
have an
HMC from which you reboot/ipl from?
You should be able to go to it and activate the osa cards.
Good Luck
Mace
--- On Tue, 7/21/09, Ron Foster at Baldor-IS rfos...@baldor.com wrote:
From: Ron Foster at Baldor-IS rfos...@baldor.com
Subject: Re: OSA/Express Assistance
To: LINUX-390
On 7/21/2009 at 2:08 PM, David Stuart david.stu...@ventura.org wrote:
Mace,
Oh, I hope a POR isn't required. The OSA/Express cards are shared across
multiple LPARs...
I doubt very much that a POR will be needed. What does ifconfig -a and
lsqeth show you?
Mark Post
Dave,
The HMC ASCII Console is enabled inside of Linux with the following in
/etc/inittab. The mingetty line comes commented out.
#
# z900 LPAR SE/HMC VT220/Linux console - uncomment to enable getty on it:
#
2:2345:respawn:/sbin/mingetty --noclear /dev/ttyS1 linux
Then once you have done a
, 2009 1:26 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: OSA/Express Assistance
On 7/21/2009 at 2:08 PM, David Stuart david.stu...@ventura.org wrote:
Mace,
Oh, I hope a POR isn't required. The OSA/Express cards are shared across
multiple LPARs...
I doubt very much that a POR will be needed
On 7/21/2009 at 2:32 PM, Moody, Craig craig.mo...@lrs.com wrote:
I have reset OSA ports by using the OSA Advanced Facilities dialog in the
HMC.
I really don't think that will be needed either. Everything so far just points
to messed up configuration files.
Mark Post
Afternoon,
set Newbie Alert
I am not all that experienced with Linux, and I haven't worked with it for a
while, and I have proceeded to shot myself in the foot. Maybe both feet.
Sles 10 SP 2 running 'native' in an LPAR (no, no z/VM (yeah, I know!)) - Using
Yast Network Manager, I have
20 matches
Mail list logo