{"id":83,"date":"2011-05-22T12:10:11","date_gmt":"2011-05-22T10:10:11","guid":{"rendered":"http:\/\/www.zed-network.fr\/blog\/?p=83"},"modified":"2011-05-22T12:10:11","modified_gmt":"2011-05-22T10:10:11","slug":"switch-frame-relay","status":"publish","type":"post","link":"https:\/\/zed-network.fr\/?p=83","title":{"rendered":"Switch Frame-relay"},"content":{"rendered":"<h1>Configuration d&#8217;un switch frame-relay<\/h1>\n<p>Dans cette architecture nous avons trois routeurs dont un qui \u00e0 le role de switch Frame-Relay.<\/p>\n<p>&nbsp;<\/p>\n<h2>Configuration du swith frame-relay<\/h2>\n<p>Pour cela il est necessaire d&#8217;activer le frame-relay switching :<\/p>\n<pre>frame-relay switching.<\/pre>\n<p>Ensuite il faut d\u00e9finir quel port sera attach\u00e9 \u00e0 tel routeur avec les bon DLCI. Dans notre exemple, nous aurons la configuration suivante :<\/p>\n<pre> R1 |-DLCI 104 ---------------se0\/0-| FR1 |-se0\/1---------------DLCI 401-| R4  <\/pre>\n<p>Configuration de FR1 :<\/p>\n<pre>\r\ninterface Serial0\/0\r\n no ip address\r\n encapsulation frame-relay\r\n serial restart-delay 0\r\n frame-relay intf-type dce\r\n frame-relay route 104 interface Serial0\/1 401\r\n!\r\ninterface Serial0\/1\r\n no ip address\r\n encapsulation frame-relay\r\n serial restart-delay 0\r\n frame-relay intf-type dce\r\n frame-relay route 401 interface Serial0\/0 104\r\n!\r\n<\/pre>\n<p>Configuration des interfaces series de R1 et R4 :<\/p>\n<pre>\r\nR1#sh run int se1\/0\r\nBuilding configuration...\r\n\r\nCurrent configuration : 212 bytes\r\n!\r\ninterface Serial1\/0\r\n ip address 192.168.1.1 255.255.255.0\r\n encapsulation frame-relay\r\n serial restart-delay 0\r\n frame-relay map ip 192.168.1.4 104\r\n frame-relay interface-dlci 104\r\n no frame-relay inverse-arp\r\n\r\ninterface Serial0\/0\r\n ip address 192.168.1.4 255.255.255.0\r\n encapsulation frame-relay\r\n serial restart-delay 0\r\n frame-relay map ip 192.168.1.1 401\r\n frame-relay interface-dlci 401\r\n no frame-relay inverse-arp\r\n<\/pre>\n<h1>V\u00e9rification<\/h1>\n<pre>\r\nFR1#sh frame-relay route\r\nInput Intf      Input Dlci      Output Intf     Output Dlci     Status\r\nSerial0\/0       104             Serial0\/1       401             active\r\nSerial0\/1       401             Serial0\/0       104             active\r\n!\r\nFR1#sh frame-relay pvc | inc DLCI\r\nDLCI = 104, DLCI USAGE = SWITCHED, PVC STATUS = ACTIVE, INTERFACE = Serial0\/0\r\nDLCI = 401, DLCI USAGE = SWITCHED, PVC STATUS = ACTIVE, INTERFACE = Serial0\/1\r\n\r\nR1#sh frame map\r\nSerial1\/0 (up): ip 192.168.1.4 dlci 104(0x68,0x1880), static,\r\n              CISCO, status defined, active\r\nR1#sh frame pvc | inc DLCI\r\nDLCI = 104, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1\/0\r\n\r\nR4#sh frame map\r\nSerial0\/0 (up): ip 192.168.1.1 dlci 401(0x191,0x6410), static,\r\n              CISCO, status defined, active\r\nR4#sh frame pvc | inc DLCI\r\nDLCI = 401, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0\/0\r\n\r\nR1#p 192.168.1.4 re 50\r\n\r\nType escape sequence to abort.\r\nSending 50, 100-byte ICMP Echos to 192.168.1.4, timeout is 2 seconds:\r\n!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\r\nSuccess rate is 100 percent (50\/50), round-trip min\/avg\/max = 4\/14\/72 ms\r\n<\/pre>\n","protected":false},"excerpt":{"rendered":"<p>Configuration d&#8217;un switch frame-relay Dans cette architecture nous avons trois routeurs dont un qui \u00e0 le role de switch Frame-Relay. &nbsp; Configuration du swith frame-relay Pour cela il est necessaire d&#8217;activer le frame-relay switching : frame-relay switching. Ensuite il faut d\u00e9finir quel port sera attach\u00e9 \u00e0 tel routeur avec les bon DLCI. Dans notre exemple, [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"footnotes":""},"categories":[3,4,11],"tags":[],"class_list":["post-83","post","type-post","status-publish","format-standard","hentry","category-ccie-rs","category-cisco","category-frame-relay"],"_links":{"self":[{"href":"https:\/\/zed-network.fr\/index.php?rest_route=\/wp\/v2\/posts\/83","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/zed-network.fr\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/zed-network.fr\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/zed-network.fr\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/zed-network.fr\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=83"}],"version-history":[{"count":1,"href":"https:\/\/zed-network.fr\/index.php?rest_route=\/wp\/v2\/posts\/83\/revisions"}],"predecessor-version":[{"id":84,"href":"https:\/\/zed-network.fr\/index.php?rest_route=\/wp\/v2\/posts\/83\/revisions\/84"}],"wp:attachment":[{"href":"https:\/\/zed-network.fr\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=83"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/zed-network.fr\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=83"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/zed-network.fr\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=83"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}