Manuals / Brands / Computer Equipment / Switch / HP / Computer Equipment / Switch

HP 12076A LAN/1000 LINK Installation Summary, 5.Boot the system, 6.Verify successful driver and Node Manager installation

1 156

Download 156 pages, 564.61 Kb

Installation Summary

Interface driver ID*67 is a software I/O driver provided by Hewlett"Packard to interface the RTE"A Operating System with a LANIC card. The ID*67 driver manages communications across the host I/O backplane to and from the LANIC card. It formats system I/O requests, and accesses the LANIC to complete each request. For proper node operation, the driver must be installed in the host computer system.

The driver and associated Node Management software can support up to eight (8) LANIC cards per host computer, each card with a unique station address.

The size of the driver allows it to fit into a two"page partition.

To install the driver into the host, a new operating system must be generated and installed. For details on generating and installing a new system, along with general information for incorporating drivers, refer to your RTE"A generation manuals: RTEA System Design Manual, part number 92077"90013, and RTEA System Generation and Installation Manual, part number 92077"90034.

Information relating to the installation of the LANIC driver ID*67 and associated Node Management software is summarized below and discussed further in the remainder of this chapter.

1.Identify the driver and Node Management software modules provided. Transfer them, along with other operating system modules, to a disk"based system used for system generation.

2.To generate a target system, a new •answer" file must be created. This can be done by editing an existing one. Entries for incorporating driver ID*67 into a driver partition, and generating an Interface Table (IFT) and a Device Table (DVT) for each card installed in the host must be made.

The program RTAGN is run with the new answer file specified in the runstring. This results in the creation of new system and snapshot files for the target system.

3.Link the Node Manager programs using the LAN8023.CMD command file.4.Initalize the driver and Node Manager software in the Welcome file.5.Boot the system.6.Verify successful driver and Node Manager installation.

3%2 Software Installation

Contents

HP 12076A LAN/1000 Link Node Manager's Manual NOTICE Printing History Page Preface Purpose Assumptions Related Reading Organization Table of Contents 3"6 3"7 3"8 3"9 Node Manager Operations 5"5 5"6 5"7 Group I: Commands Not Containing the FileAddress Parameter 5"8 5"58 LANVCP Operations 6"1 6"2 6"4 List of Illustrations Tables Page Introduction Identification Installation System Requirements Page Software System Memory LANVCP Operation Node Manager Software Services Configuration Services Statistical Services Diagnostic Services Event Logging Services Implementation Considerations Designating Nodes General Information Open Systems Interconnection Model Note IEEE 802 Service Types Transmission Frames Format Preamble Start Frame Delimiter Destination Address where: CA = Card Address bits comprising the lower six hex digits Globally Administered Address Locally Administered Address Individual node address Source Address Length Protocol Data Unit Page Page Control Page Information Poll bit (for commands) or Final bit (for responses) as previously defined bit values establish the Logical Link Control services provided, Type and/or Type bits are reserved and are set to •0 bits are for Receive Window Size defined for Type 2 services Pad Frame Check Sequence Page Software Installation Installation Summary Modules Provided Answer File Entries Table Generation Example 31. Sample Table Generation Entries for Two LANIC Cards Installed (An asterisk •*" denotes a comment line) sc1, lu1 are Card 1's select code (in Octal), and logical unit number sc2, lu2 Linking Node Manager Software Using LAN8023.CMD Driver and Node Manager Initialization Verifying the System Page Node Manager Operations Node Manager Modules Command Processing Command Entry Errors Command Execution Errors Files and Directories MCAST.TXT Page EL.TXT Driver Interface Driver's Class Table Packet Routing Saving Orphan Packets RAM & NOVRAM Driver's Copy Node Manager Software Initialization Page Finding Link File Directories Entering User Commands Initialization Errors Post Initialization Packet Filter Addressing Modes Page Multiple LANIC Cards Using Node Manager Parameter Notation Getting Started Exiting the Node Manager Software Using the Help Facility NM Using the Command Stack Command Entry Timeout Error Messages Command Execution Node Manager Commands Group I: Commands Not Containing the FileAddress Parameter Group II: Commands Containing the FileAddress Parameter Retrieving the ADR Parameter Configuration Commands Read Link Configuration Command (RC) Multicast Address Considerations Page RC Command Examples Page Page Page Set Link Configuration Command (SC) Page Station Address Considerations Download Server Station Address Considerations File Server Station Address Considerations Packet Filter Mode Considerations SC Command Examples Update Link Configuration Command (UC) Page UC Command Example Insert Multicast Address Command (IM) IM Command Examples Delete Multicast Address Command (DM) DM Command Examples Create Link File Directories Command (CD) CD Command Example Purge Link File Directories Command (PD) PD Command Example CK Command Examples Diagnostic Commands The Rep Parameter 1.Press any key, resulting in the Command Monitor system program prompt (CM>) 2.Set the break flag for the NM module, as follows: LANIC Self%Test Command (TC) The syntax for this command is: This is the •target" Station Address of the node whose LANIC card undergoes TC Command Examples Page Do External Loopback to MAU Command (EL) EL Command Examples Example 2. External Loopback Test Failure Issue TEST Loopback Command (TEST) This is the •target" Station Address of the node to which the TEST command See Table 5"1 for default addresses process, on the ADR node, for which the IEEE 802.2 TEST command packet is directed, and from which an IEEE 802.2 TEST response packet is desired. This DSAP Considerations Self%Addressed TEST Packets Errors TEST Command Examples Example 2. Incorrect MSGLEN Parameter MSGLEN Rep Example 4. Self"Addressed TEST Commands XID Command (XID) process (on the ADR node) for which the IEEE 802.2 XID command packet is directed and from which the XID response packet is desired. This parameter is required and entered as a two"digit hexadecimal number set (see •The Rep Parameter" discussed earlier in this chapter) Self%Addressed XID Packets XID Command Examples Event Log Commands Read Event Log File Command (RE) RE[,FileAddress] where TIME DATE List Facility RE Command Examples Example 3. Bad Packet Entry in Event Log File Example 4. Trace Packet Entry in Event Log File Statistics Commands Page Statistics Description Page Read Link Statistics Counters Command (RS) This is the Logical Unit number of the LANIC card through which the command is local LANIC card. See Table 5"1 for default values RS Command Example ZS Command Example LANVCP Operations Memory%Based System, LAN, and VCP Hardware and Software Requirements IPL_BUILD and IPL_EDIT - Configuration Files Page Examples Format of IPL_TABLE.TXT Selecting the System File to Download DISPATCH - Monitoring LAN Packets VCPMT Monitor RMVCP - Remote VCP /BREAK /EXIT /HELP /READ /WAIT Examples RMVCP Memory Dump Session RMVCP enter number of byte pages of Downloading Over a LAN Link Page Error Codes & Descriptions NMGR Error Codes Driver Error Codes LANVCP Error Codes -14:Unexpected_session received message in error, type: <VCP message type VCPMT initialization was unable to open the error printer file (LU 1) -17:Interactive session received message in error, type: <VCP message type -19:Error in reading download file, FMP error: <FMP error -23:Memory dump failed on LAN address <address NM Command Summary Page Page Page IEEE 802 Family Relationships Page Record of Changes Page Index