Related Manuals for NETEX NESiGate-CO
Summary of Contents for NETEX NESiGate-CO
- Page 1 NESiGate-CO NetEx/IP Offload Channel-to-IP Gateway Release 2.10 Reference Manual MAN-REF-COSW 2.10-19...
- Page 2 Updated for Red Hat 7.2 distribution and miscellaneous corrections and addi- tions. • 05 (Apr 2002) Added documentation for new initialization parameters. • Added documentation for additional NetEx operator commands. 06 (xxx 2002) Added documentation for Hitachi IBM-compatible configuration require- ments. 07 (Oct 2002) Added documentation for NG_CO service...
-
Page 3: Table Of Contents
IP Address ............................4 Using a Web Browser to Configure NESiGate ..................5 Define the Channel Boards(s) ......................5 Define the Devices ..........................5 Configure NetEx/IP..........................5 GNA to IP Mapping ........................... 6 Reboot NESiGate ..........................7 Web Browser Interface..........................9 Overview ..............................9 Browser Considerations ........................ - Page 4 Modify NetEx Startup Parms .......................18 NetEx Eat/Gen Test........................18 Appendix A: Configuration Worksheet ....................19 Appendix B: NetEx Default Parameters....................21 Appendix C: NetEx/IP Messages ......................29 Viewing NetEx/IP Messages......................29 Using the Web Browser Interface ....................29 Using the Command Line Interface....................29 Messages: ............................30 Appendix D.
-
Page 5: Copyrights And Trademarks
Copyrights and Trademarks This document contains references to the trademarks of the following corporations. Corporation Trademarks International Business Machines ESCON® Unisys Corporation SBCON Red Hat, Inc. RedHat® Note: RedHat® is a registered trademark of Red Hat, Inc. This product is not a product of Red Hat, Inc. -
Page 6: Notice To The Customer
Always include the complete title of the document with your comments. Information on Network Executive Software’s general software support policy (e.g., alternate contact methods, support severity level descriptions, and service status definitions) may be found at http://www.netex.com/support/software-support-policy. - Page 7 MAN-REF-COSW 2.10-19 Page...
-
Page 8: Introduction
Introduction The purpose of this manual is to provide an overview of the procedures used to integrate and customize the NetEx/IP components onto a NESiGate channel offload platform, and to provide a description of the command and web browser interfaces. - Page 9 Page 2 Introduction MAN-REF-COSW 2.10-19...
-
Page 10: Customization
This section is targeted to the end-user responsible for customizing a NESiGate appliance for use as a NetEx/IP offload channel device. It is assumed the NESiGate already has the appropriate level of the system software installed. To complete the customization, the reader must be familiar with channel de- vice and network addressing concepts. -
Page 11: Gna Address
GNA address. This enables NESiGate to perform a direct mapping be- tween GNA and IP addresses. This mapping is transparent to the NetEx/IP running on the host, as well as to all NetEx/IP applications. -
Page 12: Using A Web Browser To Configure Nesigate
The NCT can be created on any network-attached host and placed in a file named ‘<nesigate>.nct’ where <nesigate> is the configured hostname of the NESiGate being configured. Refer to the “Configuration Manager and NetEx Alternate Path Retry (APR) User Guide” [MAN- CNET-CONF-MGR] manual for a description of the NCT parameters. -
Page 13: Gna To Ip Mapping
NCT relative to a particular host. To build a PAM, use the web browser interface, on the Netex webpage under the “(buildPam) for Ne- tex Host” section and select the hostname for which you are creating the pamfile. -
Page 14: Reboot Nesigate
Reboot NESiGate After the configuration changes have been made, the NESiGate unit must be rebooted to make the changes effective: • Vary the devices offline to the host operating system. • Navigate to the “System Config” webpage of the NESiGate •... - Page 15 Page 8 Customization MAN-REF-COSW 2.10-19...
-
Page 16: Web Browser Interface
Web Browser Interface Overview NESiGate provides a web-enabled configuration facility. Connecting NESiGate to an intranet infrastruc- ture enables usage of a web browser to configure and manage the NESiGate CO. Refer to the common NESiGate Installation Manual for descriptions of all the common web pages. Browser Considerations The browser can be hosted on any system, as long as that system has network connectivity to the NESi- Gate. -
Page 17: Nesigate Board/Channel Commands
NESiGate Board/Channel Commands This webpage is used to define, display and monitor the channel interface and devices with respect to the NESiGate CO. Conflicts and illogical configurations may be accepted as input (to the web or CLI), however that does NOT mean they will work (i.e. - Page 18 CU (escon only) OS-genned Control Unit Address (must be 0 for Unisys) CHlink (escon only) Escon director host-side port#; or for direct connect: 1 (IBM), 2 (Unisys old SBCON), 77 (Unisys SCIOP/SIOP SBCON) LPAR (escon only) Logical Partition # (IBM) MAN-REF-COSW 2.10-19 Web Browser Interface Page...
-
Page 19: Show Channel Config
Show Channel Config This shows the currently defined and currently loaded ESCON subchannel ranges and their index val- ues. Prior to selecting this button, provide the following data on the selection screen: IFname the name of the channel interface to display. If IFname is not specified, all defined channel interfaces are displayed. -
Page 20: Show Channel Info
Show Channel Info This displays detailed channel interface information. Prior to selecting this button, provide the following data on the selection screen: IFname The name of the channel interface to display. If not specified, all defined chan- nel interfaces are displayed. Device# Limit the display of the channel interface to a particular device. - Page 21 Show Stats [ x3650 - Thu Jun 3 15:52:48 ] txpacks txbytes rxpacks rxbytes txMiscEr ------------ -------- ------------ -------- ------------ -------- if5e00:1 rxMiscEr haltIO streamTo sysReset selReset cmdRej intvReq -------- -------- -------- -------- -------- -------- -------- busOutCk equipCk dataCk overRun delayTx delayRx dataTo WO...
-
Page 22: Channel Define Interface
Channel Define Interface This defines a channel interface, which consists of a range of devices for use by a particular NetEx/IP. Note: a channel board must be installed before defining any channel interfaces. Prior to selecting this button, provide the following data on the selection screen: IFname a name by which the interface will be identified. -
Page 23: Remove Channel Interface
Caution: It is extremely important that the values specified for UADD, CU, CHlink, and LPAR exactly match the values specified in the host system’s device configuration. Failure to do so will make the devices unusable. The total number of devices supported on each ESCON interface board is 64. Use this selection button multiple times until all required device interfaces are defined. -
Page 24: Netex Webpage
Display the current Netex log file, the loaded NCT or PAM file. Netex Show Detailed Commands Display all or specific host, session, transport or network. buildPam Build a PAM for the specified host. the host must match the local (host) in the Netex Default file. Set Netex Parm MAN-REF-COSW 2.10-19... -
Page 25: Modify Netex Startup Parms
Certain NetEx parameters must agree with NCT-configured values for proper initialization. These can be changed by using the buttons in the “Configure Netex Default” section. Select the parameter to change in the first dropdown menu, enter the desired value in the window next to it, select “configure default value”... -
Page 26: Appendix A: Configuration Worksheet
Appendix A: Configuration Worksheet This worksheet can be used to record the necessary NESiGate configuration information. (Minimum recommended configuration is listed here.) The corresponding web configuration panel is identified in parentheses. HOST & IP Information (System Configuration) Example Site Configuration Host &... - Page 27 OS device information (Used for OS Definitions) Example Site Configuration Device number (or name) 5200 Number of devices Director port (device director port) Control unit number (or name) Unit address LPAR number Channel board Information (Used for NESiGate board definitions) Example Site Configuration Board name...
-
Page 28: Appendix B: Netex Default Parameters
Appendix B: NetEx Default Parameters This section contains a description of the default parameters used by NetEx. Only a few of these can be changed via the user interfaces. Refer to the web pages to see which parameters can be altered. All oth- ers will require direction from NESi Support personnel. - Page 29 If not specified, Ne- tEx/IP defaults to the built-in table. ackcredit This is the number of buffers that NetEx/IP sends without returning an explicit ack. Note: More buffers may be in the process of being sent. Increasing this value has little effect on system load and may decrease Ne- tEx/IP throughput.
- Page 30 This is the number of reads that NetEx/IP has outstanding to the DRIVER. This value may need to be increased, if many very small transfers are needed.
- Page 31 NetEx/IP session establishment messages to be recorded in the ‘ntxlog’ file. multihost When set ON, allows Netex to distinguish between SOFFERs of the same application name from multiple locally attached hosts (LAN or channel). Set to OFF if there is only one attached host or if all SOFFERs will have unique names.
- Page 32 The following parameters are only applicable to protocol type 4 connections: defstartkbitspersec This is the starting throughput rate at which NetEx/IP will attempt to deliver data to the network for each network connection. If zero is specified, data will be delivered with no internal throttling.
- Page 33 5000000 This is the high threshold value (in bytes) for the size of the receiving NetEx DataQue for each network connection. If the size of the Data Queue exceeds this value, subsequent blocks received on the network that are great- er than the highest received LRN are NAK'ed and discarded.
- Page 34 UDP-6950-ddnnuuss This is the name of the NetEx/IP device. The “ddnn” must be specified as either ‘0000’ or ‘0101’; “uuss” represents the unit number and subaddress portions of the GNA address of this device. The “uu” value must be the same as the “netaddr”...
- Page 35 NetEx/IP Parameter Default Description device2 This is the name of a second NetEx/IP device, and is only used if there is a second NIC card. device3 This is the name of a third NetEx/IP device, and is only used if there is a third NIC card.
-
Page 36: Appendix C: Netex/Ip Messages
Each message is prefixed with a date and timestamp of the following format: Sun Jan 27 01:03:52 2008 Viewing NetEx/IP Messages NetEx/IP messages are recorded in the ‘ntxlog’ file. There are two ways to view this file: 1) Using the NetEx/IP Web Browser Interface 2) Using the Command Line Interface (CLI) Using the Web Browser Interface To view the ‘ntxlog’... -
Page 37: Messages
Messages: ISOFFR nref n uname : offering pname at hname, t secs Description: An OFFER has been issued by the NetEx/IP application that is running under the user name ‘uname’. identifies the internal NetEx/IP session reference number uname identifies the user name under which the NetEx/IP application is running. - Page 38 User Response: None. ISCLOS nref n uname : closing Description: A CLOSE has been issued by the NetEx/IP application that is running under the user name ‘uname’. identifies the internal NetEx/IP session reference number of the local application. uname identifies the user name under which the NetEx/IP application is running.
- Page 39 FINISHSESSION nref n : nrbreq = rr, nrbstat = ssss, nrbind = i Description: A NetEx connection is terminated, due to the reason indicated in the message. identifies the internal NetEx/IP session reference number of the local application. identifies the NetEx/IP request type.
- Page 40 NETEX: network protocol error n Description: A netex network protocol error has been detected. The specific error is identified by “n” Attempt to reroute non-offering side Attempt to confirm to offerer Actual data shorter than specified in protocol D-read failed...
- Page 41 None. Netex reports the invalid message and continues. Message received with no read active Description: A Netex message was received on the network, but there was no Netex ‘read’ request ac- tive at the time. Message is dropped. User Response: None.
- Page 42 0xn Description: An unknown Netex request was received by the NESiGate-CO application. xx,yyy -- identifies the NESiGate-CO process -- n identifies the unknown request type User Response: None. Netex reports the condition and continues. emsg(xx,yyyy): abort ind received, disconnecting Description: An abort indicator was received by the NESiGate-CO application.
- Page 43 Description: A selective reset was received on the channel - identifies the NESiGate-CO channel interface name - identifies the NESiGate-CO subchannel device User Response: None. Netex reports the condition and continues. chnlMailHandler(stream nnnnnnnn(xx)): data timeout, subch=nn Description: A data timeout has occurred on the indicated subchannel device.
-
Page 44: Appendix D. Nrb Status Error Codes
The following errors are general NETEX errors. 0001 A read type operation completed normally within NETEX, but the Pdata buffer provided by the user was not large enough to hold the data. NRBLEN and NRBUBIT reflect the amount of data the other party intended to send. However, the amount of data moved to the user’s program was only the amount of addressable units specified in NRBBUFL. -
Page 45: Session Errors
0500* NETEX is not currently running on the local computer. Intervention by the local computer operator will be required to start NETEX. This code is issued by the NETEX user interface when it is determined that NETEX is unavailable. 0503* An OFFER, CONNECT, or ASSIGN request has resulted in the number of connections outstanding for the caller exceeding an implementation defined maximum. - Page 46 The request is rejected. The status of the connections remains unchanged. 3302 A connect indication was received by a preceding SOFFER, and a request other than SCON- FIRM or SDISCONNECT was issued. The request is rejected. NETEX will continue to wait for the confirm or disconnect request. 3303 An SCONNECT request was previously issued, then a request other than an SREAD or SDISCONNECT was issued.
- Page 47 NETEX was DRAINed when a connect was received. This error is returned by the Session Manager to the connector. 3550* The local host specified on an SOFFER or SCONNECT does not exist in the NETEX Ad- ministrator’s NCT. The request is rejected at the Administrator. 3552* The local host specified on an SOFFER or SCONNECT request in not in the NETEX Admin- istrator’s domain.
-
Page 48: Appendix E: Nesigate Sense Bytes
Appendix E: NESiGate Sense Bytes NESiGate ESCON Table 1. NESiGate ESCON Sense Bytes defines the sense bytes that are returned from the NESiGate ESCON interface board. Sense Bytes …… ….. X’80’ – Command Reject …… X’80’ – Data Timeout ….. X’2A’... - Page 49 Page 42 Appendix E MAN-REF-COSW 2.10-19...