Chapter 8Configuring X.25
Introduction
A Smart Switch 1 800 X.2 5 port ca n conn ect to an X.25 DTE or an X. 25 netwo rk. This
allows the node to transmit X.25 traffic, as well as IP and IPX (encapsulated per RFC
1356), and SNA (per QLLC).
X.25 support in the SmartSwitch 1800 includes:
Full compliance with CCITT Recommendation X.25
Line spe e ds up to 2. 04 8 Mbps
Full X.121 addressing capability
Address translation
RFC 1356 for IP over X.25
RFC 1490 encapsulation (HDLC)
The SmartSwitch 1800 also supports logical X.25 ports, which allow multiple legacy
protocols (SDLC, async, bisync, etc.) to be encapsulated via X.25 and transmitted
over a single physical frame relay port. A SmartSwitch 1800 can contain up to 56
logica l ports, a l l on one phy sical po rt o r spread over sever al physica l ports.
Some thi ngs to kn ow about lo gi cal ports are:
Encapsu lation c an be via ei t her T1.61 7 Annex G or T1.617 RFC1 490. You
should know the pro s and cons of using each. Th e ex planati on of "Encapsulation
Meth od" on page 8-16 offers some help.
Both le ve l-2 and l e vel-3 wind ows can be configur ed. (Confi guration and oper -
ation is the same for either encapsulation method.)
Required Configuration
To run a physical port as X.25, make sure the following are properly configured:
Node parameter s (Chapter 4). T his is g eneral config uration t hat mu st be done
no ma tter wh ich pro tocols wi ll be r un in the nod e.
Loaded protocol s (Chapter 5): X.25 and any o thers that will be transmitted over
the X.25 link.
X.25 port(s) that will connect to the user device(s) and network. See page 8- 2.
SVC Subscriber ID(s) (page 8-21), which identifiy user devices to each other
and the SmartSwitch 1800.