Which three statements about L2TPv3 are true? (Choose three)

Question

Options

• AL2TPv3 Frame Relay support includes only 32-bit DLCI addressing.
• BL2TPv3 sessions do not support Frame Relay LMI interworking.
• CMultipoint DLCI is not supported.
• DTo use DCE or a Network-to-Network Interface on a Frame Relay port, you must configure the
• EL2TPv3 feature does not support Frame Relay extended addressing.

• A
  5% (1)
• B
  14% (3)
• C
  81% (17)

Explanation

Frame Relay-Specific Restrictions -Frame Relay per-DLCI forwarding and port-to-port trunking are mutually exclusive. L2TPv3 does not support the use of both on the same interface at the same time. -The xconnect command is not supported on Frame Relay interfaces directly. For Frame Relay, the Xconnect is applied under the connect command specifying the DLCI to be used. -Changing the encapsulation type on any interface removes any existing xconnect command applied to that interface. -To use DCE or a Network-to-Network Interface (NNI) on a Frame Relay port, you must configure the framerelay switching command. -The configuration of an L2TPv3 session on a Multilink Frame Relay (MLFR) bundle interface is supported only on Cisco 12000 series Two-Port Channelized OC-3/STM-1 (DS1/E1) and Six-Port Channelized T3 (T1) line cards. (For more information, see Binding L2TPv3 Sessions to Multilink Frame Relay Interfaces.) -Frame Relay policing is nondistributed on the Cisco 7500 series. By configuring Frame Relay policing, you cause traffic on the affected PVCs to be sent to the RSP -Frame Relay support is for 10-bit DLCI addresses. Frame Relay Extended Addressing is not -Multipoint DLCI is not supported. -The keepalive will automatically be disabled on interfaces that have an Xconnect applied to Frame Relay encapsulation, which is a requirement for LMI. -Static L2TPv3 sessions will not support Frame Relay LMI interworking.

No community discussion yet for this question.