| One of the major topics on your CCNA and CCNP | | | | directed-broadcastencapsulation |
| exams is Frame Relay. Additionally, Frame | | | | frame-relaylogging event |
| Relay is one of the most popular WAN | | | | subif-link-statuslogging event |
| technolgies in today's networks. Getting | | | | dlci-status-changeclockrate 56000no |
| hands-on experience with Frame Relay in Cisco | | | | frame-relay inverse-arpframe-relay intf-type |
| networks isn't just a good idea, it's a | | | | dceframe-relay route 321 interface Serial1 |
| necessity. Let's face it, your employer is | | | | 123 |
| going to get a little touchy if you start | | | | |
| experimenting with your network's Frame Relay | | | | !interface BRI0ip address 150.1.1.1 |
| setup. | | | | 255.255.255.252no ip |
| | | | directed-broadcastencapsulation pppdialer map |
| To practice all your important Frame Relay | | | | ip 150.1.1.2 name R2 broadcast |
| commands for your exams, you need a working | | | | 2335552221dialer-group 1 |
| Frame Relay cloud in your home lab. A | | | | |
| production network's Frame cloud consists of | | | | !ip classless |
| a lot of Frame switches, but if you choose | | | | |
| wisely, a single Cisco router can act as your | | | | !dialer-list 1 protocol ip permit |
| home lab's entire Frame cloud! | | | | |
| | | | !line con 0exec-timeout 0 0logging |
| Before we look at the configuration of such a | | | | synchronoustransport input noneline aux 0line |
| router (hereafter referred to as a "frame | | | | vty 0 4login |
| relay switch"), let's look at the physical | | | | |
| requirements. | | | | !end |
| | | | |
| The more serial ports you have, the better. | | | | The key command in the global configuration |
| You should get a router with at least four | | | | is frame-relay switching. You must have this |
| serial ports. For frame switching purposes, | | | | configured before you can configure the |
| it doesn't matter if the ports are | | | | interfaces. |
| synchronous or asynchronous - you just need | | | | |
| the ports. | | | | The interfaces will be configured with the |
| | | | frame route command. Let's take a look at |
| You will also need some DTE/DCE cables. The | | | | what each value means in the command |
| DCE end of the cables will be connected to | | | | frame-relay route 122 interface Serial2 |
| the frame switch. | | | | 221.frame-relay route - the command |
| | | | |
| A great configuration for a CCNA practice lab | | | | 122 - the incoming DLCI on this |
| is three routers that serve as "production" | | | | interfaceinterface serial2 - the interface |
| routers, and a 4th router as a frame relay | | | | the data will be sent out |
| switch. (You'll want an access server as | | | | |
| well, but that's another article.) | | | | 221 - the outgoing DLCI |
| | | | |
| What I use in my student and customer pods is | | | | This command on S1 means that anything that |
| a setup where R1 is connected to the frame | | | | comes in on this port on DLCI 122 will be |
| switch's S1 port, R2 is connected to S2 on | | | | sent out interface serial2 on DLCI 221. |
| the frame switch, and R3 is connected to the | | | | |
| frame switch's S3 port. | | | | It's a good idea to hard-code the interfaces |
| | | | to act as DCEs with the frame intf-type dce |
| Now comes the tricky part - the | | | | command. Since these interfaces are acting as |
| configuration. A frame relay switch's config | | | | DCEs, the clockrate command is needed for the |
| can be hard to find, so here's a copy of | | | | line protocol to come up. |
| mine. Pay particular attention to the config | | | | |
| on ports s1, s2, and s3.version 12.0service | | | | Once you've configured your frame switch as |
| timestamps debug uptimeservice timestamps log | | | | shown and have configured the frame map |
| uptimeno service password-encryption | | | | statements on the "production" routers, you |
| | | | can test the frame switch configuration. On |
| !hostname FRAME_SWITCH | | | | the frame switch, run the command show frame |
| | | | route. |
| ! | | | | |
| | | | FRAME_SWITCH#show frame route |
| !ip subnet-zerono ip domain-lookupframe-relay | | | | |
| switching | | | | Input Intf Input Dlci Output Intf Output Dlci |
| | | | Status |
| ! | | | | |
| | | | Serial1 122 Serial2 221 active |
| ! | | | | |
| | | | Serial1 123 Serial3 321 active |
| !interface Ethernet0no ip addressno ip | | | | |
| directed-broadcastshutdown | | | | Serial2 221 Serial1 122 active |
| | | | |
| !interface Serial0ip address 10.1.1.2 | | | | Serial3 321 Serial1 123 active |
| 255.255.255.0clockrate 56000 | | | | |
| | | | You should see "active" for all the |
| !interface Serial1no ip addressno ip | | | | interfaces. If you see "deleted", make sure |
| directed-broadcastencapsulation | | | | your frame switch interfaces are open if they |
| frame-relaylogging event | | | | are, check the router configs. |
| subif-link-statuslogging event | | | | |
| dlci-status-changeclockrate 56000no | | | | Keep in mind that you can still configure |
| frame-relay inverse-arpframe-relay intf-type | | | | routing protocols to run on ports that you're |
| dceframe-relay route 122 interface Serial2 | | | | not using for frame switching. The router we |
| 221frame-relay route 123 interface Serial3 | | | | used here had an ethernet port and BRI port, |
| 321 | | | | and the BRI port has been configured as part |
| | | | of the production network. Running frame |
| !interface Serial2no ip addressno ip | | | | switching does not disable IP routing. |
| directed-broadcastencapsulation | | | | |
| frame-relaylogging event | | | | Purchasing and configuring your own frame |
| subif-link-statuslogging event | | | | relay switch is an invaluable part of your |
| dlci-status-changeclockrate 56000no | | | | Cisco education. By practicing your frame |
| frame-relay inverse-arpframe-relay intf-type | | | | commands and configuring frame connections |
| dceframe-relay route 221 interface Serial1 | | | | over your own frame relay cloud, you're |
| 122 | | | | polishing your Cisco skills and gaining |
| | | | knowledge that cannot be duplicated by |
| !interface Serial3no ip addressno ip | | | | simulator programs. |