#

# Configuring Frame Relay

Introduction
Configuring nailed bandwidth for Frame Relay
Defining Frame Relay link operations
Configuring a DLCI logical interface
Concentrating incoming calls onto Frame Relay
Configuring the MAX as a Frame Relay switch
Configuring switched Frame Relay connections

Frame Relay (FR) is a form of packet-switching, using smaller packets and less error checking than traditional forms of packet switching. For every FR interface, you must configure a dedicated line. You can obtain administrative information about the status of the FR interface by defining link management frames, specifically assigning a unique Data Link Connection Identifier (DLCI) address. By setting parameters for IP Routing, you can configure a gateway for all incoming FR calls. You can configure the MAX as a FR switch so that the MAX can receive frames on one interface and transmit them onto another interface. You can enable the MAX to support a FR switched connection over ISDN BRI or PRI connections.

You can set all these configurations (except for the last) in either the Connection profiles or the RADIUS profiles.

## Introduction

In the Frame Relay network, every access point connects directly to a switch. Frame Relay virtual circuits (VCs) are bidirectional data paths between two endpoints. An established permanent virtual circuit (PVC) is a connection between two endpoints, which can include a number of hops in between.

Depending on how a device such as the MAX is integrated into a Frame Relay network, it can operate as a Frame Relay terminating unit (Customer Premise Equipment or CPE) or as a Frame Relay switch.

A CPE is the source or destination of data traversing the Frame Relay service. For example, the MAX labeled MAX-02 in Figure 5-1 terminates the data stream to its PPP callers. When it is configured with a User-to-Network (UNI) interface to Frame Relay, the MAX acts as the user side (UNI-DTE) communicating with the network side (UNI-DCE) of a switch.

The network-side device connects the CPE device to a Frame Relay network. For example, the MAX labeled MAX-01 in Figure 5-1 receives Frame Relay encapsulated frames from a CPE and forwards them on to another Frame Relay switch. When it is configured with a UNI-DCE interface to Frame Relay, the MAX acts as the network side (UNI-DCE) communicating with the user side (UNI-DTE) of a Frame Relay device.

Figure 5-1. Frame Relay network

A Frame Relay switch is another kind of network-side device, which switches frames from one interface to another and exchanges status information with its peer switch. For example, the MAX labeled MAX-01 in Figure 5-1 receives frames from its peer switch and switches them to its other Frame Relay interface. When it is configured with a Network-to-Network (NNI) interface to Frame Relay, the MAX acts as a Frame Relay switch. Switch-to-switch communication includes both user side (NNI-DTE) and network side (NNI-DCE) functions.

### Frame Relay link management

Frame Relay link management enables administrators to retrieve information about the status of the Frame Relay interface via special management frames with a unique Data Link Connection Identifier (DLCI) address. (DLCI 0 is the default for link management frames.) Link management frames are used to monitor the interface and provide information about DLCI status.

On a UNI interface to Frame Relay, link management procedures occur in one direction. The UNI-DTE device requests information and the UNI-DCE device provides it.

On an NNI interface, link management procedures are bidirectional. Switches perform both the NNI-DTE and NNI-DCE link management functions, since both sides of the connection request information from their peer switches.

### Using the MAX as a Frame Relay concentrator

As a Frame Relay concentrator, the MAX forwards many lower-speed PPP connections onto one or more high-speed Frame Relay interfaces, as shown in Figure 5-2:

Figure 5-2. Frame Relay concentrator

In this kind of configuration, the decision to forward frames onto the Frame Relay interface can be made through OSI layer 3 (routing), or by Frame Relay Direct.

### Using the MAX as a Frame Relay switch

As a Frame Relay switch, the MAX receives frames on one interface and transmits them on another interface. The decision to forward frames onto the Frame Relay interface is made through the assignment of circuit names. The MAX router software is not involved.

To use the MAX as a switch, you must configure a circuit that pairs two Frame Relay DLCI interfaces. Instead of going to the layer 3 router for a decision on which interface to forward the frames, it relies on the circuit configuration to relay the frames received on one interface to its paired interface. A circuit is defined in two Connection or RADIUS user profiles.

Figure 5-3 shows the MAX operating as a Frame Relay switch:

Figure 5-3. Frame Relay switch

### Components of a Frame Relay configuration

The physical link to another Frame Relay device must be nailed (similar to a dedicated leased line). The administrator allocates nailed bandwidth in a line profile (the profile of a T1, E1, SWAN, or other network line).

The link interface to the Frame Relay device, which is also called a datalink, references specific nailed bandwidth in the MAX and defines the operations and link management functions the MAX performs on the interface. The administrator specifies these settings in a Frame-Relay profile or RADIUS frdlink pseudo-user profile.

The logical interface is a PVC endpoint, which requires a DLCI. DLCIs uniquely identify the logical endpoints of a virtual circuit (a specific end device). Administrators obtain DLCIs from Frame Relay providers and assign them in Connection profiles or RADIUS user profiles.

## Configuring nailed bandwidth for Frame Relay

Each Frame Relay interface in the MAX requires its own nailed bandwidth, which is similar to a dedicated leased line.

Note: If you configure the bandwidth on nailed T1, make sure that the number of channels the MAX uses for the link matches the number of channels used by the device at the other end of the link, and that only one line profile specifies the Nailed-Group number to be used by the Frame Relay datalink.

Following are some examples of relevant parameters, shown with sample settings:

    Net/T1 > Line Config > Line 1 > Ch 2=Nailed

    Net/T1 > Line Config > Line 1 > Ch 2 Prt/Grp=1

    Net/E1 > Line Config > Line 1 > Ch 2=Nailed

    Net/E1 > Line Config > Line 1 > Ch 2 Prt/Grp=1

    Serial WAN > Mod Config > Nailed Grp=1

####

####

     Parameter

     Specifies

     Ch N

     Switched or Nailed channel usage. To configure nailed bandwidth on a channelized T1 or E1 card, set to Nailed-64-Channel (a clear-channel 64K circuit). On unchannelized cards, this parameter does not apply.

     Ch N Prt/Grp
    Nailed Grp

     A number from 1 to 1024, used to identify nailed bandwidth. Frame-Relay profiles or RADIUS frdlink pseudo-user profiles specify this number to use the associated bandwidth.

For more details about configuring T1, see the Hardware Installation Guide for your MAX.

## Defining Frame Relay link operations

A Frame-Relay profile defines datalink operations, including link management functions. The same settings can be specified in a RADIUS frdlink pseudo-user profile.

Note: Link management settings are optional. It is possible to set up a Frame Relay interface and pass data across it without setting these parameters. However, link management parameters provide a mechanism for retrieving information about the status of the interface and its DLCIs.

### Settings in a Frame-Relay profile

Following are the Frame-Relay profile parameters, shown with sample settings:

    Ethernet

          Frame Relay

                Name*=""

                Active=Yes

                Call Type=Nailed

                FR Type=NNI

                Nailed Grp=1

                Data Svc=56KR

                PRI # Type=N/A

                Dial #=N/A

                Bill #=N/A

                Call-by-Call=N/A

                Transit #=N/A

                Link Status Dlci=0

                Link Mgmt=T1.617D

                N391=6

                DTE N392=3

                DTE N393=4

                DCE N392=3

                DCE N393=4

                T391=10

                T392=15

                MRU=1532

### Understanding the Frame Relay parameters

This section provides some background information about the Frame Relay parameters. For detailed information about each parameters, see the MAX Reference Guide.

#### Name and Active

