SIMULATION -RHCE Test Configuration InstructionsInformation 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 atenorthSystem'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.10The subnet mask is 255.255.255.0Your 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 domainGROUP3.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/rhelPart 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 subnet172.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 the Local Mail ServiceConfigure the mail service on system1 and system2, as required:1. These systems do not accept external sending mails2. Any mails sent locally are automatically routed to rhgls.domain11.example.com3. Mails sent from these systems will be displayed from rhgls.domain11.example.com4. You can send mail to local user "˜arthur' to test your configuration system rhgls.domain11.example.com5. You have already configured this user's mail to the following URL rhgls.domain11.example.com/received_mail/11
Share directories via SMB -Configure the SMB service on the system1Your SMB server must be a member of the work group STAFFShare /common and share name must be commonOnly clients of domain11.example.com can access the common shareCommon must be able to browse -User andy must be able to read the content of the share, if necessary, verfication code is redhat
Configure Multi-User Mount -Share the directory /devops through SMB on the systeml, as required:1. Share name is devops2. The shared directory devops just can be used by clients in domain11.example.com3. The shared directory devop must be able to be browsed4. User silene must can be able to access this share through read, access code is redhat5. User akira must can be able to access this share through read and write, access code is redhat6. 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
SIMULATION -RHCE Test Configuration InstructionsInformation 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 atenorthSystem'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.10The subnet mask is 255.255.255.0Your 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 domainGROUP3.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/rhelPart 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 subnet172.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.Share directories via SMB.Configure the SMB service on the system1.Your SMB server must be a member of the STAFF Working Group.Share the folder /common and the name must be common.Only clients of domain11.example.com can access the common share.Common must be able to browse.User Andy must be able to read the content of the share, if necessary, verification code is redhat.
Mount a NFS Share -Mount a NFS share to system1.domain11.example.com on the system2, as required:1. Mount the /public to the directory /mnt/nfsmount2. Mount the /protected to the directory /mnt/nfssecure, in a security way, key download URL: http://host.domain11.example.com/materials/nfs_client.keytab3. User deepak can creat files on /mnt/nfssecure/project4. These file systemes automatically hang up when the system is started
Cofigure SELINUX -Modify the state of selinux to Enforcing modeUse VIM /etc/selinux -
