My Experience with RHCSA and RHCE

So, I've recently completed the RHCSA and RHCE exams successfully and I wanted to share my experience with it. Here are a few of my thoughts about both exams.

Time:
There's plenty of it on RHCSA but not so much on RHCE. If you know what you are doing on the topics, you'll be done in under 1 hour (in case of the RHCSA) assuming you are decently fast in typing. However, that's not the case with RHCE. For passing RHCE, you'll need to have good time management and eventually skip tasks that you get stuck on since you might not be completing the rest of the tasks.

Tasks:
Take a minute and read through all the tasks first. Map your own 'Big Picture' on how the system has to look like in the end. This includes the configuration of SELinux, Firewalld and systemctl.
Note that your changes and configurations have to be persistent between reboots.
If you can do the labs without too much of a hassle, you should be good to go. What you want to avoid however is rebuilding your machine because you broke it by working on, let's say, partitioning. So, do (potential) destructive Tasks first!

Authentication:
It's generally not a bad idea to generate an ssh-key pair and enable key authentication on the machines you are working on. This saves the time of typing in the password every time you connect using ssh. This might not be that much important in case of the RHCSA-Exam but in the RHCE-Exam every bit of time saved is valuable.

Working with networked Storage:
If you are required to work with iSCSI and/or NFS, always remember the '_netdev' option in your mount options. By forgetting this option, you might look at a machine that takes forever to boot or might not even boot at all since your machine will think it's local storage and mount it before the network stack is started. Worst case is, that you'll be awarded 0 points because your machine isn't booting.

Troubleshooting SELinux:
The best way to troubleshoot SELinux is probably by using the sealert command. This will give you quite a lot of information on what is going on and why something is blocked or denied access to.

Finding help in the exam:
With the RHCSA-Exam I've found every bit of information I needed by adding a simple '--help | less' to my commands. With the RHCE there were man pages that had all the required pieces of information I needed. If you don't know the exact name, try the following command and you should receive a number of man pages associated with your search, here an example with nmcli:

 $ apropos nmcli  
 nmcli (1)      - command-line tool for controlling NetworkManager  
 nmcli-examples (7)  - usage examples of nmcli

Conclusion:
I think the Red Hat Certifications are challenging but they're worth it in the end. You're required to do real world tasks and you'll get rated on how well you did on each task. You're not locked in to a specific set of commands on how to accomplish one specific task but have the freedom to decide how you want to get things done.

Comments

Dynamic DNS with BIND and ISC-DHCP

I personally prefer to work with hostnames instead of ip-addresses. If you have anything like freeipa or active directory, it will do that for you by registering the client you added to your realm to the managed dns and edit the records dynamically. We can achieve the same goal with just bind and isc-dhcp. I'll use a raspberry pi with raspbian 9 for this setup. So here is a quick tutorial on how to configure the isc-dhcp-server to dynamically update bind. First set a static ip to your server. [archy@ddns ~]$ sudo vim /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) # Please note that this file is written to be used with dhcpcd # For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf' # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d auto eth0 iface eth0 inet static address 172.31.30.5 network 172.31.30.0 broadcast 172.31.30.255 netmask 255.255.255.0 ...

LACP-Teaming on CentOS 7 / RHEL 7

What is teaming? Teaming or LACP (802.3ad) is a technique used to bond together multiple interfaces to achieve higher combined bandwith. NOTE: every clients speed can only be as high as the single link speed of one of the members. That means, if the interfaces I use in the bond have 1 Gigabit, every client will only have a maximum speed of 1 Gigabit. The advantage of teaming is, that it can handle multiple connections with 1 Gigabit. How many connections depends on the amount of your network cards. I'm using 2 network cards for this team on my server. That means I can handle 2 Gigabit connections at full rate on my server provided the rest of the hardware can deliver that speed. There also exists 'Bonding' in the Linux world. They both do the same in theory but for a detailed comparison check out this article about teaming in RHEL7 . To create a teaming-interface, we will first have to remove all the interface configurations we've done on the (soon to be) sla...

Push logs and data into elasticsearch - Part 2 Mikrotik Logs

This is only about the setup of different logging, one being done with Filebeat and the other being done with sending logging to a dedicated port opened in Logstash using the TCP / UDP Inputs. Prerequesites: You'll need a working Elasticsearch Cluster with Logstash and Kibana. Start by getting the Log Data you want to structure parsed correctly. Mikrotik Logs are a bit difficult since they show you Data in the interface which is already enriched with Time / Date. That means a message that the remote logging will send to Logstash will look like this: firewall,info forward: in:lan out:wan, src-mac aa:bb:cc:dd:ee:ff, proto UDP, 172.31.100.154:57061->109.164.113.231:443, len 76 You can check them in the grok debugger and create your own filters and mapping. The following is my example which might not fit your needs. Here are some custom patterns I wrote for my pattern matching: MIKROTIK_DATE \b(?:jan(?:uary)?|feb(?:ruary)?|mar(?:ch)?|apr(?:il)?|may|jun(?:e)?|jul(?...

FreeIPA - Integrating your DHCPD dynamic Updates into IPA

I recently went over my network configuration and noticed that the dhcp-leases were not pushed into the IPA-DNS yet. So I thought, why not do it now. The setup is very similar to setting it up on a single bind instance not managed by IPA (I've already written a guide about this here ). My setup is done with the following hosts: ipa01.archyslife.lan - 172.31.0.1 inf01.archyslife.lan - 172.31.0.5 First of all, create a rndc-key: [archy@ipa01 ~]$ sudo rndc-confgen -a -b 512 This will create the following file '/etc/rndc-key' [archy@ipa01 ~]$ sudo cat /etc/rndc.key key "rndc-key" { algorithm hmac-md5; secret "secret_key_here=="; }; We also need to make named aware of the rndc-key and allow our remote dhcp server to write dns entries: [archy@ipa01 ~]$ sudo vim /etc/named.conf ... include "/etc/rndc-key"; controls { inet 172.31.0.1 port 953 allow { 172.31.0.5; } keys ...

SSSD - Debugging PAM permission denied

Sometimes there's weird errors in IT that occur on random chance. I've had such an encounter with SSSD in combination with IPA(+AD-Trust) recently, where only sometimes, a connection to one of the IPA-Servers would fail with this error: Jul 13 13:36:42 ipa02.archyslife.lan sshd[3478]: pam_sss(sshd:account): Access denied for user runner: 4 (System error) Jul 13 13:36:42 ipa02.archyslife.lan sshd[3478]: fatal: Access denied for user runner by PAM account configuration [preauth] In my case, it was only happening sometimes when running a basic system setup role using ansible on every host in the entire environment. This way, there was no consistent pattern besides being the same host every time if it failed. First up, add the 'debug_level=X' to every section required in the /etc/sssd/sssd.conf where X is a number from 1 to 10 with 10 being the most verbose. Afterward, restart sssd and check the logs for any obvious problems. 1) If you are using local users, check the...

Archy's Blog

Search This Blog