Re: Question re: Linux SLES9
It is doubtful anyone here would have run the "ifconfig down" command. But thanks for the information. What is more likely is that I am not looking in the proper place for the log I need to track down the problem. Assuming that I did not change the default where, besides /var/log, would I look for messages that may point to a problem? -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Post, Mark K Sent: Saturday, November 12, 2005 3:33 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Question re: Linux SLES9 If someone did an "ifconfig down" on the interface, and then brought it back up, all the route information would have been lost. This normally doesn't generate any logging. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, November 11, 2005 6:01 PM To: LINUX-390@VM.MARIST.EDU Subject: Question re: Linux SLES9 I have a problem with network communication. SLES9 for S/390 (64-bit) in an LPAR > (no VM) using a shared IFL I have one other LPAR running SLES9 64-bit I ran uname -a which shows: Linux techlnux 2.6.5-7.201-s390x #1 SMP Thu Aug 25 06:20:45 UTC 2005 s390x s390x s390x GNU/Linux I ran netstat -rn and it returned nothing only the column headings. I tried to ping the IP address of my system and it responded. I also successfully pinged the gateway IP 10.128.24.1. But I could not ping 10.128.26.1 or any other address. I ran "route add default gw 10.128.24.1" which re-established connectivity with the outside world. Just like I never lost communications. I searched the log files looking for a message but I didn't see anything. Does anyone have a suggestion where I might find a message showing why connectivity was suddenly dropped? -- 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: Question re: Linux SLES9
If someone did an "ifconfig down" on the interface, and then brought it back up, all the route information would have been lost. This normally doesn't generate any logging. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, November 11, 2005 6:01 PM To: LINUX-390@VM.MARIST.EDU Subject: Question re: Linux SLES9 I have a problem with network communication. SLES9 for S/390 (64-bit) in an LPAR > (no VM) using a shared IFL I have one other LPAR running SLES9 64-bit I ran uname -a which shows: Linux techlnux 2.6.5-7.201-s390x #1 SMP Thu Aug 25 06:20:45 UTC 2005 s390x s390x s390x GNU/Linux I ran netstat -rn and it returned nothing only the column headings. I tried to ping the IP address of my system and it responded. I also successfully pinged the gateway IP 10.128.24.1. But I could not ping 10.128.26.1 or any other address. I ran "route add default gw 10.128.24.1" which re-established connectivity with the outside world. Just like I never lost communications. I searched the log files looking for a message but I didn't see anything. Does anyone have a suggestion where I might find a message showing why connectivity was suddenly dropped? -- 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: Question re: Linux SLES9
On Wed, 29 Dec 2004 14:09:54 -0800, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I have looked and I have not seen any documentation that shows how to add a > dasd unit via command line under SLES9. With devfs you enable and disable devices by writing into pseudo variables under the /sys directory. Like this: rmhtest3:/sys/devices/css0/0.0.000b/0.0.019e # echo 1 > online Rob -- Rob van der Heij rvdheij @ gmail.com -- 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: Question re: Linux SLES9
Is there another way besides using the yast interface? -Original Message- From: Ranga Nathan [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 29, 2004 2:24 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Question re: Linux SLES9 If the dasd address was genned for the LPAR, then it should be visible in "yast" under system (or hardware) --> DASD. You can then activate it, format and mount. __ Ranga Nathan / CSG Systems Programmer - Specialist; Technical Services; BAX Global Inc. Irvine-California Tel: 714-442-7591 Fax: 714-442-2840 [EMAIL PROTECTED] Sent by: Linux on 390 Port 12/29/2004 02:09 PM Please respond to Linux on 390 Port To: LINUX-390@VM.MARIST.EDU cc: Subject:Question re: Linux SLES9 SLES9 for S/390 (64-bit) in an LPAR > (no VM) using a shared IFL (I have one other LPAR running SLES9 31-bit) I have looked and I have not seen any documentation that shows how to add a dasd unit via command line under SLES9. Under SLES8 I used to execute echo "add device range=" >> /proc/dasd/devices And then I would execute the following to view the changes: cat /proc/dasd/devices But that does not seem to work any more. -- 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: Question re: Linux SLES9
If the dasd address was genned for the LPAR, then it should be visible in "yast" under system (or hardware) --> DASD. You can then activate it, format and mount. __ Ranga Nathan / CSG Systems Programmer - Specialist; Technical Services; BAX Global Inc. Irvine-California Tel: 714-442-7591 Fax: 714-442-2840 [EMAIL PROTECTED] Sent by: Linux on 390 Port 12/29/2004 02:09 PM Please respond to Linux on 390 Port To: LINUX-390@VM.MARIST.EDU cc: Subject:Question re: Linux SLES9 SLES9 for S/390 (64-bit) in an LPAR > (no VM) using a shared IFL (I have one other LPAR running SLES9 31-bit) I have looked and I have not seen any documentation that shows how to add a dasd unit via command line under SLES9. Under SLES8 I used to execute echo "add device range=" >> /proc/dasd/devices And then I would execute the following to view the changes: cat /proc/dasd/devices But that does not seem to work any more. -- 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: Question re: Linux SLES9
> will Linux automatically detect the tape drive and load the necessary > drivers? Not on most distributions. It'll probably identify the subchannel and device, but it won't have the device drivers. > What steps do I need to take to access the tape drives for products like > Amanda, or Bacula, etc.? Load and configure the tape drivers. Configure your application to use the devices resulting from the previous step. Note that you do not have the ability (unless you have the for-pay UTS Global tape drivers) to actually manipulate the library automation -- you'll have to work with that. > We also have a VTS and an ATL that is being shared by the three LPARs and > various UNIX and Windows servers. Would it be a better use of my time to > use the "VTS" or the "ATL" instead of the stand alone 3490 tape drives? See note above. Library manager access is currently a real problem for Linux. If you have standalone drives, you'll have more success getting those to work with the backup utilities than you'll have with the sophisticated libraries. Another option is to use emulated tape on the Linux systems and let the systems that know how to work the libraries keep control of them. Download my presentation on that and look at using Bacula with "file" devices. Much simpler, and the tapes end up being compatible with your existing TMS environment. -- 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: Question re: Linux SLES9
Hi Doug. The device configuration of Linux 2.6.x. is all-new, don't try to use any 2.4.x related methods from documentation or such ;). Linux will automagically detect your tapes when you attach them (at runtime or at boot - does'nt matter). The device driver will automagically be loaded. You can verify/enforce that: - check if driver is loaded: look for tape390 in the output of the tool "lsmod" - load driver: "modprobe tape390" Your tape drives will not be accessible by default. Unlike on other platforms, on the mainframe Linux does not "grab" all hardware it sees. You can see your devices in the sysfs tree aleady: - change working dir to the ccw bus: "cd /sys/bus/ccw" - look for your tapes using "ls" If you cannot find your tapes now, Linux did not detect them. Do not get irretated by the format presented there, "0.0.1234" corresponds with channel subsystem #0, subchannel set #0, device number 1234hex. You check if a device that has been detected is enabled: "cat 0.0.1234/online". An output "0" indicates that the device is not enabled, "1" indicates the device is usable. You can change that value by typing echo "1" >0.0.1234/online And using cat as above, you can check if that was successfull. This way of configuration works for everything that has a single device number (dasd, tape, ctc etc.) but not for those devices with multiple device numbers like qdio osa ethernet and such. with kind regards Carsten Otte -- omnis enim res, quae dando non deficit, dum habetur et non datur, nondum habetur, quomodo habenda est -- 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
