Here is our NICDEF statement in our Linux machine.
NICDEF BC0 TYPE QDIO DEV 3 LAN SYSTEM VSWZVM01
Here is our RedHat Parm statements related to networking. When Redhat
starts up, it is asking us for a portname. Color us confused.
NETTYPE=eth NETWORK=172.16.32.0
CHANDEV=eth0,0xBC0,0xBC1,0xBC2
Do you mean your conf file, and not parm?
I've always used the following in my parms:
NETTYPE=qeth
Never used CHANDEV myself. I used SUBCHANNELS:
SUBCHANNELS=0.0.0600,0.0.0601,0.0.0602
On 04/07/2011 02:25 PM, Hughes, Jim wrote:
Here is our NICDEF statement in our Linux machine.
NICDEF BC0
-8235 (t/l 603-8235)
Send me an email de...@us.ibm.com
From:
Justin Payne jpa...@redhat.com
To:
LINUX-390@vm.marist.edu
Date:
04/07/2011 01:38 PM
Subject:
Re: Linux, VSWITCH, and??
Sent by:
Linux on 390 Port LINUX-390@vm.marist.edu
Do you mean your conf file, and not parm?
I've always used
I'm pretty sure PORTNAME is optional (at least in RHEL 5). My CONF has
PORTNAME= in it
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
Hughes, Jim
Sent: Thursday, April 07, 2011 2:25 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Linux, VSWITCH
Subject: Re: Linux, VSWITCH, and??
I'm pretty sure PORTNAME is optional (at least in RHEL 5). My CONF has
PORTNAME= in it
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
Hughes, Jim
Sent: Thursday, April 07, 2011 2:25 PM
To: LINUX-390
Of
Frankovich, Bob
Sent: Thursday, April 07, 2011 2:43 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Linux, VSWITCH, and??
I'm pretty sure PORTNAME is optional (at least in RHEL 5). My CONF has
PORTNAME= in it
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU
] On Behalf Of
Frankovich, Bob
Sent: Thursday, April 07, 2011 2:43 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Linux, VSWITCH, and??
I'm pretty sure PORTNAME is optional (at least in RHEL 5). My CONF has
PORTNAME= in it
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU
on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Marcy
Cortes
Sent: Tuesday, October 06, 2009 11:29 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Linux vswitch layer2 OSA-Express2 (z9 ) to OSA-EXPRESS3 1000T (z10
) migration issue
We are running OSA code level 7.33 according to osa/sf
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Marcy
Cortes
Sent: Friday, October 02, 2009 12:17 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Linux vswitch layer2 OSA-Express2 (z9 ) to OSA-EXPRESS3 1000T (z10
) migration issue
In addition to what
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Linux vswitch layer2 OSA-Express2 (z9 ) to
OSA-EXPRESS3 1000T (z10 ) migration issue
Marcy,
I would like to know if you picked up an updated microcode on the OSA3 and then
reloaded it or just force reloaded on it. We are running OSA CODE LEVEL
Cortes
Sent: Tuesday, October 06, 2009 11:29 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Linux vswitch layer2 OSA-Express2 (z9 ) to OSA-EXPRESS3 1000T (z10
) migration issue
We are running OSA code level 7.33 according to osa/sf
* CHPID DD
@VM.MARIST.EDU
Subject: Re: Linux vswitch layer2 OSA-Express2 (z9 ) to OSA-EXPRESS3 1000T (z10
) migration issue
On Thursday, 10/01/2009 at 07:31 EDT, Bhemidhi, Ashwin ashw...@ti.com
wrote:
We recently moved our working z/VM Linux LPAR from z9 to z10. After the
move
our Linux guest systems are unable to use
On Friday, 10/02/2009 at 12:16 EDT, Bhemidhi, Ashwin ashw...@ti.com
wrote:
This was a layer 2 vswitch before and after the move. Also if I need to
delete
and re-define do I just do it in Linux or we also need to delete and
re-define
in z/VM guest ID( I do not see if this matters). I tried
On 10/1/2009 at 7:29 PM, Bhemidhi, Ashwin ashw...@ti.com wrote:
Hello all,
We recently moved our working z/VM Linux LPAR from z9 to z10. After the move
our Linux guest systems are unable to use a layer 2 VSWITCH device.
What are the contents of /sys/devices/qeth/0.0.0800/layer2 ? It
immediately by reply e-mail and delete this message. Thank you for
your cooperation.
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Alan
Altmark
Sent: Friday, October 02, 2009 10:12 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Linux vswitch
Hello all,
We recently moved our working z/VM Linux LPAR from z9 to z10. After the move
our Linux guest systems are unable to use a layer 2 VSWITCH device. Our Linux
guest has 2 layer2 NIC interface eth0 and eth1 defined. NIC eth0 is used for IP
and NIC eth1 only does LLC over Ethernet (no IP)
-...@vm.marist.edu] On Behalf Of Bhemidhi,
Ashwin
Sent: Thursday, October 01, 2009 4:30 PM
To: LINUX-390@VM.MARIST.EDU
Subject: [LINUX-390] Linux vswitch layer2 OSA-Express2 (z9 ) to OSA-EXPRESS3
1000T (z10 ) migration issue
Hello all,
We recently moved our working z/VM Linux LPAR from z9 to z10. After
: Thursday, October 01, 2009 7:07 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Linux vswitch layer2 OSA-Express2 (z9 ) to OSA-EXPRESS3 1000T (z10
) migration issue
Looks like you are z/VM 5.3?
If so, did you install the required maintenance to support Express3 cards?
Marcy
This message may contain
On Thursday, 10/01/2009 at 07:31 EDT, Bhemidhi, Ashwin ashw...@ti.com
wrote:
We recently moved our working z/VM Linux LPAR from z9 to z10. After the
move
our Linux guest systems are unable to use a layer 2 VSWITCH device. Our
Linux
guest has 2 layer2 NIC interface eth0 and eth1 defined. NIC
19 matches
Mail list logo
