== The Design Step
New network project happens, new sites are added, or any noticeable change occurs)
Determining the requirements and creating a plan. That plan typically lists the following:
- The requirements for the project
- The sites affected
- Sample configurations
- Results from proof-of-concept testing
- Dependencies and assumptions
- Business requirements, financials, and management commitments
== Implementation Planning Step
Develop a very specific implementation plan that lists all significant tasks and actions by each group and on each device.
The existing network:
Router and switch hardware
IOS versions and feature sets
RAM and flash in each device
Existing configurations
IP Subnet and Addressing Plan, Assignments, and Conventions
Management:
Personnel and roles, contact information
Assumptions and dependencies
Required management sign-offs
New tools, reporting, status update process
New project details:
Design goals (reference to design doc possibly)
Hardware upgrades
Software upgrades
Timelines to make changes
Specific configurations for each device
Migration issues (assuming a subset of sites are implemented in any one change window)
Network diagrams, possibly for each interim step during a migration
Project completion:
Final sign-off requirements
Definitions of success
Submission of revised site documentation, operational procedures,and any other permanent documentation
== Verification Planning Step
It is used with the actual implementation of the changes in the network.
The most important part of the verification plan, identifies what commands confirm whether each key design point was implemented:
The specific showand debugcommands to be used: show ip interface brief (confirm an up/up state),
- show ip route
- show ip eigrp neighbors detail
== Documenting the Results of the Implementation
When a set of changes is attempted during a change window, some documentation must be changed based on the results.
CCNP ROUTE exam specifically related to EIGRP:
- Determine network resources needed for implementing EIGRP on a network
- Create an EIGRP implementation plan
- Create an EIGRP verification plan
- Configure EIGRP routing
- Verify EIGRP solution was implemented properly using showand debugcommands
- Document results of EIGRP implementation and verification
Verification Tables
From CCNP ROUTE Official Guide
table 2-5 Design Goal
Improve EIGRP convergence
Implement EIGRP on eachrouter so that neighborships are formed (2).
Limit neighborship formation on interfaces matched with an EIGRP network command (3).
table 2-6 Implementation Plan Peer Review
What happens on a router interface on which an EIGRP network command matches the interface? (2)
What configuration settings prevent EIGRP neighbor discovery on an EIGRP-enabled interface? (2)
What configuration settings prevent any neighborships on an EIGRP-enabled interface?
What settings do potential neighbors check before becoming EIGRP neighbors? (5)
What settings that you might think would impact EIGRP neighbor relationships actually do not prevent neighborship? (3)
What issues typically arise when the design calls for the use of EIGRP authentication key chains with lifetime settings? (2)
table 2-7 Implementation Plan Configuration
Enabling EIGRP on interfaces
Setting Hello and Hold Timers
EIGRP authentication
Passive interfaces
Static EIGRP neighbors
K-values
EIGRP router ID
ANSWERS
table 2-5 Design Goal
Improve EIGRP convergence.table 2-6
tune Hello/Hold Timers
Implement EIGRP on eachrouter so that neighborships are formed (2).
router eigrp 15 -> netwr
static neib
Limit neighborship formation on interfaces matched with an EIGRP network command (3).
passive interf
static neib
auth
What happens on a router interface on which an EIGRP network command matches the interface? (2)table 2-7 Implementation Plan Configuration
neib discov
route advertise
What configuration settings prevent EIGRP neighbor discovery on an EIGRP-enabled interface? (2)
passive interf
static neib
What configuration settings prevent any neighborships on an EIGRP-enabled interface?
passive interf
What settings do potential neighbors check before becoming EIGRP neighbors? (5)
same AS
same ip network (on primary IP)
password mismatch
K Values
no passive interface
What settings that you might think would impact EIGRP neighbor relationships actually do not prevent neighborship? (3)
MTU mismatch
Hello/Hold Timers
duplicate RID (Router ID)
What issues typically arise when the design calls for the use of EIGRP authentication key chains with lifetime settings? (2)
NTP sync (not same time on diff routers)
same key-string
Enabling EIGRP on interfaces
router eigrp 15 -> netw
Setting Hello and Hold Timers
interface -> ip hello/hold
EIGRP authentication
key chain (name/key/key-string)
interface -> ip auth mode eigrp, ip auth key-chain
Passive interfaces
router eigrp 15 -> no/passive interface <interface>/default
Static EIGRP neighbors
router eigrp 15 -> neighbor A.B.C.D
K-values
router eigrp 15 -> metric weights 0 k1 k2 k3 k4 k5
EIGRP router ID
router eigrp 15 -> eigrp router-id A.B.C.D
table 2-8 Verification Plan Memory Drill