User connections link up with the Frame Relay connection specified in a Frame Relay profile by specifying the profile's name, which is defined by the name profile. The name must be unique and cannot exceed 15 characters.

Set the Active parameter to Yes to make the profile available for use.

#### LinkUp

The LinkUp parameter specifies whether the data link comes up automatically and stays up even when the last DLCI has been removed. If you set this parameter to No, the data link does not come up unless a Connection profile (DLCI) brings it up, and it shuts down after the last DLCI has been removed.

Note: You can start and drop Frame Relay data-link connections with the DO Dial and DO Hangup commands. DO Dial brings up a datalink connection. DO Hangup closes the link and any DLCIs on it. If LinkUp=Yes, DO HANGUP brings the link down, but it automatically restarts. A restart also occurs if a DLCI Connection (DLCI) profile invokes the data link.

#### FR Type

You can set the FR Type parameter to NNI (for an NNI interface to the switch), DCE (for a UNI-DCE interface), or DTE (for a UNI-DTE interface).

#### Call Type, telco options, and Data Svc

Nailed is the default call type for Frame Relay connections. When you set Call Type to Nailed, dial numbers and other telco options are N/A. You can specify Switched if the Frame Relay switch allows dial-in. However, Frame Relay networks currently have no dial-out connection capability. The two types of data service available are 64K and 56K.

#### Link management protocol

The Link Mgmt setting can be None (no link management), T1.617D (for T1.617 Annex D), or Q.933A (for Q.933 Annex A).

#### Frame Relay timers and event counts

Frame Relay timers and event counts function as follows:

- N391-Specifies the interval at which the MAX requests a Full Status Report (from 1 to 255 seconds). Is N/A if FR Type is DCE.

- DCE N392-Specifies the number of errors, during DCE N393 monitored events, that causes the network side to declare the user-side procedures inactive. The value should be less than that of DCE N393 (from 1 to 10). DCE N392 is N/A when FR Type is DTE.

- DCE N393-Specifies the DCE monitored event count (from 1 to 10). It is N/A when FR Type is DTE.

- DTE N392-Specifies the number of errors, during DTE N393 monitored events, that cause the user side to declare the network-side procedures inactive. The value should be less than that of DTE N393 (from 1 to 10). DTE N.392 is N/A when FR Type is DCE.

- DTE N393-Specifies the number of DTE monitored events per testing cycle (from 1 to 10). It is N/A when FR Type is DCE.

- T391-Specifies the Link Integrity Verification polling timer (from 5 to 30 seconds). The value should be less than that of T392. T391 is N/A when FR Type is DCE.

- T392-Specifies the interval for Status Enquiry messages (from 5 to 30 seconds). The MAX records an error message if it does not receive an Status Enquiry message within T392 seconds. This parameter is N/A when FR Type is DTE.

#### MRU (Maximum Receive Units)

The MRU parameter specifies the maximum number of bytes the MAX can receive in a single packet across this link. Usually the default of 1532 is the right setting, unless the far end device requires a lower number.

#### Settings in a RADIUS frdlink profile

An frdlink profile is a pseudo-user profile in which the first line has this format:

    frdlink-name-N Password="ascend", User-Service = Dialout-Framed-User

The name argument is the MAX system name (specified by the Name parameter in the System profile), and N is a number in a sequential series, starting with 1. Make sure there are no missing numbers in the series specified by N. If there is a gap in the sequence of numbers, the MAX stops retrieving the profiles when it encounters the gap in sequence.

The following attributes can be used to define a frdlink pseudo-user profile:

#### Attribute | #### Value
--- | ---
Ascend-FR-Profile-Name (180) | A Frame-Relay profile name (up to 15 characters), to be referenced in user profiles that make use of this datalink.
Ascend-FR-Nailed-Grp (158) | Group number assigned to nailed bandwidth in a line profile, such as a T1 or E1 profile. The default is 1. Make sure the Frame-Relay profile specifies the correct group number. If the channels are on nailed T1, make sure that the number of channels the MAX uses for the link matches the number of channels used by the device at the other end of the link, and that only one T1 profile specifies the Nailed-Group number to be used by the Frame Relay datalink.
Ascend-Call-Type (177) | Type of nailed connection: Nailed (1), Nailed/Mpp (2), or Perm/Switched (3). Nailed is the default.
Ascend-Data-Svc (247) | Type of data service on the nailed link.Typically set to Nailed-64K for a Frame Relay datalink.
Ascend-FR-Link-Mgt (160) | The link management protocol. Settings are Ascend-FR-No-Link-Mgt (0) (link management protocol is disabled), Ascend-FR-T1-617D (1) (Annex D), and Ascend-FR-Q-933A (2)(CCITT Q.933 Annex A). Ascend-FR-No-Link-Mgt is the default. To ensure interoperability with equipment from different vendors, the same version of management protocol must be used at each end of the Frame Relay link.
Ascend-FR-Type (159) | Type of operations performed by the MAX on this interface. Settings are Ascend-FR-DTE (0), Ascend-FR-DCE (1), or Ascend-FR-NNI (2). Ascend-FR-DTE is the default. (For more information, see Examples of a UNI-DTE link interface, Examples of a UNI-DCE link interface, and Examples of an NNI link interface.)
Ascend-FR-N391 (161) | Number of T391 polling cycles between full Status Enquiry messages. The default is 6, which indicates that after 6 status requests spaced Ascend-FR-T391 seconds apart, the UNI-DTE device requests a Full status report. Does not apply when Ascend-FR-Type is Ascend-FR-DCE.
Ascend-FR-DTE-N392 (163) | Number of errors which, if occurring in the number of DTE monitored events specified by Ascend-FR-DTE-N393, causes the user-side to declare the network-side procedures inactive. The value should be less than that of Ascend-FR-DTE-N393l (which can be from 1 to 10). The default value is 3. Does not apply when Ascend-FR-Type is Ascend-FR-DCE.
Ascend-FR-DTE-N393 (165) | DTE monitored event count (from 1 to 10). The default is 4. Does not apply when Ascend-FR-Type is Ascend-FR-DCE.
Ascend-FR-T391 (166) | Link Integrity Verification polling timer. The value should be less than that of Ascend-FR-T392. The default is 10, which indicates that after Ascend-FR-N391 status requests spaced 10 seconds apart, the UNI-DTE device requests a Full status report. Does not apply when Ascend-FR-Type is Ascend-FR-DCE.
Ascend-FR-T392 (167) | Interval in which Status Enquiry messages should be received (from 5 to 30 seconds). The default T392 value is 15. An error is recorded if no Status Enquiry is received within the specified number seconds. Does not apply when Ascend-FR-Type is Ascend-FR-DTE.
Framed-MTU (12) | Maximum number of bytes the MAX can transmit in a single packet across the link interface. Usually the default of 1532 is the right setting. However, the far-end device might require a lower number.
Ascend-FR-DCE-N392 (162) | Number of errors which, if occurring in the number of DCE monitored events specified by Ascend-FR-DCE-N393, causes the network-side to declare the user-side procedures inactive. The value should be less than that of Ascend-FR-DCE-N393 (which can be from 1 to 10). Does not apply when Ascend-FR-Type is Ascend-FR-DTE.
Ascend-FR-DCE-N393 (164) | DCE monitored event count (from 1 to 10). The default is 4. Does not apply when Ascend-FR-Type is Ascend-FR-DTE.
Ascend-FR-Link-Status-Dlci (106) | DLCI to use for LMI link management on the Frame Relay datalink. Valid values are DLCI0 (the default) and DLCI1023.

