H3C Technologies H3C Intelligent Management Center - Manual (Page 481)

467
needs more bandwidth than specified by Average Bandwidth, it can be allowed to temporarily
transmit data at a higher speed if a burst bonus is available. This parameter tops the number of
bytes that may be accumulated in the burst bonus and thus transferred at a higher speed.
• Peak Bandwidth(Kbit/s): Set the peak bandwidth (in Kbps) of a port. The peak bandwidth specifies
the maximum number of bits per second to allow across a port when it is sending a burst of traffic.
This tops the bandwidth used by a port whenever it is using its burst bonus. This parameter can
never be smaller than the average bandwidth.
NIC teaming
• Load Balancing: The load balancing policy determines how outgoing traffic is distributed among
the network adapters assigned to a vSwitch. Incoming traffic is controlled by the load balancing
policy on the physical switch. This feature provides the following options.
• Route based on the originating port ID: Select an uplink based on the virtual port where the traffic
entered the vSwitch.
• Route based on IP hash: Select an uplink based on a hash of the source and destination IP
addresses of each packet. For non-IP packets, whatever is at those offsets is used to compute the
hash.
• Route based on source MAC hash: Select an uplink based on a hash of the source MAC address of
each packet.
• Use explicit failover order: Always use the highest order uplink from the list of active adapters that
passes failover detection criteria.
• Network Failover Detection: Set the failover detection method, which can be Link Status only or
Beacon Probing.
• Link State only: Relies solely on the link status that the network adapter provides. This option detects
failures, such as cable pulls and physical switch power failures, but not configuration errors, such as
a physical switch port being blocked by spanning tree or misconfigured to the wrong VLAN or
cable pulls on the other side of a physical switch.
• Beacon Probing: Sends out and listens for beacon probes on all NICs in the team and uses this
information, in addition to link status, to determine link failure. This option detects many of the
failures mentioned above that are not detected by link status alone.
• Notify Switches: Specify that a notification is sent over the network to update the lookup tables on
the physical switches whenever a virtual NIC is connected to the vSwitch or whenever that virtual
NIC's traffic is routed over a different physical NIC in the team because of a failover event. If you
select Yes, whenever a virtual NIC is connected to the vSwitch or whenever that virtual NIC's traffic
is routed over a different physical NIC in the team because of a failover event, a notification is sent
over the network to update the lookup tables on the physical switches. In most cases, this is
desirable for the lowest latency of failover occurrences and migrations with VMotion. Do not use
this option when the virtual machines using the port group are using Microsoft Network Load
Balancing (NLB) in unicast mode. No such issues exist with NLB running in multicast mode.
• Failback: Specify how a physical adapter is returned to active duty after recovering from a failure.
If failback is set to Yes, the adapter is returned to active duty immediately on recovering, displacing
the standby adapter that took over its slot, if any. If failback is set to No, a failed adapter is left
inactive even after recovery until another active adapter fails, requiring its replacement.
5. Use the Failover Order option to specify how to distribute the work load for adapters. To use some
adapters but reserve others for emergencies, you can place them into the following groups.
• Active Adapters: Specifies the active adapters. The vSwitch can continue to use the adapter when
the network adapter connectivity is available and active.