RHCE Test Configuration Instructions
Information for the two systems you will use in test is the following:
system1.group3.example.com: is one of the main sever. system2.group3.example.com: mainly used as a client.
Password for both of the two systems is atenorth
System’s IP is provided by DHCP, you can regard it as normal, or you can reset to Static IP in accordance with the following requirements:
system1.group3.example.com: 172.24.3.5
system2.group3.example.com: 172.24.3.10
The subnet mask is 255.255.255.0
Your system is a member of DNS domain group3.example.com. All systems in DNS domain group3.example.com are all in subnet 172.24.3.0/255.255.255.0, the same all systems in this subnet are also in group3.example.com, unless specialized, all network services required to be configured can be accessed by systems of domain group3.
host.group3.example.com provides a centralized authentication service domain
GROUP3.EXAMPLE.COM, both system1 and system2 have already been pre-configured to be the client for this domain, this domain provides the following user account:
Firewall is enabled by default, you can turn it off when deemed appropriate, other settings about firewall may be in separate requirements.
Your system will be restarted before scoring, so please ensure that all modifications and service configurations you made still can be operated after the restart without manual intervention, virtual machine instances of all examinations must be able to enter the correct multi-user level after restart without manual assistance, it will be scored zero if the test using virtual machine system cannot be restarted or be properly restarted.
Corresponding distribution packages for the testing using operating system Red Hat Enterprise Linux version can be found in the following link:
http://server1.group3.example.com/rhel
Part of the requirements include host security, ensure your host security limit does not prevent the request to allow the host and network, although you correctly configured the network service but would have to allow the host or network is blocked, this also does not score.
You will notice that some requirements which clearly do not allow services be accessed by service domain my133t.org, systems of this domain are in subnet 172.25.1.0/252.255.255.0, and systems of these subnets also belong to my 133t.org domain.
PS: Notice that some test questions may depend on other exam questions, for example, you might be asked to perform a series of restrictions on a user, but this user creation may be required in other questions. For convenient identification, each exam question has some radio buttons to help you identify which questions you have already completed or not completed. Certainly, you do not need to care these buttons if you don’t need them.
Implement/configure a Web Service.
Configure a site http://systeml. domain11.example.com/ on the system1, then execute the following steps:
(1) Download file from http://rhgls.domain11.example.com/materials/station.html and rename this files index.html, don’t modify the file contents;
(2) Copy the file index.html to your web server's DocumentRoot directory
(3) Clients from domain group3.example.com can access to this web service
(4) Clients from domain my133t.org deny access to this web service
RHCE Test Configuration Instructions
Information for the two systems you will use in test is the following:
system1.group3.example.com: is one of the main sever. system2.group3.example.com: mainly used as a client.
Password for both of the two systems is atenorth
System’s IP is provided by DHCP, you can regard it as normal, or you can reset to Static IP in accordance with the following requirements:
system1.group3.example.com: 172.24.3.5
system2.group3.example.com: 172.24.3.10
The subnet mask is 255.255.255.0
Your system is a member of DNS domain group3.example.com. All systems in DNS domain group3.example.com are all in subnet 172.24.3.0/255.255.255.0, the same all systems in this subnet are also in group3.example.com, unless specialized, all network services required to be configured can be accessed by systems of domain group3.
host.group3.example.com provides a centralized authentication service domain
GROUP3.EXAMPLE.COM, both system1 and system2 have already been pre-configured to be the client for this domain, this domain provides the following user account:
Firewall is enabled by default, you can turn it off when deemed appropriate, other settings about firewall may be in separate requirements.
Your system will be restarted before scoring, so please ensure that all modifications and service configurations you made still can be operated after the restart without manual intervention, virtual machine instances of all examinations must be able to enter the correct multi-user level after restart without manual assistance, it will be scored zero if the test using virtual machine system cannot be restarted or be properly restarted.
Corresponding distribution packages for the testing using operating system Red Hat Enterprise Linux version can be found in the following link:
http://server1.group3.example.com/rhel
Part of the requirements include host security, ensure your host security limit does not prevent the request to allow the host and network, although you correctly configured the network service but would have to allow the host or network is blocked, this also does not score.
You will notice that some requirements which clearly do not allow services be accessed by service domain my133t.org, systems of this domain are in subnet 172.25.1.0/252.255.255.0, and systems of these subnets also belong to my 133t.org domain.
PS: Notice that some test questions may depend on other exam questions, for example, you might be asked to perform a series of restrictions on a user, but this user creation may be required in other questions. For convenient identification, each exam question has some radio buttons to help you identify which questions you have already completed or not completed. Certainly, you do not need to care these buttons if you don’t need them.
Configure Multi-User SMB Mounts.
Share the directory /devops through SMB on the systeml, as required:
1. The share name is devops
2. The shared directory devops just can be used by clients in domain11.example.com
3. The shared directory devop must be able to be browsed
4. User silene must be able to access this share through read, access code is redhat
5. User akira must be able to access this share through read and write, access code is redhat
6. This share permanently mount to system2. domain11.example.com the user /mnt/dev, make user silene as authentication any users can get temporary write permissions from akira
RHCE Test Configuration Instructions
Information for the two systems you will use in test is the following:
system1.group3.example.com: is one of the main sever. system2.group3.example.com: mainly used as a client.
Password for both of the two systems is atenorth
System’s IP is provided by DHCP, you can regard it as normal, or you can reset to Static IP in accordance with the following requirements:
system1.group3.example.com: 172.24.3.5
system2.group3.example.com: 172.24.3.10
The subnet mask is 255.255.255.0
Your system is a member of DNS domain group3.example.com. All systems in DNS domain group3.example.com are all in subnet 172.24.3.0/255.255.255.0, the same all systems in this subnet are also in group3.example.com, unless specialized, all network services required to be configured can be accessed by systems of domain group3.
host.group3.example.com provides a centralized authentication service domain
GROUP3.EXAMPLE.COM, both system1 and system2 have already been pre-configured to be the client for this domain, this domain provides the following user account:
Firewall is enabled by default, you can turn it off when deemed appropriate, other settings about firewall may be in separate requirements.
Your system will be restarted before scoring, so please ensure that all modifications and service configurations you made still can be operated after the restart without manual intervention, virtual machine instances of all examinations must be able to enter the correct multi-user level after restart without manual assistance, it will be scored zero if the test using virtual machine system cannot be restarted or be properly restarted.
Corresponding distribution packages for the testing using operating system Red Hat Enterprise Linux version can be found in the following link:
http://server1.group3.example.com/rhel
Part of the requirements include host security, ensure your host security limit does not prevent the request to allow the host and network, although you correctly configured the network service but would have to allow the host or network is blocked, this also does not score.
You will notice that some requirements which clearly do not allow services be accessed by service domain my133t.org, systems of this domain are in subnet 172.25.1.0/252.255.255.0, and systems of these subnets also belong to my 133t.org domain.
PS: Notice that some test questions may depend on other exam questions, for example, you might be asked to perform a series of restrictions on a user, but this user creation may be required in other questions. For convenient identification, each exam question has some radio buttons to help you identify which questions you have already completed or not completed. Certainly, you do not need to care these buttons if you don’t need them.
Dynamic WEB content
Configure dynamic web content to provide on the system1, as required:
Dynamic content provided by a virtual machine named dynamic.domain11.example.com
Virtual host listening on port 8909
Download a script from http://rhgls .domain11.example.com/materials/webapp.wsgi, then put it in the right place, don’t modify the file content in any situations
Dynamically generated web page should be received when clients access http://dynamic.domain11example.com:8909.
This http:// dynamic.domain11.example.com:8909/ must be able to be accessed by all system of domain11.example.com
RHCE Test Configuration Instructions
Information for the two systems you will use in test is the following:
system1.group3.example.com: is one of the main sever. system2.group3.example.com: mainly used as a client.
Password for both of the two systems is atenorth
System’s IP is provided by DHCP, you can regard it as normal, or you can reset to Static IP in accordance with the following requirements:
system1.group3.example.com: 172.24.3.5
system2.group3.example.com: 172.24.3.10
The subnet mask is 255.255.255.0
Your system is a member of DNS domain group3.example.com. All systems in DNS domain group3.example.com are all in subnet 172.24.3.0/255.255.255.0, the same all systems in this subnet are also in group3.example.com, unless specialized, all network services required to be configured can be accessed by systems of domain group3.
host.group3.example.com provides a centralized authentication service domain
GROUP3.EXAMPLE.COM, both system1 and system2 have already been pre-configured to be the client for this domain, this domain provides the following user account:
Firewall is enabled by default, you can turn it off when deemed appropriate, other settings about firewall may be in separate requirements.
Your system will be restarted before scoring, so please ensure that all modifications and service configurations you made still can be operated after the restart without manual intervention, virtual machine instances of all examinations must be able to enter the correct multi-user level after restart without manual assistance, it will be scored zero if the test using virtual machine system cannot be restarted or be properly restarted.
Corresponding distribution packages for the testing using operating system Red Hat Enterprise Linux version can be found in the following link:
http://server1.group3.example.com/rhel
Part of the requirements include host security, ensure your host security limit does not prevent the request to allow the host and network, although you correctly configured the network service but would have to allow the host or network is blocked, this also does not score.
You will notice that some requirements which clearly do not allow services be accessed by service domain my133t.org, systems of this domain are in subnet 172.25.1.0/252.255.255.0, and systems of these subnets also belong to my 133t.org domain.
PS: Notice that some test questions may depend on other exam questions, for example, you might be asked to perform a series of restrictions on a user, but this user creation may be required in other questions. For convenient identification, each exam question has some radio buttons to help you identify which questions you have already completed or not completed. Certainly, you do not need to care these buttons if you don’t need them.
Configure NFS service
Configure the NFS service on the system1, as required:
1. Share the directory /public in read only way, just can be accessed by systems in domain11.example.com at the same time.
2. Share the directory /protected in rad and write way, Kerberos security encryption required, you can use the key provided by the following URL:
http://host.domain11.example.com/materials/nfs_server.keytab
3. The directory /protected should contain the sub directory named project and the owner name is deepak;
4. User deepak can access /protected/project in read and write ways
There were two systems:
system1, main system on which most of the configuration take place
system2, some configuration here
iSCSI Initiator
The serverX.example.com provides an iscsi port (3260). Connect the disk with desktopX.example.com and configure filesystem with the following requirements.
Create 800 MB partition on iSCSI block device and assign the filesystem as xfs
Mount the volume under /mnt/initiator at the system boot time
The filesystem should contain the copy of http://station.network0.example.com/pub/iscsi.txt
The file should be owned by root with 0644 permission
NOTE: the content of the file should not be modified
There were two systems:
system1, main system on which most of the configuration take place
system2, some configuration here
Webpage content modification.
Implement website for serverX.examp">http://serverX.example.com/owndir
Create a directory named as “owndir” under the document root of webserver
Download station.network0.example.com/pub">http://station.network0.example.com/pub/rhce/restrict.html
Rename the file into ondex.html
The content of the owndir should be visible to everyone browsing from your local system but should not be accessible from other location
There were two systems:
system1, main system on which most of the configuration take place
system2, some configuration here
Script1.
Create a script on serverX called /root/random with the following details
When run as /root/random postconf, should bring the output as “postroll”
When run as /root/random postroll, should bring the output as “postconf”
When run with any other argument or without argument, should bring any other argument or without argument, should bring the stderr as “/root/random postconf|postroll”
There were two systems:
system1, main system on which most of the configuration take place
system2, some configuration here
MariaDB
Restore a database on serverX from the backup file classroom.com/pub/rhce/backup.m">http://classroom.com/pub/rhce/backup.mdb
The database name should be Contacts. It should be access only within the localhost
Set a password for root user as “Postroll”. Other than the root user, the user Andrew is able to read the query from the above mentioned database. The user should be authenticated with the password as “Postroll”.
There were two systems:
system1, main system on which most of the configuration take place
system2, some configuration here
Customize the User Environment
Create a command called qstat on both serverX and desktop.
It should be able to execute the following command (ps –eo pid, tid, class, rtprio, ni, pri, psr, pcpu, stat, wchan:14, comm).
The command should be executable by all users.
There were two systems:
system1, main system on which most of the configuration take place
system2, some configuration here
Configure selinux.
Configure your systems that should be running in Enforcing.
