no)
Following those two paths back toward the load balancer may take you to a
router that is taking your packets to the second OSA but not to the first
OSA.
Regards,
Dennis
Dennis Musselwhite (musse...@us.ibm.com) +1(607)429-3831
z/VM
misunderstanding the purpose of breaking them into
distinct groups.
Regards,
Dennis Musselwhite
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390
is universally
good.
Regards,
Dennis Musselwhite
z/VM CP Development
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http
David Boyes wrote on 05/23/2012 10:44:51 AM:
On 5/23/12 9:40 AM, Dennis Musselwhite musse...@us.ibm.com wrote:
When the VSWITCH is defined with the IP option, ARP responsibility
is offloaded to the OSA hardware, so the Linux host should *not* be
sending ARP frames on that interface
that same rule.
Even on a Guest LAN (which is isolated) you may have a router
that passes frames between simulated and physical networks.
In that case, it is more efficient to adopt the physical MTU
limit for virtual hosts coupled to the QDIO Guest LAN.
Regards,
Dennis Musselwhite ([EMAIL PROTECTED
levels and (VM) TCP/IP Maintenance
levels for problems that might affect Guest LAN or VSWITCH operation.
Regards,
Dennis
Dennis Musselwhite ([EMAIL PROTECTED])
z/VM Development -- CP Network Simulation -- IBM Endicott NY
.
It might also help to know what level software you
are running on the virtual hosts (e.g. sles8 ?) and
dmesg lines that mention qeth (the device driver).
Regards,
Dennis
Dennis Musselwhite ([EMAIL PROTECTED])
z/VM Development -- CP
Dennis Musselwhite ([EMAIL PROTECTED])
z/VM Development -- CP Network Simulation -- IBM Endicott NY
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL
work over a Layer 2
VSWITCH connection.
Regards,
Dennis
Dennis Musselwhite ([EMAIL PROTECTED]) +1(607)429-3831
z/VM Development -- CP Network Simulation -- IBM Endicott NY
Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote on 03/24
of the problem and will be
creating a new kernel package soon.
Regards,
Dennis
Dennis Musselwhite ([EMAIL PROTECTED])
z/VM Development -- CP Network Simulation -- IBM Endicott NY
the HiperSockets interface. If this works, it will give us a better idea
where things changed. If it does NOT work, I can suggest a virtual I/O
trace that we can use to figure out why the initialization failed.
Regards,
Dennis
Dennis
that
based on your VSWITCH definition.
Do not try to define DEVICE and LINK statements for the VSWITCH in your
controller (VSWCTRL1). Let the controller create the necessary definitions
dynamically.
Regards,
Dennis
Dennis Musselwhite
will lookup the NICDEF for device xxx and use those
defaults. The following command:
CP DEFINE NIC xxx
learns from the NICDEF statement that you want to use TYPE QDIO and COUPLE
to SYSTEM PORTNAME.
Regards,
Dennis
Dennis
said.
On SLES8 we use client dhcpcd and option -B (upper
case) - will not work
without it.
All the Best
Mark Perry
From: Dennis Musselwhite
[mailto:[EMAIL PROTECTED]
Sent: 13 October 2004 18:02
To: [EMAIL PROTECTED]
Subject: Re: DHCP Server on zLinux doesn't work
SNIP
to add broadcast
support for the DHCPOFFER).
Regards,
Dennis
Dennis Musselwhite ([EMAIL PROTECTED]) +1(607)429-3831
z/VM Development -- CP Network Simulation -- IBM Endicott NY
Dennis Musselwhite ([EMAIL PROTECTED])
z/VM Development -- CP Network Simulation -- IBM Endicott NY
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email
devices, so I hope we will be able to lift that
restriction for Guest LAN at some point in the future.
Regards,
Dennis
Dennis Musselwhite ([EMAIL PROTECTED]) +1(607)429-3831
z/VM Development -- CP Network Simulation -- IBM Endicott NY
/chandev
Regards,
Dennis
Dennis Musselwhite ([EMAIL PROTECTED])
z/VM Development -- CP Network Simulation -- IBM Endicott NY
--
For LINUX-390 subscribe / signoff / archive
to read your configuration file and reprobe
for devices (see 'man chandev' for specific commands that you can echo to
/proc/chandev).
Regards,
Dennis
Dennis Musselwhite ([EMAIL PROTECTED]) +1(607)429-3831
z/VM Development -- CP
Dennis Musselwhite ([EMAIL PROTECTED])
z/VM Development -- CP Network Simulation -- IBM Endicott NY
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED
to the
appropriate VM users before those users start logging on and trying to
COUPLE.
Regards,
Dennis
Dennis Musselwhite ([EMAIL PROTECTED])
z/VM Development -- CP Network Simulation -- IBM Endicott NY
Dennis Musselwhite ([EMAIL PROTECTED])
z/VM Development -- CP Network Simulation -- IBM Endicott NY
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390
those that follow the REDHAT02 NIC information).
Maybe the interface is defined but no ifup done yet? When you try to
bring up the interface, do you get error messages from the qeth module ?
Regards,
Dennis
Dennis Musselwhite ([EMAIL
Dennis Musselwhite ([EMAIL PROTECTED])
z/VM Development -- CP Network Simulation -- IBM Endicott NY
it was caused by QUERY NIC, or just a
coincidence) you should contact IBM and open a problem report (as Adam
suggested) and send in the dump.
Regards,
Dennis
Dennis Musselwhite ([EMAIL PROTECTED]) +1(607)429-3831
z/VM Development -- CP
the same MAC address that you
see with CP QUERY NIC details. That would indicate that your drivers are
new enough to handle the request.
Regards,
Dennis
Dennis Musselwhite ([EMAIL PROTECTED])
z/VM Development -- CP Network Simulation
, but it should
work
if you logoff TCPIP and log it back on.
Regards,
Dennis
Dennis Musselwhite ([EMAIL PROTECTED])
z/VM Development -- CP Network Simulation -- IBM Endicott NY
Dennis Musselwhite ([EMAIL PROTECTED]) +1(607)429-3831
z/VM Development -- CP Network Simulation -- IBM Endicott NY
Matt Lashley/SCO
[EMAIL PROTECTED]To: [EMAIL PROTECTED
hsi0,0xf00,0xf01,0xf02,0,0 on line no 3
interpreted as hsi0,0xf00,0xf01,0xf02,0,0.
Type man chandev for more info.
Everything else looked OK to me.
Regards,
Dennis
Dennis Musselwhite ([EMAIL PROTECTED]) +1(607)429-3831
z/VM
Dennis Musselwhite ([EMAIL PROTECTED])
z/VM Development -- CP Network Simulation -- IBM Endicott NY
VMLAN and
see if VM63172 is stated as the latest VMLAN service. If that's not the
problem,
you may need the latest qeth driver.
Regards,
Dennis Musselwhite ([EMAIL PROTECTED])
IBM z/VM Development -- CP Network Simulation
something non-disruptive
with a CP command you could write a bash script to issue
the hcp commands (e.g. hcp couple 500 to othervm 500).
Regards,
Dennis Musselwhite ([EMAIL PROTECTED])
IBM z/VM Development -- CP Network Simulation
Tzafrir Cohen [EMAIL PROTECTED]@VM.MARIST.EDU on 03/13/2003
10:59:03 AM
your
portname was being ignored.
Regards,
Dennis Musselwhite ([EMAIL PROTECTED])
IBM z/VM Development -- CP Network Simulation
Chris Little [EMAIL PROTECTED]@VM.MARIST.EDU on 02/27/2003 11:27:48
AM
Please respond to Linux on 390 Port [EMAIL PROTECTED]
Sent by:Linux on 390 Port [EMAIL PROTECTED
a device is added dynamically.
You are correct in that you do NOT need to HCD gen the HiperSockets device
(Guest LAN is fully simulated within the CP layer of z/VM).
Regards,
Dennis Musselwhite ([EMAIL PROTECTED])
IBM z/VM Development -- CP Network Simulation
connection).
Regards,
Dennis Musselwhite ([EMAIL PROTECTED])
IBM Corporation -- z/VM Development -- CP Network Simulation
Jones, Brian P [EMAIL PROTECTED]@VM.MARIST.EDU on
01/15/2003 06:20:25 PM
Please respond to Linux on 390 Port [EMAIL PROTECTED]
Sent by:Linux on 390 Port [EMAIL PROTECTED
,
Dennis Musselwhite ([EMAIL PROTECTED])
IBM Corporation -- z/VM Development -- CP Network Simulation
Jørgen Birkhaug [EMAIL PROTECTED]@VM.MARIST.EDU on 11/29/2002 08:31:00
AM
Please respond to Linux on 390 Port [EMAIL PROTECTED]
Sent by:Linux on 390 Port [EMAIL PROTECTED]
To:[EMAIL
that addparms should be
add_parms
(I should remember this by now). That could also cause an initialization
failure.
Regards,
Dennis Musselwhite ([EMAIL PROTECTED])
IBM Corporation -- z/VM Development -- CP Network Simulation
they are still reported as
Unassigned devices.
I believe your CP system has been installed with only the z/VM 4.2.0 base
tapes, and
no service. After the suggested APARs (VM62958 or VM62938) are applied
your current
configuration should work properly.
Regards,
Dennis Musselwhite ([EMAIL PROTECTED
to upper-case, it is safer to use upper-case in
general.
Can you paste a copy of your /etc/chandev.conf file here?
Regards,
Dennis Musselwhite ([EMAIL PROTECTED])
IBM Corporation -- z/VM Development -- CP Network Simulation
Crowley, Glen L [EMAIL PROTECTED]@VM.MARIST.EDU on 11/06/2002
10:47:21 AM
of these ideas will help you.
Regards,
Dennis Musselwhite ([EMAIL PROTECTED])
IBM Corporation -- z/VM Development -- CP Network Simulation
describe the way you have
configured the HiperSockets DEVICE/LINK on the TCPIP side, perhaps
other readers can offer suggestions that will help.
Regards,
Dennis Musselwhite ([EMAIL PROTECTED])
IBM Corporation -- z/VM Development -- CP Network Simulation
to be your CTCA link address,
and if your CTCA link happened to be the DEFAULT NET for the TCPIP
stack. There are probably other ways that a configuration error could
account for this (I'm familiar with this one because something similar
happened to me on a test system recently).
Regards,
Dennis
a virtual NIC to that Guest
LAN:
cp define nic 800
cp couple 800 to userx sample
This connects the wires between your virtual adapter and the simulated
LAN segment.
You should define and couple before the CP IPL command that starts the
guest operating system.
Regards,
Dennis Musselwhite ([EMAIL
):/ #
echo 'add_parms,0x10,0x0b00,0x0b01,0x0b02,portname:OSDDR' /proc/chandev
Try:
echo 'qeth0,0x0b00,0x0b01,0x0b02,0,0' /proc/chandev
echo 'add_parms,0x10,0x0b00,0x0b02,portname:OSDDR' /proc/chandev
Regards,
Dennis Musselwhite ([EMAIL PROTECTED])
IBM Corporation -- z/VM Development -- CP Network
the trace agrees with the device
status
for 1802.
Regards,
Dennis Musselwhite ([EMAIL PROTECTED])
IBM Corporation -- z/VM Development -- CP Network Simulation
Keiichi Matsumoto/Japan/IBM@[EMAIL PROTECTED] on 06/05/2002 04:54:06 AM
Please respond to Linux on 390 Port [EMAIL PROTECTED]
Sent
virtual HiperSockets networks
and adapters.
Regards,
Dennis Musselwhite ([EMAIL PROTECTED])
IBM Corporation -- z/VM Development -- CP Network Simulation
? If I remember correctly from studying the CP source
for
QDIO support in 2.4, there was a capabilities mask that had a bunch of
undefined bits for new goodies, and it sounds like this would be one that
would need a bit.
Regards,
Dennis Musselwhite ([EMAIL PROTECTED])
IBM Corporation -- z/VM
is probably intended to be a symlink of
whatever is the most recent k_deflt-*.rpm.
Thank You,
Dennis Musselwhite ([EMAIL PROTECTED])
IBM Corporation -- z/VM Development -- CP Network Simulation
Regards,
Dennis Musselwhite ([EMAIL PROTECTED])
IBM Corporation -- z/VM Development -- CP Network Simulation
Philip J. Tully [EMAIL PROTECTED]@VM.MARIST.EDU on 02/13/2002
09:53:40 AM
Please respond to Linux on 390 Port [EMAIL PROTECTED]
Sent by:Linux on 390 Port [EMAIL PROTECTED
and simulation errors :-(
So: has anyone successfully set up SLES beta with the hsi interface?
Sorry... I have not used the SLES beta, but I hope somebody on the
list will confirm that the HiperSockets drivers work with that
distribution.
Regards,
Dennis Musselwhite ([EMAIL PROTECTED])
z/VM CP
Linux machine.
Hopefully somebody with more experience with configuration files can
come up with better ideas tomorrow.
Regards,
Dennis Musselwhite ([EMAIL PROTECTED])
z/VM CP Development
/WRITE/DATA roles have been
assigned yet by the interface... and which IP Addresses have been
set by this interface). In this case, since qeth.o did not find
the device it will probably just show you the initial state (all
three devices unassigned).
Best Regards,
Dennis Musselwhite ([EMAIL PROTECTED
52 matches
Mail list logo
