 |
» |
|
|
|
|  | |
Before attempting this procedure, familiarize yourself with
the system reconfiguration information in the mk_kernel(1M) manual reference page and HP-UX system literature. Refer to the System Administration manual for your system
for complete instructions on how to create a kernel. The steps below
contain a general outline of kernel configuration steps with detailed
information for the LAN/9000 drivers and parameter settings contained
within that framework. If the kernel was not created with the LAN driver in it during
the swinstall procedure, you can create it manually. To determine
whether the LAN driver is in the kernel, check the /stand/system file for the lanX keyword (where X=2 or 3). To determine whether the LAN driver is installed,
execute what /stand/vmunix and check for references to LAN in the output. If you used some other file to create the kernel previously,
copy that file to /stand/system before following the steps below. Ensure that you have super-user capabilities. Change to the /stand directory. Make a backup copy of your current configuration
description file (which is commonly system or build/system.SAM). Edit the system file to add drivers and/or change system parameters. Verify or add the appropriate keywords: Table 3-1 Fm Variable:Table ContinuationSoftware driver names Driver
Keyword | HP 9000
Systems |
|---|
| btlan | HSC and PCI 100BT adapters on SuperDome,
A, L, N and rp54xx servers | | btlan0 | EISA 100BT adapters on D-Class
and Workstations (only supported on HP-UX 11i 32-bit, and not on 64-bit) | | btlan1 | HP-PB 100BT adapters on K & T-Class
systems | lan2, lan3 | Core
Built-in 10/100BT card | gelan | Gigabit Ethernet add-on
adapters on A, L, N, Superdome, Workstations, rp7410 and rp8400. | gelan | Core IO 10/100/1000 card on rp8400 | igelan | Next Generation Core IO 10/100/1000 card
on rp7410 |
If the keyword does not exist in the /stand/system file, add the appropriate lines to the file. Depending on which filesets you have loaded, you
may also need to add the following keywords to the system file: Table 3-2 Title not available (Creating a New Kernel for HP 9000 Systems) Keyword | Comments |
|---|
hpstreams | required
for streams | dlpi | required | uipc | required
for TCP/IP | inet | required
for TCP/IP | | nms | required for TCP/IP | nfs_core | | | nfs_client | | | nfs_server | | netdiag1 | | | tun | required for PPP |
Make a copy of the existing kernel (default name vmunix). Regenerate the kernel with mk_kernel, using the edited system file as input. mk_kernel creates the new hp-ux kernel (the default is /stand/build/vmunix_test). In this example a new kernel is created in the build directory
called vmunix_test. mk_kernel -s /stand/system -o /stand/vmunix |
This second example automatically moves the kernel to the /stand directory and makes a backup (/stand/vmunix_prev) if the file /stand/vmunix already exists. If you did not use the -o option with the mk_kernel command, copy the new kernel to /stand/vmunix. If you have additional LAN adapters to add to your
system, follow the appropriate directions; otherwise skip to step
9 below. Reboot on the new kernel. If the new kernel fails
to boot, boot the system from the backup kernel and repeat the process
of creating a new kernel. To do so, follow the instructions in your
System Administration manual. Proceed to the section "Verifying LAN Device
Files," in this chapter to continue configuring LAN/9000
manually. To configure your system with the SAM utility, proceed
to chapter 2, "Configuring LAN/9000 Using SAM."
|
Printable version
