Specifications

Issue 1.0, April 2006 Section 364-180-N02

Figure 6-23 Web Tool – WAN connections page

To edit the service, click on the links at the top of the edit page. The links include:

Edit ‘Service’, Edit ‘Frame Relay’, Edit ‘Frame Relay Channel’, Edit ‘Bridge Interface’, and

Edit ‘Spanning Bridge Interface’.

In “Edit Bridge Interface” page, the option fields include:

Ether Filter Type: The value can be All, Ip, or Pppoe.

Enabled: true or false.

In “Edit Spanning Bridge Interface” page, the option fields include:

Enabled: specifies whether or not the bridge is to implement the spanning tree protocol

(STP).

Priority: sets the spanning tree protocol priority.

Path Cost: sets the cost of the path from all bridges to the root bridge.

In “Edit Frame Relay” page, the option fields include:

DLCI: sets the DLCI; the identifier for the Frame Relay data link channel that you are

using. The range of the DLCI is 16 to 1007.

Rx Max Pdu: sets the maximum Protocol Data Unit (PDU) size that can be received over

Frame Relay. The default value is 8192.

Tx Max Pdu: sets the maximum Protocol Data Unit (PDU) size that can be transmitted

over Frame Relay. The default value is 8192.

Chnl Segment Size: sets the size of the channel segment used by Frame Relay. The default

value is 0. If you set this to any number other than 0, DLCI level FRF.12

segmentation is enabled. The range of the segment size recommended is 200 to

1500. For more information on FRF.12, see

http://www.frforum.com.

Port: sets the port that an existing Frame Relay transport uses to transport data. (The port is

always fb for frame relay bridged.)

For the other Edit items, please refer to the descriptions in the Frame Relay routed subsection.

Note: The maximum number of Frame Relay DLCI channels that can be created is 14.

The availability of features and technical specifications herein subject to change without notice.