To pass the CCNA exam, you've got to master fairly a number of providers and routing protocols that could be new to you. Between RIP, IGRP, EIGRP, OSPF, and switching, there are a whole lot of particulars you've got to take up! It's easy to spend all your time on those topics and not pay correct attention to "easier" technologies, and then abruptly on examination day you can't fairly bear in mind the details of those explicit services. One setup you have to be greater than accustomed to is straight connecting serial interfaces on Cisco routers. That is additionally a beneficial talent to have in your home lab, since it permits you to add segments to your community setup. A Cisco serial interface is working as a DTE by default. The issue is that once you take a cable and connect routers immediately by their serial interfaces (with a DTE/DCE cable, that's!), they're each ready for the other to ship them a clock rate. One of many interfaces should act as the DCE and that interface should ship the clock rate. In case you can see the DTE/DCE cable, you'll be able to inform by looking which router has the DCE interface connected to it - the letters "DTE" or "DCE" will both be molded into the connector itself, or if it's an older cable there needs to be a bit piece of tape on the cable that tells you what the interface sort is. But what when you've got no entry to the cable, or there are different cables all around it and you'll't see what sort it's? Run the command "show controller serial x", with x representing the interface number the cable's connected to. There shall be fairly a little bit of output from this command, but the information you need is correct on the top: R1show controller serial 1 HD unit 1, idb = 0x1DBFEC, driver structure at 0x1E35D0 buffer dimension 1524 HD unit 1, V.35 DTE cable I left off the 16 or so rows of data that comes after this, however this is the data we need right now. If R1's got the DTE cable end, the opposite router ought to have the DCE finish: R3show controller serial 1 HD unit 1, idb = 0x1C44E8, driver structure at 0x1CBAC8 buffer dimension 1524 HD unit 1, V.35 DCE cable We all know now that R3 needs to supply a clock rate to R1. There is a hint of an issue in simply that little bit of command output - do you see what it's? Let's run present interface serial1 to get more information. R3show int s1 Serial1 is up, line protocol is down The road protocol is down because there isn't a clockrate being supplied by R3. If there was, we would have seen that within the output of present controllers serial 1. This is simple sufficient to fix, though! We'll use the command clockrate 56000 on R3's serial1 interface, and the line protocol will quickly come up. R3(config)int s1 R3(config-if)clockrate 56000 1w2d: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, modified state to up This can be an easy concept, but there are a couple of details it's essential to bear in mind! For a home lab configuration, you will need a DTE/DCE cable to make this work. In case you can not see the cable connectors, run show controllers serial x to see if the router has the DTE or DCE end of the cable attached. On the interface with the DCE hooked up, use the clockrate command to deliver the line protocol up. It is simply that straightforward! CCNA exam success is dependent upon mastering many applied sciences which can be new to you, and few examination topics have more details than ISDN. ISDN isn't just to your CCNA exam studies, though. Whereas ISDN is dismissed by many, the fact is that there are many small and mid-size networks out there that use ISDN as their backup to frame relay. Some of these corporations have spoke networks that use ISDN to connect to their hub as nicely, so it is a fantastic idea to know ISDN configuration and troubleshooting on your real-world career as well as passing the CCNA. With that in thoughts, let's take a look at five frequent ISDN errors and learn how to avoid them. With dialer map statements, keep in mind that the cellphone number you place in the dialer map is the cellphone number of the remote router, not the local one. Look at it this way - if you want to call a buddy on your cell, you do not choose up your cell and dial your individual quantity! Speaking of dialer map statements, don't forget the all-necessary broadcast possibility on the end of the command: R1(config-if)dialer map ip 172.12.21.1 name R2 broadcast 5555555 The router will settle for that command with out the "broadcast" choice, however routing protocol updates and hellos wouldn't be able to journey throughout the line. (This command can also be needed in frame relay map statements to permit broadcasts and multicasts to be transmitted.) PAP is PPP's clear-text authentication scheme, and clear text is a really unhealthy idea. But if you do need to configure it, do not forget that PAP requires further configuration -the ppp pap sent-username command. R1(config-if)ppp pap despatched-username R1 password CISCO Must set encapsulation to PPP earlier than utilizing PPP subcommands R1(config-if) The error message we obtained while configuring the despatched-username command is one other essential reminder - by default, a BRI line is operating HDLC, not PPP. Since HDLC would not permit us to make use of either PAP or CHAP, we'll need to set the hyperlink to PPP with the encapsulation ppp command. R1(config-if)encapsulation ppp R1(config-if)ppp authentication pap R1(config-if)ppp pap despatched-username R1 password CISCO But before we configure any of this information, we should always configure the ISDN switch-type. Why? Because with out the change-sort configuration, it does not matter that we keep away from the opposite four errors - the road will not come up. Configure the switch-type with the "isdn switch-type" command, after which verify it with "show isdn status". R1(config)isdn change-type fundamental-ni R1show isdn status International ISDN Switchtype = fundamental-ni (output of this command reduce here for readability) In case you neglect this a part of the configuration, the output of present isdn standing wastes no time in reminding you! R1show isdn standing **** No International ISDN Switchtype at present defined **** ISDN is a vital part of your CCNA research, and this information nonetheless is useful in production networks as well. Maintain studying, discover the small print, run these debugs, and you'll be a CCNA earlier than you recognize
Article Source: http://www.articlecontentprovider.com/articlesubmit
Configuring straight related serial interfaces seems easy sufficient, however there are necessary details you must know to make it work and cross the CCNA examination! Learn these details from Chris Bryant, CCIE 12933.
You may read extra in my web site , i'm pleased that you just read my article, thnak you , you'll be able to go to here 2010 Detroit tax forms
Please Rate this Article
5 out of 5 4 out of 5 3 out of 5 2 out of 5 1 out of 5
