and if you see anything that looks odd in
the information posted above please let me know.
Thanks again,
Steve
-Original Message-
From: Post, Mark K [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 15, 2004 4:03 PM
To: [EMAIL PROTECTED]
Subject: Re: VSWITCH Connections
Steve,
I didn't mean
Steve,
My understanding is that the address triplet must be defined as
qethN,even address,odd address,remaining address.
cat /etc/chandev.conf
noauto
qeth0,0x3909,0x390A,0x390B,0,0
add_parms,0x10,0x3909,0x390B,portname:VSI3000
qeth1,0x3009,0x300A,0x300B,0,0
On Friday, 04/16/2004 at 09:32 ZE2, Ronald Van Der Laan
[EMAIL PROTECTED] wrote:
Steve,
My understanding is that the address triplet must be defined as
qethN,even address,odd address,remaining address.
Real OSAs changed at some point to allow any address to be used. However,
z/VM's virtual
-
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 triplet must be defined as
qethN
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'll clean
up
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 little
:
390 Port Subject: Re: [LINUX-390] VSWITCH
Connections
[EMAIL PROTECTED]
ST.EDU
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 Connections
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 Ready; T=0.01/0.01
--
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 communication from my RHEL 3
.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of ODOT
zSeries Linux
Sent: Thursday, April 15, 2004 11:30 AM
To: [EMAIL PROTECTED]
Subject: FW: VSWITCH Connections
--
From: ADAMS Steven
Sent: Thursday, April 15, 2004
]
Subject: Re: VSWITCH Connections
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
will be arbitrary.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of ODOT
zSeries Linux
Sent: Thursday, April 15, 2004 11:30 AM
To: [EMAIL PROTECTED]
Subject: FW: VSWITCH Connections
--
From: ADAMS Steven
Sent: Thursday
, April 15, 2004 9:05 AM
To: [EMAIL PROTECTED]
Subject: Re: VSWITCH Connections
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
: 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 this guest was directly
[mailto:[EMAIL PROTECTED] Behalf Of
ODOT zSeries Linux
Sent: Thursday, April 15, 2004 10:30 AM
To: [EMAIL PROTECTED]
Subject: FW: VSWITCH Connections
--
From: ADAMS Steven
Sent: Thursday, April 15, 2004 8:29:46 AM
Subject: VSWITCH Connections
Auto forwarded by a Rule
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 addresses (triplet) is used. Am I wrong?
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
ODOT zSeries Linux
Sent: Thursday, April 15, 2004 10:30 AM
To: [EMAIL PROTECTED]
Subject: FW: VSWITCH Connections
--
From: ADAMS Steven
Sent: Thursday, April 15, 2004 8:29:46 AM
Subject
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
where a range of addresses (triplet) is used.
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
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,
Yes, that's
PROTECTED]
Sent: Thursday, April 15, 2004 3:00 PM
To: [EMAIL PROTECTED]
Subject: Re: VSWITCH Connections
Modprobe returns without error. Doing an insmod returns the message that the
module is already loaded. Doing an /etc/init.d/network restart shuts down
hsi1 and lo, then attempts to load eth0
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 might want to
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
24 matches
Mail list logo
