IBM Power Systems/AIX (H62x) FAQs
MIGAIX1.0.x BFX Migration Tool Frequently Asked Questions
Refer to the Support Table for the supported releases of MIGAIX. Typically the latest release is the highest numbered version.
No. A software key is not required for this tool.
H624 1.x (Secure NetEx/IP) Frequently Asked Questions
Refer to the Support Table for the supported releases of H624. Typically the latest release is the highest numbered version.
Yes. A software key is required to operate this product. To obtain a key, please contact support@netex.com with your company and site name, contact information, NetEx/IP product designator (i.e. H624) and the host name.
With Secure NetEx/IP, IP Addresses and the corresponding NetEx Hostname must be added to the name resolver (or in the /etc/hosts file). The order in which IP Addresses are returned from the resolver is dependent on the resolver configuration.
While Secure NetEx/IP provides many of the same features and User Interface for NetEx applications, it is NOT interoperable. Legacy NetEx/IP applications must be linked with the Secure NetEx/IP library on both the local and remote hosts.
H625 1.x (Secure BFX) Frequently Asked Questions
Refer to the Support Table for the supported releases of H625. Typically the latest release is the highest numbered version.
No. A software key is not required to operate this product.
With Secure BFX and Secure NetEx/IP, IP Addresses and the corresponding NetEx Hostname must be added to the name resolver (or in the /etc/hosts file). The order in which IP Addresses are returned from the resolver is dependent on the resolver configuration.
While Secure BFX provides many of the same features and User Interface as legacy BFX, it is NOT interoperable. BFX jobs must operate with the Secure BFX products on both the local and remote hosts.
Refer to the Support Table for the supported releases of H620IP. Typically the latest release is the highest numbered version.
Yes. A software key is required to operate this product. To obtain a key, please contact support@netex.com with your company and site name, contact information, NetEx/IP product designator (i.e. H620IP) and the host name.
Note: Beginning with Release 7.0.1, a new license key structure is in place so a new key will need to be obtained when upgrading from Releases prior to Release 7.0.1.
The order in which paths are generated is related to the order in which ADAPTER statements are specified in the NCT. Paths are generated in the following order: For each Local Host ADAPTER (proceeding from last to first), paths are generated to each Remote Host ADAPTER (proceeding from first to last). For example:
HOSTA HOST TYPE=Linux MODEL=Fedora ADAPTER MODEL=N130 NETADDR=02 TO=eth0 ADAPTER MODEL=N130 NETADDR=03 T0=eth0 HOSTB HOST TYPE=Linux MODEL=Fedora ADAPTER MODEL=N130 NETADDR=12 T0=eth0 ADAPTER MODEL=N130 NETADDR=13 T0=eth0
Paths will be generated in the following order:
Path 1: 03->12 Path 2: 03->13 Path 3: 02->12 Path 4: 02->13