### Examples of a UNI-DTE link interface

On a UNI-DTE interface, the MAX acts as the user side communicating with the network side DCE switch. It initiates link management functions by sending a Status Enquiry to the UNI-DCE device. Status Enquiries may include queries about the status of PVC segments the DTE knows about, as well as the integrity of the datalink between the UNI-DTE and UNI-DCE interfaces.

The UNI-DTE uses the values of the N391, N392, N393, and T391 parameters in the Frame-Relay profile to define the timing of its Status Enquiries to the DCE and its link integrity parameters. (These correspond to the Ascend-FR-N391, Ascend-FR-DTE-N392, Ascend-FR-DTE-N393, and Ascend-FR-T391 attributes in a RADIUS profile.)

Figure 5-4 shows an example of the MAX with a UNI-DTE interface.

Figure 5-4. Frame Relay DTE interface

The following parameters specify nailed group 11 as the bandwidth for the sample DTE interface. Make sure that the Frame-Relay profile specifies the correct nailed group.

    Ethernet

          Frame Relay

                Active=Yes

                FR Type=DTE

                Nailed Grp=11

                Link Mgmt=Q.933A

With these link management settings, the MAX uses the CCITT Q.933 Annex A link management protocol to communicate with the Frame Relay DCE. It initiates link management functions by sending a Status Enquiry to the DCE every 10 seconds.

On a UNI-DTE interface, the state of a DLCI is determined by the Full status report from the DCE or by an async PVC update. The Full status report from the DCE specifies active and inactive and new DLCIs. If the DCE does not specify a DLCI as active or inactive, the DTE considers it inactive.

Following is a comparable RADIUS profile:

    frdlink-max-1 Password = "ascend", User-Service = Dialout-Framed-User

        Ascend-FR-Profile-Name = "fr-dte",

        Ascend-Call-Type = Nailed,

        Ascend-FR-Type = Ascend-FR-DTE,

        Ascend-FR-Nailed-Grp = 11,

        Ascend-FR-Link-Mgt = Ascend-FR-Q-933A,

        Ascend-Data-Svc = Nailed-64K

### Examples of a UNI-DCE link interface

On a UNI-DCE interface, the MAX acts as the network side communicating with the user side (UN-DTE) of a Frame Relay terminating unit.

The UNI-DCE uses the values of the T392, DCE N392, and DCE N393 parameters in the Frame Relay profile to define the parameters of the Status Enquiries expected from the DTE. (These correspond to the Ascend-FR-T392, Ascend-FR-DCE-N392, and Ascend-FR-DCE-N393 attributes in a RADIUS profile.)

For example, if the MAX expects a Status Enquiry from the DTE every ten seconds, it records an error if it does not receive a Status Enquiry in ten seconds.

Figure 5-5 shows an example of the MAX with a UNI-DCE interface.

Figure 5-5. Frame Relay DCE interface

The following parameters specify nailed group 36 as the bandwidth for the sample DCE interface. Make sure that the Frame-Relay profile specifies the correct nailed group.

    Ethernet

          Frame Relay

                Active=Yes

                FR Type=DCE

                Nailed Grp=36

                Link Mgmt=Q.933A

                T392=15

With these link management settings, the MAX uses the CCITT Q.933 Annex A link management protocol to communicate with the CPE endpoint. It expects a Status Enquiry at intervals less than seven seconds.

On a UNI-DCE interface, if the datalink is up, the DLCI is considered to be up as well. In the DCE Full status response to the DTE, if a PVC segment terminates within the DCE, it is reported as active. If the PVC segment is not terminated, the DCE has to request further information on the Frame Relay network. In that case, it requests information about the DLCI from the next hop switch, and reports back to the DTE when the segment is confirmed to be active or inactive.

Following is a comparable RADIUS profile:

    frdlink-max-2 Password = "ascend", User-Service = Dialout-Framed-User

        Ascend-FR-Profile-Name = "fr-dce",

        Ascend-Call-Type = Nailed,

        Ascend-FR-Type = Ascend-FR-DCE,

        Ascend-FR-Nailed-Grp = 36,

        Ascend-FR-Link-Mgt = Ascend-FR-Q-933A,

        Ascend-Data-Svc = Nailed-64K,

        Ascend-FR-T392 = 15

### Examples of an NNI link interface

An NNI interface implements procedures used by Frame Relay switches to communicate status between them. The MAX uses these procedures to inform its peer switch about the status of PVC segments from its side of the Frame Relay network, as well as the integrity of the datalink between them. The procedure is bidirectional. The switches act as both the user side (DTE) and network side(DCE) in that they both send Status Enquiries and respond to them.

Because NNI is bidirectional, all of the link management values defined in the Frame-Relay profile are used. The values of the N391, N392, N393, and T391 parameters define the user side of the NNI. These values define the timing of the status enquiries the MAX MAX sends to its peer switch and the boundary conditions that define link integrity. The values of the T392l, DCE N392, and DCE N393 parameters are used by the network side of the NNI to define the parameters of the Status Enquiries it expects from the its peer switch.

Figure 5-6 shows a MAX with an NNI interface:

Figure 5-6. Frame Relay NNI interface

To operate as a switch, the MAX requires a hard-coded circuit configuration in two Connection profiles. It relies on the circuit configuration to relay the frames received on one of the circuit endpoints to the other circuit endpoint. For details about circuit configuration, see Configuring the MAX as a Frame Relay switch.

Note: The two Frame Relay endpoints that make up the circuit do not require NNI interfaces.

The following parameters specify the nailed group 52 as the bandwidth for the NNI interface to Switch-3 (Figure 5-6). Make sure that the Frame-Relay profile specifies the correct nailed group.

    Ethernet

          Frame Relay

                Active=Yes

                FR Type=NNI

                Nailed Grp=52

                Link Mgmt=T1.617D

                N391=6

                T391=10

                T392=15

With these link management settings, the MAX uses the ANSI Annex D link management protocol to communicate with Switch-3. It sends a Status Enquiry for Link Integrity Verification to Switch-3 every 10 seconds, and requests a Full status report every sixth enquiry (every 60 seconds). It also sends a Full Status report in response to requests from the other switch. If it does not receive a Status Enquiry within a 15-second interval (T392), it records an error.

Following is a comparable RADIUS profile:

    frdlink-max-3 Password = "ascend", User-Service = Dialout-Framed-User

        Ascend-FR-Profile-Name = "switch-3",

        Ascend-Call-Type = Nailed,

        Ascend-FR-Type = Ascend-FR-NNI,

        Ascend-FR-Nailed-Grp = 52,

        Ascend-FR-Link-Mgt = Ascend-FR-T1-617D,

        Ascend-Data-Svc = Nailed-64K,

        Ascend-FR-N391 = 6,

        Ascend-FR-T391 = 10,

        Ascend-FR-T392 = 15

## Configuring a DLCI logical interface

A Connection profile defines a DLCI interface. The same settings can be specified in a RADIUS permconn pseudo-user profile.

### Overview of DLCI interface settings

Administrators configure a Connection or RADIUS permconn profile that specifies a connection to a far end device across Frame Relay. The first hop of the connection is known by the DLCI assigned in the profile.

A DLCI is an integer between 16 and 991 that uniquely identifies a specific endpoint in the Frame Relay network. The Frame Relay administrator must provide a valid DLCI for each logical interface to a Frame Relay network.

#### Settings in a Connection profile

