|
Home > Archive > CCNP > November 2000 > need help on bcran !!!.............thanks
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
need help on bcran !!!.............thanks
|
|
|
| hi,
Can someone help me with these 'basic' questions?
1) What does 'Int Async 0' refers to?Physically a port on the serial interface or logically ?
2) On page 114 of Cisco press BCRAN, point 3 state that Password must be identical on both end, but why is the Password set in Fig 5-7 not identical? Typo error?
3) Why do Fig 5-7 configure 'dialer-map' ?
Lastly, can i use ' username left password left1 ' ( from Sybex CCNA) instead of 'PPP pap sent-username left password left1 ' ???
Pls help..
Thanks in advance.
kill97 | |
|
| Kill97,
I'll try to answer.
They aren't bloody basic...
People, correct me if I'm out to lunch...
1. Interface anything is physical, that's what I know. Any router has a Async0 interface, where you hook up a modem, to be able to dial-up into the router (back door) to manage it remotely. Async0 is not the serial interface Serial0 e.g that you will use for Frame-relay. And is physical.
2. I don't have the book you're talking about. But I know from real life that if you use CHAP authentication, the password MUST be the same on both ends, because the password doesn't get transmitted through the wire, it's just referenced by both parties while creating the hash.
3.I don't have the book. Don't understand the question.
4. "username left password left1 " will just create a user named left with the password of left1 on the destination router .
'PPP pap sent-username left password left1' you will put on the calling router, to tell him to send the PAP password left1 upon attempted connection.
No, you can not substitute. Both commands are needed, one on the called router, one on the calling router.
| |
|
|
bravo, thanks transilvanian, i own you once.
P.S i been waiting 4 2 days for this questions to be answered. | |
|
| quote:
Originally posted by transilvanian:
Kill97,
I'll try to answer.
They aren't bloody basic...
People, correct me if I'm out to lunch...
1. Interface anything is physical, that's what I know. Any router has a Async0 interface, where you hook up a modem, to be able to dial-up into the router (back door) to manage it remotely. Async0 is not the serial interface Serial0 e.g that you will use for Frame-relay. And is physical.
2. I don't have the book you're talking about. But I know from real life that if you use CHAP authentication, the password MUST be the same on both ends, because the password doesn't get transmitted through the wire, it's just referenced by both parties while creating the hash.
3.I don't have the book. Don't understand the question.
4. "username left password left1 " will just create a user named left with the password of left1 on the destination router .
'PPP pap sent-username left password left1' you will put on the calling router, to tell him to send the PAP password left1 upon attempted connection.
No, you can not substitute. Both commands are needed, one on the called router, one on the calling router.
Just a note!
Becareful about stating "Interface anything is physical". When you create a Dialer Profile (interface dialer 0) you are actually creating a logical or virtual interface not a physical one. Then within this interface you create Dialer pools which associate a number of physical interfaces. | |
|
| Ouch, what an embarrasment! BigK is correct, ". When you create a Dialer Profile (interface dialer 0) you are actually creating a logical or virtual interface not a physical one."
So I was out to lunch when making that statement.Now, that I think it better, the point-to-point subinterfaces on the Frame Relay configs are logical as well..
Anyway, I'd venture to maintain "Interface Async 0" is physical, for the simple reason that I'm able to see it on the back of the router, labeled as such. | |
|
|
1 more thing, what is a rotary group? What is the function?
Thanks in advance.
kill97 | |
|
| Rotary Groups are generally for the Corporate Site (or an ISP). They allow dial up clients to use ONE phone number to access the first available interface from a pool.
I may be wrong, but I don't think they are used to dial out much anymore. | |
|
|
So does it mean that if i don't set a rotary group, every individual Asyn Interface needs its OWN unique phone number?
kill97
P.S 1 Async int = 1 line ? or multiple logical line ?
need help. | |
|
|
|
| can't you wait a little?
I didn't get to read that chapter yet! | |
|
| Kill, You ask a ton of questions and I'm sure the answers benefit alot of people,so don't take this wrong, but I have to ask.... Do you ever research anything yourself?
And yes if you configure individual Async interfaces each one will use a line and require its own phone number.
Yankee | |
|
| The way I read and understand the CISCO training BCRAN book, Rotary Groups are for dialing OUT. You associate physical interfaces to a rotary group, and then the router , when needed, will dial out using whatever physical interfaces available from that rotary group.
If you want INCOMING users to connect to an access server that has multiple modems by dialing only one phone number, you order from the telecom service provider ONE NUMBER WITH HUNT GROUP.
I have in my company a CISCO access server that has no "rotary group " configured on it whatsoever , and incoming users are able to connect simultaneously to many of its modems by just dialing the main number. The main number is a hunt group (that's how it was ordered), and the call will transparently be directed by the telecom provider to the next available modem.
In short: Dialer Rotary-group is relevant only when the router dials out. | |
|
| Dialer rotary groups make ease of configuration of physical interfaces, by allowing you to apply a single logical interface configuration to a number of physical interfaces. Simply put: if you have several physical interface with the same configurations, it is much easier to configure one (logical) and associate these physical interface to it.
Do remember the difference between dialer Pools and dialer rotary groups. With a dialer pool, you can associate one physical interface to several dialer pools, but with a dialer rotary group each physical interface can only belong to one rotary group.
Hope that helps! |
|
|
|
|