DFS

Preparing to pass the BSCI exam and earn your Cisco CCNP? Route summarization is just one of the many skills you’ll have to master in order to earn your CCNP. Whether it’s RIP version 2, OSPF, or EIGRP, the BSCI exam will demand that you can flawlessly configure route summarization.

Route summarization isn’t just important for the BSCI exam. It’s a valuable skill to have in the real world as well. Correctly summarizing routes can lead to smaller routing tables that are still able to route packets accurately – what I like to call “concise and complete” routing tables.

The first skill you’ve got to have in order to work with route summarization is binary math more specifically, you must be able to take multiple routes and come up with both a summary route and mask to advertise to downstream routers. Given the networks 100.16.0.0 /16, 100.17.0.0 /16, 100.18.0.0 /16, and 100.19.0.0 /16, could you quickly come up with both the summary address and mask? All you need to do is break the four network numbers down into binary strings. We know the last two octets will all convert to the binary string 00000000, so in this article we’ll only illustrate how to convert the first and second octet from decimal to binary.

100 16 = 01100100 00010000

100 17 = 01100100 00010001

100 18 = 01100100 00010010

100 19 = 01100100 00010011

To come up with the summary route, just work from left to right and draw a line where the four networks no longer have a bit in common. For these four networks, that point comes between the 14th and 15th bits. This leaves us with this string: 01100100 000100xx. All you need to do is convert that string back to decimal, which gives us 100 for the first octet and 16 for the second. (The two x values are bits on the right side of the line, which aren’t used in calculating the summary route.) Since we know that zero is the value for the last two octets, the resulting summary network number is 100.16.0.0.

But we’re not done! We now have to come up with the summary mask to advertise along with the summary route. To arrive at the summary route, write out a mask in binary with a “1″ for every bit to the left of the line we drew previously, and a “0″ for every bit to the right. That gives us the following string:

11111111 11111100 00000000 00000000

Converting that to dotted decimal, we arrive at the summary mask 255.252.0.0. The correct summary network and mask to advertise are 100.16.0.0 252.0.0.0.

For the BSCI exam, emphasis is put on knowing how to advertise these summary routes in RIPv2, EIGRP, and OSPF. For RIP v2 and EIGRP, route summarization happens at the interface level – it’s not configured under the protocol. On the interface that should advertise the summary route, use the command “ip summary-address”. Here are examples of how the above summary route would be configured on ethernet0 in both RIPv2 and EIGRP.

R1(config-if)#ip summary-address rip 100.16.0.0 255.252.0.0

R1(config-if)#ip summary-address eigrp 100 100.16.0.0 255.252.0.0

The main difference between the two is that the EIGRP command must specify the AS number – that’s what the “100″ is in the middle of the EIGRP command. Since RIPv2 does not use AS numbers, there’s no additional value needed in the configuration.

For OSPF, the commands differ. If you’re configuring inter-area route summarization, use the “area range” command. The number following “area” is the area containing the routes being summarized, not the area receiving the summary.

R1(config)#router ospf 1

R1(config-router)#area 1 range 100.16.0.0 255.252.0.0

If you are summarizing routes that are being redistributed into OSPF, use the summary-address command under the OSPF routing process on the ASBR.

R1(config)#router ospf 1

R1(config-router)#summary-address 100.16.0.0 255.252.0.0

I speak from experience when I tell you that practice makes perfect on the BSCI exam, especially with binary and summarization questions. The great thing about these questions is that there are no grey areas with these questions – you either know how to do it or you don’t. And with practice and an eye for detail, you can master these skills, pass the exam, and become a CCNP. Here’s to your success on these tough Cisco certification exams!

• route summarization
• ripv2 route summarization
• route summarization in rip

When you’re studying for the CCNP certification, especially the BSCI exam, you must gain a solid understanding of BGP. BGP isn’t just one of the biggest topics on the BSCI exam, it’s one of the largest. BGP has a great many details that must be mastered for BSCI success, and those of you with one eye on the CCIE must learn the fundamentals of BGP now in order to build on those fundamentals at a later time.

Path attributes are a unique feature of BGP. With interior gateway protocols such as OSPF and EIGRP, administrative distance is used as a tiebreaker when two routes to the same destination had different next-hop IP addresses but the same prefix length. BGP uses path attributes to make this choice.

The first attribute considered by BGP is weight. Weight is a Cisco-proprietary BGP attribute, so if you’re working in a multivendor environment you should work with another attribute to influence path selection.

The weight attribute is significant only to the router on which it is changed. If you set a higher weight for a particular route in order to give it preference (a higher weight is preferred over a lower one), that weight is not advertised to other routers.

BGP uses categories such as “transitive”, “non-transitive”, “mandatory”, and “optional” to classify attributes. Since weight is a locally significant Cisco-proprietary attribute, it does not all into any of these categories.

