Visara FEP-4600 Installation - Manual (Page 61)

FEP-4600 Installation and Configuration
707119-001 5-9
Drop ID: The ‘Drop ID’ is the name that is being given to this drop, and is the same
name that will be added to the list of drops when this definition is saved. The name can
be most any text string (alphanumeric characters plus dash, underscore, and period
characters), and should be created by the administrator to provide a name for the drop
that is most useful to describe what or where it is.
Remote MAC Address: This is the LAN address of the platform that the FEP-4600 is
talking to on this drop. This address might also be referred to as the remote platform’s
hardware address or LLC address. Note that an address of ‘00:00:00:00:00:00’ will
indicate that this drop has been configured to be dynamic (’00:00:00:00:00:00’ is not
accepted for a static definition). Any other address makes this definition static. See the
discussion below about dynamic versus static drops.
Local SAP: This option defines the local Service Access Point address that is assigned
by the FEP-4600 for use for communications with the remote platform. Refer to the ‘SAP
Assignments’ section above for selecting a valid SAP value. Note that if you have the
Dynamic Connections option selected, the SAP used for the dynamic connections should
be different than the one used for static connections.
Remote SAP: This option defines the remote Service Access Point address that is
configured on the remote platform that the FEP-4600 is communicating with. Refer to the
‘SAP Assignments’ section below for a discussion on selecting valid SAP values.
Max Transmit Frame Size: This value represents the maximum size frame (including
TH, RH, and RU) that may be sent in a single packet over the LLC link. Most Token
Ring LLC circuits are limited to a maximum frame size of 4105, but some (usually older)
platforms may be limited to a smaller maximum frame size. Using a smaller value than
what is supported by the session partner will work, but will result in the transmission of
more packets than if a larger value is set. The minimum size for a PU type 2 is 265. The
default value for this option is 521. Note that if the traffic is to cross an Ethernet LAN
segment to get to the session partner, then the maximum value must be restricted to that
handled by Ethernet (a value of 1490).
Receive Window Size: This is the maximum number of packets in an LLC conversation
with a session partner that can be received, before an LLC acknowledgement must be
sent. The default value for this option is 1. Refer to the ‘Window Size Selection’ section
below.
Transmit Window Size: This is the maximum number of packets that will be sent
before requiring an LLC acknowledgement. The default value for this option is 2. Refer
to the ‘Window Size Selection’ section below.