🚀 go-pugleaf

Darren,

The answer to your question is "It depends".  It depends on what services
you are using VAX PSI for.  My understanding is that VAX PSI provides X.25
access for at least 3 purposes:

	 1) Forwarding DECNet Phase IV datagrams over VC's,
	 2) Allowing Triple-X (X.29/X.28/X.3) based login to the vax from
	    PAD's
	 3) allowing application programs to open X.25 VC's to arbitrary
	    hosts & services through a library interface.


If the machine(s) at the other end of PSS are DEC Vaxes, then you could
leave the PSS line directly connected to your vax, and still use the 64k
leased line through the Ethernet & cisco as your primary path.


     9.6 x25 (Public-PSS)
      ---------------------------------------------
						  |
		                   (LAN)	  |
                                     |		  |
                            |Cisco|  |	 -----------------------
                            |     |--|---|VAX with PSI Software|
			    |AGS2 |  |	 -----------------------
      ----------------------|     |  |
      64k Leased Line

If the machines at the other end of PSS are also cisco routers, then you
can do what you pictured:

		                   (LAN)
     9.6 x25 (Public-PSS)            |
      ----------------------|Cisco|  |
                            |     |--|---|VAX with PSI Software|
			    |AGS2 |  |
      ----------------------|     |  |
      64k Leased Line


We don't support application #3, VAX library access to X.25 via Ethernet.
If you are also using VAX PSI also to allow Triple-X access to the VAX
(application #2 above), then can use another cisco product, the Protocol
Translator, to convert from the Triple-X protocols to LAT.

Feel free to call or write to us (customer-service@cisco.com) for more details.


 -- Jim Forster
    cisco Systems