Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Linux for Networking Professionals

You're reading from   Linux for Networking Professionals Securely configure and operate Linux network services for the enterprise

Arrow left icon
Product type Paperback
Published in Nov 2021
Publisher Packt
ISBN-13 9781800202399
Length 528 pages
Edition 1st Edition
Languages
Tools
Concepts
Arrow right icon
Author (1):
Arrow left icon
Rob VandenBrink Rob VandenBrink
Author Profile Icon Rob VandenBrink
Rob VandenBrink
Arrow right icon
View More author details
Toc

Table of Contents (20) Chapters Close

Preface 1. Section 1: Linux Basics
2. Chapter 1: Welcome to the Linux Family FREE CHAPTER 3. Chapter 2: Basic Linux Network Configuration and Operations – Working with Local Interfaces 4. Section 2: Linux as a Network Node and Troubleshooting Platform
5. Chapter 3: Using Linux and Linux Tools for Network Diagnostics 6. Chapter 4: The Linux Firewall 7. Chapter 5: Linux Security Standards with Real-Life Examples 8. Section 3: Linux Network Services
9. Chapter 6: DNS Services on Linux 10. Chapter 7: DHCP Services on Linux 11. Chapter 8: Certificate Services on Linux 12. Chapter 9: RADIUS Services for Linux 13. Chapter 10: Load Balancer Services for Linux 14. Chapter 11: Packet Capture and Analysis in Linux 15. Chapter 12: Network Monitoring Using Linux 16. Chapter 13: Intrusion Prevention Systems on Linux 17. Chapter 14: Honeypot Services on Linux 18. Assessments 19. Other Books You May Enjoy

Server and service health checks

One of the issues we discussed in the section on DNS load balancing was health checks. Once you start load balancing, you usually want some method of knowing which servers (and services) are operating correctly. Methods for checking the health of any connection include the following:

  1. Use ICMP to effectively "ping" the target servers periodically. If no pings return with an ICMP echo reply, then they are considered down, and they don't receive any new clients. Existing clients will be spread across the other servers.
  2. Use the TCP handshake and check for an open port (for instance 80/tcp and 443/tcp for a web service). Again, if the handshake doesn't complete, then the host is considered down.
  3. In UDP, you would typically make an application request. For instance, if you are load balancing DNS servers, the load balancer would make a simple DNS query – if a DNS response is received, then the sever is considered...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime