7 Replies Latest reply on Aug 20, 2011 5:39 AM by edwardzh

    NIC Bonding/Teaming and RMM3




      I have the Server Board S3420GPLX with a XEON 3450, BIOS 49, BMC124, FRUSDR09,

      withe the RMM3 Modul.

      I was happy with the module RMM3 particularly because it enables the turning on the computer.

      Now I have merged the two on S3420GPLX available NICs in Linux via bonding (802.3ad / LACP), accordingly I have configured the switch.

      This works.
      BUT the RMM3 module is no longer remotely accessible,
      not on a separate (third) port of the module itself
      What do I need to adjust to reach the server remote again by RMM3 - even if he turned out?




        • 1. Re: NIC Bonding/Teaming and RMM3

          What IP address is assigned to the team, and what IP address to the RMM3?


          If you check your ARP cache, did the team accidentally get the MAC address of the RMM3, somehow?

          • 2. Re: NIC Bonding/Teaming and RMM3

            Let me clarify here - you have three network cables connected to the server, two to the onboard NICs and on to the dedicated RMM3 NIC right? and you configured the two onboard NICs in a 802.3ad bonding.


            You may want to check your switch settings and make sure the switch port connected to the RMM3 port is not configured as part of the 802.3ad bonding. The RMM3 port should be totally seperate from OS networking. Also, make sure the BMC channel 1 IP address is not configured in the same subnet as channel 3 (RMM3 port).

            • 3. Re: NIC Bonding/Teaming and RMM3

              Hi Dan, Hi Edward


              Thanks for the reply.
              I think my configuration is wrong, if I understand correctly your answer.
              My current configuration:
              In the BIOS: Server Management
              1: Base board LAN Configuration - Static
              IP - Subnet - GW: - -
              2: Intel LAN co RMM3 - Static
              IP - Subnet - GW: - -
              Configuration via web browser: Network Settings
              Lan Channel - Baseboard Mgmt MAC: 00:1 e: 67:06: ce: 2a IP:
              Lan Channel - Intel RMM3 MAC: 00:1 e: 67:06: ce: 2b


              My Teaming configuration (Debian Linux)
              iface bond0 inet manual
                       slaves eth0 eth1
                       bond_miimon 300
                       bond_mode 802.3ad
              vmbr0 iface inet static
                       bridge_ports bond0
                       bridge_stp off
                       bridge_fd 0


              And the system says:
              Proxmox: ~ # cat / proc/net/bonding/bond0
              Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)


              Bonding Mode: IEEE 802.3ad Dynamic link aggregation
              Transmit Hash Policy: layer2 (0)
              MII Status: up
              MII Polling Interval (ms): 300
              Up Delay (ms): 0
              Down Delay (ms): 0


              802.3ad info
              LACP rate: slow
              Aggregator selection policy (ad_select): stable
              Active aggregator Info:
                       Aggregator ID: 2
                       Number of ports: 2
                       Actor Key: 17
                       Partner Key: 1
                       Partner Mac Address: 1c: 7e: e5: 18:6 c: 2d


              Slave Interface: eth0
              MII Status: up
              Link Failure Count: 1
              Permanent HW addr: 00:1 e: 67:06: ce: 29
              Aggregator ID: 2


              Slave Interface: eth1
              MII Status: up
              Link Failure Count: 0
              Permanent HW addr: 00:1 e: 67:06: ce: 28
              Aggregator ID: 2


              Both depend on the motherboard NICs, pluged in a D-Link switch on port 17 + 18.

              This ports 17+18 as well on the switch set as a team (802.3ad LACP)


              The RMM3 port of the server is plugged in the same switch (of course without teaming)


              Nachricht geändert durch symie

              • 4. Re: NIC Bonding/Teaming and RMM3

                Try to assign LAN Channel 1 of your BMC an IP address of different subnet (e.g. 10.x.x.x) and access RMM3 via

                • 5. Re: NIC Bonding/Teaming and RMM3



                  It works!

                  Now I get back the RMM3 module, even if the server is out.


                  I have a problem all MAC- and IP- addresses on ports surely assigned to.


                  An attempt:


                  1: NIC_1 - (eth0)  00:1e:67:06:ce:29
                                                NIC_1 + NIC_2 = = = > teaming > Mode > 802.3ad LACP
                  2: NIC_2 - (eth1)  00:1e:67:06:ce:28


                  3: Basebord LAN  Static - MAC: 00:1e:67:06:ce:2a
                  old:  IP - Supbnet - GW: - -
                  new:  IP - Supbnet - GW: - -


                  4: Intel RMM3 LAN co - Static - MAC:  00:1e:67:06:ce:2b
                  IP - Supbnet - GW: - -


                  If I disconnect the LAN cable from NIC_1 NIC_2  I still reach the RMM3 port.t (top-No.4).

                  What is and where is No.3 Base board LAN - witch I of course cannot achieve?


                  thank you

                  • 6. Re: NIC Bonding/Teaming and RMM3

                    If you're asking about 3: Basebord LAN  Static - MAC: 00:1e:67:06:ce:2a - it's BMC LAN channel 1, and it shares the physical NIC port with NIC 1 (in your case eth1, because of the enumerate order). Since you're using RMM3, you don't need that port anymore because all BMC functions are also available on RMM3. Configuring it to another subnet eliminates the confusion to the BMC so that it will always use RMM3 port for network community.

                    1 of 1 people found this helpful
                    • 7. Re: NIC Bonding/Teaming and RMM3

                      Hello Edward,


                      okay, I understand it.

                      your answer will help me very much.


                      Thank you.