Limited access circuit
Switched parallel circuit
Customers can define their virtual circuit needs in far greater combinations, with increments as small as 64 kbps.
Customers pay for an end-to-end connection that includes the local loop and the network link.
Customers only pay for the local loop and the bandwidth they purchase from the network provider
Connecting new sites requires new lower cost circuit installations when compared to ISDN dialup costs or adding additional
Hardware for leased service.
Local address identifying a destination router across a Frame Relay network
Locally significant address used to identify a virtual circuit
Logical address identifying the interface between a router and a Frame Relay switch
Logical address used to identify the DCE
It helps to conserve IP addresses.
It establishes multiple PVC connections to multiple physical interfaces.
It eliminates split horizon issues without increasing the likelihood of routing loops.
It requires the configuration of the encapsulation command on the subinterface.
• It is currently not transmitting data.
It is in the process of establishing the PVC.
It has put a hold on processing frames in excess of the CIR.
It is experiencing congestion.
LMI updates are not being received properly.
The LMI type for the Serial 0/0/0 interface has been left to its default configuration.
Cisco HDLC is used as a Layer 2 encapsulation protocol on the Serial 0/0/0 interface.
The Serial 0/0/0 interface has been configured as a data communications equipment device
Serial 0/0/0 has been configured with an DLCI of 201
Serial 0/0/0 has the feature frame-relay inverse-arp enabled.
Serial 0/0/0 has been configured with an IP address of 172.16.4.3.
Serial 0/0/0 has been configured with the command frame-relay map ip 172.16.4.3 201 broadcast
The Frame Relay LMI DLCI has been incorrectly configured as DLCI 1023.
The Frame Relay LMI type has been changed from its default.
The Serial 0/0/0 interface has been configured as a data communication
The command encapsulation frame-relay ietf has been used on the Serial 0/0/0 interface
The broadcasts will be forwarded to 10.1.1.1
The router will use DLCI 22 to forward data to 10.1.1.1.
DLCI 22 will replace the MAC address in the ARP table for entry 10.1.1.1
Frames arriving on interface serial 0/0/0 of RT_1 will have a data link layer address of 22.
Inverse-ARP will now add an entry for 10.1.1.1 into the Frame Relay map table using DLCI 22.
The IP address of the local Frame Relay interface is 172.16.1.4.
The local DLCI number is 401.
Inverse ARP is being used on this connection.
This interface is in the active state and in the process of negotiating configuration parameters.
Multicast is not enabled on this connection.
The frame-relay map command requires the broadcast keyword.
The DLCIs on each end of the PVCs are not identical.
The R2 S0/0/0 interface has not been brought online
The LMI or Inverse ARP or both are not working.
Multipoint interfaces will automatically forward routing broadcasts but will consume more IP addresses than point-to-point
Subinterfaces will consume.
Point-to-point subinterfaces act like leased lines and eliminate split-horizon routing issues.
Interfaces with multiple PVCs require a separate subinterface for each PVC.
Multipoint configurations cannot use subinterfaces.
Split horizon must be disabled
The LMI type must be specified.
Logical subinterfaces must be used instead.
The frame-relay map commands are using incorrect DLCIs.