Single Interface

Single Interface

Let’s get started by attractive at a simple example. Say that you aloof appetite to affix two routers

with a distinct PVC. Here’s how that agreement would look:

RouterA#config t

Enter agreement commands, one per line. End with CNTL/Z.

RouterA(config)#int s0/0

RouterA(config-if)#encapsulation frame-relay

RouterA(config-if)#ip abode 172.16.20.1 255.255.255.0

RouterA(config-if)#frame-relay lmi-type ansi

RouterA(config-if)#frame-relay interface-dlci 101

RouterA(config-if)#^Z

RouterA#

The aboriginal footfall is to specify the encapsulation as Frame Relay. Notice that back I didn’t specify

a accurate encapsulation type—either Cisco or IETF—the Cisco absence blazon was used. If the

other router were non-Cisco, I would’ve defined IETF. Next, I assigned an IP abode to the

interface and afresh defined the LMI blazon of ANSI (the absence actuality Cisco) based on information

provided by the telecommunications provider. Finally, I added the DLCI of 101, which

indicates the PVC I appetite to use (again, accustomed to me by my ISP) and assumes there’s alone one

PVC on this concrete interface.

That’s all there is to it—if both abandon are configured correctly, the ambit will appear up.

Check out Hands-on Lab 14.3 in the Sybex CCNA 640-802 Study Guide for a

complete archetype of this blazon of configuration, including instructions on creating

your own Frame Relay about-face from a router.