Skip to content

cofignetwork_for_RH7

Yuan Bai edited this page Nov 25, 2015 · 5 revisions

configuring physical nics/bond/vlan/bridge

Main Function

  1. Disable network manager, enable network service.

  2. Get nics types and nicdevice list from nics table.

  3. Configure bond/vlan/bridge, and create network interface configure file to configure bond,vlan and bridge (linux bridge or ovs bridge). For easier understanding, we assume there are physical nics eth1, eth2, eth3, eth4 which can be configured in different scenarios as bond/vlan or bridge, there are several main usage scenarios in "configuring ethx/bond/vlan/bridge" as following:

    a). configure bond using multiple physical nics ethx.... But we will not cover bond different types of nics. we will cover bonding physical nics directly, for example, configure bond0 using eth1 and eth2:

    `bond0----eth1,eth2`
    

    b). configure vlans for physical nics, for example, configure 2 vlans for eth1, vlan ids are 1 and 2, vlan names are eth1.1 and eth1.2;

    `eth1---eth1.1,eth1.2`
    

    c). create bridge (linux or ovs) for physical nics ethx... directly, for example,

    `eth1---br1, eth2---br2`
    

    d). configure vlans for physical nics, create bridge for every vlan, for example,

    `eth1---eth1.1---br11`
    
    `eth1---eth1.2---br12`
    
    `eth2---eth2.1---br21`
    
    `eth2---eth2.2---br22`
    

    e). configure bond first, then create bridge, for example,

    `eth1,eth2,eth3---bond0---br0`
    

    f). configure bond with different physical nics ethx..., then configure vlans using these bonds, create bridge using these vlans, for example,bonding eth1 and eth2 to create bond0, make vlan bond0.1 and bond0.2; bonding eth3 and eth4 to create bond1, make vlan bond1.11 and bond1.12, create br11 using bond1.11, create br12 using bond1.12

    `eth1,eth2---bond0---bond0.1,bond0.2`
    `bond0.1---br01`
    `bond0.2---br02`
    
    `eth3,eth4---bond1---bond1.11,bond1.12`
    `bond1.11---br11`
    `bond1.12---br12`
    

User interface

Here gives an example for easier understanding user interface. Physical nics are eth1 and eth2; bonding eth1 and eth2 as bond1; from bond1, make 2 vlans: vlan1 and vlan2; make bridge br1 using vlan1, make bridge br2 using vlan2, br1 ip is 10.0.0.1, br2 ip is 20.0.0.1.

News

History

  • Oct 22, 2010: xCAT 2.5 released.
  • Apr 30, 2010: xCAT 2.4 is released.
  • Oct 31, 2009: xCAT 2.3 released. xCAT's 10 year anniversary!
  • Apr 16, 2009: xCAT 2.2 released.
  • Oct 31, 2008: xCAT 2.1 released.
  • Sep 12, 2008: Support for xCAT 2 can now be purchased!
  • June 9, 2008: xCAT breaths life into (at the time) the fastest supercomputer on the planet
  • May 30, 2008: xCAT 2.0 for Linux officially released!
  • Oct 31, 2007: IBM open sources xCAT 2.0 to allow collaboration among all of the xCAT users.
  • Oct 31, 1999: xCAT 1.0 is born!
    xCAT started out as a project in IBM developed by Egan Ford. It was quickly adopted by customers and IBM manufacturing sites to rapidly deploy clusters.
Clone this wiki locally