Académique Documents
Professionnel Documents
Culture Documents
Not sure I understand your question and I haven't used Packet tracer but you would have the point to multipoint on
the head end router. Each DLCI would be a separate subinterface.
I.E.
Serial0/0/0.101
Serial0/0/0.102
Of course you can call the subinterfaces anything you want just put in 101 and 102 as an example. Go over the
frame-relay portion of the CCNA book for more info
Hi Olabisi,
It is not difficult to configure the frame relay cloud.
Click on the cloud, then click CONFIG, you will see a list of all the interfaces present, under the heading
INTERFACES on the left hand side. When you click on any of the interface, you will see the textboxes to configure
lmi, dlci etc. on right side.
Where exactly are you facing the problem ?
Can you attach your packet tracer file ?
If that is not possible, can you attach the picture of your desired network ?
You can take a screenshot of the network in packet tracer also and attach here as a file.
in response to: Chetan Hello Chetan, I am new to Packet Tracer and I am also having problems configuring the
Cloud. I have attached screenshots of my setup to give you an idea of what I'm trying to do. When I try to configure
the cloud, it won't let me map more than one connection as you can see in the Error screenshot. What am I missing?
What am I doing wrong? Any help would be appreciated.
Thanks!
http://img190.imagevenue.com/img.php?image=75341_Frame_Relay_Network_122_238lo.JPG
http://img249.imagevenue.com/img.php?image=75215_DLCI_50_122_42lo.jpg
http://img23.imagevenue.com/img.php?image=75216_DLCI_51_122_1160lo.jpg
http://img169.imagevenue.com/img.php?image=75223_DLCI_52_122_762lo.jpg
http://img46.imagevenue.com/img.php?image=75225_DLCI_53_122_336lo.jpg
http://img132.imagevenue.com/img.php?image=75226_Error_122_937lo.jpg
Hi Olabisi,
You were trying to map one router interface directly to many dlci. This is not the right way.
Instead you should create subinterfaces first, and then do the mapping.
Map One subinterface per DLCI.
And also don't forget to set the encapsulation of the router's interface to frame-relay. By default encapsulation is
HDLC.
There are many things that you can't set using the GUI. So you have to use CLI on routers. There is no alternative.
I am attaching the exact coding and all the required commands.
I Hope this will solve your problem.
Let me know the progres.
https://cisco.hosted.jivesoftware.com/thread/2650?tstart=0
There is no information in it about how to config FR cloud. Because Olabisi has already done that part in the original
question.
In addition to configuring DLCIs on Routers, it is also necessary that FR switches from the service provider are also
configured with those DLCI values. But in our case we have access to FR cloud as a whole ( and not any particular
FR Switch).
Attachments:
•
Your point about DTE is correct. I am also using the same cabling.
DTE(config)#router eigrp 1
DTE(config-router)#network 10.10.10.0 0.0.0.255
DTE(config-router)#network 192.168.1.0
DTE(config-router)#exit
There is nothing new as far as enabling of routing protocols is concerned.
4. We can use all the three lmi-types in Packet tracer 5.0 viz. Cisco, Q933a and Ansi.
5. As far as your last question is concerned, after reading many many reviews of qualified CCNAs, I am getting
a feeling that whatever is given in Todd Lammle and Cisco Press Books ( ICND1 and ICND2) will be more than
enough for the CCNA exam. But I would also like to add that I have still to appear for CCNA.
I hope it helps,
Regards,
Chetan
Thank you very much for replying in detail, nice to hear that you are too preparing for CCNA.
Many thanks once again
Ahsan
,
in response to: Chetan LoL.. Sometimes we just need a nudge! Don't forget to post a link to your document so
that the Googlers who happen across this thread find it as well..
2. They signal whether a PVC is active or inactive. An access link might be up, but one or more VCs could be down.
DTE needs to know which VCs are up and which are down. It learns that information from the switch using LMI
status messages.
If you disable keepalive using "no keepalive" interface configuration command, then you won't get above information
automatically. So if the PVCs are working properly, it won't disturb the DTE. But if PVCs are facing a problem, you
won't be able to communicate. But the main problem is you won't come to know easily where is the problem whether
PVC is active, inactive or deleted.. LMI provide this useful information automatically to you.
And also remember that LMI doesn't work end to end i.e. DTE to DTE. It works only between DTE and FR Switch.
It is somewhat similar to how Dynamic Routing Protocols work. If you have configured static routes to a destination,
then that route would always be available in the routing table even if the destination network is removed later on. ( I
am not talking about the local exit interface going down, in which case static route might be removed from the table)
But if you configured OSPF or EIGRP or RIP etc, then they can automatically add/remove the routes in the routing
table depending upon the timers and updates received. Thus they provide useful information automatically.
Does it provide any help ??