• No results found

Multiuser mode

In document AN143XSTUDHINT (Page 52-56)

Exercise instructions with hints Preface

Part 1: Multiuser mode

__ 1. Log in to your assigned LPAR as the root user.

__ 2. View the /etc/inittab file. Take a moment to become familiar with its contents. What is the run level of init? _______ 2

What does it mean? ___________________________________ This sets the default run level. Run level 2 represents AIX multi-user mode.

» # more /etc/inittab

__ 3. Using the PID of the SRC master process, produce a process tree listing of all the subsystems and subservers running on the system.

» Following are suggested commands: # ps -ef |grep srcmstr

# ps -T <pid of the srcmstr process> __ 4. List all subsystems running on the system. »# lssrc -a | more

__ 5. List all subsystems that are part of the TCP/IP group. »# lssrc -g tcpip

EXempty __ 6. Determine if the tftpd process is currently active. Edit the /etc/inetd.conf file. If the tftp service is commented out, uncomment it and if the tftp service is not

commented out, then comment it out. Refresh the inetd subsystem. Confirm the state of the tftpd process is affected by the change.

» Following are suggested commands:

# ps -T <pid of the srcmstr process> |grep tftp # vi /etc/inetd.conf

/tftp

» Either add or remove the comment symbol in column 1.

#tftp dgram udp6 SRC nobody /usr/sbin/tftpd tftpd -n » Save and exit the file.

» Refresh inetd and examine resulting process tree: # refresh -s inetd

# ps -T <pid of the srcmstr process> |grep tftp

» The tftp service is normally defined as a subserver to the inetd subsystem. Any ftpd daemons should have inetd as their parent process. You should see an ftpd daemon as a inetd child process only if the inetd.conf configuration file has it as an effective definition.

Note

Preparation for single user mode

Shutting a system down to single user mode removes the TCP/IP network configuration. Because of this, you need to log in to the system using a virtual console session, while performing the rest of the lab steps. To start a virtual console session, you must first log in directly to the HMC and then open a console session to your assigned LPAR (as completed in Exercise 1).

In the following steps, you can choose between using the HMC command line interface or the HMC browser based graphical interface. Hints are provided for both options.

__ 7. Using a separate command line window, log in to the HMC as an admin user. Your instructor will provide you with the following information:

Managed system name: _________________________ HMC name/IP address: __________________________ HMC admin user: ______________________________ HMC admin password: __________________________

__ 8. Connect to your assigned HMC and log in using your assigned administrative user name.

» If using the command line interface:

- Establish an interactive ssh session to the HMC (if you do not already have one) and log in with your assigned administrative user name.

» If using the graphic interface:

- Start your browser (Firefox if using the e-lab environment) and type in the URL: https://<IP address of assigned HMC>

- At the resulting web page, click the Log on and launch the Hardware

Management Console web application link.

- On the next window to pop-up, enter your assigned HMC admin login user and password. If presented with an option to reconnect to an existing disconnected session, click the New Session button to create a new session.

__ 9. Open a virtual terminal for your assigned LPAR. » If using the command line interface:

- From the HMC, use the vtmenu command to open a virtual terminal for your assigned LPAR.

- When presented with the Managed Systems list, enter the number for your server.

When presented with the Partitions list, enter the number for your assigned LPAR.

Note

Only one console terminal at a time can be open to a given LPAR. If you get an error that a terminal session is already open, first check to be sure you did not try to access another student’s LPAR.

If there is a terminal session is still active to your LPAR, for which you do not have a window on your workstation, type:

~> rmvterm -m <managed system> -p <your assigned LPAR> and then repeat your attempt to open a new session.

x

» If using the graphic interface:

- In the Navigation area (on the left), expand the Systems Management item and then expand the Servers item. Click the name of your assigned system. In the Content area, you will see the defined LPARs listed.

- Select your assigned LPAR so there is a check mark in the box. When the small chevron icon appears to the right of the LPAR name, click that icon. This will display a menu. We will call this the task menu.

EXempty - Select the Console Window item from the task menu and then click the Open

Terminal Window sub-menu item. A virtual terminal emulation window should be

started, as a result.

» Note: The terminal emulation window might be hidden behind existing windows).

Note

Only one console terminal at a time can be open to a given LPAR. If you get an error that a terminal session is already open, first check to be sure you did not try to access another student’s LPAR.

If there is a terminal session is still active to your LPAR, for which you do not have a window on your workstation:

In the task menu for your LPAR, click the Select the Console Window menu item. Then click the Close Terminal Window sub-menu item.

Then repeat your attempt to open a new session.

x

__ 10. Log in to the LPAR as the root user and shutdown the system into single user mode.

»# shutdown -Fm

» You will see several messages appear. Enter the root password when you see the following:

INIT: Single-User Mode PASSWORD:

__ 11. Verify that the SRC subsystems have been stopped. »# lssrc -a

__ 12. Verify that there are few processes running on the system. »# ps -ef

__ 13. Reset the run level back to multi-user mode, log back in as root, and run /etc/rc.net to configure and start the network interfaces.

»# telinit 2 »# /etc/rc.net

__ 14. Use the bootlist command to display the boot device used during a normal boot operation.

»# bootlist -m normal -o

In document AN143XSTUDHINT (Page 52-56)