Skip to main content

Network Services - Key concepts

First Hop Redundancy Protocols (FHRP)

HSRP, GLBP, VRRP

HSRP (Hot Standby Router Protocol): Provides redundancy by allowing one router to be active while others are standby. Technical Tip: Always configure preempt to allow a higher priority router to become active automatically when it comes back online. Use authentication to prevent rogue routers from taking over as active routers. Example:

standby 1 ip 10.1.25.22

standby 1 priority 200

standby 1 preempt

standby 1 authentication md5 key-string Cisco

GLBP (Gateway Load Balancing Protocol): Adds load balancing to FHRP by distributing traffic among multiple routers using virtual MAC addresses. Technical Tip: Prioritize the selection of Active Virtual Gateway (AVG) using the priority command, and use authentication for security. Example:

glbp 1 ip 10.1.1.100

glbp 1 priority 255

glbp 1 authentication md5 key-string Cisco

VRRP (Virtual Router Redundancy Protocol): Similar to HSRP but is an open standard. Allows routers to share a virtual IP. Technical Tip: Use object tracking to monitor links, and preempt to automatically select the higher priority router. Example:

vrrp 1 ip 10.1.12.11

vrrp 1 priority 200

vrrp 1 preempt

vrrp 1 authentication md5 Cisco

4.5.1.2 Redundancy using IPv6 RS/RA

Router Solicitation (RS) and Router Advertisement (RA) messages in IPv6 enable devices to discover the best routers for traffic. Technical Tip: Ensure correct configurations for IPv6 redundancy using RS and RA to avoid black holes.

4.5.2 Network Time Protocol (NTP)

Ensures synchronized time across the network devices.

4.5.2.1 Master, Client

Configure NTP to sync time from a master server to clients. Technical Tip: Use authentication to prevent rogue NTP servers from affecting network time synchronization.

4.5.2.2 Authentication

Enable NTP authentication to validate the source of NTP updates. Example:

ntp authenticate

ntp authentication-key 1 md5 cisco123

ntp trusted-key 1

DHCP on Cisco IOS

Client, Server, Relay

DHCP Relay: Relays DHCP requests from clients in one subnet to a DHCP server in another subnet. Technical Tip: Use the ip helper-address command to configure the relay agent.

ip helper-address 192.168.1.1

Options

DHCP options provide additional parameters such as default gateway and DNS server addresses. Technical Tip: Configure necessary DHCP options to ensure proper network configuration for clients.

SLAAC/DHCPv6 Interaction

In IPv6, SLAAC (Stateless Address Autoconfiguration) allows devices to configure their IP address automatically, while DHCPv6 assigns additional network parameters. Technical Tip: Combine SLAAC and DHCPv6 for full IPv6 address and configuration management.

Stateful, Stateless DHCPv6

Stateful DHCPv6 assigns IP addresses and other configuration data, while stateless only provides configuration data. Technical Tip: Use stateful when more control over IP addressing is needed, and stateless for simpler configurations.

DHCPv6 Prefix Delegation

Allows routers to request an IPv6 prefix from a service provider. Technical Tip: Use prefix delegation to dynamically configure and distribute prefixes to downstream routers.

IPv4 Network Address Translation (NAT)

Static NAT, PAT

Static NAT provides a one-to-one mapping of internal IP addresses to external ones. PAT (Port Address Translation) maps many internal addresses to a single external address by using port numbers. Technical Tip: Use static NAT for servers needing constant external access and PAT for regular clients.

ip nat inside source static 192.168.1.10 203.0.113.5

ip nat inside source list 1 interface serial 0 overload

Dynamic NAT, PAT

Dynamic NAT assigns external IPs from a pool, while PAT uses ports to map many internal IPs to one external. Technical Tip: Use dynamic NAT when you need multiple internal devices to access the internet without fixed IPs.

Policy-Based NAT, PAT

