Hi Guys, It looks like sometime in September I'm going to get to offer the beta exams for LPI's Level 2 (Sr Sysadmin) certification on-site (in Fairview/O'Fallon and Carbondale, as well as Springfield and St Louis). While the exams are beta, the results are final (meaning if you pass, you pass as if it were the final exam). I'm going to be trying for 200 qualified individuals to take part in this beta exam, and I'd like for 50 of them to be from our local areas. Likely the exam will carry a small fee of $10 (give or take, though this isn't final) which will be considerably less expensive than the $100-$125 to take once the exam is finally published. I have attached the Level 2 Objectives that are going to be covered with LPI's Level 2 exams. If you think you'll be interested, could you let me know? I want to get a good idea of interest before I pursue finishing this program. Please email me direct. -Kara -- Kara Pritchard Phone: 618-398-7360 Author, RHCE Exam Cram Director of Exam Development http://www.lpi.org/ Site Manager http://www.LinuxUsersGroups.org/ --Title: Preliminary Objectives - Draft Review #2
To become involved with our development, please visit http://www.lpi.org/ and join our LPI Exam Development mailing list (email listar@lpi.org with "subscribe lpi-examdev" in the SUBJECT: field. Else, if you wish to simply comment on our current objectives and provide clarification please email kara@lpi.org. We appreciate your participation! For any questions, comments, or other requests regarding LPI development, please contact Kara Pritchard via email or telephone (618)398-7360. Kernel ObjectivesObjective ID #: 2.5.1 Kernel ComponentsIncludes tasks 2.3.4 2.3.5 2.3.14 Candidates should be able to utilize kernel components that are necessary to specific hardware, hardware drivers, system resources and requirements. This objective includes implementing different types of kernel images, identifying stable and development kernels and patches, as well as using kernel modules.
Objective ID #: 2.5.2 Compiling a KernelIncludes tasks 2.2.1 2.2.2 2.2.7 2.2.11 2.2.12 2.2.13 2.3.9 Candidates should be able to properly compile a kernel to include or disable specific features of the Linux kernel as necessary. This objective includes compiling and recompiling the Linux kernel as needed, implementing updates and noting changes in a new kernel, creating a system initrd image, and installing new kernels.
Objective ID #: 2.5.3 Patching a KernelIncludes tasks 2.2.5 2.2.8 2.2.9 2.2.10 2.2.15 Candidates should be able to properly patch a kernel for various purposes including to implement kernel updates, to implement bug fixes, and to add support for new hardware. This objective also includes being able to properly remove kernel patches from existing production kernels.
Objective ID # 2.5.4: Customizing a KernelIncludes task IDs 2.3.8 2.4.1 2.4.2 2.4.3 2.4.5 2.4.7 2.4.8 2.4.10 2.5.3 2.5.4 2.5.7 2.5.8 2.5.9 2.5.10 Candidates should be able to customize a kernel for specific system requirements by patching, compiling, and editing configuration files as required. This objective includes being able to assess requirements for a kernel compile versus a kernel patch as well as build and configure kernel modules.
Objective ID 2.5.5: Debugging a Kernel CompileIncludes task IDs 2.3.13 Candidates should be able to debug Linux kernel compiling problems. This objective includes reviewing error logs and kernel configuration files to aid in debugging.
System Startup ObjectivesObjective ID 2.10.1: Customizing System Startup and Boot ProcessesIncludes task IDs 1.4.1 1.4.2 2.2.11 2.3.3 Candidates should be able to edit appropriate system startup scripts to customize standard system run levels and boot processes. This objective includes interacting with run levels and creating custom initrd images as needed.
Objective ID 2.10.2: System RecoveryIncludes task IDs 1.4.6 1.4.7 Candidates should be able to properly manipulate a Linux system during both the boot process and during recovery mode. This objective includes using both the init utility and init= kernel options.
Filesystem ObjectivesObjective ID 2.2.1: Operating the Linux FilesystemIncludes task IDs 1.2.9 1.3.8 Candidates should be able to properly configure and navigate the standard Linux filesystem. This objective includes configuring and mounting various filesystem types. Also included, is manipulating filesystems to adjust for disk space requirements or device additions.
Objective ID 2.2.2: Maintaining a Linux FilesystemIncludes task IDs 1.2.5 Candidates should be able to properly maintain a Linux filesystem using system utilities. This objective includes manipulating a standards ext2 filesystem.
Objective ID 2.2.3: Creating and Configuring Filesystem OptionsIncludes task IDs 1.2.10 1.3.10 Candidates should be able to configure automount filesystems. This objective includes configuring automount for network and device filesystems. Also included is creating non ext2 filesystems for devices such as CD-ROMs.
Hardware ObjectivesObjective ID 2.4.1: Configuring RAIDIncludes task IDs 4.1.1 4.1.2 Candidates should be able to configure and implement software RAID. This objective includes using mkraid tools and configuring RAID 0, 1, and 5.
Objective ID 2.4.2: Adding New HardwareIncludes task IDs 4.2.1 4.3.2 4.3.3 4.4.5 Candidates should be able to configure internal and external devices for a system including new hard disks, dumb terminal devices, serial UPS devices, multi-port serial cards, and LCD panels.
Objective ID 2.4.3: Software and Kernel ConfigurationIncludes task IDs 4.2.2 4.2.3 4.6.3 4.11.1 4.11.2 4.11.3 Candidates should be able to configure kernel options to support various hardware devices including UDMA66 drives and IDE CD burners. This objective includes using LVM (Logical Volume Manager) to manage hard disk drives and particitions as well as software tools to interact with hard disk settings.
Objective ID 2.4.4: Configuring PCMCIA DevicesIncludes task IDs 4.8.1 4.8.2 Candidates should be able to configure a Linux installation to include PCMCIA support. This objective includes configuring PCMCIA devices, such as ethernet adapters, to autodetect when inserted.
Networking ObjectivesObjective ID 2.8.1: Basic Networking ConfigurationIncludes task IDs 3.2.3 3.4.6 3.5.1 3.10.4 3.10.5 3.10.12 3.10.13 3.10.14 3.15.3 3.17.5 The candidate should be able to configure a network device to be able to connect to a local network and a wide-area network. This objective includes being able to communicate between various subnets within a single network, configure dialup access using mgetty, configure dialup acccess using a modem or ISDN, configure authentication protocols such as PAP and CHAP, and configure TCP/IP logging.
Objective ID 2.8.2: Advanced Network Configuration and TroubleshootingIncludes task IDs 3.10.3 3.11.4 3.16.7 3.16.9 3.17.4 4.10.2 5.2.1 5.2.12 The candidate should be able to configure a network device to implement various network authentication schemes. This objective includes configuring a multi- homed network device, configuring a virtual private network and resolving networking and communication problems.
Mail and News ObjectivesObjective ID 2.6.1: Configuring Mailing ListsIncludes task IDs 1.2.13 Install and maintain mailing lists using majordomo. Monitor majordomo problems by viewing majordomo logs.
Objective ID 2.6.2: Using SendmailIncludes task IDs 1.2.14, 1.5.3, 3.9.1, 3.9.3, 3.9.4, 3.9.5, 3.9.6, 3.9.7, 3.9.9, 3.9.10 Candidates should be able to manage a Sendmail configuration including email aliases, mail quotas, and virtual mail domains. This objective includes configuring internal mail relays and monitoring SMTP servers.
Objective ID 2.6.3: Managing Mail TrafficIncludes task IDs 1.3.12 Candidates shold be able to implement client mail management software to filter, sort, and monitor incoming user mail. This objective includes using software such as procmail on both server and client side.
Objective ID 2.6.4: Serving NewsIncludes task IDs 3.8.2 Candidates should be able to install and configure news servers using inn. This objective includes customizing and monitoring served newsgroups.
DNS ObjectivesObjective ID 2.1.1: Basic BIND 8 ConfigurationIncludes task IDs 3.1.7 3.1.12 3.1.16 3.1.17 3.1.18 The candidate should be able to configure BIND to function as a caching-only DNS server. This objective includes the ability to convert a BIND 4.9 named.boot file to the BIND 8.x named.conf format, and reload the DNS by using kill or ndc. This objective also includes configuring logging and options such as directoryh location for zone files.
Objective ID 2.1.2: Create and Maintain DNS ZonesIncludes task IDs 3.1.2 3.1.3 3.1.6 3.1.8 3.1.9 3.1.10 3.1.14 3.1.15 The candidate should be able to create a zone file for a forward or reverse zone or root level server. This objective includes setting appropriate values for the SOA resource record, NS records, and MX records. Also included is adding hosts with A resource records and CNAME records as appropriate, adding hosts to reverse zones with PTR records, and adding the zone to the /etc/named.conf file using the zone statement with appropriate type, file and masters values. A candidate should also be able to delegate a zone to another DNS server.
Objective ID 2.1.3: Securing a DNS ServerIncludes task IDs 3.1.1 3.1.4 3.1.5 3.1.13 3.1.19 The candidate should be able to configure BIND to run as a non-root user, and configure BIND to run in a chroot jail. This objective includes configuring DNSSEC statements such as key and trusted-keys to prevent domain spoofing. Also included is the ability to configure a split DNS configuration using the forwarders statement, and specifying a non-standard version number string in response to queries.
Web Services ObjectivesObjective ID 2.14.1: Implementing a Web ServerIncludes task IDs 3.6.1 3.6.2 3.6.3 3.6.4 3.6.6 3.6.7 3.6.13 3.6.14 3.6.15 3.6.16 Candidates should be able to install and configure an Apache web server. This objective includes monitoring Apache load and performance, restricting client user access, configuring mod_perl and PHP support, and setting up client user authentication. Also included is configuring Apache server options such as maximum requests, minimum and maximim servers, and clients.
Objective ID 2.14.2: Maintaining a Web ServerIncludes task IDs 3.6.10 3.6.11 3.6.12 3.6.17 Candidates should be able to configure Apache to use virtual hosts for websites without dedicated IP addresses. This objective also includes creating an SSL certification for Apache and defining SSL definitions in configuration files using OpenSSL. Also included is customizing file access by implementing redirect statements in Apache's configuration files.
Objective ID 2.14.3: Implementing a Proxy ServerIncludes task IDs 3.19.1 3.19.2 3.19.3 Candidates should be able to install and configure a proxy server using Squid. This objective includes impelementing access policies, setting up authentication, and utilizing memory usage.
File and Service Sharing ObjectivesObjective ID 2.3.1: Configuring a Samba ServerIncludes task IDs 3.12.2 3.12.3 3.12.4 3.12.5 3.12.7 3.12.6 3.12.9 The candidate should be able to set up a Samba server for various clients. This objective includes setting up a login script for Samba clients, and setting up an nmbd WINS server. Also included is to change the workgroup in which a server participates, define a shared directory in smb.conf, define a shared printer in smb.conf, use nmblookup to test WINS server functionality, and use the smbmount command to mount an SMB share on a Linux client.
Objective ID 2.3.2: Configuring an NFS ServerIncludes task IDs 3.14.6 3.14.2 3.14.8 3.14.4 3.14.9 3.14.10 3.14.11 3.14.5 The candidate should be able to create an exports file and specify filesystems to be exported. This objective includes editing exports file entries to restrict access to certain hosts, subnets or netgroups. Also included is to specify mount options in the exports file, configure user ID mapping, mount an NFS filesystem on a client, using mount options to specify soft or hard and background retries, signal handling, locking, and block size. The candidate should also be able to configure tcpwrappers to further secure NFS.
Network Client Management ObjectivesObjective ID 2.7.1: DHCP ConfigurationIncludes task IDs 3.13.1 3.13.2 3.13.3 3.13.4 3.13.5 3.13.6 The candidate should be able to configure a DHCP server and set default options, create a subnet, and create a dynamically-allocated range. This objective includes adding a static host, setting options for a single host, and adding bootp hosts. Also included is to configure a DHCP relay agent, and reload the DHCP server after making changes.
Objective ID 2.7.2: NIS ConfigurationIncludes task IDs 3.11.1 3.11.2 3.11.3 3.11.4 3.11.5 The candidate should be able to configure an NIS server and create NIS maps for major configuration files. This objective includes configuring a system as a NIS client, setting up an NIS slave server, and configuring ability to search local files, DNS, NIS, etc. in nsswitch.conf.
Objective ID 2.7.3: LDAP ConfigurationIncludes task IDs 3.18.3 3.18.5 3.18.6 3.18.7 The candidate should be able to configure an LDAP server. This objective includes configuring a directory hierarchy, adding group, hosts, services and other data to the hierarchy. Also included is importing items from LDIF files and add items with a management tool, as well as adding users to the directory and change their passwords.
Objective ID 2.7.4: PAM AuthenticationIncludes task IDs 6.3.7 3.11.4 The candidate should be able to configure PAM to support authentication via traditional /etc/passwd, shadow passwords, NIS, or LDAP.
System Maintenance ObjectivesObjective ID 2.11.1: System LoggingIncludes task IDs 3.16.2 3.16.5 5.1.11 5.1.8 6.1.6 The candidate should be able to configure syslogd to act as a central network log server. This objective also includes configuring syslogd to send log output to a central log server, logging remote connections, and using grep and other text utils to automate log analysis.
Objective ID 2.11.2: Packaging SoftwareIncludes task IDs 1.7.6 The candidate should be able to build a package. This objective includes building (or rebuilding) both RPM and DEB packaged software.
Objective ID 2.11.3: Backup ProceduresIncludes task ID 6.3.8 The candidate should be able to create an offsite backup storage plan. System Security ObjectivesObjective ID 2.9.2: Configuring a routerIncludes task IDs 3.4.3 3.4.6 3.2.1 3.2.2 3.4.1 3.4.2 3.4.4 3.4.5 6.4.1 6.4.3 6.4.4 6.4.5 The candidate should be able to configure ipchains and iptables to perform IP masquerading, and state the significance of Network Address Translation and Private Network Addresses in protecting a network. This objective includes configuring port redirection, listing filtering rules, and writing rules that accept or block datagrams based upon source or destination protocol, port and address. Also included is saving and reloading filtering configurations, using settings in /proc/sys/net/ipv4 to respond to DOS attacks, using /proc/sys/net/ipv4/ip_forward to turn IP forwarding on and off, and usingtools such as PortSentry to block port scans and vulnerability probes.
Objective ID 2.9.3: Securing FTP ServersIncludes task IDs 3.7.1 3.7.2 3.7.3 3.7.4 The candidate should be able to configure an anonymous download FTP server. This objective includes configuring an FTP server to allow anonymous uploads, listing additional precautions to be taken if anonymous uploads are permitted, configuring guest users and groups with chroot jail, and configuring ftpaccess to deny access to named users or groups.
Objective ID 2.9.4: Secure Shell (OpenSSH)Includes task IDs 5.2.2 5.2.5 5.2.7 5.2.8 5.2.9 5.2.13 5.2.16 5.2.17 5.2.18 5.2.23 6.3.1 The candidate should be able to configure sshd to allow or deny root logins, enable or disable X forwarding. This objective includes generating server keys, generating a user's public/private key pair, adding a public key to a user's authorized_keys file, and configuring ssh-agent for all users. Candidates should also be able to configure port forwarding to tunnel an application protocol over ssh, configure ssh to support the ssh protocol versions 1 and 2, disable non-root logins during system maintenance, configure trusted clients for ssh logins without a password, and make multiple connections from multiple hosts to guard against loss of connection to remote host following configuration changes.
Objective ID 2.9.5: TCP_wrappersIncludes task IDs 5.2.11 The candidate should be able to configure tcpwrappers to allow connections to specified servers from only certain hosts or subnets.
Objective ID 2.9.6: Security TasksIncludes task IDs 5.2.22 6.2.2 6.2.7 6.2.8 6.2.9 6.2.10 6.3.5 The candidate should be able to install and configure kerberos and perform basic security auditing of source code. This objective includes arranging to receive security alerts from Bugtraq, CERT, CIAC or other sources, being able to test for open mail relays and anonymous FTP servers, installing and configuring an intrusion detection system such as snort or Tripwire. Candidates should also be able to update the IDS configuration as new vulnerabilities are discovered and apply security patches and bugfixes.
System Customization and Automation ObjectivesObjective ID 2.12.1: Automating Tasks using ScriptsIncludes task IDs 1.7.1 1.7.2 1.7.3 1.7.4 1.7.5 5.1.1 5.1.2 5.1.10 5.2.15 6.2.6 The candidate should be able to write simple Perl scripts that make use of modules where appropriate, use the Perl taint mode to secure data, and install Perl modules from CPAN. This objective includes using sed and awk in scripts, and using scripts to check for process execution and generate alerts by email or pager if a process dies. Candidates should be able to write and schedule automatic execution of scripts to parse logs for alerts and email them to administrators, synchronize files across machines using rsync, monitor files for changes and generate email alerts, and write a script that notifies administrators when specified users log in or out.
Troubleshooting ObjectivesObjective ID 2.13.2: Creating Recovery DisksIncludes task IDs 3.34.1 3.34.2 Candidate should be able to: create both a standard bootdisk for system entrance, and a recovery disk for system repair.
Objective ID 2.13.3: Identifying Boot StagesIncludes task IDs 3.34.2 Candidate should be able to: determine, from bootup text, the 4 stages of boot sequence and distinguish between each.
Objective ID 2.13.4: Troubleshooting LILOIncludes task IDs 3.34.3 Candidate should be able to: determine specific stage failures and corrective techniques.
Objective ID 2.13.5: General TroubleshootingIncludes task IDs 3.34.4 3.34.5 3.34.6 A candidate should be able to recognize and identify boot loader and kernel specific stages and utilize kernel boot messages to diagnose kernel errors. This objective includes being able to identify and correct common hardware issues, and be able to determine if the problem is hardware or software.
Objective ID 2.13.6: Troubleshooting System ResourcesIncludes task IDs 3.34.7 3.34.8 A candidate should be able to identify, diagnose and repair local system environment.
Objective ID 2.13.7: Troubleshooting Network IssuesIncludes task IDs 3.34.9 3.34.10 A candidates should be able to identify and correct common network setup issues to include knowledge of locations for basic configuration files and commands.
Objective ID 2.13.8: Troubleshooting Environment ConfigurationsIncludes task IDs 3.34.11 A candidate should be able to identify common local system and user environment configuration issues and common repair techniques.
|
- To unsubscribe, send email to majordomo@silug.org with "unsubscribe silug-discuss" in the body.