Scenario details: Configuration for the iSeries™ system in Minneapolis

Use the prompt display for the Create Network Interface (Frame Relay) (CRTNWIFR) command to create the network interface (NWI) description on the Minneapolis system. The INTERFACE and LINESPEED parameter values must match the network subscription, and you must specify a LMIMODE value when communicating over a frame-relay network. The LMIMODE value must match the network subscription and can be *TE, *ANNEXA, or *NONE. The local management interface (LMI) uses data link connection identifier 0 (DLCI 0) for both *ANNEXA and *TE, but it does not use a DLCI for *NONE.

Use the prompt display for the Create Line Description (Frame Relay) (CRTLINFR) command to create the frame-relay line description on the Minneapolis system. The DLCI that you specify for the line must match the network subscription. Because frame-relay Systems Network Architecture (SNA) direct addressing requires 10 bytes of overhead, a frame size of 1590 is configured for the MAXFRAME parameter. In other words, you need to use a frame size that is at least 10 bytes less than the network subscription. You also need to know the frame size at the other side of the network. For example, if one side is 1600 and the other is 2100, then both sides need to be set to 1600.

Use the prompt display for the Create Controller Description (APPC) (CRTCTLAPPC) command to create the APPC controller description on the Minneapolis system. You must specify LINKTYPE(*FR) for SNA direct connections.

Note: The default values for SSAP and DSAP are both 04. These values must match the values specified for the remote system. If you create more controllers using the same line description (DLCI), you must specify a unique SSAP and DSAP pair. This might require you to configure more SAPs on the frame-relay line description.