Load Balancing
EIGRP Load Balancing
EIGRP supports both equal-cost and unequal-cost load balancing, allowing traffic to be distributed across multiple paths for improved bandwidth utilization and redundancy.
Types of Load Balancing
Equal-Cost
Default Behavior
Routes with identical metrics
Up to 16 paths (default 4)
Unequal-Cost
Variance Command
Routes with different metrics
Must satisfy feasibility condition
Equal-Cost Load Balancing
By default, EIGRP performs equal-cost load balancing across up to 4 paths with identical metrics. This can be adjusted using the maximum-paths command.
Equal-Cost Configuration
router eigrp 100
maximum-paths 6 ! Allow up to 6 equal-cost paths
! Default is 4, maximum is 16
Equal-Cost Example
Network Topology
Router A
/|\
/ | \
/ | \
Router B C D --- Destination 192.168.1.0/24
(Cost 100) (Cost 100) (Cost 100)
Path | Next Hop | Metric | Status |
---|---|---|---|
Path 1 | Router B | 100 | Successor (Active) |
Path 2 | Router C | 100 | Successor (Active) |
Path 3 | Router D | 100 | Successor (Active) |
Unequal-Cost Load Balancing
EIGRP's unique feature allows load balancing across paths with different metrics using the variance command. The variance multiplier determines which paths qualify for load balancing.
Variance Formula
Qualifying Metric ≤ (Best Metric × Variance)
AND the path must satisfy the feasibility condition (RD < FD)
Unequal-Cost Configuration
router eigrp 100
variance 2 ! Allow paths up to 2x the best metric
maximum-paths 6 ! Allow up to 6 total paths
Unequal-Cost Example
Network Scenario
Router A to 192.168.1.0/24:
- Path 1 via Router B: Metric 100 (Best path)
- Path 2 via Router C: Metric 150 (1.5x best metric)
- Path 3 via Router D: Metric 250 (2.5x best metric)
With variance 2:
- Path 1: 100 ≤ (100 × 2) = 200 ✓ Qualifies
- Path 2: 150 ≤ (100 × 2) = 200 ✓ Qualifies
- Path 3: 250 ≤ (100 × 2) = 200 ✗ Does not qualify
Traffic Distribution
EIGRP distributes traffic proportionally to the inverse of the path metrics. Lower metric paths carry more traffic.
Path | Metric | Inverse | Traffic Share | Percentage |
---|---|---|---|---|
Path 1 | 100 | 1/100 = 0.01 | 6 | 60% |
Path 2 | 150 | 1/150 = 0.0067 | 4 | 40% |
Load Balancing Verification
Verification Commands
# Check routing table
show ip route 192.168.1.0
# View topology table
show ip eigrp topology
# Check traffic share
show ip route eigrp
Sample Output
D 192.168.1.0/24 [90/100]
via 10.1.1.2, GigabitEthernet0/1
[90/150] via 10.2.2.2, GigabitEthernet0/2
# Traffic share count shown
Load Balancing Best Practices
Optimization Guidelines
- Conservative Variance: Use variance 2-3 to avoid suboptimal paths
- Monitor Utilization: Check link utilization after enabling load balancing
- Consider Bandwidth: Ensure paths can handle distributed traffic
- Test Thoroughly: Verify application performance with load balancing
- Document Changes: Keep track of variance and maximum-paths settings
Common Issues
Load Balancing Pitfalls
- Per-packet vs Per-destination: Default is per-destination load balancing
- Feasibility Condition: Unequal paths must still satisfy RD < FD
- High Variance: Too high variance may include very poor paths
- Application Impact: Some applications sensitive to path changes
- Bandwidth Mismatch: Overloading lower bandwidth paths
Route Summarization
EIGRP Route Summarization
Route summarization reduces routing table size, improves convergence time, and limits query scope. EIGRP supports both automatic and manual summarization techniques.
Types of Summarization
Auto-Summary
Legacy Feature
Classful boundary summarization
Disabled by default
Manual Summary
Recommended Method
Interface-level configuration
Full administrator control
Manual Route Summarization
Manual summarization is configured on interfaces and provides precise control over summary routes. It's the preferred method for modern networks.
Manual Summary Configuration
interface GigabitEthernet0/0
ip summary-address eigrp [as-number] [network] [mask] [admin-distance]
# Example:
interface GigabitEthernet0/0
ip summary-address eigrp 100 192.168.0.0 255.255.240.0
# Summarizes 192.168.0.0/20 (192.168.0.0 - 192.168.15.255)
Summarization Benefits
Benefit | Description | Impact |
---|---|---|
Reduced Table Size | Fewer routes in routing tables | Lower memory usage |
Query Boundary | Queries stop at summary boundaries | Prevents SIA conditions |
Faster Convergence | Less computation required | Improved network stability |
Bandwidth Savings | Fewer routing updates | Reduced network overhead |
Summarization Example
Network Scenario
Regional Office Networks:
192.168.0.0/24 - Branch 1
192.168.1.0/24 - Branch 2
192.168.2.0/24 - Branch 3
192.168.3.0/24 - Branch 4
Summary Route: 192.168.0.0/22
Covers: 192.168.0.0 - 192.168.3.255
Regional Router Configuration
# Regional router advertising to core
interface Serial0/0
description Link to Core Network
ip summary-address eigrp 100 192.168.0.0 255.255.252.0
# Advertises single /22 summary instead of four /24 routes
Null0 Route Creation
When a summary is configured, EIGRP automatically creates a Null0 route to prevent routing loops for destinations within the summary range that don't exist.
Automatic Null0 Route
# Show routing table after summary configuration
show ip route
# Output shows:
D 192.168.0.0/22 is a summary, 00:05:23, Null0
D 192.168.0.0/24 [90/2172416] via 10.1.1.2, 00:05:20, Serial0/1
D 192.168.1.0/24 [90/2172416] via 10.1.2.2, 00:05:18, Serial0/2
Query Boundary Effect
Summary routes act as query boundaries, preventing DUAL queries from propagating beyond the summary point. This is crucial for network stability.
Query Propagation with Summarization
Without Summary
Queries propagate
through entire network
With Summary
Queries stop at
summary boundary
Result
Reduced SIA
conditions
Benefit
Improved network
stability
Hierarchical Summarization
Multi-Level Summary Example
Receives: 10.0.0.0/8 (Company-wide summary)
Advertise: 10.1.0.0/16, 10.2.0.0/16, 10.3.0.0/16
Individual: 10.1.1.0/24, 10.1.2.0/24, etc.
Summarization Best Practices
Design Guidelines
- Plan Address Space: Design hierarchical addressing for effective summarization
- Strategic Placement: Summarize at logical network boundaries
- Avoid Over-Summarization: Don't create overly broad summaries
- Document Summaries: Maintain clear documentation of summary routes
- Monitor Null0: Watch for traffic to Null0 indicating routing issues
Verification Commands
Summary Verification
# Check summary routes
show ip eigrp topology summary
# View interface summaries
show ip eigrp interfaces detail
# Check Null0 routes
show ip route null0
Troubleshooting
# Debug summary creation
debug eigrp summary
# Monitor route advertisements
debug eigrp packets update
# Check query propagation
debug eigrp packets query
Common Summarization Issues
Potential Problems
- Black Holes: Traffic to non-existent subnets within summary range
- Suboptimal Routing: Less specific paths due to summarization
- Discontiguous Networks: Summary may include non-adjacent networks
- Load Balancing Issues: Unequal distribution due to summary metrics
Stub Routing
EIGRP Stub Routing
Stub routing optimizes EIGRP behavior in hub-and-spoke topologies by preventing queries to stub routers and reducing unnecessary DUAL computations.
What is EIGRP Stub?
EIGRP stub routing prevents a router from becoming a transit point for other routers. Stub routers receive routes but don't forward queries, improving network stability and reducing bandwidth usage.
Stub Router Behavior
Query Handling
Never receives queries from neighbors
Route Advertisement
Limited route advertisement options
Transit Traffic
Doesn't forward traffic between neighbors
SIA Prevention
Reduces Stuck-in-Active conditions
Stub Configuration Options
Basic Stub Configuration
router eigrp 100
eigrp stub [connected] [summary] [static] [redistributed] [receive-only]
# Common configurations:
router eigrp 100
eigrp stub connected summary # Default behavior
router eigrp 100
eigrp stub receive-only # Receive routes only
Stub Options Explained
Option | Description | Use Case |
---|---|---|
connected | Advertise connected networks | Default, advertise local subnets |
summary | Advertise summary routes | Default, allow manual summaries |
static | Advertise static routes | When redistributing static routes |
redistributed | Advertise redistributed routes | When redistributing other protocols |
receive-only | Don't advertise any routes | Pure receive-only stub |
Typical Stub Deployment
Hub-and-Spoke Topology
Core Network
|
[Hub Router]
/ | \
/ | \
[Stub A] [Stub B] [Stub C]
| | |
Branch A Branch B Branch C
Hub Router Configuration
# Hub router - normal EIGRP configuration
router eigrp 100
network 10.0.0.0 0.255.255.255
# No stub configuration needed
Stub Router Configuration
# Branch router - stub configuration
router eigrp 100
network 192.168.1.0 0.0.0.255
network 10.1.1.0 0.0.0.3
eigrp stub connected summary
Query Behavior with Stubs
Query Processing
Without Stub
Hub queries
all neighbors
With Stub
Hub skips
stub routers
Result
Faster
convergence
Benefit
Reduced
SIA risk
Leak-Map Configuration
Leak-maps allow stub routers to advertise specific routes even when using receive-only mode.
Leak-Map Example
# Create access list for leaked routes
access-list 10 permit 192.168.100.0 0.0.0.255
# Create route-map
route-map LEAK-ROUTES permit 10
match ip address 10
# Apply leak-map to stub configuration
router eigrp 100
eigrp stub receive-only
eigrp stub leak-map LEAK-ROUTES
Stub Verification
Verification Commands
# Check stub status
show ip eigrp neighbors detail
# View EIGRP configuration
show running-config | section eigrp
# Check advertised routes
show ip eigrp topology
Sample Output
Router# show ip eigrp neighbors detail
EIGRP neighbor is 10.1.1.1 on Serial0/0
Version 12.4/1.2, Retrans: 0, Retries: 0
Stub Peer Advertising (CONNECTED SUMMARY) Routes
Stub Benefits
Advantages of Stub Routing
- Reduced Queries: Hub doesn't query stub routers
- Faster Convergence: Less computation during network changes
- SIA Prevention: Eliminates SIA conditions from stub routers
- Bandwidth Savings: Reduced query/reply traffic
- Simplified Topology: Clearer network hierarchy
Stub Limitations
Considerations
- Transit Restriction: Cannot be transit point between neighbors
- Redundancy Impact: May affect backup path availability
- Route Advertisement: Limited route advertisement options
- Topology Constraints: Best suited for hub-and-spoke designs
Route Filtering
EIGRP Route Filtering
Route filtering controls which routes are advertised, received, or installed in the routing table. EIGRP supports multiple filtering mechanisms for granular control.
Types of Route Filtering
Distribute Lists
Access List Based
Filter based on network addresses
In/Out direction control
Route Maps
Advanced Filtering
Multiple match criteria
Modify route attributes
Prefix Lists
Subnet Mask Aware
Match network and mask length
More precise than ACLs
Administrative Distance
Route Preference
Control route selection
Per-route basis
Distribute Lists
Distribute lists use access lists to filter routes in either inbound or outbound direction on specific interfaces or for all EIGRP neighbors.
Basic Distribute List Configuration
# Create access list
access-list 10 deny 192.168.100.0 0.0.0.255
access-list 10 permit any
# Apply distribute list
router eigrp 100
distribute-list 10 out GigabitEthernet0/0 # Outbound on interface
distribute-list 10 in # Inbound from all neighbors
Distribute List Directions
Direction | Purpose | Effect | Usage |
---|---|---|---|
Inbound (in) | Filter received routes | Prevents installation in routing table | Control what routes are learned |
Outbound (out) | Filter advertised routes | Prevents advertisement to neighbors | Control what routes are shared |
Route Maps for Advanced Filtering
Route maps provide sophisticated filtering capabilities with multiple match criteria and the ability to modify route attributes.
Route Map Configuration
# Create route map
route-map EIGRP-FILTER permit 10
match ip address 20
set metric 1000 100 255 1 1500
route-map EIGRP-FILTER deny 20
match ip address 30
# Apply to EIGRP
router eigrp 100
distribute-list route-map EIGRP-FILTER out
Route Map Match Criteria
Match Command | Purpose | Example |
---|---|---|
match ip address | Match networks via ACL | match ip address 10 |
match ip route-source | Match advertising router | match ip route-source 15 |
match metric | Match route metric | match metric 1000 |
match interface | Match next-hop interface | match interface Serial0/0 |
Prefix Lists
Prefix lists provide more precise filtering than standard access lists by matching both the network address and subnet mask length.
Prefix List Configuration
# Create prefix list
ip prefix-list BRANCH-NETWORKS seq 5 permit 192.168.0.0/16 le 24
ip prefix-list BRANCH-NETWORKS seq 10 deny 0.0.0.0/0 le 32
# Apply to EIGRP
router eigrp 100
distribute-list prefix BRANCH-NETWORKS out GigabitEthernet0/0
Prefix List Operators
Operator | Meaning | Example | Matches |
---|---|---|---|
le (less equal) | Mask length ≤ value | 192.168.0.0/16 le 24 | /16 through /24 masks |
ge (greater equal) | Mask length ≥ value | 10.0.0.0/8 ge 16 | /16 through /32 masks |
eq (equal) | Exact mask length | 172.16.0.0/12 eq 24 | Only /24 masks |
Administrative Distance Filtering
Modify administrative distance for specific routes to control route preference and selection.
Distance Configuration
# Set administrative distance for specific routes
router eigrp 100
distance 200 10.1.1.1 0.0.0.0 20 # AD=200 for routes from 10.1.1.1 matching ACL 20
distance 150 0.0.0.0 255.255.255.255 # AD=150 for all other EIGRP routes
Filtering Examples
Example 1: Block Specific Networks
Block Guest Networks
# Block guest network advertisements
access-list 25 deny 192.168.200.0 0.0.0.255
access-list 25 permit any
router eigrp 100
distribute-list 25 out
# Prevents advertising guest networks to any neighbor
Example 2: Allow Only Specific Subnets
Permit Production Networks Only
# Allow only production networks
ip prefix-list PRODUCTION-ONLY seq 5 permit 10.100.0.0/16 le 24
ip prefix-list PRODUCTION-ONLY seq 10 permit 10.200.0.0/16 le 24
ip prefix-list PRODUCTION-ONLY seq 15 deny 0.0.0.0/0 le 32
router eigrp 100
distribute-list prefix PRODUCTION-ONLY in
Example 3: Modify Route Metrics
Increase Backup Path Metrics
# Make backup paths less preferred
access-list 30 permit 192.168.50.0 0.0.0.255
route-map BACKUP-PATHS permit 10
match ip address 30
set metric 10000 1000 255 1 1500
route-map BACKUP-PATHS permit 20
router eigrp 100
distribute-list route-map BACKUP-PATHS in Serial0/1
Verification Commands
Filter Verification
# Check applied distribute lists
show ip protocols
# View prefix lists
show ip prefix-list
# Check route maps
show route-map
Route Analysis
# Check filtered routes
show ip eigrp topology
# Verify routing table
show ip route eigrp
# Debug filtering
debug ip routing
Filtering Best Practices
Implementation Guidelines
- Use Prefix Lists: Prefer prefix lists over ACLs for route filtering
- Document Filters: Maintain clear documentation of all filtering rules
- Test Thoroughly: Verify connectivity after implementing filters
- Start Permissive: Begin with allow-all and gradually restrict
- Monitor Impact: Watch for unintended filtering effects
Common Filtering Mistakes
Avoid These Issues
- Implicit Deny: Remember ACLs have implicit deny at the end
- Direction Confusion: Carefully consider in vs out filtering
- Wildcard Mask Errors: Use correct wildcard masks in ACLs
- Over-Filtering: Don't block necessary routing information
- Missing Permits: Ensure legitimate routes can pass
Authentication
EIGRP Authentication
EIGRP authentication provides security by validating the identity of EIGRP neighbors, preventing unauthorized routers from participating in the routing domain.
Authentication Methods
MD5 Authentication
Legacy Method
Uses MD5 hash algorithm
Supports key rotation
SHA Authentication
Modern Method
Uses SHA-256 algorithm
More secure than MD5
MD5 Authentication Configuration
MD5 authentication uses a shared key to authenticate EIGRP packets. Each router must have matching key configurations.
MD5 Authentication Setup
# Configure key chain
key chain EIGRP-KEYS
key 1
key-string MySecretKey123
accept-lifetime 00:00:00 Jan 1 2024 infinite
send-lifetime 00:00:00 Jan 1 2024 infinite
# Apply to interface
interface GigabitEthernet0/0
ip authentication mode eigrp 100 md5
ip authentication key-chain eigrp 100 EIGRP-KEYS
Key Chain Components
Component | Purpose | Configuration |
---|---|---|
Key Chain | Container for authentication keys | key chain [name] |
Key ID | Unique identifier for each key | key [number] |
Key String | Actual authentication password | key-string [password] |
Lifetime | Time period for key validity | accept/send-lifetime |
SHA Authentication Configuration
SHA authentication provides stronger security than MD5 and is recommended for new deployments.
SHA Authentication Setup
# Configure key chain with SHA
key chain EIGRP-SHA-KEYS
key 1
key-string SecurePassword456
cryptographic-algorithm hmac-sha-256
accept-lifetime 00:00:00 Jan 1 2024 infinite
send-lifetime 00:00:00 Jan 1 2024 infinite
# Apply to interface
interface GigabitEthernet0/0
ip authentication key-chain eigrp 100 EIGRP-SHA-KEYS
Key Rotation Strategy
Key rotation allows for secure key changes without disrupting EIGRP adjacencies by overlapping key lifetimes.
Key Rotation Configuration
key chain EIGRP-ROTATION
key 1
key-string OldKey123
send-lifetime 00:00:00 Jan 1 2024 23:59:59 Mar 31 2024
accept-lifetime 00:00:00 Jan 1 2024 23:59:59 Apr 30 2024
key 2
key-string NewKey456
send-lifetime 00:00:00 Mar 1 2024 infinite
accept-lifetime 00:00:00 Mar 1 2024 infinite
Key Rotation Process
Seamless Key Transition
Phase 1
Old key active
for send/accept
Phase 2
Both keys active
overlap period
Phase 3
New key for send
old key for accept
Phase 4
New key only
old key expired
Authentication Verification
Verification Commands
# Check neighbor authentication
show ip eigrp neighbors detail
# View interface authentication
show ip eigrp interfaces detail
# Check key chain configuration
show key chain
Debug Authentication
# Debug authentication issues
debug eigrp packets
debug ip eigrp neighbor
# Check authentication failures
show logging | include AUTH
Common Authentication Issues
Troubleshooting Authentication
- Key Mismatch: Ensure identical key strings on both neighbors
- Clock Synchronization: Verify system clocks for lifetime validity
- Interface Configuration: Authentication must be on correct interfaces
- AS Number Match: Authentication configuration must reference correct AS
- Partial Deployment: All neighbors on segment must use authentication
Authentication Best Practices
Security Guidelines
- Use Strong Keys: Employ complex, long passwords
- Regular Rotation: Change keys periodically for security
- Prefer SHA: Use SHA authentication over MD5 when possible
- Secure Storage: Protect key configurations and backups
- Monitor Authentication: Watch for authentication failures
- Document Keys: Maintain secure documentation of key schedules
Bandwidth Tuning
EIGRP Bandwidth Optimization
Bandwidth tuning optimizes EIGRP's use of network resources, controls convergence behavior, and ensures optimal route selection through proper interface parameter configuration.
EIGRP Bandwidth Parameters
Interface Bandwidth
Metric Calculation
Affects EIGRP route metrics
Should match actual speed
EIGRP Bandwidth Percent
Protocol Utilization
Limits EIGRP traffic usage
Default 50% of interface bandwidth
Hello Timers
Convergence Speed
Affects failure detection
Bandwidth-dependent defaults
Delay Settings
Path Selection
Secondary metric component
Fine-tune route preference
Interface Bandwidth Configuration
The bandwidth command sets the interface bandwidth value used by EIGRP for metric calculations. This should accurately reflect the actual link speed.
Bandwidth Configuration
# Set interface bandwidth (in kilobits per second)
interface Serial0/0
bandwidth 1544 # T1 link speed
interface Serial0/1
bandwidth 256 # 256 Kbps link
interface GigabitEthernet0/0
bandwidth 1000000 # Gigabit Ethernet
Common Bandwidth Values
Interface Type | Speed | Bandwidth Command | EIGRP Metric Impact |
---|---|---|---|
56K Serial | 56 Kbps | bandwidth 56 | High metric (slow path) |
T1 | 1.544 Mbps | bandwidth 1544 | Medium metric |
E1 | 2.048 Mbps | bandwidth 2048 | Medium metric |
Ethernet | 10 Mbps | bandwidth 10000 | Low metric (fast path) |
Fast Ethernet | 100 Mbps | bandwidth 100000 | Very low metric |
EIGRP Bandwidth Percentage
Control how much interface bandwidth EIGRP can use for its own traffic (hellos, updates, queries, replies).
Bandwidth Percentage Configuration
# Limit EIGRP to 25% of interface bandwidth
interface Serial0/0
ip bandwidth-percent eigrp 100 25
# Allow EIGRP to use 75% of interface bandwidth
interface GigabitEthernet0/0
ip bandwidth-percent eigrp 100 75
Bandwidth Percentage Guidelines
Link Type | Recommended % | Reasoning | Considerations |
---|---|---|---|
Low-speed WAN | 25-50% | Preserve bandwidth for data | Slower convergence acceptable |
High-speed LAN | 50-90% | Fast convergence needed | Bandwidth not constrained |
Backup Links | 10-25% | Minimize overhead | May be activated under stress |
Voice/Video Links | 25-35% | QoS requirements | Real-time traffic priority |
Hello Timer Tuning
Adjust hello intervals and hold times to optimize failure detection speed vs. bandwidth usage.
Hello Timer Configuration
# Faster failure detection on critical links
interface GigabitEthernet0/0
ip hello-interval eigrp 100 2 # Send hellos every 2 seconds
ip hold-time eigrp 100 6 # Declare neighbor dead after 6 seconds
# Slower timers for bandwidth conservation
interface Serial0/0
ip hello-interval eigrp 100 30 # Send hellos every 30 seconds
ip hold-time eigrp 100 90 # Hold time 90 seconds
Timer Relationships
Timer Guidelines
Hold Time = 3 × Hello Interval
This ratio provides reliable neighbor detection while minimizing false failures.
Delay Tuning for Path Selection
Use delay modification to influence EIGRP path selection without affecting bandwidth calculations.
Delay Configuration
# Increase delay to make path less preferred
interface Serial0/1
delay 5000 # 50ms delay (value in tens of microseconds)
# Primary path with lower delay
interface Serial0/0
delay 2000 # 20ms delay (more preferred)
Bandwidth Tuning Example
Network Scenario
Router A --- T1 (Primary) --- Router B
| |
\-- 256K (Backup) ----------/
Goal: Optimize primary path, limit backup usage
Router A Configuration
# Primary T1 link optimized for performance
interface Serial0/0
description Primary T1 to Router B
bandwidth 1544
ip bandwidth-percent eigrp 100 50
ip hello-interval eigrp 100 5
ip hold-time eigrp 100 15
# Backup link optimized for minimal overhead
interface Serial0/1
description Backup 256K to Router B
bandwidth 256
ip bandwidth-percent eigrp 100 25
ip hello-interval eigrp 100 30
ip hold-time eigrp 100 90
delay 5000 # Make less preferred
Quality of Service Integration
Coordinate EIGRP bandwidth usage with QoS policies to ensure routing protocol doesn't interfere with critical applications.
QoS and EIGRP Coordination
# Reserve bandwidth for EIGRP in QoS policy
policy-map WAN-QOS
class EIGRP-TRAFFIC
bandwidth 64 # Reserve 64K for EIGRP
class VOICE
priority 256 # Voice gets priority
class class-default
fair-queue
# Limit EIGRP to reserved bandwidth
interface Serial0/0
ip bandwidth-percent eigrp 100 25 # 25% of 256K = 64K
Verification and Monitoring
Bandwidth Verification
# Check interface bandwidth settings
show interface brief
show ip eigrp interfaces detail
# Monitor EIGRP traffic
show ip eigrp traffic
# Check hello timers
show ip eigrp neighbors detail
Performance Monitoring
# Monitor interface utilization
show interface Serial0/0 | include load
# Check convergence times
show ip eigrp events
# Analyze route metrics
show ip eigrp topology all-links
Bandwidth Tuning Best Practices
Optimization Guidelines
- Accurate Bandwidth: Set interface bandwidth to match actual link speed
- Conservative Limits: Start with lower EIGRP percentages and increase if needed
- Monitor Impact: Watch application performance after tuning changes
- Document Changes: Keep records of all bandwidth modifications
- Test Failover: Verify backup path performance after tuning
- Consider QoS: Coordinate with quality of service policies
Common Tuning Issues
Avoid These Problems
- Mismatched Bandwidth: Bandwidth values don't reflect actual speeds
- Aggressive Timers: Too fast hello intervals can cause instability
- Over-Limiting: Too restrictive bandwidth percentages slow convergence
- Ignoring QoS: EIGRP traffic conflicts with other applications
- Inconsistent Tuning: Different settings on opposite ends of links