solaris 9 student guide part 2 sa299 phần 1 docx

Advanced System Administration for the Solaris™ Operating Environment SA-299 Student Guide Sun Microsystems, Inc UBRM05-104 500 Eldorado Blvd Broomfield, CO 80021 U.S.A Revision A Copyright 2002 Sun Microsystems, Inc., 901 San Antonio Road, Palo Alto, California 94303, U.S.A All rights reserved This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any Third-party software, including font technology, is copyrighted and licensed from Sun suppliers Sun, Sun Microsystems, the Sun logo, Solaris, JumpStart, Web Start, Solstice DiskSuite, SunBlade, SunSolve, Ultra, OpenBoot, Java, Sun Ray, Java Card and iPlanet are trademarks or registered trademarks of Sun Microsystems, Inc in the U.S and other countries All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc in the U.S and other countries Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc UNIX is a registered trademark in the U.S and other countries, exclusively licensed through X/Open Company, Ltd The OPEN LOOK and Sun Graphical User Interface was developed by Sun Microsystems, Inc for its users and licensees Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written license agreements U.S Government approval might be required when exporting the product RESTRICTED RIGHTS: Use, duplication, or disclosure by the U.S Government is subject to restrictions of FAR 52.227-14(g)(2)(6/87) and FAR 52.227-19(6/87), or DFAR 252.227-7015 (b)(6/95) and DFAR 227.7202-3(a) DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS, AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID THIS MANUAL IS DESIGNED TO SUPPORT AN INSTRUCTOR-LED TRAINING (ILT) COURSE AND IS INTENDED TO BE USED FOR REFERENCE PURPOSES IN CONJUNCTION WITH THE ILT COURSE THE MANUAL IS NOT A STANDALONE TRAINING TOOL USE OF THE MANUAL FOR SELF-STUDY WITHOUT CLASS ATTENDANCE IS NOT RECOMMENDED Export Control Classification Number (ECCN): 5E992 Please Recycle Copyright 2002 Sun Microsystems Inc., 901 San Antonio Road, Palo Alto, California 94303, Etats-Unis Tous droits réservés Ce produit ou document est protégé par un copyright et distribué avec des licences qui en restreignent l’utilisation, la copie, la distribution, et la décompilation Aucune partie de ce produit ou document ne peut être reproduite sous aucune forme, par quelque moyen que ce soit, sans l’autorisation préalable et écrite de Sun et de ses bailleurs de licence, s’il y en a Le logiciel détenu par des tiers, et qui comprend la technologie relative aux polices de caractères, est protégé par un copyright et licencié par des fournisseurs de Sun Sun, Sun Microsystems, le logo Sun, Solaris, JumpStart, Web Start, Solstice DiskSuite, SunBlade, SunSolve, Ultra, OpenBoot, Java, Sun Ray, Java Card, et iPlanet sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc aux Etats-Unis et dans d’autres pays Toutes les marques SPARC sont utilisées sous licence sont des marques de fabrique ou des marques déposées de SPARC International, Inc aux Etats-Unis et dans d’autres pays Les produits portant les marques SPARC sont basés sur une architecture développée par Sun Microsystems, Inc UNIX est une marques déposée aux Etats-Unis et dans d’autres pays et licenciée exclusivement par X/Open Company, Ltd L’interfaces d’utilisation graphique OPEN LOOK et Sun™ a été développée par Sun Microsystems, Inc pour ses utilisateurs et licenciés Sun reconnt les efforts de pionniers de Xerox pour larecherche et le développement du concept des interfaces d’utilisation visuelle ou graphique pour l’industrie de l’informatique Sun détient une licence non exclusive de Xerox sur l’interface d’utilisation graphique Xerox, cette licence couvrant également les licenciés de Sun qui mettent en place l’interface d’utilisation graphique OPEN LOOK et qui en outre se conforment aux licences écrites de Sun L’accord du gouvernement américain est requis avant l’exportation du produit LA DOCUMENTATION EST FOURNIE “EN L’ETAT” ET TOUTES AUTRES CONDITIONS, DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L’APTITUDE A UNE UTILISATION PARTICULIERE OU A L’ABSENCE DE CONTREFAÇON CE MANUEL DE RÉFÉRENCE DOIT ÊTRE UTILISÉ DANS LE CADRE D'UN COURS DE FORMATION DIRIGÉ PAR UN INSTRUCTEUR (ILT) IL NE S'AGIT PAS D'UN OUTIL DE FORMATION INDÉPENDANT NOUS VOUS DÉCONSEILLONS DE L'UTILISER DANS LE CADRE D'UNE AUTO-FORMATION Please Recycle Table of Contents About This Course .Preface-xix Instructional Goals Preface-xix Course Map Preface-xx Topics Not Covered Preface-xxi How Prepared Are You? Preface-xxiii Introductions Preface-xxiv How to Use Course Materials Preface-xxv Conventions Preface-xxvi Icons Preface-xxvi Typographical Conventions Preface-xxvii Describing Interface Configuration 1-1 Objectives 1-1 Controlling and Monitoring Network Interfaces 1-2 Displaying the MAC Address 1-2 Displaying the IP Address 1-3 Marking an Ethernet Interface as Down 1-3 Sending ICMP ECHO_REQUEST Packets 1-4 Capturing and Inspecting Network Packets 1-5 Configuring IPv4 Interfaces at Boot Time 1-6 Introducing IPv4 Interface Files 1-6 Changing the System Host Name 1-9 Performing the Exercises 1-12 Exercise: The Solaris OE Network Commands (Level 1) 1-13 Preparation 1-13 Tasks 1-13 Exercise: The Solaris OE Network Commands (Level 2) 1-14 Preparation 1-14 Task Summary 1-14 Tasks 1-15 v Copyright 2002 Sun Microsystems, Inc All Rights Reserved Enterprise Services, Revision A Exercise: The Solaris OE Network Commands (Level 3) 1-17 Preparation 1-17 Task Summary 1-17 Tasks and Solutions 1-18 Exercise Summary 1-20 Describing the Client-Server Model 2-1 Objectives 2-1 Introducing Client-Server Processes 2-2 Introducing Client Processes 2-2 Introducing Server Processes 2-4 Starting Server Processes 2-6 Introducing the Internet Service Daemon (inetd) 2-6 Introducing Network Ports 2-9 Starting Services That Use a Well-Known Port 2-10 Starting RPC Services 2-13 Using the rpcinfo Commands 2-16 Performing the Exercises 2-18 Exercise: Observing the Solaris OE Network (Level 1) 2-19 Preparation 2-19 Tasks 2-19 Exercise: Observing the Solaris OE Network (Level 2) 2-20 Preparation 2-20 Task Summary 2-20 Tasks 2-21 Exercise: Observing the Solaris OE Network (Level 3) 2-24 Preparation 2-24 Task Summary 2-24 Tasks and Solutions 2-25 Exercise Summary 2-30 Customizing the Solaris™ Management Console 3-1 Objectives 3-1 Introducing the Solaris Management Console Toolbox Editor Actions 3-2 Starting the Solaris Management Console 3-2 Introducing the Solaris Management Console and the Solaris Management Console Toolbox Editor 3-4 Adding a Toolbox URL 3-17 Adding a Tool 3-17 Using the Solaris Management Console Toolbox Editor 3-19 Adding Access to a Toolbox URL of a Solaris Management Console 3-19 Adding Access to a Tool 3-36 Performing the Exercises 3-61 vi Advanced System Administration for the Solaris™ Operating Environment Copyright 2002 Sun Microsystems, Inc All Rights Reserved Enterprise Services, Revision A Exercise: Using the Solaris Management Console (Level 1) 3-62 Preparation 3-62 Task Summary 3-62 Exercise: Using the Solaris Management Console (Level 2) 3-63 Preparation 3-63 Task Summary 3-63 Tasks 3-64 Exercise: Using the Solaris Management Console (Level 3) 3-71 Preparation 3-71 Task Summary 3-71 Tasks and Solutions 3-72 Exercise Summary 3-80 Managing Swap Configuration 4-1 Objectives 4-1 Introducing Virtual Memory 4-2 Physical RAM 4-2 Swap Space 4-3 The swapfs File System 4-3 Paging 4-5 Configuring Swap Space 4-6 Displaying the Current Swap Configuration 4-6 Adding Swap Space 4-7 Removing Swap Space 4-8 Performing the Exercises 4-10 Exercise: Managing swap Utility Configuration (Level 1) 4-11 Preparation 4-11 Tasks 4-12 Exercise: Managing swap Utility Configuration (Level 2) 4-13 Preparation 4-13 Task Summary 4-14 Tasks 4-14 Exercise: Managing swap Utility Configuration (Level 3) 4-16 Preparation 4-16 Task Summary 4-17 Tasks and Solutions 4-17 Exercise Summary 4-21 vii Copyright 2002 Sun Microsystems, Inc All Rights Reserved Enterprise Services, Revision A Managing Crash Dumps and Core Files 5-1 Objectives 5-1 Managing Crash Dump Behavior 5-2 The Crash Dump 5-2 Displaying the Current Dump Configuration 5-4 Changing the Crash Dump Configuration 5-4 Managing Core File Behavior 5-6 Core Files 5-6 Displaying the Current Core File Configuration 5-7 Changing the Core File Configuration 5-8 Performing the Exercises 5-14 Exercise: Collecting the Crash Dump and Core Dump (Level 1) 5-15 Preparation 5-15 Tasks 5-15 Exercise: Collecting the Crash Dump and Core Dump (Level 2) 5-16 Preparation 5-16 Task Summary 5-16 Tasks 5-17 Exercise: Collecting the Crash Dump and Core Dump (Level 3) 5-19 Preparation 5-19 Task Summary 5-19 Tasks and Solutions 5-20 Exercise Summary 5-23 Configuring NFS 6-1 Objectives 6-1 Introducing the Benefits of NFS 6-2 Benefits of Centralized File Access 6-3 Benefits of Common Software Access 6-3 Introducing the Fundamentals of the NFS Distributed File System 6-4 NFS Server 6-5 NFS Client 6-6 Managing an NFS Server 6-7 The NFS Server Files 6-7 The NFS Server Daemons 6-10 Managing the NFS Server Daemons 6-12 NFS Server Commands 6-13 Configuringthe NFS Server for Sharing Resources 6-14 Managing the NFS Client 6-20 NFS Client Files 6-20 NFS Client Daemons 6-21 Managing the NFS Client Daemons 6-22 viii Advanced System Administration for the Solaris™ Operating Environment Copyright 2002 Sun Microsystems, Inc All Rights Reserved Enterprise Services, Revision A NFS Client Commands 6-23 Configuring the NFS Client for Mounting Resources 6-23 Enabling the NFS Server Logging 6-28 Fundamentals of NFS Server Logging 6-28 Configuring NFS Log Paths 6-29 Initiating NFS Logging 6-31 Configuring the nfslogd Daemon Behavior 6-32 Managing NFS With the Solaris Management Console Storage Folder Tools 6-33 Adding a Shared Directory on the NFS Server 6-33 Mounting a Shared Directory on the NFS Client 6-35 Troubleshooting NFS Errors 6-37 The rpcbind failure Error 6-37 The server not responding Error 6-38 The NFS client fails a reboot Error 6-38 The service not responding Error 6-39 The program not registered Error 6-39 The stale NFS file handle Error 6-40 The unknown host Error 6-40 The mount point Error 6-40 The no such file Error 6-41 Performing the Exercises 6-42 Exercise: Configuring NFS (Level 1) 6-43 Preparation 6-43 Tasks 6-43 Exercise: Configuring NFS (Level 2) 6-45 Preparation 6-45 Task Summary 6-45 Tasks 6-46 Exercise: Configuring NFS (Level 3) 6-49 Preparation 6-49 Task Summary 6-49 Tasks and Solutions 6-50 Exercise Summary 6-54 Configuring AutoFS 7-1 Objectives 7-1 Introducing the Fundamentals of AutoFS 7-2 AutoFS File System 7-3 The automountd Daemon 7-4 The automount Command 7-4 Using Automount Maps 7-5 Configuring the Master Map 7-6 Identifying Mount Points for Special Maps 7-8 Adding Direct Map Entries 7-9 Adding Indirect Map Entries 7-11 ix Copyright 2002 Sun Microsystems, Inc All Rights Reserved Enterprise Services, Revision A Updating the Automount Maps 7-14 Stopping and Starting the Automount System 7-16 Performing the Exercises 7-18 Exercise: Using the Automount Facility (Level 1) 7-19 Preparation 7-19 Tasks 7-19 Exercise: Using the Automount Facility (Level 2) 7-20 Preparation 7-20 Task Summary 7-20 Tasks 7-21 Exercise: Using the Automount Facility (Level 3) 7-25 Preparation 7-25 Task Summary 7-25 Tasks and Solutions 7-26 Exercise Summary 7-31 Describing RAID and the Solaris™ Volume Manager Software 8-1 Objectives 8-1 Introducing RAID 8-2 RAID 8-2 RAID 8-7 RAID 8-13 Hardware Considerations 8-16 Introducing Solaris Volume Manager Software Concepts 8-20 Logical Volume 8-20 Soft Partitions 8-22 Introducing the State Database 8-23 Introducing Hot Spares and Hot Spare Pools 8-26 Configuring Solaris Volume Manager Software 9-1 Objectives 9-1 Distributing the State Database Replicas 9-2 Creating the State Database 9-2 Building a Mirror of the Root (/) File System 9-13 Creating a RAID Volume 9-14 Creating a RAID-1 Volume 9-27 Executing the metaroot Command 9-40 Updating the boot-device PROM Variable 9-41 Unmirroring the root (/) File System 9-43 Performing the Exercises 9-45 Exercise: Mirroring the root (/) File System (Level 1) 9-46 Preparation 9-46 Tasks 9-47 x Advanced System Administration for the Solaris™ Operating Environment Copyright 2002 Sun Microsystems, Inc All Rights Reserved Enterprise Services, Revision A Exercise: Observing the Solaris OE Network (Level 3) Exercise: Observing the Solaris OE Network (Level 3) In this exercise, you use basic, network-related commands to observe the inetd daemon and the rpcbind services Preparation To prepare for this exercise, perform the following tasks: q Check that you have two systems listed in the /etc/hosts file on each system q Eliminate entries for the root user in /etc/ftpd/ftpusers file to ensure that the root user is not restricted from using the FTP service on both systems q Work with a partner for this exercise, and perform all steps on both systems, unless noted otherwise Task Summary Perform the following tasks: q q Check that the FTP application is listed in the /etc/inetd.conf file and the /etc/services file Record the name of the FTP server daemon On both systems, check if the FTP application or server daemon is running Use one system as the FTP client and the other as the FTP server Establish an FTP connection, and check again for ftp command-related applications and daemons Record your observations Terminate your FTP connection q 2-24 Monitor the network traffic throughout the exercise Check the port number assigned to the rpcbind service to make sure that it is a well-known port Record the port number Check and record the port number and program number assigned to the sprayd daemon Check that your partner’s system can contact your system using the sprayd daemon Unregister the sprayd service Check that the service has unregistered Advanced System Administration for the Solaris™ Operating Environment Copyright 2002 Sun Microsystems, Inc All Rights Reserved Enterprise Services, Revision A Exercise: Observing the Solaris OE Network (Level 3) q Check that the sprayd daemon does not function from your partner’s system to your system Send the HUP signal to the inetd daemon, and check that the sprayd service is again a registered service, and that the sprayd service functions correctly between the two systems Check the new port number assigned to the sprayd service and the program number that it uses Tasks and Solutions This section describes the tasks for you to perform and lists the solutions Task – Interaction Between the inetd Daemon and the FTP Application You must use two additional windows on the FTP client host for this section of the exercise Complete the following steps: In a dedicated terminal window, open a snoop session between the two hosts used during this exercise This snoop session should remain active throughout this exercise # snoop host1 host2 Display the entry for the FTP application in the /etc/inetd.conf file, and record the name of the server daemon that is listed # grep ftp /etc/inetd.conf # ftp telnet shell login exec tftp finger printer # TFTPD - tftp server (primarily used for booting) #tftp dgram udp6 wait root /usr/sbin/in.tftpd /tftpboot ftp stream tcp6 nowait root /usr/sbin/in.ftpd in.tftpd -s in.ftpd -a in.ftpd Check that the FTP application is a service with a well-known port listed in the /etc/services file # grep ftp /etc/services ftp-data 20/tcp ftp 21/tcp tftp 69/udp Is it listed? Yes It uses port 21 Describing the Client-Server Model Copyright 2002 Sun Microsystems, Inc All Rights Reserved Enterprise Services, Revision A 2-25 Exercise: Observing the Solaris OE Network (Level 3) Use the pgrep command to check if the ftp daemon is currently running # pgrep -xl ftpd # Is it running? No It should not be running yet Note – Determine which system acts as the FTP client and which acts as the FTP server On the FTP client, in one window, establish an FTP connection to the FTP server # ftp host Connected to host 220 host FTP server ready Name (host:root): 331 Password required for root Password:xxxxxxx 230 User root logged in Remote system type is UNIX Using binary mode to transfer files ftp> On the FTP client in another window, check for daemons or applications related to the FTP service # pgrep -l ftp nnn ftp What does the pgrep command display? The pgrep command should list the FTP application if the system is acting as an FTP client On the FTP server, in an available window, check for daemons and applications related to the FTP service # pgrep -l ftp nnnn in.ftpd What does the pgrep command display? The pgrep command should list the in.ftpd daemon if the system is acting as an FTP server 2-26 Advanced System Administration for the Solaris™ Operating Environment Copyright 2002 Sun Microsystems, Inc All Rights Reserved Enterprise Services, Revision A Exercise: Observing the Solaris OE Network (Level 3) On the FTP client, terminate your FTP connection to the server On both the FTP server and FTP client, check for FTP-related daemons and applications ftp> bye # pgrep -l ftp What does the pgrep command report? Nothing Both the FTP application and FTP server daemon have terminated 10 Observe the output from the snoop utility on both systems What FTP-related login information does the snoop command display? The login name and password in clear text 11 Change the client-server roles of the two systems, and repeat Step through Step Task – The rpcbind Service Operations Complete the following steps: Use the rpcinfo command to display information for the rpcbind process # rpcinfo -p |grep rpcbind 100000 tcp 111 100000 tcp 111 100000 tcp 111 100000 udp 111 100000 udp 111 100000 udp 111 rpcbind rpcbind rpcbind rpcbind rpcbind rpcbind Which port number does the rpcbind process use? 111 Which protocols does the rpcbind process use? Both TCP and UDP Check that the rpcbind service is listed in the /etc/services file, and that the listed port number matches the output from the rpcinfo command in Step # grep rpcbind /etc/services sunrpc 111/udp sunrpc 111/tcp rpcbind rpcbind Does it? Yes Describing the Client-Server Model Copyright 2002 Sun Microsystems, Inc All Rights Reserved Enterprise Services, Revision A 2-27 Exercise: Observing the Solaris OE Network (Level 3) Use the rpcinfo command to display information for the sprayd service # rpcinfo -p |grep sprayd 100012 udp 32777 sprayd Which port number is the sprayd service using? It varies among different systems Which program number is the sprayd service using? 100012 Check the /etc/services file to determine if the sprayd service has been assigned a well-known port number # grep sprayd /etc/services # Has it? No Check the /etc/rpc file to see if the sprayd service is listed # grep sprayd /etc/rpc sprayd 100012 spray Is it listed? Yes Check that your system will respond to the sprayd service requests Have your partner run the spray command, and specify your system as the target Use the rpcinfo command to unregister the sprayd service’s port number Check that the sprayd service is no longer listed as a registered port number # spray host1 # rpcinfo -d sprayd # rpcinfo -p | grep sprayd Have your partner run the spray command, and specify your system as the target again What message does the spray command return? # spray host spray: cannot clnt_create host:netpath: RPC: Program not registered Send the HUP signal to the inetd daemon for the rpcbind service to register all services listed in its configuration file # pkill -HUP inetd 2-28 Advanced System Administration for the Solaris™ Operating Environment Copyright 2002 Sun Microsystems, Inc All Rights Reserved Enterprise Services, Revision A Exercise: Observing the Solaris OE Network (Level 3) 10 Verify that the sprayd service is listed as a registered service # rpcinfo -p | grep sprayd 100012 udp 32841 sprayd What port number is the sprayd service using now? It varies among different systems Is the program number used by the sprayd service the same as the program number that was listed in Step 3? 100012 11 To check that the sprayd service can now contact your system, have your partner run the spray command, and specify your system as the target # spray host 12 Stop the snoop processes running on both systems Press Control-C Describing the Client-Server Model Copyright 2002 Sun Microsystems, Inc All Rights Reserved Enterprise Services, Revision A 2-29 Exercise Summary Exercise Summary ! ? Discussion – Take a few minutes to discuss the experiences, issues, or discoveries that you had during the lab exercises Experiences q Interpretations q Conclusions q 2-30 q Applications Advanced System Administration for the Solaris™ Operating Environment Copyright 2002 Sun Microsystems, Inc All Rights Reserved Enterprise Services, Revision A Module Customizing the Solaris™ Management Console Objectives The Solaris™ Management Console uses a graphical user interface (GUI) to display management tools that are stored in containers referred to as toolboxes The console includes a default toolbox containing tools for managing users, projects, and cron jobs The toolbox also contains tools for mounting and sharing file systems and for managing disks and serial ports The Solaris Management Console toolbox editor application, which looks similar to the console, can add and modify toolboxes, add tools to a toolbox, and extend the functionality of a toolbox to other applications Upon completion of this module, you should be able to: q Describe the Solaris Management Console toolbox editor actions q Use the Solaris Management Console toolbox editor The following course map shows how this module fits into the current instructional goal Describing Network Basics Describing Describing the Interface Client-Server Configuration Model Figure 3-1 Customizing the Solaris™ Management Console Course Map 3-1 Copyright 2002 Sun Microsystems, Inc All Rights Reserved Enterprise Services, Revision A Introducing the Solaris Management Console Toolbox Editor Actions Introducing the Solaris Management Console Toolbox Editor Actions This section describes how to start the Solaris Management Console components and how to edit a toolbox to increase functionality with access to other Solaris Management Console servers or to legacy applications Starting the Solaris Management Console The Solaris Management Console has three primary components: q The Solaris Management Console server q The console q The Solaris Management Console toolbox editor Starting the Solaris Management Console Server If you have trouble starting the Solaris Management Console, it might be because the Solaris Management Console server is not running or because it is somehow in a problem state Note – Open a system console window to view Solaris Management Console load messages To determine if the Solaris Management Console server is running, as root perform the command: # /etc/init.d/init.wbem status If the Solaris Management Console server is running, you see a response similar to the following: Solaris Management Console server version 2.1.0 running on port 898 To stop the Solaris Management Console server, perform the command: # /etc/init.d/init.wbem stop The following message appears: Shutting down Solaris Management Console server on port 898 3-2 Advanced System Administration for the Solaris™ Operating Environment Copyright 2002 Sun Microsystems, Inc All Rights Reserved Enterprise Services, Revision A Introducing the Solaris Management Console Toolbox Editor Actions To start the Solaris Management Console server, perform the command: # /etc/init.d/init.wbem start After a short time the following message appears: Starting Solaris Management Console server version 2.1.0 endpoint created: :898 Solaris Management Console server is ready Note – For more information, visit http://www.dmtf.org Starting the Console You can start the console from the command line from the Tools menu of the CDE front panel, or by double-clicking a Solaris Management Console icon in the Applications Manager or in the File Manager To start the console from the command line, perform the command: # smc Note – You can start Solaris Management Console as a regular user, but some tools and applications might not load unless you log in to the Solaris Management Console server as root, or unless you assume a role-based access control (RBAC) role during Solaris Management Console server login Starting the Toolbox Editor To start the Solaris Management Console toolbox editor, perform the command: # smc edit You can start the Solaris Management Console toolbox editor as a normal user, but you cannot save a server toolbox unless you log in as root Customizing the Solaris™ Management Console Copyright 2002 Sun Microsystems, Inc All Rights Reserved Enterprise Services, Revision A 3-3 Introducing the Solaris Management Console Toolbox Editor Actions Caution – In this module, you modify the contents of the Solaris Management Console’s toolboxes This module directs you to alter and save both the Management Tool (root) toolbox and the This Computer (default) toolbox Before you modify either toolbox, create backups of both toolboxes using the following commands: # cd /var/sadm/smc/toolboxes # cp smc/smc.tbx smc.tbx.orig # cp this_computer/this_computer.tbx this_computer.tbx.orig Introducing the Solaris Management Console and the Solaris Management Console Toolbox Editor The Solaris Management Console contains a hierarchical collection of folders, tools, legacy applications, and links to other toolboxes A toolbox can include links to other toolboxes, individual tools, folders, and legacy applications q q The root toolbox, or container, is called Management Tools The default behavior of the Management Tools is to look for a toolbox on the local host and link to it when the Solaris Management Console starts You can add multiple toolboxes to Management Tools q A toolbox Universal Resource Locator (URL), or link, is a pointer to another toolbox that might be on the current Solaris Management Console server or on any other Solaris Management Console server q A tool is an application or applet that is compatible with the Solaris Management Console that integrates easily into the Console A Solaris Management Console tool is built using the Solaris Management Console software development kit (SDK) q A folder is a container that groups tools within a toolbox q 3-4 A Solaris Management Console toolbox is a collection of tools that have been registered using the smcregister utility A legacy application is an application that is not a Solaris Management Console tool A legacy application can be a command, X Application, or a URL Advanced System Administration for the Solaris™ Operating Environment Copyright 2002 Sun Microsystems, Inc All Rights Reserved Enterprise Services, Revision A Introducing the Solaris Management Console Toolbox Editor Actions The root toolbox URL is: http://hostname:898/toolboxes/smc.tbx The default location for this toolbox on the system is: /var/sadm/smc/toolboxes/smc/smc.tbx The root toolbox is loaded by default when either the smc or smc edit commands are run on a server This toolbox only allows access to other toolboxes, not to the tools within those toolboxes You access the actual default tools through the URL: http://hostname:898/toolboxes/this_computer.tbx The default location for this toolbox on the system is: /var/sadm/smc/toolboxes/this_computer/this_computer.tbx Customizing the Solaris™ Management Console Copyright 2002 Sun Microsystems, Inc All Rights Reserved Enterprise Services, Revision A 3-5 Introducing the Solaris Management Console Toolbox Editor Actions Introducing the Solaris Management Console To start the Solaris Management Console, perform the command: # smc & The Solaris Management Console window appears, as shown in Figure 3-2 Figure 3-2 3-6 Solaris Management Console 2.1 Window Advanced System Administration for the Solaris™ Operating Environment Copyright 2002 Sun Microsystems, Inc All Rights Reserved Enterprise Services, Revision A Introducing the Solaris Management Console Toolbox Editor Actions When you select a toolbox in the Navigation pane, as shown in Figure 3-3, the set of tools in that toolbox are displayed in the View pane You can double-click a tool in the View pane to open the next layer within the toolbox hierarchy Figure 3-3 This Computer Toolbox Window A toolbox allows for the grouping of tools into a consistent, user-friendly hierarchy The default toolbox for a Solaris Management Console server is called This Computer Table 3-1 describes the categories (or folders) and tools included in the default toolbox Table 3-1 Solaris Management Console Categories Category Includes System Status Processes, Log Viewer, System Information, and Performance System Configuration Users, Projects, Computers and Networks, and Patches Services Scheduled Jobs Storage Disks, Mounts and Shares, and Enhanced Storage Tool Devices and Hardware Serial Ports Terminal Terminal is not a category Clicking the Terminal icon launches a terminal window Customizing the Solaris™ Management Console Copyright 2002 Sun Microsystems, Inc All Rights Reserved Enterprise Services, Revision A 3-7 Introducing the Solaris Management Console Toolbox Editor Actions Double-click a specific folder to view the contents of that folder category The tools that are stored within the folder are displayed in the View pane, as shown in Figure 3-4 Figure 3-4 System Status Window Double-click on a specific tool to launch that tool 3-8 Advanced System Administration for the Solaris™ Operating Environment Copyright 2002 Sun Microsystems, Inc All Rights Reserved Enterprise Services, Revision A ... U.S Government is subject to restrictions of FAR 52. 227 -14 (g) (2) (6/87) and FAR 52. 227 - 19 ( 6/87), or DFAR 25 2 .22 7-7 015 (b)(6 /95 ) and DFAR 22 7. 720 2-3(a) DOCUMENTATION IS PROVIDED “AS IS” AND ALL... Access Control (RBAC) 11 -1 Objectives 11 -1 Introducing RBAC Fundamentals 11 -2 Roles 11 -2 Rights Profiles 11 -2 Authorizations 11 -4 Administrator Profile... 11 -23 Managing RBAC Using the Command Line 11 -57 Performing the Exercises 11 - 61 Exercise: Configuring RBAC (Level 1) 11 - 62 Preparation 11 - 62 Task Summary 11 -62