Cabletron Systems Netlink FRX4000 User Manual page 47

LLC2 Function
RFC1490 Format
Subscriber IDs
Introduction to Database Configuration
originated LLC2 interface must match the LAN ID on the corresponding termi-
nated interface.
Be aware that when configuring these records, LAN IDs must be entered in hex. Also
note that, other than the matching IDs on each originated/terminated interface pair,
each LAN ID must be unique within the network on which the FRX4000/6000 will
operate.
Internally, LLC2 connects to interfaces via a virtual bridge. LLC2 Host and Interface
records act as both origination and termination points for LLC2. For example, if you
are configuring SDLC-to-LLC2 conversion to be transmitted over frame relay to a
Token Ring host, the following is the logical LLC2 record flow: SNA Port/PU record
(Chapter 9), with the parameter
LLC2 Host and LLC2 Interface termination record). In addition, you must configure
an originated Host for the target MAC address, and an interface for the physical con-
nection.
Terminated LLC Host records always make the calls. Originated LLC Host records
always expect to receive calls.
Only one Originated and one Terminated LLC Host record can be configured for each
MAC address.
An RFC1490 format used for SNA traffic is configured in the frame relay LLC2
Interface/Bridge Port record. The options, in order of lowest overhead to highest
overhead, are:
Native LLC2 (also known as BNN, or Boundary Network Node). When this
format is used, no MAC addresses are transmitted across the frame relay link.
802.5 SRB (source route bridge) (also known as BAN, or Boundary Access
Node. (FRX4000/6000 devices support BAN type 1). This format is generally
used for 3174 gateways and AS/400s, because they need to see a MAC address).
802.3 TB (transparent bridge), used when talking to routers that cannot do BAN
or BNN.
Subscriber IDs are only used locally within each FRX4000/6000 to link records (e.g.
SDLC PU record to LLC host record), unless the device is running X.25, SDLC/LLC2
primary (the FRX4000/6000 would be SDLC secondary to the FEP), or logical ports
(i.e., QLLC), in which case the subscriber IDs correlate to the static routes defined in
the subscriber routing tables.
set to
LLC2 Connection
. (This acts as the both the
Yes
3-9