From: Schulz, Dave (DSchulz@dpsciences.com)
Date: Wed Jan 18 2006 - 15:20:07 GMT-3
Interestingly enough, I was working on a lab from one of the well-known
vendors yesterday......where the scenario disallowed you from using the
frame interface-dlci command AND the frame map statements, and to not
allow any unused dlci to show up. This had me stumped! However, it
does work....and the solution is to enable frame-relay, set the IP
address and add no frame-relay inverse <#dlci> to the interface. At
first, I thought that there was no way this was going to work. But it
did. I have to research this a bit further. Maybe some of the experts
can chime in on this. It appears that the encapsulation frame-relay is
doing a lot more behind the scenes in this new rev. Very different!
Dave Schulz,
Email: dschulz@dpsciences.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
CCIEin2006
Sent: Wednesday, January 18, 2006 12:40 PM
To: Cisco certification
Subject: Frame relay auto-config?
Hey guys,
I noticed some interesting behavior on my lab routers when I load my
initial
configs. I was hoping each of these points could be addressed:
1. Encapsulation frame-relay IETF is automatically configured even
though it
is neither in my initial config nor the encapsulation type used on my
frame
relay switch. My frame relay switch is using default encapsulation of
Cisco.
2. I am able to ping between a router configured with IETF and another
router configured with Cisco encapsulation on the other end! I thought
the
two encapsulation types were incompatible?
3. Although the serial interfaces are enabled, IP's are configured, and
PVC's are active, there are no dynamic mapping statements when I do a
show
frame-relay map. I thought the reason why you shut the interface even
before
configuring frame-relay was to prevent this dynamic mapping?
4. The command frame-relay lmi-type cisco is automatically added to my
configuration. I thought the default is to use LMI autosense?
Thanks again!
This archive was generated by hypermail 2.1.4 : Wed Feb 01 2006 - 07:45:49 GMT-3