일 | 월 | 화 | 수 | 목 | 금 | 토 |
---|---|---|---|---|---|---|
1 | 2 | 3 | ||||
4 | 5 | 6 | 7 | 8 | 9 | 10 |
11 | 12 | 13 | 14 | 15 | 16 | 17 |
18 | 19 | 20 | 21 | 22 | 23 | 24 |
25 | 26 | 27 | 28 | 29 | 30 | 31 |
- Proxy
- macos
- 로그인불가
- XCP-ng
- ssh key 배포
- pfsense
- miniconda
- x-pack
- 보안양파
- 한글가이드
- PlayBook
- ansible
- Elasticsearch
- GitLab
- G-suite
- Kibana
- hardening
- freebsd
- endpoint security
- proxycfg
- Windows
- Kibana server is not ready yet
- xe guest utilities
- bash
- ELASTIC
- elastic stack
- centos 8
- application security
- docker
- Today
- Total
선 밖에 선 자유인
DHCP failover in Linux 본문
- Primary Server
vi /etc/dhcp/dhcpd.failover
# Failover specific configurations
failover peer “dhcp” {
primary;
address 192.168.10.1;
port 647;
peer address 192.168.10.2;
peer port 647;
max-response-delay 60;
max-unacked-updates 10;
mclt 600;
split 128;
load balance max seconds 3;
}
- Secondary Server
vi /etc/dhcp/dhcpd.failover
failover peer “dhcp” {
secondary;
address 192.168.10.2;
port 647;
peer address 192.168.10.1;
peer port 647;
max-response-delay 60;
max-unacked-updates 10;
load balance max seconds 3;
}
- 두 서버 모두
# vi /etc/dhcp/dhcpd.conf
include “/etc/dhcp/dhcpd.failover”;
network 192.168.10.0 netmask 255.255.0.0 {
option routers 192.168.10.254;
option subnet-mask 255.255.0.0;
option broadcast-address 192.168.10.5.255;
pool {
failover peer “dhcp”;
range 192.168.10.100 192.168.10.4.254;
}
}
# systemctl restart dhcpd (
http://blog.whatgeek.com.pt/2012/03/dhcp-failover-load-balancing-and-synchronization-centos-6/
https://kb.isc.org/article/AA-00502/0/A-Basic-Guide-to-Configuring-DHCP-Failover.html