Changes between Version 38 and Version 39 of Installation/Nodes


Ignore:
Timestamp:
May 20, 2013 4:42:36 PM (12 years ago)
Author:
jhickey
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Installation/Nodes

    v38 v39  
    232232The testbed nodes should be set to boot only off of the network.  Disable hard drive boot to prevent failed PXE requests from falling through to booting whatever is on the disk.
    233233
     234
     235
    234236== Node Types ==
     237
     238=== Determining the disk type ===
     239
     240It is important to know what sort of disks your new nodes have.  FreeBSD differentiates between SATA and SAS drives by using the device types ad and da, respectively.  Also, with older machines, the first ATA disk unit number may be 4.  You will need to know what disk type and unit number you are dealing with before attempting to create a node type.  It is easiest to probably boot a node to a FreeBSD live USB key and run "''geom disk list''':
     241
     242{{{
     243$ geom disk list
     244Geom name: cd0
     245Providers:
     2461. Name: cd0
     247   Mediasize: 0 (0B)
     248   Sectorsize: 2048
     249   Mode: r0w0e0
     250   descr: NECVMWar VMware IDE CDR10
     251   ident: (null)
     252   fwsectors: 0
     253   fwheads: 0
     254
     255Geom name: da0
     256Providers:
     2571. Name: da0
     258   Mediasize: 85899345920 (80G)
     259   Sectorsize: 512
     260   Mode: r2w2e3
     261   descr: VMware Virtual disk
     262   ident: (null)
     263   fwsectors: 63
     264   fwheads: 255
     265}}}
     266
     267So for this example, our type is '''da''' and our unit is 0.
     268
     269=== Determining the control network interface ===
     270
     271Before creating a node type, you should know which interface is the control network interface on your node.  Typically it is the first interface on the system, but sometimes it isn't.  You can double check that you have the correct interface by watching a node boot into the "freebsd.newnode" MFS.  During the boot, dhcp requests will be sent out of all interfaces in order to determine the control network interface.  You can also log into the MFS as root and run '''ifconfig -a''' to see which interface is configured.  When new nodes check in, you can also verify that the wiring detected matches which port your control network interface is wired to.
     272
     273=== Creating the type ===
    235274
    236275You will have to create a new "Node Type" for each class of node you wish to add to your testbed.