Shulou(Shulou.com)05/31 Report--

Today, the editor will share with you the relevant knowledge about what problems you need to pay attention to in server relocation. The content is detailed and the logic is clear. I believe most people still know too much about this, so share this article for your reference. I hope you can get something after reading this article, let's take a look at it.

one

Modify ILO IP

The ILO IP can be modified in the following way, which is the last straw for us to remotely control the server.

Ipmitool lan set 1 ipsrc static

Ipmitool lan set 1 ipaddr 10.129.117.100

Ipmitool lan set 1 netmask 255.255.252.0

Ipmitool lan set 1 defgw ipaddr 10.129.119.254

The general ILO password will be very complex, we can modify as easily as possible, when something goes wrong, it is easy to debug, in any case, at least you have to know the password.

Modify ILO password

# / usr/bin/ipmitool user list 1 | grep root

2 root true true true ADMINISTRATOR

# / usr/bin/ipmitool user set password 2 'xxxx'

two

Modify root password

This step should not be taken lightly. If ILO is accessible and there is no root password, it will be a waste of work. Some password files are restricted, do not take it lightly, the password has not been successfully modified, they do not remember the password, the problem will be very desperate.

Chattr-I / etc/passwd / etc/shadow

Passwd root

three

In the process of server relocation, there is a very important place, that is, the modification of the server IP, we need to pay attention to the gateway, routing configuration, whether there is an external network IP, this information is very important.

/ etc/sysconfig/network-scripts/ifcfg-eth0

/ etc/sysconfig/network-scripts/eth0.route

Route-n

four

Modify firewall configuration

The firewall itself has the state in memory and files. If the firewall information is not saved in time, the firewall rules will change after restart, and the service with normal connection will also have an exception.

/ etc/sysconfig/iptables

five

Modify network security settings

This is easy to miss. If the configuration of these network access is set, the IP address will change, and the services that can be connected will be limited.

/ etc/ssh/sshd_config

six

Database

There may be MySQL,Oracle,MongoDB and other databases on the server, let's be gentle, do not directly use the way of unplugging power, and avoid power outages and outages as much as possible. Actually encountered some cases of MySQL power failure restart, slave library application failure and so on.

In addition, for database connections, try to use domain name resolution. For example, MySQL is configured with / etc/hosts to resolve, and Oracle uses listener.ora,tnsnames.ora with hostname instead of IP. It will be easy to maintain later.

seven

Detect hardware statu

If there is a hardware failure after the server relocation, we can at least know in advance whether there is a hardware problem during the relocation or before the relocation.

You can use metaCli to detect, such as detecting bad blocks

/ opt/MegaRAID/MegaCli/MegaCli64-CfgDsply-a0 | grep Error

Check the status of firmware

/ opt/MegaRAID/MegaCli/MegaCli64-PDList-aALL | grep Firmware

eight

Turn off Zabbix monitoring

In the process of relocation, it is necessary to turn off the alarm and monitoring of Zabbix in advance, or the alarm storm is likely to occur.

These are all the contents of this article "what are the problems you need to pay attention to in server relocation?" Thank you for reading! I believe you will gain a lot after reading this article. The editor will update different knowledge for you every day. If you want to learn more knowledge, please pay attention to the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.