Re: VSWITCH
Gordon, The VM userid must have a NIC defined as type qdio, eg. DEF NIC 480 TYPE QDIO Couple it to the vswitch, eg. COUPLE 480 SYSTEM VSW1 I have defined the VSWITCH in my SYSTEM CONFIG file: DEF VSWITCH VSW1 RDEV 5000 4F00 5000 is the primary OSA triplet and 4F00 is the failover Grant the VM userid access with SET VSWITCH VSW1 GRANT vm_id Define your vswitch controllers, I use the default VSWCTRL1 and VSWCTRL2. Include IUCV *VSWITCH in their entries. Create entries for them in the SYSTEM DTCPARMS file on TCPMAINT :nick.VSWCTRL1 :type.server :class.stack :exit.VSWCTRL The zLinux file, /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 BOOTPROTO=static BROADCAST= NETMASK= NETTYPE=qeth NETWORK= ONBOOT=yes SUBCHANNELS=0.0.0480,0.0.0481,0.0.0482 TYPE=Ethernet Hope this helps, Betsie Wolfe, Gordon W wrote: Can someone point me to a reference for configuring Linux SLES9-SP1 with z/VM 5.1 using VSWITCH? We're trying to convert over from guest LANs. All the references I've been able to find are either for z/VM 4.4 or for SLES8, or both. I've tried Wunder,Odonez and MacIsaac, z/VM VSWITCH with failover (no linux details) Vic Cross VSWITCH and VLAN features of z/VM 4.4 (z/VM 4.4 and SLES8) Simon Williams, Networking overview for Linux on zSeries (z/VM 4.4 and SLES8) linuxvm.org/how-to SLES9 has changed how it handles the qeth driver from sles8. We no longer use /etc/chandev.conf, but files within /etc/sysconfig/network. I need to know how to set up those files for VSWITCH, and if there are any others I should be aware of. Some people are like Slinkies... Not really good for anything, but they still bring a smile to your face when you push them down a flight of stairs. Gordon Wolfe, Ph. D. (425)865-5940 VM Technical Services, The Boeing Company -- 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
Re: SLES9 on zVM 4.4 Install Issue
Mark, Both SuSE SLES 9 and RedHat 4 are good zLinux distributions and usually include IBM's recommended modules. Have you tried an NFS install? This works well on both SuSE and RH. Betsie Llewellyn, Mark wrote: Thanks for the responses! We had looked into firewall problem as well as the relative path name. Neither seem to be the issue here, unfortunately. We've scrounged around the shop for a TCPIP guru and plan to drag them over here to see what might be in the way. We're still sure it's something simple and stupid. Changing the subject somewhat: We're playing with a trial version of SLES9. Eventually we're going to have to *groan* pay for Linux, and we were wondering what the flavor of the month was. It appears that SuSE seems to have an edge in the zVM world. Out of curiosity, what are most shops running? We are also very interested in Linux management software, such as Aduva OnStage and Levanta. We've seen both products demonstrated, and are impressed. Is anyone out there using them? Any preferences? Thanks very much for your guidance! Mark Llewellyn Visa USA -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Post, Mark K Sent: Monday, August 01, 2005 12:21 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES9 on zVM 4.4 Install Issue David's response about firewall rules is definitely worth looking into, particularly since the IP address of your Linux/390 guest is different from any of the other systems you've tried to reach the FTP server with. The second note is that the path to the installation files on your FTP server _must_ be a relative path, unless your FTP server puts you into a chroot environment, where your home directory looks like it is / and not /home/userid. If you mounted the installation files underneath your home directory, then just specify ./remotecdrom and not /remotecdrom. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Llewellyn, Mark Sent: Monday, August 01, 2005 2:27 PM To: LINUX-390@VM.MARIST.EDU Subject: SLES9 on zVM 4.4 Install Issue Greetings - our issue is very similar to one posed by John Bohnsack back in Feb 05. Simply put, we've been trying to persuade our SLES9 guest to see our FTP server. We have an OSA Express card attached to the guest, and we fall down through the SLES9 installation script, only to have our FTP session time out, although it is able to ping it. The output from the script is below, and the entered IP addresses and directory names are correct. The odd thing: We're a TPF shop, and use VPARS to clone many instances of TPF for development. We ARE able to establish a connection with the FTP Server from a TPF session under zVM. But we get timeouts on our Linux guest (same VM). We've tried swapping OSA cards/addresses, and SAMBA (same result). We're Glow-in-the-Dark Newbies at this, and we're stumped. We have no doubt this is something simple and probably stupid. Any guidance at all would be greatly appreciated! Here's a console fragment: Please specify the installation Source: 1) NFS 2) SAMBA 3) FTP 0) Abort Choice: 15:48:24 3 15:48:24 Please enter the IP-Number of the host providing the installation media: 15:49:26 10.172.43.21 15:49:26 PING 10.172.43.21 (10.172.43.21) 56(84) bytes of data. 64 bytes from 10.172.43.21: icmp_seq=1 ttl=121 time=29.0 ms 15:49:27 64 bytes from 10.172.43.21: icmp_seq=2 ttl=121 time=28.9 ms 15:49:28 64 bytes from 10.172.43.21: icmp_seq=3 ttl=121 time=35.3 ms --- 10.172.43.21 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2021ms rtt min/avg/max/mdev = 28.999/31.135/35.308/2.954 ms Please enter the directory of the installation media: 15:49:34 Jul 29 22:49:34
Re: Doing a sles8 install
Did you run the last step of the install? There is one more step after it first boots from /dev/dasda1. Since I use ssh, I have to run /usr/lib/YaST2/bin/YaST2.sshinstall Betsie James Melin wrote: Just to make sure that the test VM system is working the way I need it to The installer runs. Things get put where they should be... it shuts down. Then I go and IPL the newly installed system and The last things on the screen are: RAMDISK: Compressed image found at block 0 Freeing initrd memory: 644k freed VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 14k freed # # # It never makes it all the way up. I'm not sure why. Not much besides CD seems to be available I can bring it up and mount things, but I'm not sure what to look at to figure this one out. -- 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
Re: rexec - how to enable in SuSE9
Ranga, rsh-server has to be installed before you can chkconfig rexec on Betsie Ranga Nathan wrote: One of the developers is harassing us to allow rexec. Although I am opposed to it vehemently, I have to turn it on for a brief period. For some reason I can not find any reference to rexecd or a stanza for it under /etc/xinetd.d. I am not sure if SuSE has killed it for security reasons. __ Ranga Nathan / CSG Systems Programmer - Specialist; Technical Services; BAX Global Inc. Irvine-California Tel: 714-442-7591 Fax: 714-442-2840 -- 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
Re: LVM problem
Phil, Run fdasd against them to create the partition and use the partition name in the pvcreate command, eg. pvcreate /dev/dasdm1, and in the vgcreate command. Betsie Phil Smith III wrote: I'm trying to set up an LVM. I have 3 10MB disks defined at 8001, 8002, 8003; they appear in /proc/dasd/devices as: 8001(ECKD) at ( 94: 48) is dasdm : active at blocksize: 4096, 2520 blocks, 9 MB 8002(ECKD) at ( 94: 52) is dasdn : active at blocksize: 4096, 2520 blocks, 9 MB 8003(ECKD) at ( 94: 56) is dasdo : active at blocksize: 4096, 2520 blocks, 9 MB So far so good. I dasdfmt-ed them, then did a vgscan and a pvcreate /dev/dasdm /dev/dasdn /dev/dasdo. That worked. Now pvscan and vgcreate both whine. pvscan says: pvscan -- reading all physical volumes (this may take a while...) pvscan -- ERROR pv_read(): read reading physical volumes vgcreate says: vgcreate -- ERROR pv_read(): read reading physical volumes I tried the dd if=/dev/zero of=/dev/dasd[mno] bs=1k count=1 trick, no change. Running pvscan with -d suggests that it's getting all the way to the end of dasdo before whining. It did say: 1 pv_read_all_pv -- device /dev/dasdm NOT used 1 pv_read_all_pv -- device /dev/dasdn NOT used 1 pv_read_all_pv -- device /dev/dasdo NOT used as it handled each of those. I'm not sure why it said that (but then, I'm not sure why it's doing most of what it's doing). I tried mke2fs on the disks as well, trying to Easter Egg it, but still no change. This is Logical Volume Manager 1.0.5(mp-v6) on SLES8. Anyone got any ideas? I get the list digested so direct replies as well as list replies are appreciated, but of course beggars can't be choosers... -- 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
Re: FW: LVM DISK PROBLEM!!
Melissa, To reinitialize a physical volume, use pvcreate -ff /dev/dasd... Betsie Perry, Melissa wrote: From: Perry, Melissa Sent: Thursday, June 23, 2005 1:12 PM To: '[EMAIL PROTECTED]' Subject: LVM DISK PROBLEM!! Got myself in a bind trying to remove of a volume that belongs to LVM ( I wanted to redo the whole LVM thing)...I did an unmount and then an lvremove of the disk...I then tried to to a vgcreate and it said that the name still existed. I then went into /dev/... and deleted the entry for the volume group. When I try to do the pvcreate or a vgremove, I get the following error ERROR: VGDA in kernel and lvmtab are NOT consistent; please run vgscan I have run this to no avail. HELP!! I am VERY VERY new to all of this...I am a Z/os person! -- 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
Re: risk if I relabel an LVM DASD Volume
I have run fdasd against LVM minidisks and recreated the VTOC from 0x0300 (for example) to a standard pack name that can be read by the z/OS systems. Betsie Little, Chris wrote: My initial guess is that it doesn't use the volume label. I know that you can change device numbers, and device names and lvm will still find it. However, don't take my word for it. i've screwed up before. -Original Message- From: Uriel Carrasquilla [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 21, 2005 5:00 PM To: LINUX-390@VM.MARIST.EDU Subject: risk if I relabel an LVM DASD Volume Question: would my volume-group and logical-volume (LVM) be in trouble if I re-label one or more of the physical volumes allocated to the lv? I forgot to label the volumes when I created them and my zOS guy is getting them in his reports (bad label). We use zOS DF/DSS for backups so I am very much forced into having the correct label. I was thinking to IPL SLES-9 without the LVM's in /etc/fstab. That way I could do the fdasd -l xxx. My other option is to backup the data, delete the LV-group/volume. Re-label. Then put it back. A lot of work. any suggestions are welcome, except killing the zOS guy. Regards, [EMAIL PROTECTED] NCCI Boca Raton, Florida 561.893.2415 greetings / avec mes meilleures salutations / Cordialmente mit freundlichen Grüßen / Med vänlig hälsning The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. -- 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
Re: Change Linux DASD Label
Use fdasd /dev/dasdg (no partition number) Choose V to recreate vtoc Betsie Michael Coffin wrote: Howdy Folks, Ok, one last question and then I'll go away for a while. :) How do you change the Linux DASD label WITHOUT reformatting the disk?!?! I have a need to reformat/change the Linux DASD label only, but looking at DASDFMT I don't see this as an option. I guess I'm looking for the Linux equivalent of FORMAT 191 A (LABEL. -TIA Michael Coffin, President MC Consulting Company, Inc. PMB 123 289 Park Street Stoughton, Massachusetts 02072 Voice: (781) 344-9837FAX: (781) 344-7683 [EMAIL PROTECTED] www.mccci.com We employ aggressive SPAM filters. If you cannot reply or send email to mccci.com go to www.mccci.com/spamblockremove.php -- 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
Re: Expanded Storage
David, Your XSTORE is being used for MDCache (usage= 12%, and max=1024). You can force MDCache to only use main store with SET MDCACHE XSTORE 0M 0M SET MDCACHE STORAGE 0M 4096M Betsie David Boyes wrote: q xstore XSTORE= 1024M online= 1024M XSTORE= 1024M userid= SYSTEM usage= 99% retained= 0M pending= 0M XSTORE MDC min=0M, max=1024M, usage=12% XSTORE= 1024M userid= (none) max. attach= 1024M Does the above mean that the xstore is being used by the system already without me telling the system how/when/where to use it ? Yes -- you're using 12% of your XSTORE for minidisk cache and I'd suspect the rest is in use as 1st tier paging. If xstore is available, then CP uses it for various things (paging hierarchy, minidisk cache, etc). CP has some default settings (which looks like what you're getting) that aren't really optimal for Linux workloads. You may want to cap MDC or force it to real storage, and I've seen arguments for disabling it entirely. See SET MDC in the docs for twiddling it in and out of XSTORE or turning it off. See your favorite monitoring tool for more details on how CP is using XSTORE. Do the users on the system benefit just by having xstore defined to the system ? Absolutely! If XSTORE is available, CP pages to it first before going to real DASD. This lets you sustain astonishing paging rates -- I think Rob v.d.H. has reported 40,000 pages/sec with good response time, vs 50-60 pps on real disk. Overcommitting RAM for VDISK depends on good VM paging performance, so XSTORE wins big. VM: Autonomic, when Autonomic Wasn't Cool. 8-) -- 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
Re: Red Hat Enterprise Linux and NSS
Gordon, How are you feeling?Those of us at SHARE were concerned when you left to go home. Betsie Wolfe, Gordon W wrote: Is RHEL4 out GA yet? So one elephant says to another, You'll never believe what happened last night. I was trying on Groucho Marx's pajamas--and he shot me! Gordon Wolfe, Ph.D. (425)865-5940 VM Technical Services, The Boeing Company -- From: Post, Mark K Reply To: Linux on 390 Port Sent: Thursday, March 10, 2005 1:27 PM To: LINUX-390@VM.MARIST.EDU Subject:Re: Red Hat Enterprise Linux and NSS I'm not sure about RHEL3, but RHEL4 should. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Kent Pirkle Sent: Thursday, March 10, 2005 3:15 PM To: LINUX-390@VM.MARIST.EDU Subject: Red Hat Enterprise Linux and NSS Does anyone know if RHEL v3 or v4 for zSeries supports this? http://www.vm.ibm.com/linux/linuxnss.html Thanks -- 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
Re: Can't find default gateway during SLES 9 install
Patrick, The default gateway is defined in /etc/sysconfig/network/routes eg: default 130.35.52.1 - - Patrick B. O'Brien wrote: Almost there; I can ping my SLES 9 guest if I'm in its same segment. Per the below, SLES 9 can't find the default gateway. I know its there because I can ping it from a SLES 8 guest. But, looking in my SLES 8 guest's /etc/sysconfig/network/ ifcfg-eth0 file, I don't see the DG there either, hmm. Also, doing a traceroute from a SLES 8 guest or a ping, it says 10.131.150.254 is the next hop. Any thoughts and thank you! Configuration for eth0 will be: Full host name : NVLNXT25.STATE.NV.US IP address : 10.131.150.125 Net mask : 255.255.255.0 Broadcast address: 10.131.150.255 Gateway address : 10.131.150.254 DNS IP address : 10.131.11.24 DNS search domain: STATE.NV.US MTU size : 1500 Is this correct (Yes/No) ? . 64 bytes from 10.131.150.125: icmp_seq=1 ttl=64 time=0.061 ms 64 bytes from 10.131.150.125: icmp_seq=2 ttl=64 time=0.056 ms 64 bytes from 10.131.150.125: icmp_seq=3 ttl=64 time=0.057 ms --- 10.131.150.125 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.056/0.058/0.061/0.002 ms Trying to ping the IP address of the Gateway: PING 10.131.150.254 (10.131.150.254) 56(84) bytes of data. --- 10.131.150.254 ping statistics --- 10 packets transmitted, 0 received, 100% packet loss, time 9014ms Warning: The gateway address 10.131.150.254 did not ping. Do you want to ignore this error and continue anyway? (Yes/No) your choice (0-10): 0 SuSe8Guest $ ping 10.131.130.254 PING 10.131.130.254 (10.131.130.254) from 10.131.150.122 : 56(84) bytes of data. 64 bytes from 10.131.130.254: icmp_seq=1 ttl=254 time=2.01 ms 64 bytes from 10.131.130.254: icmp_seq=2 ttl=254 time=1.58 ms -- 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
SLES 9 and raw devices
Hi I'm trying to find out if anyone has successfully accessed raw devices in SLES9. We're on kernel 2.6.5-7.139 (SP1). The error I get is Cannot open master raw device '/dev/rawctl /etc/modprobe.conf has the entry 'alias char-major-162 raw' Betsie -- 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
Re: SLES9 mkinitrd problem? (was: dasd/initrd question for 2.6)
Daniel, This worked for me: Install with devices 200-206. After first boot, I updated /etc/zipl.conf and added dasd=200-209,300-31f to the parameters line, prceeding root= Ran /sbin/zipl -c /etc/zipl.conf Shutdown. Updated the zLinux guest directory with minidisks at 300, 30F, 310-312. Booted. cat /proc/dasd/devices had 300 as dasdk, 30F as dasdz, 310 as dasdaa, 311 as dasdab and 312 as dasdac There were no entries for the addresses that had no minidisks, example: 301 at 94: 44 is dasdl : unknown Betsie Daniel Jarboe wrote: mkinitrd appears to add the dasd devices as they appear in alphabetical order of /sys/block. Which means dasda, dasdaa, dasdab, dasdac, dasda* before dasdb, dasdc, etc. Is anyone else using SLES9 that, after install time, added more devices to put you over 26? Thanks, ~ Daniel -- 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
Re: SLES 9.0 Refresh?
I heard that SP1 would be available on 1/19 with zLinux shortly after. Betsie Ledbetter, Scott E wrote: Someone mentioned recently that they were testing a service pack for SLES9? I can't seem to get a reading from the Novell/SuSE website about avalability of this. Does anyone know a timeframe? Scott Ledbetter StorageTek -- 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
vswitch question
Hi, Anyone know of a way to delete a VSWITCH without IPLing? Betsie -- 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
SLES 9 /etc/chandev.conf
File /etc/chandev.conf does not seem to exist in zLinux SLES9. /etc/modules.conf was replaced by /etc/modprobe.conf Any other changes? What file replaced chandev.conf? Betsie -- 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
Re: ypbind on SLES9 error
Hi Mark, portmap is up and running. ifconfig shows UP BROADCAST RUNNING MULTICAST It's using an OSA card ypbind comes up with either version of yp.conf i.e. domain us.oracle.com broadcast ordomain us.orcacle.com server pasysyp1.us.oracle.com If I use the second version, I must add pasysyp1 to /etc/hosts. No error messages with the second version.Use the broadcast version on SLES8. Betsie Post, Mark K wrote: What kind of interface are you using? Does it have broadcast specified on it when you do an ifconfig command? I don't know if the yp stuff requires portmap to be running or not. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Betsie Spann Sent: Wednesday, January 05, 2005 5:02 PM To: LINUX-390@VM.MARIST.EDU Subject: ypbind on SLES9 error Hi, I'm running SuSE SLES 9, kernel 2.6.5-7.97-s390x glibc-2.3.3-98.28 When I start ypbind, I get the following error: ypbind: RPC: Timed out ypbind:: broadcast: RPC: Can't encode arguments. My IP is x.x 54.18 netmask 255.255.252.0 network x.x.52.0 broadcast x.x.55.255 This works on my SLES8 servers. /etc/yp.conf domain us.oracle.com broadcast The subnet has domain servers but broadcast doesn't seem to work. If I code yp.conf with server and IP instead of broadcast, ypbind comes up. nsswitch.conf has passwd: compat group: compat hosts and services files dns everything else files Any suggestions? Betsie -- 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
ypbind on SLES9 error
Hi, I'm running SuSE SLES 9, kernel 2.6.5-7.97-s390x glibc-2.3.3-98.28 When I start ypbind, I get the following error: ypbind: RPC: Timed out ypbind:: broadcast: RPC: Can't encode arguments. My IP is x.x 54.18 netmask 255.255.252.0 network x.x.52.0 broadcast x.x.55.255 This works on my SLES8 servers. /etc/yp.conf domain us.oracle.com broadcast The subnet has domain servers but broadcast doesn't seem to work. If I code yp.conf with server and IP instead of broadcast, ypbind comes up. nsswitch.conf has passwd: compat group: compat hosts and services files dns everything else files Any suggestions? Betsie -- 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
Re: more than 26 disks
Ken, For any dasd greater than dasdz you must run mknod mknod -m 660 /dev/dasdaa b 94 104 mknod -m 660 /dev/dasdaa1 b 94 105 mknod -m 660 /dev/dasdab b 94 108 mknod -m 660 /dev/dasdab1 b 94 109 Get the major/minor node numbers from a cat of /proc/dasd/devices I don't create nodes for partitions 2 and 3 because I don't use them. No harm in doing it though mknod -m 660 /dev/dasdaa2 b 94 106 etc Betsie - Original Message - From: Ken Vance [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, April 22, 2004 9:22 AM Subject: more than 26 disks Hi, We were adding a large number of disks to our SuSE8 image. Normally, it adds the dasd as dasda, dasdb, etc. When we added disk 27, it adds the dasd as dasdaa. Here is the log when the devices were added: dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]: 3390/0A(CU:3990/01) Cyl:3338 Head:15 dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]: 3390/0A(CU:3990/01) Cyl:3338 Head:15 dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]: DIAG210 returned VRDCRCCL = 04, VRDC dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]: XRC_supported reset because of missi dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]: 3390/0A(CU:3990/01): Configuration d Apr 22 13:00:02 linvm01 kernel: debug: dasdz: new level 3 Apr 22 13:00:02 linvm01 kernel: dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]: 3390 Apr 22 13:00:02 linvm01 kernel: dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]: DIAG 82 dasd(eckd): /dev/dasdy ( 94: 96),[EMAIL PROTECTED]: (4kB blks): 2403360kB at 48kB/trk li Apr 22 13:00:02 linvm01 kernel: dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]: XRC_ Apr 22 13:00:02 linvm01 kernel: dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]: 3390 Apr 22 13:00:02 linvm01 kernel: dasd(eckd): /dev/dasdy ( 94: 96),[EMAIL PROTECTED]: (4kB debug: dasdaa: new level 3 The Linux administration group then formatted and made a file system on the various dasd volumes. He had a problem when he went to format the dasdaa volume. It could not find the dasdaa device. He created it, and then he could format it. When he tried to make a files system, it again failed. When he creates the filesystem, he specifies the dasd without a number, ie. dasdj, dasdk, etc. I noticed in Mark Post's presentation , he has the following: 2.4.x Kernels mke2fs -b 4096 /dev/dasd?1,2,3 mke2fs -b 4096 /dev/dasda1 mke2fs -b 4096 /dev/dasda2 mke2fs -b 4096 /dev/dasda3 What is the difference betweem 1, 2, and 3. Also, why did the system not create the dasdaa, and dasdaa1 information? Is there something special we must do when we reach disk number 27? Are the numbers used if you partition the drive into smaller areas? We only have one area on the disk, so I would guess that it would be the 1. Here is the log: linvm01:~ # dasdfmt -b 4096 -d ldl -f /dev/dasdaa dasdfmt: Unable to open device /dev/dasdaa: No such file or directory This was true: linvm01:~ # ls -la /dev/dasda* brw-rw1 root disk 94, 0 Nov 6 2002 /dev/dasda brw-rw1 root disk 94, 1 Nov 6 2002 /dev/dasda1 brw-rw1 root disk 94, 2 Nov 6 2002 /dev/dasda2 brw-rw1 root disk 94, 3 Nov 6 2002 /dev/dasda3 And then (checking major/minor numbers before) linvm01:~ # mknod -m 660 /dev/dasdaa b 94 104 linvm01:~ # ls -la /dev/dasdaa brw-rw1 root root 94, 104 Apr 22 17:27 /dev/dasdaa linvm01:~ # chown root:disk /dev/dasdaa linvm01:~ # ls -la /dev/dasdaa brw-rw1 root disk 94, 104 Apr 22 17:27 /dev/dasdaa Afterwards dasdformat runs without complains. linvm01:~ # dasdfmt -b 4096 -d ldl -f /dev/dasdaa Drive Geometry: 3338 Cylinders * 15 Heads = 50070 Tracks I am going to format the device /dev/dasdaa in the following way: Device number of device : 0x274 Labelling device: yes Disk label : LNX1 Disk identifier : 0X0274 Extent start (trk no) : 0 Extent end (trk no) : 50069 Compatible Disk Layout : no Blocksize : 4096 --- ATTENTION! --- All data of that device will be lost. Type yes to continue, no will leave the disk untouched: yes Formatting the device. This may take a while (get yourself a coffee). Finished formatting the device. Rereading the partition table... ok When I tried a mkfs it failed. linvm01:/ # /sbin/mkfs.ext3 -b 4096 /dev/dasdaa mke2fs 1.28 (31-Aug-2002) mkfs.ext3: No such device while trying to determine filesystem size linvm01:/ # ls -la /dev/dasdaa brw-rw1 root disk 94, 104 Apr 22 17:27 /dev/dasdaa linvm01:/ # Thanks, Ken Vance Amadeus -- 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
Re: WebSphere on SLES8-SP3
WebSphere on SLES 8 is only for 31-bit. See GC34-6078 Betsie - Original Message - From: Wolfe, Gordon W [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, April 21, 2004 4:05 PM Subject: WebSphere on SLES8-SP3 Hi, List: Here's a unique one for you. We're trying to put up WebSphere on SuSE SLES8 at the SP3 level, and it doesn't seem to work. It installs all right, but MQSeries won't come up -- it gets a socket error, as noted 'way below. We've been working with IBM's WebSphere support and they've given up. they say the problem is our installation of SuSE. Well, we're pretty vanilla on SLES8-SP3. IBM says they support SLES8 but haven't tested and do not support SP3. Before I open a problem with SuSE, let me take the easy way out and ask the knowlegable elite of this list if any of you have seen this before, or if anyone's tried to get Websphere going on SLES8-SP3. Nature and nature's laws lay hid in night: God said, 'Let Newton Be!' and all was light. - Alexander Pope It did not last; the Devil howling 'Ho! Let Einstein Be!' restored the status quo.- John Collings Squire God Rolled his dice, to Einstein's great dismay: 'Let Feynman Be!' and all was clear as day. - Jagdish Mehra Gordon W. Wolfe, Ph. D. VM Technical Services, The Boeing Company -- From: Cooper, Vickie Sent: Wednesday, April 21, 2004 3:46 PM To: Wolfe, Gordon W Subject: RE: IBM's response... Hi Gordon: The only command I issue is to try and start WebSphere: ./startServer.sh server1 Then it runs for awhile and I get this error: com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2059 MQJE011: Socket connection attempt refused at com.ibm.mq.MQManagedConnectionJ11.init(MQManagedConnectionJ11.java:239) at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQCl ientManagedConnectionFactoryJ11.java:276) at com.ibm.mq.MQClientManagedConnectionFactoryJ11.createManagedConnection(MQCli entManagedConnectionFactoryJ11.java:296) at com.ibm.mq.StoredManagedConnection.init(StoredManagedConnection.java:80) at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConnectionMa nager.java:171) at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.java:737) at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:671) at com.ibm.mq.MQQueueManager.init(MQQueueManager.java:452) at com.ibm.mq.MQSPIQueueManager.init(MQSPIQueueManager.java:52) at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1659) --Vickie -Original Message- From: Wolfe, Gordon W Sent: Wednesday, April 21, 2004 3:23 PM To: Cooper, Vickie Subject: RE: IBM's response... Vickie, Can you send me the commands you are issuing and the error messages you get. I can open a problem with SuSE and post it on with the Linux-390 listserver. Nature and nature's laws lay hid in night: God said, 'Let Newton Be!' and all was light. - Alexander Pope It did not last; the Devil howling 'Ho! Let Einstein Be!' restored the status quo.- John Collings Squire God Rolled his dice, to Einstein's great dismay: 'Let Feynman Be!' and all was clear as day. - Jagdish Mehra Gordon W. Wolfe, Ph. D. VM Technical Services, The Boeing Company -- From: Cooper, Vickie Sent: Wednesday, April 21, 2004 3:17 PM To: Darbro, Brandon S; Wolfe, Gordon W Subject:IBM's response... The service pack seems to breaking the ability of the message broker to determine the user and group membership of the process. Perhaps you can ask SUSE support whether they know if they have an known issue regarding this. Our support matix says the United Linux 1.0, no service packs installed, for the Linux S390 platform. You are using a platform which we have not tested, therefore we don't support it. --Vickie Vickie Cooper OS/390 Web Services FOCUS/EDA Technical Support Phone: (425) 957-5502 Email: [EMAIL PROTECTED] -- 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
dasd_diag_mod mission in SLES8 64bit
The Release Notes for SLES 8 S/390 zSeries Service Pack 2 (SP2), 1.2 Other enhancements, S/390 specific fixes mentions disable DASD DIAG discipline on 64-bit becuase of z/VM issues (#26732). Betsie -- 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
perl-DBI for zSeries Linux?
Has anyone found an rpm for perl-DBI for zSeries Linux? Betsie -- 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
Re: RHEL Adding DASD
RHEL? Update /etc/modules.conf Betsie - Original Message - From: ODOT zSeries Linux [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, March 01, 2004 3:12 PM Subject: FW: RHEL Adding DASD -- From: ADAMS Steven Sent: Monday, March 01, 2004 3:12:24 PM Subject: RHEL Adding DASD Auto forwarded by a Rule Having a rough time adding a couple more Mod-3's to a guest and I think I'm missing something. Here's where I've been so far: 1. Added the MDISK entries to user direct for the appropriate VM guest 2. CMS format the new MDISK's 3. In Linux, added the devno's to the dasd_mod option line 4. IPL the guest and no DASDF or DASDG 5. Got frustrated and added the 500 and 501 devno's to zipl.conf's kernel parm line 6. IPL the guest and still no DASDF or DASDG 7. Did an echo add device range=0500 /proc/dasd/devices works fine (same results for 0501). Anyone have any suggestions as to what I'm missing? (it's more than likely something stupid) Steve
Re: VM Linux OSA Problems
On z/VM 4.4 VM63385 is required. It's an enhancement created after z/VM 4.4 went GA. We saw great response on the Linux guests using the same card as the VM TCP/IP server. Before the ptf went on, the TCP/IP server had lousy response on ping and tracerte. Betsie - Original Message - From: Adam Thornton [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, February 26, 2004 9:15 AM Subject: Re: VM Linux OSA Problems On Thu, 2004-02-26 at 10:56, Little, Chris wrote: we saw something similar once. it was a combination of a bad mproute/tcpip configuration on the vm side and a bad config on the cisco side. Come to think of it, so did I. Flushing the cache on the Cisco helped radically, but we never figured out *why* it had been wrecking performance. In our case, internal communication was fine, but as soon as we left the box and hit the Cisco switch, bad delays happened. Adam
nfs hangs on NetApp NAS device
My RH AS 3.0 system frequently hangs with the message nfs: server pafiler not responding It's a NetApp NAS device that is ro nfs mounted by the entire universe here. My Linux guest frequently waits on it. Then it has to be rebooted. Network restarts hang on the server also. I am using NFS vers 3 with a timeo value of 40 and rsize/wsize of 8192 using UDP. I'm going to try the tcp option next. Any suggestions or known problems, please? Betsie
nfs on RH AS3
Anyone know any reason not to use NFS V3 on RH AS3? Betsie
RHEL3 for s390x gcc 2.95 compatibility libraries
RedHat has said that Rh 3.0 has gcc 2.95 compatibility libraries. I can't find them. Anyone know what they are called? Betsie
Re: RHEL3 for s390x gcc 2.95 compatibility libraries
I can find compat-db-4.0.14-5.s390x.rpm compat-libstdc++-7.2-2.95.3.77.s390x.rpm compat-pwdb-0.62-3.s390x.rpm but nothing called compat-gcc Betsie - Original Message - From: Alan Cox [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, February 23, 2004 1:47 PM Subject: Re: RHEL3 for s390x gcc 2.95 compatibility libraries On Llu, 2004-02-23 at 19:53, Betsie Spann wrote: RedHat has said that Rh 3.0 has gcc 2.95 compatibility libraries. I can't find them. Anyone know what they are called? Betsie I'm not directly familiar with RHEL3 S/390 but the general naming policy is compat-[something].
Re: invalid ICMP type 11 record
Each of my systems that report the message only give their own IP addr. In fact, the first message comes when booting up and after the Binding to the NIS domain message. Is this just a nuisance message then? Should I suspress it in /etc/sysctl.conf? Betsie - Original Message - From: Alan Cox [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, February 23, 2004 3:54 PM Subject: Re: invalid ICMP type 11 record On Llu, 2004-02-23 at 23:12, Betsie Spann wrote: Someone kindly responded to my first question on what might be causing the invalid ICMP type 11 records. He suggested that it may be a bad netmask. I have checked and rechecked my /etc/sysconfig/network and /etc/sysconfig/network-scripts/ifcfg-eth0 files and cannot find a problem. Any other suggestions, please? RHAS3.0 on zSeries under z/VM 4.4 Betsie The problem is almost certainly a bad netmask on the machine that it is logging the ICMP from, not your system.
RH gcc 2.95.x compatibility libraries
Does anyone know which rpm files are the RHEL3 for s390x gcc 3.95.x compatibility libraries? Betsie
Re: Invalid ICMP records
I'm not running Samba. Mine are RH AS 3.0. I've checked /etc/sysconfig/network-scripts/ifcfg-eth0 and the output from ifconfig -a and my netmasks look correct. I create my images by DDRing my disks, so whatever the original problem was has been copied to a second server. Betsie - Original Message - From: Wilson, Eric [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, February 18, 2004 6:07 AM Subject: Re: Invalid ICMP records Alan, Et al; I'm getting this same error from one VM Guests, but not from any of the others. The route tables are identical for all. For me, the difference is, the VM Guest issuing the error is running Sambs, and at boot, I see the error on the console, just after Samba is started. Cheers; E! - Eric Wilson IBM Certified Advanced Technical Expert RedHat Certified Engineer -Original Message- From: Alan Cox [mailto:[EMAIL PROTECTED] Sent: Monday, February 16, 2004 7:09 PM To: [EMAIL PROTECTED] Subject: Re: Invalid ICMP records On Llu, 2004-02-16 at 23:33, Betsie Spann wrote: Hi, A zLinux guest is issuing this message: pazxxq03: nnn.nn.nn.nnn sent an invalid ICMP type 11, code 0 errer to a broadcast: nnn.nn.nn.255 on eth0 The nnn.nnn.nnn.nnn is the IP address, of course. Any suggestions as to where I find information on this type of error, please? One of your other systems (nnn.nn) sent an ICMP error or status message which the zLinux guest received and which the zLinux box considers wrong because it is one the spec says may not be sent broadcast. Generally it indicates one of the boxes has an incorrect netmask
Invalid ICMP records
Hi, A zLinux guest is issuing this message: pazxxq03: nnn.nn.nn.nnn sent an invalid ICMP type 11, code 0 errer to a broadcast: nnn.nn.nn.255 on eth0 The nnn.nnn.nnn.nnn is the IP address, of course. Any suggestions as to where I find information on this type of error, please? Betsie
SLES 8 and LVM
Hi, Anyone using SuSE SLES 8 and LVM? Is the maximum number of logical volumes still 256? The version is 1.0.5-34. Can't find any other rpms for LVM. Betsie
Re: SLES 8 and LVM
It's not necessarily 256 DASD but 256 logical volumes on your volume group. Betsie - Original Message - From: Little, Chris [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 27, 2004 1:29 PM Subject: Re: SLES 8 and LVM Please, can I have enough DASD to need 256 volumes? and yes, I believe the limit with LVM1 is 256. -Original Message- From: Betsie Spann [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 27, 2004 3:26 PM To: [EMAIL PROTECTED] Subject: SLES 8 and LVM Hi, Anyone using SuSE SLES 8 and LVM? Is the maximum number of logical volumes still 256? The version is 1.0.5-34. Can't find any other rpms for LVM. Betsie
Re: SLES 8 and LVM
Thanks everyone. The LVM limitation is real and I'll have to adjust what I'm doing. Betsie - Original Message - From: McKown, John [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 27, 2004 1:45 PM Subject: Re: SLES 8 and LVM -Original Message- From: Little, Chris [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 27, 2004 3:37 PM To: [EMAIL PROTECTED] Subject: Re: SLES 8 and LVM let me rephrase . . . enought dasd for 256 logical volumes :) OK, Get z/VM. Slice 1 3390-3 (3339 cylinders) into 256 minidisks, each being 13 cylinders. Presto! 256 Logical Volumes. -- John McKown Senior Systems Programmer UICI Insurance Center Applications Solutions Team +1.817.255.3225 This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its' content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited.
Re: SLES 8 and LVM
The limitation is 256 logical volumes across all volume groups. Betsie - Original Message - From: Post, Mark K [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 27, 2004 2:22 PM Subject: Re: SLES 8 and LVM Betsie, Is the limitation 256 logical volumes, or 256 logical volumes per physical volume group? Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Betsie Spann Sent: Tuesday, January 27, 2004 4:26 PM To: [EMAIL PROTECTED] Subject: SLES 8 and LVM Hi, Anyone using SuSE SLES 8 and LVM? Is the maximum number of logical volumes still 256? The version is 1.0.5-34. Can't find any other rpms for LVM. Betsie
Re: quick vm question
Chris, 1) If you use DirMaint, the backup directory is a flat file on DIRMAINT 1DB. The systems programmer usually sets up one or more userids that can link to other minidisks without using a link password. 2) If you back up your directory, restore it to another disk that you can link to. 3) Does your stand-alone test system use a copy of the production system? If so, check the directory there. Betsie - Original Message - From: Little, Chris [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, December 16, 2003 10:34 AM Subject: quick vm question we have a level 2 vm guest that hasn't been used in a while. unfortunately, i have forgotten the password for maint. is there any way of retrieving it? +--- + | Chris Little[EMAIL PROTECTED] | | Ok Dept of Human Services Data Services Division (405)522-1306 | +--- +
Re: VM DASD oddness
Eric, I had to attach the VM dasd to another VM Linux guest and run dasdfmt and fdasd first. RHEL doesn't seem to see any disks formatted under VM. Betsie - Original Message - From: Wilson, Eric [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, December 09, 2003 1:16 PM Subject: VM DASD oddness Hey All; I'm not a VM'er so please be gentle... What does Volume has an incompatable disk layout mean? We are trying to install RHEL v 3.0 on a particular VMGuest. We have used this same code many times previous. We are now not seeing any dasd devices in anaconda, and we see the following on the console: dasd(eckd): ECKD discipline initializing dasd(eckd): /dev/dasda ( 94: 0),[EMAIL PROTECTED]: 3390/0C(CU:3990/04) Cyl:188 Head:15 S ec:224 dasd(eckd): /dev/dasda ( 94: 0),[EMAIL PROTECTED]: 3390/0C(CU:3990/04): Configuration da ta read dasd: No request IRQ dasd(eckd): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 3390/0C(CU:3990/04) Cyl:740 Head:15 S ec:224 dasd(eckd): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 3390/0C(CU:3990/04): Configuration da ta read dasd(eckd): /dev/dasda ( 94: 0),[EMAIL PROTECTED]: Volume has incompatible disk layout dasd: No request IRQ dasd(eckd): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: 3390/0A(CU:3990/04) Cyl:2928 Head:15 Sec:224 dasd(eckd): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: Volume has incompatible disk layout dasd(eckd): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: 3390/0A(CU:3990/04): Configuration da ta read dasd: No request IRQ dasd(eckd): /dev/dasdd ( 94: 12),[EMAIL PROTECTED]: 3390/0C(CU:3990/04) Cyl:740 Head:15 S ec:224 All the DASD was formated this way: cpfmtxa ENTER FORMAT, ALLOCATE, LABEL, OR QUIT: format ENTER THE VDEV TO BE PROCESSED OR QUIT: 200 ENTER THE CYLINDER RANGE TO BE FORMATTED ON DISK 0200 OR QUIT: 0-end ENTER THE VOLUME LABEL FOR DISK 0200: lnx200 CPFMTXA: FORMAT WILL ERASE CYLINDERS 0-00187 ON DISK 0200 DO YOU WANT TO CONTINUE? (YES | NO) yes HCPCCF6209I INVOKING ICKDSF. ICK030E DEFINE INPUT DEVICE: FN FT FM, CONSOLE, OR READER CONSOLE ICK031E DEFINE OUTPUT DEVICE: FN FT FM, CONSOLE, OR PRINTER CONSOLE ICKDSF - CMS/XA/ESA DEVICE SUPPORT FACILITIES 16.0TIME: 11:33:04 12/09/03 PAGE 1 ENTER INPUT COMMAND: CPVOL FMT MODE(ESA) UNIT(0200) VOLID(LNX200) NOVFY - ENTER INPUT COMMAND: RANGE(0,187) ICK00700I DEVICE INFORMATION FOR 0200 IS CURRENTLY AS FOLLOWS: PHYSICAL DEVICE = 3390 STORAGE CONTROLLER = 3990 STORAGE CONTROL DESCRIPTOR = EC DEVICE DESCRIPTOR = 0C ADDITIONAL DEVICE INFORMATION = 71002160 ICK04000I DEVICE IS IN SIMPLEX STATE ICK00703I DEVICE IS OPERATED AS A MINIDISK ICK03020I CPVOL WILL PROCESS 0200 FOR VM/ESA MODE ICK03090I VOLUME SERIAL = LNX200 ICK03022I FORMATTING THE DEVICE WITHOUT FILLER RECORDS ICK03011I CYLINDER RANGE TO BE FORMATTED IS 0 - 187 ICK003D REPLY U TO ALTER VOLUME 0200 CONTENTS, ELSE T U ICK03000I CPVOL REPORT FOR 0200 FOLLOWS: FORMATTING OF CYLINDER 0 STARTED AT: 11:33:05 FORMATTING OF CYLINDER 100 ENDED AT: 11:33:18 FORMATTING OF CYLINDER 187 ENDED AT: 11:33:29 VOLUME SERIAL NUMBER IS NOW = LNX200 CYLINDER ALLOCATION CURRENTLY IS AS FOLLOWS: TYPE START END TOTAL - --- - PERM 0 187 188 ICK1I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0 11:33:2912/09/03 ENTER INPUT COMMAND: END ICK2I ICKDSF PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 0 ENTER ALLOCATION DATA TYPE CYLINDERS .. end Ready; T=0.03/0.07 11:33:33 Cheers; E! - Eric Wilson IBM Certified Advanced Technical Expert RedHat Certified Engineer
Re: DASD= Parm for RH EL 3.0 AS
Sully, I was able to replace the parameter line with parameters=200-209 root=/dev/dasda1. I verified it with cat /proc/dasd/devices after the re-boot. Did you run zipl before the shutdown? Betsie - Original Message - From: Scully, William P [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 11:10 AM Subject: DASD= Parm for RH EL 3.0 AS I apologize for not including a subject line in my original note. -Original Message- From: Scully, William P Sent: Wednesday, December 03, 2003 1:14 PM To: Linux on 390 Port (E-mail) Subject: On Red Hat Enterprise Linux 3.0 AS, I find that file /etc/zipl.conf does not contain the dasd=vcuu-vcuu string anymore. And when I add this string and rerun the zipl command it doesn't seem effective. How do you identify all the disks you want to use on this brand of Linux now? William P. Scully Senior Systems Programmer Computer Associates International, Inc William.Scully att CA.com
Re: Guest Lans
cat /etc/sysconfig/network/ifcfg-hsi1 STARTMODE=onboot BOOTPROTO=static IPADDR=10.10.3.3 NETMASK=255.255.255.0 NETWORK=10.10.3.0 BROADCAST=10.10.3.255 DEVICE=hsi1 USERCTL=no ONBOOT=yes cat /etc/sysconfig/network/routes default 130.35.52.1 0.0.0.0 eth0 server ip is 130.35.54.215/255.255.252.0 Betsie Spann VM Systems Programmer - Original Message - From: Wolfe, Gordon W [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, July 10, 2003 10:34 AM Subject: Guest Lans We're in the process of bringing up SLES8. We have a bunch of servers on SLES7 that communicate via CTC's. I have SLES8 up with CTC's, but we want to convert to guest lans. Can someone using SLES8 with a guest lan send me a copy of their file /etc/sysconfig/network/ifcfg-hsi0 Great Minds discuss ideas. Average minds discuss events. Small minds discuss people. - Admiral Hyman Rickover Gordon Wolfe, Ph.D. (425)856-5940 VM Enterprise Servers, The Boeing Company
DirMaint COR PTFs
Hi, I have received the DirMaint PTFs: UV60796 and UV60757 but get errors at the apply: VMFAPP2113E An error was detected while updating the version information for part DVHDMCTL CEX in PTF UV60757 for reason = 5.Both PTFs get the message. Betsie Spann VM Systems Programmer
Re: mke2fs fails for 1TB filesystem
I've experimented with vol group sizes from 1.4TB to 800GB. With the less-than-1TB size, I experimented with vol group PE sizes from 8M to 16M to 32M. The vol group is 633600MB PE size of 8M, I can only stripe logical vols under 100GB in size. PE size of 16M, the largest logical vol with striping is 103GB (105600 MB). PE size of 32M, same as 16M PE, 103GB. Betsie Spann VM Systems Programmer - Original Message - From: Ulrich Weigand [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Tuesday, April 01, 2003 4:50 PM Subject: Re: mke2fs fails for 1TB filesystem Betsie Spann wrote: Has anyone successfully created a filesystem on a 1TB logical volume on SLES7? Is this exactly 1TB, or slightly more? I think you are running into the 2.4 block device layer limit here; it uses 'int' variables in places to represent sector counts, where 1 sector equals 512 bytes. So, at about 1 TB you start getting sign overflows, and weird things happen ... If you make sure you're using a total block device size of slightly *less* than 1 TB, does it work then? mke2fs -b 4096 lvname fails with a segmentation fault. Well, that's a bug in any case, of course. Bye, Ulrich -- Dr. Ulrich Weigand [EMAIL PROTECTED]
mke2fs fails for 1TB filesystem
Has anyone successfully created a filesystem on a 1TB logical volume on SLES7? I created a volume group on 169 model 9's with a physical extent size of 32MB. (also tried 64MB and 128MB).I created a logical volume of 1T without striping. mke2fs -b 4096 lvname fails with a segmentation fault. Couldn't create it with striping; got not enough allocatable/free physical volume space in VG1. SuSE SLES7 2.4.7-31 May 2002 Betsie Spann VM Systems Programmer
LVM and maximum VGDA kernel size
Hi, Apparently, SuSE SLES7 has a maximum VGCA kernel size of 268427264 which limits the size of an LVM logical volume to about 250GB. I'm on 2.4.7-31 May 21, 2002. Does anyone have experience creating a larger logical volume? If so, what linux level (kernel, etc) are you at? Betsie Spann VM Systems Programmer
Re: fdasd never ends
I found a Linux guest at 2.4.7-31, May 21, 2002. I was able to dasdfmt and
fdasd 151 mod 9's after running mknod on the dasdaa - dasdex vols. I
created a logical volume group and am attempting to create a 1TB logical
volume. Now I'm up against mazimum VGDA kernel size of 268427264. Trying
to figure this one out.
Betsie Spann
VM Systems Programmer
- Original Message -
From: James Melin [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, March 30, 2003 11:53 AM
Subject: Re: fdasd never ends
I can't see any reason why you couldn't. I assume you never had mod-9 dasd
up to this point?
|-+
| | Betsie Spann |
| | [EMAIL PROTECTED]|
| | cle.com |
| | Sent by: Linux on|
| | 390 Port |
| | [EMAIL PROTECTED]|
| | IST.EDU |
| ||
| ||
| | 03/28/2003 04:28 |
| | PM |
| | Please respond to|
| | Linux on 390 Port|
| ||
|-+
---
---|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: fdasd never ends
|
---
---|
Jim.
Since I have a 2.4.7 system up, can I just ftp the k_deflt.rpm from the
patch cd and install it?
Betsie Spann
VM Systems Programmer
- Original Message -
From: James Melin [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, March 28, 2003 1:25 PM
Subject: Re: fdasd never ends
Betsie - This is what I get
Linux rockhopper 2.4.7-SuSE-SMP #1 SMP Mon Dec 17 11:23:56 GMT 2001 s390
unknown
Have a great weekend!
|-+
| | Betsie Spann |
| | [EMAIL PROTECTED]|
| | cle.com |
| | Sent by: Linux on|
| | 390 Port |
| | [EMAIL PROTECTED]|
| | IST.EDU |
| ||
| ||
| | 03/28/2003 03:24 |
| | PM |
| | Please respond to|
| | Linux on 390 Port|
| ||
|-+
--
-
---|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: fdasd never ends
|
--
-
---|
James,
What is the output to uname -a?
My current is 2.4.7-SuSE-SMP #1 Tue Oct 30 22:39:07 GMT 2001 s390
Betsie
- Original Message -
From: James Melin [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, March 28, 2003 11:59 AM
Subject: Re: fdasd never ends
Betsie - IPL your initrd from the Patch CD. The kernal that is loaded
from
CD 1 of that distribution really cannot handle 3390-mod 9 volumes. IPL
the
initrd from that patch cd and do the install of your choice. When you
have
installed all the packages but BEFORE you commit to finishing the
installm
you will have to get a new kernel in place from the patch CD before
you
can
IPL that system successfully.
While YAsT was running, but before you commit your changes, you should
open
another FTP session to that machine. Change directories via 'cd
/mnt//usr/bin/ftp' and start the ftp client (since its not part of the
initial ramdisk) by typing ./ftp
Then FTP to a place where you have the patch CD either mounted, or a
copy
of it available and ftp the kernel off of that disk to some place like
/opt
or something. I forget the name of the package so look it up in the
patch
CD tree structure. Once you've located it, bring it into your system
and
run an rpm -i {kernel package name} so that your kernel is updated
properly.
That's basically wat I had to do.
|-+
| | Betsie Spann |
| | [EMAIL PROTECTED]|
| | cle.com |
| | Sent by: Linux on|
| | 390 Port |
| | [EMAIL PROTECTED]|
| | IST.EDU
Re: fdasd never ends
Thanks, Adam. Appreciate the help. Betsie Spann VM Systems Programmer - Original Message - From: Adam Thornton [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, March 31, 2003 11:32 AM Subject: Re: fdasd never ends On Mon, Mar 31, 2003 at 09:24:33AM -0800, Betsie Spann wrote: I found a Linux guest at 2.4.7-31, May 21, 2002. I was able to dasdfmt and fdasd 151 mod 9's after running mknod on the dasdaa - dasdex vols. I created a logical volume group and am attempting to create a 1TB logical volume. Now I'm up against mazimum VGDA kernel size of 268427264. Trying to figure this one out. http://www-106.ibm.com/developerworks/library/l-lvm2.html Basically, make your extents bigger. 4M extents give you a maximum size of 256G. So you need at least 16M extents for a 1T filesystem. Create your volume groups with vgcreate -s 16M name /dev/dasdXY (Or give yourself room to grow and vgcreate -s 32M) Adam
Re: fdasd never ends
Adam, Was able to build a volume group and I get the message maximum logical volume size 1023.97 Gigabyte. I have 153 volumes, totalling 1077120 MB with a PE of 16MB. When creating the logical volume, I get not enought allocatable/free physical volume space in VG1, please check if physical volumes are allocatable. I ran vgscan and can see the vg. I ran pvscan and can see all 153 physical volumes with 6.88 GB free on each. Total 153 1.03 TB. I've tried lvcreate -L 1T -i 128 -I 64 -n LV1 VG1 a couple of times varying the -I value. Any other suggestions? Betsie Spann VM Systems Programmer - Original Message - From: Adam Thornton [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, March 31, 2003 11:32 AM Subject: Re: fdasd never ends On Mon, Mar 31, 2003 at 09:24:33AM -0800, Betsie Spann wrote: I found a Linux guest at 2.4.7-31, May 21, 2002. I was able to dasdfmt and fdasd 151 mod 9's after running mknod on the dasdaa - dasdex vols. I created a logical volume group and am attempting to create a 1TB logical volume. Now I'm up against mazimum VGDA kernel size of 268427264. Trying to figure this one out. http://www-106.ibm.com/developerworks/library/l-lvm2.html Basically, make your extents bigger. 4M extents give you a maximum size of 256G. So you need at least 16M extents for a 1T filesystem. Create your volume groups with vgcreate -s 16M name /dev/dasdXY (Or give yourself room to grow and vgcreate -s 32M) Adam
Re: fdasd never ends
Adam, Recreated the volume group with physical extents of 32M. A 1TB lv could be created if I didn't use striping, otherwise only an 850GB lv was possible. I was using -i 128 for striping and letting the stripe size default to 16KB. I tried various combinations of stripe size (the -I) but seemed to get the bigger lv with a default stripe size of 16KB. Betsie Spann VM Systems Programmer - Original Message - From: Adam Thornton [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, March 31, 2003 11:32 AM Subject: Re: fdasd never ends On Mon, Mar 31, 2003 at 09:24:33AM -0800, Betsie Spann wrote: I found a Linux guest at 2.4.7-31, May 21, 2002. I was able to dasdfmt and fdasd 151 mod 9's after running mknod on the dasdaa - dasdex vols. I created a logical volume group and am attempting to create a 1TB logical volume. Now I'm up against mazimum VGDA kernel size of 268427264. Trying to figure this one out. http://www-106.ibm.com/developerworks/library/l-lvm2.html Basically, make your extents bigger. 4M extents give you a maximum size of 256G. So you need at least 16M extents for a 1T filesystem. Create your volume groups with vgcreate -s 16M name /dev/dasdXY (Or give yourself room to grow and vgcreate -s 32M) Adam
fdasd never ends
Hi, SuSE SLES7, 2.4.7-SuSE-SMP Ran dasdfmt on a 3390-9 but fdasd never seems to finish. I ran fdasd /dev/dasdc, picked option 'n' for native linux, checked it with the print option and then hit 'w' to write the VTOC. messages: writing VTOC... rereading partition table ... 6 dasdc:VOL1/ 0X0202: dasdc and then sits there for ever. I have only the main console and can't telnet in to run TOP. Any suggestions? Anyone else have problems with fdasd and model 9's with this level of Linux/390? Betsie
Re: fdasd never ends
James,
What is the output to uname -a?
My current is 2.4.7-SuSE-SMP #1 Tue Oct 30 22:39:07 GMT 2001 s390
Betsie
- Original Message -
From: James Melin [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, March 28, 2003 11:59 AM
Subject: Re: fdasd never ends
Betsie - IPL your initrd from the Patch CD. The kernal that is loaded from
CD 1 of that distribution really cannot handle 3390-mod 9 volumes. IPL the
initrd from that patch cd and do the install of your choice. When you
have
installed all the packages but BEFORE you commit to finishing the installm
you will have to get a new kernel in place from the patch CD before you
can
IPL that system successfully.
While YAsT was running, but before you commit your changes, you should
open
another FTP session to that machine. Change directories via 'cd
/mnt//usr/bin/ftp' and start the ftp client (since its not part of the
initial ramdisk) by typing ./ftp
Then FTP to a place where you have the patch CD either mounted, or a copy
of it available and ftp the kernel off of that disk to some place like
/opt
or something. I forget the name of the package so look it up in the patch
CD tree structure. Once you've located it, bring it into your system and
run an rpm -i {kernel package name} so that your kernel is updated
properly.
That's basically wat I had to do.
|-+
| | Betsie Spann |
| | [EMAIL PROTECTED]|
| | cle.com |
| | Sent by: Linux on|
| | 390 Port |
| | [EMAIL PROTECTED]|
| | IST.EDU |
| ||
| ||
| | 03/28/2003 01:51 |
| | PM |
| | Please respond to|
| | Linux on 390 Port|
| ||
|-+
---
---|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: fdasd never ends
|
---
---|
Hi,
SuSE SLES7, 2.4.7-SuSE-SMP
Ran dasdfmt on a 3390-9 but fdasd never seems to finish.
I ran fdasd /dev/dasdc, picked option 'n' for native linux, checked it
with the print option and then hit 'w' to write the VTOC.
messages:
writing VTOC...
rereading partition table ...
6 dasdc:VOL1/ 0X0202: dasdc
and then sits there for ever. I have only the main console and can't
telnet in to run TOP.
Any suggestions? Anyone else have problems with fdasd and model 9's with
this level of Linux/390?
Betsie
Re: fdasd never ends
Jim.
Since I have a 2.4.7 system up, can I just ftp the k_deflt.rpm from the
patch cd and install it?
Betsie Spann
VM Systems Programmer
- Original Message -
From: James Melin [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, March 28, 2003 1:25 PM
Subject: Re: fdasd never ends
Betsie - This is what I get
Linux rockhopper 2.4.7-SuSE-SMP #1 SMP Mon Dec 17 11:23:56 GMT 2001 s390
unknown
Have a great weekend!
|-+
| | Betsie Spann |
| | [EMAIL PROTECTED]|
| | cle.com |
| | Sent by: Linux on|
| | 390 Port |
| | [EMAIL PROTECTED]|
| | IST.EDU |
| ||
| ||
| | 03/28/2003 03:24 |
| | PM |
| | Please respond to|
| | Linux on 390 Port|
| ||
|-+
---
---|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: fdasd never ends
|
---
---|
James,
What is the output to uname -a?
My current is 2.4.7-SuSE-SMP #1 Tue Oct 30 22:39:07 GMT 2001 s390
Betsie
- Original Message -
From: James Melin [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, March 28, 2003 11:59 AM
Subject: Re: fdasd never ends
Betsie - IPL your initrd from the Patch CD. The kernal that is loaded
from
CD 1 of that distribution really cannot handle 3390-mod 9 volumes. IPL
the
initrd from that patch cd and do the install of your choice. When you
have
installed all the packages but BEFORE you commit to finishing the
installm
you will have to get a new kernel in place from the patch CD before you
can
IPL that system successfully.
While YAsT was running, but before you commit your changes, you should
open
another FTP session to that machine. Change directories via 'cd
/mnt//usr/bin/ftp' and start the ftp client (since its not part of the
initial ramdisk) by typing ./ftp
Then FTP to a place where you have the patch CD either mounted, or a
copy
of it available and ftp the kernel off of that disk to some place like
/opt
or something. I forget the name of the package so look it up in the
patch
CD tree structure. Once you've located it, bring it into your system and
run an rpm -i {kernel package name} so that your kernel is updated
properly.
That's basically wat I had to do.
|-+
| | Betsie Spann |
| | [EMAIL PROTECTED]|
| | cle.com |
| | Sent by: Linux on|
| | 390 Port |
| | [EMAIL PROTECTED]|
| | IST.EDU |
| ||
| ||
| | 03/28/2003 01:51 |
| | PM |
| | Please respond to|
| | Linux on 390 Port|
| ||
|-+
--
-
---|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: fdasd never ends
|
--
-
---|
Hi,
SuSE SLES7, 2.4.7-SuSE-SMP
Ran dasdfmt on a 3390-9 but fdasd never seems to finish.
I ran fdasd /dev/dasdc, picked option 'n' for native linux, checked it
with the print option and then hit 'w' to write the VTOC.
messages:
writing VTOC...
rereading partition table ...
6 dasdc:VOL1/ 0X0202: dasdc
and then sits there for ever. I have only the main console and can't
telnet in to run TOP.
Any suggestions? Anyone else have problems with fdasd and model 9's
with
this level of Linux/390?
Betsie
Re: QDIO for virtual NIC
Alex, I moved the file LICENSE from redhat-oco directory to /lib and was able to load the modules. Betsie Spann VM Systems Programmer - Original Message - From: Alex Leyva [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, March 12, 2003 11:05 AM Subject: Re: QDIO for virtual NIC i've tried it, lots of time, but it returns: # depmod -a depmod: *** Unresolved symbols in /lib/modules/2.4.19/kernel/drivers/s390/qeth.o qeth.o is really qeth-2.4.19-s390-1-may2002.o i think that something is broken.but i dont know what thanks On Wed, 12 Mar 2003, Post, Mark K wrote: Alejandro, Try doing a depmod -a command. That should fix things for you. Mark Post -Original Message- From: Alex Leyva [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 12, 2003 12:07 PM To: [EMAIL PROTECTED] Subject: Re: QDIO for virtual NIC i know where is the problem... in modules.dep: /lib/modules/2.4.19/kernel/drivers/s390/qdio.o: /lib/modules/2.4.19/kernel/drivers/s390/qeth.o: /lib/modules/2.4.19/kernel/net/ipv6/ipv6.o if i do a modprobe qeth it complain about unresolved symbols, but it is because it doesnt have qdio.o in modules.dep but depmod complains too about unresolved symbols, so the question is: what can i do to have qdio.o permanently like dependency in qeth.o? so i have something like this: /lib/modules/2.4.19/kernel/drivers/s390/qdio.o: /lib/modules/2.4.19/kernel/drivers/s390/qeth.o: /lib/modules/2.4.19/kernel/net/ipv6/ipv6.o \ /lib/modules/2.4.19/kernel/drivers/s390/qdio.o thanks On Wed, 12 Mar 2003, Vic Cross wrote: On 12.03.2003 at 10:54:26, Alex Leyva [EMAIL PROTECTED] wrote: I've used the qeth.o module that Adam send to me, and activated the ipv6, and now its working, but i have to load the qdio module, then ipv6, and then qeth.o Great that it's working! Check that the following line is added to /etc/modules.conf: alias eth0 qeth Once this is added, when you issue ifup eth0 the correct chain of modules will be loaded automatically. Cheers, Vic Cross -- Alejandro Leyva Rabinovich. Jefe de la Unidad Departamental de Soporte Ticnico (Administracisn de Mainframe). Direccisn General de Informatica. Secretarma de Finanzas. Gobierno del Distrito Federal. -- Alejandro Leyva Rabinovich. Jefe de la Unidad Departamental de Soporte Ticnico (Administracisn de Mainframe). Direccisn General de Informatica. Secretarma de Finanzas. Gobierno del Distrito Federal.
Re: SLES8 iinstall - base disk size question
Silly me, I'm trying to use the manual that came with the CDs. It says to format one or multiple DASDS. to the system. Would the install guide be on the CD, on the SuSE site, on an IBM site? I'm still learning... Betsie Spann VM Systems Programmer - Original Message - From: Ken Dreger [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, February 03, 2003 5:43 PM Subject: Re: SLES8 iinstall - base disk size question Yep, you will need to divide up /usr.. the install guide shows: /usr 3000, /usr/bin 200, /usr/lib 950, /usr/share 1500, /usr/X11R6 170 and /var 130 but above that layout in the RELEASE-NOTES is a section that states you will need to divide up the /usr area. good luck, and let us know how you made out. Ken Dreger Kenneth G. Dreger Director of Information Services and Technology californiaprivateinvestigators.org L.A.Privateeye.com High Tech investigator Consultant in OS390, z/OS Systems, Linux 390 systems, Web page consulting, High Tech Investigations Home pages: http://ken.dreger.com Our Santa site: www.acornartists.com The PI site: www.laprivateeye.com The CAPI site: http://californiaprivateinvestigators.org My RedHat system for Linux (s390) downloads http://kendreger.homeftp.net Contracting services available at reasonable rates Contact: [EMAIL PROTECTED]
SLES8 iinstall - base disk size question
Hi All, I'm installing SuSE SLES8. Doc says default installation for 64-bit is 1.6 GB. I have a 3000 cyl minidisk which doesn't seem to be enough. Anyone else know what minidisk size works? Betsie
modprobe: can't find module binfmt-4c46
Hi, Anyone have any suggestions for researching this problem? Betsie
Re: Recommended chunk size with 3390's on s/390 (was RE: mkraid failure)
I code chunk-size 4 which I assume is 4096. Betsie Spann VM Systems Programmer - Original Message - From: Daniel Jarboe [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, December 10, 2002 6:35 AM Subject: Recommended chunk size with 3390's on s/390 (was RE: mkraid failure) For a related question, man raidtab indicates that typical values are anything from 4k to 128k, the best value should be determined by experimenting on a given array, alot depends on the SCSI and disk configura-tion. Should there really be much experimentation required for 3390 volumes on s/390? Is there a, it should probably be this value? I've been using chunk-size 4096. ~ Daniel Per Jessen wrote: On Tue, 10 Dec 2002 11:44:18 +, Ashley Chaloner wrote: I think the chunk-size shouldn't have the 'k' at the end. Well, mine doesn't, and it works... I second that - no 'k' on chunk-size. I didn't bother testing if it failed with a 'k' :-) regards, Per Jessen, Zurich http://www.enidan.com - home of the J1 serial console. --- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you.
Asking for RH technical reference
Hi, Looking for a reference book to teach myself about RH. The type of questions I have are Why can't I login as root? Why can't I issue commands with rexecd? Betsie
Re: zipl question
Mark, You were giving me the answer all the time. I was so sure I was IPLing from the correct device. I had an IPLable image on two disks and didn't realize I was booting from the wrong one. Thanks, Betsie Spann VM Systems Programmer - Original Message - From: Post, Mark K [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, November 11, 2002 4:39 PM Subject: Re: zipl question Betsie, Sorry I haven't gotten back to you on this sooner. I'm assuming you're IPLing from device number 200? If not, then which unit? If so, then what does Linux show you for the parmline contents? Mark Post -Original Message- From: Betsie Spann [mailto:betsie.spann;oracle.com] Sent: Monday, November 04, 2002 11:25 AM To: [EMAIL PROTECTED] Subject: Re: zipl question Mark, I have a 200, 201, 203, 204. 200 is /, 201 is swap, 203 is /usr and 204 is /home. df Filesystem 1k-blocks Used Available Use% Mounted on /dev/dasda1 348608 65644264972 20% / /dev/dasde11417240884300460948 66% /usr /dev/dasdd1 69640 132 65916 1% /home [root@vmlinuxg2 root]# cat /proc/dasd/devices cat /proc/dasd/devices 0200(ECKD) at ( 94: 0) is dasda : active at blocksize: 4096, 9 blocks, 351 MB 0201(FBA ) at ( 94: 4) is dasdb : active at blocksize: 512, 20480 blocks, 10 MB 0202(none) at ( 94: 8) is dasdc : unknown 0203(ECKD) at ( 94: 12) is dasdd : active at blocksize: 4096, 18000 blocks, 70 MB 0204(ECKD) at ( 94: 16) is dasde : active at blocksize: 4096, 36 blocks , 1406 MB [root@vmlinuxg2 root]# cat /etc/zipl.conf [defaultboot] default=linux [linux] target=/boot/ image=/boot/vmlinuz-2.4.9-37 parameters=root=/dev/dasda1 dasd=200-204,300-302,400-405 [root@vmlinuxg2 root]# CP Q V DA DASD 0190 3390 430RES R/O107 CYL ON DASD 3662 SUBCHANNEL = 0006 DASD 0191 3390 VM365E R/O 1 CYL ON DASD 365E SUBCHANNEL = 0007 DASD 019D 3390 430RES R/O102 CYL ON DASD 3662 SUBCHANNEL = 0005 DASD 019E 3390 430RES R/O175 CYL ON DASD 3662 SUBCHANNEL = 0004 DASD 0200 3390 LX1026 R/W500 CYL ON DASD 1026 SUBCHANNEL = 0008 DASD 0201 9336 (VDSK) R/W 20480 BLK ON DASD VDSK SUBCHANNEL = 0018 DASD 0203 3390 LX1206 R/W100 CYL ON DASD 1206 SUBCHANNEL = 0009 DASD 0204 3390 LX1206 R/W 2000 CYL ON DASD 1206 SUBCHANNEL = 000A DASD 0300 3390 LX100B R/W 1000 CYL ON DASD 100B SUBCHANNEL = 000B DASD 0301 3390 LX1110 R/W 1000 CYL ON DASD 1110 SUBCHANNEL = 000C DASD 0302 3390 LX112F R/W 1000 CYL ON DASD 112F SUBCHANNEL = 000D DASD 0400 3390 LX100B R/W 1000 CYL ON DASD 100B SUBCHANNEL = 000E DASD 0401 3390 LX1110 R/W 1000 CYL ON DASD 1110 SUBCHANNEL = 000F DASD 0402 3390 LX112F R/W 1000 CYL ON DASD 112F SUBCHANNEL = 0010 DASD 0403 3390 LX120A R/W 1000 CYL ON DASD 120A SUBCHANNEL = 0011 DASD 0404 3390 LX120A R/W 1000 CYL ON DASD 120A SUBCHANNEL = 0012 DASD 0405 3390 LX120A R/W 1000 CYL ON DASD 120A SUBCHANNEL = 0013 DASD 0592 3390 430W01 R/O 67 CYL ON DASD 3663 SUBCHANNEL = 0014 Thanks for any insight you may have on this. Betsie Spann VM Systems Programmer - Original Message - From: Post, Mark K [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, November 01, 2002 5:40 PM Subject: Re: zipl question Betsie, That was just a test to make sure zipl wasn't picking up parameters from somewhere else. It apparently is not, so you can rename it back. I guess I'd still like to know... are you sure you are booting from the same DASD volume as /boot is on? What does a df command show, as well as cat /proc/dasd/devices and what is in your /etc/zipl.conf? Mark Post -Original Message- From: Betsie Spann [mailto:betsie.spann;oracle.com] Sent: Friday, November 01, 2002 6:18 PM To: [EMAIL PROTECTED] Subject: Re: zipl question Mark, I renamed /etc/zipl.conf and got an error message telling me that it could not access configuration file /etc/zipl.conf and that a target directory was not specified on the command line or in a config file. I added 'noinitrd' to the parm file but it made no difference. Does this have anything to do with the s390-tools or s390-utils? Betsie Spann VM Systems Programmer - Original Message - From: Post, Mark K [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, November 01, 2002 1:22 PM Subject: Re: zipl question Betsie, Try renaming /etc/zipl.conf to something else and see what happens when you run the command. Also, are you booting from the same DASD volume as /boot is on? Mark Post -Original Message- From: Betsie Spann [mailto:betsie.spann;oracle.com] Sent: Friday, November 01, 2002 3:56 PM To: [EMAIL PROTECTED] Subject: Re: zipl question 'strace
zipl question
Hi, On SuSE, I force a new zipl parm by /sbin/zipl -c /etc/zipl.conf what is the equivalent in RedHat? The above command doesn't seem to use the /etc/zipl.conf file. Where does the boot process get the kernel command line in RH? Betsie
Re: zipl question
'strace zipl.conf' gave me strace: zipl.conf: command not found when I did, strace /sbin/zipl, I got a display similar to yours. It pointed to /etc/zipl.conf and /boot/parmfile. Both had the same dasd= string but neither matched the dasd used in the Kernel command line shown at boot time or from dmesg. Betsie Spann VM Systems Programmer - Original Message - From: Post, Mark K [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, November 01, 2002 12:48 PM Subject: Re: zipl question Not at all. It shows me what files are accessed, etc., etc. Works great for the intended purpose. Mark Post -Original Message- From: John Summerfield [mailto:summer;computerdatasafe.com.au] Sent: Friday, November 01, 2002 3:39 PM To: [EMAIL PROTECTED] Subject: Re: zipl question On Fri, 1 Nov 2002, Post, Mark K wrote: Betsie, When I do an strace zipl.conf on my Red Hat 7.2 system, it reads /etc/zipl.conf: I've used strace quite a bit, but I never thought tu use it just like that! I'm sure you mean something else. -- Cheers John. Please, no off-list mail. You will fall foul of my spam treatment. Join the Linux Support by Small Businesses list at http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
Re: zipl question
Mark, I renamed /etc/zipl.conf and got an error message telling me that it could not access configuration file /etc/zipl.conf and that a target directory was not specified on the command line or in a config file. I added 'noinitrd' to the parm file but it made no difference. Does this have anything to do with the s390-tools or s390-utils? Betsie Spann VM Systems Programmer - Original Message - From: Post, Mark K [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, November 01, 2002 1:22 PM Subject: Re: zipl question Betsie, Try renaming /etc/zipl.conf to something else and see what happens when you run the command. Also, are you booting from the same DASD volume as /boot is on? Mark Post -Original Message- From: Betsie Spann [mailto:betsie.spann;oracle.com] Sent: Friday, November 01, 2002 3:56 PM To: [EMAIL PROTECTED] Subject: Re: zipl question 'strace zipl.conf' gave me strace: zipl.conf: command not found when I did, strace /sbin/zipl, I got a display similar to yours. It pointed to /etc/zipl.conf and /boot/parmfile. Both had the same dasd= string but neither matched the dasd used in the Kernel command line shown at boot time or from dmesg. Betsie Spann VM Systems Programmer - Original Message - From: Post, Mark K [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, November 01, 2002 12:48 PM Subject: Re: zipl question Not at all. It shows me what files are accessed, etc., etc. Works great for the intended purpose. Mark Post -Original Message- From: John Summerfield [mailto:summer;computerdatasafe.com.au] Sent: Friday, November 01, 2002 3:39 PM To: [EMAIL PROTECTED] Subject: Re: zipl question On Fri, 1 Nov 2002, Post, Mark K wrote: Betsie, When I do an strace zipl.conf on my Red Hat 7.2 system, it reads /etc/zipl.conf: I've used strace quite a bit, but I never thought tu use it just like that! I'm sure you mean something else. -- Cheers John. Please, no off-list mail. You will fall foul of my spam treatment. Join the Linux Support by Small Businesses list at http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
Re: How do I reconfigure my ETH0 LCS device to a new device address i n Command Line Mode?
Donna, I update my SuSE guests from a 3270 console, using the ed editor. Files are /etc/chandev.conf /etc/modules.con - add alias for eth0 to point to new dasd driver, eg. alias eth0 qeth /etc/route.conf /etc/rc.config- run /sbin/SuSEconfig after changing run ifconfig or reboot Betsie Spann VM Systems Programmer - Original Message - From: Donna Awald [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, October 30, 2002 11:55 AM Subject: How do I reconfigure my ETH0 LCS device to a new device address i n Command Line Mode? I am trying to clone my SLE system running in LPAR mode to another LPAR. My lan addresses are different as well as the IP address. I am able to do a DFDSS backup of the volumes, restore them to new addresses, IPL from the CDROM, update PARMFILE, ZIPL, and IPL successfully on the new DASD and LPAR. But I can not configure the network. I am looking for something like the NETSETUP command on the boot CDROM. Because I am using a MP3000, and the system messages area as my console, I can only use command line commands. Does anyone know of a way to re-configure this thru command line? Or even booting from CDROM and chroot over to the system? It looks like IFCONFIG will help with switching the IP address, but I need to change the definition of ETH0 to use a new address and port number. Thanks, Donna Awald Director of Systems Architecture Empagio Creating Harmony in Human Resources [EMAIL PROTECTED] http://www.empagio.com (678) 931-3016 (office) (678) 931-3001 (Fax)
Re: RH network problem
Mark Perry gave me the info I needed to see the problem. I was relying on the messages displayed during the IPL. Running dmesg showed additional messages. The host IP was still in my TCP/IP server's config file, and it was up, running as a gateway. Took down TCP/IP and corrected the config file. My Linux guest is now up on the network. Thanks for all the advice. I'll be back Betsie Spann VM Systems Programmer - Original Message - From: Post, Mark K [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, October 26, 2002 5:03 PM Subject: Re: RH network problem In addition to Mark Perry's questions, the output from route and/or route -n would be helpful. Mark Post -Original Message- From: Betsie Spann [mailto:betsie.spann;oracle.com] Sent: Friday, October 25, 2002 3:37 PM To: [EMAIL PROTECTED] Subject: RH network problem Hi, IBM 2064, z/VM 4.3, linux guest, RH 7.1, kernel 2.4.9-37 on a s390x Can ping myself, cannot ping router OSA card, 4842-4844 attached as 480-482. Card is working for several other guests /etc/chandev add_parms,0x10,0x480,0x482,portname:OSD4800 (verified portname) qeth0,0x480,0x481,0x482(read is 4842, write is 4843, data is 4844) /etc/sysconfig/network NETWORKING=yes HOSTNAME=vmlinux1.us.oracle.com NLSDOMAIN=us.oracle.com GATEWAY=139.185.115.1 /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 BOOTPROTO=static IPADDR=139.185.115.87 NETMASK=255.255.255.0 GATEWAY=139.185.115.1 ONBOOT=yes /etc/hosts 127.0.0.1 localhost.localdomain localhost 139.185.115.87 vmlinux1.us.oracle.com /etc/modules.confincludes alias eth0 qeth lsmod shows qeth and qdio are loaded ifconfig eth0 inet addr:139.185.115.87 Mask:255.255.255.0 UP RUNNING MULTICAST MUT:1492 Metric:1 collisions:0 txqueuelen:100 Interrupt:12 Any suggestions? Betsie
RH network problem
Hi, IBM 2064, z/VM 4.3, linux guest, RH 7.1, kernel 2.4.9-37 on a s390x Can ping myself, cannot ping router OSA card, 4842-4844 attached as 480-482. Card is working for several other guests /etc/chandev add_parms,0x10,0x480,0x482,portname:OSD4800 (verified portname) qeth0,0x480,0x481,0x482(read is 4842, write is 4843, data is 4844) /etc/sysconfig/network NETWORKING=yes HOSTNAME=vmlinux1.us.oracle.com NLSDOMAIN=us.oracle.com GATEWAY=139.185.115.1 /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 BOOTPROTO=static IPADDR=139.185.115.87 NETMASK=255.255.255.0 GATEWAY=139.185.115.1 ONBOOT=yes /etc/hosts 127.0.0.1 localhost.localdomain localhost 139.185.115.87 vmlinux1.us.oracle.com /etc/modules.confincludes alias eth0 qeth lsmod shows qeth and qdio are loaded ifconfig eth0 inet addr:139.185.115.87 Mask:255.255.255.0 UP RUNNING MULTICAST MUT:1492 Metric:1 collisions:0 txqueuelen:100 Interrupt:12 Any suggestions? Betsie
Re: Logical Volumes
As root, issue pvscan to see physcial volumes and what groups they are in vgscan shows active volume groups lvscan shows active logical volumes Betsie Spann VM Systems Programmer - Original Message - From: Robert J Brenneman [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, October 24, 2002 12:35 PM Subject: Re: Logical Volumes vgdisplay -v vgname Jay Brenneman Wolfe, Gordon W gordon.w.wolfe@bTo: [EMAIL PROTECTED] oeing.com cc: Sent by: Linux onSubject: Logical Volumes 390 Port [EMAIL PROTECTED] IST.EDU 10/24/2002 03:25 PM Please respond to Linux on 390 Port Is there a quick command in Linux to display all physical volumes that are in a volume group? I can do a pvdisplay /dev/dasdc1 and it will tell me what volume group dasdc1 is in, but aside from doing that command for all volumes (or going through the menus in yast), can I tell what volumes are in a volume group? If Paradise Lost had been written by a system administrator, it would have had the sequel 'Paradise Restored from Backup'. Gordon Wolfe, Ph. D. (425)865-5940 VM Technical Services, The Boeing Company
RH network changes
Hi All, Anyone know the difference between these files? /etc/sysconfig/network-scripts/ifcfg-eth0 and /etc/sysconfig/networking/devices/ifcfg-eth0 The second file and the directory 'networking' doesn't exist on my RH Seawolf. 7.1, 64bit but does on Enigma, RH 7.2, 31bit. I'm trying to change the network on the 31bit server from a ctc to an OSA card in qdio mode. I've updated /etc/sysconfig/network created /etc/sysconfig/network-scripts/ifcfg-eth0 with DEVICE=eth0 and copied it to /etc/sysconfig/networking/devices updated /etc/chandev.conf updated /etc/modules.conf for the 'alias eth0 qeth' When the system comes up and the message 'Setting network parameters:' displays, I see the 'Bringing up interface lo' and 'ctc0' messages but no 'eth0' message. Should the DEVICE parameter in ifcfg-eth0 be set to 'qeth' or 'qeth0'? Also, 3270 console support is better on the 64bit version; 'ls' actually works. Can anyone recommend a Linux manual that covers this basic network file layout?
RH network changes
Hi, I'm trying to change my network settings on a RH 7.1 system from the 3270 console. On SuSE, I update /etc/route.conf, /etc/rc.config, /etc/chandev.conf, /etc/modules.conf (if necessary), run /sbin/SuSEconfig, ifconfig and reboot. I suspect the RH files are in /etc/sysconfig. TELNET,RLOGIN is not an option. Any one know the files needed? Betsie Spann
