HA / DB2
Hello again listeners, I need set up ours db2 servers on cluster... what kind of solution are used on z/linux ? anybody can share a how to or redbook or any paper about this? Thanks ! Rogério Soares -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
2011-01-27 Linux on System z kernel 2.6.37 related updates on developerWorks
Please refer to http://www.ibm.com/developerworks/linux/linux390/whatsnew.html for several updates to the 'Development stream': * description of upstream kernel 2.6.37 features that were contributed by Linux on System z development * kernel 2.6.37 patch for kernel message catalog * s390-tools 1.12.0 delivers new functionality and bugfixes * updated documentation -- Device Drivers, Features, and Commands -- How to use FC-attached SCSI devices with Linux on System z -- Kernel Messages as well as updated Restrictions and Technical Details * end of message Mit freundlichen Grüßen / Kind regards Gerhard Hiller Systems Software Management IBM Systems Technology Group, Systems Software Development Phone: +49-7031-16-4388 IBM Deutschland Fax: +49-7031-16-3545 Schoenaicher Str. 220 E-Mail: ghil...@de.ibm.com 71032 Boeblingen Germany IBM Deutschland Research Development GmbH / Vorsitzender des Aufsichtsrats: Martin Jetter Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 image/gifimage/gifimage/gifimage/gifimage/gifimage/gifimage/gif
CMS SSH, SFTP, and SCP support available Feb 1
We're pleased to announce SSH, SCP and SFTP support for CMS systems. Please see http://www.sinenomine.net/SSHUtilities for details. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
LVM, PAVs, and cloning
My turn to ask a question :-) I have a bunch of Model 54 disk volumes that contain not-quite-fullpack n-minus-1-cyl minidisks. Some have 8 static PAVs, some have only 2. 1. I want to exploit virtual PAVs (MINIOPT/DEFINE PAVALIAS), as a lot of I/O will be done to these volumes (multiple of them per guest). 2. I want to set up LVM to use those PAVs. 3. I want to be able to clone or recover the LVM to other volumes 4. I want LVM to be insensitive to the number of PAVs, it being just a performance improvement mechanism 5. These are not-quite-fullpack n-minus-1-cyl minidisks Are there issues that will inhibit me from reaching my goal? Regards, Alan z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 alan_altm...@us.ibm.com -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: LVM, PAVs, and cloning
On 1/31/2011 at 04:07 PM, Alan Altmark alan_altm...@us.ibm.com wrote: My turn to ask a question :-) I have a bunch of Model 54 disk volumes that contain not-quite-fullpack n-minus-1-cyl minidisks. Some have 8 static PAVs, some have only 2. 1. I want to exploit virtual PAVs (MINIOPT/DEFINE PAVALIAS), as a lot of I/O will be done to these volumes (multiple of them per guest). I haven't actually played with PAVs, so I'm coming at this from about the same level of expertise. However, I thought PAVs were only of interest to Linux if the devices were dedicated, not minidisks. I thought PAVs for minidisks would be handled by z/VM itself. 2. I want to set up LVM to use those PAVs. 3. I want to be able to clone or recover the LVM to other volumes 4. I want LVM to be insensitive to the number of PAVs, it being just a performance improvement mechanism 5. These are not-quite-fullpack n-minus-1-cyl minidisks If I'm remembering correctly, and z/VM does do all the work with PAV for minidisks, then 3-4 should be completely transparent to Linux. Are there issues that will inhibit me from reaching my goal? For sure, if you were to use dedicated DASD, then you would need to set up multipathing for them. If z/VM doesn't do the heavy lifting for minidisks, then the same would hold true there. So, you would need to define the multiple paths to the various devices and tell LVM to use those multipathed names for the PVs, and exclude the raw device names in the LVM filters. I've never done that with ECKD or FBA volumes, so I can't be more specific about how to go about that. I believe it would mean that any clones or restores to other volumes might involve some manual intervention to get things looking just so to multipathd. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Hipersockets Not working z/Linux to z/VM z/OS
Mark, Here is what we have: The hsi0 is a real hipersocket Linux netstat [z034876@UTLZ0002 ~]$ netstat -r Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 10.90.3.0 * 255.255.255.0 U 0 0 0 hsi0 10.90.30.0 * 255.255.255.0 U 0 0 0 eth0 169.254.0.0 * 255.255.0.0 U 0 0 0 hsi0 default 10.90.30.1 0.0.0.0 UG0 0 0 eth0 Linux ifconfig [z034876@UTLZ0002 ~]$ /sbin/ifconfig eth0 Link encap:Ethernet HWaddr 02:00:01:00:00:07 inet addr:10.90.30.18 Bcast:10.90.30.255 Mask:255.255.255.0 inet6 addr: fe80::1ff:fe00:7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1 RX packets:1990904 errors:0 dropped:0 overruns:0 frame:0 TX packets:1347060 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1665137706 (1.5 GiB) TX bytes:788094246 (751.5 MiB) hsi0 Link encap:Ethernet HWaddr 06:00:FA:06:00:56 inet addr:10.90.3.100 Bcast:10.90.3.255 Mask:255.255.255.0 inet6 addr: fe80::400:faff:fe06:56/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:16384 Metric:1 RX packets:85 errors:0 dropped:0 overruns:0 frame:0 TX packets:151 errors:36 dropped:36 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:9252 (9.0 KiB) TX bytes:11956 (11.6 KiB) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:26137 errors:0 dropped:0 overruns:0 frame:0 TX packets:26137 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3600746 (3.4 MiB) TX bytes:3600746 (3.4 MiB) z/VM netstat gate Known IPv4 gateways: Subnet Address Subnet Mask FirstHopFlgs PktSz Metric Link -- --- - -- -- Default none 10.90.1.1 UG 1500 11 OSD2 Default none 10.90.1.1 UG 1500 11 OSD0 10.90.1.0 255.255.255.0directU1500 10 OSD0 10.90.1.0 255.255.255.0directU1500 10 OSD2 10.90.3.0 255.255.255.0directUS 16384 none HIPERLFA 10.90.11.0 255.255.255.010.90.1.12 UG 1500 20 OSD2 ... ... ... z/VM netstat dev Device HIPERDFAType: HIPERS Status: Ready Queue size: 0 CPU: 0 Address: FA50Port name: UNASSIGNED IPv4 Router Type: NonRouter Arp Query Support: No Link HIPERLFA Type: QDIOIP Net number: 0 Speed: 1 BytesIn: 3848BytesOut: 20456 Forwarding: Enabled MTU: 16384 IPv6: Disabled IPv4 Path MTU Discovery: Disabled Maximum Frame Size : 24576 Broadcast Capability: Yes Multicast Capability: Yes Multicast Group Members --- --- 224.0.0.1 1 z/VM netstat home netstat home VM TCP/IP Netstat Level 610 TCP/IP Server Name: TCPIP IPv4 Home address entries: Address Subnet Mask Link VSWITCH --- --- ----- 10.90.25.1 255.255.255.0VC1LVIPA none 10.90.1.14 255.255.255.0OSD2 none 10.90.1.13 255.255.255.0OSD0 none 10.90.3.60 255.255.255.0HIPERLFA none Test z/OS LPAR: = EZA0619I Running IBM MVS TCP/IP CS V1R11 TCP/IP Configuration Tester EZA0621I The FTP configuration parameter file used will be SYS1.TCPPARMS(FTPDATA) EZA0602I TCP Host Name is: ZSJES2 EZA0605I Using Name Server to Resolve ZSJES2 EZA0611I The following IP addresses correspond to TCP Host Name: ZSJES2 EZA0612I 10.90.21.1 EZA0614I The following IP addresses are the HOME IP addresses defined in PROFILE.TCPIP: EZA0615I 10.90.21.1 EZA0615I 10.90.1.19 EZA0615I 10.90.1.20 EZA0615I 10.90.21.10 EZA0615I 10.90.21.90 EZA0615I 10.90.3.20 EZA0615I 127.0.0.1 EZA0618I All IP addresses for ZSJES2 are in the HOME list! EZA0622I Hometest was successful - all Tests Passed! NETSTAT ROUTE MVS TCP/IP NETSTAT CS V1R11 TCPIP Name: TCPIP 18:41:28 DestinationGateway FlagsRefcnt Interface ------ --- - Default10.90.1.1 UGO 05 OSD0 Default10.90.1.1 UGO 00 OSD2 10.90.1.0/24 0.0.0.0
Re: Hipersockets Not working z/Linux to z/VM z/OS
On Monday, 01/31/2011 at 05:22 EST, Kyle Stewart kyle.stew...@zionsbancorp.com wrote: We have been struggling trying to get our z/VM z/OS systems to talk via hipersockets to our RHEL5.3 Linux (under z/VM 6.1). We can ping out from Linux to VM or to z/OS, but when we ping into Linux from z/VM z/OS the 'tcpdump -I hsi0 ip proto \\icmp' on the Linux only shows the request received. No reply is sent from Linux back. The z/OS, z/VM, and Linux have OSAs to reach the world. The OSA address for z/VM z/OS is what comes across the hsi0 ping. We need to bring customer requests in to the OSA - VSWITCH - Linux - hsi0 - z/OS and back through the process. We are quite perplexed. Any help would be greatly appreciated. Just looking at this again. Since you didn't see the ICMP ECHO RESPONSE go back out on the hsi0 interface, you can come to two conclusion 1. The ECHO RESPONSE went out over another interface, OR 2. The ECHO RESPONSE didn't go out at all. Remove the -I hsi0 filter and see what you see. It is also interesting to see the ORIGIN IP address in incoming the ECHO REQUEST. This may have something to do with the IP addresses z/VM and z/OS use on their outbound packets. Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 alan_altm...@us.ibm.com IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
