Differences

This shows you the differences between two versions of the page.

Link to this comparison view

public:hardware:headnode:start [2012/04/17 13:28]
jonmills
public:hardware:headnode:start [2014/03/20 14:09] (current)
jonmills
Line 1: Line 1:
 ====== ExoGENI Head Node ====== ====== ExoGENI Head Node ======
  
-==== Example Hardware Specs ==== +==== IBM x3650 M4  ==== 
- +Part Number Description Quantity ^ 
-Vendor Model Revision CPU(s) ^ CPU Speed ^ CPU Cores ^ CPU Count ^ RAM ^ HDD ^ 1GB NICs | +7915AC1|IBM System x3650 M4|1| 
-| IBM x3650 M3 7945-AC1 Intel Xeon E5620 2.40GHz 4 | 2 | 8 2GB DDR3 PC3-10600 1333MHz ECC | > 500 GB | 8 +A2N2  |ServeRAID M5110e SAS/SATA Controller for IBM System x| 
-IBM | x3650 M4 | | | | | | | | +A1JX  |x3650 M4 8x 2.5" HS HDD Assembly Kit| 
- +A1LF  |IBM System x Lightpath Kit
-==== Notes ==== +3757  |IBM Single Cable USB Conversion Option (UCO)| 
- +A3V6  |IBM System x3650 M4 Planar (IVB Refresh )| 
-  * [[Installation Installation Notes]] +6263  |4.3m, 10A/100-250V, C13 to IEC 320-C14 Rack Power Cable
-  * [[Network Network Configuration]] +A1LA  |x3650 M4 System Level Code| 
- +A1ML  |IBM Integrated Management Module Advanced Upgrade
-==== Network Configuration ==== +A1JZ  |System Documentation and Software-US English| 
- +9206  |No Preload Specify
-=== Interfaces === +| A2R0  |x3650 M4 Mini SAS Cable 820MM| 
- +| A1L8  |x3650 M4 Riser 2 Bracket| 
-^ Bond ^ Slave Interfaces ^ VLAN(s^ Tagging ^ Purpose ^ +| A1JP  |x3650 M4 PCIe Riser Card 1 (1 x16 FH/FL + 1 x8 FH/HL Slots)| 
-bond0 eth0 (from public); eth4 (from Port 47 on BNT8052) | 1010 untagged Public +| 5977  |Select Storage devices no IBM-configured RAID required| 
-bond1 eth1, eth5 1009 untagged iSCSI +| A1KF  |IBM System x3650 M4 2.5Base without Power Supply| 
-bond2 eth2,eth3,eth6,eth7 1006,1007,1008 tagged Mgt, OpenStack, xCAT +| A1LB  |x3650 M4 Agency Label GBM| 
- +| 8971  |Integrate in manufacturing| 
-=== A Word on Public Interface Connection === +| 2306  |Rack Installation >1U Component| 
-In an ideal scenario, the head node has public access failover capability, via a bonded active/active or active/passive interface.  In that scenario, the provider has two cables providing public-facing connectivity.  One runs to the head node, and the other runs to the SSG5.  For example: +| 8034  |e1350 Solution Component| 
- +| A193  |Integrated Solutions| 
-  * Go to eth0 on head node +| 3101  |Rack 01| 
-  * Goes to 0/0 on SSG5 +| A2U4  |IBM 128GB SATA 2.5MLC HS Enterprise Value SSD|2| 
-    * Go to port 48 on mgt switch (BNT8052+| A1H5  |IBM System x 750W High Efficiency Platinum AC Power Supply|2| 
-    * Go from port 47 on mgt switch back to eth4 on head node +| A3VY  |Addl Intel Xeon Processor E5-2640 v2 8C 2.0GHz 20MB Cache 95W| 
- +| 3737  |3m Molex Direct Attach Copper SFPCable| 
-The SSG5 has an IPSEC tunnel back to an SSG5 tunnel at RENCI.  If the cable running to eth0 loses network connectivity, then hopefully the head node would still be able to speak to RENCI via the SSG5 link. +| A3QE  |4GB (1x4GB, 1Rx4, 1.35V) PC3L-12800 CL11 ECC DDR3 1600MHz LP RDIMM|8| 
- +| 6311  |2.8m10A/100-250V, C13 to IEC 320-C14 Rack Power Cable| 
-=== Example RHEL/CentOS ifcfg-device scripts === +| A3VE  |Intel Xeon Processor E5-2640 v2 8C 2.0GHz 20MB Cache1600MHz 95W| 
-<code> +| A2ZQ  |Mellanox ConnectX-3 EN Dual-port SFP+ 10GbE Adapter|2| 
-# Used for Public +| A1JU  |x3650 M4 PCIe Gen-III Riser Card 2 (1 x8 FH/FL + 2 x8 FH/HL Slots)| 
-#/etc/sysconfig/network-scripts/ifcfg-bond0 +| A2HR  |Configuration ID 03| 
-DEVICE="bond0" +| 3222  |Rack location U22| 
-BOOTPROTO="none" +| 5374CM1|Configuration Instruction| 
-ONBOOT="yes" +| A2N2  |ServeRAID M5110e SAS/SATA Controller for IBM System x| 
-NETWORK="X.X.X.0+| A2L4  |ServeRAID M5100 Series 1GB Flash/RAID 5 Upgrade Placement| 
-NETMASK="255.255.255.0" +| A2JX  |Controller 01| 
-BROADCAST="X.X.X.255" +| A2HR  |Configuration ID 03|
-IPADDR=&quot;X.X.X.Y"+
-BONDING_OPTS="mode=balance-alb miimon=25" +
- +
-# Used for iSCSI storage network +
-#/etc/sysconfig/network-scripts/ifcfg-bond1 +
-DEVICE="bond1" +
-BOOTPROTO="none" +
-ONBOOT="yes" +
-NETWORK="10.102.0.0+
-NETMASK="255.255.255.0" +
-BROADCAST="10.102.0.255" +
-IPADDR="10.102.0.1" +
-BONDING_OPTS="mode=802.3ad miimon=25 xmit_hash_policy=layer3+4 lacp_rate=1" +
- +
-# Omnibus Bond aggregates four 1Gbps interfaceswith VLAN tagging +
-#/etc/sysconfig/network-scripts/ifcfg-bond2 +
-DEVICE="bond2" +
-BOOTPROTO="none" +
-ONBOOT="yes" +
-BONDING_OPTS="mode=802.3ad miimon=25 xmit_hash_policy=layer3+4 lacp_rate=0" +
- +
-#/etc/sysconfig/network-scripts/ifcfg-bond2:1 +
-DEVICE=nova +
-BOOTPROTO=none +
-ONBOOT=yes +
- +
-# VLAN used for communication with Worker Node Linux OSes +
-#/etc/sysconfig/network-scripts/ifcfg-bond2.1007 +
-DEVICE="bond2.1007" +
-VLAN="yes" +
-BOOTPROTO="none" +
-ONBOOT="yes" +
-NETWORK="10.100.0.0" +
-NETMASK="255.255.255.0" +
-BROADCAST="10.100.0.255" +
-IPADDR="10.100.0.1" +
-USERCTL="no" +
- +
-# VLAN used for bare metal nodes +
-#/etc/sysconfig/network-scripts/ifcfg-bond2.1008 +
-DEVICE="bond2.1008" +
-VLAN="yes" +
-BOOTPROTO="none" +
-ONBOOT="yes" +
-NETWORK="10.101.0.0" +
-NETMASK="255.255.255.0" +
-BROADCAST="10.101.0.255" +
-IPADDR="10.101.0.1" +
-USERCTL="no" +
- +
-# VLAN used for management network: access to IBM Integrated Management Module (IMM)switch access +
-#/etc/sysconfig/network-scripts/ifcfg-bond2.1006 +
-DEVICE="bond2.1006" +
-VLAN="yes" +
-BOOTPROTO="none" +
-ONBOOT="yes" +
-NETWORK="192.168.102.0" +
-NETMASK="255.255.255.0" +
-BROADCAST="192.168.102.255" +
-IPADDR="192.168.102.10" +
-USERCTL="no" +
- +
-#/etc/sysconfig/network-scripts/ifcfg-eth0 +
-DEVICE="eth0" +
-BOOTPROTO="static" +
-HWADDR="5C:F3:FC:FF:FF:FF" +
-IPV6INIT="no" +
-MTU="1500" +
-NM_CONTROLLED="no" +
-ONBOOT="yes" +
-TYPE="Ethernet" +
-MASTER="bond0" +
-SLAVE="yes" +
- +
-#/etc/sysconfig/network-scripts/ifcfg-eth1 +
-DEVICE="eth1" +
-HWADDR="5C:F3:FC:FF:FF:FF" +
-BOOTPROTO="static" +
-IPV6INIT="no" +
-MTU="1500" +
-NM_CONTROLLED="no" +
-ONBOOT="yes" +
-TYPE="Ethernet" +
-MASTER="bond1" +
-SLAVE="yes" +
- +
-#/etc/sysconfig/network-scripts/ifcfg-eth2 +
-DEVICE="eth2" +
-HWADDR="5C:F3:FC:FF:FF:FF" +
-BOOTPROTO="static" +
-IPV6INIT="no" +
-MTU="1500" +
-NM_CONTROLLED="no" +
-ONBOOT="yes" +
-TYPE="Ethernet" +
-MASTER="bond2" +
-SLAVE="yes" +
- +
-#/etc/sysconfig/network-scripts/ifcfg-eth3 +
-DEVICE="eth3" +
-HWADDR="5C:F3:FC:FF:FF:FF" +
-BOOTPROTO="static" +
-IPV6INIT="no" +
-MTU="1500" +
-NM_CONTROLLED="no" +
-ONBOOT="yes" +
-TYPE="Ethernet" +
-MASTER="bond2" +
-SLAVE="yes" +
- +
- +
-#/etc/sysconfig/network-scripts/ifcfg-eth4 +
-DEVICE="eth4" +
-BOOTPROTO="static" +
-HWADDR="00:10:18:FF:FF:FF" +
-IPV6INIT="no" +
-MTU="1500" +
-NM_CONTROLLED="no" +
-ONBOOT="yes" +
-TYPE="Ethernet" +
-MASTER="bond0" +
-SLAVE="yes" +
- +
- +
-#/etc/sysconfig/network-scripts/ifcfg-eth5 +
-DEVICE="eth5" +
-HWADDR="00:10:18:FF:FF:FF" +
-BOOTPROTO="static" +
-IPV6INIT="no" +
-MTU="1500" +
-NM_CONTROLLED="no" +
-ONBOOT="yes" +
-TYPE="Ethernet" +
-MASTER="bond1" +
-SLAVE="yes" +
- +
-#/etc/sysconfig/network-scripts/ifcfg-eth6 +
-DEVICE="eth6" +
-HWADDR="00:10:18:FF:FF:FF" +
-BOOTPROTO="static" +
-IPV6INIT="no" +
-MTU="1500" +
-NM_CONTROLLED="no" +
-ONBOOT="yes" +
-TYPE="Ethernet" +
-MASTER="bond2" +
-SLAVE="yes" +
- +
- +
-#/etc/sysconfig/network-scripts/ifcfg-eth7 +
-DEVICE="eth7" +
-HWADDR="00:10:18:FF:FF:FF" +
-BOOTPROTO="static" +
-IPV6INIT="no" +
-MTU="1500" +
-NM_CONTROLLED="no" +
-ONBOOT="yes" +
-TYPE="Ethernet" +
-MASTER="bond2" +
-SLAVE="yes" +
- +
- +
-#/etc/sysconfig/network-scripts/ifcfg-lo +
-DEVICE=lo +
-IPADDR=127.0.0.1 +
-NETMASK=255.0.0.0 +
-NETWORK=127.0.0.0 +
-# If you're having problems with gated making 127.0.0.0/8 a martian, +
-# you can change this to something else (255.255.255.255, for example) +
-BROADCAST=127.255.255.255 +
-ONBOOT=yes +
-NAME=loopback +
-</code> +
-  * MAC addresses in this example are all fake +
-  * See also, [[public:network:vlans ExoGENI VLANs ]]+
Navigation
Print/export