08/28/96, Block Multiplexer Diagnostic Hints SPECIAL NOTICES Information in this document is correct to the best of our knowledge at the time of this writing. Please send feedback by fax to "AIXServ Information" at (512) 823-4009. Please use this information with care. IBM will not be responsible for damages of any kind resulting from its use. The use of this information is the sole responsibility of the customer and depends on the customer's ability to eval- uate and integrate this information into the customer's operational environment. +----------------------------------------------------------+ | | | NOTE: The information in this document has NOT been | | verified for AIX 4.1. | | | +----------------------------------------------------------+ BLOCK MULTIPLEXER DIAGNOSTIC HINTS ABOUT THIS DOCUMENT This document is intended to help you diagnose common prob- lems that may occur with the Block Multiplexer. Please read through this document and verify items 1-5 before contacting the defect support center for assistance. PROCEDURE NOTE: There is a subset of Block Multiplexer PTFs that are needed for proper configuration. The minimum requirements are U415742, U414756, U417775, U413617, U406215, U406223. These or their supercedes can be found in the 3.2.4/PMP upgrade with the blkmux subsystem. These need to be ordered and installed before you proceed. 1. Issue the following command: lslpp -h blkmux.obj If the release level shows 01.01.0000.0000, call 1-800-879-2755 for a new release of blkmux. 2. Before you can configure Block Multiplexer Channel Adapter Services, you must configure the RISC System/6000 blkmux adapter and interface, vary the channel on, and start TCP/IP. The following steps do these things and assume that IOCPGEN has already been done on the mainframe. a. To configure the blkmux adapter, enter "smit chgcat" and change the following: Block Multiplexer Diagnostic Hints 1 08/28/96, Channel SPEED (must match on mainframe) STARTING subchannel address (IOCP Definition on mainframe) NUMBER of subchannel addresses (IOCP Definition on mainframe) CLAW Mode Host NAME (must match DEVICE statement in tcpip.profile--case sensitive) Adapter NAME (must match DEVICE statement in tcpip.profile--case sensitive) subchannel set (even subchannel for Claw set, last two numbers in DEVICE statement in tcpip.profile.) b. To configure the blkmux interface, enter "smit chinet" and change the following: INTERNET ADDRESS (dotted decimal) DESTINATION Address (dotted decimal) Subchannel Address (even subchannel for CLAW set) Current STATE (change to up) c. To vary on the mainframe subchannel, enter: VARY [device address], ONLINE (MVS command) VARY ON [device address] (VM command) d. To verify subchannel status, enter: D U ,,,[device address],[range of addresses] (MVS command) status should be 'O' QUERY [device address] (VM command) e. To configure TCP/IP on the mainframe, set the fol- lowing minimum requirements in tcpip.profile: DEVICE [devicename] CLAW [channel-subchannel] \ [Host NAME] [Adapter NAME] NONE [read_buffers] \ [write_buffers] [read_size] [write_size] LINK [hostname] IP 0 [devicename] HOME [ip address] [hostname] GATEWAY [network] = [hostname] [packet size(mtu on RS/6000)] \ [subn mask] START [devicename] f. Start TCP/IP on the mainframe and watch for errors. If the system is an MVS system, verify with the "D U" command: primary subchannel 'A' and 'BSY' secondary subchannel 'A' If the system is a VM system, verify subchannel "A" with the QUERY command. Block Multiplexer Diagnostic Hints 2 08/28/96, 3. Verify connectivity by entering the following on the RISC System/6000: ping -c1 [host ip address] 4. Common Problems. 1. If you have problems while configuring the adapter: o Verify that the switch on the cable is set to "S" instead of "B" o Verify that the status is "Available" with the "lsdev -Cc adapter" command. The output will look similar to the following: cat0 Available 00-01 370 Parallel Channel Adapter If the state is "Defined" instead of "Available", then reseat the card and reboot. If the state is still "Defined", verify that the microcode is on the machine ("lslpp -h p370.mc"), and run hardware diagnostics. 2. If you have problems while configuring the interface: o Before you change anything, verify that the inter- face in the "DOWN" state. 3. If you have problems with varying on the channel on the mainframe, causes could be: o IOCPGEN was done improperly o The RISC System/6000 has an incorrect channel/subchannel configuration o RISC System/6000 is not online 4. If you have problems with bringing up TCP/IP on the mainframe: o Verify the mtu size on the RISC System/6000 matched packet o Verify that the channel/subchannel on the RISC System/6000 adapter configuration matches with DEVICE statement on the mainframe. o Verify the hostname and adapter name on the RISC System/6000 adapter configuration match with the DEVICE statement on the mainframe. 5. If you have problems with pinging the mainframe, the cause may be: o If the error is "network unavailable", then the channel is not configured properly and needs to be reconfigured. 6. Also note: Block Multiplexer Diagnostic Hints 3 08/28/96, o The RISC System/6000 must be configured, online, and up before mainframe channels can be brought on line. Prior to rebooting the RISC System/6000, detach the blkmux interface (i.e., "ifconfig caX detach" where X is the number of the interface). This will allow the RISC System/6000 to recycle without requiring changes on the mainframe side. o Do NOT try to verify blkmux configuration on the RISC System/6000 side by attempting to "ping" the local interface. This will not work. Block Multiplexer Diagnostic Hints 4 08/28/96, READER'S COMMENTS Please fax this form to (512) 823-4009, attention "AIXServ Informa- tion". You may also e-mail comments to: elizabet@austin.ibm.com. These comments should include the same customer information requested below. Use this form to tell us what you think about this document. If you have found errors in it, or if you want to express your opinion about it (such as organization, subject matter, appearance) or make sug- gestions for improvement, this is the form to use. If you need technical assistance, contact your local branch office, point of sale, or 1-800-CALL-AIX (for information about support offer- ings). These services may be billable. Faxes on a variety of sub- jects may be ordered free of charge from 1-800-IBM-4FAX. Outside the U.S. call 415-855-4329 using a fax machine phone. When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any way it believes appropriate without incurring any obligation to you. NOTE: If you have a problem report or item number, supplying that number may help us determine why a procedure did or did not work in your specific situation. Problem Report or Item #: Branch Office or Customer #: Be sure to print your name and fax number below if you would like a reply: Name: Fax Number: ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ END OF DOCUMENT (blkmux.tcp,) Block Multiplexer Diagnostic Hints 5