Visara FEP-4600 Planning Guide - Manual (Page 68)

Chapter 6. Support of PU 4 Connections
6-12 707117-003
Loading of Remote NCPs
For environments where an NCP is currently being loaded remotely into a remote 3745
through a local 3745, it may be desired to be able to remotely load that NCP through the
facilities of the FEP-4600. This is not currently supported. Let’s look at this situation
more closely, however for other solutions.
Note: The clustering feature described below is no longer offered for new installations.
It can be assumed that the remote 3745 is part of the local SNA network, thus owned by
the same organization that owns or is replacing the local 3745. Remote loading of an
NCP is typically part of a disaster recovery plan, or the remote 3745 is positioned to
better provide resources closer to where they are needed.
The FEP-4600 technology is better suited to replace the remote 3745 and associated NCP
license, with a remote FEP-4600 in its place. Requirements to have a serial interface to
the remote 3745 for loading purposes go away, and higher speed, more dynamic IP
connections can be implemented instead. The clustering feature of the FEP-4600 can be
leveraged to make the remote network connections appear to be local, making
administration of the remote connections simpler and more dynamic.