A personal detailed view of a journey of acquiring IT certifications and career progression.
Monday, February 22, 2010
BGP Summary and Aggregated Routes
I spent this morning briefly covering how to summarize routes in BGP using CIDR Aggregated Routes. BGP specifically uses the Atomic Aggregate attribute which is considered one of the well-known discretionary attributes. BGP also uses the optional transitive attribute called an Aggregator which specifies the BGP ID and the AS that performed the aggregation in BGP updates. If you aren't careful when planning which routes to summarize your AS could easily claim routes that it really doesn't own which could upset other AS's in the BGP system! AS's doesn't really use aggregation as much as they could because some are multihomed to many ISP's and would rather make sure that all of the routes that own are being advertised without being summarized into one route.
Sunday, February 21, 2010
Policy Based Routing 2
This morning I created another PBR lab that I was able to wrap my head around a lot easier than yesterday. As you see in the above image, there are 3 routers in which specific LAN traffic from Router C should be routed out of Router A's Serial 0/0/1 interface. It was good to get some more hands on with route-maps the past few days. I'm going to work some more labs throughout the day most likely on BGP. My lab guide book should be here in another weeks so you should be seeing a ton of new labs from me here shortly!
Saturday, February 20, 2010
Policy-Based Routing
Now that I finished the main book for BSCI, I'm now reviewing everything I learned and will spend most of my time creating labs and touching up the details. But before I do to much, Cisco was kind enough to include 5 extra Appendix PDF files to learn about some technology in even more detail. This is mainly appendixes on how to manipulate packets and even more BGP no surprise! I hear that in order to fully be perpared for the BSCI you have to dig even deeper than what the Self Study Guide book provides. This includes everything from reading white papers, CBT's, and creating labs for pretty much ANYTHING related to the exam.
Today I learned a little bit about Policy Based Routing (PBR) which is basically route-maps on steroids. Similar to how there are access-lists and then extended access-lists (access-list on steroids), PBR allows you to maniplulate routes in a more granular manner. Tomorrow I'll be finishing this appendix up and moving to the last few that are left.
Don't forget to download my FREE CCNA Lab book for the ICND1 course at www.configurethenetwork.com while it's still available. The full version of the lab book is FINISHED and ready to sell, I'm just working on some things on the back end. The full lab contains 17 scenario based CCNA labs that will test your theory on every topic included in the CCNA
Tuesday, February 16, 2010
IPv6 End of Chapter Configuration
Well I Finally Finally Finally made it through the entire CCNP Self Study Guide book. I polished off the rest of the book by finishing the end of chapter lab for IPv6. I managed to get through most of the tasks successfully but I'm still having troubles setting up IPv6 tunnels and I'm not sure why. Even after mirroring the configuration settings exactly, I've been unable to bring the tunnels up. Hopefully I can figure out what was missing by doing a little research aka Google. The next step for me will be going through the exam-guide and lab guide, I'm hoping to get through these two books in about two months so I can sit the test in April!
Sunday, February 14, 2010
IPv6 OSPF Configuration
Today I configured a simple OSPF network using Ipv6 as my routed protocol. When using IPv6 to create an OSPF network, there are many differences and also similarities with IPv4. The main difference is obviously you're using the IPv6 format instead of the traditional 32 bit addressing scheme. Another difference involves having to manually create a 32 bit Router ID, this was optional in IPv4 but it is required for IPv6. One other thing I noticed is that you can implement OSPF on specific interfaces (links) rather than for specific subnets. Tomorrow I will be finishing up the last of the IPv6 theory which talks about transitioning from IPv4 to IPv6. Only a few more pages and I'll actually be completly finished with the self study guide! After I finish this book, the next step for me will be going through the lab and exam books to tidy up on everything l learned and prepare to take the BSCI test in the next coming months.
Saturday, February 13, 2010
Ipv6 Anycast Addresses
I spent some time over the past few days learning more about the many types of IPv6 addresses out there. A new address type made specifically for IPv6 is called the Anycast Address. IPv6 Anycast addresses are global addresses, theses addressed can be assigned to more than one interface unlike a Ipv6 unicast address. Anycast is designed to send a packet to the nearest interface that is apart of that anycast group.
The sender creates an anycast packet and fowards the packet to the anycast address as the destination address which goes to the nearest router. The nearest router or interface is found by using the metric of a routing protocol. However in a LAN setting the nearest interface is found depending on the order the neighbors were learned. The anycast packet in a LAN setting forwards the packet to the neighbor it learned about first. Anycast was first proposed in 1993 but even to this data there isn't much usage as of yet. There are actually only a few anycast addresses currently assigned!
The source sending the anycast path can use the address to control the paths that traffic flows. For example, when a customer has multiple connections to multiple IP's using BGP. The customer can create a different anycast address for each ISP, and then configure the same anycast address on the closest router to that specific ISP. Therefore the routers along the source's path to the ISP can determine the shortest route based on the IPv6 anycast address. Which then forwards the packet based on the routers closest anycast address link. Another example would be on a LAN link. All the routers on the same LAN can have the same IPv6 address so that distant devices only need to identify the anycast address.
Thursday, February 11, 2010
IPv6 Unicast Addressing
The IPv6 global aggregatable unicast address, also known as the IPv6 global unicast address, is the equivalent of the IPv4 global unicast address. A global unicast address is an IPv6 address from the global unicast prefix. These global unicast addresses are designed in a way so that their prefixes can be reduced making for more efficient routing due to a decreased routing table size. Global unicast addresses used on links are aggregated upward through organizations and eventually to the ISP's. This also allows for more efficient and scalable routing within the Internet, an improved bandwidth and functionality for user traffic.
A global unicast address typically consists of a 48-bit global routing prefix, a 16-bit subnet ID, and a 64-bit interface ID that's usually in the EUI-64 bit format.The subnet field is similar to the IPv4 subnets, organizations can use the subnet ID to create their own local addressing hierarchy. This field allows an organization to use up to 65,536 individual subnets!
The current global unicast address assignment by the Internet Assigned Numbers Authority (IANA) uses the range of address that start with the binary value 001 (2000::/3). This is one-eighth of the total IPv6 address space and is the largest block of assigned addresses. The IANA then allocates the 2001::/16 prefixes to the registries.
IPv6 Link-Local addressing have a scope limited to the local link and are dynamically created on all IPv6 interfaces by using the specific link-local prefix FE80::/10 and a 64-bit interface identifier. Link-local addresses are used for automatic address configuration, neighbor discovery, router discovery, and by different routing protocols.
Subscribe to:
Posts (Atom)