FS6200 Server System Implementation Guide - Public Support ...

Changing the Network Services EVLAN IP Address
Unisys recommends that you do not change the IP Address and Subnet Mask for Network
Services (EVLAN path). However, one reason to change these addresses is because you
already have nodes in your network using the same subnet. In this case, choose a
different private set of IP addresses that do not conflict with the subnets in your network.
Modify the EVLAN IP address and mask through the system editor. Refer to ″Using the
System Editor to Configure MCP Networking″ later in this section for more information.
Notes:
• The Internet Assigned Numbers Authority (IANA) has reserved Class C addresses
192.168.0.0 through 192.168.255.255 for use within private networks (see RFC 1918).
• Changing the IP addresses of the EVLAN path is likely to require updates to the
firewall rules within the I/O engine of the FS6200 Server. See the topic “Environment
Secured Configuration” in Section 4 of this guide. Call Home functionality might also
be affected. Refer to the appropriate Call Home documentation for more information.
Supporting MCP Network Adapters
Customizing the Server Configuration
MCP network adapters provide MCP access to qualified NICs, operating at speeds ranging
from 10 megabits per second to 10 gigabits per second. Although the MCP network
adapter software service allows connection to networks comprised of high-performance
technologies, the actual data transfer rate might be less than the potential maximum for
that network technology. For example, a 10Gb Ethernet MCP network adapter allows the
MCP server to participate on a 10Gb Ethernet backbone, but the MCP does not transfer
data at the maximum 10Gb Ethernet transfer rate.
The FS6200 Server includes all necessary licenses required for MCP network adapter
connections through TCP/IP.
Network Services supports up to eight MCP network adapter connections per Network
Processor – where a connection is an Ethernet port, an 802.1Q Virtual LAN (VLAN)
connection, or an Adapter Team. In essence, the ClearPath Network Services view of an
adapter is the same as that of the I/O engine view of the adapter. If it shows up as an entity
to be managed within the Network Connections list of the Network and Sharing center
within Control Panel, then you can make an MCP network adapter out of it. This is
accomplished through the MCP Networking entities listed by the System Editor and using
one of the MCP network adapter connections for a network processor.
Network Services supports up to 6 network processors per I/O engine on ClearPath
FS6200 Server systems. Both TCP/IP and Heritage Network Services (BNA) are supported
to and from the MCP Environment through MCP network adapter connections. The use of
Heritage Network Services might require the purchase of additional MCP software
licenses beyond the base Integrated Operating Environment package.
8222 3694–000 3–15