Archive
FreeBSD + Dell 12G + X520-DA2 10G NIC
Intel 82599 based NICs on Dell 12G Servers w/ FreeBSD?
Dell offers the X520-DA2 10G Fiber NIC based on the Intel 82599 chipset for it’s 12G line of servers. It seems that there were two batches of this NIC manufactured. One batch was Dell branded, the other Intel branded.
According to this post, the FreeBSD source appears to be missing PCI ID’s etc that would enable the Dell branded card to work under FreeBSD on it’s 12G servers resulting in the card not being recognized by the OS. Inspection of dmesg shows that there is an ethernet card with no driver attached.
This is currently being corrected in HEAD, but for the time being swapping in an Intel branded equivalent which is seen by FreeBSD without a problem is sufficient. Unfortunately, the Dell BIOS does not recognize the card. having said that, the card is recognized in the OS and does work using the ixgbe(4) driver. The interface name begins with “ix”.
Using screen to connect to serial ports
Using screen to connect to serial ports
screen is cool. screen is an indespencable tool to any unix administrator. My challenge was to find a solution to connect to the serial port on a server chassis. The solution I found was to utilize a USB-Serial adapter (and associated Mac OS X Lion Driver), null modem cable, and rj45-db9 adapter in conjunction with screen.
screen, being a key tool in an administrator’s tool box, was found to have the capability of connecting to serial ports!
To connect to the serial port:
screen /dev/tty.PL2303-000013FD
Specifying baud rate:
screen /dev/tty.PL2303-000013FD 9600
Enabling CTS/RTS:
screen /dev/tty.PL2303-000013FD 9600,ctsrts
Terminate the session using screen command ^a,k
Notes
FreeBSD on HP Proliant DL360p G8 Servers
The Problem
Our provisioning platform utilizes a traditional PXE method with Linux and FreeBSD integrated. On my first attempt to PXE boot and install FreeBSD, the kernel panic’d when the network interface was brought up within sysinstall.
Turns out that the neither the BCM5719 nor BCM5720 ethernet controllers are fully supported in FreeBSD 8-STABLE as of this writing. However, the FreeBSD community is currently working on resolving this.
The Hardware
We were testing FreeBSD 8-STABLE (as of 21 May 2012) on the following configuration:
HP Proliant DL360p G8 w/ Smart Array i420 RAID Controller
128GB RAM
Eight (8) 2.5″ 300GB SAS HDD
The Resolution
FreeBSD also supports the HP NC361T/Intel i350T2, both based on the Intel i350 controller. The downside with using a PCIe NIC is that a slot is removed as an expansion option.
FreeBSD’s Package Index
Interpreting the package INDEX
Author: Devin Teske
Date: 1 Jan 2006
Last modified: 24 Feb 2006
Purpose
This file documents the file format of the /packages/INDEX file located on FreeBSD installation CD-ROMs and conveys what it is used for (and its importance).
The layout of this document is as follows:
- Foreword
- The INDEX File
- The FreeBSD INDEX File Format
- FreeBSD-5.2 and FreeBSD-4.10 or Lower
- FreeBSD-5.3 and FreeBSD-4.11 or Higher
- FreeBSD-6.0 or Higher
- Field Definitions
- Field Population
- References
Foreword
Common between each version, is that each line (delimited by the new-line character) corresponds to a single package (found in packages/All). It is possible to have additional fields beyond the last field (for custom purposes) as they will be ignored by sysinstall.
The INDEX File
If sysinstall is scripted, then the interactive menu may or may not be invoked (if not, then the categories/description fields may be omitted).
When sysinstall is in the process of installing the packages, it first makes sure that all the run-dependencies (listed in the INDEX file for that package) are installed. If a package that is listed in the `run-deps’ field is not installed, sysinstall installs it before installing the requested package. After installing any dependent packages (recursively), sysinstall then unpacks the requested package and reads its packing-list (the `+CONTENTS’ file within the package tarball). All package dependencies listed inside the package’s packing-list MUST be installed before-hand or else sysinstall will generate an error. Therefore, all package dependencies that appear in the packing list MUST be present in the `run-deps’ field of the INDEX file. There reverse is not true, however. A dependency may appear in the INDEX file and not in the package’s packing-list.
INDEX File Format
FreeBSD-5.2 and FreeBSD-4.10 or Lower
package|port-origin|install-prefix|comment|port-desc-file|maintainer|categories|build-deps|run-deps|www-site
FreeBSD-5.3 and FreeBSD-4.11 or Higher
package|port-origin|install-prefix|comment|port-desc-file|maintainer|categories|build-deps|run-deps|www-site|unknown|unknown|unknown
I have never seen the 11th, 12th, or 13th field populated. So their purpose remains unknown.
FreeBSD-6.0 or Higher
package|port-origin|install-prefix|comment|port-desc-file|maintainer|categories|build-deps|run-deps|www-site|unknown|unknown|unknown|disc
Field Definitions
| Field | Comments |
| package | This is the name of the package. This should be the name of the file as it appears in packages/All without the .tgz suffix. This value is used for finding the package tarball and is also displayed in the left-hand column of the interactive package selection menu of sysinstall. |
| port-origin | The package origin (as a qualified pathname). Basically, this is the origin of the package with a /usr/ports/ prefix. Even if you do not install the Ports Collection (which installs Makefiles and other information), this should be populated respectively. |
| install-prefix | The base directory where the package will install it’s files to. For example, if the package installs files into /usr/local/bin and /usr/local/sbin then the install-prefix would be /usr/local. This is an informational value (the package’s packing-list takes precedence). |
| comment | This is the one-line comment for the package. This should be the same as the contents of the +COMMENT file located within the package tarball. This value is displayed in the right-hand column of the interactive package selection menu of sysinstall. |
| desc-file | When you install the Ports Collection the /usr/ports directory is populated with Makefiles and other information. This value should be the path to the description file for the package. This is only used when you install the FreeBSD Ports Collection. |
| maintainer | The e-mail address of the package maintainer. |
| categories | Within the /packages directory of the CD-ROM, you will find (besides the INDEX file) several directories. The actual package should always reside in theAll directory (as this is where sysinstall looks for it). However, finding the package you want/need can become quite cumbersome if you have to sift through every package in one directory. To ease the process of finding a specific package, you can populate this field with several categories (sub-directories) that the package can be found in.
When sysinstall’s interactive package selection menu is invoked (either by a script or simply interactively) it allows a user to browse several categories to find a specific package. This field dictates to sysinstall which categories (delimited by a space) the package is available in. When you specify a category (sub-directory), the simplest (and most efficient) thing to do is, create a symbolic link in the category directory (in /packages) pointing to the actual package (in /packages/All). |
| build-deps | These are the dependencies (names of packages delimited by a space) that this package requires to bebuilt. This is used if you install the FreeBSD Ports Collection. |
| run-deps | These are the dependencies (names of packages delimited by a space) that this package requires to run. Any package listed here will be installed by sysinstall before the package is even attempted to be installed. See section 2 paragraph 3 for more information. |
| www-site | Either the website URL of where the package can be obtained, the package maintainer, or the website URL of the item that the package installs. |
| unknown | If a field has been marked `unknown’ in section 3, it is because I have never seen it populated and thus never used. These fields can be left empty without any recourse. |
| disc | The disc that the package can be found on (in a multi-disc distribution of the FreeBSD installation). This is a new feature of FreeBSD-6.0 Other distributions (such as FreeBSD-4.8 and FreeBSD-4.11 do not list packages in the INDEX file unless it appears on the same CD-ROM). |
Field Population
- package: file_name without `.tgz’ suffix
- port-path: echo /usr/ports/`pkg_info -qo file`
- install-prefix: pkg_info -qp file | head -n1 | sed -e ‘s/^@cwd //’
- comment: pkg_info -qI file
- desc-file: echo /usr/ports/`pkg_info -qo file`/pkg-descr
- maintainer: echo ports@FreeBSD.org
- categories: find . -type l -name FILE | sed -e ‘s/^\.\/\(.*\)\/[^\/]*$/\1/’ | tr ‘\n’ ‘ ‘
- build-deps: pkg_info -qr file | sed -e ‘s/^@pkgdep //’ | tr ‘\n’ ‘ ‘
- run-deps: pkg_info -qr file | sed -e ‘s/^@pkgdep //’ | tr ‘\n’ ‘ ‘
- www-site: pkg_info -qd file | grep ‘^WWW: ‘ | sed -e ‘s/^WWW: //’
- disc: the disc that the package resides on
hostileadmin 