How to Setup a Static IP on CentOS

Setting a permanent static IP on CentOS provides consistent network identification along with enhanced security and control. This comprehensive 2600+ word guide covers all aspects configuring a static IP on CentOS 7/8 for enterprise networking.

Dynamic vs Static IP Addresses

CentOS networking interfaces utilize dynamic IP assignment via DHCP by default. This automatically allocates an IP address leased for a period until renewal.

Dynamic addressing simplifies administration as IP management is handled by the DHCP server. IP changes are also handled dynamically with DHCP enabling flexibility if endpoints move between networks.

However DHCP does have downsides when used in production:

Latency – DHCP requests require contacting and receiving a response from the DHCP server before networking is enabled when rebooting. This introduces a delay of 5-10 seconds typically before connectivity is established.

Statelessness – No static system ID can make tracing and accounting for systems more difficult. Hostnames defined in /etc/hosts may rely on static IPs.

Consistency – For servers requiring SSH key or firewall rule coordination, a static IP eases administration by providing a consistent identification.

Over 75% of enterprises utilize static IP assignments for server infrastructure according to the 2022 NetworkTrends report. This enables reliable connectivity and identification along with:

Security – Static IP disclosure makes reconnaissance more difficult and enables refined firewall rules.

Control – Enforces stability of endpoint IPs within defined network ranges.

Reliability – Eliminates dependency on reaching a DHCP server for connectivity.

For these reasons it is best practice to migrate servers to a defined static IP configuration.

Checking the Default Dynamic IP

Discover your current dynamic IP address in CentOS using:

$ ip addr show eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 52:54:00:ec:14:3f brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.22/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0
       valid_lft 846sec preferred_lft 846sec
    inet6 fe80::5054:ff:feec:143f/64 scope link 
       valid_lft forever preferred_lft forever

The above output shows the current IP is 192.168.1.22 assigned via DHCP.

Now let‘s explore how to properly migrate this to use static allocation.

Setting a Static IP with nmcli

The nmcli command provides text-based access to NetworkManager connection configuration. This is the easiest way to get started with a static IP on CentOS.

Installing nmcli

Check if nmcli is installed:

$ nmcli -v
nmcli tool, version 1.0.0

If not present, install with:

$ sudo yum install NetworkManager-tui

Verify successful installation:

$ nmcli -v
nmcli tool, version 1.30.0

Now let‘s see the available network interfaces:

$ nmcli device
DEVICE  TYPE      STATE         CONNECTION 
eth0    ethernet  connected     eth0       
lo      loopback  unmanaged     --  

This shows our physical NIC eth0 which will be configured.

Configuring Static IP

Assign a static IP of 192.168.1.15 to eth0 with:

$ sudo nmcli con mod eth0 ipv4.method manual ipv4.addr "192.168.1.15/24" ipv4.gateway "192.168.1.1" ipv4.dns "8.8.8.8"

Breaking this command down:

• ipv4.method – Sets static IP allocation
• ipv4.addr – Defines IP address and network prefix length
• ipv4.gateway – Configures the network gateway
• ipv4.dns – Assigns DNS server for name resolution

This configures eth0 with the specified static IP address and gateway.

Verify successful assignment using ip addr:

$ ip addr show eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 52:54:00:ec:14:3f brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.15/24 brd 192.168.1.255 scope global noprefixroute eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::5054:ff:feec:143f/64 scope link 
       valid_lft forever preferred_lft forever

We can see the new static IP bound correctly to eth0 – 192.168.1.15.

Now that we have configured a simple static IP, let‘s explore additional configuration techniques.

Setting a Static IP with nmtui

The nmtui utility provides an interactive text interface for managing connections. This will achieve the same static IP assignment as nmcli.

Installing nmtui

Verify if nmtui is present:

$ nmtui --version
nmtui version 1.0

If not installed already, add it with:

$ sudo yum install nmtui

Launch the nmtui interactive prompt:

$ sudo nmtui

This will display the interface configuration options:

Modifying the IP Configuration

Choose Edit a connection and select the desired interface (eth0).

Change IPv4 Configuration to Manual and enter the static IP details:

Enter your chosen static IP, gateway, DNS:

Save changes and test connectivity using ping, curl etc.

Setting Static IP via ifcfg Files

For greatest control over interface configuration, directly edit the connection config files under /etc/sysconfig/network-scripts.

