Output of vmcp q v osa:
vmcp q v osa
OSA 0600 ON NIC 0600 UNIT 000 SUBCHANNEL = 0006
0600 DEVTYPE OSA CHPID 01 OSD
0600 MAC 02-08-01-00-00-03 CURRENT
0600 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE
OSA 0601 ON NIC 0600 UNIT 001 SUBCHANNEL = 0007
0601 DEVTYPE OSA CHPID 01 OSD
0601 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE
OSA 0602 ON NIC 0600 UNIT 002 SUBCHANNEL = 0008
0602 DEVTYPE OSA CHPID 01 OSD
0602 QDIO ACTIVE QIOASSIST-ELIGIBLE
0602
0602 INP + 01 IOCNT = 00001139 ADP = 012 PROG = 000 UNAVAIL = 116
0602 BYTES = 0000000000023C08
0602 OUT + 01 IOCNT = 00000000 ADP = 000 PROG = 000 UNAVAIL = 128
0602 BYTES = 0000000000000000
0602 OUT + 02 IOCNT = 00000000 ADP = 000 PROG = 000 UNAVAIL = 128
0602 BYTES = 0000000000000000
0602 OUT + 03 IOCNT = 00000816 ADP = 000 PROG = 128 UNAVAIL = 000
0602 BYTES = 000000000003BD67
0602 OUT + 04 IOCNT = 00000000 ADP = 000 PROG = 000 UNAVAIL = 128
0602 BYTES = 0000000000000000
It is a vswitch at Layer 3.
Yes, I have root access, but do not have a z/vm console or access.
When rebooting, it hangs on:
Waiting for Mandatory device etho __NSC__ anc counts down from 30.
We than have to do a znetconf -A then add the GW route in.
Having been a member of the kernel dev team in the past (X86 only)
and having dealt with Linux since 1994, this tells me some config file
did
not get the "NOTICE OF UPDATE" for the z/vm devices.
I dunno, and will profess all this z/VM layer stuff is new to me, But I
like it ..
Ben Duncan - Business Network Solutions, Inc. 336 Elton Road Jackson
MS, 39212
"Never attribute to malice, that which can be adequately explained by
stupidity"
- Hanlon's Razor
> -------- Original Message --------
> Subject: Re: Issues with persistence of Drivers
> From: Ron Foster <[email protected]>
> Date: Mon, July 02, 2012 1:48 pm
> To: [email protected]
>
>
> A vmcp q v osa would work.
>
> Also, are you the one who logs on the quest. That is do you have the
> authority to shutdown zlinux and logoff the guest. Then logon the guest and
> ipl the Linux guest?
>
> If so, what kind of messages are you getting when you first logon to the
> Linux guest and before you ipl the Linux image? Just looking to see if you
> have full access to the devices you need.
>
> Also, are you using vswitches or dedicated OSAs?
>
> If vswitch, layer2 or layer3.
>
> Ron Foster
>
> Baldor Electric Company
>
> 5711 R S Boreham Jr Street
>
> Fort Smith, AR 72901
>
> Phone:479-648-5865
>
> Fax:479-646-5440
>
> Email: [email protected]
>
> www.baldor.com
>
>
>
> ________________________________________
> From: Linux on 390 Port [[email protected]] on behalf of Ben Duncan
> [[email protected]]
> Sent: Monday, July 02, 2012 1:30 PM
> To: [email protected]
> Subject: Re: Issues with persistence of Drivers
>
> Opps sorry. Suse 11.1 zLinux
>
> uname -ran output: Linux sup00039 2.6.32.46-0.3-default #1 SMP
> 2011-09-29 17:49:31 +0200 s390x s390x s390x GNU/Linux
>
> cat /etc/SuSE-release :
>
> SUSE Linux Enterprise Server 11 (s390x)
> VERSION = 11
> PATCHLEVEL = 1
>
> Sorry, I cannot give a vm CP query since I am not allowed zvm access.
>
>
> after doing znetconf -A:
>
> sup00039:/etc/udev/rules.d # znetconf -c
> Device IDs Type Card Type CHPID Drv. Name
> State
> --------------------------------------------------------------------------------
> 0.0.0600,0.0.0601,0.0.0602 1731/01 GuestLAN QDIO 01 qeth eth0
> online
>
> /etc/sysconfig/network/ifcfg-eth0 file:
>
> BOOTPROTO='static'
> IPADDR='10.12.9.114'
> NETMASK='255.255.255.0'
> BROADCAST='10.12.9.144'
> STARTMODE='onboot'
> NAME='OSA Express Network card (0.0.0600)'
>
>
> I even delete the /etc/udev/rules.d/70-persistent-net.rules to force a
> rebuild
> but that does seem to help ... it looks like this:
>
> # This file was automatically generated by the /lib/udev/write_net_rules
> # program run by the persistent-net-generator.rules rules file.
> #
> # You can modify it,as long as you keep each rule on a single line.
> # S/390 qeth device at 0.0.0600
> # This file was automatically generated by the /lib/udev/write_net_rules
> # program run by the persistent-net-generator.rules rules file.
> #
> # You can modify it,as long as you keep each rule on a single line.
> # S/390 qeth device at 0.0.0600
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="qeth", KERNELS=="0.0.0600",
> ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
>
> supztest:/var/log # vmcp q 0600
> OSA 0600 ON NIC 0600 UNIT 000 SUBCHANNEL = 0006
> 0600 DEVTYPE OSA CHPID 01 OSD
> 0600 MAC 02-08-01-00-00-03 CURRENT
> 0600 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE
>
> Anything else I need to supply ?
>
>
> MY Guess is there is a config file that HOLDS the MAC address that is
> not getting changed
> and fubaring the whole thing
>
>
> Thanks ..
>
>
> Ben Duncan - Business Network Solutions, Inc. 336 Elton Road Jackson MS,
> 39212
> "Never attribute to malice, that which can be adequately explained by
> stupidity"
> - Hanlon's Razor
>
>
>
>
> -------- Original Message --------
> Subject: Re: Issues with persistence of Drivers
> From: Mark Post <[email protected]>
> Date: Mon, July 02, 2012 12:18 pm
> To: [email protected]
>
>
> >>> On 7/2/2012 at 01:09 PM, Ben Duncan <[email protected]> wrote:
> > The network driver and network works fine on the Z9.
> >
> > After rebooting the Z114 zLinux, the network device goes away.
> >
> > We are experiencing the same thing with the multi-path drivers.
>
> Distribution? Version? Interface definition file(s)? CP QUERY output for
> NIC? Etc.
>
>
> Mark Post
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> ----------------------------------------------------------------------
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO LINUX-390 or visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> ----------------------------------------------------------------------
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO LINUX-390 or visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> ----------------------------------------------------------------------
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