Policy-based NAT translates traffic based on specific policies, like source or destination. Technical Tip: Use ACLs to control which traffic gets translated and ensure proper route mappings for translated IPs.

VRF-Aware NAT, PAT

Enables NAT within Virtual Routing and Forwarding (VRF) instances, allowing different routing tables to use NAT separately. Technical Tip: Use VRF-aware NAT when deploying NAT in multi-VRF environments.

IOS-XE VRF-Aware Software Infrastructure (VASI) NAT

Allows virtual routing tables to perform NAT, enabling segregation of NAT rules across VRF instances.

Key Technical Tips:

  • Use object tracking with FHRPs like HSRP, VRRP, and GLBP to ensure seamless failover based on upstream link status.
  • Configure NTP authentication to prevent time-sync vulnerabilities.
  • Apply stateful DHCPv6 when full control over IP allocation is required and stateless for lighter configurations.
  • For NAT, use PAT to conserve public IP addresses and policy-based NAT to selectively translate traffic based on policies.
Labels:

Comments

Post a Comment

Popular posts from this blog

Basic MPLS BGP and L3VPN Lab Setup

In this lab, we’ve set up a basic MPLS, BGP, and L3VPN environment, which is a great foundation for understanding how service providers build scalable networks. The lab uses the EVE-NG simulator along with Router IOS C7200-ADVENTERPRISEK9-M, Version 15.2(4)M8 to emulate a realistic MPLS environment. Below is a summary of the key components and roles of each router in the lab. MPLS Core Routers : The MPLS core consists of the routers responsible for label switching and forwarding customer traffic through the network: PE1 (Provider Edge 1) : Connects customer networks to the MPLS core and handles both MPLS and BGP routing. It also hosts VRF (Virtual Routing and Forwarding) instances for customers. PE2 (Provider Edge 2) : Functions similarly to PE1, connecting another customer network to the MPLS core. P1 (Core Router 1) and P2 (Core Router 2) : These routers serve as MPLS core routers and handle label switching but do not store or process customer routes directly. They simply f
Post a Comment
Read more

OSPF Adjacency Stuck in EXSTART on Cisco IOS XR – Issue and Solution

In a recent lab setup using Cisco IOS XR on EVE-NG, I faced a common but frustrating issue with OSPF adjacencies getting stuck in the EXSTART state. After spending considerable time troubleshooting interface MTUs and configurations, I discovered that the root cause was related to the virtual network interface type being used. This post outlines the issue, troubleshooting steps, and the eventual solution that got everything working. Issue: While configuring OSPF between two routers running Cisco IOS XR in my lab, OSPF adjacencies were getting stuck in the EXSTART state. I verified that interface configurations, MTU settings, and OSPF parameters were correct, but the problem persisted. I tried adjusting the MTU size, using the mtu-ignore command, and even checked for ACLs, but nothing seemed to resolve the issue. Troubleshooting Steps: MTU Settings: I started by verifying that both sides of the OSPF adjacency had matching MTUs. I used the default MTU and even tried different values wit
Post a Comment
Read more

How to Properly Clone an EVE-NG Lab with Configurations

Cloning labs in EVE-NG is a great way to duplicate setups and expand or experiment on a new copy without affecting the original lab. However, if not done correctly, the cloned lab may only copy the topology without configurations. In this guide, I’ll show you how to properly clone a lab in EVE-NG with all configurations using the EVE-NG GUI . Follow these steps to ensure that both the topology and router configurations are retained when cloning your lab. Steps to Clone an EVE-NG Lab with Configurations Save Running Configuration on All Devices In your original lab, make sure all devices have their configurations saved to NVRAM. Go into the CLI of each router and run the command: copy running-config startup-config Export All Configurations (CFGs) On the left sidebar in the EVE-NG Web UI , click on the "More Actions" option. Then select "Export all CFGs" . This step exports the configurations of all devices in the lab. Shutdown All Devices After exporting the confi
Post a Comment
Read more