IP Over Frame Relay WAN August 13, 1999 Lucent PortMaster (TM) Models Each of the following Lucent router models are equipped with synchronous ports that can be used as Wide Area Network (WAN) interfaces. The synchronous ports for each unit type are listed below:  PM-2R, W1  PM-2ER, W1  IRX-211, S1  IRX-111, S1  IRX-112, S1,S2  IRX-114, S1,S2,S3,S4  OR-LS, W1  OR-HS, W1  Summary A Frame Relay network represents two or more routers interconnected by a Frame Relay cloud. Each router on the Frame Relay cloud is connected to the Frame Relay network that has a Permanent Virtual Circuit (PVC). The Frame Relay network is connected to a Frame Relay switch that in turn connects to the Frame Relay cloud.  The interface or port used to connect the router to the Frame Relay network is called a Frame Relay interface and each Frame Relay interface must have an IP address.  Each router is a node on the Frame Relay network.  The Frame Relay network has its own IP network number that is normally a class C or a subnet of a class C that is unique from other subnets on the system. Each router Frame Relay interface (port) is assigned an IP address from the Frame Relay network's subnet, thus the netmask for each Frame interface on each router of the Frame Relay network is the same. Data Link Connector Identifier (DLCI) numbers are used to point from the Frame Relay switch located at the telephone company central office, to the PVC of a router(s) on the other side of the Frame cloud. The PortMaster communicates with the switch by polling the switch at a manually configured polling interval. The PortMaster can communicate with the switch using Local Management Interface (LMI) or Annex-d  signaling. If the PortMaster receives 3 LMI packets back from the switch the connection is ESTABLISHED. If  LMI packets are not present  the connection will go DOWN.  When using LMI the switch will respond with a full DLCI list after a few exchanges of LMI packets. The PortMaster can use this information to build a dynamic DLCI list or the DLCI list can be setup statically.   ====ETHERNET===================== 192.168.100.0/24 ===         |         | E0 IP: 192.168.100.100 +-------+--------+ |       E0       | |  Lucent A  | |       W1       | +-------+--------+         | W1 IP: 192.168.1.1         |        [-] CSU/DSU         |         |Frame Relay Cloud WAN 192.168.1.0 255.255.255.0         +----------------------------+         |                            |        [-] CSU/DSU                   | W1 IP: 192.168.1.3         |                    +-------+-------+         | W1 IP: 192.168.1.2 |       W1      | +-------+--------+           |  Lucent C | |       W1       |           |       E0      | |  Lucent B  |           +-------+-------+ |       E0       |                   | 192.168.300.300 +-------+--------+  ===ETHERNET======= 192.168.200.0/24===         | 192.168.200.200         | ====ETHERNET===================== 192.168.200.0/24 === Items To Verify Before Your Start: Verify that  the CSU/DSU is configured for external clock. Verify that you have a V.35 cable to connect the PortMaster synchronous port to the CSU/DSU Verify that your Frame Relay line has been ordered from your local telephone service provider   Configuring IP Over Frame Relay The following is a sample of a port configuration:  For this example: The Frame Relay interface on the router is S1 For this example: The IP address of the Frame Relay on the router is 192.168.1.1 Command> set s1 network hardwire Command> set s1 protocol Frame Command> set s1 mtu 1500 Command> set s1 modem on # If connection to CSU/DSU is lost it will    # cause the PortMaster to retrain # Set the polling interval.  Use LMI or Annex-D type 0 (choose one, not both) Command> set s1 lmi 10 # The Frame switch will be polled once # every 10 seconds with LMI packets OR Command> set s1 annex 10 # The Frame switch will be polled once # every 10 seconds with Annex-d packets Command> set s1 address 192.168.1.1 # This is the local IP address  # for the Frame network Command> set s1 netmask 255.255.255.0 # This is the netmask for the  # Frame network Command> set s1 dlci 100:192.168.1.2 101:192.168.1.3 The above configures a static DLCI list. When using LMI this can be learned dynamically.  NOTE: The static DLCI list can hold about 8 DLCI:IP address pairs. If the Frame Relay network in question has more than 8 sites a sub interface will be required.  NOTE: Using a static DLCI list is recommended when using routers from multiple vendors or if the Frame Relay network configuration in question rarely changes.  NOTE:  Dynamic DLCI lists are required when planning to route both Internet Protocol (IP) and Internet Protocol eXchange ( IPX).  Command> save all Command> reset s1 The configured port will then look similar to the following example: Command> show s1 ------------------- Current Status - Port S1 -----------         Status: CONNECTING          Input: 0                        Abort Errors: 0         Output: 13                         CRC Errors: 0        Pending: 0                      Overrun Errors: 0      TX Errors: 0                        Frame Errors: 0              Active Configuration    Default Configuration              --------------------    ---------------------      Port Type: Netwrk                  Netwrk (Hardwired)     Line Speed: Ext Clock               Ext Clock  Modem Control: on                      on  Local Address: 192.168.1.1 192.168.1.1        Netmask: 255.255.255.0           255.255.255.0      Interface: Unassigned (FRM,Routing (FRM,Routing)            Mtu: 1500                    0   LMI Poll Int: 10 (seconds)      DLCI List: At this point: LMI packets should be being transmitted and received. The status of the WAN port should change to ESTABLISHED. It should now be possible to ping the other side.