Configuring the FM LAN Connection for Red Hat Linux

Log in as root, and do the following:

  1. Create a file named ifcfg-eth-fmp3 in the /etc/sysconfig/networks-scripts directory with the following content:

    DEVICE=eth-fmp3
TYPE=Ethernet
ONBOOT=yes
BOOTPROTO=none
NM_CONTROLLED=no
SLAVE=yes
MASTER=bond1
USERCTL=no
HOTPLUG=yes

  2. Create a file named ifcfg-eth-fmp4 in the /etc/sysconfig/network-scripts directory with the following content:

    DEVICE=eth-fmp4
TYPE=Ethernet
ONBOOT=yes
BOOTPROTO=none
NM_CONTROLLED=no
SLAVE=yes
MASTER=bond1
USERCTL=no
HOTPLUG=yes

  3. Create a file named ifcfg-bond1 in the /etc/sysconfig/network-scripts directory with the following content:

    DEVICE=bond1
IPADDR=172.29.xx.1
PREFIX=16
ONBOOT=yes
NM_CONTROLLED=no
BOOTPROTO=none
MTU=
USERCTL=no
BONDING_OPTS="mode=active-backup miimon=250"

    Where xx is the platform number for your enterprise partition platform.

    Note: The default subnet of the FM LAN is 172.29. If the subnet was changed (for example, during initial hardware installation and software configuration), be sure to use the new subnet value when configuring your network connections. If needed, use the Fabric Manager user interface to check the FM LAN IP address for the partition on the partition summary page of the nonpartitionable enterprise partition platform (NEPP).

  4. Update the file named /etc/modprobe.d/bonding.conf with the following line:

    alias bond1 bonding

  5. If you have a firewall, ensure that your firewall rules allow responses to incoming pings on the FM LAN.

    Note: The Fabric Manager monitors the health status of a partition image through ping checks; if the ping requests on the FM LAN to the partition image are blocked by a firewall, the Fabric Manager user interface displays a warning state for the partition image’s health (but does not generate an event).

Proceed to update the UDEV persistent rules for Red Hat Linux. For more information, see Updating the UDEV Persistent Rules for Red Hat LINUX.