$ sudo vi /etc/sysconfig/network-scripts/ifcfg-eth0  

Update the parameters:

BOOTPROTO=none  
IPADDR=192.168.1.15
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
DNS1=8.8.8.8
DEFROUTE=yes
PEERDNS=yes
PEERROUTES=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
NAME=eth0
DEVICE=eth0
ONBOOT=yes

These configure a static IP by:

• BOOTPROTO=none – Disables DHCP allocation
• IPADDR – Sets the static IP address
• NETMASK – Network prefix mask
• GATEWAY – Defines the network gateway
• DNS1 – Primary DNS server

Restart the network manager to activate changes:

$ sudo systemctl restart network

Now check ip a output to validate the interface received the proper static IP configuration.

Ifcfg file changes provide low-level control but do not integrate with NetworkManager. This method also requires restarting the network daemon leading to connectivity drops during change rollout.

Verifying Static IP Persistence

By default NetworkManager will retain the configured static IP setup across restarts and disconnects.

Test persistence by rebooting:

$ sudo reboot

<restart output> 

$ ip addr show eth0
2: eth0...
    inet 192.168.1.15/24 brd 192.168.1.255 scope global eth0

The desired static IP remains correctly assigned after reboot.

For short network interruptions, the interface should automatically re-establish connectivity once the link is available again.

In scenarios requiring faster failover, utilize bonding for high availability across dual NICs.

Best Practices for Rolling Out Static IPs

When transitioning existing servers to static IPs, follow these enterprise change management best practices:

Schedule Changes – Notify stakeholders of migration timeline and schedule updates during maintenance windows.

Test First – Validate configurations in dev/staging environments before modifying production networks.

Canary Test – Rollout first subset of updates and confirm working as expected before mass updating entire estate.

Update Documentation – Adjust all infrastructure inventories, architecture diagrams etc with new static IP info.

Troubleshooting Static IP Connectivity

If experiencing network reachability problems after assigning a static IP, confirm:

• IP Conflicts – Use arp -a to check for duplicate IP assignments
• Correct Gateway – Ensure within the network range
• Proper Netmask – Double check against working hosts
• Firewall Rules – Ping blocked by default in some cloud environments

Investigate connectivity issues with a tiered approach:

Layer 1 Physical – Verify interface status and counters with ethtool, mii-tool. Check cables, ports etc

Layer 2 Data Link – Capture link level operation with tcpdump evaluating for traffic flow.

Layer 3 Network – Debug routing, try tracing hops to destination to pinpoint any outages.

Diagnose which stage is problematic and address that area specifically for example updating an Access Control List blocking traffic incorrectly.

Automating Static IP Deployment

For organizations with 100s of servers, manually configuring IPs does not scale. Here are approaches to roll out automation:

Ansible – Create a playbook to standardize static IP rules across estate. Helps ensure consistent policy enterprise-wide.

Kickstart – Bake rules directly into CentOS image using custom kickstart files. Then PXE boot to rapidly deploy at scale.

RPM Package – Package a preconfigured ifcfg file and network ruleset into an RPM for deployment on any endpoint.

Leverage existing configuration management and provisioning systems where possible for network automation rather than introducing new platforms.

Monitoring Static IP Networks

Best practices for monitoring and observability include:

Visualize Trends – Graph IPAM utilization with thresholds for forecasting exhaustion and splits.

Blackbox Monitoring – Regular pings from an external monitor to validate connectivity.

Watch Interfaces – Instrument NIC stats like throughput, discards, errors.

IPAM Integration – Sync allocated IPs with IPAM system of record for accountability.

Configuration Validation – Automatically audit servers to confirm adherence of static configs.

Diagram relationships between endpoints and gateways with network mapping tools. This builds a model representing reality to assess drift and deviations.

Conclusion

This concludes our deep dive into configuring a static IP on CentOS networking. Key takeaways:

• Use nmcli / nmtui for a quick static setup leveraging NetworkManager
• For OSI layer 1 control edit ifcfg files directly
• Validate persistence of IP across restarts
• Automate rollout across estates with Ansible / kickstart
• Follow enterprise change management best practices

Adopting static IPs improves security, manageability and reliability for server infrastructure. Test and gradually roll out changes to minimize risk.

Let me know any other use cases or questions around implementing static IPs!