DFS

There is a real revolution today among CCNA and CCNP candidates. More and more of you are turning your back on “router simulators” and putting your own CCNA and/or CCNP Home Lab together, which is the best way to totally prepare to pass these tough Cisco exams.

I get hundreds of emails every month from CCNA and CCNP candidate who are putting together their first lab or adding to their existing one. I’m always glad to help with suggestions, and I thought I’d list five common questions regarding home labs here.

Do I have to spend thousands of dollars?

No! There are vendors all over the web, as well as on ebay, who sell used Cisco routers and switches to Cisco exam candidates like you every single day. They sell kits that consist of multiple routers and switches, as well as single routers and switches. You can add one piece at a time, or make a larger investment. You can spend just a few hundred dollars and put together a very nice lab.

What’s an “access server“?

It’s not what it sounds like. When I first heard the term, I thought of a typical server like we see in LANs every single day. An access server is actually a Cisco router that allows you to connect to multiple other routers and switches without continually moving the rolled cable around.

You don’t have to have an access server right away, but once you add a few more routers and switches to your lab, you’ll get tired of moving the rollover cable from console port to console port. (The console port is used to directly connect your PC to the router.) You’ll find an access server is easy to set up and configure, and will save you quite a bit of time.

What’s a “frame relay switch“?

Again, it’s not quite what it sounds like. A frame relay switch is not a switch; it’s a Cisco router that has been configured to serve as a frame relay provider in your home lab.

This is very close to being a “must” for your home lab. You don’t need it right away if your budget allows for only one or two routers to get started. To truly practice frame relay map statements and see the effect of different frame relay statements, you’ll need a Cisco router to serve as a frame switch. Again, the configuration is easy, and having a frame relay switch in your home lab will give you practice that will be invaluable on exam day.

Do I need a switch? What switch should I buy?

I recommend you get at least one switch in your lab; two if your budget allows. Make sure that at least one of your switches has an IOS; 1900 switches do not have an IOS and while they’re better than not having a switch, they’re not going to give you the practice you need to pass the CCNA and CCNP. Look to the 2500 family of switches.

I want to build my CCNP lab and then use it for the CCIE. What should I buy?

It’s impossible to tell what technologies and devices will be on the CCIE lab, even if you zip through the CCNP and then take the IE within six months. Cisco refreshing the CCIE lab blueprint every six months, and different technologies can be taken off the lab. While Cisco gives plenty of notice that these changes are going to take effect, it can be a big pain in your wallet if Cisco takes something off of the exam after you spend a bundle to add it to your lab.

As an example, Cisco is in the process of removing ISDN and ATM from the CCIE Routing & Switching lab. If you bought an ATM switch for your lab, you’ve got an expensive paperweight right now. While you may be able to practice your core protocols on a CCIE home lab, it’s going to be difficult and expensive to keep your home lab totally current with the Cisco lab blueprint.

The decision to put together your own CCNA or CCNP home lab is the best decision you can ever make – and I speak from experience. With home labs becoming less expensive every day, it’s becoming more affordable as well. Start looking into used Cisco router vendors today (ebay is a great place to find some vendors, as is Google), and you can be practicing on REAL Cisco routers and switches soon – and be totally prepared for CCNA and CCNP exam success.

• Related posts on Access Server
• DPM agent installing Error 337 « Ingazat Information Technology …
• Google Dorks « Kid zoom!
• Cisco Certification: Building Your Home Lab, Part II | Sachiko …

• Related posts on ccie
• INE Blog Redesign | CCIE Blog
• Juniper vs Cisco. « Gungajim’s Blog

• Related posts on ccna
• VisualExams – IT certifications Blog » Blog Archive » HP0-J12 …
• INE Blog Redesign | CCIE Blog
• Making students industry-ready » OnlySoftwareBlog

• ccna routers for sale
• ccna lab access software
• cisco ccna ccnp ccie blogs

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