Steve, I didn't mean the VM operator's console, I meant the virtual console for the guest. Is the NIC defined properly and coupled to the VSWITCH? #cp q nic details #cp q lan details
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL 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 (which returns "qeth device eth0 does not seem to be present, delaying initialization". The only problem seen 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 correct. So, what happens if you do a "modprobe qeth" command? You should see some things on the VM console as to what is detected and used (or not). Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: 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 to the OSA Express and eth0 (alias eth0 qeth) was already defined. I did change chandev.conf lines to reflect the different devnos associated with the new simulated device and not the real OSA device. I think that should be correct? -----Original Message----- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Thursday, April 15, 2004 8:52 AM To: [EMAIL PROTECTED] 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 The portname 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 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 AS guests to the rest of the world. I have created the controller, switch and simulated QDIO devices in VM and a query on the devices (Q LAN DET) shows that all is well - including that connection to the OSA Express. The one thing that I'm confused about is which driver Linux would require to access the new QDIO device. Right now I am aliasing eth0 to qeth in modules.conf but when the guest is started it complains that the interface is not responding. When I do an /sbin/ifconfig -a I do not see eth0, only local and eth1 (Hipersockets) are initialized. Am I using the correct Linux driver module for this type of connection? Also, is there something that I might be missing in the DEF or COUPLE statements for the simulated NIC devices that's new to VM4.40? Currently using: To define the NIC: DEF NIC 3909 TYPE QDIO DEV 3 COUPLE 3909 TO SYSTEM VSS3000 To define the Controller in PROFILE TCPIP: VSWITCH CONTROLLER ON 0206 To define the Virtual Switch: DEF VSWITCH VSS3000 RDEV 0206 CON PORT DEV0200 Any input's appreciated, thanks in advance. Steve ---------------------------------------------------------------------- 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 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 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 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 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 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
