Default IP Addresses

The ClearPath Forward Management LAN (FM LAN) and the predefined IP-LAN secure fabric use Classless Inter-Domain Routing (CIDR) address allocation, where the network ID field is 16 bits, and the host ID field is 16 bits. While Unisys assigns default network ID fields for these LANs (see Default CIDR Address), the network ID fields can be configured during initial installation prior to commissioning any partitions. You can modify the network ID fields (upper two octets of the IP address) to customize for your environment. The lower two octets are fixed (see ClearPath Forward Management LAN (FM LAN) IP Addresses and IP-LAN Secure Fabric IP Addresses).

You use the Fabric Manager to configure your IP addresses. Note that the addresses for each LAN must be the same subnet.

Table 8. Default CIDR Address

LAN

CIDR Address (IP Subnet)

ClearPath Forward Management LAN (FM LAN)

172.29.0.0/16

IP-LAN Secure Fabric

172.31.0.0/16


Table 9. ClearPath Forward Management LAN (FM LAN) IP Addresses

Component

Endpoint

IP Address

Comments

Fabric Management Platform

Platform Management Console

172.29.m.254

Where m is used internally to identify the Fabric Management Platform.

  • Fabric Management Platform 1: m=254

  • Fabric Management Platform 2: m=253

Uses ports 1 and 2 on the LAN on motherboard (LOM) of the Fabric Management Platform.

Only one IP address is allowed for the Platform Management Console.

Fabric Manager

172.29.m.252

Where m is used internally to identify the Fabric Management Platform.

  • Fabric Management Platform 1: m=254

  • Fabric Management Platform 2: m=253

Uses port 1 on the LOM of the Fabric Management Platform and port A on the quad port NIC (slot 1), and the two ports are bonded for a single IP address.

If two Fabric Management Platforms are clustered for high availability, the “floating” FMP IP address is 172.29.254.60.

ClearPath Forward Dorado Operations Server

172.29.m.251

Where m is the ClearPath Forward Dorado Operations Server number.

  • Operations Server 1: m=254

  • Operations Server 2: m=253

Uses ports A and B on the quad port NIC of the Operations Server.

Enterprise Partition Platform

Platform Management Console

172.29.m.254

(bond) partition # (62)+192

Where m is used internally to identify the enterprise partition platform.

Uses ports 3 and 4 on the LAN on motherboard (LOM) of the enterprise partition platform.

Only one IP address is allowed.

The following addresses are reserved:

  • 172.29.m.62

  • 172.29.m.126

  • 172.29.m.190

 

s-Par® firmware

172.29.m.253

(bond) partition # (61)+192

Where m is used internally to identify the enterprise partition platform.

Uses ports 3 and 4 on the LAN on motherboard (LOM) of the enterprise partition platform.

Only one IP address is used for the connection.

The following addresses are reserved:

  • 172.29.m.61

  • 172.29.m.125

  • 172.29.m.189

Enterprise Partition Platform n

172.29.m.n

(bond)

Where m and n are used internally to identify the enterprise partition platform and the partition, respectively.

Note: For a nonpartitionable enterprise partition platform, the n value is always 1.

Uses ports 3 and 4 on the LAN on motherboard (LOM) of the enterprise partition platform, but only one IP address is used for the connection:

  • For a nonpartitionable enterprise partition platform (NEPP), the two ports are bonded (teamed) for a single IP address.

  • For a partitionable enterprise partition platform (PEPP), Unisys Secure Partitioning (s-Par) utilizes both ports but only presents a single virtual NIC (with one IP address) to the partition image.

The following addresses are reserved:

  • 172.29.m.n+64

  • 172.29.m.n+128

  • 172.29.m.n+192

InfiniBand Switch 1

Management Port 1

172.29.0.1

Switch management port 1 (mgmt0) on the switch.

Note: For a single cabinet ClearPath Forward Dorado system, the IP address is 172.29.254.126.

Management Port 2

172.29.254.190

Switch management port 2 (mgmt1) on the switch.

InfiniBand Switch 2

Management Port 1

172.29.0.2

Switch management port 1 (mgmt0) on the switch.

Note: For a single cabinet ClearPath Forward Dorado system, the IP address is 172.29.253.126.

Management Port 2

172.29.253.190

Switch management port 2 (mgmt1) on the switch.

InfiniBand Switches 1 and 2

Subnet Manager

172.29.0.3

The virtual management IP address for a high availability configuration.

Note: For a single cabinet ClearPath Forward Dorado system, the IP address is 172.29.254.61.

