* cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIO Name: UNASSIGNED Devices: 3
AR 0015 MAC: 02-00-01-00-00-0E LAN: * None MFS: 8992 AR 0015 RX Packets: 0 Discarded: 0 Errors: 0 AR 0015 TX Packets: 0 Discarded: 0 Errors: 0 AR 0015 RX Bytes: 0 TX Bytes: 0 AR 0015 Unassigned Devices: AR 0015 Device: 0AA0 Unit: 000 Role: Unassigned AR 0015 Device: 0AA1 Unit: 001 Role: Unassigned AR 0015 Device: 0AA2 Unit: 002 Role: Unassigned But the other one (one without any RDEVs): * cp q v nic a90 details AR 0015 Adapter 0A90.P00 Type: QDIO Name: UNASSIGNED Devices: 9 AR 0015 MAC: 02-00-01-00-00-0B VSWITCH: SYSTEM VSWTMK00 AR 0015 RX Packets: 6 Discarded: 0 Errors: 0 AR 0015 TX Packets: 5 Discarded: 0 Errors: 0 AR 0015 RX Bytes: 277 TX Bytes: 204 AR 0015 Connection Name: Session Established AR 0015 Device: 0A90 Unit: 000 Role: CTL-READ AR 0015 Device: 0A91 Unit: 001 Role: CTL-WRITE AR 0015 Device: 0A92 Unit: 002 Role: DATA vPort: 0085 Index: 0085 AR 0015 Options: IPv4 AR 0015 Unicast IP Addresses: AR 0015 192.168.199.2 MAC: 02-00-01-00-00-0B Local AR 0015 Unassigned Devices: AR 0015 Device: 0A93 Unit: 003 Role: Unassigned AR 0015 Device: 0A94 Unit: 004 Role: Unassigned AR 0015 Device: 0A95 Unit: 005 Role: Unassigned AR 0015 Device: 0A96 Unit: 006 Role: Unassigned AR 0015 Device: 0A97 Unit: 007 Role: Unassigned AR 0015 Device: 0A98 Unit: 008 Role: Unassigned These devices were all listed as "FREE" before I started this. Frank M. Ramaekers Jr. -----Original Message----- From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf Of Alan Altmark Sent: Friday, August 27, 2010 3:08 PM To: [email protected] Subject: Re: VSWITCH defined VSE TCP/IP fails On Friday, 08/27/2010 at 03:18 EDT, "Frank M. Ramaekers" <[email protected]> wrote: > The error message description is less than hepful: > > REASON = X?0035? The Startlan function failed. This is most likely indicated by > RETCODE=E080. The OSA/SF book, which has those error codes in it, says: E080 A LAN connection could not be made, possibly for one of the following reasons: The cable may not be present The LAN may not be functioning The port may have been disabled from the Support Element (SE) of the server This suggests that the NIC is not COUPLEd to the VSWITCH. You need to issue 'cp q v nic aa0 details'. Alan Altmark z/VM Development IBM Endicott _____________________________________________________ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at [email protected].
