Access network

Content Platform S Series Node Help

Version
4.0.0
Audience
anonymous
Part Number
MK-HCPS027-02

For communication to occur over the access network, at least one access network port on one server module must be connected to an active Ethernet switch.

To work with the access network in the Management Console, go to Configuration > Networking. Then click the edit icon (Pencil icon) for the access network.

Port bonding and transmit hash policy

The access network ports can be configured for active-active bonding using the IEEE 802.3ad Link Aggregation Control Protocol (LACP) or for active-backup bonding. When the bonding mode is active-backup, the active port is the lowest-numbered connected port. All other connected ports are backup ports.

With 802.3ad bonding, the selected S Series Node transmit hash policy determines how the ports in the bond share the workload on the network. The options are layer 2+3 and layer 3+4:

  • With layer 2+3, all traffic from any given client port targets the same access network port. Because the target port for a client port is selected independently of the target port selection for any other client port, the workload is not guaranteed to be balanced across the bonded access network ports. However, the greater the number of client ports, the more balanced the workload is likely to be.
  • With layer 3+4, an algorithm enables traffic from any given client to span multiple access network ports. The algorithm ensures that the workload is balanced across the bonded access network ports.

With active-backup bonding, the only possible transmit hash policy is layer 2. With the S Series Node, layer 2 by itself is effectively the same as layer 2+3.

Port connections

The access network ports connect the server modules to your networking infrastructure through one or two Ethernet switches. The suggested configurations are:

  • Both the access network and two switches configured for active-backup bonding. In this case, all the even-numbered ports (that is, eth0 and, if present, eth2) in use on both server modules connect to one switch. All the odd-numbered ports (that is, eth1 and, if present, eth3) in use on both server modules connect to the other switch.
  • Both the access network and one or two switches configured for 802.3ad bonding:
    • With one switch, all the ports being used on both server modules connect to that switch.
    • With two switches, all the ports being used on one server module connect to one switch. All the ports being used on the other server module connect to the other switch.
  • Both the access network and two switches configured for 802.3ad bonding and Cisco Virtual Port Channel (vPC). In this case:
    • All the even-numbered ports (that is, eth0 and, if present, eth2) in use on one server module and all the odd-numbered ports (that is, eth1 and, if present, eth3) in use on the other server module connect to one switch.
    • All the odd-numbered ports in use on the first server module and all the even-numbered ports in use on the second server module connect to the other switch.

For the best configuration for your S Series Node, consult your network administrator.

Port connection expectations

You can configure the access network so that the S Series Node expects specific access network ports to be connected to an active switch.

Regardless of the configured expectations, the S Series Node uses each connected port, either as an active port or as a backup port, depending on the bonding mode.

Tip: To prevent the S Series Node from issuing alerts about unexpected or missing port connections, set the connection expectation for each port according to whether the port is actually connected to an active switch.