Re: Upgrading SLES8 to SLES10 with Oracle 9
Depends on your bureaucracy for getting a new server into production... And how difficult the clients can be :) WAS is behaved now in versions 5. Oracle, haven't tried that one --- but I would hope it doesn't do that! DB2 is ok with it. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Thursday, November 08, 2007 9:16 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Upgrading SLES8 to SLES10 with Oracle 9 And my favorite step of all: 7) Find all the hardcoded IP addresses in client setups and fix them to point to the DNS name... 8-) Nah, skip that stuff and have the new server steal the name and IP of the old one (after you shut it down first). We do a lot of that :) Makes it harder to test thoroughly, though. You also get the unmatched thrill of finding all the places that the Oracle install utility wrote IP addresses into scripts, and in WAS configs, and in Many Other Stupid and Undocumented Places. More fun than I'm allowed to have these days. Easier to fix the clients. They'll call you and tell you where it's broken. Then you get to yell at them for hardcoding addresses. Much more attractive fun. 8-) -- db -- 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: Upgrading SLES8 to SLES10 with Oracle 9
6) Update DNS to point to the SLES 10 system. And my favorite step of all: 7) Find all the hardcoded IP addresses in client setups and fix them to point to the DNS name... 8-) Nah, skip that stuff and have the new server steal the name and IP of the old one (after you shut it down first). We do a lot of that :) Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -- 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: SLES10 SP1 Starter system
One of my guys did it - I don't think he had any issues with it. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Martha McConaghy Sent: Wednesday, November 14, 2007 6:59 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] SLES10 SP1 Starter system Has anyone on the list tried installing the SLES10 SP1 starter system? I'm trying it for the first time and its going OK except for one problem. The 151 disk image, NOV151 VMARC, won't unpack. It churned all yesterday afternoon on our z/9 and never finished. So, I moved it over to our development machine and let it churn all night, still it isn't done. Its a 2G file, so I expected it to take a long time, but this is crazy. Has anyone gotten this to work? I'm under the gun for a deadline right now, so can't afford to wait if this isn't going to work. Martha -- 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: SUSE Linux Enterprise Server 10 SP1 Starter System for IBM System z
Hey Mark and David(and others). Does this guy work for upgrading a sles9x (SP3+) server to SLES 10 SP1? Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Wednesday, October 31, 2007 8:18 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] SUSE Linux Enterprise Server 10 SP1 Starter System for IBM System z Cross-posted to IBM-MAIN, IBMVM, and 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: Stupid newbie question re: Installing SP1 to SLES10 on z/890
Mark wrote: Which ever way you go, you'll need to rummage through your system afterwards, and make sure things are still configured the way you want them. I've seen cases where stuff got changed, and I had to re-do them. Also, look for *.rmpnew files. Those will be new versions of configuration files that didn't get moved into place because you updated the ones on the running system. Also look for *.rpmsave files. I'm not sure what criteria gets used to create those, but they're copies of configuration files that were replaced, but saved. There's a nice utility provided by SuSE which lists them out for you. Use chkconfig rpmconfigcheck on. Then it will post a list of these files for you (on the console) to investigate when the server boots (or go review it in /var/adm/rpmconfigcheck later). You should do this whenever you apply any updates at all. You'll have not fun issues if say you've got pam customization and it shoves it off to .rpmsave and puts its stuff there instead :(. Marcy Cortes Team Lead, Enterprise Virtualization - z/VM and z/Linux Enterprise Hosting Services w. (415) 243-6343 c. (415) 517-0895 This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- Which ever way you go, you'll need to rummage through your system afterwards, and make sure things are still configured the way you want them. I've seen cases where stuff got changed, and I had to re-do them. Also, look for *.rmpnew files. Those will be new versions of configuration files that didn't get moved into place because you updated the ones on the running system. Also look for *.rpmsave files. I'm not sure what criteria gets used to create those, but they're copies of configuration files that were replaced, but saved. 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 -- 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 smime.p7s Description: S/MIME cryptographic signature
Re: SUSE Linux Enterprise Server 10 SP1 Starter System for IBM System z
You would think I would have ... but I didn't... having been using another vendor's product... Off to vanilla land Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Wednesday, November 28, 2007 2:20 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] SUSE Linux Enterprise Server 10 SP1 Starter System for IBM System z On Wed, Nov 28, 2007 at 4:54 PM, in message [EMAIL PROTECTED], Marcy Cortes [EMAIL PROTECTED] wrote: Hey Mark and David(and others). Does this guy work for upgrading a sles9x (SP3+) server to SLES 10 SP1? Marcy, Sure, but if you've already got a working network installation server in place, it won't really buy you anything. The whole idea was to get a site's first installation server up and running without having to scrounge up space on another box (or scrounge up a new box), get firewall rules changed, etc., and do it with native z/VM tools. Since, I imagine, you already have an install server set up, all you'll need to do is incorporate the SLES10 SP1 installation files into 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 -- 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: SUSE Linux Enterprise Server 10 SP1 Starter System for IBM System z
That's true too! More than one way to pet a cat I guess! Since I already had someone here try out the starter system, I figured I'd see what happens if I tried it that way. Ah, I feel the freeze in the air --- time to get useful stuff done without all those pesky applications folks in a panic about their own stuff :) Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Wednesday, November 28, 2007 2:55 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] SUSE Linux Enterprise Server 10 SP1 Starter System for IBM System z On Wed, Nov 28, 2007 at 5:26 PM, in message [EMAIL PROTECTED], Marcy Cortes [EMAIL PROTECTED] wrote: You would think I would have ... but I didn't... having been using another vendor's product... Off to vanilla land Ah, that's right. I remember now. Even so, if you create a stripped down SLES10 (or even SLES9) system using your current tool, and use YaST to turn itself into an installation server, you still won't need the starter system. 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 -- 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: Is 275GB of VDISK stupid?
I haven't added it all up, but we do it that way and would have to be either right around 275G if not over. One thing to look out for is the vm.swappiness setting. Seems that on SLES 9 (latest kernel) some virtual machines have a tendency to just keep writing more and more to swap and never free up those pages in vdisk until the process is stopped. We had production machines march through all their space and then java core dump :(.Used page space was also growing too quickly without it. Yes, swapoff/swapon would free up those pages (but the structures would still exist in VM). Setting kernel parameter vm.swappiness=20 seemed to prevent that. Don't ask me why... It just does :) (no time to go read the code and truly understand that)... The default is 60. PS. We use mod 3's for paging and mod 27's mostly for everything else. 9's seem kind of useless after you build a file system on them and only have like 6-something Gig left. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Rob van der Heij Sent: Monday, December 03, 2007 11:04 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Is 275GB of VDISK stupid? On Dec 3, 2007 7:54 PM, Bill Bitner [EMAIL PROTECTED] wrote: This is a good approach, but please one reminder. The DAT structures for virtual disk in storage address spaces, including PGMBKs, are not pageable (user space PGMBKs are). And prior to z/VM 5.3.0, they must reside in real memory below 2GB. So 275GB of vdisk would be more than 2GB of memory required below 2GB for the DAT structures. One would want to be on z/VM 5.3.0. The PGMBKs are not reflected in the PTRM numbers. But only when used, isn't it? As long as you have not touched them, there's no PGMBKs except for the first one. Once he actually starts using them I would think that 550 GB of paging space might approach some other limitations in CP (though with 3390-9 not the number of cpowned volumes). -Rob -- Rob van der Heij Velocity Software, Inc http://velocitysoftware.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 -- 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 smime.p7s Description: S/MIME cryptographic signature
Re: Is 275GB of VDISK stupid?
We have about 65 mod 3 for 112 servers (at the moment). About 1/2 of them are fat WAS virtual machines. Once we hit 50% utilization, we add more ... Think of it this way... Would you rather have dedicated swap (real) disks to each virtual machine that may or may not be used or would you rather pool them all together and have VM's very robust block paging system manage full volumes and balance across all of them. Easier to monitor.. Your i/o load is spread... There's even multilevel storage of those pages (memory, xstor, disk). Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of James Melin Sent: Tuesday, December 04, 2007 6:20 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Is 275GB of VDISK stupid? So Marcy, if you have 275GB of VDISK defined, what do you define for total page space for your VM? Just curious. I am almost always in disagreement with our VM guy on our configuration, but I'm getting ready to revisit VDISK swap because we're on a new machine with more memory. The more information I have on 'real companies' and their configurations the less intractable he seems to be. -J Marcy Cortes [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc 12/03/2007 07:30 PM Subject Re: Is 275GB of VDISK stupid? Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU I haven't added it all up, but we do it that way and would have to be either right around 275G if not over. One thing to look out for is the vm.swappiness setting. Seems that on SLES 9 (latest kernel) some virtual machines have a tendency to just keep writing more and more to swap and never free up those pages in vdisk until the process is stopped. We had production machines march through all their space and then java core dump :(.Used page space was also growing too quickly without it. Yes, swapoff/swapon would free up those pages (but the structures would still exist in VM). Setting kernel parameter vm.swappiness=20 seemed to prevent that. Don't ask me why... It just does :) (no time to go read the code and truly understand that)... The default is 60. PS. We use mod 3's for paging and mod 27's mostly for everything else. 9's seem kind of useless after you build a file system on them and only have like 6-something Gig left. Marcy Cortes -- 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: Extracting user IDs and IP addresses from QUERY VSWITCH DETAILS
It would be nice to be able to say something like
Q vswitch details for USERID
If you've got a good number of them on a vswitch... It's a big PITA to
clear screen many many many times to get the one you wanted to see. I
often pipe it into a file to be able to study the output.
Marcy Cortes
This message may contain confidential and/or privileged information. If
you are not the addressee or authorized to receive this for the
addressee, you must not use, copy, disclose, or take any action based on
this message or any information herein. If you have received this
message in error, please advise the sender immediately by reply e-mail
and delete this message. Thank you for your cooperation.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Michael MacIsaac
Sent: Saturday, December 22, 2007 6:37 AM
To: LINUX-390@VM.MARIST.EDU
Subject: [LINUX-390] Extracting user IDs and IP addresses from QUERY
VSWITCH DETAILS
Hello list,
I was hoping to use a bash script to determine Linux user IDs and IP
addresses attached to a certain VSWITCH. With the vmcp module and the
QUERY VSWITCH DETAILS command, I get a lot of good information. I wrote
a short function that makes some assumptions:
1) Adapter owner: lines have user IDs
2) If the Name is UNASSIGNED then the user ID is not attached to the
VSWITCH
3) Otherwise the IP address follows after the line Unicast IP
Addresses:
Here's the output:
==
# ./foo
userID = LINUX116 IPaddr = 9.60.29.116
userID = LINUX117 IPaddr = 9.60.29.117
userID = LINUX118 IPaddr = 9.60.29.118
userID = LINUX119 IPaddr = 9.60.29.119
userID = LINUX124 IPaddr = 9.60.29.124
userID = LINUX125 IPaddr = 9.60.29.125
userID = LNXTEST IPaddr = none
userID = RHEL5U1 IPaddr = none
userID = SLES10S1 IPaddr = 9.60.29.115
parseVSWITCH vsw2 failed
==
So it *seems* to work. If anybody sees any bad assumptions or can
suggest a cleaner way to do this, I'd appreciate your thoughts.
Here's the code:
==
# cat foo
#!/bin/bash
#+--
+
function parseVSWITCH()
# extract user IDs and IP addresses connected to a vswitch
# Arg1: VSWITCH name
# Return: 0 - success
# 1 - Q VSWITCH failed
#+--
+
{
vswitch=$1
vmcp q vswitch $vswitch /dev/null 21
if [ $? != 0 ]; then # error
return 1
fi
vmcp q vswitch details | \
while [ 1 = 1 ]; do # do forever
read line
if [ $? = 1 ]; then # end of file
return 0
fi
if [ ${line:0:14} = Adapter Owner: ]; then # extract user ID and
name
userID=$(echo $line | awk '{ print $3 }')
name=$(echo $line | awk '{ print $7 }')
if [ $name != UNASSIGNED ]; then # get the IP address
while [ ${line:0:21} != Unicast IP Addresses: ]; do # skip
read line
done
read line
IPaddr=$(echo $line | awk '{ print $1 }')
else # assume UNASSIGNED means no IP address
IPaddr=none
fi
echo userID = $userID IPaddr = $IPaddr
fi
done
}
# main ()
parseVSWITCH vsw1
if [ $? != 0 ]; then echo parseVSWITCH vsw1 failed; fi parseVSWITCH
vsw2 if [ $? != 0 ]; then echo parseVSWITCH vsw2 failed; fi
==
For completeness here's the output of Q VSWITCH DET
==
# vmcp q vswitch det
VSWITCH SYSTEM VSW1 Type: VSWITCH Connected: 9Maxconn: INFINITE
PERSISTENT RESTRICTEDNONROUTER Accounting: OFF
VLAN Unaware
MAC address: 02-00-01-00-00-01
State: Ready
IPTimeout: 5 QueueStorage: 8
RDEV: 7004 VDEV: 7004 Controller: DTCVSW1
VSWITCH Connection:
MAC address: 00-09-6B-1A-9C-18
RX Packets: 4232093Discarded: 5 Errors: 0
TX Packets: 2817344Discarded: 0 Errors: 0
RX Bytes: 3143709816 TX Bytes: 489254172
Device: 7006 Unit: 002 Role: DATA Port: 0001 Index: 0001
RDEV: 7008 VDEV: 7008 Controller: DTCVSW2 BACKUP
Adapter Connections:
Adapter Owner: LINUX116 NIC: 0600 Name: dontcare
RX Packets: 3752469Discarded: 0 Errors: 0
TX Packets: 1821025Discarded: 0 Errors: 18
RX Bytes: 2218486112 TX Bytes: 250077384
Device: 0602 Unit: 002 Role: DATA Port: 0067 Index: 0048
Options: Broadcast Multicast IPv6 IPv4 VLAN
Unicast IP Addresses:
9.60.29.116 MAC: 02-00-01-00-00-04
FE80::200:100:800:4 MAC: 02-00-01-00-00-04 Local
Multicast IP Addresses:
224.0.0.1MAC: 01-00-5E-00-00-01
FF02::1
Re: Extracting user IDs and IP addresses from QUERY VSWITCH DETAILS
Nope - that gives me all of them... Just prefixed with the userid and a colon :) Odd that a class G userid can get that much info? Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Tuesday, January 08, 2008 10:35 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Extracting user IDs and IP addresses from QUERY VSWITCH DETAILS On Tuesday, 01/08/2008 at 01:21 EST, Marcy Cortes [EMAIL PROTECTED] wrote: It would be nice to be able to say something like Q vswitch details for USERID If you've got a good number of them on a vswitch... It's a big PITA to clear screen many many many times to get the one you wanted to see. I often pipe it into a file to be able to study the output. That would be FOR userid CMD Q VSWITCH [name] DETAILS. Alan Altmark z/VM Development IBM Endicott -- 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: Extracting user IDs and IP addresses from QUERY VSWITCHDETAILS
I mean, does the sysprog *really* want to be involved in every guest A can't ping guest B quandry? Umm. We always are. If not us, then who else? The Linux sysadmin? The network admin? Those would be us too. We may not *want* to, but that's what we do for a living :) Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Tuesday, January 08, 2008 12:25 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Extracting user IDs and IP addresses from QUERY VSWITCHDETAILS On Tuesday, 01/08/2008 at 03:09 EST, Pieter Harder [EMAIL PROTECTED] wrote: I would even say this is a security exposure. A class G user can find out what another user's macid is on a layer2 switch, and then play all kind of mischief with it. We are aware of the requirement to prevent two users on the same VSWITCH from talking to each other. Restricting the details of the VSWITCH simply makes it more difficult for the guest to be configured correctly. I mean, does the sysprog *really* want to be involved in every guest A can't ping guest B quandry? And if I wanted to, I'd just start ARPing for different IP addys and see what responses I get. Not have the QUERY output would slow me down for a few minutes. Alan Altmark z/VM Development IBM Endicott -- 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: Extracting user IDs and IP addresses from QUERY VSWITCHDETAILS
I think I'd agree with Marcy: it seems odd to tell a class G guest anything about the other guests attached to a switch. Class B, sure, but not class G. It does seem like it could give someone an idea of which was the most interesting guest on switch based on bytes in/out and therefore the most worthwhile to try to hack into first. Certain not here at a bank where that would never happen :)-- but maybe some college might have an issue. You know those students. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -- 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: IODF-HCD Defining FCP on a z9 for z/Linux
(BTW, why should PR/SM care what OS is to be run in the LPAR?) So it can know which one the IFLs can be given to? It was probably not using IFLs either since it was defined as MVS. I've been told also that you get a little penguin picture there somewhere too. Course I haven't actually seen it since no one lets me near an HMC. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Monday, January 14, 2008 2:41 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] IODF-HCD Defining FCP on a z9 for z/Linux On Mon, Jan 14, 2008 at 5:11 PM, in message [EMAIL PROTECTED], Alan Altmark [EMAIL PROTECTED] wrote: -snip- Define attached in this context. Configured is the term of art. As long as the chpids, CUs, and devices are configured to the VM LPAR (via IOCDS, HCD, or dynamic DEFINE), then CP (EDEVICE) and Linux (ATTACH or DEDICATE) can talk to the FCP adapters. This was the problem the OP was having. Since the LPAR was defined as being an MVS LPAR (BTW, why should PR/SM care what OS is to be run in the LPAR?), HCD would not allow him to configure the FCP I/O devices onto the LPAR. He had to either create a new LPAR definition, saying it was a VM LPAR or delete and redefine the existing one. The above is necessary, but typically not sufficient. Additional configuration of your SAN fabric is usually required to give Linux and/or CP access to the target WWPNs LUNs. Sure, but you have to get past the first hurdle before you can even try to deal with these items. 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 -- 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: Linux not recognizing file systems
/sbin/SuSEconfig can change permissions on things based on the settings in /etc/permissions* and /etc/sysconfig/security Could you have changed those things and run it? (or yast2 ran it after changing something else). Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of John Summerfield Sent: Monday, January 14, 2008 4:11 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Linux not recognizing file systems Joell Chockley wrote: I've got a strange problem with a Linux guest. The only indicator we've come up with so far is that /dev/null had it's file permissions changed on Friday afternoon to -rw-r--r-- 1 root root 81 2008-01-11 15:03 /dev/null (we don't know how this was changed). One of our admins changed it back to This is what I would expect to see if someone deleted /dev/null and then root did something like echo /dev/null as you would expect root to do sometimes - just look at /etc/init.d/* grep /dev/null /etc/init.d/* _I_ would like to know who|what deleted /dev/null and what else was done, it sounds to me like a breakdown in procedures, or some malware was installed. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- 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: Linux not recognizing file systems
As long as a manager says they can have it, they have it. That's all audit cares about. Ours do as well (via sudo), but they actually do do a lot of sysadmin'y things that require root. They've also have sysadmin experience and training. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Thursday, January 17, 2008 6:52 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Linux not recognizing file systems On Thu, Jan 17, 2008 at 9:21 AM, in message [EMAIL PROTECTED], Joell Chockley [EMAIL PROTECTED] wrote: We did find out after getting the problem fixed that our WebSphere Admin had mistyped a command they use to clear a log file (did a mv on /dev/null instead of a cp)...we've changed their procedure so they don't do either command anymore! This raises a whole new set of questions, one of which being why does a WebSphere admin have general root access? To prevent situations such as what you've experienced, that's not a good idea, and it's likely your auditors will have a much harsher assessment. 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 -- 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: Finding /dev/disk/by-path
I'm pretty sure it's udev. Chkconfig boot.udev on Marcy Cortes Team Lead, Enterprise Virtualization - z/VM and z/Linux Enterprise Hosting Services w. (415) 243-6343 c. (415) 517-0895 This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of RPN01 Sent: Thursday, January 31, 2008 9:05 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Finding /dev/disk/by-path Would anyone know when the /dev/disk path came into existance, or what package creates it? I have it on some of my SuSE SLES 9 images, but not on others, and I need to know what is missing to add this path -- .~.Robert P. Nix Mayo Foundation /V\RO-OE-5-55 200 First Street SW / ( ) \ 507-284-0844 Rochester, MN 55905 ^^-^^ - In theory, theory and practice are the same, but ³Join the story... Ride Ural.² in practice, theory and practice are different. -- 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 smime.p7s Description: S/MIME cryptographic signature
Re: SuSE Versions
If you haven't discovered this one yet, the sitar package will make a nice little HTML page of every thing about your servers. Mgmt might be happy with that. You can quickly build an inventory web page. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Walters, Gene P Sent: Thursday, January 31, 2008 10:09 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] SuSE Versions We are running several versions of SuSE on our IFL. I am trying to make a list of what we are running. I went into each Instance and did a cat /proc/version, but that shows me the kernel level. How can I either find the SuSE version, or equate that kernel level to a specific SuSE version? Management wants this list and they don't understand kernel versions..lol Also, how can I tell if it is 32-bit or 64-bit. 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
Re: NEW TOPIC -- Workload move from z/OS to z/Series Linux
There was a guy I talked to a z/Expo. Small customer but they had moved about all their DB2 over to Linux. I haven't seen him ever post here though. There's some quiet folks (unlike us :) out there. They are usually govt places or employers that don't let their folks say what they are doing. MQ Series and WebSphere Message Broker would be some other things to look for. But I think you'll need to inventory the z/OS stuff first! Good luck! Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Alan Ackerman Sent: Thursday, January 31, 2008 5:56 PM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] NEW TOPIC -- Workload move from z/OS to z/Series Linux My original topic was completely hijacked by disucssion of ZIIPS and ZAAP so I am going to try again. Please no more ZIIPs and ZAAPs. (Frankly, my dear, ...) Has anyone actually moved workload from z/OS to z/Linux? So far I got only one response, someone who moved TSM from z/OS to z/Linux. I got some good suggestions. Thank you! Someone asked what we run on z/OS. I don't know. It seems a bit strange that a VM system programmer is being asked to do this. I will no doubt find out one of these days. But so far I have to report that no one is doing this except one shop. Alan Ackerman Alan (dot) Ackerman (at) Bank of America (dot) 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 -- 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: Finding /dev/disk/by-path
Whew. There is this mystery I just discovered with /dev/disk/by-path [EMAIL PROTECTED]:/dev/disk/by-path ls -al total 8 drwxr-xr-x 2 root root 4096 Feb 1 09:00 . drwxr-xr-x 4 root root 4096 Feb 1 09:00 .. lrwxrwxrwx 1 root root 11 Feb 1 09:00 ccw-0.0.0100 - ../../dasda lrwxrwxrwx 1 root root 12 Feb 1 09:00 ccw-0.0.0100p1 - ../../dasda1 lrwxrwxrwx 1 root root 11 Feb 1 09:00 ccw-0.0.0101 - ../../dasdb lrwxrwxrwx 1 root root 12 Feb 1 09:00 ccw-0.0.0101p1 - ../../dasdb1 lrwxrwxrwx 1 root root 11 Feb 1 09:00 ccw-0.0.0102 - ../../dasdc lrwxrwxrwx 1 root root 12 Feb 1 09:00 ccw-0.0.0102p1 - ../../dasdc1 lrwxrwxrwx 1 root root 11 Feb 1 09:00 ccw-0.0.0103 - ../../dasdd lrwxrwxrwx 1 root root 12 Feb 1 09:00 ccw-0.0.0103p1 - ../../dasdd1 lrwxrwxrwx 1 root root 11 Feb 1 09:00 ccw-0.0.0104 - ../../dasde lrwxrwxrwx 1 root root 12 Feb 1 09:00 ccw-0.0.0104p1 - ../../dasde1 lrwxrwxrwx 1 root root 11 Feb 1 09:00 ccw-0.0.0105 - ../../dasdf lrwxrwxrwx 1 root root 12 Feb 1 09:00 ccw-0.0.0105p1 - ../../dasdf1 lrwxrwxrwx 1 root root 11 Feb 1 09:00 ccw-0.0.8001 - ../../dasdg lrwxrwxrwx 1 root root 12 Feb 1 09:00 ccw-0.0.8001p1 - ../../dasdg1 lrwxrwxrwx 1 root root 11 Feb 1 09:00 ccw-0.0.8002 - ../../dasdh lrwxrwxrwx 1 root root 12 Feb 1 09:00 ccw-0.0.8002p1 - ../../dasdh1 lrwxrwxrwx 1 root root 11 Feb 1 09:00 ccw-0.0.8003 - ../../dasdi lrwxrwxrwx 1 root root 12 Feb 1 09:00 ccw-0.0.8003p1 - ../../dasdi1 lrwxrwxrwx 1 root root 11 Feb 1 09:00 ccw-0.0.8004 - ../../dasdj lrwxrwxrwx 1 root root 12 Feb 1 09:00 ccw-0.0.8004p1 - ../../dasdj1 lrwxrwxrwx 1 root root 11 Feb 1 09:00 ccw-0.0.8005 - ../../dasdk lrwxrwxrwx 1 root root 12 Feb 1 09:00 ccw-0.0.8005p1 - ../../dasdk1 lrwxrwxrwx 1 root root 11 Feb 1 09:00 ccw-0.0.8006 - ../../dasdl lrwxrwxrwx 1 root root 12 Feb 1 09:00 ccw-0.0.8006p1 - ../../dasdl1 lrwxrwxrwx 1 root root 11 Feb 1 09:00 ccw-0.0.8007 - ../../dasdm lrwxrwxrwx 1 root root 12 Feb 1 09:00 ccw-0.0.8007p1 - ../../dasdm1 lrwxrwxrwx 1 root root 11 Feb 1 09:00 ccw-0.0.8008 - ../../dasdn lrwxrwxrwx 1 root root 12 Feb 1 09:00 ccw-0.0.8008p1 - ../../dasdn1 lrwxrwxrwx 1 root root 11 Feb 1 09:00 ccw-0.0.8009 - ../../dasdo lrwxrwxrwx 1 root root 12 Feb 1 09:00 ccw-0.0.8009p1 - ../../dasdo1 lrwxrwxrwx 1 root root 11 Feb 1 09:00 ccw-0.0.800a - ../../dasdp lrwxrwxrwx 1 root root 12 Feb 1 09:00 ccw-0.0.800a1 - ../../dasdp1 lrwxrwxrwx 1 root root 11 Feb 1 09:00 ccw-0.0.800b - ../../dasdq lrwxrwxrwx 1 root root 12 Feb 1 09:00 ccw-0.0.800b1 - ../../dasdq1 lrwxrwxrwx 1 root root 11 Feb 1 09:00 ccw-0.0.800c - ../../dasdr lrwxrwxrwx 1 root root 12 Feb 1 09:00 ccw-0.0.800c1 - ../../dasdr1 lrwxrwxrwx 1 root root 11 Feb 1 09:00 ccw-0.0.800d - ../../dasds lrwxrwxrwx 1 root root 12 Feb 1 09:00 ccw-0.0.800d1 - ../../dasds1 lrwxrwxrwx 1 root root 11 Feb 1 09:00 ccw-0.0.800e - ../../dasdt lrwxrwxrwx 1 root root 12 Feb 1 09:00 ccw-0.0.800e1 - ../../dasdt1 lrwxrwxrwx 1 root root 11 Feb 1 09:00 ccw-0.0.800f - ../../dasdu lrwxrwxrwx 1 root root 12 Feb 1 09:00 ccw-0.0.800f1 - ../../dasdu1 lrwxrwxrwx 1 root root 11 Feb 1 09:00 ccw-0.0.8010 - ../../dasdz lrwxrwxrwx 1 root root 12 Feb 1 09:00 ccw-0.0.8010p1 - ../../dasdz1 lrwxrwxrwx 1 root root 12 Feb 1 09:00 ccw-0.0.8011 - ../../dasdaa lrwxrwxrwx 1 root root 13 Feb 1 09:00 ccw-0.0.8011p1 - ../../dasdaa1 lrwxrwxrwx 1 root root 11 Feb 1 09:00 ccw-0.0.ff00 - ../../dasdv lrwxrwxrwx 1 root root 12 Feb 1 09:00 ccw-0.0.ff00p1 - ../../dasdv1 lrwxrwxrwx 1 root root 11 Feb 1 09:00 ccw-0.0.ff01 - ../../dasdw lrwxrwxrwx 1 root root 12 Feb 1 09:00 ccw-0.0.ff01p1 - ../../dasdw1 lrwxrwxrwx 1 root root 11 Feb 1 09:00 ccw-0.0.ff02 - ../../dasdx lrwxrwxrwx 1 root root 12 Feb 1 09:00 ccw-0.0.ff02p1 - ../../dasdx1 lrwxrwxrwx 1 root root 11 Feb 1 09:00 ccw-0.0.ff03 - ../../dasdy lrwxrwxrwx 1 root root 12 Feb 1 09:00 ccw-0.0.ff03p1 - ../../dasdy1 Is there some reason why the 800a-800f disks don't result in 800ap1-800fp1? The p goes missing. Is this a bug? Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Friday, February 01, 2008 9:11 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Finding /dev/disk/by-path Marcy Cortes [EMAIL PROTECTED] 01/31/08 12:11 PM I'm pretty sure it's udev. Correct. Mark Post -- For LINUX-390 subscribe / signoff / archive
Re: Finding /dev/disk/by-path
Using the ones shipped by Novell (sles9x - udev-021-36.69 ). I guess I get to make use of my support contract! Let's see if I remember how! Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Friday, February 01, 2008 12:26 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Finding /dev/disk/by-path On Fri, Feb 1, 2008 at 1:02 PM, in message [EMAIL PROTECTED], Marcy Cortes [EMAIL PROTECTED] wrote: -snip- Is there some reason why the 800a-800f disks don't result in 800ap1-800fp1? The p goes missing. Is this a bug? I agree with Adam. The fact that only the subchannel addresses with values greater than 9 makes me suspicious that it's a udev rule problem. The question is, whether the udev rules are as-shipped by Novell, or if they've been tweaked by you. If the former, I would open up a problem record. 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 -- 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: qeth setup cause code documentation
Sure looks like you don't have a 7000. What do you get with #CP Q NIC DETAILS If on a vswitch with no ESM, you may have lost your access. Set vswitch n grant vmid Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Collinson.Shannon Sent: Monday, February 04, 2008 1:01 PM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] qeth setup cause code documentation Can someone point me to where the qeth setup return codes are documented? I've found a few mentioned in scattered postings online, but none that represent our error (0xf6). I figure knowing where TFM is will help me R it... Thanks! For those interested, we're getting the following when attempting to set up the first Linux guest on a new VM lpar. Oddly, this only popped up after we had to reconfigure the ethernet settings (we had the DNS ip address wrong) during the Linux installation, but now we can't get rid of it. (Even an IPL of the lpar didn't help) ... Enter MAC address (leave empty for VSwitch) (): Device 0.0.7000 configured qeth: received an IDX TERMINATE with cause code 0xf6 qeth: sense data available on channel 0.0.7000. qeth: cstat 0x0 dstat 0xE qeth: irb: 00 c2 60 17 7b 4b d0 38 0e 00 10 00 00 80 00 00 qeth: irb: 01 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 qeth: sense data: 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 qeth: sense data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 qeth: Initialization in hardsetup failed! rc=-5 eth0: error fetching interface information: Device not found eth0 not available, check device addresses/cards. Do you want to retry the qeth-setup (Yes/No) ? Shannon Collinson l Mainframe Operating Systems l ETI l SunTrust Banks l 404.827.6070 (office) l 404.642.1280 (mobile) Seeing beyond money (sm) LEGAL DISCLAIMER The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. SunTrust and Seeing beyond money are federally registered service marks of SunTrust Banks, Inc. [ST:XCL] -- 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: OSA portname
If I recall, it requires a big chunk of memory in your virtual machine. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Ken Schweiker Sent: Wednesday, February 06, 2008 2:18 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] OSA portname I know a lot of folks are using vswitch. I just don't see a compelling reason to yet. The OSA's have been rock solid. There are plenty of ports to assign. It's a shorter pathlength. It's less complex, though vswitches are not that complex but they are another layer to set up. We do have vm guest lans for security reasons for certain servers. What am I missing? Redundancy. Anything else? Not being a LAN architect, all suggestions are welcome. We will need to address the redundancy issue in the future with some kind of OSA failover if workloads become more critical. About the portname, I finally found the location for that parameter. It wasn't my search string, just that some numskull (no names mentioned :) had set a different portname than I was looking for, on some of the servers. (I must not have noticed the portname mismatch message on startup). So then I think the answer is I would not have to use YaST to change them, just edit the hwcfg-qeth-bus-ccw-0.0.1d20? Mark Post [EMAIL PROTECTED] To Sent by: Linux on LINUX-390@VM.MARIST.EDU 390 Port cc [EMAIL PROTECTED] IST.EDU Subject Re: OSA portname 02/06/2008 03:54 PM Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU On Wed, Feb 6, 2008 at 10:14 AM, in message [EMAIL PROTECTED], Ken Schweiker [EMAIL PROTECTED] wrote: Re-defining osa addresses on zVM for a SuSE 9x server to another OSA card (OSA Express Gb LX). This is the first time this card is being used and the link does not come up. (example DEDICATE 1D00 1F20 DEDICATE 1D01 1F21 DEDICATE 1D02 1F22 ) From later notes in this thread, I see you're onto the possible cause of your error. So, I'll ask the question no one else has. Why in the world are you DEDICATEing OSA ports to a guest? Why are you not using VSWITCH? (There are legitimate reasons to do this, but the question needs to be asked, just in case.) -snip- I followed a Mark Post post to see/set portname using Yast. It was already blank but I saved it anyway. So where is the below portname coming from? -snip- Setting up network interfaces: qeth: Device 0.0.1d00/0.0.1d01/0.0.1d02 is a OSD Express card (level: 0635) with link type OSD_1000 (portname: osacssd) -snip- The fact that it is lower case means that it is being set by a Linux system, somewhere. Any Linux system connected to the OSA could be doing it, not necessarily this particular one. (You say this is the first system to use the card, so it likely is the culprit.) So, on all the systems connected to this card, you could do this: find /etc -type f | xargs grep -il osacssd 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 -- 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: OSA portname
On Wednesday, 02/06/2008 at 05:19 EST, Ken Schweiker [EMAIL PROTECTED] wrote: I know a lot of folks are using vswitch. I just don't see a compelling reason to yet. The OSA's have been rock solid. I just wanted to point out that I can remember at least 3 occasions where we've lost OSA cards. Redundancy is a good thing - but of course it depends on the criticality of your apps. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -- 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 for a friend: RPM spec file for WAS on z?
You mean like one created by something from a product that you probably are pretty familiar with ? :) (so I have one :) If you want one, some open source things like tar2rpm (alien) are worth looking at. WAS itself is not an rpm install but a java based installer. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Phil Smith III Sent: Friday, February 08, 2008 7:08 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Question for a friend: RPM spec file for WAS on z? Does anyone have an RPM spec file for WAS on z that they can share? -- ...phsiii Phil Smith III (703) 476-4511 (home office) (703) 568-6662 (cell) -- 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 smime.p7s Description: S/MIME cryptographic signature
Re: Question for a friend: RPM spec file for WAS on z?
Well, it you have a tool that only does rpms for distribution, that'd be one reason. Or maybe you like to be able to query information about the package or verify that all the pieces of it are still there, rpm would give you that. But I don't know why Phil was asking ?! So maybe he has some other things? Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Daryl Hoffman Sent: Monday, February 11, 2008 5:24 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Question for a friend: RPM spec file for WAS on z? I would be interested in knowing the benefits of this over installing from the tar files or sharing the binaries across multiple images? Does this speed up or make the installation easier? Does this make it installable on the root partition and why would one want to do that? Just curious being a linu newbie, but being more experienced with WebSphere. Thanks for any insight. Daryl On Feb 9, 2008 10:37 PM, Marcy Cortes [EMAIL PROTECTED] wrote: You mean like one created by something from a product that you probably are pretty familiar with ? :) (so I have one :) If you want one, some open source things like tar2rpm (alien) are worth looking at. WAS itself is not an rpm install but a java based installer. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Phil Smith III Sent: Friday, February 08, 2008 7:08 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Question for a friend: RPM spec file for WAS on z? Does anyone have an RPM spec file for WAS on z that they can share? -- ...phsiii Phil Smith III (703) 476-4511 (home office) (703) 568-6662 (cell) -- 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 -- Daryl R. Hoffman System Administrator Administrative Information Systems The Pennsylvania State University Cell/Home: 814-441-9448 Work: 814-863-3829 Website: http://www.personal.psu.edu/drh4 email: [EMAIL PROTECTED] [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
Yast online_update problem - curl vs. our proxy server
Wanted to see if anyone else has run into this. YOU has stopped working for me. Probabably a while ago, but I think I've finally figured out why. We have a proxy server. Novell is putting up 302 redirects on https://you.novell.com/update and files beneath that url and curl is stopping on those. I see I'm pulling things like: zlinux-maint:~ # cat /var/lib/YaST2/you/mnt/media.1/media HTMLHEADTITLENovell iChain/TITLE/HEADBODYbpYour old browser does not support a 302 Redirect./b/BODY/HTML I've disected it some and found that curl with ah -L option goes right on through these redirects and will pull good files. But I can't find a way to make online_update call curl with a -L option. Any ideas? Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -- 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: Yast online_update problem - curl vs. our proxy server
Well, still not liking me. (yast2-packagemanager-2.9.73-0.1) I did the rm command. It's hanging here and /var/lib/YasST2/you/mnt/media.1/media is still empty: zlinux-maint:~ # tail /var/log/YaST2/y2log 2008-02-12 16:08:58 1 zlinux-maint(11355) [Y2PM] Y2PM.locale.cc(LocaleSettings):103 Fallback locale: 'en' 2008-02-12 16:08:58 1 zlinux-maint(11355) [Y2PMrc] Y2PM.rcvalue.cc(rcInit):428 Initialize using: file /var/adm/YaST/y2pm/y2pmrc 2008-02-12 16:08:58 1 zlinux-maint(11355) [Y2PMrc++] Y2PM.rcvalue.cc(parse):272 assignstatus == 1 2008-02-12 16:08:58 1 zlinux-maint(11355) [Y2PM] Y2PM.cc(setCandidateOrder):137 setCandidateOrder 0 2008-02-12 16:08:58 1 zlinux-maint(11355) [mediaaccess] MediaAccess.cc(open):114 Opened: https(https://you.novell.com/update not attached; localRoot /var/lib/YaST2/you/mnt) 2008-02-12 16:08:58 2 zlinux-maint(11355) [mediaaccess] MediaCurl.cc(attachTo):129 Disable certificate verification for https. 2008-02-12 16:08:58 1 zlinux-maint(11355) [mediaaccess] MediaHandler.cc(attach):171 Attached: https://you.novell.com/update attached; localRoot /var/lib/YaST2/you/mnt 2008-02-12 16:08:58 1 zlinux-maint(11355) [mediaaccess++] MediaCurl.cc(getFileCopy):360 dest: /var/lib/YaST2/you/mnt/media.1/media 2008-02-12 16:08:58 1 zlinux-maint(11355) [mediaaccess++] MediaCurl.cc(getFileCopy):361 destNew: /var/lib/YaST2/you/mnt/media.1/media.new.yast.37456 2008-02-12 16:08:58 1 zlinux-maint(11355) [mediaaccess++] MediaCurl.cc(getFileCopy):369 URL: https://you.novell.com/update/media.1/media It'll eventually time that out, I'm sure. I'll try the very ugly hack later this evening and I *will* call you. That's what premium support is supposed to be for, right?!! Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Tuesday, February 12, 2008 4:05 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Yast online_update problem - curl vs. our proxy server On Tue, Feb 12, 2008 at 6:53 PM, in message [EMAIL PROTECTED], Marcy Cortes [EMAIL PROTECTED] wrote: Wanted to see if anyone else has run into this. YOU has stopped working for me. Probabably a while ago, but I think I've finally figured out why. We have a proxy server. Novell is putting up 302 redirects on https://you.novell.com/update and files beneath that url and curl is stopping on those. I see I'm pulling things like: zlinux-maint:~ # cat /var/lib/YaST2/you/mnt/media.1/media HTMLHEADTITLENovell iChain/TITLE/HEADBODYbpYour old browser does not support a 302 Redirect./b/BODY/HTML Hmm. I was messing with something similar today with another customer. I wound up doing an rm /var/lib/YaST2/you/mnt/media.1/* command and then things started working again for me. What's the version of yast2-packagemanager on that system? I've disected it some and found that curl with ah -L option goes right on through these redirects and will pull good files. But I can't find a way to make online_update call curl with a -L option. If the above doesn't get you back on track, I would think that a very ugly hack of renaming /usr/bin/curl to /usr/bin/curl.bin, and creating a shell script named /usr/bin/curl that invoked /usr/bin/curl.bin with the -L ahead of the rest of the parms might get you by. Just don't call me/us if it breaks. :) Try the other workaround first. 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 -- 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: Yast online_update problem - curl vs. our proxy server
I think I might have a subscription problem. I noticed all my products in my novell customer care are expired. I'll pursue that issue first and then try online_update again. Thanks Mark Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -- 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
YOU proxy CONNECT aborted
I posted a few weeks ago and Mark tried to help. I'm pretty sure our contracts stuff is straighted out on novell.com now - I can now pull stuff as described here in testing your id: http://www.novell.com/support/search.do?cmd=displayKCdocType=kcexterna lId=10099959 But when I run online_update I hang and eventually time out. These are the messages in /var/log/YaST2/y2log 2008-02-26 09:52:04 1 zlinux-maint(27828) [mediaaccess] MediaAccess.cc(open):114 Opened: https(https://marcydc:[EMAIL PROTECTED]/update not attached; localRoot /var/lib/YaST2/you/mnt) 2008-02-26 09:52:04 2 zlinux-maint(27828) [mediaaccess] MediaCurl.cc(attachTo):129 Disable certificate verification for https. 2008-02-26 09:52:04 1 zlinux-maint(27828) [mediaaccess] MediaHandler.cc(attach):171 Attached: https://marcydc:[EMAIL PROTECTED]/update attached; localRoot /var/lib/YaST2/you/mnt 2008-02-26 09:52:04 1 zlinux-maint(27828) [packagemanager++] PMYouPatchInfo.cc(getDirectory):485 Patch path: ./s390x/update/SUSE-CORE/9/patches 2008-02-26 09:52:04 1 zlinux-maint(27828) [packagemanager++] PMYouPatchInfo.cc(getDirectory):488 Directory file: ./s390x/update/SUSE-CORE/9/patches/directory.3 2008-02-26 09:52:04 1 zlinux-maint(27828) [mediaaccess++] MediaCurl.cc(getFileCopy):360 dest: /var/lib/YaST2/you/mnt/s390x/update/SUSE-CORE/9/patches/directory.3 2008-02-26 09:52:04 1 zlinux-maint(27828) [mediaaccess++] MediaCurl.cc(getFileCopy):361 destNew: /var/lib/YaST2/you/mnt/s390x/update/SUSE-CORE/9/patches/directory.3.new. yast.37456 2008-02-26 09:52:04 1 zlinux-maint(27828) [mediaaccess++] MediaCurl.cc(getFileCopy):369 URL: https://marcydc:[EMAIL PROTECTED]/update/s390x/update/SUSE-CORE/9/ patches/directory.3 2008-02-26 09:57:10 1 zlinux-maint(27828) [liby2util++] PathInfo.cc(_Log_Result):271 unlink /var/lib/YaST2/you/mnt/s390x/update/SUSE-CORE/9/patches/directory.3.new. yast.37456 2008-02-26 09:57:10 3 zlinux-maint(27828) [mediaaccess] MediaCurl.cc(getFileCopy):413 curl error: 56: Proxy CONNECT aborted But I can sit on the command line and issue a curl of that file successfully so I'm pretty sure my proxy server is configured correctly: zlinux-maint:~ # curl -v -O https://marcydc:(passwdhere)@you.novell.com/update/s390x/update/SUSE-COR E/9/patches/directory.3 -i * About to connect() to ourproxy.wellsfargo.com port 80 * Connected to ourproxy.wellsfargo.com (x.x.x.x) port 80 * Establish HTTP proxy tunnel to you.novell.com:443 * Server auth using Basic with user 'marcydc' HTTP/1.0 200 Connection established * Proxy replied OK to CONNECT request * successfully set certificate verify locations: * CAfile: /usr/share/curl/curl-ca-bundle.crt CApath: none * SSL connection using DES-CBC3-SHA * Server certificate: *subject: /C=US/ST=Utah/L=Provo/O=Novell, Inc./CN=*.novell.com *start date: 2007-11-19 19:02:51 GMT *expire date: 2009-01-18 19:02:51 GMT *common name: *.novell.com (matched) *issuer: /C=US/O=Equifax/OU=Equifax Secure Certificate Authority * SSL certificate verify ok. * Server auth using Basic with user 'marcydc' GET /update/s390x/update/SUSE-CORE/9/patches/directory.3 HTTP/1.1 Authorization: Basic bWFyY3lkYzpuN2hvYmJlcw== User-Agent: curl/7.11.0 (s390x-ibm-linux) libcurl/7.11.0 OpenSSL/0.9.7d ipv6 zlib/1.2.1 Host: you.novell.com Pragma: no-cache Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */* % Total % Received % Xferd Average Speed Time Curr. Dload Upload TotalCurrentLeft Speed 0 0 0 0 0 0 0 0 --:--:-- 0:00:00 --:--:-- 0 HTTP/1.1 200 OK Last-Modified: Mon, 25 Feb 2008 14:45:01 GMT Accept-Ranges: bytes Date: Tue, 26 Feb 2008 18:13:31 GMT Server: Apache/2.2.2 (Unix) PHP/4.4.4 ETag: 4560035-13d9-9ddc3540 Cache-Control: no-cache, must-revalidate, max-age=0 Content-Type: text/plain Content-Length: 5081 Set-Cookie: ZNPCQ002-you=V001578886e4; path=/ P3p: CP=NOI Set-Cookie: IPCZQX018ef15359=36005102026b2b0f8eda1f07; path=/; domain=.novell.com P3p: CP=NOI Via: 1.1 ICS_SERVER (iChain 2.3.410) 100 5081 100 5081 0 0 5393 0 0:00:00 0:00:00 0:00:00 64316 * Connection #0 left intact * Closing connection #0 What am I missing here? Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -- 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: YOU proxy CONNECT aborted
Yep, it's all up to date. Spident -vvv gives me all +'s except for net-snmp from Velocity. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Tuesday, February 26, 2008 10:36 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] YOU proxy CONNECT aborted On Tue, Feb 26, 2008 at 1:23 PM, in message [EMAIL PROTECTED], Marcy Cortes [EMAIL PROTECTED] wrote: I posted a few weeks ago and Mark tried to help. I'm pretty sure our contracts stuff is straighted out on novell.com now - I can now pull stuff as described here in testing your id: http://www.novell.com/support/search.do?cmd=displayKCdocType=kcexter na lId=10099959 Hmm. This is sounding a little familiar now. I think I worked with someone else on this same thing. Is your YOU server completely updated? If not, update it and try again. I'm pretty sure there was some YaST/YOU maintenance that was waiting out there, and if you didn't put it on, later on things like this start happening. I'm not 100% sure though. My brain's been a little full lately. 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 -- 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: YOU proxy CONNECT aborted
YOU doesn't work so nothing is waiting! I did go pull every rpm from Novell website for everything and did an rpm -Fvh against them all. So it is SP4+ for real. I'm about to open a service request. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Wednesday, February 27, 2008 12:40 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] YOU proxy CONNECT aborted On Tue, Feb 26, 2008 at 1:49 PM, in message [EMAIL PROTECTED], Marcy Cortes [EMAIL PROTECTED] wrote: Yep, it's all up to date. Spident -vvv gives me all +'s except for net-snmp from Velocity. We, that's not necessarily a good indication. If you put on a bunch of maintenance a long time ago, SPident will still show you as being SLESx + SPy + online updates. If you go into YOU and see if there are any updates waiting, I would try putting on anything yast2-* related and see what happens. What SPident checks against gets updated with maintenance, so if that control file hasn't been updated recently, it's checking against old information. 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 -- 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 smime.p7s Description: S/MIME cryptographic signature
Re: Syslog from z/VM CMS... And on being frustrated...
Part 1: you can stick it in the obey list, you can stick it in the PORT section, or you can turn off restrictlowports Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of RPN01 Sent: Friday, March 07, 2008 1:29 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Syslog from z/VM CMS... And on being frustrated... Part one: You apparently have to be in the Obey list to talk to port 514. There may be a way to talk to 514 from a higher port, but I haven't gone back to look at the UDP stage yet to see if that's true. In any case, adding the user to the Obey list solves the problem temporarily. We have only the Pipelines that come with z/VM 5.3 It'd be nice if IBM would catch up with the rest of the Pipelines world, but we stick to what's supported in the system. Part two: It's not how much of the network you want to sniff; it's that there is a 14 byte header missing beneath z/VM that Linux, and more importantly, tcpdump expect and that isn't provided. There is a perl script that we found that supplies this header for each record so that you can go back and properly analyze the captured data. I supposed you could pass it through to the tcpdump -r again to see it in real time, but I didn't try that. The script we found is called tcpdump-qeth.pl, so it appears to be a problem that others have previously run into. -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different. On 3/7/08 3:20 PM, Rob van der Heij [EMAIL PROTECTED] wrote: On Fri, Mar 7, 2008 at 5:47 PM, RPN01 [EMAIL PROTECTED] wrote: I put together a service virtual machine to do this task for me on some regular basis. But when the rexx exec runs there, even though it gets no errors, nothing shows up at the syslog server. This is true when the service machine is disconnected, and when I log into it and recreate by hand what I was doing from my own userid. Have you tried to run a UDP stage on the VM system and see the messages getting there? I¹m looking for differences between the two virtual machines, but I haven¹t found anything yet that makes any difference. I¹m fishing for ideas, hoping that someone here will have one that¹s better than my own have been... It could not be that you try to send UDP from port 514 as well and have the pipeline in both users at the same time, could it? Or maybe the service machine has a very old version of CMS Pipelines (not that I know of anything that would silently fail, but there could be other stage that behave a bit different). This has been complicated by the fact that tcpdump doesn¹t work on a Linux guest (at least with a default setup). I did find the grant promiscuous option, but it doesn¹t seem to make a difference on the fly; I¹m assuming that I¹d have to do the grant promiscuous before logging in the guest to allow tcpdump to work. (It would be really useful if you could turn this on on the fly) You don't have to sniff the entire network just to catch the traffic sent to port 514. After all, if you're logged on you already know the Linux server can receive data and all you need to see is what data arrives (unless you think your sending pipeline has the wrong IP address or port). Just do a tcpdump -i eth0 -n port 514 or so. And are both sending to the same Linux server? I recall the default setup is pretty stubborn in doing a firewall for no good reason... Rob -- 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: CMM questions
Hi Betsie! Have you read this one? http://www-128.ibm.com/developerworks/linux/linux390/perf/tuning_pap_VM. html#vmlm Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Spann, Elizebeth (Betsie) Sent: Friday, March 07, 2008 3:06 PM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] CMM questions Hi Gang, I'm confused and have some basic questions, please. Does VMRM Cooperative Memory Management require anything to be installed on the zLinux guest? I've activated the VMRMSVM server. Does it work with the Collaborative Memory Management Assist machine feature? Do they work independently of each other? Require each other? I need a CMM for Dummies tutorial. 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
Re: CMM questions
You'll probably have to cut and paste that back together. Not sure how to make this list not chop it. Should end with /perf/tuning_pap_VM.html#vmlm Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Spann, Elizebeth (Betsie) Sent: Friday, March 07, 2008 3:31 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] CMM questions Any other versions of the URL? I can't get to the one below. Betsie -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Marcy Cortes Sent: Friday, March 07, 2008 3:26 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: CMM questions Hi Betsie! Have you read this one? http://www-128.ibm.com/developerworks/linux/linux390/perf/tuning_pap_VM. html#vmlm Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Spann, Elizebeth (Betsie) Sent: Friday, March 07, 2008 3:06 PM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] CMM questions Hi Gang, I'm confused and have some basic questions, please. Does VMRM Cooperative Memory Management require anything to be installed on the zLinux guest? I've activated the VMRMSVM server. Does it work with the Collaborative Memory Management Assist machine feature? Do they work independently of each other? Require each other? I need a CMM for Dummies tutorial. 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 -- 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: Betr.: how can I mount /tmp as a tmpfs in SLES9?
Well, memory is a pricey resource in the z environment (and I don't suppose it got cheaper on a z10 :) Now, maybe if you had an application that had high performance needs to files in its /tmp areas... But other than that, I don't think you'd probably want to waste the memory. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Pieter Harder Sent: Monday, March 17, 2008 2:17 PM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Betr.: how can I mount /tmp as a tmpfs in SLES9? My first thought would be that it isn't a great idea to mount /tmp in Linux memory as that adds to the working set of the machine. If you want memory I would make it a z/VM Vdisk and put /tmp there and let CP handle the memory requirement. But I may be totally off base here. Anybody have numbers about this? Velocity guys? Best regards, Pieter Harder [EMAIL PROTECTED] tel +31-73-6837133 / +31-6-47272537 Collinson.Shannon [EMAIL PROTECTED] 03/17/08 10:06 And is this a bad idea? In the USS world at our shop, we've had our /tmp directory mounted as a temporary file system (backed in memory) for a decade with no problems, but we don't run all that much in USS. I know that it's possible to mount tmp as memory-it's mentioned in a few read-only-root redbooks-but I can't seem to find the mechanics on it. So either it's such a no-brainer that it doesn't bear mentioning for the most part, or it's a bad idea (explained in some doc I haven't been able to google). Which is it? Thanks! Shannon Collinson l Mainframe Operating Systems l ETI l SunTrust Banks l 404.827.6070 (office) l 404.642.1280 (mobile) Seeing beyond money (sm) LEGAL DISCLAIMER The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. SunTrust and Seeing beyond money are federally registered service marks of SunTrust Banks, Inc. [ST:XCL] -- 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 Brabant Water N.V. Postbus 1068 5200 BC 's-Hertogenbosch http://www.brabantwater.nl Handelsregister: 16005077 -- 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: Having trouble adding a volume
Be sure the place you are writing to with mkinitrd and zipl is the same thing you are booting off of. Do you see any thing regarding the 210 in dmesg? Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Brad Hinson Sent: Tuesday, March 25, 2008 12:05 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Having trouble adding a volume On Tue, 2008-03-25 at 12:37 -0600, Mark Post wrote: On Tue, Mar 25, 2008 at 2:33 PM, in message [EMAIL PROTECTED], Bauer, Bobby (NIH/CIT) [E] [EMAIL PROTECTED] wrote: Yeah, that was my though also. I just redid those steps with somebody who is a bit familiar with Linux looking over my shoulder. Same results, volume 210 does not come online. I can however use the chccwdev to bring 210 online after the boot. When you ran mkinitrd, was the 210 volume online at that point? If not, try mkinitrd and zipl while it is online. 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 It may help to run mkinitrd with -v to show verbose output. You should see a line similar to: adding dasd_mod with options dasd=200-201,210 If it does say this, can you paste the output of zipl -V? -- Brad Hinson [EMAIL PROTECTED] Sr. Support Engineer Lead, System z Red Hat, Inc. (919) 754-4198 -- 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: modprobe.conf
I take it you are not under VM, which would make all of this fun irrelevant because you can keep the same address virtually! I think what you need to do is mkinitrd and zipl to another disk but using a zipl.conf that has the appropriate dasd= parm. That is still an option in 2.6 even though most don't use it and tend to just build it without it so that the kernel picks up all the online at the time devices, from what I can tell anyway. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Fuhrmann Anna Sent: Thursday, March 27, 2008 10:16 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] modprobe.conf Hi Mark, My task and problem is not: having to bring a device online, and yes, we are running on kernel 2.6. We worked out a method to clone the system (for different purposes, involving different DASD and networking hardware) . But we do not do this by the known clone procedure that involves mount-and-modify the copied system as to DASD and network-scripts (see PS). Our method consists of 1. a fake initramdisk with changed DASD addresses that can be accessed via boot menu parameter 2. a network script in init.d that routes to different /network-scripts/-directories with the appropriate (different) configuration depending on a parameter given to the system at IPL time also via (modified) boot menu In this way we have a boot menu that enables us to boot different systems with different hardware, governed by zipl.conf paramaters. Well ... but: When trying this configuration, I ended up with kernel panic ;-)) Next thing I thought of was: I forgot about modprobe conf. I remembered that when establishing a new device in a running system one has to modify - among others - modprobe.conf. So now I am trying to copy my system to new DASD and IPL there. This different DASD is established by means of a different intrd that can be accessed by way of this new zipl.conf. But it is not established by way of modprobe.conf. And I think this might be the reason for the kernel panicking. And this is why I wanted to change modprobe.conf just for the time the system gets copied over ... PS Why I am afraid of the semi-official clone method: mounting the DASD where I copied the system and wanting to change configuration files this way may be risky because the home system and the mounted system both have the very same LogVol-setup. Same setup, meaning also same names/labels. So even if I edit a config file accessing it with an explicit path, the LogVol-manager may get upset or confused because it can find these files on both LogVols. But maybe you have an idea ...? Kind regards Anna -Original Message- From: Linux on 390 Port on behalf of Mark Post *EXTERN* Sent: Thu 3/27/2008 3:44 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: modprobe.conf On Thu, Mar 27, 2008 at 6:26 AM, in message [EMAIL PROTECTED], Fuhrmann Anna [EMAIL PROTECTED] wrote: -snip- Can I modify modprobe.conf so that in contains the *wrong* DASD addresses for a while (this should happen for the sake of copying the system DASD as a whole so that the ready copy contains the modified modprobe.conf for another LPAR with a different DASD config. Anna, Why do you think you have to modify modprobe.conf to do this? I have to believe that you're running on a 2.6 kernel, so you should be able to use chccwdev to bring the devices online and offline without modifying any configuration files. 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 -- 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: recover root password
Does anyone have full sudo? Then you could just sudo su - passwd And change it. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Miguel Roman Sent: Monday, April 14, 2008 8:03 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] recover root password Hello, We are running Suse Linux 9.3 (64 bit) under z/VM 5.1. One of the administrators changed the root password and forgot the password. Does anyone know how to recover the root password? Thanks. Miguel A Roman. -- 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: recover root password
Hey, didn't we talk about this stuff a few weeks ago on the phone? Anyway, we have a unix/linux product in lieu of sudo (on every place but zLinux at the moment due to vendor support, but that is changing real soon now) that key stroke logs (to a remote server) every thing one does while running as root, because, like Alan said, you can do things like turn off audit and destroy logs, or change the root pw, grant someone else, etc. While logonby is great and we use it all the time with byonly userids and never ever share a password on VM, we still really can't tell those who care about SOX what someone did when they logged into MAINT or VMSECURE or RACFVM if he's your guy. You can't even use last changed date on minidisks, because, well there is DDR! z/VM doesn't really have anything in place to protect you from your sysprog (or at least read about it after the fact), unlike the other o/s's that at least give the illusion that they can. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Tuesday, April 15, 2008 10:39 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] recover root password Bob Nix wrote: Anyone sticking to the I have to have root! model of system administration is leaving themselves open to a huge awakening as Sarbanes-Oxley and other regulations overtake us. While we aren't required by law to conform to Sarbanes-Oxley, we've chosen to bring ourselves as close as we possibly can. The are also living in the Dark Ages. One of the requirements is that what is done to your systems is done with accountability. To be completely compliant, everything done by / with root will need to be logged, showing what was done, and by whom. Can you do that now, with two or more people logging into root? Can you do it with even one person logging into root? Not on any distribution I know today. So you aren't compliant, and will be pinged on your audit, and if you're required to be S-O compliant, you're leaving your company open to legal action. It is heartwarming, after a fashion, to see this discussion. I forget: When did we introduce LOGON BY to z/VM? The requirement for accountability is not driven by law, but by Good Business Practices, with an eye towards long-term survival. (The fact that we had to have laws to tell people that they must use Good Business Practices speaks volumes about our society and its [lack of] values. :-( ) One of the reasons the mainframes have endured for so long is because, I believe, its purchasers' continued adherence to rigid change control practices. Time is money. So if you screw up a change, you cost us money. This was all before S-O Co. Give someone root authority, but make them say Give me root authority. Here are my credentials. If you'll check your e-clipboard, you'll that I'm On The List. (Of course, not REALLY root authority. E.g. no ability to grant root to someone else or to turn off security subsystems, auditing, etc. Dinosaurs can cause serious injury or death is not the only message to take from the movie Jurassic Park.) If I was working as a sysadmin, the number of admins was 1 and all I had was root, I'd be screaming from the rafters. Like my company, I want protection from the actions of others (plausible denability). Don't give me root's password - I don't want to know it. Alan Altmark z/VM Development IBM Endicott -- 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: Vswitch and subnets
The vswitch doesn't really advertise. You can do a couple of things. Get both of your systems hooked to the same subnet (vlan). We've done that. Or get a vip address on a new subnet (like a /30 of your own) and run a routing protocol (zebra, quagga) on your linuxes. A vswitch can be part of more than one subnet, but you do have to set it up that way out in the network. So you could give both system A and system B access to both subnets you have today. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Ayer, Paul W Sent: Wednesday, April 16, 2008 5:26 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Vswitch and subnets Good morning, Running Oracle RAC and having a problem with supporting the way Oracle does VIP address fail over. This environment has two z9 systems running z/VM 5.3 with Vswitch on each and a linux (rhel 44). On each z/VM the Vswitch is setup to support a specific subnet. Vswitch on System A side supports 192.168.127.* Vswitch on System B side supports 192.168.87.* Oracle on linux on system A has Home address 192.168.127.1 ETH0 Oracle VIP192.168.127.2 ETH0:1 Oracle Priv192.168.127.3 ETH1 Oracle on linux on system B has Home address 192.168.87.1 ETH0 Oracle VIP192.168.87.2 ETH0:1 Oracle Priv192.168.87.3 ETH1 * The problem; If something happens on the system A side and access is lost (at any level) Oracle on the system B side brings up via ETH0:2 the VIP address of the lost system. So now system B linux looks like this; Home address 192.168.87.1 ETH0 Oracle VIP192.168.87.2 ETH0:1 Oracle VIP 192.168.127.2 ETH0:2 Oracle Priv192.168.87.3 ETH1 A Q VSWITCH DET shows the 192.168.127.2 address known in the Vswitch, but it can not be routed to. Is there anything that can be done in he Vswitch to help advertise just this address only, since all the other 192.168.127.* addresses are still on the other system... Thank you, Paul... -- 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: OCFS2 Setup
One thing that comes to mind is that you need to be sure you have MDC set off for the volumes being shared. (cp set shared on ). Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Jim Fujimoto Sent: Monday, April 28, 2008 10:49 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] OCFS2 Setup Hello All, I'm trying to set up a two node ocfs2 cluster and run it on two SLES10 SP1 guests running in two different z/VM 5.3 lpars. The shared disk is an lvm volume comprised of 3390-3s, and I'm using the standard disk-based heartbeat and port . I was able to get this to work when both guests were running on the same system, but the nodes won't connect if they are running on two different z/VM systems. At first I thought it might be a network problem, but the nodes can ping and ssh each other. Is there something else that needs to be set up for this to work across lpars? 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
Re: OCFS2 Setup
Mark wrote: Please note that OCFS2 is not supported for production use on Linux for System z. This is largely due to a lack of extensive enough testing/QA work. It should work for you, but at this time its only recommended for testing. Now, if one needed to have a file system r/w from more than 1 linux server on z, what would the current supported recommendation be? And is anyone doing such with MQ Series? Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -- 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: Root file system is 90% full and I can't see why....
THe question is.. how do I re-create these device entries so that the are not regular files anymore? I can tell you that they are created out of the script /usr/share/doc/packages/devs/makedevs You could probably delete them and rerun makedevs, but I'd back things up first to make sure. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -- 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
Sles9 to 10 upgrades and disk naming
We use /dev/disk/by-path names to label all of our disks on sles9 rather than the /dev/dasda.. In zipl.conf for the root= as well as in /etc/fstab. Now.. Sles10 has decided that instead of /dev/disk/by-path/ccw-0.0.0100p1 It will call the disk /dev/disk/by-path/ccw-0.0.0100-part1 So the upgrade process doesn't work. Is there a better way other than reverting back to /dev/dasda.. And then changing it backup again when we're doing upgrading? Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -- 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 10 and /etc/sysconfig/proxy
If I update /etc/syscongfig/proxy with our proxy server and include NO_PROXY = localhost, wellsfargo.com , yast2 seems to ignore the no_proxy part and still attempts to go throught the proxy server to get to the installation source, which fails. If proxy is turned off in that file, all is well with yast, but then I can't get out for other stuff. Is there something else I'm missing here before I open a ticket with Novell? Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -- 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 smime.p7s Description: S/MIME cryptographic signature
Re: SLES 10 and /etc/sysconfig/proxy
* sorry about the digital signature thing on the previous one If I update /etc/syscongfig/proxy with our proxy server and include NO_PROXY = localhost, wellsfargo.com , yast2 seems to ignore the no_proxy part and still attempts to go throught the proxy server to get to the installation source, which fails. If proxy is turned off in that file, all is well with yast, but then I can't get out for other stuff. Is there something else I'm missing here before I open a ticket with Novell? Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -- 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: Searching this archive
Alan, Try searching here http://www.mail-archive.com/linux-390@vm.marist.edu/ instead. Seems to work better for me (and faster). Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -- 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 10 and /etc/sysconfig/proxy
Noproxy would be the .wellsfargo.com stuff - where my installation server is sitting. I don't want it to attempt to go through proxy for that. It won't work. I do have to go through the proxy to get to nu.novell.com or anything else on the net for that matter. Unless I turn off all proxy (PROXY_ENABLED=no in /etc/sysconfig/proxy), I can't get yast2 to stay inside to see the installation server. Sles9 works the way I want. Just sles 10 seems to ignore the noproxy line. I've been trying to open an SR, but apparently novell.com is all confused about us again - I've got the account team looking at that. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Tuesday, May 27, 2008 11:30 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] SLES 10 and /etc/sysconfig/proxy On Fri, May 23, 2008 at 11:21 AM, in message [EMAIL PROTECTED], Marcy Cortes [EMAIL PROTECTED] wrote: * sorry about the digital signature thing on the previous one If I update /etc/syscongfig/proxy with our proxy server and include NO_PROXY = localhost, wellsfargo.com , yast2 seems to ignore the no_proxy part and still attempts to go throught the proxy server to get to the installation source, which fails. If proxy is turned off in that file, all is well with yast, but then I can't get out for other stuff. Is there something else I'm missing here before I open a ticket with Novell? Well, yes there is. :) The domain you want to have in your noproxy list is likely nu.novell.com, right? Mark -- 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 to 10 upgrades and disk naming
It can't find the root file system on the 1st boot and you don't get very far. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Tuesday, May 27, 2008 12:13 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Sles9 to 10 upgrades and disk naming On Thu, May 22, 2008 at 10:14 PM, in message [EMAIL PROTECTED], Marcy Cortes [EMAIL PROTECTED] wrote: We use /dev/disk/by-path names to label all of our disks on sles9 rather than the /dev/dasda.. In zipl.conf for the root= as well as in /etc/fstab. Now.. Sles10 has decided that instead of /dev/disk/by-path/ccw-0.0.0100p1 It will call the disk /dev/disk/by-path/ccw-0.0.0100-part1 So the upgrade process doesn't work. Is there a better way other than reverting back to /dev/dasda.. And then changing it backup again when we're doing upgrading? What exactly happens during the upgrade? I haven't tried this myself, so I don't know. 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 -- 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 to 10 upgrades and disk naming
lrwxrwxrwx 1 root root 11 May 25 02:07 ccw-0.0.ff02 - ../../dasdl lrwxrwxrwx 1 root root 12 May 25 02:07 ccw-0.0.ff02p1 - ../../dasdl1 lrwxrwxrwx 1 root root 11 May 25 02:07 ccw-0.0.ff03 - ../../dasdm lrwxrwxrwx 1 root root 12 May 25 02:07 ccw-0.0.ff03p1 - ../../dasdm1 Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of RPN01 Sent: Tuesday, May 27, 2008 12:57 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Sles9 to 10 upgrades and disk naming I've noticed that the naming of the devices is very inconsistent. Just within SuSE SLES 9, I see /dev/disk/by-path/ccw-0.0.07ffp1 and /dev/disk/by-path/ccw-0.0.07ff1. And as noted, this is different from SLES 10 which had /dev/disk/by-path/ccw-0.0.07ff-part1. Isn't the point of this to have predictable names for the devices? But if you can't predict what the predictable name will be, how is it any better than /dev/dasda and /dev/dasdb? On 5/27/08 2:13 PM, Mark Post [EMAIL PROTECTED] wrote: On Thu, May 22, 2008 at 10:14 PM, in message [EMAIL PROTECTED], Marcy Cortes [EMAIL PROTECTED] wrote: We use /dev/disk/by-path names to label all of our disks on sles9 rather than the /dev/dasda.. In zipl.conf for the root= as well as in /etc/fstab. Now.. Sles10 has decided that instead of /dev/disk/by-path/ccw-0.0.0100p1 It will call the disk /dev/disk/by-path/ccw-0.0.0100-part1 So the upgrade process doesn't work. Is there a better way other than reverting back to /dev/dasda.. And then changing it backup again when we're doing upgrading? What exactly happens during the upgrade? I haven't tried this myself, so I don't know. 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 -- 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 to 10 upgrades and disk naming
Not yet (bigger fishies to fry). Little wary of doing so. A fix would probably break our /etc/fstab which is coded without the p's :). Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Tuesday, May 27, 2008 2:15 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Sles9 to 10 upgrades and disk naming On Tue, May 27, 2008 at 5:02 PM, in message [EMAIL PROTECTED], Marcy Cortes [EMAIL PROTECTED] wrote: Absolutely agree with that! There is also what I consider a bug in SLES 9 - if the address ends in a A-F as opposed to a 0-9, the p is left off. We've coded around it where needed. (See 900A-900F below). That does indeed look like a bug. Have you filed a problem report against 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 -- 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: express password ?
Considering that SP2 only came out a week ago, that's hardly surprising. FWIW, there are post-SP2 updates already, including a security kernel update 2.16.60-0.23 update from the 0.21 shipped with SP2. It came out the 20th as well. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -- 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 smime.p7s Description: S/MIME cryptographic signature
Re: express password ?
I think I figured this one out. At least this is what it took for my yup server to get it to grap SP2+ as well. Try updating /etc/sysconfig/yup like this: YUP_SUBVERSIONS=GA SP1 SP2 Or maybe better: YUP_SUBVERSIONS=SP1 SP2 Marcy -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Chase, John Sent: Wednesday, May 28, 2008 10:50 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] express password ? -Original Message- From: Linux on 390 Port On Behalf Of Levy, Alan I want to log in to see the directory structure that is on nu.novell.com. I have a local yum server that someone else maintains (and is on vacation). I ran the move to sles10 sp2 patch and when I went back into online update, there were no patches available. Fascinating. I observed the same result on a SLED 10.1 box at home the other night. I wonder if it's related? -jc- -- 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 Maintenance Mirror (was: Express Password?)
A lot: # du -cksh * 1.9GSLES10-SP1-Online 4.9GSLES10-SP1-Updates 2.1GSLES10-SP2-Online 58M SLES10-SP2-Updates 1.6GSLES10-Updates 11G total Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Kern Sent: Thursday, May 29, 2008 4:44 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] SLES Maintenance Mirror (was: Express Password?) Can anyone give a rough estimate of the DASD space required to hold all of the maintenance for 'GA SP1 SP2' of SLES10? Having read Mark's article on setting up a maintenance mirror, I am interested in trying it, but do not want to be in the run it, increase space, run it, increase space, run it, repeat until complete mode. /Tom Kern Mark Post wrote: On Wed, May 28, 2008 at 11:56 PM, in message [EMAIL PROTECTED], Marcy Cortes [EMAIL PROTECTED] wrote: I think I figured this one out. At least this is what it took for my yup server to get it to grap SP2+ as well. Try updating /etc/sysconfig/yup like this: YUP_SUBVERSIONS=GA SP1 SP2 Or maybe better: YUP_SUBVERSIONS=SP1 SP2 That didn't work for me without modifying the yup script itself. To avoid having a number of people spend some amount of time doing just that, might I draw your attention to the Subscription Management Tool that was announced in the SP2 press release: http://www.novell.com/news/press/novell-delivers-suse-linux-enterprise -10-enhancements-in-service-pack-2 It's the second paragraph, and it's intended to be a _supported_ replacement for YUP, as well as having far more functionality. I don't believe it is available for download yet, contrary to the verbiage in the press release, but if not, it should be within a couple of weeks. 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 -- 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 10 and /etc/sysconfig/proxy
Only my own. No novell.com. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Thursday, May 29, 2008 11:07 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] SLES 10 and /etc/sysconfig/proxy On Tue, May 27, 2008 at 2:59 PM, in message [EMAIL PROTECTED], Marcy Cortes [EMAIL PROTECTED] wrote: Noproxy would be the .wellsfargo.com stuff - where my installation server is sitting. I don't want it to attempt to go through proxy for that. It won't work. I do have to go through the proxy to get to nu.novell.com or anything else on the net for that matter. Unless I turn off all proxy (PROXY_ENABLED=no in /etc/sysconfig/proxy), I can't get yast2 to stay inside to see the installation server. Sles9 works the way I want. Just sles 10 seems to ignore the noproxy line. What installation sources does YaST think you have? If one of them is a novell.com host, then you should remove it. Mark -- 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: Intrusion Detection Solution for Suse SLES 10 on zLinux
I recently read in the SLES 10 SP 2 release notes that AIDE is replacing Tripwire in SLES. Not sure if that's the kind of tool you are looking for. http://sourceforge.net/projects/aide Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Perry Sent: Thursday, June 05, 2008 6:42 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Intrusion Detection Solution for Suse SLES 10 on zLinux Robert Giordano wrote: I am looking for a software solution that is supported on zLinux SuSe SLES 10 SP1 for Intrusion Detection. Any thoughts is greatly appreciated! I've not really tried it, but SNORT ships with SLES See http://www.snort.org mark -- 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: How do I pull the SP2 updates down with YUM?
I think you need to upgrade yup. Its working for me with yup-232-2.1 Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Peter E. Abresch Jr. - at Pepco Sent: Monday, June 09, 2008 7:25 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] How do I pull the SP2 updates down with YUM? How do I pull the SP2 updates down with YUM? I changed YUP_SUBVERSIONS=SP1? to YUP_SUBVERSIONS=SP1 SP2 in the YUP configuration. I also have YUP_DEST_DIR=/var/cache/yup so I created the following SP2 directories there: drwxr-xr-x 3 root root 80 Jun 27 2007 SLES10-SP1-Online drwxr-xr-x 3 root root 80 Jul 10 2007 SLES10-SP1-Updates drwxr-xr-x 3 root root 80 Jun 9 09:44 SLES10-SP2-Online drwxr-xr-x 3 root root 80 Jun 9 09:45 SLES10-SP2-Updates However, after running yup, the SP2 directories are empty. I have been pulling SP1 updates successfully for quite some time. I know I am missing something but cannot determine what. I am running yup-224-27.1 Peter This Email message and any attachment may contain information that is proprietary, legally privileged, confidential and/or subject to copyright belonging to Pepco Holdings, Inc. or its affiliates (PHI). This Email is intended solely for the use of the person(s) to which it is addressed. If you are not an intended recipient, or the employee or agent responsible for delivery of this Email to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this message in error, please immediately notify the sender and permanently delete this Email and any copies. PHI policies expressly prohibit employees from making defamatory or offensive statements and infringing any copyright or any other legal right by Email communication. PHI will not accept any liability in respect of such communications. -- 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: How do I pull the SP2 updates down with YUM?
It might be possible that you have to register an SP2 system first. FWIW - I don't have one registered. Peter does SP1 work ok for you? Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Monday, June 09, 2008 10:30 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] How do I pull the SP2 updates down with YUM? On Mon, Jun 9, 2008 at 12:48 PM, in message [EMAIL PROTECTED], Peter E. Abresch Jr. - at Pepco [EMAIL PROTECTED] wrote: Thanks Marcy and Marc, I downloaded the latest yup (yup-232-2.2) but am still having problems. I am seeing curl: (22) The requested URL returned error: 403 -- -- Fetching https://nu.novell.com/repo/$RCE/SLES10-SP2-Online/sles-10-s390x/repodata /repomd. xml.. . FAILED with e xit code 22 Failure details: -- -- Warning: Illegal date format for -z/--timecond (and not a file name). Warning: Disabling time condition. See curl_getdate(3) for valid date syntax. * About to connect() to nu.novell.com port 443 * Trying 72.246.210.34... connected * Connected to nu.novell.com (72.246.210.34) port 443 * successfully set certificate verify locations: * CAfile: /usr/share/curl/curl-ca-bundle.crt CApath: none I noticed that in the yup config I have the following new parameter but do not quite understand what I should specify or whether it is causing the problem. Any ideas? YUP_SP_SUBCHANS= The YaST /etc/sysconfig editor will tell you what can go there. Essentially it will be -Updates or -Online or both. I just tested on my system, and I don't see the 403 errors. That almost always means some sort of authorization/permissions error on the server side. It might be possible that you have to register an SP2 system first. If that doesn't work, and you can still mirror SP1 updates, then I would open an SR with Novell to find out why you don't seem to have access to the SP2 channels. 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 -- 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 10 SP1 and SP2 install defaults of disk by device-ID
It's a bad choice of defaults on z. It coming out of the HW. My guess is your box had some changes made to it, internally perhaps, or you are on a different volume. All minidisks on the same VM volume will have the same by-id, from what I can tell. Makes cloning problematic too I suspect. And problematic if you pprc I think, although I haven't gotten that far with testing anywhere that we have pprc. I like device path personally. The numbers look just like the numbers you have to enter on the chccwdev command. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Michael MacIsaac Sent: Tuesday, June 10, 2008 8:10 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] SLES 10 SP1 and SP2 install defaults of disk by device-ID Hi, We have some SLES 10 SP1 and SP2 systems which were installed using the default of identifying disks by device ID. This weekend our raised floor took a power hit so all LPARs and disk arrays crashed. Most Linux systems came back fine, but a few SLES 10 SP1 and SP2 systems that identified disks by device ID failed. Here are the important console messages: ... Loading jbd Loading ext3 Waiting for device /dev/disk/by-id/ccw-IBM.7500030375.010b.22-part1 to appear: ..not found -- exiting to /bin/sh The systems had to be repaired manually. Once /etc/fstab and /etc/zipl.conf (followed by mkinitrd and zipl) were modified to identify disk by file name (e.g. /dev/dasda1), the systems came up fine. What strikes me as surprising is that it seems the disks by-id could not be found after a power hit (I have no idea where to find the value ccw-IBM.7500030375.010b.22 in the above example). Why could the system find the correct disk by name but not by ID? Has anyone experienced this? (rebooting such systems has worked fine normally, so the power hit seems to be related). Also, just a heads-up for anyone with SLES 10 SP1 and SP2. If you are installing, you might want to click Fstab Options on the Edit Partition panel and set the Mount in /etc/fstab radio button group to device name. If you have systems that identify disk by ID, you might want to test scenarios such as this. Mike MacIsaac [EMAIL PROTECTED] (845) 433-7061 -- 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 10 SP1 and SP2 install defaults of disk by device-ID
Yay! We wish you success! Mike, from the release notes: http://www.novell.com/linux/releasenotes/s390x/SUSE-SLES/10/RELEASE-NOTE S.en.html Using Disks in z/VM If SLES 10 is installed on disks in z/VM, which reside on the same physical disk, the created access path (/dev/disk/by-id/) is not unique. The ID of a disk is the ID of the underlaying disk. So if two or more disk are on the same physical disk, they all have the same ID. To avoid this ambiguity, please use the access path by-path. This can be specified during the installation when the mount points are definied. To change from by-id to by-path please perform the following steps: Modify /etc/zipl.conf to use by-path names, example: parameters = root=/dev/disk/by-path/ccw-0.0.0201-part1 TERM=dumb Have the boot configuration pick up the changes: mkinitrd zipl -V Change all by-id entries in /etc/fstab to by-path entries as well, example: /dev/disk/by-path/ccw-0.0.0201-part1 / ext3 acl,user_xattr 1 1 reboot to pick up changes So they tell you to change it (and say please)!!! Scary just to move a minidisk and have your linux not boot :) Marcy Cortes Team Lead, Enterprise Virtualization - z/VM and z/Linux Enterprise Hosting Services w. (415) 243-6343 c. (415) 517-0895 This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Tuesday, June 10, 2008 2:17 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] SLES 10 SP1 and SP2 install defaults of disk by device-ID On Tue, Jun 10, 2008 at 5:11 PM, in message [EMAIL PROTECTED], Marcy Cortes [EMAIL PROTECTED] wrote: It's a bad choice of defaults on z. -snip- I like device path personally. The numbers look just like the numbers you have to enter on the chccwdev command. If I am successful, that default will be changing to by-path with SLES10 SP3 and SLES11 for System z. 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 -- 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 10 SP1 and SP2 install defaults of disk by device-ID
And if you really want to use UID, you should install the recently available VM64273 and follow the instructions in the sles10 sp2 release notes. (although, still, I think a bad idea :) on z -- maybe a really good idea on a peecee perhaps). Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Tuesday, June 10, 2008 2:37 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] SLES 10 SP1 and SP2 install defaults of disk by device-ID On Tuesday, 06/10/2008 at 05:15 EDT, Mark Post [EMAIL PROTECTED] wrote: The uid comes from the storage device itself. From one of my z/VM guests: # cat /sys/bus/ccw/devices/0.0.0150/uid IBM.7500026069.1014.16 It is supposed to be unique to the hardware device itself, based on serial number, or some such thing. If the actual hardware changes, so does that value. The by-name value gets generated by the Linux kernel, based on the order of the device numbers that get passed to it. That's why the names are not persistent, and can change if the kernel parameters are changed without preserving the original order. The UID is indeed unique to the device. It consists of manufacturer's name, plant of manufacture, and a serial number. That allows you to identify a volume, independent of how you access it (UAs, device numbers, chpids, etc.). Alan Altmark z/VM Development IBM Endicott -- 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: How do I pull the SP2 updates down with YUM?
I get not authorized as well when pulling with that wget command and my NCC id. It does work, however with the credentials from my /etc/sysconfig/yup (YUP_ID and YUP_PASS) - those were the mirror credentials from ncc for my SLES 10 product in there. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Peter E. Abresch Jr. - at Pepco Sent: Tuesday, June 10, 2008 4:30 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] How do I pull the SP2 updates down with YUM? Thanks for your patience, Mark, I enter the command and got exactly what you expected. Resolving nu.novell.com... 72.246.210.34 Connecting to nu.novell.com|72.246.210.34|:443... connected. HTTP request sent, awaiting response... 401 Unauthorized Reusing existing connection to nu.novell.com:443. HTTP request sent, awaiting response... 401 Unauthorized Authorization failed. I am still confused. I do not understand why I am not authorized. I am registered for SLES10. I am fine with SLES10-SP1. How do I authorized for SLES10-SP2? Peter Mark Post [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 06/10/2008 02:48 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: How do I pull the SP2 updates down with YUM? On Tue, Jun 10, 2008 at 7:30 AM, in message [EMAIL PROTECTED], Peter E. Abresch Jr. - at Pepco [EMAIL PROTECTED] wrote: From the YUP log I see the following Illegal date format error which starts the errors off. I do not think this has any relation to authorization problems but then I do not claim to be an expert on the internal tickings of YUP. The order the error messages come out don't necessarily reflect chronology due to buffering or something. If you cannot successfully issue this command (with appropriate substitutions for nccuserid and nccpassword): wget --http-user=nccuserid --http-password=nccpassword https://nu.novell.com/repo/\$RCE/SLES10-SP2-Updates/sles-10-s390x/repoda ta/repomd.xml.asc then you have a permissions problem. Marcy, we are running yup-232-2.2 and you said you are running yup-232-2.1? Mark, which version of yup are you running? Maybe this is a yup problem? # rpm -q yup yup-232-2.2 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 This Email message and any attachment may contain information that is proprietary, legally privileged, confidential and/or subject to copyright belonging to Pepco Holdings, Inc. or its affiliates (PHI). This Email is intended solely for the use of the person(s) to which it is addressed. If you are not an intended recipient, or the employee or agent responsible for delivery of this Email to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this message in error, please immediately notify the sender and permanently delete this Email and any copies. PHI policies expressly prohibit employees from making defamatory or offensive statements and infringing any copyright or any other legal right by Email communication. PHI will not accept any liability in respect of such communications. -- 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: linux error during IPL requesting root password
Felipe Bannwart Perina wrote: Hello all! Whenever one of our linux system crashes during IPL, I get this message: fsck failed for at least one filesystem (not /). Please repair manually and reboot. The root file system is is already mounted read-write. Does this happen often? I'd be kinda concerned if it does. Are they journaled filesystems? Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -- 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: Linux guest on a diet
It's actually simpler - you don't have to create any CDx directories. Just mount the iso file somewhere with path ending in DVD1 and use that as your installation source. I used: /apps/installroot/SLES10/DVD1 So mount -t iso9660 -oloop SLES-10-SP2-DVD-s390x-GM-DVD1.iso /apps/installroot/SLES10/DVD1 Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Peter E. Abresch Jr. - at Pepco Sent: Monday, June 23, 2008 9:35 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Linux guest on a diet I downloaded the SLES10-SP2 DVD ISO and copied it to my local Linux server in directory /usr/local/share/sles10-s390x/DVD. I have the following directories, the CDx is from my original SLES10 installation. drwxr-xr-x 7 root root 944 Apr 19 2007 CD1 drwxr-xr-x 4 root root 224 Apr 19 2007 CD2 drwxr-xr-x 4 root root 224 Apr 19 2007 CD3 drwxr-xr-x 4 root root 224 Apr 19 2007 CD4 drwxr-xr-x 8 root root 968 Jun 20 15:48 DVD I go into YaST2 and add another NFS installation source. I enter my NFS IP address and Path to directory image is /usr/local/share/sles10-s390x/DVD. ISO Image option is not checked. The file structure looks just like that of CD1. However, it fails with the following from the YaST2 log: . . . 2008-06-23 12:19:32 1 linuxyum(3142) [susetags] SuseTagsImpl.cc(operator()):77 Probing for YaST source... 2008-06-23 12:19:32 1 linuxyum(3142) [susetags] SuseTagsImpl.cc(operator()):84 YaST source detected... 2008-06-23 12:19:32 1 linuxyum(3142) [YCP] PackageCallbacks.ycp:986 Source nfs://10.10.33.245/usr/local/share/sles10-s390x/DVD is type YaST 2008-06-23 12:19:32 1 linuxyum(3142) [YCP] PackageCallbacks.ycp:861 CloseSourcePopup: _source_open: 1 2008-06-23 12:19:32 1 linuxyum(3142) [YCP] PackageCallbacks.ycp:858 Closing source progress popup 2008-06-23 12:19:32 1 linuxyum(3142) [YCP] PackageCallbacks.ycp:861 CloseSourcePopup: _source_open: 0 2008-06-23 12:19:32 1 linuxyum(3142) [YCP] PackageCallbacks.ycp:1060 Source probe end: error: url: nfs://10.10.33.245/usr/local/share/sles10-s390x/DVD, error: NO_ERROR, description: 2008-06-23 12:19:32 1 linuxyum(3142) [YCP] PackageCallbacks.ycp:865 SourceCreateStart: nfs://10.10.33.245/usr/local/share/sles10-s390x/DVD 2008-06-23 12:19:32 1 linuxyum(3142) [YCP] PackageCallbacks.ycp:776 Opening source progress popup: Creating source nfs://10.10.33.245/usr/local/share/sles10-s390x/DVD 2008-06-23 12:19:32 1 linuxyum(3142) [YCP] PackageCallbacks.ycp:834 OpenSourcePopup: _source_open: 1 2008-06-23 12:19:32 1 linuxyum(3142) [zypp] SourceFactory.cc(createSourceImplWorkflow):162 Trying to create source of type YaST 2008-06-23 12:19:32 1 linuxyum(3142) [source] MediaSet.cc(redirect):64 Adding media verifier to redirected medium 2008-06-23 12:19:32 0 linuxyum(3142) [media] MediaManager.cc(delVerifier):550 MediaVerifier change: id=7, verifier=zypp::media::NoVerifier 2008-06-23 12:19:32 0 linuxyum(3142) [media] MediaManager.cc(addVerifier):534 MediaVerifier change: id=7, verifier=N4zypp6source10SourceImpl8VerifierE 2008-06-23 12:19:32 1 linuxyum(3142) [source] SourceImpl.cc(factoryCtor):177 Setting autorefresh: 1 2008-06-23 12:19:32 1 linuxyum(3142) [susetags] SuseTagsImpl.cc(cacheExists):553 Checking if source cache exists in 2008-06-23 12:19:32 1 linuxyum(3142) [susetags] SuseTagsImpl.cc(cacheExists):568 DATA not found, MEDIA not found, MEDIA/media.1/media not found 2008-06-23 12:19:32 1 linuxyum(3142) [susetags] SuseTagsImpl.cc(factoryInit):590 Cache dir not set. Downloading to temp dir: /var/tmp/zypp.eMhGpk/TmpDir.adwFTY 2008-06-23 12:19:32 0 linuxyum(3142) [media] MediaManager.cc(checkDesired):113 checkDesired(7): desired (report by N4zypp6source10SourceImpl8VerifierE) 2008-06-23 12:19:32 5 linuxyum(3142) [base] Exception.cc(log):94 MediaHandler.cc(getFile):1238 THROW:MediaHandler.cc(getFile):1238: File './media.1/media' not found on medium 'nfs://10.10.33.245/usr/local/share/sles10-s390x/DVD' 2008-06-23 12:19:32 5 linuxyum(3142) [base] Exception.cc(log):94 2008-06-23 12:19:32 1 linuxyum(3142) [susetags] SuseTagsImpl.cc(downloadNeeded):224 media file used to determine if source changed not found. Assuming refresh needed. 2008-06-23 12:19:32 1 linuxyum(3142) [susetags] SuseTagsImpl.cc(saveMetadataTo):537 SuseTags source has changed since last download. Re-reading metadata into /var/tmp/zypp.eMhGpk/TmpDir.adwFTY 2008-06-23 12:19:32 1 linuxyum(3142) [source] SourceImpl.cc(resetMediaVerifier):411 Reseting media verifier 2008-06-23 12:19:32 0 linuxyum(3142) [media] MediaManager.cc(delVerifier):550 MediaVerifier change: id=7,
Re: Question DASD on CLIENT from Start system instructions
The other advantage to a small /boot minidisk of its own in a VM environment is that if you mess it up (like your maintenance to the kernel missed doing mkinitrd/zipl) , you can DDR a good one from a another server. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Edmund R. MacKenty Sent: Wednesday, July 02, 2008 9:22 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Question DASD on CLIENT from Start system instructions On Wednesday 02 July 2008 12:02, Mark Post wrote: Some people like to break /boot out into a separate partition, even on System z. It's not necessary, per se, since mainframe's don't have any BIOS limitations to work around. But, some people feel more comfortable with it, or want their mainframe systems to look more like their midrange ones. One reason for having /boot on a separate filesystem is to keep it safe. Some distros (Gentoo, perhaps Debian?) default to a separate /boot filesystem which is not mounted by default. This keeps your pesky users from mucking with it. It also ensures that the /boot filesystem is never mounted read-write during normal operations, including reboots. This pretty much avoids the possibility of filesystem corruption. The only time you mount it read-write is when you have to install a new kernel into it. So a separate /boot is a safety measure. - MacK. - Edmund R. MacKenty Software Architect Rocket Software, Inc. Newton, MA USA -- 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: Systems management - quick survey?
Define systems management :) The items under 1 to me say monitoring, the items under 2 say provisioning, 3 provisioning + patching (at least for Levanta anyway). Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Michael MacIsaac Sent: Monday, July 07, 2008 12:39 PM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Systems management - quick survey? Hello list, I'm preparing for a SHARE presentation (week of Aug 11, San Jose, CA) on z/VM and Linux systems management. If you use Linux and z/VM on System z, do you have time for a quick survey? I tried to categorize what's available today into 4 main areas (I apologize if I your software is not on the list, or if it listed as Dead or dying but is not. I do not also plan to address performance management). Here is the survey: ---snip--- Systems management software used: 1) Open source software: _ Hobbit _ Nagios _ Other ___ 2) Priced software: _ CSL-Wave _ IBM Systems Director/Tivoli Provisioning Manager _ Mainstar Provisioning Expert (formerly Rocket Software) _ Other ___ 3) Dead or dying (??): _ Aduva OnStage/Director _ Levanta _ Other ___ 4) Roll your own systems management - comments: What is your greatest need in z/VM and Linux systems management? : Comments on z/VM and Linux systems management in general: ---snip--- Reply on or off-list. Your feedback is appreciated. Thanks. Mike MacIsaac [EMAIL PROTECTED] (845) 433-7061 -- 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
Reiser
Hans Reiser leads police to body: http://www.sfgate.com/cgi-bin/article.cgi?f=/c/a/2008/07/07/BAN011LDR8.D TL Those still running reiserfs on their linux server may want to format and try ext3... Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -- 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 download the compete dvd of sp10
And you might just want to grab the SP2 one instead. It is a complete install disk replacement for the original sles10 disk. Will save you from having to update it later. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Wednesday, July 09, 2008 12:22 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] can't download the compete dvd of sp10 On Wed, Jul 9, 2008 at 3:15 PM, in message [EMAIL PROTECTED], Ayer, Paul W [EMAIL PROTECTED] wrote: Hi On the web page: http://download.novell.com/protected/Summary.jsp?buildid=0SF2mutIxKc~ I have used the download button next to ; SLES-10-IBM zSeries-DVD1.iso 4.2 GB (4514115584) The download completes successfully as far as my http session is concerned but the file is only 219148288 in size ... -rw-r--r-- 1 root root 219148288 Jul 9 14:59 SLES-10-IBM_zSeries-DVD1.iso I did an md5 on if also it is's way off ... What am I doing wrong please? Most likely, you're using Internet Explorer. Either use a different browser, or download it directly to your Linux system: wget -N --http-user=nccuserid --http-password=nccpassword https://downloadurl from the download button. I do this all the time, and it works fine. To get the URL, right click on the download button, and select the equivalent of copy the link location. Then paste that into your SSH session on the Linux system. 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 -- 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: dvd download
Re: wget on Linux - I think Paul already said he wasn't allowed out of Linux to the internet. But perhaps he could set up linux to use the same proxy server that his IE is set up for and sneak out that way :) (update /etc/sysconfig/proxy and run /sbin/SuSEconfig on SuSE - be sure to logout/in to get the new env variables). Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Scott Rohling Sent: Wednesday, July 09, 2008 1:46 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] dvd download Try wget on Linux.. If you're on Windows -- well, I use Cygwin and have wget on there.. For files this big, straight browser downloads don't seem to do well. wget allows you do recontinue a broken xfer (wget -c).. I have terrible luck with very large files with just about anything but wget and torrent clients.. Scott On Wed, Jul 9, 2008 at 2:18 PM, Ayer, Paul W [EMAIL PROTECTED] wrote: Ok after the Firefox session sitting at 4% for a long time for the sp0 dvd1 it now says complete. The file size I got is 219,148,577 SLES-10-IBM zSeries-DVD1.iso (almost the same size as before with IE) Should be 4,514,115,584 Per the web page ... The directory has 41,055,455,777 bytes still free Paul -- 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: Systems management - quick survey?
One should ask some really tough questions :) When was your last release for this platform? What date is the next planned update? How does that compare to the other platform? Are they on the same level? How many other z customers do you have? Can you give me references? Quiz the marketing rep--- who else is he/she marketing too at the moment? Can we have some joint discussions/presentations? (once bitten twice shy :) I kinda feel for the vendors. This is a very tough and really super educated crowd. (what other computer internet list can you get on and not get ripped apart for being clueless ? :) While that it is good, that just means fewer vendors are going to tread into the z linux space without a good sized handful of customers with checkbooks (unless they are IBM - but hey, not even all their stuff runs on z linux :) Even CA hasn't made good progress in z Linux things and their pockets are probably deep and they do understand the z customers. We've had some success in getting together with other large customers and pressuring the vendors to deliver z linux agents for their stuff (we're not even asking for the servers -- just the darn agents so we can fall in line with the company choices -- choices made by the distributed world czars). Levanta did really help with a lot of the systems management issues that Mike asked about. The interface to the VM directory (whether it be VM:secure, Dirmaint/RACF, or xedit the big file) - call that 'virtual bare metal' if you will, was flawless. They solved the DASD sharing problem transparently to the server with their mapfs filesystem. Being venture capitalist funded... They ran outta time (but imploded way way after the rest of those who came on the map in 2000 :) Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Wednesday, July 09, 2008 7:06 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Systems management - quick survey? On Wed, Jul 9, 2008 at 2:38 PM, in message [EMAIL PROTECTED], Michael MacIsaac [EMAIL PROTECTED] wrote: Thanks to all who replied. I did get a note off-list that Aduva does still support System z: Yes, we do still have a version that supports Z - but most of our growth is really in the distributed Linux and Solaris space. So I apologize to Aduva for suggesting their product might be dead. Perhaps, but try finding any mention of that on their web site. 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 -- 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: Reiser
Yes, we have a whole department dedicated to vendor flogging and no one doing any kernel building. We call that function vendor management (VM)(not to be confused with voice mail or virtual machine - VF would have been a better acronym IMHO ;). Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Monday, July 14, 2008 3:12 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Reiser On Monday, 07/14/2008 at 05:55 EDT, Erik N Johnson [EMAIL PROTECTED] wrote: Building a kernel is not a herculean task by any measure. It is completely automated and the configuration can easily be done graphically if you have an X11 server. You probably need to go looking for some literature before you try to boot up a machine as expensive as a z10 on a homebrew kernel, but scads of PC Linux users build their own kernel with every new release. The benefit is perhaps to be questioned on big iron, bearing in mind that the folks like SuSE that provide those default builds also provide lots of the actual kernel code. Besides, the peripherals on a mainframe are much less numerous and klugey, eliminating another big reason to roll your own. It's not hard, just not that useful. It's not a question of difficulty. When you build your own kernel, the support you get from the distributors evaporates. Corporate customers need someone to flog in case things go bad, ergo no custom kernels by policy. Perhaps the distributors are more tolerant of custom kernels on other platforms - I don't know. Alan Altmark z/VM Development IBM Endicott -- 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: Adding SuSE 10 dasd
Lea, Just vary it online (chccwdev -e 0.0.) and then mkinitrd and zipl. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Stahr, Lea Sent: Tuesday, August 12, 2008 9:55 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Adding SuSE 10 dasd The disk was defined in the VM directory for the Linux guest but was not picked up during the boot. On SLES 8 we added them ZIPL.CONF but the SLES 10 ZIPL.CONF file does not contain the disk range on the PARAMETERS statement. Lea Stahr zVM, Linux and zLinux Administrator Navistar, Inc. 630-753-5445 [EMAIL PROTECTED] -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Rich Smrcina Sent: Tuesday, August 12, 2008 11:44 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding SuSE 10 dasd That doesn't add a disk, it enables (think: vary online) an existing disk. Mauro Souza wrote: I usually add a dasd using chccwdev -e 0.0.0123 have you tried it? -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2009 - Orlando, FL - May 15-19, 2009 -- 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 CONFIDENTIALITY NOTICE: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender. -- 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: Safety Reminder: If you are planning disk upgrades, make sure you switch your Linux guests to by-path IDs in /etc/fstab BEFORE you switch
by-path is what we do I couldn't find any down side to it - unless you like to change virtual addresses in your VM directory entry randomly or something like that :) Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Fargusson.Alan Sent: Tuesday, August 12, 2008 10:07 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Safety Reminder: If you are planning disk upgrades, make sure you switch your Linux guests to by-path IDs in /etc/fstab BEFORE you switch Is there a consensus on what should be used? YAST gives me five choices. I don't understand some of them: Device name: I think this one is a problem if you add a device that has a lower device number then an existing device. Volume label: This might be a good way to go. This will probably break cloning. UUID: This might also be a good way to go, if UUIDs are really as unique as they should be. This probably will not work for cloning. Device ID: This one seems like a bad idea, since it breaks cloning, and it fails if one Linux instance has two or more minidisk on the same volume. Device path: This looks like the best option to me. Any down side to this? -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of David Boyes Sent: Tuesday, August 12, 2008 9:22 AM To: LINUX-390@VM.MARIST.EDU Subject: Safety Reminder: If you are planning disk upgrades, make sure you switch your Linux guests to by-path IDs in /etc/fstab BEFORE you switch A safety reminder: If you're planning to replace disk subsystems, make sure your Linux guests (particularly any SLES 10 or above) guests do NOT use by-ID paths in /etc/fstab. Fix this BEFORE the new disk goes in, both RH and SuSE (Debian, too), or your guests will not be able to find their filesystems (and thus won't boot or run). This really should be in IBM and other DASD vendors planning information for new installs, and I'd demand a fix from your Linux vendors. By-ID is a stupid default for this architecture (for any architecture, I'd argue...) and needs a fix ASAP. IBM, EMC, Hitachi: how do we get this added to your planning guides? RH, Novell, how about it? -- db -- 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 __ CONFIDENTIALITY NOTICE: This email from the State of California is for the sole use of the intended recipient and may contain confidential and privileged information. Any unauthorized review or use, including disclosure or distribution, is prohibited. If you are not the intended recipient, please contact the sender and destroy all copies of this email. -- 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: z/VM, Linux, MQ, HA?
z10's are reliable, but not perfect - they go down (well, z9's do :). RAID disks fail too. SW fails. Nothing's perfect. You have to figure out the cost of providing redundancy in all layers vs. what an outage costs you. It's different for every app usually. Have you seen this? (watch for line wrap) http://www-03.ibm.com/servers/eserver/zseries/library/whitepapers/pdf/HA _Architectures_for_Linux_on_System_z.pdf Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Wednesday, August 13, 2008 4:14 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] z/VM, Linux, MQ, HA? On Wednesday, 08/13/2008 at 05:12 EDT, Tom Burkholder [EMAIL PROTECTED] wrote: So I contend that the z/10 h/w is reliable, the DASD is raid, the vswitch can have failover OSA's, so as long as we alert and don't fill up filesystems, we have a decent chance to keep the QMGR available on the z/Linux server. Because of HACMP for AIX and Windows clustering, everybody wants to know about z/Linux HA at the O/S level. You need it. It's not about the hardware, it's about people and software. Your applications need protection from an *unplanned* outage, for a variety of reasons: - loss of power - z/VM abend - I *meant* to shutdown my 2nd level system And, of course, there are other reasons you may PLAN to turn off the machine, the LPAR, or VM (service). Alan Altmark z/VM Development IBM Endicott -- 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: z/VM, Linux, MQ, HA?
There's this http://www.ibm.com/developerworks/linux/library/l-halinux2/ which discusses MQ. We've got a project that wants to try this. Nothing special for z/Linux except that the DASD would be accessible by more than one LPAR and we need to make sure its not r/w on both. Requires minidisk cache off, CSE perhaps to protect having r/w by more than one system by accident. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Tom Burkholder Sent: Wednesday, August 13, 2008 5:59 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] z/VM, Linux, MQ, HA? Alan and Marty, Thanks... yes, I had previously read this HA architectures for Linux on System z (which is a very good reference) and because we are a z/OS DB2 sysplex environment I can understand the WAS diagrams to use WebSphere clustering to two z/Linux AppServers each running http and WebSphere. In front of the http, we can use a network load balancer to balance (redundant) to the http servers, and the backend z/OS db2 is on multiple z/OS lpars within a sysplex. These solutions I can understand and provide appropriate redundancy based on what the app is willing to pay. Currently, we only have one z/VM (still POC) and multiple z/Linux WAS appservers (and still just testing, nothing production). I've read about db2/udb's HADR and this, from what I understand with no working knowledge, is a way to active/passive provide failover for db2/udb, onto two (2) separate z/Linux servers. What I haven't seen yet, is anything similar to the whitepaper below explaining WebSphere AppServer and db2/udb or any docs on WebSphere MQ High Availability for QMGR's on z/Linux. Does anybody have any links or docs that have something specific for MQ on z/Linux, similar to the whitepaper doc below? Thanks in advance, Tom Burkholder From: Linux on 390 Port [EMAIL PROTECTED] On Behalf Of Marcy Cortes [EMAIL PROTECTED] Sent: Wednesday, August 13, 2008 7:31 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: z/VM, Linux, MQ, HA? z10's are reliable, but not perfect - they go down (well, z9's do :). RAID disks fail too. SW fails. Nothing's perfect. You have to figure out the cost of providing redundancy in all layers vs. what an outage costs you. It's different for every app usually. Have you seen this? (watch for line wrap) http://www-03.ibm.com/servers/eserver/zseries/library/whitepapers/pdf/HA _Architectures_for_Linux_on_System_z.pdf Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Wednesday, August 13, 2008 4:14 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] z/VM, Linux, MQ, HA? On Wednesday, 08/13/2008 at 05:12 EDT, Tom Burkholder [EMAIL PROTECTED] wrote: So I contend that the z/10 h/w is reliable, the DASD is raid, the vswitch can have failover OSA's, so as long as we alert and don't fill up filesystems, we have a decent chance to keep the QMGR available on the z/Linux server. Because of HACMP for AIX and Windows clustering, everybody wants to know about z/Linux HA at the O/S level. You need it. It's not about the hardware, it's about people and software. Your applications need protection from an *unplanned* outage, for a variety of reasons: - loss of power - z/VM abend - I *meant* to shutdown my 2nd level system And, of course, there are other reasons you may PLAN to turn off the machine, the LPAR, or VM (service). Alan Altmark z/VM Development IBM Endicott -- 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
Re: Help with network settings on z/Linux
Check your MTU sizes along the way. Try ping with a large packet size (-c ) and see if it gets through. Tracepath command might be useful to see what's happening along the way. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Martin, Terry R. (CMS/CTR) (CTR) Sent: Tuesday, August 19, 2008 7:40 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Help with network settings on z/Linux Hi We have two environments that we are building as part of our POC. We ship data via DB2 Connect from the mainframe DB2 to a Linux guest via a HiperSockets Network. In our DEV environment all of our tables process without issue. In our VAL environment there are six tables that the SQL fails for. We have been engaged with IBM via a PMR on this and have been going back and forth. At this point it appears that the issue is with the number of rows. In the SQL when they do an SELECT * and do not specify the rows it works. When they specify the tables in the Select it apparently increases the size of the SQL and it never gets to the mainframe. It looks like it is a 2k buffer limitation somewhere. Is there anything in the TCP/IP stack in z/Linux or any network setting in z/Linux that would enforce this limitation? IBM says that the TCP/IP and DB2 Connect on the z/OS side appear to be ok. They are sending us back to look at the Linux settings. This is the original error message: DSNL511I .DB1I DSNLIENO TCP/IP CONVERSATION FAILED 922 TO LOCATION 10.4.26.19 IPADDR=10.4.26.19 PORT=32924 SOCKET=RECV RETURN CODE=1121 REASON CODE= Thank You, Terry Martin Lockheed Martin - Information Technology z/OS z/VM Systems - Performance and Tuning Cell - 443 632-4191 Work - 410 786-0386 [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
Re: z/VM, Linux, MQ, HA?
Right - to have more than one system access it - only one side can be r/w to it (unless you have some sort of clustering file system). That's why I suggested CSE to keep it safe - VM can protect the links. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Fargusson.Alan Sent: Tuesday, August 19, 2008 8:45 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] z/VM, Linux, MQ, HA? Even with minidisk cache off you can still have problems sharing a Linux filesystems if any system has the filesystem mounted r/w. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Marcy Cortes Sent: Monday, August 18, 2008 9:32 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: z/VM, Linux, MQ, HA? There's this http://www.ibm.com/developerworks/linux/library/l-halinux2/ which discusses MQ. We've got a project that wants to try this. Nothing special for z/Linux except that the DASD would be accessible by more than one LPAR and we need to make sure its not r/w on both. Requires minidisk cache off, CSE perhaps to protect having r/w by more than one system by accident. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Tom Burkholder Sent: Wednesday, August 13, 2008 5:59 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] z/VM, Linux, MQ, HA? Alan and Marty, Thanks... yes, I had previously read this HA architectures for Linux on System z (which is a very good reference) and because we are a z/OS DB2 sysplex environment I can understand the WAS diagrams to use WebSphere clustering to two z/Linux AppServers each running http and WebSphere. In front of the http, we can use a network load balancer to balance (redundant) to the http servers, and the backend z/OS db2 is on multiple z/OS lpars within a sysplex. These solutions I can understand and provide appropriate redundancy based on what the app is willing to pay. Currently, we only have one z/VM (still POC) and multiple z/Linux WAS appservers (and still just testing, nothing production). I've read about db2/udb's HADR and this, from what I understand with no working knowledge, is a way to active/passive provide failover for db2/udb, onto two (2) separate z/Linux servers. What I haven't seen yet, is anything similar to the whitepaper below explaining WebSphere AppServer and db2/udb or any docs on WebSphere MQ High Availability for QMGR's on z/Linux. Does anybody have any links or docs that have something specific for MQ on z/Linux, similar to the whitepaper doc below? Thanks in advance, Tom Burkholder From: Linux on 390 Port [EMAIL PROTECTED] On Behalf Of Marcy Cortes [EMAIL PROTECTED] Sent: Wednesday, August 13, 2008 7:31 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: z/VM, Linux, MQ, HA? z10's are reliable, but not perfect - they go down (well, z9's do :). RAID disks fail too. SW fails. Nothing's perfect. You have to figure out the cost of providing redundancy in all layers vs. what an outage costs you. It's different for every app usually. Have you seen this? (watch for line wrap) http://www-03.ibm.com/servers/eserver/zseries/library/whitepapers/pdf/HA _Architectures_for_Linux_on_System_z.pdf Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Wednesday, August 13, 2008 4:14 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] z/VM, Linux, MQ, HA? On Wednesday, 08/13/2008 at 05:12 EDT, Tom Burkholder [EMAIL PROTECTED] wrote: So I contend that the z/10 h/w is reliable, the DASD is raid, the vswitch can have failover OSA's, so as long as we alert and don't fill up filesystems, we have a decent chance to keep the QMGR available
Re: z/VM, Linux, MQ, HA?
The solution is that MQ is up only on 1 server at a time. The HA portion takes it down on one server (dismounts the disks) and up on the other server (after remounting the disks). Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Fargusson.Alan Sent: Tuesday, August 19, 2008 10:15 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] z/VM, Linux, MQ, HA? Even if only one system has the filesystem mounted r/w the other systems can see an inconsistent filesystem due to buffering. The only safe way is to mount the filesystem r/o everywhere, or use NFS or something similar. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Marcy Cortes Sent: Tuesday, August 19, 2008 8:59 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: z/VM, Linux, MQ, HA? Right - to have more than one system access it - only one side can be r/w to it (unless you have some sort of clustering file system). That's why I suggested CSE to keep it safe - VM can protect the links. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Fargusson.Alan Sent: Tuesday, August 19, 2008 8:45 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] z/VM, Linux, MQ, HA? Even with minidisk cache off you can still have problems sharing a Linux filesystems if any system has the filesystem mounted r/w. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Marcy Cortes Sent: Monday, August 18, 2008 9:32 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: z/VM, Linux, MQ, HA? There's this http://www.ibm.com/developerworks/linux/library/l-halinux2/ which discusses MQ. We've got a project that wants to try this. Nothing special for z/Linux except that the DASD would be accessible by more than one LPAR and we need to make sure its not r/w on both. Requires minidisk cache off, CSE perhaps to protect having r/w by more than one system by accident. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Tom Burkholder Sent: Wednesday, August 13, 2008 5:59 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] z/VM, Linux, MQ, HA? Alan and Marty, Thanks... yes, I had previously read this HA architectures for Linux on System z (which is a very good reference) and because we are a z/OS DB2 sysplex environment I can understand the WAS diagrams to use WebSphere clustering to two z/Linux AppServers each running http and WebSphere. In front of the http, we can use a network load balancer to balance (redundant) to the http servers, and the backend z/OS db2 is on multiple z/OS lpars within a sysplex. These solutions I can understand and provide appropriate redundancy based on what the app is willing to pay. Currently, we only have one z/VM (still POC) and multiple z/Linux WAS appservers (and still just testing, nothing production). I've read about db2/udb's HADR and this, from what I understand with no working knowledge, is a way to active/passive provide failover for db2/udb, onto two (2) separate z/Linux servers. What I haven't seen yet, is anything similar to the whitepaper below explaining WebSphere AppServer and db2/udb or any docs on WebSphere MQ High Availability for QMGR's on z/Linux. Does anybody have any links or docs that have something specific for MQ on z/Linux, similar to the whitepaper doc below? Thanks in advance, Tom Burkholder From: Linux on 390 Port [EMAIL PROTECTED] On Behalf Of Marcy Cortes [EMAIL PROTECTED] Sent: Wednesday, August 13, 2008 7:31 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: z/VM, Linux, MQ, HA? z10's are reliable, but not perfect - they go down (well, z9's do :). RAID disks fail too. SW fails
Re: 3270 console confusion
From /etc/sysconfig/yup # There are two options, to get the ID: # # 1. use the Machine ID: this value is in #/etc/zmd/deviceid #on the machine you registered with. # # 2. go to the Novell Customer Center and request #mirror credentials to get updates to all your #systems with one yup run #http://www.novell.com/center/ The 1st way did not work for me either. The second did. That is, after I figured which proxy server would let me out of our env - hopefully you too don't have a picky picky proxy server. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Friday, August 22, 2008 9:29 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] 3270 console confusion On 8/22/2008 at 8:52 AM, in message [EMAIL PROTECTED], Robin Atwood [EMAIL PROTECTED] wrote: -snip- Thanks for the pointer. I have activated the product and configured yup as documented but when I run it I get a lot of messages: -snip- I have set YUP_ID and YUP_PASS to the values in /etc/zmd, so what have I missed? That looks like the registration failed for some reason. What does rug sl and rug ca show you? 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 -- 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
Support dates for IBM products on new releases of SLES
Have to do some 2009 planning... How long is it typically between the availability of the next release of SLES (or RHEL for that matter) before IBM will support WAS, DB2, MQ Series on it? Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -- 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: 3270 console confusion
With the defaults, your going to get all the patches from GA, SP1, and SP2 plus the ones to take you from each of the levels to the other. That'll be like 12G of stuff. If you're already SP2 (either installed from that media or upgraded with the DVD image), just pull the ones for SP2+. Change YUP_SP_SUBCHANNELS to -Updates and YUP_SUBVERSIONS to SP2. On novell.com, be sure and login first or you won't find any s390x stuff. Here's a link to the latest kernel - http://download.novell.com/Download?buildid=HLu7cmk-lZA~ Wasn't easy to find -- took some hunting. What I love is their Error!! You seem to have encountered an error on an otherwise perfect Web Site. And no link to report that. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Robin Atwood Sent: Saturday, August 23, 2008 4:57 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] 3270 console confusion On Friday 22 Aug 2008, Mark Post wrote: On 8/21/2008 at 4:11 PM, in message The first part of my article at http://www.zjournal.com/index.cfm?section=articleaid=992 talks about how you register your system. If you follow those directions, the setup is done for you by the tools. Ok, I give up, the yup thing is complete overkill, it downloaded 3GB of rpms I have no interest in before it filled up the file-system. All I want is *one* rpm file, maybe plus a dependency. It seems impossible to find anything on the Novell website. If I go to the Patch finder and select s390x, nothing is found. If I enter kernel-default into the search field, no kernels are found. I am logged in, so please tell me, what is the secret? TIA -Robin -- -- Robin Atwood. Ship me somewheres east of Suez, where the best is like the worst, Where there ain't no Ten Commandments an' a man can raise a thirst from Mandalay by Rudyard Kipling -- -- 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: Problem with chccwdev and SuSE SLES10 SP2
It fails for me too on 0.27 kernel. Looks like you have a bug to report. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Florian Bilek Sent: Sunday, August 24, 2008 8:32 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Problem with chccwdev and SuSE SLES10 SP2 Dear all, I made a fall back on kernel 0.23 and the situation is that chccwdev is working well. I am more convinced now that it has something to do with the patch for the kernel 0.27. Best regards, Florian On Sun, Aug 24, 2008 at 5:16 PM, Neale Ferguson [EMAIL PROTECTED]wrote: Did you do a vmcp attach or link to get the device back into your virtual machine configuration? The detach has removed the device so the virtual machine cannot see it anymore. On 8/24/08 10:53 AM, Florian Bilek [EMAIL PROTECTED] wrote: When I do now a e.g. chccwdev -e 0.0.3210 it is working, I can use the disk. Then I do a unmount, chccwdev -d 0.0.3210 and a vmcp detach. Later, when I want to do a second time this exercise, chccwdev retruns a fail and a retcode 1. This is not only for this device but for any other I link and enable with chccwdev later. When I recycle the Linux Guest, it is working again one time. I suspect the 0.27 kernel but I have to prove this. Does somebody have the same expericene? -- 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 -- Best regards Florian Bilek -- 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: Rename vol label
David's is the best answer, but if you must, use fdasd -l to change them. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Monday, August 25, 2008 8:09 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Rename vol label How the volume label can be changed for the Z/linux machine which is cloned . Use minidisks. Then you don't have to change them. -- 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: Two Different YaST2 Control Center displays
It's impossible to get rid of some of these things too. Sound drivers, wireless, usb, pci utils, other things pre-req these type of things and in the deleting them you get to a point that yast itself would have to go too. Although I did manage to get rid of alsa! Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Scott Rohling Sent: Tuesday, August 26, 2008 2:47 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Two Different YaST2 Control Center displays Hmm.. a sound card on a z .. I've often grumbled that the s390x distros need to exclude drivers for devices that don't even exist on a z .. (or maybe we can direct it to the HMC PC to entertain the ops folks? ;-) Scott Rohling -- 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: Differece in RED Hat and Suse
I have to say I'm very impressed that SuSE can backport so many of those new features that Linux dev is pumping out into the service stream without requiring us to get to new versions, releases. We have to go through so many hours of certifications and checkouts and other vendor concurrence to get new releases in that we're just now getting to SLES 10 on the eve of 11, +2 years past GA. But getting to SLES9 SP4 has not been traumatic at all - with zero impact to users.And the very long support life will certainly help us - the large enterprise customers who have hundreds to upgrade.. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Wednesday, August 27, 2008 8:36 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Differece in RED Hat and Suse On 8/27/2008 at 11:02 PM, in message [EMAIL PROTECTED], Scott Rohling [EMAIL PROTECTED] wrote: SUSE tends to be more 'bleeding edge' and RH tends to be more 'stable' (please - no flame wars on that - it's just my impression that RH is very focused on stability - more so than SUSE). Having seen what goes on from the inside for the last 18 months, I can confidently say that you're incorrect about that. After all, it was SUSE that invented the concept of an enterprise Linux distribution. Novell/SUSE isn't so crazy as to commit to supporting things for seven years, and then not be extremely concerned about product stability. 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 -- 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: YAST fails to grow an ext3 FS on LVM.
Works for me. Just did that a couple of days ago. With Yast. On SLES 10 SP 2. Volume still mounted too. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Fargusson.Alan Sent: Friday, August 29, 2008 11:54 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] YAST fails to grow an ext3 FS on LVM. Has anyone ask Novell why YAST fails to grow a logical volume that has an ext3 filesystem on it? I would, except we don't have support. __ CONFIDENTIALITY NOTICE: This email from the State of California is for the sole use of the intended recipient and may contain confidential and privileged information. Any unauthorized review or use, including disclosure or distribution, is prohibited. If you are not the intended recipient, please contact the sender and destroy all copies of this email. -- 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: 127.0.0.2 in /etc/hosts?
Nope. Fresh installl of 10 sp2 looks like that here too. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Wednesday, September 10, 2008 11:58 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] 127.0.0.2 in /etc/hosts? On Wednesday, 09/10/2008 at 11:18 EDT, Michael MacIsaac/Poughkeepsie/[EMAIL PROTECTED] wrote: Hello list, On a SLES 10 SP2 system, it seems the last line in /etc/hosts is: # tail -1 /etc/hosts 127.0.0.2 gpok189.endicott.ibm.com gpok189 Where the DNS name of the machine is gpok189.endicott.ibm.com. But the IP address is not there. Why is 127.0.0.2 and not Linux's IP address there? Is this something new in SP2? I don't recall seeing it in older versions of SLES. Thanks. That smells like someone manually created it. 127.anything, not just 127.0.0.2, is localhost. Alan Altmark z/VM Development IBM Endicott -- 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: Informix on zLinux ?
We've certified it. That means the DBA's have tested it, found that all their tools work, and are happy supporting it. I don't think they've found any apps that have any time or perhaps apps with any $ to move. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, September 19, 2008 7:39 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Informix on zLinux ? anyone doing this yet ? We appear to be about to jump into this world and any advise is welcome. We have 2 IFLs, VM 5.3 and SLES 10.1 ( or maybe 10.2 by now ) but are truly raw rookies in this environment. We are going to look at the Velocity toolset and take whatever tools IBM has provided us - what else need to go into the toolkit ? Bruce Lightsey Mississippi Dept. of Information Technology Services 301 N. Lamar St., Suite 508 Jackson, Ms 39201-1495 (601) 359-2644 voice (601) 359-1394 fax www.its.ms.gov www.ms.gov mailto:[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
Re: var subdirectory
Try doing init 1 That'll take down all your processes. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Gentry, Stephen Sent: Saturday, September 27, 2008 12:58 PM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] var subdirectory I think I've painted myself into a corner. My root subdirectory has gotten full. When I built this linux, /opt and a couple other subdir were installed as separate mount points. Now, I'd like to move var to a separate dasd/mount point. When I try to rm the var subdirectory, I use the -rf command. However, 5 subdir's won't delete. They are: `var/lib/nfs/rpc_pipefs/statd' `var/lib/nfs/rpc_pipefs/portmap' `var/lib/nfs/rpc_pipefs/nfs' `var/lib/nfs/rpc_pipefs/mount' `var/lib/nfs/rpc_pipefs/lockd' I get an operation not permitted message. I figure that maybe there is a task running, so I go and kill some tasks that look like they might be related to this, but still no luck. I need to remove this subdir so I can mount the new one (var). I do not have a 2nd linux running therefore, I cannot mount this disk to a 2nd one and delete var. Basically, all I have is a linux command line in a 3270 session. I can't putty into this linux under existing conditions. Does anyone have any suggestion? Thanks, Steve -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: var subdirectory
Once logged into root at the console, you can do the init 1 from there. If you're not getting that far, you may have to boot your rescue system and fix it from there. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Gentry, Stephen Sent: Saturday, September 27, 2008 1:39 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] var subdirectory I tried doing init 1 at the command prompt after linux came up. It accepted the init command, but when I issue the rm statement, I get the same messages. When I issue a ps -ef command, all processes are still running. If I'm supposed to issue init 1 at startup time, where do I do that? At startup time, I get a list of kernels and I can issue a #cp command to choose which kernel. If I have to do the init 1 here, how do I do it? Steve -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Marcy Cortes Sent: Saturday, September 27, 2008 4:23 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: var subdirectory Try doing init 1 That'll take down all your processes. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Gentry, Stephen Sent: Saturday, September 27, 2008 12:58 PM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] var subdirectory I think I've painted myself into a corner. My root subdirectory has gotten full. When I built this linux, /opt and a couple other subdir were installed as separate mount points. Now, I'd like to move var to a separate dasd/mount point. When I try to rm the var subdirectory, I use the -rf command. However, 5 subdir's won't delete. They are: `var/lib/nfs/rpc_pipefs/statd' `var/lib/nfs/rpc_pipefs/portmap' `var/lib/nfs/rpc_pipefs/nfs' `var/lib/nfs/rpc_pipefs/mount' `var/lib/nfs/rpc_pipefs/lockd' I get an operation not permitted message. I figure that maybe there is a task running, so I go and kill some tasks that look like they might be related to this, but still no luck. I need to remove this subdir so I can mount the new one (var). I do not have a 2nd linux running therefore, I cannot mount this disk to a 2nd one and delete var. Basically, all I have is a linux command line in a 3270 session. I can't putty into this linux under existing conditions. Does anyone have any suggestion? Thanks, Steve -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Change the Linux from VSWITCH to DEDICATEd OSA addresses
I have a Linux server (sles 10 sp 2) that is currently using VSWITCH with no problems. I need to change him to use a DEDICATEd OSA. I keep getting qeth: Could not register IP address 10.93.27.248 (rc=0xe080/57472) When I change the device from a NIC to 3 dedicated OSAs (same osa cards). I've tried both layer 2 and layer 3. Any ideas? The OSA is there it just doesn't seem to want to talk to the Linux guest: CP Q V OSA OSA 3000 ON OSA F408 SUBCHANNEL = 3000 DEVTYPE OSA CHPID D9 OSD 3000 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE OSA 3001 ON OSA F409 SUBCHANNEL = 0001 3001 DEVTYPE OSA CHPID D9 OSD 3001 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE OSA 3002 ON OSA F40A SUBCHANNEL = 0002 3002 TOKEN = D2F75100 3002 DEVTYPE OSA CHPID D9 OSD 3002 QDIO ACTIVE QIOASSIST-ELIGIBLE QEBSM 3002 3002 INP + 01 IOCNT = ADP = 015 PROG = 000 UNAVAIL = 113 3002 BYTES = 3002 OUT + 01 IOCNT = ADP = 000 PROG = 000 UNAVAIL = 128 3002 BYTES = 3002 OUT + 02 IOCNT = ADP = 000 PROG = 000 UNAVAIL = 128 3002 BYTES = 3002 OUT + 03 IOCNT = ADP = 000 PROG = 000 UNAVAIL = 128 3002 BYTES = 3002 OUT + 04 IOCNT = ADP = 000 PROG = 000 UNAVAIL = 128 3002 BYTES = Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -- 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 the Linux from VSWITCH to DEDICATEd OSA addresses
Nope, picking some address I know has never been used: # ifconfig eth0 10.93.27.200 ifconfig eth0 10.93.27.200 qeth: Could not register IP address 10.93.27.200 (rc=0xe080/57472) Oct 7 15:36:42 tefvm-proxy kernel: qeth: Could not register IP address 10.93.27 .200 (rc=0xe080/57472) Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Tuesday, October 07, 2008 3:28 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Change the Linux from VSWITCH to DEDICATEd OSA addresses On 10/7/2008 at 6:21 PM, in message [EMAIL PROTECTED], Marcy Cortes [EMAIL PROTECTED] wrote: I have a Linux server (sles 10 sp 2) that is currently using VSWITCH with no problems. I need to change him to use a DEDICATEd OSA. I keep getting qeth: Could not register IP address 10.93.27.248 (rc=0xe080/57472) Is that the same IP address the system had on the VSWITCH? If so, the OSA probably thinks it's already in use. What happens if you try an address that isn't/wasn't in use before? 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 -- 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 the Linux from VSWITCH to DEDICATEd OSA addresses
But that's got to be a big lie :) --- it is working if it is on a vswitch. Just not with dedicates. The cables are happy. The ports are happy. The physical switch is happy. What else would cause a reject? Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Bruce Hayden Sent: Tuesday, October 07, 2008 3:43 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Change the Linux from VSWITCH to DEDICATEd OSA addresses An old post from the world traveling Alan Altmark said this about code 0xe080: Now *this* I can help with. See that RETCODE? I recognize it as an OSA reject code. Those are documented in an appendix of the OSA/SF book. It means that: - a cable is not plugged into the port (both ends) - the port has been disabled by the Support Element - the port is not enabled on the physical switch Bottom line: The OSA is suffering from sensory deprivation of one form or another. On Tue, Oct 7, 2008 at 6:38 PM, Marcy Cortes [EMAIL PROTECTED] wrote: Nope, picking some address I know has never been used: # ifconfig eth0 10.93.27.200 ifconfig eth0 10.93.27.200 qeth: Could not register IP address 10.93.27.200 (rc=0xe080/57472) Oct 7 15:36:42 tefvm-proxy kernel: qeth: Could not register IP address 10.93.27 .200 (rc=0xe080/57472) Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -- Bruce Hayden Linux on System z Advanced Technical Support IBM, Endicott, NY -- 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 the Linux from VSWITCH to DEDICATEd OSA addresses
Yep, same chpid. This is on a z10, z/VM 5.4, sles 10 sp2. Maybe I should go try in on a z9, z/VM 5.3 and sles9 sp4 just for grins since it sounds like it ought to work! Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Tuesday, October 07, 2008 3:56 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Change the Linux from VSWITCH to DEDICATEd OSA addresses On 10/7/2008 at 6:46 PM, in message [EMAIL PROTECTED], Marcy Cortes [EMAIL PROTECTED] wrote: But that's got to be a big lie :) --- it is working if it is on a vswitch. Just not with dedicates. The cables are happy. The ports are happy. The physical switch is happy. Are you sure what is/was being used for the VSWITCH is on the same CHPID as the new device you're trying to use? Each card has two possible cable connections (4 with the new z10s). 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 -- 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: Kjournal questions
What disk HW is it? Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Spann, Elizebeth (Betsie) Sent: Tuesday, October 07, 2008 4:32 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Kjournal questions Thank you. Unfortunately for us, the ESADS reports are for 3390s. We are using FCP-attached SCSI. Betsie -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Barton Robinson Sent: Tuesday, October 07, 2008 4:45 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Kjournal questions Check your DASD Cache statistics (ESADSD5 on ESAMAP). This kjournal problem happens when the Non-volatile storage in cache controller fills up - dasd performance gets terrible and kjournal uses more CPU. Spann, Elizebeth (Betsie) wrote: Hi, We've noticed that the kjournal process takes up almost 30% of our processing at times. When I ran mke2fs -jI let it default. Would this be a block size of 4096? Should I have used -E stride=stripe-size? If so, are there recommendations for large files? We have raid 5 and raid 1. 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 -- 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: Kjournal questions
Betsie, contact EMC and ask them why, as Barton said, the cache controller NVS is full. I've heard you are not the only one to experience this. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Spann, Elizebeth (Betsie) Sent: Wednesday, October 08, 2008 8:37 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Kjournal questions EMC DMX4-950. RH OS is on EDEVICE. Local file systems are FCP-attached SCSI. VM uses 3390 disks. Betsie -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Marcy Cortes Sent: Tuesday, October 07, 2008 10:23 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Kjournal questions What disk HW is it? Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Spann, Elizebeth (Betsie) Sent: Tuesday, October 07, 2008 4:32 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Kjournal questions Thank you. Unfortunately for us, the ESADS reports are for 3390s. We are using FCP-attached SCSI. Betsie -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Barton Robinson Sent: Tuesday, October 07, 2008 4:45 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Kjournal questions Check your DASD Cache statistics (ESADSD5 on ESAMAP). This kjournal problem happens when the Non-volatile storage in cache controller fills up - dasd performance gets terrible and kjournal uses more CPU. Spann, Elizebeth (Betsie) wrote: Hi, We've noticed that the kjournal process takes up almost 30% of our processing at times. When I ran mke2fs -jI let it default. Would this be a block size of 4096? Should I have used -E stride=stripe-size? If so, are there recommendations for large files? We have raid 5 and raid 1. 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 -- 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
FW: [LINUX-390] Change the Linux from VSWITCH to DEDICATEd OSA
-OK, I went and tried it with the sles10 sp2 rescue system image from the DVD to make sure it wasn't my guest. Same problem. I then went and tried the sles10 SP2 rescue system image from a z9 with z/VM 5.3 That worked. So, I'm sure the HW is fine (it runs the vswitch - why couldn't it run it dedicated, right?) So, it's likely z/VM 5.4, or perhaps the z10 - but I find that hard to believe since the OSA does function on vswitch. I guess I'll open a PMR. Marcy Yep, same chpid. This is on a z10, z/VM 5.4, sles 10 sp2. Maybe I should go try in on a z9, z/VM 5.3 and sles9 sp4 just for grins since it sounds like it ought to work! Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [EMAIL PROTECTED] On Behalf Of Mark Post Sent: Tuesday, October 07, 2008 3:56 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Change the Linux from VSWITCH to DEDICATEd OSA addresses On 10/7/2008 at 6:46 PM, in message Marcy Cortes [EMAIL PROTECTED] wrote: But that's got to be a big lie :) --- it is working if it is on a vswitch. Just not with dedicates. The cables are happy. The ports are happy. The physical switch is happy. Are you sure what is/was being used for the VSWITCH is on the same CHPID as the new device you're trying to use? Each card has two possible cable connections (4 with the new z10s). 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 -- 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 smime.p7s Description: S/MIME cryptographic signature
Re: IBM Tivoli Composite Application Manager for WebSphere
Yes, it does run on Linux for z. We trialed it. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Stahr, Lea Sent: Tuesday, October 14, 2008 7:08 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] IBM Tivoli Composite Application Manager for WebSphere Does anyone have IBM Tivoli Composite Application Manager for WebSphere running on zLinux or know if it will run there? The manual does not mention this environment. Lea Stahr Senior Systems Engineer Linux and zLinux Navistar, Inc. 630-753-5445 [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
Re: SuSE 10 SP 2 - New Install - Misc Questions
Welcome newbie :) 1) I've seen it too on SP2. You can just copy the file in /etc/sysconfig/hardware/ and the file in /etc/sysconfig/network files that correspond to the existing interace to appropriately named new files and edit with vi, changing the IP and chanids. With 2 interfaces, you'll have to figure out your routing, but you probably knew that already. 2) We too have a proxy server that can't see to get to Novell Customer Center. Mark Post worked with me for quite some time and was very close to figuring it all out (likely malformed request and their inbound is pickier than your average bear ) when I suddenly found another proxy server within the bank that worked just fine and I dumped him and moved on to my next challenges. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of David Stuart Sent: Tuesday, October 14, 2008 8:36 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] SuSE 10 SP 2 - New Install - Misc Questions Morning all, newbie on Yesterday I completed a new install of SLES 10 SP 2 into an LPAR. During the install, I defined one OSA-Express port, and it appears to be working fine. However, I have several networking related nuisances and questions. 1) How do you define a second OSA-Express port? I tried defining it using YAST, but the OSA-Express is running QDIO, and YAST seems to treat each individual address as a separate network card, rather than using the three required for QDIO. I chose a network type of QETH. I didn't see anything specific to QDIO, but thought QETH was probably the closest. 2) Novell Customer Center - We have a proxy between our internal network and the internet. I configured the proxy, and the 'test connection' says that it works ok, but when I try to 'register', check for patches, etc., it says that it can't connect. And that's enough for so early in the morning. /newbie on TIA, Dave Dave Stuart Prin. Info. Systems Support Analyst County of Ventura, CA 805-662-6731 [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