All connections that use Frame Relay must specify the name of a configured Frame Relay profile that defines the data link between the MAX and the Frame Relay network. Forwarded or routed connections over the Frame Relay link use the following sets of parameters (shown with sample settings):

    Ethernet
          Answer
                Encaps...
                      PPP=Yes
                      FR=Yes

                PPP Options...
                      Route IP=Yes

For gateway connections:

    Ethernet
          Connections
                any Connection profile
                      Encaps=FR
                      Encaps options...
                            FR Prof=pacbell
                            DLCI=16
                            Circuit=N/A

                      Route IP=Yes

                      Ip options...
                      LAN Adrs=10.2.3.4/24

For Frame Relay circuits:

    Ethernet
          Connections
                any Connection profile
                      Encaps=FR_CIR
                      Encaps options...
                            FR Prof=pacbell
                            DLCI=16
                            Circuit=circuit-1

For FR Direct connections:

    Ethernet
          Connections
                any Connection profile
                      Encaps=PPP
                      Route IP=Yes
                      Ip options...
                            LAN Adrs=10.2.3.4/24

                      Session options...
                            FR Direct=Yes
                            FR Prof=pacbell
                            DLCI=16

#### Understanding the Frame Relay connection parameters

This section provides some background information about the Frame Relay connection parameters. For detailed information about each parameter, see the MAX Reference Guide.

##### Gateway connections (Encaps=FR)

Gateway connections require FR encapsulation, a Frame Relay profile name, and a DLCI. Your Frame Relay provider tells you the DLCI to assign to each connection.

A Connection profile that specifies Frame Relay encapsulation must include a DLCI to identify the first hop of a permanent virtual circuit (PVC). The MAX does not allow you to enter duplicate DLCIs, except when they are carried by separate physical links specified in different Frame Relay profiles.

##### Frame Relay circuits (Encaps=FR_CIR)

A circuit is a PVC segment configured in two Connection profiles. Data coming in on the DLCI configured in one Connection profile is switched to the DLCI configured in the other. Data gets dropped if the circuit has only one DLCI. If more than two Connection profiles specify the same circuit name, the MAX uses only two DLCIs.

In a circuit, both Connection profiles must specify FR_CIR encapsulation and the same circuit name. Each profile must specify a unique DLCI. The MAX does not allow you to enter duplicate DLCIs, except when separate physical links specified in different Frame Relay profiles carry duplicate DLCIs.

##### FR Direct connections (FR Direct=Yes)

In an FR Direct connection, the MAX simply attaches a Frame Relay PVC to multiple Connection profiles. It does so in the Session Options subprofile, by enabling FR Direct, specifying a Frame Relay profile, and setting a DLCI for the PVC endpoint in the FR DLCI parameter. Any packet coming into the MAX on these connections gets switched out on the DLCI. In this mode, the MAX allows multiple Connection profiles to specify the same PVC (the same DLCI).

FR Direct is an unusual mode, in that the MAX ignores the destination of the packets. It assumes that some device at the far end of the PVC makes the routing decisions. The Connection profile, however, must use IP routing to enable the MAX to route data back to the client.

#### Settings in a RADIUS profile

A permconn profile is a pseudo-user profile in which the first line has this format:

    permconn-name-N Password="ascend", User-Service = Dialout-Framed-User

The name argument is the MAX system name (specified by the Name parameter in the System profile), and N is a number in a sequential series, starting with 1. Make sure there are no missing numbers in the series specified by N. If there is a gap in the sequence of numbers, the MAX stops retrieving the profiles when it encounters the gap in sequence.

The following attributes can be used to define a permconn pseudo-user profile that uses Frame Relay:

#### Attribute | #### Value
--- | ---
User-Name (1) | Name of the far end Frame Relay device.
Framed-Protocol (7) | The encapsulation protocol. Must be set to FR (261).
Ascend-FR-Profile-Name (180) | Name of the Frame-Relay profile that defines the data link.
Ascend-FR-DLCI (179) | A DLCI for this PVC endpoint.The DLCI must be obtained from a Frame Relay provider. The MAX does not allow you to enter duplicate DLCIs, except when they are carried by separate physical links specified in different Frame-Relay profiles.
Ascend-Backup (176) | Name of a backup Connection profile to the next hop (optional). See Examples of backup interfaces for nailed Frame Relay links.

### Examples of a DLCI interface configuration

In the following example, the MAX has a connection to a Frame Relay switch that also supports IP routing, as shown in Figure 5-7:

Figure 5-7. Frame Relay PVC

The following set of parameters configures the Connection profile, assigning DLCI 100:

    Ethernet

          Connections

                any Connection profile

                      Active=Yes

                      Encaps=FR

                      IP options

                            LAN Adrs=10.11.12.3/24

                      Encaps options

                            FR Prof=fr-dce

                            DLCI=100

                      Telco options

                            Call Type=Nailed

Following is a comparable RADIUS profile:

    permconn-max-1 Password = "ascend", User-Service = Dialout-Framed-User

        User-Name = "max-switch",

        Framed-Protocol = FR,

        Framed-Address = 10.11.12.3,

        Framed-Netmask = 255.255.255.0,

        Ascend-Route-IP = Route-IP-Yes,

        Ascend-FR-DLCI = 100,

        Ascend-FR-Profile-Name = "fr-dce"

Note: When IP routing is enabled, the MAX creates a route for this destination. Administrators can choose to add static routes to other subnets or to enable RIP updates to or from the router across Frame Relay. The usual considerations for IP routing connections apply (see Chapter 7, Configuring IP Routing).

### Examples of backup interfaces for nailed Frame Relay links

On UNI-DTE and NNI interfaces, the MAX issues Status Enquiries that check the state of the other end of PVC segments on the interface. If a DLCI becomes inactive, and the profile configuring its nailed interface specifies a backup connection, the MAX uses the backup connection to provide an alternate route to the other end.

In the sample profiles that follow, the primary interface is a Frame Relay DLCI interface defined in a profile named `fp7`, and the backup interface is another DLCI interface defined in a profile named `pvc`. In this example, the remote IP address of the primary and the backup connection are different.

The following set of parameters defines the primary and backup interfaces in local Connection profiles:

    Ethernet

          Connections

                fp7

                      Name=fp7

                      Active=Yes

                      Encaps=FR

                      IP options

                            LAN Adrs=10.168.7.9/24

                      Encaps options

                            FR Prof=frt2-7

                            DLCI=18

                      Telco options

                            Call Type=Nailed

                      Session options

                            BackUp=pvc

    Ethernet

          Connections

                pvc

                      Name=pvc

                      Active=Yes

                      Encaps=FR

                      IP options

                            LAN Adrs=10.168.7.11/24

                      Encaps options

                            FR Prof=frt1-7

                            DLCI=16

                      Telco options

                            Call Type=Nailed

Following are comparable RADIUS profiles:

    permconn-max1-1 Password = "ascend", User-Service = Dialout-Framed-
    User

       User-Name = "fp7",

       Framed-Protocol = FR,

       Framed-Address = 10.168.7.9,

       Framed-Netmask = 255.255.255.0,

       Ascend-Route-IP = Route-IP-Yes,

       Ascend-Backup = "pvc",

       Ascend-Metric = 7,

       Ascend-FR-DLCI = 18,

       Ascend-FR-Profile-Name = "radius-frt2-7",

       Framed-MTU = 1524,

       Ascend-Call-Type = Nailed

    permconn-max1-2 Password = "ascend", User-Service = Dialout-Framed-
    User

       User-Name = "pvc",

       Framed-Protocol = FR,

       Framed-Address = 10.168.7.11,

       Framed-Netmask = 255.255.255.0,

       Ascend-Route-IP = Route-IP-Yes,

       Ascend-Metric = 7,

       Ascend-FR-DLCI = 16,

       Ascend-FR-Profile-Name = "radius-frt1-7",

       Framed-MTU = 1524,

       Ascend-Call-Type = Nailed

