Re: Help with Linux - to VSE Hipersockets
Is anything else on the Hipersocket network that you can ping? Maybe try this route: DEFINE ROUTE,ID=HIPERS,LINKID=OSAA,IPADDR=192.68.24.0,- GATEWAY=192.68.24.1 You may want to post this to vse-l. CSI monitors vse-l can may respond there. Aristarc Diez Redorta wrote: Here is the ifconfig: eth0 Link encap:Ethernet HWaddr 00:11:25:C0:D6:A5 inet addr:130.10.230.101 Bcast:130.10.255.255 Mask:255.255.0.0 inet6 addr: fe80::11:2500:9c0:d6a5/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1 RX packets:55489 errors:0 dropped:0 overruns:0 frame:0 TX packets:4839 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:8928543 (8.5 Mb) TX bytes:746842 (729.3 Kb) hsi0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.68.24.1 Bcast:192.68.24.255 Mask:255.255.255.0 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:9 errors:0 dropped:0 overruns:0 frame:0 TX packets:492 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:756 (756.0 b) TX bytes:33760 (32.9 Kb) 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:22 errors:0 dropped:0 overruns:0 frame:0 TX packets:22 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1712 (1.6 Kb) TX bytes:1712 (1.6 Kb) And here is the startup of the TCP/IP (See attached file: tcpstahi.txt) Thanks in advance. Aris. -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com Catch the WAVV! http://www.wavv.org WAVV 2007 - Green Bay, WI - May 18-22, 2007 -- 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: Help with Linux - to VSE Hipersockets
Hi Rick, we cannot ping from Linux to VSE and from Vse to Linux. This is the first time we're trying to configure it. TIA. Aris. Rich Smrcina [EMAIL PROTECTED] om Para Enviado por: LINUX-390@VM.MARIST.EDU Linux on 390 Port cc [EMAIL PROTECTED] IST.EDU Asunto Re: Help with Linux - to VSE Hipersockets 20/04/2007 14:22 Por favor, responda a Linux on 390 Port [EMAIL PROTECTED] IST.EDU There is nothing special that has to be done in Linux to access VSE via Hipersockets. If you have Hipersockets configured on the system, attach the device sets to each Linux and VSE and configure the interfaces. One thing to remember on the VSE side is that when adding the device you need to use the mode operand 01. The TCP/IP doc should indicate that. Are you having a specific problem? Aristarc Diez Redorta wrote: Hi all, can anyone help me or show me how to configure Linux Hipersockets to access VSE Hipersockets? TIA. Aris. -- 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 -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com Catch the WAVV! http://www.wavv.org WAVV 2007 - Green Bay, WI - May 18-22, 2007 -- 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: Help with Linux - to VSE Hipersockets
There is nothing special that has to be done in Linux to access VSE via Hipersockets. If you have Hipersockets configured on the system, attach the device sets to each Linux and VSE and configure the interfaces. One thing to remember on the VSE side is that when adding the device you need to use the mode operand 01. The TCP/IP doc should indicate that. Are you having a specific problem? Aristarc Diez Redorta wrote: Hi all, can anyone help me or show me how to configure Linux Hipersockets to access VSE Hipersockets? TIA. Aris. -- 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 -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com Catch the WAVV! http://www.wavv.org WAVV 2007 - Green Bay, WI - May 18-22, 2007 -- 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
Help with Linux - to VSE Hipersockets
Hi all, can anyone help me or show me how to configure Linux Hipersockets to access VSE Hipersockets? TIA. Aris. -- 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: Help with Linux - to VSE Hipersockets
Here is the ifconfig: eth0 Link encap:Ethernet HWaddr 00:11:25:C0:D6:A5 inet addr:130.10.230.101 Bcast:130.10.255.255 Mask:255.255.0.0 inet6 addr: fe80::11:2500:9c0:d6a5/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1 RX packets:55489 errors:0 dropped:0 overruns:0 frame:0 TX packets:4839 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:8928543 (8.5 Mb) TX bytes:746842 (729.3 Kb) hsi0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.68.24.1 Bcast:192.68.24.255 Mask:255.255.255.0 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:9 errors:0 dropped:0 overruns:0 frame:0 TX packets:492 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:756 (756.0 b) TX bytes:33760 (32.9 Kb) 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:22 errors:0 dropped:0 overruns:0 frame:0 TX packets:22 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1712 (1.6 Kb) TX bytes:1712 (1.6 Kb) And here is the startup of the TCP/IP (See attached file: tcpstahi.txt) Thanks in advance. Aris. Rich Smrcina [EMAIL PROTECTED] om Para Enviado por: LINUX-390@VM.MARIST.EDU Linux on 390 Port cc [EMAIL PROTECTED] IST.EDU Asunto Re: Help with Linux - to VSE Hipersockets 20/04/2007 14:58 Por favor, responda a Linux on 390 Port [EMAIL PROTECTED] IST.EDU Do the interfaces come up on both Linux and VSE. Send the output from the Linux ifconfig and your VSE TCP/IP config and startup messages. Aristarc Diez Redorta wrote: Hi Rick, we cannot ping from Linux to VSE and from Vse to Linux. This is the first time we're trying to configure it. TIA. Aris. -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com Catch the WAVV! http://www.wavv.org WAVV 2007 - Green Bay, WI - May 18-22, 2007 -- 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 tcpstahi.txt Description: Binary data
Re: Help with Linux - to VSE Hipersockets
On Fri, Apr 20, 2007 at 10:36 AM, in message [EMAIL PROTECTED], Aristarc Diez Redorta [EMAIL PROTECTED] wrote: Here is the ifconfig: -snip- The very end of your TCP/IP start up log shows successful pings: 20070420 162754.71 0012: IPC108I ICMP Echo request has been received from: 192.68.24.1 20070420 162755.71 0012: IPC108I ICMP Echo request has been received from: 192.68.24.1 20070420 162756.71 0012: IPC108I ICMP Echo request has been received from: 192.68.24.1 20070420 163000.13 0012: IPC108I ICMP Echo request has been received from: 192.68.24.1 20070420 163001.13 0012: IPC108I ICMP Echo request has been received from: 192.68.24.1 20070420 163028.35 0012: IPC108I ICMP Echo request has been received from: 192.68.24.1 20070420 163029.36 0012: IPC108I ICMP Echo request has been received from: 192.68.24.1 So, is there really a problem? Mark Post -- 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: Help with Linux - to VSE Hipersockets
Do the interfaces come up on both Linux and VSE. Send the output from the Linux ifconfig and your VSE TCP/IP config and startup messages. Aristarc Diez Redorta wrote: Hi Rick, we cannot ping from Linux to VSE and from Vse to Linux. This is the first time we're trying to configure it. TIA. Aris. -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com Catch the WAVV! http://www.wavv.org WAVV 2007 - Green Bay, WI - May 18-22, 2007 -- 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: Help with Linux - to VSE Hipersockets
Clearly I didn't read far enough... :) Mark Post wrote: On Fri, Apr 20, 2007 at 10:36 AM, in message [EMAIL PROTECTED], Aristarc Diez Redorta [EMAIL PROTECTED] wrote: Here is the ifconfig: -snip- The very end of your TCP/IP start up log shows successful pings: 20070420 162754.71 0012: IPC108I ICMP Echo request has been received from: 192.68.24.1 20070420 162755.71 0012: IPC108I ICMP Echo request has been received from: 192.68.24.1 20070420 162756.71 0012: IPC108I ICMP Echo request has been received from: 192.68.24.1 20070420 163000.13 0012: IPC108I ICMP Echo request has been received from: 192.68.24.1 20070420 163001.13 0012: IPC108I ICMP Echo request has been received from: 192.68.24.1 20070420 163028.35 0012: IPC108I ICMP Echo request has been received from: 192.68.24.1 20070420 163029.36 0012: IPC108I ICMP Echo request has been received from: 192.68.24.1 So, is there really a problem? Mark Post -- 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 -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com Catch the WAVV! http://www.wavv.org WAVV 2007 - Green Bay, WI - May 18-22, 2007 -- 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: Help with Linux - to VSE Hipersockets
On Fri, Apr 20, 2007 at 11:53 AM, in message [EMAIL PROTECTED], Rich Smrcina [EMAIL PROTECTED] wrote: Clearly I didn't read far enough... :) The only reason I read as far as I did, was because I had no idea what in the world I was looking at until I got to the end. Fresh set of eyes, and all that. Mark Post -- 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
dmsetup suspend
Can somebody help me understand the practical aspects of this statement from dmsetup(8) ? suspend device_name Suspends a device. Any I/O that has already been mapped by the device but has not yet completed will be flushed. Any further I/O to that device will be postponed for as long as the device is suspended. Specifically, I am researching possible approaches to solving the problem of guaranteeing good DR backups and reliable clones of running Linux users in combination with the CP FLASHCOPY facility of our DS8100. The new AF_IUCV support will probably prove necessary in the effort, as well as the asynchronous FLASHCOPY we're promised in z/VM 5.3. The statement to the effect that I/Os which have been mapped but not completed will be flushed is of some concern, but I am unsure of the potential danger I would be exposing myself to, in any real terms. Should it be a small concern? A large concern? My intial experimentation seems to suggest it works in practice (given my small sample size), but what are the theoretical dangers? I get a better feeling from the 'freeze' capabilities of xfs, but as deploying it in preference to something which uses the 'suspend' capabilities of the device_mapper involves getting our distrubted systems people to buy off on adopting xfs as the standard filesystem for linux on zSeries, I would like to exhaust the possibilities of 'dmsetup suspend', first. This would be on SLES10; I am aware of the kernel panics people are reporting with RHEL5 on intel systems and am assuming, for now, that it is a non issue in our SuSE/zSeries environment (given I've been playing with it and haven't seen a kernel panic myself). ok r. -- 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
