Hello listers,
We have two SLES10 guests running SAMBA. The two machines should be
identical, and in VM they are.
The production machine has two network interfaces defined, F00 and F10.
The first is the network for regular connections, the second is the
connection to our TSM backup server.
Th
Seems some operational hiccup if you got the configs right. What does lsqeth
tell you about the state of the nics?
Best regards,
Pieter Harder
Van: Linux on 390 Port [linux-...@vm.marist.edu] namens van Sleeuwen, Berry
[berry.vansleeu...@atosorigin.com]
2010/2/15 van Sleeuwen, Berry :
> The test machine can't start the connection for TSM backup. ifconfig
> shows only eth0. The f10 device is indeed available but for some reason
> it isn't started. I have compared the two guests but can't find a
> difference that could tell me why this networkinter
Only one nic, eth0. No information on eth1. The production server shows
both eth0 and eth1.
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Harder, Pieter
Sent: maandag 15 februari 2010 12:04
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Location of net
Barry,
> The /etc/sysconfig/hardware contains identical entries.
Are they really identical?
I have a system with two interfaces connected to NICs at 600 and 700. The
/etc/sysconfig/hardware configuration files are different:
# cat /etc/*release
SUSE Linux Enterprise Server 10 (s390x)
VERSION = 10
No, ifup doesn't start it. It should be on eth1 but eth1 is not
available.
The module parameter was missing at first, so I added the MODULE='qeth'
but is made no difference.
I have tried /etc/sysconfig/network/ifcfg-qeth-bus-ccw-0.0.0f10 with
ETHERDEVICE='eth1' and, as listed in the production se
Sorry, I mean the directories on the two servers are identical.
Obviously, the configuration for device f00 is not the same as for f10.
But the f00 for the production samba is the same as the f00 for the test
server. And the same goes for the f10 configuration. Well, that is, the
IP address is diff
Berry,
there is a known problem (race in udev) in activation of network
interfaces. Details can be found in Novell-bugzilla number 506571.
Regards, Ursula Braun, IBM Germany, Linux on System z development
On Mon, 2010-02-15 at 11:55 +0100, van Sleeuwen, Berry wrote:
> Hello listers,
>
> We have
I can't access bugzilla so I can't look into the details.
Anyway. Since a race could be a problem here I have rebooted the guest.
And indeed now the eth1 is available. And since it is available the
network is started. In the near future we have to restart guests quite a
bit so I'll have to check t
Correct. Ifup command will not make it permanent. There is a pretty good step
through in here starting at page 97. This is for HiperSockets but it works the
same.
www.redbooks.ibm.com/redbooks/pdfs/sg246816.pdf
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist
We had a situation the other day where one of our z10's was taking
"thermals" for lack of a better word. The kernel dutifully reported:
Feb 11 15:08:29 zsles10sp3ctl kernel: sclp_config: cpu capability
changed.
sclp_config: cpu capability changed.
The CE replaced
11 matches
Mail list logo