When the MAX brings up the two Frame Relay PVC, the routing table includes entries such as this:

    ...

    10.168.7.0/24    10.168.7.9     wan33     rGT     60    1     0    89

    10.168.7.0/24    10.168.7.9     wan33     *SG    120    7     0   198

    10.168.7.9/32    10.168.7.9     wan33     rT      60    1     0    89

    10.168.7.9/32    10.168.7.9     wan33     *      120    7         198

    10.168.7.11/32   10.168.7.11    wan32     rT      60    1     0    51

    10.168.7.11/32   10.168.7.11    wan33     *S     120    1          89

    ...

At this point, both nailed connections are up, and the output of the Ifmgr command contains entries such as the following:

    bif slot sif u m p ifname   host-name remote-addr      local-addr

    --------------------------------------------------------------------

    032 1:03 001 *   p wan32    pvc       10.168.7.11/32   11.168.6.234/32

    033 1:03 002 *   p wan33    fp7       10.168.7.9/32    11.168.6.234/32

If the primary PVC becomes unavailable, the routing table does not change, but the entries in the output of the Ifmgr command look like the following output:

    bif slot sif u m p ifname  host-name  remote-addr      local-addr

    --------------------------------------------------------------------

    032 1:03 001 *   p wan32    pvc       10.168.7.11/32   11.168.6.234/32

    033 1:17 000 +   p wan33    fp7       10.168.7.9/32    11.168.6.234/32

Notice that `fp7` is shown with a plus-sign (+) to show that it is in the Backup Active state (that it is backed up by another connection). When the primary PVC comes up again, the data flow is directed to that interface again. At that point, the Ifmgr command output again shows both interfaces as up.

## Concentrating incoming calls onto Frame Relay

A common way to concentrate incoming connections onto a Frame Relay link is by making use of OSI layer 3 (IP routing). For this purpose, the MAX requires ordinary profiles for the callers, and a DLCI logical interface that specifies a destination IP router. When clients dial in to reach the destination router, the MAX consults its routing table to forward the packets onto Frame Relay. In this type of configuration, the MAX acts as a Frame Relay gateway.

For incoming PPP connections, Frame Relay Direct is another way to concentrate the calls onto a Frame Relay link. Frame Relay Direct aggregates multiple PPP connections and forwards them as a combined data stream solely on the basis of the FR-Direct specifications. The assumption is that an upstream device will examine the packets and route them appropriately.

Note: A Frame Relay Direct connection is not a full-duplex tunnel between a PPP dial-in and a far-end device. Although the MAX does not use the router to forward packets onto the Frame Relay link, it must use the router to send packets received across Frame Relay back to the appropriate PPP caller. For this reason, Frame Relay Direct connections must enable IP routing.

### Setting up a Frame Relay gateway

To act as a Frame Relay gateway, the Frame Relay DLCI profile must specify a destination router. Incoming connections are routed in the usual way, and all of the usual options apply. Administrators can choose to create static routes, enable or disable RIP, and so forth. For details, see Chapter 7, Configuring IP Routing.

For background information about specifying a DLCI interface, see Configuring a DLCI logical interface.

#### Routing parameters in the DLCI profile

In addition to the Frame Relay settings described in Overview of DLCI interface settings, the following Connection parameters are relevant to a gateway DLCI profile:

####

####

    Ethernet

          Connections

                any Connection profile

                      Route IP=Yes

                IP options

                      LAN Adrs=0.0.0.0/0

     Parameter

     Specifies

     Route IP

     Enables/disables IP routing for this connection. It is enabled by default, and must be enabled for a Frame Relay gateway.

     LAN Adrs

     Destination IP address, which lies at the end of a PVC whose first hop is known by the specified DLCI.

#### Routing parameters in RADIUS

In addition to the attributes described in Overview of DLCI interface settings, the following attribute-value pairs must be specified in the permconn profile of a Frame Relay gateway:

#### Attribute | #### Value
--- | ---
Ascend-Route-IP (228) | Enables/disables IP routing for this connection. (IP is enabled by default. If this attribute is present, it must be set to Route-IP-Yes for Frame Relay gateway connections.)
Framed-Address (8) | Destination IP address, which lies at the end of a PVC whose first hop is known by the specified DLCI.
Framed-Netmask (9) | A subnet mask for Framed-Address.

#### Examples of a gateway configuration

In the following example, the MAX acts as a gateway between a client that dials in with the address 10.1.2.3/29, and a remote router that is reachable across Frame Relay, as shown in Figure 5-8:

Figure 5-8. Frame Relay gateway

The following set of parameters configures an MP+ Connection profile for the dial-in client in Figure 5-8:

    Ethernet

          Connections

                mpp-client

                      Name=mpp-client

                      Active=Yes

                      Encaps=MPP

                      Encaps options

                            Recv PW=clientpw

                      IP options

                            LAN Adrs=10.1.2.3/29

Following is a comparable RADIUS profile:

    mpp-client Password = "clientpw", User-Service = Dialout-Framed-User

        Framed-Protocol = MPP,

        Framed-Address = 10.10.1.3,

        Framed-Netmask = 255.255.255.248

The next set of parameters configures a DLCI Connection profile to the CPE router:

    Ethernet

          Connections

                cpe-router

                      Name=cpe-router

                      Active=Yes

                      Encaps=FR

                      IP options

                            LAN Adrs=10.9.8.7/24

                      Encaps options

                            FR Prof=fr-dte

                            DLCI=55

Following is a comparable RADIUS profile:

    permconn-max-2 Password = "ascend", User-Service = Dialout-Framed-User

        User-Name = "cpe-router",

        Framed-Protocol = FR,

        Framed-Address = 10.9.8.7,

        Framed-Netmask = 255.255.255.0,

        Ascend-Route-IP = Route-IP-Yes,

        Ascend-FR-DLCI = 55,

        Ascend-FR-Profile-Name = "fr-dte"

Note: The MAX creates a route for this destination and uses it to forward packets from PPP clients. Administrators can choose to add static routes to other subnets or to enable dynamic routing updates to or from the router across Frame Relay. The usual considerations for IP routing connections apply (see Configuring IP Routing).

### Configuring Frame Relay Direct

When a PPP Connection profile specifies FR-Direct, the MAX simply forwards the data stream out on a specified DLCI interface. It leaves the task of routing the packets to an upstream device.

For background information about specifying a DLCI interface, see Configuring a DLCI logical interface.

#### Settings in a Connection profile

Following are the relevant FR-Direct parameters, shown with sample settings:

    Ethernet

          Connections

                any Connection profile

                      Active=Yes

                      Encaps=PPP

                      Route IP=Yes

                      Encaps options

                            Recv PW=clientpw

                      IP options

                            LAN Adrs=10.111.112.113/24

                      Session options

                            FR Direct=Yes

                            FR Prof=

                            FR Dlci=16

