On Wed, Nov 9th, 2011 at 3:44 PM, Alan Altmark wrote:
> > Just because the current crop of security weebles don't "get it" does
> > not a true problem make.
>
> Eh?
LOL.
Should it come to pass that Alan and I are once again in the same bar
imbibing the best of Aussie brews/wine, I must remember
On Wednesday, 11/09/2011 at 12:19 EST, "Martin, Terry R. (CMS/CTR) (CTR)"
wrote:
> We just set up a 10GB OSA network and we are planning to use Jumbo
Frames. Is
> there anything that I need to do on the VSWITCH to allow for Jumbo Frame
> transfers ?
No, there's nothing to configure.
Alan Altmark
Hi
We just set up a 10GB OSA network and we are planning to use Jumbo Frames. Is
there anything that I need to do on the VSWITCH to allow for Jumbo Frame
transfers ?
Thank You,
Terry Martin
Principal Systems Engineer
Lockheed Martin
CMS - CITIC
3300 Lord Baltimore Drive, Suite 200, 21244
Engin
On Tuesday, 11/08/2011 at 10:49 EST, Richard Troth
wrote:
> Stop calling this a security problem. (but see below about the conf
> file) The security point for virtual machines is devices. If the
> device is available, then whatever the guest does is okay by
> definition.
No, it's not. It may
Stop calling this a security problem. (but see below about the conf
file) The security point for virtual machines is devices. If the
device is available, then whatever the guest does is okay by
definition.
Just because the current crop of security weebles don't "get it" does
not a true problem
That worked - the error msg. went away, and it shaved about 20 seconds
off the boot time.
This was a new clone of SLES11sp1. So the file must have been created
by yast or something else I did while trying to fix the problem.
Since you're paying taxes in Germany, I suppose you're doing your par
Roger,
good news. I am working in the networking team of Linux on System z
development; thus qeth-related problems are my daily business. But
please do not ask me financial questions ;-)
For your remaining problem: Have you upgraded your system from SLES10?
In this case you may still have old con
Thank you, Ursula
That solved the problem. I can now ping and ftp between my layer3
hipersockets. I still get the "Waiting for mandatory devices.
hsi-bus-ccw-0.0.7000 No interface found " msg. when booting
but now that it works, I'll just stop watching.
You're pretty amazing. Thin
Roger,
when configuring a network interface with yast, a udev-rule is created
for the device containing qeth attribute definitions, among them
attribute layer2. Look into /etc/udev/rules.d and check a rule starting
with 51-...7000... . I assume this rule contains a line with layer2=1.
Change this
Roger,
get rid of the LLADDR='00:00:00:00:00:00' definition. ifup does no
longer work for a zero MAC-address. HiperSockets define a MAC-address;
during initialization Linux determines this MAC-address and uses it, if
LLADDR is not defined.
Ursula
On Tue, 2011-11-08 at 10:47 +0100, Roger Evans wr
Forgot to send the info you requested:
DPRODDB2:/etc/sysconfig/network # cat ifcfg-hsi0
BOOTPROTO='static'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR='10.5.2.11/16'
LLADDR='00:00:00:00:00:00'
MTU=''
NAME='Hipersocket (0.0.7000)'
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='manual'
USERCONTROL='no'
-
THanks for that tip. I can't remember having chosen level2, but I see
that my other (older) interfaces are not level2, so, yes, I would like
to switch to level3.
I used the commands (from "Device Drivers, Features...") to to take the
device offline and to make it not level2 (level2=9); After t
Hi Roger,
your boot.messages do not show any message refering to 0.0.7000 or hsi0.
Your hsi0-device is in state SOFTSETUP, which means it has been
activated successfully; just the ifup step fails. The configuration file
for ifup is /etc/sysconfig/network/ifcfg-hsi0. Can you check the
definitions o
13 matches
Mail list logo
