FYI
LOGON LINUXFTP
z/VM Version 5 Release 2.0, Service Level 0602 (64-bit),
built on IBM Virtualization Technology
There is no logmsg data
FILES: NO RDR, NO PRT, NO PUN
RECONNECTED AT 17:02:49 PDT MONDAY 10/22/07
CMS
IND USER LINUXFTP
USERID=LINUXFTP MACH=ESA STOR=512M VIRT=V XSTORE=NONE
IPLSYS=CMS DEVNUM=00016
PAGES: RES=00000952 WS=00000931 LOCKEDREAL=00000000 RESVD=00000000
NPREF=00000000 PREF=00000000 READS=00000018 WRITES=00000008
XSTORE=000000 READS=000000 WRITES=000000 MIGRATES=000000
CPU 00: CTIME=69:17 VTIME=000:00 TTIME=000:00 IO=000599
RDR=000000 PRT=000000 PCH=000000
,
,RUNNING
BEADEV1 ,,
Thanks & Regards,
-GnanaShekar-
On 10/23/07, GnanaShekar Subramani <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> Thanks a lot for the detailed explanation.
>
> You were right, LINUXFTP was running linux. But I was unable to connect
> to it using "putty-ssh or telnet" session. I was only able to "ftp" from
> the dos prompt.
>
> Now, when I login as LINUXFTP; all it display is CMS. I guess I did
> something like a LOGOFF without being aware of the consequence.
>
> Thanks & Regards,
> -GnanaShekar-
>
> On 10/22/07, RPN01 <[EMAIL PROTECTED]> wrote:
> >
> > Thanks for the console log; The most interesting command you've shown
> > here is:
> >
> > QUERY NAMES
> >
> > LINUXFTP - DSC , PERFSVM - DSC , TCPIP - DSC , DTCVSW2 - DSC
> > DTCVSW1 - DSC , OPERSYMP - DSC , DISKACNT - DSC , EREP - DSC
> > TCPMAINT - DSC , BEADEV01 -L0003
> >
> > VSM - TCPIP
> >
> > This tells you what is logged in on your system. Of these users, most
> > can be accounted for as standard z/VM service machines. The two that are
> > not, are BEADEV01 and LINUXFTP (although this could be TCPIP's ftpserve
> > under a different name; You'd have to log into it to see if it really is
> > running Linux.)
> >
> > From the others, I'd say you have a vSwitch active (because DTCVSW1 and
> > 2 are the controllers for a vSwitch) and you have the IBM Performance
> > Toolkit (the service machine PERFSVM). I'm not sure why TCPMAINT would be
> > logged in disconnected. This isn't needed for anything. OPERSYMP, DISKACNT
> > and EREP are collectors for various information produced by z/VM. I'm
> > surprised to not see OPERATOR logged in on a terminal.
> >
> > The user you need to log into (due to the fact that it has the "keys to
> > the cabinet") is MAINT. MAINT is the equivalent to Linux's root account.
> > Since I don't see DIRMAINT running on your system, I'd assume that the
> > current CP Directory is on one of MAINT's minidisks, probably named USER
> > DIRECT. You need to be able to log into MAINT to perform even minor
> > maintenance tasks on the system. Hopefully someone has left you the
> > password.
> >
> > The reason that you immediately see a Linux logon when you log into the
> > system is that you're logging into a user that is running a Linux guest. You
> > need your own, personal userid, so that you can easily log in and issue
> > commands. Once you find the CP Directory, it should be a simple task to add
> > one for yourself.
> >
> > Key to stepping into all this mud would be to look at the CP
> > Administration and Customization manual. It describes the contents of the CP
> > Directory file and how to put it into production, and also describes the
> > SYSTEM CONFIG file, found on MAINT's CF1, 2, and 3 minidisks.
> >
> > Do lots of querys and look at the files that MAINT and TCPMAINT control.
> > Don't change anything until you understand what those changes will affect.
> >
> > Good luck, and good hunting.
> >
> > --
> > .~. 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."
> >
> >
> >
> >
> > On 10/22/07 12:53 AM, "GnanaShekar Subramani" < [EMAIL PROTECTED]>
> > wrote:
> >
> > Hi,
> >
> > Since my mail attachments have not reached you, I am pasting the details
> > below:
> >
> > LOGON BEADEV01
> > z/VM Version 5 Release 2.0, Service Level 0602 (64-bit),
> > built on IBM Virtualization Technology
> > There is no logmsg data
> > FILES: NO RDR, NO PRT, NO PUN
> > RECONNECTED AT 14:42:43 PDT SUNDAY 10/21/07
> >
> > Welcome to SUSE Linux Enterprise Server 10 (s390x) - Kernel
> > 2.6.16.21-0.8-defaul
> > t (ttyS0).
> >
> >
> > beadev01 login:
> >
> >
> >
> > ,
> >
> > ,RUNNING BEADEV1 ,,
> >
> > ------------------------------------------------------------------------------------------------------------
> > [EMAIL PROTECTED]:~> pwd
> > pwd
> > /home/beadev01
> >
> > [EMAIL PROTECTED]:~> uname -a
> > uname -a
> > Linux beadev01 2.6.16.21-0.8-default #1 SMP Mon Jul 3 18:25:39 UTC 2006
> > s390x s3
> > 90x s390x GNU/Linux
> >
> > [EMAIL PROTECTED]:~> more /etc/SuSE-release
> > more /etc/SuSE-release
> > SUSE Linux Enterprise Server 10 (s390x)
> > VERSION = 10
> >
> > [EMAIL PROTECTED] :~> free
> > free
> > total used free shared buffers
> > cached
> > Mem: 505192 239696 265496 0 73676
> > 122404
> > -/+ buffers/cache: 43616 461576
> > Swap: 348688 0 348688
> > [EMAIL PROTECTED]:~>
> >
> >
> > ,
> >
> > ,RUNNING BEADEV1 ,,
> >
> > ------------------------------------------------------------------------------------------------------------
> >
> > more /proc/cpuinfo
> > more /proc/cpuinfo
> > vendor_id : IBM/S390
> > # processors : 1
> > bogomips per cpu: 2398.61
> > processor 0: version = FF, identification = 01D48C, machine = 2084
> > [EMAIL PROTECTED]:~>
> >
> >
> > ,
> >
> > ,RUNNING BEADEV1 ,,
> >
> > ------------------------------------------------------------------------------------------------------------
> > LOGON BEADEV01
> > z/VM Version 5 Release 2.0, Service Level 0602 (64-bit),
> > built on IBM Virtualization Technology
> > There is no logmsg data
> > FILES: NO RDR, NO PRT, NO PUN
> > RECONNECTED AT 15:47:47 PDT SUNDAY 10/21/07
> >
> > QUERY NAMES
> > LINUXFTP - DSC , PERFSVM - DSC , TCPIP - DSC , DTCVSW2 - DSC
> > DTCVSW1 - DSC , OPERSYMP - DSC , DISKACNT - DSC , EREP - DSC
> > TCPMAINT - DSC , BEADEV01 -L0003
> > VSM - TCPIP
> >
> > IND USER BEADEV01
> > USERID=BEADEV01 MACH=ESA STOR=512M VIRT=V XSTORE=NONE
> > IPLSYS=DEV 0700 DEVNUM=00017
> > PAGES: RES=00073223 WS=00073210 LOCKEDREAL=00000013 RESVD=00000000
> > NPREF=00000001 PREF=00000000 READS=00000001 WRITES=00000001
> > XSTORE=000000 READS=000000 WRITES=000000 MIGRATES=000000
> > CPU 00: CTIME=42:24 VTIME=002:42 TTIME=003:30 IO=071474
> > RDR=000000 PRT=000000 PCH=000000
> >
> >
> > ,
> >
> >
> > ,RUNNING BEADEV1 ,,
> > -----------------------------------------------------------------------------------------------------------
> >
> >
> >
> > Thanks & Regards,
> > -GnanaShekar-
> >
> >
> > On 10/20/07, *Kris Buelens* < [EMAIL PROTECTED]> wrote:
> >
> > VM user and Virtual machine / guest os are indeed one and the same
> >
> > LOGOFF, that's like pulling the plug out, not an orderly shutdown. So
> > better stop your Linuxes with the appropriate Linux command and then enter
> > LOGOFF.
> >
> > At the other hand: modern Linuxes register themselves to receive
> > shutdown signals from CP, what means that if the LPAR gets stopped, of when
> > you issue CP SHUTDOWN, or when one uses FORCE, these Linuxes will shutdown
> > themselves and CP gives them some to do that. This time can be defined in
> > SYSTEM CONFIG (on MAINT CF1) or by a CP SET command; by default, the time is
> > 0 and FORCE or SHUTDOWN won't give Linuxes any time to stop.
> > To find out the details, use QUERY SIGNALS or QUERY SIGNAL SHUTDOWN (or
> > something like it, my memory isn't that good anymore to remember all details
> > of relatively new commands). HELP CPQUERY MENU is a start to find the
> > details online.
> >
> >
> >
>
