| 271 | | Before 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. |
| | 271 | Before 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. Here is an example of a machine with 6 interfaces. It turns out that the unit for the control network is 4 instead of 0. |
| | 272 | |
| | 273 | {{{ |
| | 274 | Emulab looking for control net among: igb0 igb1 igb2 igb3 igb4 igb5 ... |
| | 275 | igb5: link state changed to UP |
| | 276 | igb3: link state changed to UP |
| | 277 | igb2: link state changed to UP |
| | 278 | igb0: link state changed to UP |
| | 279 | igb4: link state changed to UP |
| | 280 | Terminated |
| | 281 | Emulab control net is igb4 |
| | 282 | }}} |
| | 283 | |
| | 284 | 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. |
