Ron, the MAC-address for a VSWITCH interface is defined by z/VM. Can you check somehow if this MAC-address changes during upgrade - for instance in z/VM CP with command CP Q VSWITCH DETAILS? If yes, the problem seems to be related to Novell bugzilla 617373.
Kind regards, Ursula Braun, IBM Germany, Linux on System z development On Thu, 2012-02-02 at 13:34 -0600, Ron Foster at Baldor-IS wrote: > Hello, > We are in the midst of performing our first upgrade from SLES10 SP4 to > SLES11 SP1 and are having network connection issues. > We are attempting to upgrade our Linux "sandbox" system that runs under > z/VM. We ipl from the card reader and perform the first part of the > upgrade just fine. After the first part of the upgrade, the install > program reboots itself. All appears to be working fine until the part > that tells us to VNC into the system to finish the upgrade. > At that point we try to do this and VNC does not connect. We try to > ping the guest and get no response. I run nmap against the address and > it shows no ports open. > The device 0700 being used is connected to a VSWITCH. Before the > upgrade, the device works fine. The first part of the upgrade works > fine. It is only the second part of the upgrade that does not work ok. > Here are what I think are the relevant portions of the messages that > come out out boot. > dasd-eckd.412b53: 0.0.0201: DASD with 4 KB/block, 2403360 KB total size, > 48 KB/t > rack, compatible disk layout > dasdd: > qeth.736dae: 0.0.0700: Device is a Guest LAN QDIO card (level: V620) > with link type GuestLAN QDIO (portname: ) > qeth.47953b: 0.0.0700: Hardware IP fragmentation not supported on eth0 > qeth.066069: 0.0.0700: Inbound source MAC-address not supported on eth0 > qeth.d7fdb4: 0.0.0700: VLAN enabled > qeth.e90c78: 0.0.0700: Multicast enabled > qeth.5a9d02: 0.0.0700: IPV6 enabled > qeth.184d8a: 0.0.0700: Broadcast enabled > qeth.dac2aa: 0.0.0700: Using SW checksumming on eth0. > qeth.9c4c89: 0.0.0700: Outbound TSO not supported on eth0 > VOL1/ 0X0200: > Adding 2403256k swap on /dev/dasdb1. Priority:-1 extents:1 across:2403256k > device-mapper: uevent: version 1.0.3 > device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: > dm-de...@redhat.com > <redir.aspx?C=c96b8535c5c94f02aa7b733fd5bd1f87&URL=mailto%3adm-devel%40redhat.com> > > loop: module loaded > > REISERFS (device dasda2): found reiserfs format "3.6" with standard journal > (Deleted lines) > Disabling IPv6 privacy..done > ..done > Setting up hostname 'bus0105'..done > Setting up loopback interface lo > lo IP address: 127.0.0.1/8 > IP address: 127.0.0.2/8 > ..done > Running sadc > ..done > Setting kernel specific parameters for a SAP system > ..doneSystem Boot Control: The system has been set up > Skipped features: [80C [14Dboot.md > System Boot Control: Running /etc/init.d/boot.local > ..doneStarting syslog services..done > Starting D-Bus daemon..done > Loading CPUFreq modules (CPUFreq not supported) > Starting HAL daemon..done > Setting up (localfs) network interfaces: > lo > lo IP address: 127.0.0.1/8 > IP address: 127.0.0.2/8 > lo > ..done eth0 name: IBM OSA Express Network card (0.0.0700) > eth0 IP address: 10.80.200.126/24 > eth0 > ..doneWaiting for mandatory devices: qeth-bus-ccw-0.0.0600 > qeth-bus-ccw-0.0.510 > 0 qeth-bus-ccw-0.0.5200 qeth-bus-ccw-0.0.a006 __NSC__ > 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 > qeth-bus-ccw-0.0.0600 No interface found > ..failed qeth-bus-ccw-0.0.5100 No interface found > ..failed qeth-bus-ccw-0.0.5200 No interface found > ..failed qeth-bus-ccw-0.0.a006 No interface found > ..failedSetting up service (localfs) network . . . . . . . . . > ...fail > ed > > *** > *** Please return to your X-Server screen to finish installation > *** > > pcilib: Cannot open /proc/bus/pci > lspci: Cannot find any working access method. > > starting VNC server... > A log file will be written to: /var/log/YaST2/vncserver.log ... > > *** > *** You can connect to 10.80.200.126, display :1 now with > vncviewer > *** Or use a Java capable browser on > http://10.80.200.126:5801/ > <redir.aspx?C=c96b8535c5c94f02aa7b733fd5bd1f87&URL=http%3a%2f%2f10.80.200.126%3a5801%2f> > > *** > > (When YaST2 is finished, close your VNC viewer and return to this window.) > > *** Starting YaST2 *** > This is a sandbox system, so for various reasons has many network > interfaces. > But for this run, the 0600, 5100, 5200, and a006 interfaces have been > removed > from the directory. That is the reason for all the no interface found > messages. > We have also made an update run where we removed the interfaces from the > guest before we started. The results were the same. We try to connect > to 10.80.200.126 > and do not get a response. > Any ideas? > Any additional documentation required? > Thanks, > Ron > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu 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/