The weight can be changed on a single route via a route-map, or it can be set for a different weight for all routes received from a given neighbor. To change the weight for all incoming routes, use the “weight” option with the neighbor command after forming the BGP peer relationships.

R2(config)#router bgp 100

R2(config-router)#neighbor 100.1.1.1 remote-as 10

R2(config-router)#neighbor 100.1.1.1 weight 200

Learning all of the BGP attributes, as well as when to use them, can seem an overwhelming task when you first start studying for your BSCI and CCNP exams. Break this task down into small parts, learn one attribute at a time, and soon you’ll have the BGP attributes mastered.

• bgp weight
• bgp weight attribute
• bgp wight

From the CCNA to the CCIE, ISDN is one of the most important technolgies you’ll work with. It’s also very common in the field ISDN is frequently used as a backup connection in case an organization’s Frame Relay connections go down. Therefore, it’s important to know ISDN basics not only for your particular exam, but for job success.

ISDN is used between two Cisco routers that have BRI or PRI interfaces. Basically, with ISDN one of the routers places a phone call to the other router. It is vital to understand not only what causes one router to dial another, but what makes the link go down.

Why? Since ISDN is basically a phone call from one router to another, you’re getting billed for that phone call — by the minute. If one of your routers dials another, and never hangs up, the connection can theoretically last for days or weeks. The network manager then receives an astronomical phone bill, which leads to bad things for everyone involved!

Cisco routers use the concept of interesting traffic to decide when one router should call another. By default, there is no interesting traffic, so if you don’t define any, the routers will never call each other.

Interesting traffic is defined with the dialer-list command. This command offers many options, so you can tie interesting traffic down not only to what protocols can bring the link up, but what the source, destination, or even port number must be for the line to come up.

One common misconception occurs once that link is up. Interesting traffic is required to bring the link up, but by default, any traffic can then cross the ISDN link.

What makes the link come down? Again, the concept of interesting traffic is used. Cisco routers have an idle-timeout setting for their dialup interfaces. If interesting traffic does not cross the link for the amount of time specified by the idle-timeout, the link comes down.

To summarize: Interesting traffic brings the link up by default, any traffic can cross the link once it’s up a lack of interesting traffic is what brings the link down.

Just as important is knowing what keeps the link up once it is dialed. Why? Because ISDN acts as a phone call between two routers, and it’s billed that way to your client. The two routers that are connected by this phone call may be located in different area codes, so now we’re talking about a long distance phone call.

If your ISDN link does not have a reason to disconnect, the connection could theoretically last for days or weeks before someone realizes what’s going on. This is particularly true when the ISDN link is used as a backup for another connection type, as is commonly the case with Frame Relay. When the Frame Relay goes down, the backup ISDN link comes up when the Frame Relay link comes back not billed for all that time.

To understand why an ISDN link stays up when it’s not needed, we have to understand why it stays up period. Cisco’s ISDN interfaces use the idle-timeout to determine when an ISDN link should be torn down. By default, this value is two minutes, and it also uses the concept of interesting traffic.

Once interesting traffic brings the link up, by default all traffic can cross the link. However, only interesting traffic resets the idle-timeout. If no interesting traffic crosses the link for two minutes, the idle-timer hits zero and the link comes down.

If the protocol running over the ISDN link is RIP version 2 or EIGRP, the most efficient way to prevent the routing updates from keeping the line up is expressly prohibiting their multicast routing update address in the access-list that is defining interesting traffic. Do not prevent them from crossing the link entirely, or the protocol obviously won’t work correctly.

With OSPF, Cisco offers the ip ospf demand-circuit interface-level command. The OSPF adjacency will form over the ISDN link, but once formed, the Hello packets will be suppressed. However, the adjacency will not be lost. A check of the adjacency table with show ip ospf adjacency will show the adjacency remains at Full, even though Hellos are no longer being sent across the link. The ISDN link can drop without the adjacency being lost. When the link is needed, the adjacency is still in place and data can be sent without waiting for OSPF to go through the usual steps of forming an adjacency.

This OSPF command is vital for Cisco certification candidates at every level, but is particularly important for CCNA candidates. Learn this command now, get used to the fact that the adjacency stays up even though Hellos are suppressed, and add this valuable command to your Cisco toolkit.

One myth about ISDN is that Cisco Discovery Packets keep an ISDN link up. CDP is a Cisco-proprietary protocol that runs between directly connected Cisco devices. There is a school of thought that CDP packets have to be disabled on a BRI interface in order to prevent the link from staying up or dialing when it’s not really needed. I’ve worked with ISDN for years in the field and in the lab, and I’ve never seen CDP bring up an ISDN link. Try it yourself the next time you’re working on a practice rack!

• isdn tutorial
• isdn pri tutorial
• isdn certification