Scenario: Bridged connection to an Ethernet network

This scenario involves connecting an IBM® eServer iSeries™ system to an Ethernet local area network (LAN) using a 6611 Network Processor. The 6611 is used as both the frame-relay frame handler and a bridge.

Figure 1 shows the configuration of an iSeries system for frame-relay communications with devices on an Ethernet network.

Figure 1. Bridged configuration to the Ethernet network
Bridged configuration to the Ethernet network

The Ethernet LAN is connected by using a 6611 bridge and transparent bridging. The bridge is connected to the iSeries system by using a T1 link.

As seen in Figure 1, there is no frame-relay network in the connection between the iSeries system and the 6611. In this scenario, the iSeries provides the frame handler (FH), or DCE function, and the 6611 bridge is the terminal equipment (TE). Both SNA APPC/APPN and TCP/IP traffic are possible in this configuration. The TCP/IP configuration for line ETHER6611 is done similarly to the way all Ethernet lines are configured for TCP/IP on the iSeries.

Use the following commands to configure the iSeries connection to the Ethernet network through a 6611 Network Processor.

CRTNWIFR   NWID(FT1) RSRCNAME(LIN231) NRZI(*YES)1 
           INTERFACE(*RS449V36)2 LINESPEED(1536000)2 +
           LMIMODE(*FH)3 +
           TEXT('Network Interface for T1 link to Ethernet Bridge')

CRTLINETH4 LIND(ETHER6611) RSRCNAME(*NWID) NWI(FRT1)
           NWIDLCI(20)5 ADPTADR(020000036759)6 +
           EXCHID(05636759) LINKSPEED(1536000) AUTOCRTCTL(*YES)7 +
           TEXT('DLCI to the 6611 Ethernet LAN')

ADDTCPIFC8 INTNETADR('59.1.2.222') LIND(ETHER6611)

CRTCTLAPPC CTLD(PC5) LINKTYPE(*LAN) SWTLINLST(ETHER6611) +
           RMTNETID(RPC) RMTCPNAME(PC5) ADPTADR(020000043405) +
           TEXT('PC5 on 6611 Ethernet Network')

CRTDEVAPPC DEVD(PC5) RMTLOCNAME(PC5) LCLLOCNAME(SYS320) CTL(PC5) +
           TEXT('PC5 on 6611 Ethernet Network')

CRTCTLAPPC CTLD(PC6) LINKTYPE(*LAN) SWTLINLST(ETHERNET6611) +
           RMTNETID(RPC) RMTCPNAME(PC6) ADPTADR(400000455405) +
           TEXT('PC6 on 6611 Ethernet Network')

CRTDEVAPPC DEVD(PC6) RMTLOCNAME(PC6) LCLLOCNAME(SYS320) CTL(PC6) +
           TEXT('PC6 on 6611 Ethernet Network')
Notes:
  1. You must configure NRZI(*YES) when communicating directly with a 6611 without a frame-relay network, such as on a T1 link. You must also configure the 6611 to use NRZI.
  2. The INTERFACE and LINESPEED parameters must match the characteristics of the T1 line that you use.
  3. The local management interface (LMI) mode is *FH, which means the iSeries acts as the frame handler and the 6611 acts as the terminal equipment (TE). LMI is exchanged on data link connection identifier 0 (DLCI 0).
  4. By creating an Ethernet line (CRTLINETH), you are indicating that the DLCI connects to an Ethernet bridge. The Ethernet bridge carries out RFC 1490 bridging and performs transparent bridging.
  5. The iSeries system communicates with the 6611 bridge on DLCI 20.
    Note: If the 6611 Network Processor passes TCP/IP data from a frame-relay network to a token-ring or Ethernet network, you must ensure that the 6611 does not filter data for service access point (SAP) AA. You must turn off filtering for SAP AA on both the frame-relay port and the token-ring or Ethernet port.
  6. You must generate an adapter address (ADPTADR) for each line description that you configure for bridging over frame relay. The frame-relay adapter does not have a preset address.
  7. Configure the Automatically Create Controller Description (AUTOCRTCTL) command so that any devices that dial in to the iSeries have controller and device descriptions automatically created.
  8. Use the Add TCP/IP Interface (ADDTCPIFC) command to define a new interface to the TCP/IP configuration.

Use this configuration to communicate by using either SNA or TCP/IP data.

Parent topic: Scenarios: Bridged configuration for frame relay