Filter
Top Products
Chapter 12: AI2524 X.25 Configuration Steps
August 1997 Page 12-19
2524UM
support several protocols; alternatively, you can define one map for
each supported protocol.
In interface configuration mode, establish a map:
x25 map
protocol address
[
protocol2
address2
[...[
protocol9 address9
]]]
x121-
address
[
option
]
For example, if you are encapsulating IP over a given X.25 interface,
you must define an IP address for the interface and, for each of the de-
sired destination hosts, map the host's IP address to its X.121 address.
Note: You can map an X.121 address to as many as nine
protocol addresses, but each protocol can be mapped only
once in the command line.
An individual host map can use these keywords to specify these pro-
tocols:
z apollo
—Apollo Domain
z bridge
—Bridging
z clns
—OSI Connectionless Network Servic
z compressedtcp
—TCP/IP header compression
z ip
—IP
z ipx
—Novell IPX
z pad
—Packet Assembler/Disassemble
z qllc
—IBM's QLLC
Each mapped protocol, except bridging and CLNS, takes a datagram
address. All bridged datagrams are sent to all bridge maps on an inter-
face. CLNS uses the mapped X.121 address as the SNPA, which is ref-
erenced by a
clns neighbor
command. The configured datagram
protocol(s) and relevant addresses are mapped to the destination host's
X.121 address. All protocols that are supported for RFC 1356 opera
tion can be specified in a single map. Bridging and QLLC are not sup-
ported for RFC 1356 encapsulation. If IP and TCP/IP header
compression are both specified, the same IP address must be given for
both protocols.
When setting up the address map, you can include options such as en-
abling broadcasts, specifying the number of virtual circuits allowed,
and defining various user facility settings.