I currently have 1gig OSA's port(2) defined...
Do I need to do anything in Config of VSWITCH if I swap out 1Gig for a 10Gig ?
--
Email Disclaimer
This E-mail contains confidential information belonging to the sender,
Can someone point me to a reference for configuring Linux SLES9-SP1 with z/VM
5.1 using VSWITCH? We're trying to convert over from guest LANs.
All the references I've been able to find are either for z/VM 4.4 or for SLES8,
or both.
I've tried
Wunder,Odonez and MacIsaac, &qu
I am trying to install linux on a z890 vm lpar I am having trouble with the
vswitch
I am using the z/vm and linux on ibm system z cookbook for sles9
on page 92 where you enter the exec sles9x to do the install to get to the
vnc client this is where
I receive the message that the ping failed for
router linux with eth0 on VSWITCH1 and eth1 on VSWITCH2,
this guest has ip_forward=1 and works like a router between this two
vswitch. There is no problem to ping 172.18.1.x to 192.168.6.x thru this
router for all linux guest.
If I try to ping from a local station on the same lan 172.18.1.16, a
z/vm
We are setting up a vswitch and our problem is we can't use the same OSA
subnet for the vswitch IP addresses without redesigning our whole OSA and
OSPF network.
My question is 'Can Linux on a vswitch point to a zVM static VIPA as its
gateway instead of a LAN router gateway to reach t
Hi,
Anyone know of a way to delete a VSWITCH without IPLing?
Betsie
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http
VSITCH
section, the default is HIPERSOCKETS
The Process is pretty straight forward up to this point, but now I need to
do the Linux side. Any suggestions for a F00-F02 device range on a Vswitch
on the same network as VM
And an example of a separate network from VM would be great. Ultimately w
I am confused about the RDEV setting on the DEFINE VSWITCH command. I currently have
my OSA adapter (address 0100,0101,0102) attached to TCPIP and defined as:
DEVICE [EMAIL PROTECTED] OSD 0100 PORTNAME QSPORT0 PRIR
LINK VMTCPIP QDIOETHERNET [EMAIL PROTECTED]
When I attempt to
Ref: Your note of Thu, 8 Apr 2004 16:02:46 -0500 (attached)
Yes, generate more OSA I/O devices and then specify one of them (such as
103) for the vswitch. I have exactly this configuration working on a
couple of systems. This is not unlike sharing an OSA between LPARS, but
in this case the
Ref: Your note of Fri, 9 Apr 2004 10:20:35 +0200 (attached)
Apparently it can - I had my doubts, but that's what they gave me:
q vswitch
VSWITCH SYSTEM VSWITCH1 Type: VSWITCH Active: 0 MAXCONN: INFINITE
PERSISTENT RESTRICTEDNONROUTER MFS: 8192 ACCOUNTING: OFF
State:
Nope
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Ron Wells
Sent: Friday, March 25, 2016 7:33 AM
To: LINUX-390@VM.MARIST.EDU
Subject: [LINUX-390] VSWITCH
I currently have 1gig OSA's port(2) defined...
Do I need to do anything in Conf
Tks Marcy
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Marcy
Cortes
Sent: Friday, March 25, 2016 3:41 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: VSWITCH
Nope
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU
The 10Gb only have a single port, so if you're using both ports on the 1Gb then
you'll need 2 x 10Gb cards.
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Ron Wells
Sent: 25 March 2016 2:33 PM
To: LINUX-390@VM.MARIST.EDU
Subject:
We are running z/VM 5.4 with linux machines running off a VSWITCH.
Can I run QUAGGA OSPF thru the VSWITCH or do I need to dedicate OSA ports to my
Linux machine?
T.I.A. for any help.
Bruce
--
For LINUX-390 subscribe / signoff
Hello,
For backup over the same network without affecting real time traffic, Is it
possible to establish routes to the media server over particular OSAs on the
same VLAN and VSwitch. We currently have two OSAs from the same VSwitch to two
different Cisco switches with the same VLANs.
For
We have test and production Linux systems on one of our z/VM 520 systems.
We want to separate the test and production systems - different VSWITCHes,
subnets etc.
However it seems there is no way to separate the controllers - that is if
you want more than one by specifying CONTROLLER *VSWITCH
Gordon,
The VM userid must have a NIC defined as type qdio, eg. DEF NIC 480
TYPE QDIO
Couple it to the vswitch, eg. COUPLE 480 SYSTEM VSW1
I have defined the VSWITCH in my SYSTEM CONFIG file:
DEF VSWITCH VSW1 RDEV 5000 4F00
5000 is the primary OSA triplet and 4F00 is the failover
Grant the VM
Without meaning to play down your quest for a reference,
converting from Guest LAN to VSWITCH should only require
using a different router than you did before. With VSWITCH,
your guests are "bridged" to a physical ethernet, where they can
"hit" the same router as VM, MVS
Wolfe, Gordon W wrote:
> SLES9 has changed how it handles the qeth driver from sles8. We no longer
> use /etc/chandev.conf, but files within /etc/sysconfig/network.
> I need to know how to set up those files for VSWITCH, and if there are any
> others I should be aware of.
Actua
15, 2005 3:52 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: VSWITCH
>
> Gordon,
> The VM userid must have a NIC defined as type qdio, eg. DEF NIC 480
> TYPE QDIO
> Couple it to the vswitch, eg. COUPLE 480 SYSTEM VSW1
> I have defined the VSWITCH in my SYSTEM CONFIG
The hardware is configured using files in /etc/sysconfig/hardware. Therre
should be a hwcfg-qeth-bus-ccw-0.0.a001 file in there. If one isn't there,
then copy the file /etc/sysconfig/hardware/skel/hwcfg-qeth to
/etc/sysconfig/hardware/hwcfg-qeth-bus-ccw-0.0.a001 and then edit that file.
You're
2005 12:27 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: VSWITCH
Thanks for the assistance, Betsie, but this is exactly what I'm talking about.
In my copy of SLES9 there is no file
/etc/sysconfig/network-scripts/ifcfg-eth0
in fact, there is no directory
/etc/sysconfig/network-scripts
at all.
I'm having some problems with hosts connecting to vswitch(es) that is
causing me to migrate back towards separate OSA's for some Linux hosts.
One issue is that for a few hosts including a test SLES8 host on a test
vswitch I have: I cannot ping the host from other hosts in the sa
Besides granting access for a user ID to a VSWITCH in AUTOLOG1's
PROFILE EXEC, is there anything else that needs to be done for that
user to use this network construct? I'm having an issue pinging the gateway
from a new user ID, but on the surface, it appears to be coupled prope
Has anyone been able to connect a SLES9 virtual server to an ethernet VSwitch
in z/VM 5.1?
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
>>> On Thu, May 31, 2007 at 5:58 PM, in message
<[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]> wrote:
> I am trying to install linux on a z890 vm lpar I am having trouble with the
> vswitch
>
> I am using the z/vm and linux on ibm system z cookbook for sles9
>
&
A good guess is that you did not grant your linux guest access to the
vswitch.
CP SET VSWITCH GRANT virtual_machine_name (optionally VLAN ###)
This can also be added to the SYSTEM CONFIG file as a MODIFY VSWITCH
statement
Thanks,
Gary L. Detro
Senior IT Specialist 1177 S. Belt Line Rd
Also, does it make any difference if you #cp ipl 00c a couple of times?
You could be hitting that known bug in the shaded box.
-Brad
On Thu, 2007-05-31 at 16:58 -0500, [EMAIL PROTECTED] wrote:
> I am trying to install linux on a z890 vm lpar I am having trouble with the
> vswitch
>
>
> I receive the message that the ping failed for the gateway and the
network
> is unreachable
It may be that your network guys do not allow ping to the gateway. Try to
reply Yes to the question if you want to continue.
--
Mark Pace
Mainline Information Systems
--
your network guys do not allow ping to the gateway. Try to
> reply Yes to the question if you want to continue.
"Network unreachable" messages mean that the packets aren't even going out the
interface. It sounds like he's eith
Linux on 390 Port wrote on 06/01/2007 10:49:24
AM:
>
> "Network unreachable" messages mean that the packets aren't even
> going out the interface. It sounds like he's either not able to set
> the IP address, or he's not coupled to the VSWITCH.
Could
On Jun 1, 2007, at 10:52 AM, Tom Shilson wrote:
Linux on 390 Port wrote on 06/01/2007
10:49:24
AM:
"Network unreachable" messages mean that the packets aren't even
going out the interface. It sounds like he's either not able to set
the IP address, or he's n
: RX Bytes: 0TX Bytes: 0
00: Unassigned Devices:
00: Device: 0600 Unit: 000 Role: Unassigned
00: Device: 0601 Unit: 001 Role: Unassigned
00: Device: 0602 Unit: 002 Role: Unassigned
00: CP Q LAN DETAILS
00: VSWITCH SYSTEM VSW1 Type: VSWITCH
I replied yes and the ping to the dns failed with the same message network
unreachable
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
h
tells me that your NIC is not coupled to the VSWITCH. There are a few
reasons why that might happen.
-snip-
> ifconfig eth0
> DMSACC724I 191 replaces A (191)
> Ready; T=0.01/0.01 11:18:52
> ETH0 inet addr: 10.12.26.108 mask: 255.255.255.0
> UP BROADCAST MULTICAST MT
Mark I used the following command to couple the vswitch to the nic 0600
couple 0600 to system vsw1
after I did that everything worked fine
thanks for your help
--
For LINUX-390 subscribe / signoff / archive access instructions
: 469-549-8235 (t/l 603-8235)
Send me an email [EMAIL PROTECTED]
IBM Global Solution Center
[EMAIL PROTECTED]
Sent by: Linux on 390 Port
06/04/2007 12:03 PM
Please respond to
Linux on 390 Port
To
LINUX-390@VM.MARIST.EDU
cc
Subject
Re: VSWITCH
Mark I used the following command to
the changes online with
DIRECTXA?
With that model the NICDEF should be automatically coupled to the VSWITCH
when the user ID logs on.
"Mike MacIsaac" <[EMAIL PROTECTED]> (845) 433-7061
--
For LINUX-390 subscrib
rd port 0 are used in my VSWITCH2 ip
> address is 192.168.6.0/24.
>
> VSWITCH1 as PRIROUTER set on.
>
> I defined a router linux with eth0 on VSWITCH1 and eth1 on VSWITCH2,
> this guest has ip_forward=1 and works like a router between this two
> vswitch. There is no problem to ping
e-
De : Linux on 390 Port [mailto:[EMAIL PROTECTED] De la part de
Alan Altmark
Envoyé : vendredi 4 juin 2004 16:34
À : [EMAIL PROTECTED]
Objet : Re: VSWITCH router
On Friday, 06/04/2004 at 04:04 ZE2, Monteleone <[EMAIL PROTECTED]>
wrote:
> Hello,
>
> I use two osa card defined in QDIO m
Hi,
You have two OSA cards. VSWITCH1 (with PRIROUTER enabled) is connected to
one card and VSWITCH2 is connected to the second card. I assume these two
OSA cards are connected to two different physical LAN segments in the real
world and your router is the only network link between them.
You men
Hi,
Probably a stupid remark, but should you not define both VSWITCHes with the
PRIROUTER function?
VSWITCH1 to be able to route to your destination, and VSWITCH2 to route the
answer back to the originator?
Ronald van der Laan
-
é : vendredi 4 juin 2004 16:34
À : [EMAIL PROTECTED]
Objet : Re: VSWITCH router
On Friday, 06/04/2004 at 04:04 ZE2, Monteleone <[EMAIL PROTECTED]>
wrote:
> Hello,
>
> I use two osa card defined in QDIO mode.
> Primary card port 0 and Secondary card port 1 are used in my VSWITCH
-Message d'origine-
De : Linux on 390 Port [mailto:[EMAIL PROTECTED] De la part de
Ronald Van Der Laan
Envoyé : samedi 5 juin 2004 15:17
À : [EMAIL PROTECTED]
Objet : Re: VSWITCH router
Hi,
Probably a stupid remark, but should you not define both VSWITCHes with
the
PRIROUTER function?
VSW
If you're talking about sending all your Linux/390 network traffic through
the z/VM TCP/IP stack, then there's no point at all in using VSWITCH.
Simply set up a Guest LAN and define the z/VM TCP/IP IP address on the Guest
LAN as the default gateway. You'll need to have z/VM adver
On Wednesday, 12/29/2004 at 11:00 EST, Dave Kutz <[EMAIL PROTECTED]>
wrote:
> We are setting up a vswitch and our problem is we can't use the same OSA
> subnet for the vswitch IP addresses without redesigning our whole OSA
and
> OSPF network.
> My question is 'Can Linux
All 10 of my LPARs have 2 OSA physical ports. Each port is on a different
subnet and different gigabit switches for redundancy. (102.33.106.130 and
102.33.107.130 for example).
Now I understand that vswitch guests must be on the same subnet as the
physical OSAs. So there is two issues we face 1
Dave,
This is just a guess, but I suspect that you are falling into the trap
that many of us fell into when the guest lan and vswitch capability first
appeared in VM. Network guys, as well as other people, tend to think of
mainframes as big PC's, a "thing" on the network that n
.
The channel addresses used are FB50,3 and FC50,3.
Then we are setting up a vswitch zVM controller to share these two OSA
ports.
Question is 'Does the zVM controller code in its RDEV the same channel
addresses (Fb50 and Fc50) as the main zVM? Or do we need to do an I/O HCD
gen to define n
me out
and
> clearly say.
> Our zVM main tcp stack has device/link statements for the two OSA ports.
> The channel addresses used are FB50,3 and FC50,3.
> Then we are setting up a vswitch zVM controller to share these two OSA
> ports.
> Question is 'Does the zVM controller co
Betsie,
Check out DETACH VSWITCH (in the 5.1 CP Commands and Reference).
Betsie Spann wrote:
Hi,
Anyone know of a way to delete a VSWITCH without IPLing?
Betsie
--
For LINUX-390 subscribe / signoff / archive access instructions
Monday 17 January 2005 23:45, You wrote:
> Hi,
> Anyone know of a way to delete a VSWITCH without IPLing?
> Betsie
z/VM 4.4, from MAINT:
q vswitch
VSWITCH SYSTEM VSWITCH_NAME Type: VSWITCH Active: 0 MAXCONN: INFINITE
...
cp detach vswitch VSWITCH_NAME
VSWITCH SYSTEM VSWITC
I've researched the archives and redbooks. I think I've come across every
combination of implementation except the one I'm trying to do. We have a number
of VSWITCH LINUX instances running under one z/VM LPAR. We have a production VM
TCP/IP stack that we use for 'older
I am attempting to move a SLES7(32) guest from a 9672 using a Guestlan
under z/VM 4.3 to a 2084 using vswitch under z/VM 4.4 (64 bit). I am
already running a number of SLES8(64 bit) guests in this environment. I
can't seem to route to/from this SLES7 image even though I have default
I have three Linux images coupled to a VSWITCH. The VSWITCH is connected
to an OSA Express. The OSA Express is plugged into a VLAN on a Cisco 6509
which is plugged into a PIX with an IP address if 172.16.64.1
The Linux images have IP addresses in the 192.168.2.0/24 subnet. The PIX
does NAT for
I've got a test system running SUSE SLES7. The z/VM system is z/VM Version
4 Release 4.0, service level 0301 (64-bit). I have an OSA card on the
machine, connected to a VSWITCH. My guest is also connected to that
VSWITCH. The virtual NIC is defined as a QDIO device:
#cp q nic details
Ad
Is there any good articles or presentations on setting up a Linux, Sorry
should it be Flock, Herd, or School for penguins.
I am trying to setup a REDHAT AS 3 system on a VSWITCH network under z/VM
4.4.0 RSU 0401
Any suggestions?
TIA,\|/
(. .)
ooO-(_)-Ooo
Larry Davis, 6-2380
"Sorry should it be Flock, Herd, or School for
penguins."
The correct term seems to be "rookery" of penguins.
=
Jim Sibley
RHCT, Implementor of Linux on zSeries
"Computer are useless.They can only give answers." Pablo Picasso
__
Do you Yahoo!?
Yahoo! Search -
Larry,
I'm not sure what you're asking for regarding "the Linux side." Can you
explain a little more?
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Davis,
Larry
Sent: Friday, March 12, 2004 12:09 PM
To: [EMAIL PROTECT
I was wrong the Linux side picked up the NIC cards right away. I believe I
have a routing issue now though.
I currently have a starter system up now playing with the VSWITCH structure
here is the VMSWITCH information
q vswitch detail
VSWITCH SYSTEM REDHAT Type: VSWITCH Active: 2 MAXCONN
On Friday, 03/12/2004 at 04:05 EST, "Davis, Larry"
<[EMAIL PROTECTED]> wrote:
> I was wrong the Linux side picked up the NIC cards right away. I believe
I
> have a routing issue now though.
>
> I currently have a starter system up now playing with the VSWITCH
stru
Hi Larry,
Based on the Query VSWITCH response, it seems only one guest initialized
the interface. The other guest is represented in the response with a
single line:
Adapter Owner: REDHAT01 NIC: 0F00 Name: UNASSIGNED
If it had initialized the interface you would have seen more lines (like
Hi,
If you were trying to test connectivity between your Linux guest and the
outside world then you would need a controller and an interface (a set of
three I/O devices) on a real OSA Express in QDIO mode. Based on the first
few lines from your Query VSWITCH response:
VSWITCH SYSTEM REDHAT
First Thanks to everyone for there inputs. Here is what I had to do to get
the basic VSWITCH setup going
In the PROFILE TCPIP file (TCPMAINT 198'D' disk) added
VSWITCH CONTROLLER ON 0C5C 0C5E
For each User connecting to the switch, I added this directory entry to the
correspo
On Monday, 03/15/2004 at 01:44 EST, "Davis, Larry"
<[EMAIL PROTECTED]> wrote:
> VSWITCH CONTROLLER ON 0C5C 0C5E
Unless you intend to add a VSWITCH CONTROLLER statement for each VSWITCH,
or have to change it when the real address changes, I suggest using the
generic
The VSWITCH OSA devices are attached to no one. CP will drive them but use
the VM TCPIP stack to initialize the devices. CP uses the *VSWITCH IUCV
service to talk with the stack. The stack will issue the necessary CCWs to
get the OSAs initialized. From that point on CP will drive the devices
UNITADD=FE
Should I generate more OSA IODEVICE addresses, say 0103, 0104, and 0105 and use 0103
as the RDEV for the VSWITCH? What's confusing is that VSWITCH RDEV wants a REAL
device, so is it possible to generate more addresses fo
: [EMAIL PROTECTED]
Subject: Re: [LINUX-390] VSWITCH question
So, my current IOCP has:
CNTLUNIT CUNUMBR=0100,PATH=(00),UNIT=OSA
IODEVICE ADDRESS=(0100,03),CUNUMBR=(0100),UNIT=OSA, X
UNITADD=00
IODEVICE ADDRESS=(010F),CUNUMBR=(0100),UNIT=OSAD, X
UNITADD
=3C01, X
UNIT=OSA
IO10FE IODEVICE ADDRESS=(40FE,001),UNITADD=FE,CUNUMBR=3C01, X
UNIT=OSAD
Sample commands to define vswitch:
"DEFINE VSWITCH VSWITCH1 RDEV 4000 CON CONTR * PORT MYPORT"
"SET VSWITCH VSWITCH1 GRANT TCPIPVLAN ANY"
DD=FE
>
> Should I generate more OSA IODEVICE addresses, say 0103, 0104, and 0105 and use
> 0103 as the RDEV for the VSWITCH? What's confusing is that VSWITCH RDEV wants a
> REAL device, so is it possible to generate more addresses for the real OSA?
Yes, you should. You can have load
: Thursday, April 08, 2004 4:53 PM
To: [EMAIL PROTECTED]
Subject: Re: VSWITCH question
On Thu, 2004-04-08 at 23:02, David Booher wrote:
>
>CNTLUNIT CUNUMBR=0100,PATH=(00),UNIT=OSA
>IODEVICE ADDRESS=(0100,03),CUNUMBR=(0100),UNIT=OSA, X
> UNITADD=00
>IO
Bruce Hayden wrote:
Yes, generate more OSA I/O devices and then specify one of them (such as
103) for the vswitch. I have exactly this configuration working on a
couple of systems. This is not unlike sharing an OSA between LPARS, but
in this case the sharing is all within the same LPAR.
Well
He could always use 104 and 105 for the read/write channels, and 103 as the
data channel.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Rob
van der Heij
Sent: Friday, April 09, 2004 4:21 AM
To: [EMAIL PROTECTED]
Subject: Re: VSWITCH question
Post, Mark K wrote:
He could always use 104 and 105 for the read/write channels, and 103 as the
data channel.
But that was the point Bruce and I were fighting about. If you were
attaching the 3 devices of a tripod to a virtual machine you could, but
if you define a VSWITCH you specify the first
> --
> From: ADAMS Steven
> Sent: Thursday, April 15, 2004 8:29:46 AM
> Subject: VSWITCH Connections
> Auto forwarded by a Rule
>
Hi All,
I'm mid-way through migrating from VM4.30 to VM4.40 and have successfully
created a virtual switch for commu
Steve,
Yes, qeth.o is the correct module to be using for a VSWITCH. You'll also
need some entries in /etc/chandev.conf for the driver to initialize
properly. Something that looks like this:
qeth0,0x0F00,0x0F01,0x0F02
add_parms,0x10,0x0F00,0x0F02,portname:LINUX390
The portname will be arbi
I also had to add some entries to, in my case AUTOLOG1's PROFILE EXEC to
authorize users to use the switch
ADDRESS COMMAND CP 'SET VSWITCH SWITCH01 RDEV 0C5C '
ADDRESS COMMAND CP 'SET VSWITCH SWITCH01 GRANT TCPIP'
ADDRESS COMMAND CP 'SET VSWITCH SWITCH01 GRA
chandev.conf lines to reflect the different devnos associated with the new
simulated device and not the real OSA device. I think that should be
correct?
-Original Message-
From: Post, Mark K [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 15, 2004 8:52 AM
To: [EMAIL PROTECTED]
Subject: Re: VSWITCH
I did have to add the SET VSWITCH VSS3000 GRANT REL3001 but I haven't
granted TCPIP yet and it looks normal when I query the switch, controller,
LAN and NIC (just won't bind qeth.o to the interface from Linux).
-Original Message-
From: Davis, Larry [mailto:[EMAIL PROTECTED]
Sent
PROTECTED]
Sent: Thursday, April 15, 2004 12:19 PM
To: [EMAIL PROTECTED]
Subject: Re: VSWITCH Connections
Oops, my bad Mark. I do have these entries on chandev but neglected to
mention them in the original post. The one thing that I have not done is
mkinitrd since the original connection for
Hello,
Great thread! I'm also going to implement VSWITCH tonight, but I understood the
PROFILE TCPIP change to be something like this:
VSWITCH CONTROLLER ON 0104 0106
where a range of addresses (triplet) is used. Am I wrong?
Dave
-Original Message-
From: Linux on 390
On Fri, 16 Apr 2004 03:18 am, David Booher wrote:
DB> Hello,
DB>
DB> Great thread! I'm also going to implement VSWITCH tonight, but I
understood the PROFILE TCPIP change to be something like this:
DB>
DB> VSWITCH CONTROLLER ON 0104 0106
DB>
DB> where a range of addresse
that's what mine looks like
David Booher wrote:
Hello,
Great thread! I'm also going to implement VSWITCH tonight, but I understood the PROFILE TCPIP change to be something like this:
VSWITCH CONTROLLER ON 0104 0106
where a range of addresses (triplet) is used. Am I wr
On Thursday, 04/15/2004 at 12:18 EST, David Booher
<[EMAIL PROTECTED]> wrote:
> Hello,
>
> Great thread! I'm also going to implement VSWITCH tonight, but I
understood
> the PROFILE TCPIP change to be something like this:
>
> VSWITCH CONTROLLER ON 0104 0106
>
>
Thanks for all the great responses...consider it stricken ;)
Dave
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Alan Altmark
Sent: Thursday, April 15, 2004 1:21 PM
To: [EMAIL PROTECTED]
Subject: Re: VSWITCH Connections
On Thursday, 04/15/2004 at 12:18
ly problem seen
on the operators console is that vm440 is out of swap space, this is now
corrected and no longer an issue.
-Original Message-
From: Post, Mark K [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 15, 2004 9:42 AM
To: [EMAIL PROTECTED]
Subject: Re: VSWITCH Connections
Steve,
Y
Steve,
I didn't mean the VM operator's console, I meant the virtual console for the
guest. Is the NIC defined properly and coupled to the VSWITCH?
#cp q nic details
#cp q lan details
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf
On Thursday, 04/15/2004 at 12:00 MST, [EMAIL PROTECTED] wrote:
> To define the Controller in PROFILE TCPIP:
> VSWITCH CONTROLLER ON 0206
This doesn't look good. Get rid of the 0206 or use
VSWITCH CONTROLLER ON 0206 0208
A #CP QUERY NIC DETAILS will be interesting to see.
You mi
Hi Steve,
After you updated /etc/chandev.conf did you reboot the system or echo some
commands to /proc/chandev to ask it to read the new configuration and probe
for new devices? Use 'man chandev' to check all of the options, but
probably:
echo "read_conf" > /proc/chandev
echo "reprobe" > /proc/c
Mark/Alan
My apologies, I misunderstood the request.
Yes, the NIC does couple to the switch successfully and I changed to VSWITCH
CONTROLLER statement, from VSWITCH CONTROLLER ON 0206 0208, after reading
Alan's suggestions. Here are the snips from VM 4.40:
def nic 3909 type qdio
01: NIC 39
Steve,
My understanding is that the address triplet must be defined as
"qethN,,,".
> cat /etc/chandev.conf
> noauto
> qeth0,0x3909,0x390A,0x390B,0,0
> add_parms,0x10,0x3909,0x390B,portname:VSI3000
> qeth1,0x3009,0x300A,0x300B,0,0
> add_parms,0x10,0x3009,0x300B,portname:HSI3000
becomes:
» cat /
tual OSA still adheres to the old restriction, so, yes, the
first address must be *even* on a Guest LAN or VSWITCH.
And, Steve, the q nic details is only interesting after you have tried to
start the device but while Linux is still up. I.e. #cp q nic details.
Alan Altmark
Sr. Softw
al Message-
From: Alan Altmark [mailto:[EMAIL PROTECTED]
Sent: Friday, April 16, 2004 5:39 AM
To: [EMAIL PROTECTED]
Subject: Re: VSWITCH Connections
On Friday, 04/16/2004 at 09:32 ZE2, Ronald Van Der Laan
<[EMAIL PROTECTED]> wrote:
> Steve,
>
> My understanding is that the address tr
day, April 16, 2004 7:08 AM
To: [EMAIL PROTECTED]
Subject: Re: VSWITCH Connections
Thanks Alan, Unfortunately I can't get to that place just yet. Good
information though, I have been getting away with starting hsi1 on an odd
number for over a year in vm4.3 so I guess I missed that detail. I&#
On Friday, 04/16/2004 at 07:08 MST, [EMAIL PROTECTED] wrote:
> Thanks Alan, Unfortunately I can't get to that place just yet. Good
> information though, I have been getting away with starting hsi1 on an
odd
> number for over a year in vm4.3 so I guess I missed that detail. I'll
clean
> up that lit
ent by: Linux on cc:
390 Port Subject: Re: [LINUX-390] VSWITCH
Connections
<[EMAIL PROTECTED]
to
control, what appears to be, very dissimilar devices. I think that confusion
is now cleared up with Dennis Musselwhite's post.
Steve
-Original Message-
From: Alan Altmark [mailto:[EMAIL PROTECTED]
Sent: Friday, April 16, 2004 7:55 AM
To: [EMAIL PROTECTED]
Subject: Re: VSWITCH Connec
individuals =)
-Original Message-
From: Dennis Musselwhite [mailto:[EMAIL PROTECTED]
Sent: Friday, April 16, 2004 9:26 AM
To: [EMAIL PROTECTED]
Subject: Re: VSWITCH Connections
Hi Steve,
>From your note:
> def nic 3909 type qdio
> 01: NIC 3909 is created; devices 3909-390B defined Read
Hello,
I have about 40 guests attached to a single vswitch and all but one are
having a problem.
test-09 keeps coming up as UNASSIGNED. This is z/VM V6.1.0
Has anyone ever seen this before?
Adapter Owner: test-09 NIC: 8000.P00 Name: UNASSIGNED Type: QDIO
00: Porttype: Access
00
auto-negotiation: Yes
Speed: 10Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Link detected: yes
(Neither has native OSA, so I don't know if this is just a VSw
1 - 100 of 737 matches
Mail list logo