#### Parameter | #### Specifies
--- | ---
Encaps | Specifies the supported encapsulation protocol. Must be set to PPP, MP, or MPP for Frame Relay Direct connections.
FR Direct | Enables/disables FR-Direct mode for this connection.
FR Prof | Specifies the name of the Frame Relay profile that defines the datalink.
FR Dlci | DLCI assigned in a Connection profile to a next hop on the specified interface. Multiple FR-Direct Connection profiles can refer to the same DLCI in this setting.
Route IP | Enables/disables IP routing for this connection. Must be enabled for the MAX to send data back to the appropriate PPP caller.
LAN Adrs | Specifies the PPP caller's IP address. As the MAX receives return packets for many Frame Relay Direct connections on the same DLCI, it uses this address to determine which PPP caller should receive the return packets.

#### Settings in a RADIUS profile

Following are the relevant RADIUS attributes for FR-Direct connections:

#### Attribute | #### Value
--- | ---
Framed-Protocol (7) | The encapsulation protocol. Must be set to PPP (1), MP (262), or MPP (256) for FR-Direct connections.
Ascend-FR-Direct (219) | Enables/disables FR-Direct mode for this connection. FR-Direct-No (0) is the default. Set to FR-Direct-Yes (1) for FR-Direct connections.
Ascend-FR-Direct-Profile (220) | Name of the Frame-Relay profile that defines the datalink.
Ascend-FR-Direct- DLCI (221) | DLCI assigned in a Connection profile to a next hop on the specified interface. Multiple FR-Direct Connection profiles can refer to the same DLCI in this setting.
Ascend-Route-IP (228) | Enables/disables IP routing for this connection. (IP is enabled by default. If this attribute is present, it must be set to Route-IP-Yes to enable the MAX to send data back to the appropriate PPP caller.
Framed-Address (8) | PPP caller's IP address. As the MAX receives return packets for many Frame Relay Direct connections on the same DLCI, it uses this address to determine which PPP caller should receive the return packets.
Framed-Netmask (9) | A subnet mask for Framed-Address.

#### Examples of FR-Direct connections

In the following example, the MAX forwards the data stream from two PPP dial-in hosts across Frame Relay on the same DLCI interface, as shown in Figure 5-9:

Figure 5-9. Frame Relay Direct

The following parameters specify the DLCI interface to frswitch-1 in Figure 5-9:

    Ethernet

          Connections

                frswitch-1

                      Name=frswitch-1

                      Active=Yes

                      Encaps=FR

                      IP options

                            LAN Adrs=10.10.10.10/24

                      Encaps options

                            FR Prof=fr-dte

                            DLCI=72

Following is a comparable RADIUS profile:

    permconn-max-3 Password = "ascend", User-Service = Dialout-Framed-User

        User-Name = "frswitch-1",

        Framed-Protocol = FR,

        Framed-Address = 10.10.10.10,

        Framed-Netmask = 255.255.255.0,

        Ascend-Route-IP = Route-IP-Yes,

        Ascend-FR-DLCI = 72,

        Ascend-FR-Profile-Name = "fr-dte"

The following set of parameters configures FR Direct Connection profiles for the incoming calls:

    Ethernet

          Connections

                caller-1

                      Name=caller-1

                      Active=Yes

                      Encaps=PPP

                      Encaps options

                            Recv PW=caller1*3

                      IP options

                            LAN Adrs=10.5.6.7/32

                      Session options

                            FR Direct=Yes

                            FR Prof=fr-dte

                            FR Dlci=72

    Ethernet

          Connections

                caller-2

                      Name=caller-2

                      Active=Yes

                      Encaps=PPP

                      Route IP=Yes

                      Encaps options

                            Recv PW=caller2!!8

                      IP options

                            LAN Adrs=10.5.6.7/32

                      Session options

                            FR Direct=Yes

                            FR Prof=fr-dte

                            FR Dlci=72

Following are comparable RADIUS profiles:

    caller-1 Password = "caller1*3", User-Service = Framed-User

        Framed-Protocol = PPP,

        Framed-Address = 10.5.6.7,

        Framed-Netmask = 255.255.255.255

        Ascend-FR-Direct = FR-Direct-Yes,

        Ascend-FR-Direct-Profile = "fr-dte",

        Ascend-FR-Direct-DLCI = 72

    caller-2 Password = "caller2!!8", User-Service = Framed-User

        Framed-Protocol = PPP,

        Framed-Address = 10.7.8.9,

        Framed-Netmask = 255.255.255.255

        Ascend-FR-Direct = FR-Direct-Yes,

        Ascend-FR-Direct-Profile = "fr-dte",

        Ascend-FR-Direct-DLCI = 72

## Configuring the MAX as a Frame Relay switch

As a Frame Relay switch, the MAX receives frames on one DLCI interface and transmits them on another one. The decision to forward frames is made on the basis of circuit name assignments.

To use the MAX as a switch, you must configure a circuit that pairs two DLCI interfaces. Instead of going to the layer 3 router for a decision on which interface to forward the frames, it relies on the circuit name to relay the frames to the paired interface. A circuit is defined in two Connection profiles, one for each endpoint of the circuit.

Note: When it is operating as a switch, the MAX relays all frames received on one endpoint of the circuit to the other endpoint of the circuit. It does not examine the packets at OSI layer 3.

### Overview of circuit-switching options

With a Frame Relay circuit configuration, the MAX can operate as a switch on UNI-DCE interfaces, NNI interfaces, or a combination of the two. NNI is not required.

Routing parameters or attributes should be disabled for switched connections.

Note: Make sure that the Enabled parameter is set to Yes in the Answer-Defaults FR-Answer subprofile.

#### Settings in a Connection profile

Following are the relevant circuit parameters, shown with sample settings:

####

####

    Ethernet

          Connections

                caller-1

                      Name=caller-1

                      Active=Yes

                      Encaps=FR-Cir

                      Encaps options

                            FR Prof=max

                            DLCI=100

                            FR Circuit=frcir1

     Parameter

     Specifies

     Encaps

     Encapsulation protocol. Both endpoints of the circuit must specify Frame-Relay-Circuit encapsulation.

     FR Prof

     Name of the Frame-Relay profile that defines the datalink.

     DLCI

     A DLCI for this PVC endpoint.The DLCI must be obtained from a Frame Relay provider. The MAX does not allow you to enter duplicate DLCIs, except when they are carried by separate physical links specified in different Frame-Relay profiles.

     FR Circuit

     Circuit name (up to 16 characters). The other endpoint must specify the same circuit name. If only one profile specifies a circuit name, data received on the specified DLCI is dropped. If more than two profiles specify the same circuit name, only two of the profiles will be used to form a circuit.

#### Settings in a RADIUS profile

Following are the RADIUS attributes for configuring a Frame Relay circuit:

#### Attribute | #### Value
--- | ---
Framed-Protocol (7) | Encapsulation protocol. Both endpoints of a circuit must specify FR-CIR (263) encapsulation.
Ascend-FR-Profile-Name (180) | Name of the Frame-Relay profile that defines the datalink.
Ascend-FR-DLCI (179) | A DLCI for this PVC endpoint. The MAX does not allow you to enter duplicate DLCIs, except when they are carried by separate physical links specified in different Frame-Relay profiles.
Ascend-FR-Circuit-Name (156) | Circuit name (up to 16 characters). The other endpoint must specify the same circuit name. If only one profile specifies a circuit name, data received on the specified DLCI is dropped. If more than two profiles specify the same circuit name, only two of the profiles will be used to form a circuit.

### Examples of a circuit between UNI interfaces

Figure 5-10 shows a circuit configuration using UNI-DCE interfaces in the MAX:

Figure 5-10. Frame Relay circuit with UNI interfaces

#### Using local profiles

The following parameters on the MAX define the datalinks to the MAX and to the Pipeline 130 (P130-East):

    Ethernet

          Frame Relay

                max

                      Name=max

                      Active=Yes

                      FR Type=DCE

                      Nailed Grp=111

    Ethernet

          Frame Relay

                p130east

                      Name=p130east

                      Active=Yes

                      FR Type=DCE

                      Nailed Grp=222

The next set of parameters specifies the circuit between the two Frame Relay interfaces:

    Ethernet

          Connections

                max6

                      Name=max6

                      Active=Yes

                      Encaps=FR-Cir

                      Route IP=No

                      Encaps options

                            FR Prof=max

                            DLCI=100

                            FR Circuit=frcir1

    Ethernet

          Connections

                p130

                      Name=p130

                      Active=Yes

                      Encaps=FR-Cir

                      Encaps options

                            FR Prof=p130east

                            DLCI=200

                            FR Circuit=frcir1

#### Using RADIUS profiles

The following RADIUS frdlink pseudo-user profiles define the datalinks to the MAX and to the Pipeline 130 (P130-East):

    frdlink-max-21 Password = "ascend", User-Service = Dialout-Framed-User

        Ascend-FR-Profile-Name = "max",

        Ascend-Call-Type = Nailed,

        Ascend-FR-Type = Ascend-FR-DCE,

        Ascend-FR-Nailed-Grp = 111

    frdlink-max-22 Password = "ascend", User-Service = Dialout-Framed-User

        Ascend-FR-Profile-Name = "p130east",

        Ascend-Call-Type = Nailed,

        Ascend-FR-Type = Ascend-FR-DCE,

        Ascend-FR-Nailed-Grp = 222

The next set of profiles specifies the circuit between the two Frame Relay interfaces:

    permconn-max-10 Password = "ascend" , User-Service = Dialout-Framed-
    User

        User-Name = "max6",

        Framed-Protocol = FR-CIR,

        Ascend-Route-IP = Route-IP-No,

        Ascend-FR-DLCI = 100,

        Ascend-FR-Profile-Name = "max",

        Ascend-FR-Circuit-Name = "fr-cir1"

    permconn-max-11 Password = "ascend", User-Service = Dialout-Framed-
    User

        User-Name = "p130",

        Framed-Protocol = FR-CIR,

        Ascend-Route-IP = Route-IP-No,

        Ascend-FR-DLCI = 200,

        Ascend-FR-Profile-Name = "p130east",

        Ascend-FR-Circuit-Name = "fr-cir1"

### Examples of a circuit between NNI interfaces

Figure 5-11 shows a circuit configuration that uses NNI interfaces:

Figure 5-11. Frame Relay circuit with NNI interfaces

#### Using local profiles

The following parameters on the MAX define the datalinks to the two switches labeled FR-Asnd-A and FR-Asnd-B:

    Ethernet

          Frame Relay

                fr-asnd-a

                      Name=fr-asnd-a

                      Active=Yes

                      FR Type=NNI

                      Nailed Grp=333

    Ethernet

          Frame Relay

                fr-asnd-b

                      Name=fr-asnd-b

                      Active=Yes

                      FR Type=NNI

                      Nailed Grp=444

The next set of parameters specifies the circuit between the two Frame Relay interfaces:

    Ethernet

          Connections

                asnd-a

                      Name=asnd-a

                      Active=Yes

                      Encaps=FR-Cir

                      Route IP=No

                      Encaps options

                            FR Prof=fr-asnd-a

                            DLCI=100

                            FR Circuit=pvc-pipe

    Ethernet

          Connections

                asnd-b

                      Name=asnd-b

                      Active=Yes

                      Encaps=FR-Cir

                      Route IP=No

                      Encaps options

                            FR Prof=fr-asnd-b

                            DLCI=200

                            FR Circuit=pvc-pipe

#### Using RADIUS profiles

The following frdlink pseudo-user profiles define the datalinks to the two switches labeled FR-Asnd-A and FR-Asnd-B:

    frdlink-max-23 Password = "ascend", User-Service = Dialout-Framed-User

        Ascend-FR-Profile-Name = "fr-asnd-a",

        Ascend-Call-Type = Nailed,

        Ascend-FR-Type = Ascend-FR-NNI,

        Ascend-FR-Nailed-Grp = 333

    frdlink-max-24 Password = "ascend", User-Service = Dialout-Framed-User

        Ascend-FR-Profile-Name = "fr-asnd-b",

        Ascend-Call-Type = Nailed,

        Ascend-FR-Type = Ascend-FR-NNI,

        Ascend-FR-Nailed-Grp = 444

The next set of profiles specifies the circuit between the two Frame Relay interfaces:

    permconn-max-12 Password = "ascend", User-Service = Dialout-Framed-
    User

        User-Name = "asnd-a",

        Framed-Protocol = FR-CIR,

        Ascend-Route-IP = Route-IP-No,

        Ascend-FR-DLCI = 100,

        Ascend-FR-Profile-Name = "fr-asnd-a",

        Ascend-FR-Circuit-Name = "pvc-pipe"

    permconn-max-13 Password = "ascend", User-Service = Dialout-Framed-
    User

        User-Name = "asnd-b",

        Framed-Protocol = FR-CIR,

        Ascend-Route-IP = Route-IP-No,

        Ascend-FR-DLCI = 200,

        Ascend-FR-Profile-Name = "fr-asnd-b",

        Ascend-FR-Circuit-Name = "pvc-pipe"

### Examples of circuits that use UNI and NNI interfaces

Figure 5-12 shows circuit configurations that use one UNI-DCE and one NNI interface:

Figure 5-12. Frame Relay circuit with UNI and NNI interface

#### Using local profiles

The following parameters on MAX-42 define the datalinks to the MAX and MAX-39:

    Ethernet

          Frame Relay

                dce-max

                      Name=dce-max

                      Active=Yes

                      FR Type=DCE

                      Nailed Grp=555

    Ethernet

          Frame Relay

                nni-39

                      Name=nni-39

                      Active=Yes

                      FR Type=NNI

                      Nailed Grp=999

The next set of parameters on MAX-42 specifies the circuit between its two Frame Relay interfaces:

    Ethernet

          Connections

                max

                      Name=max

                      Active=Yes

                      Encaps=FR-Cir

                      Route IP=No

                      Encaps options

                            FR Prof=dce-max

                            DLCI=100

                            FR Circuit=cir-42

    Ethernet

          Connections

                max39

                      Name=max39

                      Active=Yes

                      Encaps=FR-Cir

                      Route IP=No

                      Encaps options

                            FR Prof=nni-39

                            DLCI=200

                            FR Circuit=cir-42

The following parameters on MAX-39 define the datalinks to MAX-42 and to the Pipeline 130:

    Ethernet

          Frame Relay

                nni-42

                      Name=nni-42

                      Active=Yes

                      FR Type=NNI

                      Nailed Grp=777

    Ethernet

          Frame Relay

                dce-p130

                      Name=dce-p130

                      Active=Yes

                      FR Type=dce

                      Nailed Grp=888

The next set of parameters on MAX-39 specifies the circuit between its two Frame Relay interfaces:

    Ethernet

          Connections

                max42

                      Name=max42

                      Active=Yes

                      Encaps=FR-Cir

                      Route IP=No

                      Encaps options

                            FR Prof=nni-42

                            DLCI=200

                            FR Circuit=cir-39

    Ethernet

          Connections

                max39

                      Name=max39

                      Active=Yes

                      Encaps=FR-Cir

                      Route IP=No

                      Encaps options

                            FR Prof=dce-p130

                            DLCI=300

                            FR Circuit=cir-39

#### Using RADIUS profiles

The following profiles define the datalinks from MAX-42 to the MAX and MAX-39:

    frdlink-max-25 Password = "ascend", User-Service = Dialout-Framed-User

        Ascend-FR-Profile-Name = "dce-max",

        Ascend-Call-Type = Nailed,

        Ascend-FR-Type = Ascend-FR-DCE,

        Ascend-FR-Nailed-Grp = 555

    frdlink-max-26 Password = "ascend", User-Service = Dialout-Framed-User

        Ascend-FR-Profile-Name = "nni-39",

        Ascend-Call-Type = Nailed,

        Ascend-FR-Type = Ascend-FR-NNI,

        Ascend-FR-Nailed-Grp = 999

The next set of profiles specifies the circuit on MAX-42:

    permconn-max-14 Password = "ascend", User-Service = Dialout-Framed-
    User

        User-Name = "max"

        Framed-Protocol = FR-CIR,

        Ascend-Route-IP = Route-IP-No,

        Ascend-FR-DLCI = 100,

        Ascend-FR-Profile-Name = "dce-max",

        Ascend-FR-Circuit-Name = "cir-42"

    permconn-max-15 Password = "ascend", User-Service = Dialout-Framed-
    User

        User-Name = "max39",

        Framed-Protocol = FR-CIR,

        Ascend-Route-IP = Route-IP-No,

        Ascend-FR-DLCI = 200,

        Ascend-FR-Profile-Name = "nni-39",

        Ascend-FR-Circuit-Name = "cir-42"

The following profiles define the datalinks from MAX-39 to MAX-42 and the Pipeline 130:

    frdlink-max-27 Password = "ascend", User-Service = Dialout-Framed-User

        Ascend-FR-Profile-Name = "nni-42",

        Ascend-Call-Type = Nailed,

        Ascend-FR-Type = Ascend-FR-NNI,

        Ascend-FR-Nailed-Grp = 777

    frdlink-max-28 Password = "ascend", User-Service = Dialout-Framed-User

        Ascend-FR-Profile-Name = "dce-p130",

        Ascend-Call-Type = Nailed,

        Ascend-FR-Type = Ascend-FR-DCE,

        Ascend-FR-Nailed-Grp = 888

The next set of profiles specifies the circuit on MAX-39:

    permconn-max-16 Password = "ascend", User-Service = Dialout-Framed-
    User

        User-Name = "max42"

        Framed-Protocol = FR-CIR,

        Ascend-Route-IP = Route-IP-No,

        Ascend-FR-DLCI = 200,

        Ascend-FR-Profile-Name = "nni-42",

        Ascend-FR-Circuit-Name = "cir-39"

    permconn-max-17 Password = "ascend", User-Service = Dialout-Framed-
    User

        User-Name = "p130",

        Framed-Protocol = FR-CIR,

        Ascend-Route-IP = Route-IP-No,

        Ascend-FR-DLCI = 300,

        Ascend-FR-Profile-Name = "dce-p130",

        Ascend-FR-Circuit-Name = "cir-39"

## Configuring switched Frame Relay connections

You can enable the MAX to support Frame Relay switched connections over ISDN BRI or PRI connections. A switched Frame Relay connection provides either a 56K or 64K connection, depending on the ISDN network configuration.

### Overview

When a Frame Relay profile and an associated Connection profile are configured for a switched Frame Relay connection, the Connection profile can establish a Frame Relay session either by placing an outgoing call or by matching the CLID or DNIS of an incoming call. Once the session is established, it behaves just like a nailed Frame Relay connection with an access rate of 64K or 56K, depending on the ISDN network configuration. Authentication can be by DNIS and CLID.

Switched Frame Relay connections support the same logical interfaces as do nailed connections: NNI, DTE, and DCE.

Keep the following information in mind:

- Your Frame Relay service provider must allow switched Frame Relay connections.

- A switched Frame Relay connection is a point-to-point connection and supports only one DLCI.

- Verify that the Committed Information Rate of the DLCI(s) using switched connections allow 56K or 64K connections.

### Configuring a switched Frame Relay connection

To set up a switched Frame Relay connection, you must perform the following general steps:

1. Set up a Frame Relay profile as follows:

- Call Type set to Switched

- FR Type set to NNI, DTE, or DCE, depending on the network configuration

- FR Prof set to the name of the Frame Relay encapsulated Connection profile

- Data link information specified as given to you by your service provider

2. Set up a Frame Relay encapsulated Connection profile as follows:

- Encaps set to FR

- Call Type set to Switched

- Dial#, Calling# and Called# specified if you are authenticated with CLID or DNIS

3. Set up the Answer profile as follows:

- FR set to Yes

- Profile Reqd set to Yes

- Id Auth set to Require (for CLID) or set to Called Require (for DNIS), depending on the authentication

#### Configuring a Frame Relay profile

The following example shows how to configure a switched Frame Relay NNI connection, but you configure a switched DCE or DTE connection similarly.

To configure a Frame relay profile for a Frame Relay switched connection, proceed as in the following example:

1. Open Ethernet > Frame Relay> any profile

2. Specify a Name. For example:

   `Station=fr-sw-fr`

3. Set Active to Yes.

4. Set Call Type to Switched.

5. Set FR Type=NNI.

6. Specify the data link information as given to you by your Frame Relay Service provider.

7. Exit and save the Frame Relay profile.

#### Configuring a Connection profile

Next, to configure a Connection profile for a Frame Relay switched connection, proceed as in the following example:

1. Open Ethernet > Connection > any profile

2. Specify a Station Name. For example:

   `Station=fr-sw-conn`

3. Set Active to Yes.

4. Set Encaps to FR.

5. Open the Encaps Options submenu.

6. Specify the name of the Frame Relay profile that uses this Connection profile. For example:

   `FR Prof=fr-sw-fr`

7. Specify the DLCI for this Frame Relay connection. For example:

   `DLCI=165`

8. Open the Telco Options submenu.

9. Set Call Type to Switched.

   You can only set Call Type to Switched if the Frame Relay Profile associated with it also has Call Type set to Switched.

10. If necessary, set AnsOrig to control whether the MAX establishes the Frame Relay connection for incoming or outgoing connections.

11. Exit the Telco Options submenu.

12. If you are authenticating with CLID or DNIS, specify a Dial#, Calling# and Called#.

13. If necessary, open the Session options submenu and set the Idle parameter to the number of seconds inactive sessions remain connected. For example:

    `Idle=120`

14. Exit and save the Connection profile.

#### Configuring the Answer profile

To allow incoming calls to bring up the Frame Relay connection, configure the Answer profile as in the following example:

1. Open Ethernet > Answer.

2. Set Profile Reqd=Yes.

3. If necessary, set the Id Auth parameter as follows:

   - Require (for CLID)

   - Called Require (for DNIS)

4. Open the Encaps Options submenu.

5. Set FR to Yes.

6. Exit and save the Answer profile.

#### Establishing the connection

To bring up the Frame Relay manually, open the Connection profile and press Ctrl-D, then select `1=Dial`.

If you configure an Answer profile, an incoming call with the correct CLID or DNIS brings up the session.

Copyright © 1998, Ascend Communications, Inc. All rights reserved.