Production Environment host server deployment Summary
Deploy all the host servers of a new project with colleagues over the past two days, and record the general process.
Environment:
Host model: HP ProLiant DL380 Gen9
Basic configuration: 2.40 GB memory, 2 E5-2630 7200 GHz CPU, 12 4 tb sata rpm hard drive
RAID card: Smart HBA H240ar (supports RAID1, RAID5, RAID50, RAID1 + 0, etc)
In the production environment, host servers are deployed. Generally, the following things need to be done in the data center. Other tasks can be done remotely after the network is connected.
- 1. RAID Planning
- 2. Operating System Installation
- 3. Operating System Configuration
- 4. IP bonding configuration
- 5. Telnet configuration
1. RAID Planning
For all-new hosts, the first thing after power-on is to divide RAID.
Based on actual business needs, select a type that meets the project requirements from RAID5, RAID50, and RAID10.
RAID5 loses the capacity of a disk;
RAID50 loses the capacity of two disks;
Raid 10 loses half of the disk capacity.
The I/O performance of the three is RAID10> RAID50> RAID5.
2. Operating System Installation
Select RHEL or CentOS based on actual project requirements;
RHEL payment;
CentOS is free of charge.
Custom installation, for convenience, you can select all the items under "Basic System", "server", "System Management", "desktop", "application", and "development.
We recommend that you save an ISO image file to the server directory.
dd if=/dev/cdrom of=/root/rhel6.x-x86_64.iso
To facilitate later configuration of local yum sources, you can install software more conveniently and solve dependencies between software packages.
3. Operating System Configuration
Decide based on the actual project requirements:
- Disable system firewall?
- Disable SELinux?
- Disable NetworkManager?
- Enable NTP?
- Enable FTP?
- Whether IP bonding is used
- Whether to install Telnet
The system service class can bechkconfig --list|more
View.
4. IP bonding configuration
Generally, the host server has multiple NICs, and the current server generally has at least four Gigabit NICs;
In general environments (even high-end environments such as RAC), each machine only needs two networks.
In this way, you can bind the real NIC with the IP bonding technology to provide the high availability of the NIC;
For example,
First, disable NetworkManager;
chkconfig NetworkManager offchkconfig --list|grep Net
Vi/etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0HWADDR=34:09:DF:59:EF:A0TYPE=EthernetUUID=7a0aac67-978a-4a64-87d1-6cc1cc8dsaf1ONBOOT=yesBOOTPROTO=noneMASTER=bond0SLAVE=yes
Vi/etc/sysconfig/network-scripts/ifcfg-eth1
DEVICE=eth1HWADDR=34:09:DF:59:EF:A1TYPE=EthernetUUID=ac783077-1b31-44e1-bb34-f1aad774adf3ONBOOT=yesBOOTPROTO=noneMASTER=bond0SLAVE=yes
Vi/etc/sysconfig/network-scripts/ifcfg-bond0
DEVICE=bond0TYPE=EthernetONBOOT=yesBOOTPROTO=noneIPADDR=192.168.1.11NETMASK=255.255.255.128GATEWAY=192.168.1.1IPV6INIT=noUSERCTL=noPEERDNS=yes
Vi/etc/modprobe. conf
alias bond0 bonding options bond0 miimon=100 mode=1
Cat/etc/rc. local
Add the following two lines at the end of the file:
ifenslave bond0 eth0 eth1 route add -net 192.168.1.0 netmask 255.255.255.128 bond0
Restart the host and test it.
5. Telnet configuration
Because Telnet is transmitted in plain text, it is not secure. This tool is not installed by default.
If the project does need it, you must find the rpm package of telnet-server * from the CD.
Directrpm -ivh telnet-server*.rpm
Install it.
Then configure/etc/xinetd.d/telnet
File, comment outdisable=yes
This line, or change yes to no. It is recommended to comment out, which makes it easier to modify.
Restart the xinetd service:
service xinetd restart
In RHEL6.5, if the root user is required to remotely log on via Telnet/etc/securetty
Add
pts/0pts/1pts/2pts/3pts/4pts/5pts/6pts/7pts/8pts/9pts/10pts/11pts/12pts/13pts/14pts/15pts/16pts/17pts/18pts/19pts/20pts/21pts/22pts/23pts/24pts/25pts/26pts/27pts/28pts/29pts/30
In this way, you can use root to remotely Telnet to log on to the host.
This article permanently updates the link address: