ROUTE Exam Blueprint

The ROUTE exam blueprint. Mastering the knowledge that is required for each topic is what stands before me and obtaining ROUTE. Onwards!

 

Implement an EIGRP based solution, given a network design and a set of requirements

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 show and debug commands
Document results of EIGRP implementation and verification

Implement a multi-area OSPF Network, given a network design and a set of requirements

Determine network resources needed for implementing OSPF on a network
Create an OSPF implementation plan
Create an OSPF verification plan
Configure OSPF routing
Verify OSPF solution was implemented properly using show and debug commands
Document results of OSPF implementation and verification plan

Implement an eBGP based solution, given a network design and a set of requirements

Determine network resources needed for implementing eBGP on a network
Create an eBGP implementation plan
Create an eBGP verification plan
Configure eBGP routing
Verify eBGP solution was implemented properly using show and debug commands
Document results of eBGP implementation and verification plan

Implement an IPv6 based solution, given a network design and a set of requirements

Determine network resources needed for implementing IPv6 on a network
Create an IPv6 implementation plan
Create an IPv6 verification plan
Configure IPv6 routing
Configure IPv6 interoperation with IPv4
Verify IPv6 solution was implemented properly using show and debug commands
Document results of IPv6 implementation and verification plan

Implement an IPv4 or IPv6 based redistribution solution, given a network design and a set of requirements

Create a redistribution implementation plan based upon the results of the redistribution analysis
Create a redistribution verification plan
Configure a redistribution solution
Verify that a redistribution was implemented
Document results of a redistribution implementation and verification plan
Identify the differences between implementing an IPv4 and IPv6 redistribution solution

Implement Layer 3 Path Control Solution

Create a Layer 3 path control implementation plan based upon the results of the redistribution analysis
Create a Layer 3 path control verification plan
Configure Layer 3 path control
Verify that a Layer 3 path control was implemented
Document results of a Layer 3 path control implementation and verification plan

Implement basic teleworker and branch services

Describe broadband technologies
Configure basic broadband connections
Describe basic VPN technologies
Configure GRE
Describe branch access technologies

Advertisements

Weekend Labbing

This weekend I have finished reading over EIGRP (more study notes to come) and started to lab and put into practice the theory.

I have at my disposal the GNS3 Labs from CBT Nuggets ROUTE track, the Network Academy ROUTE Lab book.

These two resources provide a solid foundation to my practical studies. I have found that they give me directions when trying to lab a new concept. This then gets me rolling and then I can make my own to ensure the topic is firmly embedded in my brain and not leaking out my other ear.

I believe the best way to make it stick is blog examples of my configurations with an imaginary company.

Not sure of the name just yet but I do believe it will help.

New Study Computer

Currently I am in a bit of a dilemma. I need a new computer that will be the foundation for my studies for CCNP and CCIE. I am not sure of the route I want to take yet. Notebook/Desktop.

My requirements are modest I suppose. Something that can run GNS3, Play my CBT nuggets and maybe play Diablo 3. Oh and to use for work occasionally. Any suggestions?

EIGRP Packets

 

Time to play packets. EIGRP Packets to be precise.

 

EIGRP when running in a routed environment utilizes five types of packets. A Hello, Update, Query, Reply and Acknowledgement (ACK) packet.

 

Hello Packets

Pretty much used for neighbor discovery. Multicasts with ACK # of 0.

 

Update

Update packets contain route change information. They are send to affected routers. Updates routers that the particular route has used to converge. Sent as multicasts when a route becomes passive. Syncs by unicasting during startup. Sent reliably.

 

Query

Performed in route computation when no FS is found. Sent to neighbors asking if they have a route to destination. Usually multicast but can be send as unicast. Sent reliably.

 

Reply

Send in response to a query. Must always reply. Sent reliably.

 

ACK

Acknowledges updates, queries, and replies. Unicast hello’s that contain a non zero ACK number. (Hello’s and ACK don’t require ACK’s)

 

 

image

 

Above An example Hello Packet. Notice the information provided by a simple packet sniff.

 

image

 

Above Here is an exchange of connected routes via an Update packet.

 

image

Above An example of another update packet, this time declaring it cannot reach certain networks.

 

 

A thank you to Stretch over at Packetlife for his Captures library. I am currently away from my lab.

EIGRP–Study Notes

ROUTE begins with a EIGRP brush up and pow-wow. I ❤ EIGRP due to it’s fast failover times but being proprietary it makes me a little sad.

Fun Facts

 

An Advanced Distance Vector Routing Protocol.

Keeps Backup Routes  in Topology table as FS

 

Combined the best attributes of a DV whilst not being as intensive as OSPF with Databases.

 

Summarization can be done anywhere unlike OSPF at ABR and ABSR

Unequal load cost balancing .

EIGRP uses Multicast and Unicast rather than broadcast. It uses the multicast address of 224.0.0.10

Administrative Distance – Cost between Routers

Feasible Distance – The sum of costs.

 

Successor –  Route with lowest FD to destination. Proven to not be a part of a Routing Loop.
Successors are offered to the Routing Table to Forward packets. Can be many if they have same FD.

 

Feasible Successor – DUAL remembers backup paths. 2nd best route to Destination. Kept in the topology table. FS are selected when successors are. Topology table maintains many FS’s.

Neighbor table

Everyone Router contains a neighbor table with Directly Connected router. Neighbor relationship stable with Hello Packets. Neighbor tables include data such as address of each neighbor, interface it is connected too and keeps Round Trip Timers in regards to optimal retransmission periods.

 

Topology table

Topology table lists best routes to a network, Successor routes, Also lists second best routes, known as Feasible Successor. (Also 3rd, 4th and so on). Instantaneously switches. Topology table maintains the metric that neighbors advertise for each destination (AD). Also the metric that the router would use to reach the dest. Via the( FD).

 

If there is a topology change, DUAL gets funky. It immediately checks if it has a FS to the Destination. If it does, no computation is required and the FS becomes the successor.

 

If there is no FS, the router sends out Query Packets to its neighbors.  If any neighbors have routes to the destination they send back a Reply Packet. If not, the neighbor sends Query packets to it’s neighbors. During this stage the destination is in Active state, a router cannot change Routing table information for the destination.

 

No route from neighbors reply with unreachable. If at least one has a route the destination returns to a passive state and becomes successor.

 

Routing table

Routing Table (show ip route shows off the best routes the router knows about).

Router compares all FDs to reach a specific network and selects the lowest FD . It earns it’s place in the routing table. FD chosen for the successor is the EIGRP metric to reach that network in the table.

image

Above: Notes regarding the Neighbor table, Topology table and Routing table.

Not a bad start. The understanding of EIGRP’s tables is paramount to it’s success maintaining uptime in your EIGRP environment.

2011. CCNA Certified and looking to the future.

December 2010 was when I finally went from “I would like to be a Cisco Certified Network Guru” to taking my first step towards my CCIE. Networking isn’t a job for me, it isn’t something that I *have* to do. For me it is a passion. I work in a heavily switched enterprise environment and want to bring my routing skills up to where my Switching knowledge is.

Follow me as I head along the path of Cisco Certification to CCIE, starting with CCNP ROUTE. The aims this year for 2011 are SWITCH, ROUTE and TSHOOT. Let’s begin.