FILE NAME: vlan-1.8.0u-1.src.rpm TITLE: HP Tested and Approved Linux 802.1q VLAN Driver VERSION: 1.8.0u-1 LANGUAGE: English CATEGORY: Software Solutions DIVISIONS: Enterprise and Mainstream Servers PRODUCTS AFFECTED: HP NC325m Quad Port PCIe Gigabit Server Adapter (bcm5700) HP NC326m Dual Port PCIe Gigabit Server Adapter (bcm5700) HP NC340T PCI-X Quad-port Gigabit Server Adapter (e1000) HP NC370x Gigabit Server Adapter (bnx2) HP NC371x Gigabit Server Adapter (bnx2) HP NC373x Gigabit Server Adapter (bnx2) HP NC374x Gigabit Server Adapter (bnx2) HP NC380x Gigabit Server Adapter (bnx2) HP NC67xx Gigabit Server Adapter (bcm5700) HP NC77xx Gigabit Server Adapter (bcm5700) HP NC324i Integrated Dual Port PCI Express Gigabit Server Adapter (bcm5700) HP NC325i Integrated Dual Port PCI Express Gigabit Server Adapter (bcm5700) HP NC326i Integrated Dual Port PCI Express Gigabit Server Adapter (bcm5700) HP NC150T PCI 4-Port Gigabit Combo Switch Adapter (bcm5700) HP NC320x PCI Express Gigabit Server Adapter (bcm5700) HP NC1020 Fast Ethernet Adapter (bcm5700) HP NC31xx Fast Ethernet Adapter (e100) HP NC340T PCI-X Quad-port Gigabit Server Adapter (e1000) HP NC310F PCI-X Gigabit Server Adapter (e1000) HP NC61xx Gigabit Server Adapter (e1000) HP NC71xx Gigabit Server Adapter (e1000) OPERATING SYSTEM: Red Hat Enterprise Linux 3 for AMD64/EM64T Red Hat Enterprise Linux 3 for x86 SUSE LINUX Enterprise Server 9 for AMD64/EM64T SUSE LINUX Enterprise Server 9 for x86 NOTE: The vlan driver distributed on the Red Hat Enterprise Linux 4 (and later) media is supported. This package (vlan-1.8.0s-14.src.rpm) will not build correctly on this distribution. To install the script and configuration files of vlan on Red Hat Enterprise Linux 4, use the latest vlan_init package. vlan_init package can be downloaded from: http://h18004.www1.hp.com/support/files/server/us/index.html by selecting the Linux distribution and version in the operating system drop down menu and selecting "Driver - Network" from the category drop down menu. PREREQUISITES: Pentium-based computer 256MB RAM minimum Latest HP system ROM bcm5700 driver version 8.3.17a e100 driver version 3.4.14a e1000 driver version 6.2.19b bnx2 driver version 1.4.36c NOTE: Visit the following URL to upgrade the ROM http://h18000.www1.hp.com/support/files (select ProLiant from the server column) EFFECTIVE DATE: 05/22/2006 SUPERSEDES: vlan-1.8.0t-14.src.rpm DESCRIPTION: This RPM contains the vlan driver, which allows you to use virtual LANs with ProLiant NICs running under Linux. ENHANCEMENTS/FIXES: - Tested on latest distributions Table of Contents ================= Introduction Packaging Kernel Source Code Setup Installing the RPM Package VLAN Configuration Driver Messages Statistics Limitations Uninstalling the RPM Package Introduction ============ This package provides a driver module which implements the 802.1q VLAN implementation and the vconfig utility used to configure VLANs. After installation,additional information can be found in the manual page for vconfig, and in the vlan.txt file located at: For Red Hat: /usr/share/doc/vlan-1.8.0u/vlan.txt For SLES 9: /usr/share/doc/packages/vlan/vlan.txt The References section in vlan.txt provides many useful articles on VLANs and possible configurations of VLANs. 8021q.o is the module name in the 2.4 kernel and 8021q.ko is the module name in the 2.6 kernel. Packaging ========= The driver is released in source RPM format. The file name for the package is vlan-.src.rpm and is dependent on the kernel source code. Kernel Source Code Setup ======================== The Linux VLAN driver requires the presence of the kernel source code and configuring the kernel source before building the VLAN driver. The following steps need to be done once for each kernel that is booted. For example, if the current kernel is UP (uni-processor) and an SMP (symmetrical-multi-processor) kernel is booted, these steps must be performed again to configure the kernel source for SMP before building the VLAN driver for the SMP kernel. Red Hat installation: If the /usr/src/linux- directory does not exist install the kernel source code per Red Hat instructions. Once installed, follow the commands listed below to configure the kernel source to match the running kernel. # cd /usr/src/linux- # make mrproper # make -e KERNELRELEASE=`uname -r` oldconfig # make -e KERNELRELEASE=`uname -r` dep SLES 9 Installation: If the /usr/src/linux- directory does not exist, install the kernel source code per SUSE instructions. Once installed, follow the commands listed below to set up the kernel source tree. # cd /usr/src/linux- # make mrproper # make cloneconfig # make dep Installing the RPM Package ============================= 1. Check for the existence of a current version of the vlan package as follows: # rpm -q vlan If an old version of the package exists the RPM package should be removed. # rpm -e vlan Then remove the loaded vlan module. # rmmod Verify that the old vlan package has been removed as follows: # rpm -q vlan 2. Install the RPM source package. # rpm -ivh vlan-.src.rpm 3. Change to the following directory and build the binary RPM for the VLAN driver. Red Hat Installations: # cd /usr/src/redhat # rpmbuild -bb SPECS/vlan.spec SLES 9 Installations: # cd /usr/src/packages # rpmbuild -bb SPECS/vlan.spec NOTE: If an error is encountered while building the driver or this directory does not exist, refer to the "Kernel Source Code Setup" section of this document. 4. Install the new binary RPM package using the following command. Do not use the U (Upgrade) flag in the RPM command below - previous vlan drivers must be removed as described in step one above before installing this version. NOTE: To Preserve the current VLAN configuration ( if applicable ), the user is advised to backup the /etc/vlan.conf file before installing the new package and restore the file after the installation finishes. Refer to the section on "Startup Scripts & VLAN Automation" section in vlan.txt for more details. # rpm -ivh RPMS/i386/vlan-.i386.rpm --force The "force" rpm option is required since the VLAN driver is part of the kernel rpm. 4. The vlan driver is installed in the /lib/modules//kernel/net/8021q directory. VLAN Configuration ================== The VLAN driver can be configured either as a stand-alone adapter or with a team of adapters using the Bonding driver. Refer to the "VLAN Configuration (stand-alone adapters)" section in vlan.txt for details on how to setup VLANs with stand alone adapters. Refer to the "VLAN configuration (teamed with Bonding driver)" section in vlan.txt for details on how to setup VLANs in a teamed environment using the Bonding driver. Driver Messages =============== The following messages will appear on the console when the 8021q.o module loads: 802.1Q VLAN Support V1.8 Ben Greear (greear@candelatech.com) If the user attempts to configure VLANs without loading the module, the following messages will appear on the console after which the module will automatically get loaded. WARNING: could not open /proc/net/vlan/config. Maybe you need to load the 8021q module, or you are not using PROCFS 802.1Q VLAN Support V1.8 Ben Greear (greear@candelatech.com) set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config Note: When driver is loaded in SLES9, following message are logged in /var/log/messages: "8021q: unsupported module, tainting kernel" These messages are normal and can be ignored. Statistics ========== Refer to "Verification of VLAN Configuration" in vlan.txt for detailed information regarding statistics and configuration information of VLANs. Limitations =========== If jumbo frames are used, the network interface (ethX) must have an MTU equal to the largest MTU of the VLANs on that interface. The VLAN driver does not automatically increase the MTU of the underlying network interface. The "Limitations" Section of vlan.txt provides information on the current limitations and some possible configuration changes that can be done to avoid some limitations. Uninstalling the RPM Package ============================ The following command will uninstall the vlan RPM. # rpm -e vlan Copyright 2002, 2003, 2004 Hewlett-Packard Development Company, L.P. Product names mentioned herein may be trademarks and/or registered trademarks of their respective companies