09.12.2012 Views

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

1.544Mbps. The actual transport link is ei<strong>the</strong>r a permanent or switched virtual<br />

circuit (PVC/SVC), with <strong>the</strong> former being <strong>the</strong> most common provisioning<br />

implementation.<br />

Because FR PVC is still <strong>the</strong> most common implementation, we will focus our<br />

examples on FR PVC configuration. Configuring a FR PVC has three basic steps:<br />

1. The interface must be enabled <strong>to</strong> use FR encapsulation, using <strong>the</strong> interface<br />

configuration subcommand:<br />

2.<br />

3. jupiter(config)# interface serial0<br />

4. jupiter(config-if)#encapsulation frame-relay<br />

5.<br />

6. After encapsulation is set, <strong>the</strong> Data-Link Connection Identifier (DLCI) and<br />

Local Management Interface (LMI) type need <strong>to</strong> be configured. The DCLI is<br />

set using <strong>the</strong> FR interface configuration subcommand . The LMI type can be configured dynamically (on<br />

IOS versions 11.2 and later) by <strong>the</strong> router when <strong>the</strong> interface is activated or<br />

<strong>the</strong> LMI can be set explicitly in <strong>the</strong> routers FR interface configuration. The<br />

default LMI is Cisco. IOS supports three LMI types: ansi (most often used),<br />

cisco, and q933a. Let's look at Jupiter's DCLI and LMI configuration:<br />

7.<br />

8. jupiter(config-if)#frame-relay interface-dcli 35<br />

9. jupiter(config-if)#lim-type ansi<br />

10.<br />

11. The last step is <strong>the</strong> configuration of <strong>the</strong> Layer 3 pro<strong>to</strong>col address assignment.<br />

FR supports four different <strong>network</strong> <strong>to</strong>pologies: point-<strong>to</strong>-point, meshed and<br />

partially meshed point-<strong>to</strong>-point, and multipoint. We will look at meshed and<br />

multipoint <strong>to</strong>pologies in a moment. If you are only running IP over a FR<br />

point-<strong>to</strong>-point connection, it is possible <strong>to</strong> configure <strong>the</strong> interface <strong>to</strong> use<br />

ei<strong>the</strong>r unnumbered IP or static IP address assignments. With unnumbered IP,<br />

one router appears as a DTE and <strong>the</strong> o<strong>the</strong>r as a DCE. You should recall that<br />

<strong>the</strong> IP address of one of <strong>the</strong> router's IP configured E<strong>the</strong>rnet interfaces is used<br />

<strong>to</strong> exchange IP datagrams across <strong>the</strong> link. Alternatively, if you are using <strong>the</strong><br />

point-<strong>to</strong>-point FR connection for multipro<strong>to</strong>col transport, it is best <strong>to</strong> assign<br />

Layer 3 addresses for all <strong>the</strong> pro<strong>to</strong>cols. Here is an example of a<br />

point-<strong>to</strong>-point interface using AppleTalk and IP and static Layer 3 <strong>to</strong> DCLI<br />

mappings:<br />

12.<br />

13. jupiter(config-if)#ip address 172.16.33.1 255.255.255.252<br />

14. jupiter(config-if)#appletalk cable-range 6678-6678 6678.1

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!