Did some more digging in the DocCD and found my answer:
The following example sets IETF encapsulation at the interface level. The
keyword *ietf* sets the default encapsulation method for all maps to IETF.
encapsulation frame-relay ietf
frame-relay map ip 131.108.123.2 48 broadcast
frame-relay map ip 131.108.123.3 49 broadcast
IETF Encapsulation on a Per-DLCI Basis Example
The following example configures IETF encapsulation on a per-DLCI basis.
This configuration has the same result as the configuration in the first
example.
encapsulation frame-relay
frame-relay map ip 131.108.123.2 48 broadcast ietf
frame-relay map ip 131.108.123.3 49 broadcast ietf
On Thu, Dec 23, 2010 at 11:08 AM, Brad Edgeworth <edgie512_at_gmail.com> wrote:
> So between 'frame-relay encapsulation' and 'frame-relay encapsulation
> ietf', one uses Cisco encapsulation and the other uses open standards
> version. Pretty straightforward.
>
> Now when it comes to our frame-relay map statements, should we use the IETF
> on those as well, if we are using 'frame-relay encapsulation ietf' as well?
>
> IE. 'frame-relay interface-dlci 100 IETF'
> or
> 'frame-relay map ip 1.1.1.1 101 ietf'
>
> If we forget the IETF on the lab, is this something that could cause us to
> lose points for not completing the lab; even though it functionally
> works....?
>
> Thanks for the input.
>
> -Brad
Blogs and organic groups at http://www.ccie.net
Received on Sun Dec 26 2010 - 00:40:29 ART
This archive was generated by hypermail 2.2.0 : Sat Jan 01 2011 - 09:37:49 ART