|
|
United States-English | |
|
|
 |
|
HP-UX 11i March 2002 Release Notes: HP-UX Servers and Workstations > Chapter 5 I/0 and Networking Cards
Network Drivers |
|
|
new at 11i |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |
| |
| |
 | IMPORTANT: Although there you will see no impact in most cases, you will if you have scripts that refer specifically to btlan3, btlan4, btlan5 or btlan6. |
| |
| |
| |
You will need to use the new driver name btlan with the following commands:
what string
For example: what /stand/vmunix | grep btlan
ioscan
For example: ioscan -kfC lan | grep btlan
You will also see the driver name btlan as the output in:
the system file /stand/system
nettlgen.conf and in the file /var/admin/sw/nettl.LOG00
The following files have changed to include the new btlan driver name (most involve just name changes):
kernel library is now called /usr/conf/libbtlan.a
nettl formatter/catalog files (no change except instead of btlan3, btlan4, btlan5, btlan, or btlan6, it will just refer to btlan)
debug/q4
lanscan/lanadmin support libraries/catalog files now have names to reflect btlan such as libdsbtlan.a, dsbtlan.cat, etc.
master file
init scripts/conf file
The init script will be hpbtlan and the configuration file will be called hpbtlanconf.
The configuration files under /etc/rc.config.d/ will be replaced by hpbtlanconf. When a cold install is performed, this file will be installed for all btlan driver claimed cards. If, however, an upgrade is done, you can choose to merge the files using pre-update scripts. If you do not elect to merge during an upgrade, then the files will, by default, be saved as .obsolete files which can be later merged manually into the hpbtlanconf file.
The drivers of all of the following networking, I/O, and mass storage cards are now pre-installed with (or built into) each of the HP-UX 11i Operating Environments:
PCI 10/100Base-TX card A3738A will be discontinued starting February 1, 2002
PCI 4-port 10/100Base-TX card A5506A has been replaced by A5506B
Core 1000Base-T/SCSI card A6794A for HP server rp7410
PCI Tachyon XL2 Fibre Channel card A6795A
PCI 1000Base-T (gigabit over copper) card A4929A
PCI 1000Base-SX (gigabit over fiber) card A4926A
PCI Combination Dual port 10/100Base-TX and Wide Ultra2 SCSI card A5838A
PCI 4-port 10/100Base-TX cards A5506A and A5506B
PCI 10/100Base-TX card A3738A
PCI core 10/100Base-TX card for workstations and servers
PCI 10/100Base-TX card A5230A for servers
PCI 10/100Base-TX card B5509BA for workstations
PCI Tachyon TL Fibre Channel card A5158A
PCI FDDI card A3739B
PCI RAID 4Si controller A5856A
HSC 10/100Base-TX card J3514A opt #001 2-port for K-Class servers
HSC 10/100Base-FX (fiber) card J3514A opt #002 2-port for K-Class servers
HSC 10/100Base-TX card J3515A 1-port for workstations and D-Class servers
HSC 10/100Base-TX card J3516A opt #001 2-port for workstations and D-Class servers
HSC 10/100Base-FX (fiber) card J3516A opt #002 2-port for workstations and D-class servers
HSC 10/100Base-TX card J3850A for T-Class server
HSC 1000Base-SX (gigabit over fiber) cards A4924A, A4925A
HSC Tachlite Fibre Channel cards A6684A, A6685A
Instructions for configuring built-in (or core) 100Base and 1000Base PCI cards can be found in Appendix C of the HP-UX 11i Installation and Update Guide.
In HP-UX 11i, the drivers for PCI and HSC-based Fast Ethernet networking are consolidated into one driver called btlan, which is pre-installed as part of the kernel. The configuration files used by these networking drivers in HP-UX 10.20 and 11.0—hpbtlanconf (btlan), hpbase100conf (btlan3), hpgsc100conf (btlan4), hppci100conf (btlan5) and hpsppci100conf (btlan6), which are in the /etc/rc.config.d directory—are merged into one file.
| |
| |
| |
| IMPORTANT: The configuration files used by the PCI and HSC-based
Fast Ethernet networking drivers must be combined, either by use
of a script or manually, into one configuration file before upgrading
to HP-UX 11i. Merging must be done before updating because the interface used to recognize the host might be PCI or HSC-based Fast Ethernet. One of these interfaces could have been configured in a pre-update configuration file, which would have to be maintained for the update to proceed (the link-up is needed during product configuration). |
| |
| |
| |
When you run the pre-update script BTLAN.100,the configuration files used by the PCI and HSC-based Fast Ethernet networking drivers are merged into one file called hpbtlanconf.
Once the BTLAN.100 script creates the merged configuration file, it is placed temporarily in the /var/adm/sw/save_custom/UNIFIED_MER directory, and the original configuration files are saved with the extension .obsolete. During the consolidated btlan driver installation, the merged configuration file is then moved to the /etc/rc.config.d directory as hpbtlanconf.
Note that the BTLAN.100 script will only merge the driver-specific configuration files if the corresponding hardware is present on the system, and if the files have at least one LAN interface configured. (For example, if the system had the HSC-based Fast Ethernet networking driver [btlan4] and corresponding hardware [HSC cards], then the hpgsc100conf configuration file should have at least one card configured in it.)
If the update process is abandoned because of preupdate script failures (other than syntax errors in configuration files or a duplicate LAN interface error), then the configuration files have to be merged manually. Once this has been done, you can then continue the update process. (Once the update process is restarted, the user should answer NO (N) at the prompt, Do you want to proceed in merging the configuration files into one? [Y|N].)
Find out which of the five configuration files listed below exists in the /etc/rc.config.d directory.
hpbtlanconf (btlan)
hpbase100conf (btlan3)
hpgsc100conf (btlan4)
hppci100conf (btlan5)
hpsppci100conf (btlan6)
For each of the files found in Step 1, use the command ioscan -kfC lan to find out if corresponding hardware is present.
Driver Name: File Name
btlan -- hpbtlanconf
btlan3 -- hpbase100conf
btlan4 -- hpgsc100conf
btlan5 -- hppci100conf
btlan6 -- hpsppci100conf
If hardware is present, check to see if any LAN interface is configured. For example, the configuration for hpbtlanconf (btlan) would show as follows:
HP_BTLAN_INTERFACE_NAME[0]=lan1
HP_BTLAN_STATION_ADDRESS[0]=0x080009C4686E
HP_BTLAN_SPEED[0]=100HD
Create the file hpbtlanconf.merge in the directory /etc/rc.config.d as shown below:
########################################################################### |
(#) hpbtlanconf |
# hpbtlanconf: contains config values for HP PCI/HSC 100Base-T interfaces |
# |
# HP_BTLAN_INTERFACE_NAME Name of interface (lan0, lan1, . . .) |
# HP_BTLAN_STATION ADDRESS Station address of interface |
# HP_BTLAN_SPEED Speed and duplex mode |
# |
# The interface name, major number, card instance and ppa may be |
# obtained from the lanscan (1m) command. |
# The station address and speed are set through the lanadmin command. |
########################################################################### |
HP_BTLAN_INTERFACE_NAME[0]= |
HP_BTLAN_STATION ADDRESS[0]= |
HP_BTLAN_SPEED[0]= |
########################################################################### |
# The HP_BTLAN_INIT_ARGS are reserved by HP. they are NOT user changeable. |
########################################################################### |
HP_BTLAN_INIT_ARGS="HP_BTLAN_STATION ADDRESS HP_BTLAN_SPEED" |
# End of hpbtlanconf configuration file |
As described in steps a, b, and c below, merge every LAN interface (as shown to be configured in Step 2) into the file hpbtlanconf in the /var/adm/sw/save_custom/UNIFIED_MER directory.
First, note that a set of three parameters is required for each LAN interface:
HP_BTLAN_INTERFACE_NAME,
HP_BTLAN_STATION_ADDRESS and
HP_BTLAN_SPEED.
Second, note that the index value used for the set of three parameters should be unique for each interface. For example:
HP_BTLAN_INTERFACE_NAME[0]=lan1
HP_BTLAN_STATION_ADDRESS[0]=0x080009C4686E
HP_BTLAN_SPEED[0]=100HD
HP_BTLAN_INTERFACE_NAME[1]=lan2
HP_BTLAN_STATION_ADDRESS[1]=0x080009C4B23C
HP_BTLAN_SPEED[1]=FULL
Finally, merge all LAN interfaces by creating a set of three parameters with a unique index for each:
Copy the value of the interface name into the parameter HP_BTLAN_INTERFACE_NAME.
Copy the value of the station address into the parameter HP_BTLAN_STATION_ADDRESS.
If the SPEED parameter exists, and if its value (lowercase or uppercase) is 100FD or 100HD, 10FD or 10HD or auto_on, copy the value into the HP_BTLAN_SPEED parameter.
However, if the SPEED parameter does not exist, and the DUPLEX parameter has been set and its value (lowercase or uppercase) is FULL or HALF, copy the value to HP_BTLAN_SPEED parameter.
If neither the SPEED nor DUPLEX parameter values have not been set, do not put any value for the HP_BTLAN_SPEED parameter.
If the hpbtlanconf configuration file already exists (as /etc/rc.config.d/hpbtlanconf), copy it to /etc/rc.config.d/hplanconf.obsolete.
Move the file hpbtlanconf.merge to hpbtlanconf by using the command
|
|
|
Restart the update process. Answer NO (N) at the prompt, Do you want to proceed in merging the configuration file into one? [Y|N].
With the March 2002 release, the HP rp7410 server core 1000Base-T product is now supported. Customers should download the latest 11i release for the most recent version of Gigabit Ethernet.
The December 2001 release supports the core 1000Base-T/SCSI card (A6794A) for HP-UX 11i, to pre-enable future systems (64-bit only). (The driver, igelan, is available on software bundle GigEther-01.) The card is factory-installed, with a maximum of two cards. The card supports only MC/ServiceGuard in this release. Online files are located at /opt/networkdocs.
The PCI 1000Base-T card allows HP 9000s to connect to IEEE 802.3ab standard networks over Cat 5 or Cat 5E UTP copper cable. (The driver, gelan, is available on software bundle GigEther-00.) The card supports HP Auto-Port Aggregation, MC/ServiceGuard, and LAN Monitor. The card operates at 10, 100, or 1000 Mbit/s and supports auto-negotiation and auto-sensing. There is no 1000Base-T card for HSC backplanes.
The HSC and PCI 1000Base-SX/9000 products provide the means for interfacing various types of HP 9000 computers to a 1000Base-SX multimode fiber network.
It is recommended that your system have at least 128 megabytes of memory when using this product.
The PCI Gigabit Ethernet cards are for use on:
V2200, V2250, V2500, V2600, L1000, L2000, A180, N4000, and rp7400 servers running the HP-UX 11i operating system, and
B-, C-, and J-Class workstations running the HP-UX 10.20, 11.0, and HP-UX 11i operating systems.
| |
| |
| |
 | NOTE: For information on doing online addition and replacement of Gigabit Ethernet cards, refer to "Managing PCI Cards with OLAR" in the Configuring HP-UX for Peripherals manual. |
| |
| |
| |
The HSC card is for use on D-, K-, and R-Class servers running HP-UX 10.20, 11.0 and HP-UX 11i, with the following exceptions:
The A4925A HSC 1000Base-SX card is not supported on D210, D220, D230, D310, D320, and D330 systems.
The A4925A card is supported on the D250, D260, D270, D280, D350, D360, D370, D380, D390, R380, and R390 systems.
Please check with your HP representative for a definitive list of HSC card-supported systems.
The Gigabit Ethernet LAN software is for use with only the following protocols: TCP/IP, ARPA, and NFS
The HSC and PCI 1000Base-SX/9000 cards operate only at 1000 Mbps. They do not interoperate with 100Base-FX cards.
The PCI 1000Base-T card operates at 10, 100, or 1000 Mbps. Only full-duplex mode is supported at 1000 Mbps. The PCI 1000Base-T card and link partner (for example, a switch) must be set to autonegotiation to run at 1000Mbps.
If using Jumbo Ethernet frames, ensure that all switches in the data path support the Jumbo frame size and that both ends of the connection support Jumbo frames. The 1000Base-T card supports Jumbo frames only at 1000 Mbps.
On A180, B132, B132L, B160, B160L, B180, and B180L platforms running HP-UX 10.20, only one Gigabit Ethernet adapter is supported. (HP-UX 11.0 on these workstations supports multiple adapters.)
MC/ServiceGuard is not supported on A-180 servers running HP-UX 10.20.
For detailed information on advanced features and troubleshooting of the Gigabit Ethernet products, see Using PCI 1000Base-T and HSC/PCI 1000Base-SX (Gigabit Ethernet) available on the Instant Information CD or under “Networking and Communications” at http://docs.hp.com.
For information on installing and configuring the Gigabit Ethernet products, see PCI 1000Base-T and HSC/PCI 1000Base-SX/9000 Quick Installation available in the /opt/networkdocs directory and at http://docs.hp.com.
The following release notes are also located in the /opt/networkdocs directory:
gigether_relno.pdf
gigether-01_relno.pdf
Now available is the new 2Gb, single port Fibre Channel Host Bus Adapter. The A6795A PCI Tachyon XL2 adapter operates at bus speeds of up to 66 MHz with 64 bits bus width and can transfer data at a 1Gb or 2Gb transfer rate. The adapter has auto-speed negotiation that enables it to negotiate for the highest speed (1Gb or 2Gb) that is common to the port and to the infrastructure connecting the port. Using the fcmsutil diagnostic tool, you can display link speed and Vital Product Data (VPD) information programmed on the adapter.
The A6795A adapter operates on the following platforms running HP-UX 11.00, 11i, or later Operating Environments:
A400, A500, L-class, N-class, and Superdome servers
J6000 workstations
The A6795A adapter will support all of the fabric topologies currently supported by the existing Tachlite adapter. Boot support for the first release will be only on the N- and L-class systems.
As of December 2001, the HP-UX 11i Fibre Channel driver version is B.11.11.09. Although this driver is pre-installed with each of the HP-UX Operating Environments, you can also obtain it from the December 2001 application release CD. The Fibre Channel 11i driver is a common driver for the following Fibre Channel Host Bus Adapters:
A5158A PCI 1Gb Tachyon TL adapter
A6684A HSC Tachlite adapter
A6685A HSC Tachlite adapter
A6795A PCI 2Gb Tachyon XL2 adapter
HP has created a new Fibre Channel Storage Network Industry Association (SNIA) Host Bus Adapter (HBA) Application Programming Interface (API). The SNIA HBA API is a C library interface that provides both a common HBA API library for all HP-UX HBA vendors and a vendor-specific API library for HP's Tachyon/Tachlite Fibre Channel adapters. The API software is part of the driver and is installed at the same time. The intended users of this API are programmers who want to create applications for managing SANs networks.
As of December 2001, you can use the HSC Tachlite adapters (A6684A and A6685A) on the following additional platforms:
D320
D330
D220
D230
The HSC Tachlite adapters (A6684A and A6685A) will also support boot on K260, K360, K460, D390, R390, K370, K570, and K580.
Changes have also been made to the Fibre Channel online diagnostic tool, fcmsutil, to support the A6795A adapter. When you use the command, fcmsutil/dev/tdx (where x is the number assigned to the adapter), the following additional information will display:
Link Speed (1Gb or 2Gb)
Dino Present on Card
Maximum Frame Size
Driver Version
By using the command, fcmsutil/dev/tdx vpd, you can display Vital Product Data (VPD) information on the adapter. This information includes the following:
Product description
Part number
Engineering date code
Part serial number
Miscellaneous information
Manufacturing date
Check sum
EFI version
Asset Tag
Effective December 2001, the following documents (available at http://www.docs.hp.com) have changed or have been added:
Hewlett-Packard Fibre Channel Mass Storage Adapters Manual
HP Fib re Channel Fabric Migration Guide
HP FC SNIA HBA API Programmer's Guide (new)
fcmsutil(1M) manpage
The Tachlite driver enables the HSC Tachlite adapters (A6684A and A6685A), used in the K-, R- and D-Class servers, to have the same fabric capabilities as the PCI Tachlite adapter.
For a current list of driver versions, go to the ITRC web site, http://itrc.hp.com. Click navigate knowledge trees and response center FAQs. After logging in (if necessary), scroll to the Hardware area and navigate the links to networks/mass storage connectivity/fibre channel/technical support. Once you are on the Fibre Channel page, select the Tachlite driver table in the “at a glance” box.
Boot support for the A6685A and A6685A HSC adapters on selected platforms will be available later in 2001. For the latest information on boot support for these adapters and other support information, see the web site mentioned above.
This version of the driver continues to support the following features:
Fabric zoning and cascading
Fabric boot and dump for supported platforms (PCI A5158A only)
Supported configurations
Arbitrated private loop
Direct fabric attachment
QuickLoop (translative mode)
Public Loop
For more information on supported Fabric topologies, see the HP Fibre Channel Fabric Migration Guide located at http://docs.hp.com.
The following documents have been revised:
HP Fibre Channel Fabric Migration Guide
HP Fibre Channel Mass Storage Adapters Manual
fcmsutil(1M) man page
HP RAID 4Si (A5856A) combines multiple small, inexpensive disks into an array that appears as a single logical unit or drive. The data is distributed across the disks in order to provide a method for data recovery or reconstruction in the event of a drive failure.
A new firmware version (U.01.06) for the RAID 4Si controller is available as a patch from the HP IT Resource Center (ITRC), at http://itrc.hp.com. This version supersedes the version (U.01.04) that is currently shipping with the HP RAID 4Si software.
As always we strongly recommend that you upgrade to the latest firmware at your convenience.
Boot support (new feature)
Ability to boot over the RAID controller.
The customer can install the OS onto the logical drives configured on the RAID controller.
There is an option now in Ignite-UX called "Configure A5856A" which brings up the configuration tool called IRM that helps in configuring logical drives.
OLA/R (new feature)
Ability to perform Online Addition/Replacement of the RAID controller.
The customer can do an OLA/R of the RAID controller using SAM or the rad command.
New firmware revision (U.01.04) of the RAID controller includes the following new features and fixes since earlier released version (U.01.01)
Provides support for disk firmware download.
Provides capability to handle NVRAM vs. Disk mismatch on replaced boot cards.
Provides fix for a problem which causes logical drives to become unavailable when a reconstruction is started from IRM (for example, when changing RAID levels).
Provides fix for I/O hang due to cache deadlock.
Provides fix for the problem of HOTSPARE sometimes not rebuilding when the disk that is part of the logical drive is pulled out.
The firmware image a5856a_01_04.img is present in the /opt/raid4Si/firmware directory on the system on which you install the RAID software. A help text file, a5856a_u_01_04.txt, for installing the image is available in the same directory.
Diagnostic improvements
You can now make use of the new -v option of the irdiag command. Also, you can use the irdfd command to perform disk firmware downloads and the irconcheck command to perform consistency checks.
For more information see the HP A5856A RAID 4Si PCI 4-Channel Ultra2 SCSI Controller Installation and Administration Guide at http://docs.hp.com and the following manpages:
irdfd(1M) (new)
irconcheck(1M ) (new)
irdisplay(1M) (revised)
irmd(1M) (revised)
irdiag(1M) (revised)
irm(1M)
i2outil(1M)
HyperFabric is a high-speed network link that runs on various HP 9000 servers and workstations. HyperFabric supports the IP network protocol stack, including TCP/IP, UDP/IP, and NFS.
The A6386A HyperFabric2 PCI fiber adapter is now supported on HP-UX 11i on these HP 9000 systems:
A400, A500, L-, N-, V-Class, Superdome, and rp8400 systems
B1000, B2000, B2600, C3000, C3600, C3700, J5000, J5600, J6000, J6700, and J7000 workstations
The clic_ping command is replaced by the clic_probe command
HP-UX 11i includes code that enhances the HSC FDDI driver. These driver modifications increase performance of the FDDI link by up to 20%.
The performance enhancement was done by making the driver MBLK-based, whereas previously it was MBUF-based. Other code-path and function-call reductions have further improved performance and scalability. These changes are not directly visible to the user and have no effect on current documentation or support.
 Printable version |
|
|
|
|
|
|||||||||||||||
|
|||||||||||||||
