Okay maybe I am thick or simply not getting it but for example look at the topology used by ipexpert its a frame switch with 4 spokes. In the context of configuration of the frame switch I am trying to understand why so many DLCI are used for configuration.
Example aside from turning on frame switching and enabling frame relay per serial connection of appropiate DCE side etc. the frame map parts frame-relay route map 104 interface serial 1/0 401 (thats from R2 to R4) frame-relay route map 104 interface serial 1/2 501 (thats from R5 to R2) frame-relay route map 106 interface serial 1/3 601 (thats from R2 to R6) Surely I only need the inverse of this per serial for full connectivity so why is the frame switch configuration thus for proctor labs...in short why so many dlci mappings I am clearly missing something. I simply am not getting why I need so many dlci mappings can someone go through it ..Im sure it will be of use to those of us whom don't do frame relay day in day out ...and on lab 1 technology focused too....AGH... interface Serial0 description Connection to R2 INT S0/1/0 no ip address no ip mroute-cache encapsulation frame-relay no fair-queue clockrate 64000 frame-relay intf-type dce frame-relay route 104 interface Serial1 401 frame-relay route 105 interface Serial2 501 frame-relay route 106 interface Serial3 601 frame-relay route 204 interface Serial1 402 frame-relay route 205 interface Serial2 502 frame-relay route 206 interface Serial3 602 frame-relay route 214 interface Serial1 412 frame-relay route 215 interface Serial2 512 frame-relay route 216 interface Serial3 612 frame-relay route 224 interface Serial1 422 frame-relay route 225 interface Serial2 522 frame-relay route 226 interface Serial3 622 ! interface Serial1 description Connection to R4 INT s0/0/0 no ip address encapsulation frame-relay clockrate 2000000 frame-relay intf-type dce frame-relay route 401 interface Serial0 104 frame-relay route 402 interface Serial0 204 frame-relay route 405 interface Serial2 504 frame-relay route 406 interface Serial3 604 frame-relay route 412 interface Serial0 214 frame-relay route 415 interface Serial2 514 frame-relay route 416 interface Serial3 614 frame-relay route 422 interface Serial0 224 frame-relay route 425 interface Serial2 524 frame-relay route 426 interface Serial3 624 ! interface Serial2 description Connection to R5 int S0/1/0 no ip address encapsulation frame-relay clockrate 64000 frame-relay intf-type dce frame-relay route 501 interface Serial0 105 frame-relay route 502 interface Serial0 205 frame-relay route 504 interface Serial1 405 frame-relay route 506 interface Serial3 605 frame-relay route 512 interface Serial0 215 frame-relay route 514 interface Serial1 415 frame-relay route 516 interface Serial3 615 frame-relay route 522 interface Serial0 225 frame-relay route 524 interface Serial1 425 frame-relay route 526 interface Serial3 625 ! interface Serial3 description Connection to R6 Int S4/0 no ip address encapsulation frame-relay clockrate 115200 frame-relay intf-type dce frame-relay route 601 interface Serial0 106 frame-relay route 602 interface Serial0 206 frame-relay route 604 interface Serial1 406 frame-relay route 605 interface Serial2 506 frame-relay route 612 interface Serial0 216 frame-relay route 614 interface Serial1 416 frame-relay route 615 interface Serial2 516 frame-relay route 622 interface Serial0 226 frame-relay route 624 interface Serial1 426 frame-relay route 625 interface Serial2 526 ! interface BRI0 no ip address shutdown ! ip classless _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
