When you're studying for the BSCI exam on the way to earning your CCNP certification, you've got to master the use of BGP attributes. These attributes allow you to manipulate the path or paths that BGP will use to reach a given destination when multiple paths to that destination exist.
In this free BGP tutorial, we're going to take a look at the NEXT_HOP attribute. You may be thinking "hey, how complicated can this attribute be?" It's not very complicated at all, but this being Cisco, there's got to be at least one unusual detail about it, right?
The NEXT_HOP attribute is simple enough - this attribute indicates the next-hop IP address that should be taken to reach a destination. In the following example, R1 is a hub router and R2 and R3 are spokes. All three routers are in BGP AS 100, with R1 having a peer relationship with both R2 and R3. There is no BGP peering between R2 and R3.
R3 is advertising the network 33.3.0.0 /24 via BGP, and the value of the next-hop attribute on R1 is the IP address on R3 that is used in the peer relationship, 172.12.123.3.
The issue with the next-hop attribute comes in when the route is advertised to BGP peers. If R3 were in a separate AS from R1 and R2, R1 would then advertise the route to R2 with the next-hop attribute set to 172.12.123.3. When a BGP speaker advertises a route to iBGP peers that was originally learned from an eBGP peer, the next-hop value is retained.
Here, all three routers are in AS 100. What will the next-hop attribute be set to when R1 advertises the route to its iBGP neighbor R2?
R2#show ip bgp
< no output >
There will be no next-hop attribute for the route on R2, because the route will not appear on R2. By default, a BGP speaker will not advertise a route to iBGP neighbors if the route was first learned from another iBGP neighbor.
Luckily for us, there are several ways around this rule. The most common is the use of route reflectors, and we'll look at RRs in a future free BGP tutorial.
Showing posts with label Computer Certification. Show all posts
Showing posts with label Computer Certification. Show all posts
Sunday, November 28, 2010
Tuesday, November 9, 2010
Cisco CCNP - BSCI Tutorial: The Role Of The OSPF ASBR
To pass the BSCI exam and earn your CCNP certification, you've got to master the (many) details of OSPF. You might have thought there were quite a few OSPF details in your CCNA studies, but you'll now build on that foundation on the way to earning your CCNP.
One such detail is the role of the Autonomous System Border Router (ASBR) in OSPF. The name itself raises some eyebrows, since you learned in your CCNA studies that OSPF doesn't use autonomous systems! Just as an OSPF Area Border Router borders multiple OSPF areas, the ASBR borders the entire OSPF domain and another source of routes. This can be another dynamic routing protocol, or directly connected networks that are not being advertised into OSPF by the network command.
Let's say we have a router running both OSPF and RIP version 2. By default, the RIP process will not contain any OSPF-discovered routes, and vice versa. The two separate routing processes are just that - separate. If we want the other OSPF routers to know about the RIP routes, route redistribution must be configured. When the RIP routes are redistributed into OSPF, that router is then an ASBR.
In the below example, RIP subnets have been redistributed into OSPF. A seed metric is not necessary when redistributing routes into OSPF. The command "show ip ospf" confirms that this router is now an ASBR.
R1(config)#router ospf 1
R1(config-router)#redistribute rip subnets
R1#show ip ospf
Routing Process "ospf 1" with ID 1.1.1.1
Supports only single TOS(TOS0) routes
Supports opaque LSA
It is an autonomous system boundary router
The ASBR can also perform route summarization on the routes being injected into OSPF with the summary-address command. (To configure OSPF inter-area summarization, use the area range command.) By mastering route summarization and route redistribution, you're well on your way to passing the BSCI exam and earning your CCNP certification!
One such detail is the role of the Autonomous System Border Router (ASBR) in OSPF. The name itself raises some eyebrows, since you learned in your CCNA studies that OSPF doesn't use autonomous systems! Just as an OSPF Area Border Router borders multiple OSPF areas, the ASBR borders the entire OSPF domain and another source of routes. This can be another dynamic routing protocol, or directly connected networks that are not being advertised into OSPF by the network command.
Let's say we have a router running both OSPF and RIP version 2. By default, the RIP process will not contain any OSPF-discovered routes, and vice versa. The two separate routing processes are just that - separate. If we want the other OSPF routers to know about the RIP routes, route redistribution must be configured. When the RIP routes are redistributed into OSPF, that router is then an ASBR.
In the below example, RIP subnets have been redistributed into OSPF. A seed metric is not necessary when redistributing routes into OSPF. The command "show ip ospf" confirms that this router is now an ASBR.
R1(config)#router ospf 1
R1(config-router)#redistribute rip subnets
R1#show ip ospf
Routing Process "ospf 1" with ID 1.1.1.1
Supports only single TOS(TOS0) routes
Supports opaque LSA
It is an autonomous system boundary router
The ASBR can also perform route summarization on the routes being injected into OSPF with the summary-address command. (To configure OSPF inter-area summarization, use the area range command.) By mastering route summarization and route redistribution, you're well on your way to passing the BSCI exam and earning your CCNP certification!
Friday, November 5, 2010
Cisco CCNA - CCNP Home Lab Tutorial: Cabling Your Access Server
A Cisco home lab is an invaluable study tool when you're preparing for CCNA and CCNP exam success. Once you've gotten a couple of routers and switches, you'll quickly get tired of moving that blue console cable every time you want to configure a different device. The solution to this problem is purchasing and configuring an access server (AS).
For those of you new to access servers, note that these are not white boxes running Microsoft operating systems. These are Cisco routers that allow you to connect to all the routers and switches in your home lab without moving a cable. You can physically or logically connect to the access server and work with all your devices from there.
When you're pricing access servers, please remember that you do NOT need an expensive AS. Right now on ebay there are access servers costing up to $5000 - this is NOT what you want to buy. What you're looking for is something like a 2509 or 2511, which is going to run you anywhere from $100 - $200. It's money well spent, because once you get an AS, you'll really wonder how you ever did without it.
The only additional hardware you need is the cable that will physically connect your AS to the other routers and switches in your home lab. The cable you need is called an octal cable, so named because one end of this cable is actually eight ends, all terminated with a numbered RJ-45 connector.
The large end of the cable is going to be connected to the AS itself. The cable will connect to a port on the AS that will have "async 1-8" directly above the physical port. It is this port that makes an AS different from other Cisco routers.
Once you've got your AS and this cable, you're ready to configure your AS. Connect the cable to the AS as described above, and then you will connect one of the RJ-45 connectors to the console port of each one of your routers and switches. Make sure to note the number that's on the cable itself right below the connector, because that's very important. In the next part of this home lab tutorial, I'll tell you exactly how to configure your access server for best results, along with a few troubleshooting tips.
For those of you new to access servers, note that these are not white boxes running Microsoft operating systems. These are Cisco routers that allow you to connect to all the routers and switches in your home lab without moving a cable. You can physically or logically connect to the access server and work with all your devices from there.
When you're pricing access servers, please remember that you do NOT need an expensive AS. Right now on ebay there are access servers costing up to $5000 - this is NOT what you want to buy. What you're looking for is something like a 2509 or 2511, which is going to run you anywhere from $100 - $200. It's money well spent, because once you get an AS, you'll really wonder how you ever did without it.
The only additional hardware you need is the cable that will physically connect your AS to the other routers and switches in your home lab. The cable you need is called an octal cable, so named because one end of this cable is actually eight ends, all terminated with a numbered RJ-45 connector.
The large end of the cable is going to be connected to the AS itself. The cable will connect to a port on the AS that will have "async 1-8" directly above the physical port. It is this port that makes an AS different from other Cisco routers.
Once you've got your AS and this cable, you're ready to configure your AS. Connect the cable to the AS as described above, and then you will connect one of the RJ-45 connectors to the console port of each one of your routers and switches. Make sure to note the number that's on the cable itself right below the connector, because that's very important. In the next part of this home lab tutorial, I'll tell you exactly how to configure your access server for best results, along with a few troubleshooting tips.
Subscribe to:
Posts (Atom)