Difference between revisions of "LPIC-306 Objectives V3.0"

From LPI Wiki
Jump to: navigation, search
(→‎351.1 High Availability Concepts and Theory (weight: 5))
 
(49 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
__FORCETOC__
 
__FORCETOC__
 
==Introduction==
 
==Introduction==
−
The description of the entire [[LPIC-3]] programme is listed [[LPIC-3|here]].
+
The description of the entire [[LPIC-3]] program is listed [[LPIC-3|here]].
 
<br /><br />
 
<br /><br />
 +
 
==Version Information==
 
==Version Information==
  
−
These objectives are '''A DRAFT FOR''' version 3.0.
+
These objectives are for version 3.0.
  
−
There is also a [[LPIC305SummaryVersion2To3|summary and detailed information]] on the changes from version 2.0 to 3.0 of the objectives.
+
This exam results from a split of version 2.0 of the exam 304.
 +
 
 +
There is also a [[LPIC306SummaryVersion2To3|summary and detailed information]] on the changes from version 2.0 of exam 304 to 3.0 of these objectives.
  
 
The version [[LPIC-304 Objectives V2|2.x objectives]] can be found [[LPIC-304 Objectives V2|here]].
 
The version [[LPIC-304 Objectives V2|2.x objectives]] can be found [[LPIC-304 Objectives V2|here]].
Line 15: Line 18:
 
==Translations of Objectives==
 
==Translations of Objectives==
 
The following translations of the objectives are available on this wiki:
 
The following translations of the objectives are available on this wiki:
−
* [[LPIC-305 Objectives V3.0|English]]
+
* [[LPIC-306 Objectives V3.0|English]]
−
* [[LPIC-305 Objectives V3.0(JA)|Japanese]]
+
* [[LPIC-306 Objectives V3.0(JA)|Japanese]]
 
<br />
 
<br />
  
 
==Objectives==
 
==Objectives==
−
===''Topic 351: High Availability Cluster Management''===
+
===''Topic 361: High Availability Cluster Management''===
−
====<span style="color:navy">351.1 High Availability Concepts and Theory (weight: 5)</span>====
+
====<span style="color:navy">361.1 High Availability Concepts and Theory (weight: 6)</span>====
 
{|
 
{|
 
| style="background:#dadada" | '''Weight'''
 
| style="background:#dadada" | '''Weight'''
−
| style="background:#eaeaea" | 5
+
| style="background:#eaeaea" | 6
 
|-
 
|-
 
| style="background:#dadada; padding-right:1em" | '''Description'''
 
| style="background:#dadada; padding-right:1em" | '''Description'''
Line 36: Line 39:
 
* Understand application aspects of high availability
 
* Understand application aspects of high availability
 
* Understand operational considerations of high availability
 
* Understand operational considerations of high availability
−
'''The following is a partial list of the used files, terms and utilities:'''
+
'''Partial list of the used files, terms and utilities:'''
 
* Active/Passive Cluster
 
* Active/Passive Cluster
 
* Active/Active Cluster
 
* Active/Active Cluster
Line 46: Line 49:
 
* Cluster services
 
* Cluster services
 
* Quorum
 
* Quorum
−
* Fencing
+
* Fencing (Node and Resource Level Fencing)
 
* Split brain
 
* Split brain
 
* Redundancy
 
* Redundancy
Line 53: Line 56:
 
* Service Level Agreement (SLA)
 
* Service Level Agreement (SLA)
 
* Disaster Recovery
 
* Disaster Recovery
 +
* State Handling
 
* Replication
 
* Replication
 
* Session handling
 
* Session handling
 
<br />
 
<br />
  
−
====<span style="color:navy">351.2 Load Balanced Clusters (weight: 8)</span>====
+
====<span style="color:navy">361.2 Load Balanced Clusters (weight: 8)</span>====
 
{|
 
{|
 
| style="background:#dadada" | '''Weight'''
 
| style="background:#dadada" | '''Weight'''
Line 66: Line 70:
 
|}
 
|}
 
'''Key Knowledge Areas:'''
 
'''Key Knowledge Areas:'''
−
* Understanding of LVS / IPVS.
+
* Understand the concepts of LVS / IPVS
−
* Basic knowledge of VRRP.
+
* Understand the basics of VRRP
−
* Configuration of keepalived.
+
* Configure keepalived
−
* Configuration of ldirectord.
+
* Configure ldirectord
−
* Backend server network configuration.
+
* Configure backend server networking
−
* Understanding of HAProxy.
+
* Understand HAProxy
−
* Configuration of HAProxy.
+
* Configure HAProxy
−
'''The following is a partial list of the used files, terms and utilities:'''
+
'''Partial list of the used files, terms and utilities:'''
 
* ipvsadm
 
* ipvsadm
 
* syncd
 
* syncd
Line 86: Line 90:
 
<br />
 
<br />
  
−
====<span style="color:navy">351.3 Failover Clusters (weight: 8)</span>====
+
====<span style="color:navy">361.3 Failover Clusters (weight: 8)</span>====
 
{|
 
{|
 
| style="background:#dadada" | '''Weight'''
 
| style="background:#dadada" | '''Weight'''
Line 92: Line 96:
 
|-
 
|-
 
| style="background:#dadada; padding-right:1em" | '''Description'''
 
| style="background:#dadada; padding-right:1em" | '''Description'''
−
| style="background:#eaeaea" | Candidates should have experience in the installation, configuration, maintenance and troubleshooting of a Pacemaker cluster. This includes the use of Corosync. The focus is on Pacemaker 1.1 for Corosync 2.x.
+
| style="background:#eaeaea" | Candidates should have experience in the installation, configuration, maintenance and troubleshooting of a Pacemaker cluster. This includes the use of Corosync. The focus is on Pacemaker 2.x for Corosync 2.x.
 
|}
 
|}
 
'''Key Knowledge Areas:'''
 
'''Key Knowledge Areas:'''
−
* Pacemaker architecture and components (CIB, CRMd, PEngine, LRMd, DC, STONITHd).
+
* Understand the architecture and components of Pacemaker (CIB, CRMd, PEngine, LRMd, DC, STONITHd)
−
* Pacemaker cluster configuration.
+
* Manage Pacemaker cluster configurations
−
* Resource classes (OCF, LSB, Systemd, Upstart, Service, STONITH, Nagios).
+
* Understand Pacemaker resource classes (OCF, LSB, Systemd, Service, STONITH, Nagios)
−
* Resource rules and constraints (location, order, colocation).
+
* Manage Pacemaker resources
−
* Advanced resource features (templates, groups, clone resources, multi-state resources).
+
* Manage resource rules and constraints (location, order, colocation).
−
* Pacemaker management using pcs.
+
* Manage advanced resource features (templates, groups, clone resources, multi-state resources)
−
* Pacemaker management using crmsh.
+
* Obtain node information and manage node health
−
* Configuration and Management of corosync in conjunction with Pacemaker.
+
* Manage quorum and fencing in a Pacemaker cluster
−
* Awareness of other cluster engines (OpenAIS, Heartbeat, CMAN).
+
* Configure the Split Brain Detector on shared storage
−
'''The following is a partial list of the used files, terms and utilities:'''
+
* Manage Pacemaker using pcs
 +
* Manage Pacemaker using crmsh
 +
* Configure and management of corosync in conjunction with Pacemaker
 +
* Awareness of Pacemaker ACLs
 +
* Awareness of other cluster engines (OpenAIS, Heartbeat, CMAN)
 +
'''Partial list of the used files, terms and utilities:'''
 
* pcs
 
* pcs
 
* crm
 
* crm
Line 122: Line 131:
 
* corosync-quorumtool
 
* corosync-quorumtool
 
* stonith_admin
 
* stonith_admin
 +
* stonith
 +
* ocf:pacemaker:ping
 +
* ocf:pacemaker:NodeUtilization
 +
* ocf:pacemaker:ocf:SysInfo
 +
* ocf:pacemaker:HealthCPU
 +
* ocf:pacemaker:HealthSMART
 +
* sbd
 
<br />
 
<br />
  
−
===''Topic 352: High Availability Cluster Storage''===
+
===''Topic 362: High Availability Cluster Storage''===
−
====<span style="color:navy">352.1 DRBD / cLVM (weight: 6)</span>====
+
====<span style="color:navy">362.1 DRBD (weight: 6)</span>====
 
{|
 
{|
 
| style="background:#dadada" | '''Weight'''
 
| style="background:#dadada" | '''Weight'''
Line 131: Line 147:
 
|-
 
|-
 
| style="background:#dadada; padding-right:1em" | '''Description'''
 
| style="background:#dadada; padding-right:1em" | '''Description'''
−
| style="background:#eaeaea" | Candidates are expected to have the experience and knowledge to install, configure, maintain and troubleshoot DRBD devices. This includes integration with Pacemaker. DRBD configuration of version 9.0.x is covered. Candidates are further expected to be able to manage LVM configuration within a shared storage cluster.
+
| style="background:#eaeaea" | Candidates are expected to have the experience and knowledge to install, configure, maintain and troubleshoot DRBD devices. This includes integration with Pacemaker. DRBD configuration of version 9.0.x is covered.
 
|}
 
|}
 
'''Key Knowledge Areas:'''
 
'''Key Knowledge Areas:'''
−
* Understanding of the DRBD architecture
+
* Understand the DRBD architecture
−
* Understanding of DRBD resources, states and replication modes
+
* Understand DRBD resources, states and replication modes
−
* Configuration of DRBD resources, disks and devices
+
* Configure DRBD disks and devices
−
* Configuration of DRBD networking connections and meshes
+
* Configure DRBD networking connections and meshes
−
* Configuration of DRBD automatic recovery and error handling
+
* Configure DRBD automatic recovery and error handling
−
* Managing of DRBD using drbdadm
+
* Configure DRBD quorum and handlers for split brain and fencing
−
* Basic knowledge of drbdsetup and drbdmeta
+
* Manage DRBD using drbdadm
 +
* Understand the principles of drbdsetup and drbdmeta
 
* Restore and verify the integrity of a DRBD device after an outage
 
* Restore and verify the integrity of a DRBD device after an outage
−
* Integration of DRBD with Pacemaker
+
* Integrate DRBD with Pacemaker
−
* Understanding of cLVM and manage LVM volumes on a shared block device
+
* Understand the architecture and features of LINSTOR
−
* Integration of cLVM with Pacemaker
+
'''Partial list of the used files, terms and utilities:'''
−
'''The following is a partial list of the used files, terms and utilities:'''
+
 
* Protocol A, B and C
 
* Protocol A, B and C
 
* Primary, Secondary
 
* Primary, Secondary
Line 151: Line 167:
 
* drbd kernel module
 
* drbd kernel module
 
* drbdadm
 
* drbdadm
 +
* drbdmon
 
* drbdsetup
 
* drbdsetup
 
* drbdmeta
 
* drbdmeta
Line 156: Line 173:
 
* /etc/drbd.d/
 
* /etc/drbd.d/
 
* /proc/drbd
 
* /proc/drbd
−
* LVM2
 
−
* clvmd
 
−
* vgchange, vgs
 
 
<br />
 
<br />
  
−
====<span style="color:navy">352.2 Clustered File Systems (weight: 4)</span>====
+
====<span style="color:navy">362.2 Cluster Storage Access (weight: 3)</span>====
 +
{|
 +
| style="background:#dadada" | '''Weight'''
 +
| style="background:#eaeaea" | 3
 +
|-
 +
| style="background:#dadada; padding-right:1em" | '''Description'''
 +
 
 +
| style="background:#eaeaea" | Candidates should be able to connect a Linux node to remote block storage. This includes understanding common SAN technology and architectures, including management of iSCSI, as well as configuring multipathing for high availability and using LVM on a clustered storage.
 +
|}
 +
'''Key Knowledge Areas:'''
 +
* Understand the concepts of Storage Area Networks
 +
* Understand the concepts of Fibre Channel, including Fibre Channel Topologies
 +
* Understand and manage iSCSI targets and initiators
 +
* Understand and configure Device Mapper Multipath I/O (DM-MPIO)
 +
* Understand the concept of a Distributed Lock Manager (DLM)
 +
* Understand and manage clustered LVM
 +
* Manage DLM and LVM with Pacemaker
 +
'''Partial list of the used files, terms and utilities:'''
 +
* tgtadm
 +
* targets.conf
 +
* iscsiadm
 +
* iscsid.conf
 +
* /etc/multipath.conf
 +
* multipath
 +
* kpartx
 +
* pvmove
 +
* vgchange
 +
* lvchange
 +
 
 +
<br />
 +
<br />
 +
 
 +
====<span style="color:navy">362.3 Clustered File Systems (weight: 4)</span>====
 
{|
 
{|
 
| style="background:#dadada" | '''Weight'''
 
| style="background:#dadada" | '''Weight'''
Line 167: Line 213:
 
|-
 
|-
 
| style="background:#dadada; padding-right:1em" | '''Description'''
 
| style="background:#dadada; padding-right:1em" | '''Description'''
−
| style="background:#eaeaea" | Candidates should be able to install, maintain and troubleshoot GFS2 and OCFS2 filesystems. This includes integration with Pacemaker as well as awareness of other clustered filesystems available on Linux.
+
| style="background:#eaeaea" | Candidates should be able to install, maintain and troubleshoot GFS2 and OCFS2 filesystems. This includes awareness of other clustered filesystems available on Linux.
 
|}
 
|}
 
'''Key Knowledge Areas:'''
 
'''Key Knowledge Areas:'''
Line 174: Line 220:
 
* Create, maintain and troubleshoot GFS2 file systems in a cluster
 
* Create, maintain and troubleshoot GFS2 file systems in a cluster
 
* Create, maintain and troubleshoot OCFS2 file systems in a cluster
 
* Create, maintain and troubleshoot OCFS2 file systems in a cluster
−
* Integration of GFS2 and OCFS2 with Pacemaker
 
 
* Awareness of the O2CB cluster stack
 
* Awareness of the O2CB cluster stack
−
* Awareness of other commonly used clustered file systems, such as AFS
+
* Awareness of other commonly used clustered file systems, such as AFS and Lustre
−
'''The following is a partial list of the used files, terms and utilities:'''
+
'''Partial list of the used files, terms and utilities:'''
 
* mkfs.gfs2
 
* mkfs.gfs2
 
* mount.gfs2
 
* mount.gfs2
Line 194: Line 239:
 
<br />
 
<br />
  
−
===''Topic 353: Distributed Storage''===
+
===''Topic 363: High Availability Distributed Storage''===
−
====<span style="color:navy">353.1 GlusterFS Storage Clusters (weight: 4)</span>====
+
====<span style="color:navy">363.1 GlusterFS Storage Clusters (weight: 5)</span>====
 
{|
 
{|
 
| style="background:#dadada" | '''Weight'''
 
| style="background:#dadada" | '''Weight'''
−
| style="background:#eaeaea" | 4
+
| style="background:#eaeaea" | 5
 
|-
 
|-
 
| style="background:#dadada; padding-right:1em" | '''Description'''
 
| style="background:#dadada; padding-right:1em" | '''Description'''
Line 209: Line 254:
 
* Configure high availability aspects of GlusterFS
 
* Configure high availability aspects of GlusterFS
 
* Scale up a GlusterFS cluster
 
* Scale up a GlusterFS cluster
 +
* Replace failed bricks
 +
* Recover GlusterFS from a physical media failure
 
* Restore and verify the integrity of a GlusterFS cluster after an outage
 
* Restore and verify the integrity of a GlusterFS cluster after an outage
−
* Integrate GlusterFS with Pacemaker
 
 
* Awareness of GNFS
 
* Awareness of GNFS
 
'''Partial list of the used files, terms and utilities:'''
 
'''Partial list of the used files, terms and utilities:'''
Line 216: Line 262:
 
<br />
 
<br />
  
−
====<span style="color:navy">353.2 Ceph Storage Clusters (weight: 8)</span>====
+
====<span style="color:navy">363.2 Ceph Storage Clusters (weight: 8)</span>====
 
{|
 
{|
 
| style="background:#dadada" | '''Weight'''
 
| style="background:#dadada" | '''Weight'''
Line 226: Line 272:
 
'''Key Knowledge Areas:'''
 
'''Key Knowledge Areas:'''
 
* Understand the architecture and components of Ceph
 
* Understand the architecture and components of Ceph
−
* Manage OSD, MON and MDS
+
* Manage OSD, MGR, MON and MDS
 
* Understand and manage placement groups and pools
 
* Understand and manage placement groups and pools
 +
* Understand storage backends (FileStore and BlueStore)
 +
* Initialize a Ceph cluster
 
* Create and manage Rados Block Devices
 
* Create and manage Rados Block Devices
 
* Create and manage CephFS volumes, including snapshots
 
* Create and manage CephFS volumes, including snapshots
Line 234: Line 282:
 
* Configure high availability aspects of Ceph
 
* Configure high availability aspects of Ceph
 
* Scale up a Ceph cluster
 
* Scale up a Ceph cluster
−
* Integrate Ceph with Pacemaker
 
 
* Restore and verify the integrity of a Ceph cluster after an outage
 
* Restore and verify the integrity of a Ceph cluster after an outage
 +
* Understand key concepts of Ceph updates, including update order, tunables and features
 
'''Partial list of the used files, terms and utilities:'''
 
'''Partial list of the used files, terms and utilities:'''
 
* ceph-deploy (including relevant subcommands)
 
* ceph-deploy (including relevant subcommands)
Line 243: Line 291:
 
* rdb (including relevant subcommands)
 
* rdb (including relevant subcommands)
 
* cephfs (including relevant subcommands)
 
* cephfs (including relevant subcommands)
−
* ceph-authtool  
+
* ceph-volume (including relevant subcommands)
−
* ceph-crushtool
+
* ceph-authtool
 +
* ceph-bluestore-tool
 +
* crushtool
 
<br />
 
<br />
 
<br />
 
<br />
  
−
===''Topic 354: Node High Availability''===
+
===''Topic 364: Single Node High Availability''===
−
====<span style="color:navy">354.1 Single Node High Availability (weight: 2)</span>====
+
====<span style="color:navy">364.1 Hardware and Resource High Availability (weight: 2)</span>====
 
{|
 
{|
 
| style="background:#dadada" | '''Weight'''
 
| style="background:#dadada" | '''Weight'''
Line 258: Line 308:
 
|}
 
|}
 
'''Key Knowledge Areas:'''
 
'''Key Knowledge Areas:'''
−
* Understand and monitor S.M.A.R.T values using smartmontools
+
* Understand and monitor S.M.A.R.T values using smartmontools, including triggering frequent disk checks
−
* Configure system shutdown at specific UPC events
+
* Configure system shutdown at specific UPS events
 
* Configure monit for alerts in case of resource exhaustion
 
* Configure monit for alerts in case of resource exhaustion
−
'''The following is a partial list of the used files, terms and utilities:'''
+
'''Partial list of the used files, terms and utilities:'''
 
* smartctl
 
* smartctl
 
* /etc/smartd.conf
 
* /etc/smartd.conf
 
* smartd
 
* smartd
 +
* nvme-cli
 
* apcupsd
 
* apcupsd
 
* apctest
 
* apctest
Line 270: Line 321:
 
<br />
 
<br />
  
−
====<span style="color:navy">354.2 Advanced RAID (weight: 2)</span>====
+
====<span style="color:navy">364.2 Advanced RAID (weight: 2)</span>====
 
{|
 
{|
 
| style="background:#dadada" | '''Weight'''
 
| style="background:#dadada" | '''Weight'''
Line 286: Line 337:
 
* Understand availability and performance properties of various raid levels
 
* Understand availability and performance properties of various raid levels
 
* Configure mdadm monitoring and reporting
 
* Configure mdadm monitoring and reporting
−
'''The following is a partial list of the used files, terms and utilities:'''
+
'''Partial list of the used files, terms and utilities:'''
 
* mdadm
 
* mdadm
 
* /proc/mdstat
 
* /proc/mdstat
 
* /proc/sys/dev/raid/*
 
* /proc/sys/dev/raid/*
−
* Partiton types 0xFD and 0xDA
 
 
<br />
 
<br />
  
−
====<span style="color:navy">354.3 Advanced LVM (weight: 2)</span>====
+
====<span style="color:navy">364.3 Advanced LVM (weight: 3)</span>====
 
{|
 
{|
 
| style="background:#dadada" | '''Weight'''
 
| style="background:#dadada" | '''Weight'''
−
| style="background:#eaeaea" | 2
+
| style="background:#eaeaea" | 3
 
|-
 
|-
 
| style="background:#dadada; padding-right:1em" | '''Description'''
 
| style="background:#dadada; padding-right:1em" | '''Description'''
−
| style="background:#eaeaea" | Candidates should be able to configure LVM volumes. This includes managing LVM snapshot and RAIDs.
+
| style="background:#eaeaea" | Candidates should be able to configure LVM volumes. This includes managing LVM snapshot, pools and RAIDs.
 
|}
 
|}
 
'''Key Knowledge Areas:'''
 
'''Key Knowledge Areas:'''
 
* Understand and manage LVM, including linear and striped volumes
 
* Understand and manage LVM, including linear and striped volumes
 +
* Extend, grow, shrink and move LVM volumes
 
* Understand and manage LVM snapshots
 
* Understand and manage LVM snapshots
 +
* Understand and manage LVM thin and thick pools
 
* Understand and manage LVM RAIDs
 
* Understand and manage LVM RAIDs
−
'''The following is a partial list of the used files, terms and utilities:'''
+
'''Partial list of the used files, terms and utilities:'''
 
* /etc/lvm/lvm.conf
 
* /etc/lvm/lvm.conf
 
* pvcreate
 
* pvcreate
 +
* pvdisplay
 +
* pvmove
 +
* pvremove
 +
* pvresize
 
* vgcreate
 
* vgcreate
 +
* vgdisplay
 
* vgreduce
 
* vgreduce
 
* lvconvert
 
* lvconvert
 
* lvcreate
 
* lvcreate
 +
* lvdisplay
 
* lvextend
 
* lvextend
 +
* lvreduce
 +
* lvresize
 
<br />
 
<br />
  
−
====<span style="color:navy">354.4 Network High Availability (weight: 3)</span>====
+
====<span style="color:navy">364.4 Network High Availability (weight: 5)</span>====
 
{|
 
{|
 
| style="background:#dadada" | '''Weight'''
 
| style="background:#dadada" | '''Weight'''
−
| style="background:#eaeaea" | 3
+
| style="background:#eaeaea" | 5
 
|-
 
|-
 
| style="background:#dadada; padding-right:1em" | '''Description'''
 
| style="background:#dadada; padding-right:1em" | '''Description'''
−
| style="background:#eaeaea" | Candidates should be able to configure redundant networking connections and manage VLANs.
+
| style="background:#eaeaea" | Candidates should be able to configure redundant networking connections and manage VLANs. Furthermore, candidates should have a basic understanding of BGP.
 
|}
 
|}
 
'''Key Knowledge Areas:'''
 
'''Key Knowledge Areas:'''
 
* Understand and configure bonding network interface
 
* Understand and configure bonding network interface
−
* Network bond modes and algorithms (active-backup, blance-tlb, balance-alb, 802.3ad, balance-rr, balance-xor, broadcast)
+
* Network bond modes and algorithms (active-backup, balance-tlb, balance-alb, 802.3ad, balance-rr, balance-xor, broadcast)
 
* Configure switch configuration for high availability, including RSTP
 
* Configure switch configuration for high availability, including RSTP
 
* Configure VLANs on regular and bonded network interfaces
 
* Configure VLANs on regular and bonded network interfaces
 
* Persist bonding and VLAN configuration
 
* Persist bonding and VLAN configuration
−
* Understand the principle of autonomous systems and BGP to manage redundant uplinks
+
* Understand the principle of autonomous systems and BGP to manage external redundant uplinks
−
'''The following is a partial list of the used files, terms and utilities:'''
+
* Awareness of traffic shaping and control capabilities of Linux
 +
'''Partial list of the used files, terms and utilities:'''
 
* bonding.ko (including relevant module options)
 
* bonding.ko (including relevant module options)
 
* /etc/network/interfaces
 
* /etc/network/interfaces
 
* /etc/sysconfig/networking-scripts/ifcfg-*
 
* /etc/sysconfig/networking-scripts/ifcfg-*
 +
* /etc/systemd/network/*.network
 +
* /etc/systemd/network/*.netdev
 
* nmcli
 
* nmcli
 
* /sys/class/net/bonding_masters
 
* /sys/class/net/bonding_masters
Line 340: Line 403:
 
* ifenslave
 
* ifenslave
 
* ip
 
* ip
−
<br />
 
−
<br />
 
−
 
−
===''Topic 355: Backup and Disaster Recovery''===
 
−
====<span style="color:navy">355.1 TBD: Backup (weight: TBD)</span>====
 
−
{|
 
−
| style="background:#dadada" | '''Weight'''
 
−
| style="background:#eaeaea" | TBD
 
−
|-
 
−
| style="background:#dadada; padding-right:1em" | '''Description'''
 
−
| style="background:#eaeaea" |
 
−
|}
 
−
'''Key Knowledge Areas:'''
 
−
'''The following is a partial list of the used files, terms and utilities:'''
 
−
<br />
 
−
====<span style="color:navy">355.2 Disaster Recovery (weight: TBD)</span>====
 
−
{|
 
−
| style="background:#dadada" | '''Weight'''
 
−
| style="background:#eaeaea" | TBD
 
−
|-
 
−
| style="background:#dadada; padding-right:1em" | '''Description'''
 
−
| style="background:#eaeaea" |
 
−
|}
 
−
'''Key Knowledge Areas:'''
 
−
'''The following is a partial list of the used files, terms and utilities:'''
 
 
<br />
 
<br />
 
<br />
 
<br />

Latest revision as of 11:44, 21 February 2023

Introduction

The description of the entire LPIC-3 program is listed here.

Version Information

These objectives are for version 3.0.

This exam results from a split of version 2.0 of the exam 304.

There is also a summary and detailed information on the changes from version 2.0 of exam 304 to 3.0 of these objectives.

The version 2.x objectives can be found here.


Translations of Objectives

The following translations of the objectives are available on this wiki:


Objectives

Topic 361: High Availability Cluster Management

361.1 High Availability Concepts and Theory (weight: 6)

Weight 6
Description Candidates should understand the properties and design approaches of high availability clusters.

Key Knowledge Areas:

  • Understand the goals of High Availability and Site Reliability Engineering
  • Understand common cluster architectures
  • Understand recovery and cluster reorganization mechanisms
  • Design an appropriate cluster architecture for a given purpose
  • Understand application aspects of high availability
  • Understand operational considerations of high availability

Partial list of the used files, terms and utilities:

  • Active/Passive Cluster
  • Active/Active Cluster
  • Failover Cluster
  • Load Balanced Cluster
  • Shared-Nothing Cluster
  • Shared-Disk Cluster
  • Cluster resources
  • Cluster services
  • Quorum
  • Fencing (Node and Resource Level Fencing)
  • Split brain
  • Redundancy
  • Mean Time Before Failure (MTBF)
  • Mean Time To Repair (MTTR)
  • Service Level Agreement (SLA)
  • Disaster Recovery
  • State Handling
  • Replication
  • Session handling


361.2 Load Balanced Clusters (weight: 8)

Weight 8
Description Candidates should know how to install, configure, maintain and troubleshoot LVS. This includes the configuration and use of keepalived and ldirectord. Candidates should further be able to install, configure, maintain and troubleshoot HAProxy.

Key Knowledge Areas:

  • Understand the concepts of LVS / IPVS
  • Understand the basics of VRRP
  • Configure keepalived
  • Configure ldirectord
  • Configure backend server networking
  • Understand HAProxy
  • Configure HAProxy

Partial list of the used files, terms and utilities:

  • ipvsadm
  • syncd
  • LVS Forwarding (NAT, Direct Routing, Tunneling, Local Node)
  • connection scheduling algorithms
  • keepalived configuration file
  • ldirectord configuration file
  • genhash
  • HAProxy configuration file
  • load balancing algorithms
  • ACLs


361.3 Failover Clusters (weight: 8)

Weight 8
Description Candidates should have experience in the installation, configuration, maintenance and troubleshooting of a Pacemaker cluster. This includes the use of Corosync. The focus is on Pacemaker 2.x for Corosync 2.x.

Key Knowledge Areas:

  • Understand the architecture and components of Pacemaker (CIB, CRMd, PEngine, LRMd, DC, STONITHd)
  • Manage Pacemaker cluster configurations
  • Understand Pacemaker resource classes (OCF, LSB, Systemd, Service, STONITH, Nagios)
  • Manage Pacemaker resources
  • Manage resource rules and constraints (location, order, colocation).
  • Manage advanced resource features (templates, groups, clone resources, multi-state resources)
  • Obtain node information and manage node health
  • Manage quorum and fencing in a Pacemaker cluster
  • Configure the Split Brain Detector on shared storage
  • Manage Pacemaker using pcs
  • Manage Pacemaker using crmsh
  • Configure and management of corosync in conjunction with Pacemaker
  • Awareness of Pacemaker ACLs
  • Awareness of other cluster engines (OpenAIS, Heartbeat, CMAN)

Partial list of the used files, terms and utilities:

  • pcs
  • crm
  • crm_mon
  • crm_verify
  • crm_simulate
  • crm_shadow
  • crm_resource
  • crm_attribute
  • crm_node
  • crm_standby
  • cibadmin
  • corosync.conf
  • authkey
  • corosync-cfgtool
  • corosync-cmapctl
  • corosync-quorumtool
  • stonith_admin
  • stonith
  • ocf:pacemaker:ping
  • ocf:pacemaker:NodeUtilization
  • ocf:pacemaker:ocf:SysInfo
  • ocf:pacemaker:HealthCPU
  • ocf:pacemaker:HealthSMART
  • sbd


Topic 362: High Availability Cluster Storage

362.1 DRBD (weight: 6)

Weight 6
Description Candidates are expected to have the experience and knowledge to install, configure, maintain and troubleshoot DRBD devices. This includes integration with Pacemaker. DRBD configuration of version 9.0.x is covered.

Key Knowledge Areas:

  • Understand the DRBD architecture
  • Understand DRBD resources, states and replication modes
  • Configure DRBD disks and devices
  • Configure DRBD networking connections and meshes
  • Configure DRBD automatic recovery and error handling
  • Configure DRBD quorum and handlers for split brain and fencing
  • Manage DRBD using drbdadm
  • Understand the principles of drbdsetup and drbdmeta
  • Restore and verify the integrity of a DRBD device after an outage
  • Integrate DRBD with Pacemaker
  • Understand the architecture and features of LINSTOR

Partial list of the used files, terms and utilities:

  • Protocol A, B and C
  • Primary, Secondary
  • Three-way replication
  • drbd kernel module
  • drbdadm
  • drbdmon
  • drbdsetup
  • drbdmeta
  • /etc/drbd.conf
  • /etc/drbd.d/
  • /proc/drbd


362.2 Cluster Storage Access (weight: 3)

Weight 3
Description Candidates should be able to connect a Linux node to remote block storage. This includes understanding common SAN technology and architectures, including management of iSCSI, as well as configuring multipathing for high availability and using LVM on a clustered storage.

Key Knowledge Areas:

  • Understand the concepts of Storage Area Networks
  • Understand the concepts of Fibre Channel, including Fibre Channel Topologies
  • Understand and manage iSCSI targets and initiators
  • Understand and configure Device Mapper Multipath I/O (DM-MPIO)
  • Understand the concept of a Distributed Lock Manager (DLM)
  • Understand and manage clustered LVM
  • Manage DLM and LVM with Pacemaker

Partial list of the used files, terms and utilities:

  • tgtadm
  • targets.conf
  • iscsiadm
  • iscsid.conf
  • /etc/multipath.conf
  • multipath
  • kpartx
  • pvmove
  • vgchange
  • lvchange



362.3 Clustered File Systems (weight: 4)

Weight 4
Description Candidates should be able to install, maintain and troubleshoot GFS2 and OCFS2 filesystems. This includes awareness of other clustered filesystems available on Linux.

Key Knowledge Areas:

  • Understand the principles of cluster file systems and distributed file systems
  • Understand the Distributed Lock Manager
  • Create, maintain and troubleshoot GFS2 file systems in a cluster
  • Create, maintain and troubleshoot OCFS2 file systems in a cluster
  • Awareness of the O2CB cluster stack
  • Awareness of other commonly used clustered file systems, such as AFS and Lustre

Partial list of the used files, terms and utilities:

  • mkfs.gfs2
  • mount.gfs2
  • fsck.gfs2
  • gfs2_grow
  • gfs2_edit
  • gfs2_jadd
  • mkfs.ocfs2
  • mount.ocfs2
  • fsck.ocfs2
  • tunefs.ocfs2
  • mounted.ocfs2
  • o2info
  • o2image



Topic 363: High Availability Distributed Storage

363.1 GlusterFS Storage Clusters (weight: 5)

Weight 5
Description Candidates should be able to manage and maintain a GlusterFS storage cluster.

Key Knowledge Areas:

  • Understand the architecture and components of GlusterFS
  • Manage GlusterFS peers, trusted storge pools, bricks and volumes
  • Mount and use an existing GlusterFS
  • Configure high availability aspects of GlusterFS
  • Scale up a GlusterFS cluster
  • Replace failed bricks
  • Recover GlusterFS from a physical media failure
  • Restore and verify the integrity of a GlusterFS cluster after an outage
  • Awareness of GNFS

Partial list of the used files, terms and utilities:

  • gluster (including relevant subcommands)


363.2 Ceph Storage Clusters (weight: 8)

Weight 8
Description Candidates should be able to manage and maintain a Ceph Cluster. This includes the configuration of RGW, RDB devices and CephFS.

Key Knowledge Areas:

  • Understand the architecture and components of Ceph
  • Manage OSD, MGR, MON and MDS
  • Understand and manage placement groups and pools
  • Understand storage backends (FileStore and BlueStore)
  • Initialize a Ceph cluster
  • Create and manage Rados Block Devices
  • Create and manage CephFS volumes, including snapshots
  • Mount and use an existing CephFS
  • Understand and adjust CRUSH maps
  • Configure high availability aspects of Ceph
  • Scale up a Ceph cluster
  • Restore and verify the integrity of a Ceph cluster after an outage
  • Understand key concepts of Ceph updates, including update order, tunables and features

Partial list of the used files, terms and utilities:

  • ceph-deploy (including relevant subcommands)
  • ceph.conf
  • ceph (including relevant subcommands)
  • rados (including relevant subcommands)
  • rdb (including relevant subcommands)
  • cephfs (including relevant subcommands)
  • ceph-volume (including relevant subcommands)
  • ceph-authtool
  • ceph-bluestore-tool
  • crushtool



Topic 364: Single Node High Availability

364.1 Hardware and Resource High Availability (weight: 2)

Weight 2
Description Candidates should be able to monitor a local node for potential hardware failures and resource shortages.

Key Knowledge Areas:

  • Understand and monitor S.M.A.R.T values using smartmontools, including triggering frequent disk checks
  • Configure system shutdown at specific UPS events
  • Configure monit for alerts in case of resource exhaustion

Partial list of the used files, terms and utilities:

  • smartctl
  • /etc/smartd.conf
  • smartd
  • nvme-cli
  • apcupsd
  • apctest
  • monit


364.2 Advanced RAID (weight: 2)

Weight 2
Description Candidates should be able to manage software raid devices on Linux. This includes advanced features such as partitonable RAIDs and RAID containers as well as recovering RAID arrays after a failure.

Key Knowledge Areas:

  • Manage RAID devices using various raid levels, including hot spare discs, partitionable RAIDs and RAID containers
  • Add and remove devices from an existing RAID
  • Change the RAID level of an existing device
  • Recover a RAID device after a failure
  • Understand various metadata formats and RAID geometries
  • Understand availability and performance properties of various raid levels
  • Configure mdadm monitoring and reporting

Partial list of the used files, terms and utilities:

  • mdadm
  • /proc/mdstat
  • /proc/sys/dev/raid/*


364.3 Advanced LVM (weight: 3)

Weight 3
Description Candidates should be able to configure LVM volumes. This includes managing LVM snapshot, pools and RAIDs.

Key Knowledge Areas:

  • Understand and manage LVM, including linear and striped volumes
  • Extend, grow, shrink and move LVM volumes
  • Understand and manage LVM snapshots
  • Understand and manage LVM thin and thick pools
  • Understand and manage LVM RAIDs

Partial list of the used files, terms and utilities:

  • /etc/lvm/lvm.conf
  • pvcreate
  • pvdisplay
  • pvmove
  • pvremove
  • pvresize
  • vgcreate
  • vgdisplay
  • vgreduce
  • lvconvert
  • lvcreate
  • lvdisplay
  • lvextend
  • lvreduce
  • lvresize


364.4 Network High Availability (weight: 5)

Weight 5
Description Candidates should be able to configure redundant networking connections and manage VLANs. Furthermore, candidates should have a basic understanding of BGP.

Key Knowledge Areas:

  • Understand and configure bonding network interface
  • Network bond modes and algorithms (active-backup, balance-tlb, balance-alb, 802.3ad, balance-rr, balance-xor, broadcast)
  • Configure switch configuration for high availability, including RSTP
  • Configure VLANs on regular and bonded network interfaces
  • Persist bonding and VLAN configuration
  • Understand the principle of autonomous systems and BGP to manage external redundant uplinks
  • Awareness of traffic shaping and control capabilities of Linux

Partial list of the used files, terms and utilities:

  • bonding.ko (including relevant module options)
  • /etc/network/interfaces
  • /etc/sysconfig/networking-scripts/ifcfg-*
  • /etc/systemd/network/*.network
  • /etc/systemd/network/*.netdev
  • nmcli
  • /sys/class/net/bonding_masters
  • /sys/class/net/bond*/bonding/miimon
  • /sys/class/net/bond*/bonding/slaves
  • ifenslave
  • ip



Retrieved from "https://wiki.lpi.org/pubwiki/index.php?title=LPIC-306_Objectives_V3.0&oldid=5718"