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

37x5 to FEP-4600 Migration and Planning Guide
707117-003 12-1
Chapter 12. Frequently Asked Questions
Q: Does the FEP-4600 run NCP?
A: No.
Q:
How do you load a gen from VTAM into the FEP-4600?
A: You don’t. The FEP-4600 is independently configured using a web browser. The
configuration is stored on the hard drive in the form of an INI file, and is
automatically booted at IML time.
Q:
How do I activate the FEP-4600?
A: Once the FEP-4600 is properly configured, it is self activating. Because the FEP-
4600 uses gateway technology and spoofs VTAM(s) and remote front ends, it will
automatically attempt to communicate once it has booted. You will still have to
activate VTAM resources, such as the VTAM Major nodes for devices, and PU4
link stations that communicate through the FEP-4600. Most remote connections
will simply self activate.
Q:
Do I have to change my VTAM or NCP gens to support the FEP-4600?
A: Yes. Since the FEP-4600 does not run NCP, there is no NCP gen. PU4
connections are defined as channel-to-channel connections, not as an NCP. PU2
connections are defined as Switched Major Node definitions (requires an XCA
definition). In some cases information that must be implicitly defined for NCP,
may in fact be learned by the FEP-4600 ‘on the fly’. In many cases the VTAM
gen is much simpler. Some resources such as PU 2 Switched definitions may be
used ‘as is’.
Q:
Is there a NetView interface in the FEP-4600?
A: No, not at this time. However, the platforms supported by the FEP-4600 over
remote links will still work the same from a NetView perspective as before. The
FEP-4600 passes the NMVT datastreams used by NetView to the attached
products.
Q:
Is the FEP-4600 a PU type 4?
A: No. The FEP-4600 is actually a gateway product. It supports PU 4 traffic through
it, and does terminate certain PU4 connections within it, but does not function as a
PU 4 itself. As a gateway product, the FEP-4600 brings itself up automatically at
boot time, and does not require activation by VTAM. It appears to VTAM as if it
were an adjacent VTAM. Links to and through the FEP-4600 will typically
require an operator to initiate similar to other CTC connections. The FEP-4600
handles PU 4 datastreams and responds to CDRM requests, appearing to the
external world to have a CDRM within it.