InfiniBand-Ethernet Gateway Switch 1

Management Port 1

172.29.254.127

Switch management port 1 (mgmt0) on the switch.

Management Port 2

172.29.254.191

Switch management port 2 (mgmt1) on the switch.

Not available on the 12-port switch.

InfiniBand-Ethernet Gateway Switch 2

Management Port 1

172.29.253.127

Switch management port 1 (mgmt0) on the switch.

Management Port 2

172.29.253.191

Switch management port 2 (mgmt1) on the switch.

Not available on the 12-port switch.

FM LAN Ethernet Switch 1

Ethernet Switch

172.29.254.62

Switch IP address for management, if required; no physical port needed.

FM LAN Ethernet Switch 2

Ethernet Switch

172.29.253.62

Switch IP address for management, if required; no physical port needed.


Table 10. IP-LAN Secure Fabric IP Addresses

Component

Endpoint

IP Address

Comments

Enterprise Partition Platform

Enterprise Partition Platform n

172.31.m.n

172.31.m.n+64

172.31.m.n+128

172.31.m.n+192

Where m and n are used internally to identify the enterprise partition platform and the partition, respectively.

Note: For a nonpartitionable enterprise partition platform (NEPP), the n value is always 1.

Uses ports 1 and 2 on the InfiniBand HCA (slot 3) of the enterprise partition platform.

For nonpartitionable enterprise partition platforms (NEPPs), you can choose to bond the ports for a NEPP running the Linux operating system. However, bonding (teaming) of ports is not supported for a NEPP running the Windows operating system.

For partitionable enterprise partition platform (PEPPs), IP addressing allocation is as follows:

  • 172.31.m.n

    Bond used with Linux

    Bond used in ClearPath Forward Dorado

    Port 1 configured in Windows

  • 172.31.m.n+64

    Available in fabric

    Port 1 Slot 3 configured in ClearPath Forward Dorado

    Port 1 configured in ClearPath Forward Libra

  • 172.31.m.n+128

    Port 1 configured in Linux

    Port 1 Slot 6 configured in ClearPath Forward Dorado

    Port 2 configured in ClearPath Forward Libra

  • 172.31.m.n+192

    Port 2 configured in Linux

    Available in ClearPath Forward Libra

Note: For ClearPath Forward Dorado, n is always 1. For ClearPath Forward Libra, n can be any value.


Table 11. Customer LAN IP Addresses

Component

Endpoint

IP Address

Comments

Fabric Management Platform 1

Customer device

Customer choice

For connecting the Fabric Management Platform to customer management network environment.

Port C on quad port NIC in slot 1 of the Fabric Management Platform.

Customer device

Customer choice

For connecting the Fabric Management Platform to customer management network environment.

Port D on quad port NIC in slot 1 of Fabric Management Platform.

Fabric Management Platform 2 (standby)

Customer device

Customer choice

For connecting the Fabric Management Platform to customer management network environment.

Port C on quad port NIC in slot 1 of the Fabric Management Platform.

Customer device

Customer choice

For connecting the Fabric Management Platform to customer management network environment.

Port D on quad port NIC in slot 1 of the Fabric Management Platform.


Table 12. Secure Fabric IP Addresses

Component

Endpoint

IP Address

Comments

Enterprise Partition Platform

Enterprise Partition Platform m

x.y.m.n

Where x and y is customer choice.

Where m and n are used internally to identify the enterprise partition platform and the partition, respectively.

Note: For a nonpartitionable enterprise partition platform (NEPP), the n value is always 1.

For nonpartitionable enterprise partition platforms (NEPPs), you can choose to bond the ports for a NEPP running the Linux operating system. However, bonding (teaming) of ports is not supported for a NEPP running the Windows operating system.

For partitionable enterprise partition platform (PEPPs), IP addressing allocation is as follows:

  • x.y.m.n

    Bond used with Linux

    Bond used in ClearPath Forward Dorado

    Port 1 configured in Windows

  • x.y.m.n+64

    Available in fabric

    Port 1 Slot 3 configured in ClearPath Forward Dorado

    Port 1 configured in ClearPath Forward Libra

  • x.y.m.n+128

    Port 1 configured in Linux

    Port 1 Slot 6 configured in ClearPath Forward Dorado

    Port 2 configured in ClearPath Forward Libra

  • x.y.m.n+192

    Port 2 configured in Linux

    Available in ClearPath Forward Dorado and ClearPath Forward Libra

Note: For ClearPath Forward Dorado, n is always 1. For ClearPath Forward Libra, n can be any value.