Tags |
|
|
Links |
|
|
Added for You - Cisco Certification: Introduction To ISDN, Part V
One piece of information that can help anyone who is renewing or purchasing home insurance in Washington State regards the procedure required by insurance companies when it comes to raising rates. It seems all too common for an individual to secure a great insurance rate only to see it rise the next year. In Washington State, homeowner insurance companies have to justify any rate increase to the Office of the Insurance Commissioner. Although this information is helpful regarding increases, everyone still wants to find the best rate possible.There are a few tricks and tips that can help anyone who is looking for home insurance. The first is quite straightforward. If you live in a high crime area, consider moving. Home insurance rates are naturally going to be more expensive in areas where crime is rampant. The threat of property damage or burglary directly impacts the rates you’ll be expected to pay.If you’re building a new home, consider what’s holding it up. Homes made from wood generally cost more to insure. If a brick home catches fire, the damage could be contai
Show Access-List
What's this command got to do with ISDN? Everything.
Remember how the ISDN link comes up in the first place? Interesting traffic. By default, there is no interesting traffic. You define interesting traffic with the dialer-list and dialer-group commands, AND the access-list command. If you have a problem with your link never coming up or with it coming up and staying up, use this command to see what traffic has been defined as interesting.
Show Dialer
Another helpful command to determine why an ISDN link is coming up and staying up. This command sho
The parameters used to be a little more clear. You could easily save money by building your own computer. All you needed was the basic know-how, the time and initiative, and wah-la! You had a good computer at a better price than you could buy new.But things have changed over time. As technology improved and prices dropped, suddenly the the savings benefit seemingly dwindled away. However, that is not always the case and there are still many excellent reasons for building your own computer!Customize to Your NeedsBy building your own computer, you can customize it exactly to your needs. Whether you're into gaming, video production, audio recording, autocad, or just general word processing and internet surfing, you can build a computer specifically suited to your task.Easier UpgradesBy using non-proprietary, quality parts, your new home-built computer will be much more easy to upgrade than its store-bought counterpart. Many retail computers have proprietary components that are tied together in such a way as to make part replace
The knowledge you acquire from debugs is invaluable. Frankly, it's this knowledge that puts you above the 'average??? CCNA who doesn't have that hands-on experience. Watching debugs in action also gives you a head start on the CCNP. Since 90 - 95% of CCNAs go on to pursue the CCNP, it's a great idea to get started with debugs now.
Don't make the mistake of waiting until you're studying for your CCNP and CCIE to start learning debugs and shows. The work you do for the CCNA is the foundation for everything you'll do in the future.
Never, ever, ever practice debugs on a production network. There are debugs that will give you so much information that the router actually becomes overloaded and then locks up. Never practice debugs on a production network.
It's important to know the proper show and debug commands for ISDN for several reasons. First, by watching ISDN in operation, you can see its processes and better understand what's going on. Secondly, it's difficult if not impossible to properly troubleshoot ISDN without knowing the proper show and debug commands. (It's easy to overlook an ISDN authentication error just by looking at the configuration, but running debug ppp negotiation will quickly show you where the problem lies.)
Let's take a look at the ISDN show and debug commands that every CCNA and CCNP should know.
Show ISDN Status
If you only know one ISDN show command, it's got to be this one. Always use this command after configuring your ISDN switch type and any necessary SPIDs. The command will show you the switch type (and will also show you if you did not configure a switch type), and whether the SPIDs you entered are valid:
R1#show isdn status
Global ISDN Switchtype = basic-ni < ISDN switch type is correctly configured.> ISDN BRI0 interface
dsl 0, interface ISDN Switchtype = basic-ni
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 91, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
TEI = 92, Ces = 2, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
Spid Status:
TEI 91, ces = 1, state = 5(init)
spid1 configured, no LDN, spid1 sent, spid1 valid < SPID 1 is good.>
Endpoint ID Info: epsf = 0, usid = 1, tid = 1
TEI 92, ces = 2, state = 5(init)
spid2 configured, no LDN, spid2 sent, spid2 valid
Endpoint ID Info: epsf = 0, usid = 3, tid = 1
Layer 3 Status:
0 Active Layer 3 Call(s)
Activated dsl 0 CCBs = 0
The Free Channel Mask: 0x80000003
Once in a while, you'll get this output from show isdn status:
R2#show isdn status The current ISDN Switchtype = basic-ni1 ISDN BRI0 interface
Layer 1 Status:
ACTIVE
Layer 2 Status:
Layer 2 NOT Activated
Spid Status:
TEI Not Assigned, ces = 1, state = 3(await establishment)
spid1 configured, no LDN, spid1 NOT sent, spid1 NOT valid
TEI Not Assigned, ces = 2, state = 1(terminal down)
spid2 configured, no LDN, spid2 NOT sent, spid2 NOT valid
Check your running configuration, and if the SPIDs look good, simply close the BRI interface and open it again. Then run show ISDN status again. If you then see 'spids are valid???, you're ready to proceed. If you still see a message that the spids are invalid, you've most likely mistyped the SPID.
Show Access-List
What's this command got to do with ISDN? Everything.
Remember how the ISDN link comes up in the first place? Interesting traffic. By default, there is no interesting traffic. You define interesting traffic with the dialer-list and dialer-group commands, AND the access-list command. If you have a problem with your link never coming up or with it coming up and staying up, use this command to see what traffic has been defined as interesting.
Show Dialer
Another helpful command to determine why an ISDN link is coming up and staying up. This command sho
Volatility has done it again. What should investors be doing now? Those looking to rejuvenate their underperforming portfolios and capitalize on further market gains might have to bear their losses and research for the best possible holdings in the new market cycle.Thus, instead of panicking, selling existing investments and jumping into sectors which have either performed well recently or are the flavor of the month, the more logical course of action would be to review your entire portfolio. Sell any underperforming speculative stocks, evaluate other holdings individually, ensure you diversify across sectors and match your risk profile and look for companies that pay dividends.You should give your portfolio a thorough review. Investigate each investment carefully in order to determine if it's worth holding on to. Selling your investments because you've held them for a long time isn't the good solution and holding onto them isn't the answer as well. To determine if you should take profit, ask yourself if the price has gone up as high as they're likely to.<
It's important to know the proper show and debug commands for ISDN for several reasons. First, by watching ISDN in operation, you can see its processes and better understand what's going on. Secondly, it's difficult if not impossible to properly troubleshoot ISDN without knowing the proper show and debug commands. (It's easy to overlook an ISDN authentication error just by looking at the configuration, but running debug ppp negotiation will quickly show you where the problem lies.)
Let's take a look at the ISDN show and debug commands that every CCNA and CCNP should know.
Show ISDN Status
If you only know one ISDN show command, it's got to be this one. Always use this command after configuring your ISDN switch type and any necessary SPIDs. The command will show you the switch type (and will also show you if you did not configure a switch type), and whether the SPIDs you entered are valid:
R1#show isdn status
Global ISDN Switchtype = basic-ni < ISDN switch type is correctly configured.> ISDN BRI0 interface
dsl 0, interface ISDN Switchtype = basic-ni
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 91, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
TEI = 92, Ces = 2, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
Spid Status:
TEI 91, ces = 1, state = 5(init)
spid1 configured, no LDN, spid1 sent, spid1 valid < SPID 1 is good.>
Endpoint ID Info: epsf = 0, usid = 1, tid = 1
TEI 92, ces = 2, state = 5(init)
spid2 configured, no LDN, spid2 sent, spid2 valid
Endpoint ID Info: epsf = 0, usid = 3, tid = 1
Layer 3 Status:
0 Active Layer 3 Call(s)
Activated dsl 0 CCBs = 0
The Free Channel Mask: 0x80000003
Once in a while, you'll get this output from show isdn status:
R2#show isdn status The current ISDN Switchtype = basic-ni1 ISDN BRI0 interface
Layer 1 Status:
ACTIVE
Layer 2 Status:
Layer 2 NOT Activated
Spid Status:
TEI Not Assigned, ces = 1, state = 3(await establishment)
spid1 configured, no LDN, spid1 NOT sent, spid1 NOT valid
TEI Not Assigned, ces = 2, state = 1(terminal down)
spid2 configured, no LDN, spid2 NOT sent, spid2 NOT valid
Check your running configuration, and if the SPIDs look good, simply close the BRI interface and open it again. Then run show ISDN status again. If you then see 'spids are valid???, you're ready to proceed. If you still see a message that the spids are invalid, you've most likely mistyped the SPID.
Show Access-List
What's this command got to do with ISDN? Everything.
Remember how the ISDN link comes up in the first place? Interesting traffic. By default, there is no interesting traffic. You define interesting traffic with the dialer-list and dialer-group commands, AND the access-list command. If you have a problem with your link never coming up or with it coming up and staying up, use this command to see what traffic has been defined as interesting.
Show Dialer
Another helpful command to determine why an ISDN link is coming up and staying up. This command sho
Closing costs on your home mortgage are normally the thing that buyers don't worry about until the last minute. Problem is, if you don't think about closing costs until the last minute, you will likely be shocked when you find out that these costs run into the thousands of dollars. Relax though and don't be intimidated. I have made the mistake of not planning, and I can show you how a little planning, can save you hundreds and potentially thousands at closing.If you can read a HUD1, then you should know exactly what you will be charged at closing. However, simply being able to read and understand a HUD1 doesn't mean that you'll save money. What you need to do prior to closing and during the entire time leading up to closing is be in the habit of every time you hire someone to complete work for you that's required for the close, ask how much they charge. Don't just accept the realtors recommendation for a home inspector. Ask around if possible. If you don't know the realtor that well, how do you know that their recommendations are best for you. Although they usual
R1#show isdn status
Global ISDN Switchtype = basic-ni < ISDN switch type is correctly configured.> ISDN BRI0 interface
dsl 0, interface ISDN Switchtype = basic-ni
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 91, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
TEI = 92, Ces = 2, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
Spid Status:
TEI 91, ces = 1, state = 5(init)
spid1 configured, no LDN, spid1 sent, spid1 valid < SPID 1 is good.>
Endpoint ID Info: epsf = 0, usid = 1, tid = 1
TEI 92, ces = 2, state = 5(init)
spid2 configured, no LDN, spid2 sent, spid2 valid
Endpoint ID Info: epsf = 0, usid = 3, tid = 1
Layer 3 Status:
0 Active Layer 3 Call(s)
Activated dsl 0 CCBs = 0
The Free Channel Mask: 0x80000003
Once in a while, you'll get this output from show isdn status:
R2#show isdn status The current ISDN Switchtype = basic-ni1 ISDN BRI0 interface
Layer 1 Status:
ACTIVE
Layer 2 Status:
Layer 2 NOT Activated
Spid Status:
TEI Not Assigned, ces = 1, state = 3(await establishment)
spid1 configured, no LDN, spid1 NOT sent, spid1 NOT valid
TEI Not Assigned, ces = 2, state = 1(terminal down)
spid2 configured, no LDN, spid2 NOT sent, spid2 NOT valid
Check your running configuration, and if the SPIDs look good, simply close the BRI interface and open it again. Then run show ISDN status again. If you then see 'spids are valid???, you're ready to proceed. If you still see a message that the spids are invalid, you've most likely mistyped the SPID.
Show Access-List
What's this command got to do with ISDN? Everything.
Remember how the ISDN link comes up in the first place? Interesting traffic. By default, there is no interesting traffic. You define interesting traffic with the dialer-list and dialer-group commands, AND the access-list command. If you have a problem with your link never coming up or with it coming up and staying up, use this command to see what traffic has been defined as interesting.
Show Dialer
Another helpful command to determine why an ISDN link is coming up and staying up. This command sho
If you or a business opportunities seller you may wish to know that there will be some new disclosure rules and new requirements in the near future. In fact the Federal Trade Commission is now discussing a set of proposed rule changes, which would level the playing field for franchisers and business opportunities.Additionally it appears by the Federal Trade Commission's recent report on these proposed rule changes that they wish to protect the consumer, weed out the unethical practitioners in the business opportunities sector and help those of the highest ethical standards in the business opportunities sector become more successful. Why do I assume this you ask?Well, having previously been the founder of a franchising company, I always found it odd that there were so many unscrupulous business opportunities sellers to compete with. And it was obvious to me that it was quite unfair to have to follow all the rules while other people broke the law. If you are one of the many ethical business opportunities sellers you know how frustrating that can be. Below is the Fe
Endpoint ID Info: epsf = 0, usid = 3, tid = 1
Layer 3 Status:
0 Active Layer 3 Call(s)
Activated dsl 0 CCBs = 0
The Free Channel Mask: 0x80000003
Once in a while, you'll get this output from show isdn status:
R2#show isdn status The current ISDN Switchtype = basic-ni1 ISDN BRI0 interface
Layer 1 Status:
ACTIVE
Layer 2 Status:
Layer 2 NOT Activated
Spid Status:
TEI Not Assigned, ces = 1, state = 3(await establishment)
spid1 configured, no LDN, spid1 NOT sent, spid1 NOT valid
TEI Not Assigned, ces = 2, state = 1(terminal down)
spid2 configured, no LDN, spid2 NOT sent, spid2 NOT valid
Check your running configuration, and if the SPIDs look good, simply close the BRI interface and open it again. Then run show ISDN status again. If you then see 'spids are valid???, you're ready to proceed. If you still see a message that the spids are invalid, you've most likely mistyped the SPID.
Show Access-List
What's this command got to do with ISDN? Everything.
Remember how the ISDN link comes up in the first place? Interesting traffic. By default, there is no interesting traffic. You define interesting traffic with the dialer-list and dialer-group commands, AND the access-list command. If you have a problem with your link never coming up or with it coming up and staying up, use this command to see what traffic has been defined as interesting.
Show Dialer
Another helpful command to determine why an ISDN link is coming up and staying up. This command sho
Choosing a hosting provider can seem like a quite a headache when you don’t know exactly what you’re looking for. In general, there are several factors that are common with all hosting providers, and which you will need to consider before making the final choice of which hosting provider to choose. Before signing up with a provider, ask yourself the following questions:• How much money are you willing to invest in your website? Most websites can be up and running in a couple of days for very inexpensive prices, but consider just how much you are willing to invest in your site before choosing a provider. Remember, hosting might not be the only thing you are spending money on when setting up your site, so budget accordingly.• How much hard disk storage will your website require? Will your site be a large database of files, or a mostly text based web page? If you are going to be hosting large files on your site, like pictures or music, make sure you know exactly how much space all those files are going to take up so you can have an idea of how much hard drive spac
Show Access-List
What's this command got to do with ISDN? Everything.
Remember how the ISDN link comes up in the first place? Interesting traffic. By default, there is no interesting traffic. You define interesting traffic with the dialer-list and dialer-group commands, AND the access-list command. If you have a problem with your link never coming up or with it coming up and staying up, use this command to see what traffic has been defined as interesting.
Show Dialer
Another helpful command to determine why an ISDN link is coming up and staying up. This command shows you how many successful calls and failed calls have taken place, what the current idle-timer value is (by default, it's 120 seconds), and most importantly, what the source and destination was for the current interesting traffic:
R1#show dialer
BRI0 - dialer type = ISDN
Dial String Successes Failures Last called Last status
8358662 1 0 00:00:59
successful
0 incoming call(s) have been screened.
0 incoming call(s) rejected for callback.
BRI0:1 - dialer type = ISDN
Idle timer (120 secs), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is data link layer up
Dial reason: ip (s=172.12.21.1, d=172.12.21.2) < s=Source, d=Destination >
Time until disconnect 62 secs
< Idle timer, reset by interesting traffic only >
Connected to 8358662 (R2)
Here, you can see that the idle-timer value is at its default, that there are 62 seconds left until the link comes down (unless interesting traffic resets the timer), and that the source of the interesting traffic was 172.12.21.1 and the destination is 172.12.21.2. If that destination is the multicast address of a routing protocol - say, 224.0.0.5 for OSPF - you know what traffic is keeping the line up.
Show ISDN History
Want to see what calls have been made in the last 15 minutes? Just run this command. It's helpful if you're walking in to an ISDN troubleshooting situation and want to see what calls have been made.
R1#show isdn
history-------------------------------------------------------------------------------- ISDN CALL HISTORY--------------------------------------------------------------------------------History table has a maximum of 100 entries.History table data is retained for a maximum of 15 Minutes.--------------------------------------------------------------------------------Call Calling Called Remote Seconds Seconds Seconds ChargesType Number .Number Name Used Left Idle Units/Currency-----------------------------------------------------------------------------------------------------------Out 8358662 R2 121 0Out 8358662 R2 121 0-----------------------------------------------------------------------------------------------------
Debug PPP Negotiation
Not only do you need to know this command for your CCNA and CCNP exams, you MUST know it to be an effective ISDN troubleshooter.
When PPP authentication is first configured, it's simple to mistype a password, or forget to configure a 'username / password??? combination. Instead of continually reading your running configuration to see what the problem is, run debug ppp negotiation and send a ping to bring the line up. You'll quickly see where the problem is.
R2#debug ppp negotiation PPP protocol negotiation debugging is on R2#ping 172.12.21.1
BR0:1 PPP: Phase is AUTHENTICATING, by both < Both routers are authenticating the other with CHAP. > BR0:1 CHAP: O CHALLENGE id 1 len 23 from "R2" < R2 is sending a challenge to the remote router.
HTTP = HTML link (for blogs, profiles,phorums):
<a href="http://www.added4u.com/article/171321/added4u-Cisco-Certification--Introduction-To-ISDN-Part-V.html">Cisco Certification: Introduction To ISDN, Part V</a>
BB link (for phorums):
[url=http://www.added4u.com/article/171321/added4u-Cisco-Certification--Introduction-To-ISDN-Part-V.html]Cisco Certification: Introduction To ISDN, Part V[/url]
Related Articles:
The Fastest Way To Build Your List
Are Pay Per Click Services Cost Effective?
Bookmark it:
|