27.12.2012 Views

The Virtualization Cookbook for SLES 10 SP2 - z/VM - IBM

The Virtualization Cookbook for SLES 10 SP2 - z/VM - IBM

The Virtualization Cookbook for SLES 10 SP2 - z/VM - IBM

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

OPERATOR TCPMAINT MAINT MPROUTE ROUTED DHCPD REXECD SNMPD SNMPQE<br />

ENDOBEY<br />

; ----------------------------------------------------------------------<br />

AUTOLOG<br />

FTPSERVE 0<br />

ENDAUTOLOG<br />

PORT<br />

20 TCP FTPSERVE NOAUTOLOG ; FTP Server<br />

21 TCP FTPSERVE ; FTP Server<br />

23 TCP INTCLIEN ; TELNET Server<br />

; 25 TCP SMTP ; SMTP Server<br />

...<br />

► Save your changes with the FILE subcommand:<br />

====> file<br />

You could continue to configure the system, but at this time it is recommended that you test<br />

your changes by shutting down and reIPLing the system.<br />

4.5.4 Shutting down and reIPLing the system<br />

You may want to be able to shutdown and reIPL z/<strong>VM</strong> without having to access the HMC.<br />

Often, the HMC will be logged off and thus the Integrated 3270 console (SYSG) will not be<br />

available. Because of these factors it is useful to use the System Console (SYSC - which has a<br />

title of Operating System Messages on the HMC) in order to shut down z/<strong>VM</strong> and reIPL it<br />

without needing to use the console. This console is always accessible whether you are<br />

logged on to the HMC or not. z/<strong>VM</strong> messages during both the shutdown and reIPL process<br />

will be written to the system console, but often you will be able to ignore them - you just want<br />

your system back in a few minutes over the network.<br />

To shut down and re-IPL the system, per<strong>for</strong>m the following steps:<br />

► Pass the parameter IPLPARMS CONS=SYSC to the SHUTDOWN REPIL command:<br />

==> shutdown reipl iplparms cons=sysc<br />

You will lose your session, but it should come back in a few minutes as described above.<br />

► When your system is back up, start a 3270 session and logon as MAINT. This shows that<br />

there is TCP/IP access to z/<strong>VM</strong>.<br />

Important: If you cannot start another 3270 session, do not despair - consider this a good<br />

learning experience :)) You must go back to an Integrated 3270 session from the HMC.<br />

Verify that TCPIP is logged on. If it is logged on and you still can’t get to your system, log<br />

TCPIP off (or just re-IPL CMS), log back on, press Enter and watch the messages <strong>for</strong><br />

errors.<br />

► Query the new VSWITCH:<br />

==> q vswitch<br />

VSWITCH SYSTEM VSW1 Type: VSWITCH Connected: 0 Maxconn: INFINITE<br />

PERSISTENT RESTRICTED NONROUTER Accounting: OFF<br />

VLAN Unaware<br />

MAC address: 02-00-01-00-00-01<br />

State: Ready<br />

IPTimeout: 5 QueueStorage: 8<br />

Isolation Status: OFF<br />

RDEV: B440.P00 VDEV: B440 Controller: DTCVSW2<br />

RDEV: B424.P00 VDEV: B424 Controller: DTCVSW1 BACKUP<br />

Chapter 4. Installing and configuring z/<strong>VM</strong> 49

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!