             '                    Hardware Information       D           __________________________________________________________E           14.10  What is the layout of the VAX floating point format?   D                    The VAX floating point format is derived from oneD                    of the PDP-11 FP formats, which helps explain itsH                    strange layout. There are four formats defined: F 32-H                    bit single-precision, D and G 64-bit double-precisionF                    and H 128-bit quadruple precision. For all formats,G                    the lowest addressed 16-bit "word" contains the sign_G                    and exponent (and for other than H, some of the mosttF                    significant fraction bits). Each successive higher-I                    addressed word contains the next 16 lesser-significant I                    fraction bits. Bit 15 of the first word is the sign, 1 G                    for negative, 0 for positive. Zero is represented by F                    a biased exponent value of zero and a sign of zero;D                    the fraction bits are ignored (but on Alpha, non-F                    zero fraction bits in a zero value cause an error.)F                    A value with biased exponent zero and sign bit 1 isG                    a "reserved operand" - touching it causes an error -nF                    fraction bits are ignored. There are no minus zero,8                    infinity, denormalized or NaN values.  F                    For all formats, the fraction is normalized and theJ                    radix point assumed to be to the left of the MSB, henceG                    the following range: 0.5 less than or equal to f andsI                    less than 1.0. The MSB, always being 1, is not stored. I                    The binary exponent is stored with a bias varying withrB                    type in bits 14:n of the lowest-addressed word.  E             FP      Exponent    Exponent    Mantissa (Fraction) bits, B             Type      Bits        Bias        including hidden bitF             ==========================================================6              F         8           128              246              D         8           128              566              G        11          1024              536              H        15         16384             113  I                    The layout for D is identical to that for F except for /                    32 additional fraction bits.s  H                    Example: +1.5 in F float is hex 000040C0 (fraction of7                    .11[base 2], biased exponent of 129)=                          14-40               '                    Hardware Information       D           __________________________________________________________>           14.11  Where can I find more info about VAX systems?  F                    o  HP provides limited VAX platform information viaH                       links at the AlphaServer website, itself available                       via:2                       http://www.hp.com/go/server/  G                    o  Jim Agnew maintains a MicroVAX/VAXstation FAQ at: I                       http://www.people.vcu.edu/~agnew/MVAX/MVAX_FAQ.HTML   8                    o  The VAXstation 3100 Owner's Guide:E                       http://www.whiteice.com/~williamwebb/intro/DOC-?                       i.html  C                    o  VAXstation 3520 and VAXstation 3540 (Firefox)k                       Manual:tC                       http://starfish.osfn.org/rcs/VAX/vs3540sg.pdfp  .                    o  VAX Console information:M                       http://www.mcmanis.com/chuck/computers/vaxen/panels.htm/  H                    o  A field guide to PDP-11 (and VAX) Q-bus and UNIBUS.                       modules can be found at:D                       http://metalab.unc.edu//pub/academic/computer-E                       science/history/pdp-11/hardware/field-guide.txt3  B                    o  Various VAX historical information (also see3                       Section 2.1) can be found at: ?                       http://telnet.hu/hamster/vax/e_index.html   D           __________________________________________________________H           14.12  Where can I find information on NetBSD for VAX systems?  A                    Gunnar Helliesen maintains a NetBSD VAX FAQ atl  .                    o  http://vaxine.bitcon.no/  D           __________________________________________________________@           14.13  What system disk size limit on the MicroVAX and!                  VAXstation 3100?n  G                    System disks larger than 1.073 gigabytes (GB)-1fffff J                    hexidecimal blocks - are not supported on any member ofJ                    the VAXstation 3100 series and on certain older membersD                    of the MicroVAX 3100 series, and are not reliableD                    on these affected systems. (See below to identify  J                                                                      14-41 e  m          '                    Hardware Information         F                    the affected systems-the more recent members of theB                    MicroVAX 3100 series systems are NOT affected.)  H                    Various of the SCSI commands used by the boot driversE                    imbedded in the console PROM on all members of the G                    VAXstation 3100 series use "Group 0" commands, whichnI                    allow a 21 bit block number field, which allows access H                    to the first 1fffff hexidecimal blocks of a disk. AnyF                    disk references past 1fffff will wrap-this wrappingI                    behaviour can be of particular interest when writing a F                    system crashdump file, as this can potentially leadD                    to system disk corruptions should any part of the=                    crashdump file be located beyond 1.073 GB.s  F                    More recent systems and console PROMs use "Group 1"J                    SCSI commands, which allow a 32 bit block number field.  E                    There was a similar limitation among the oldest ofrD                    the MicroVAX 3100 series, but a console boot PROMH                    was phased into production and was made available forJ                    field retrofits-this PROM upgrade allows the use of theI                    "Group 1" SCSI commands, and thus larger system disks. G                    There was no similar PROM upgrade for the VAXstation                     3100 series.   ;                    Systems that are affected by this limit:w  J                    o  VAXstation 3100 series, all members. No PROM upgrade#                       is available.   H                    o  MicroVAX 3100 models 10 and 20. No PROM upgrade is                        available.  I                    o  MicroVAX 3100 models 10e and 20e. Only systems withmH                       console VMB versions prior to V6.4 are affected. AH                       PROM upgrade for these specific systems is (or was&                       once) available.                      Also see   E                    o  http://www.whiteice.com/~williamwebb/intro/DOC-                        i.html  (                    Also see Section 9.5.                      14-42 s             '                    Hardware Information       D           __________________________________________________________8           14.14  What are the VAX processor (CPU) codes?                CPU:    Platform:              -----   ---------3              KA41-A : MicroVAX 3100 Model 10 and 20 4              KA41-B : VAXserver 3100 Model 10 and 20               KA41-C : InfoServer5              KA41-D : MicroVAX 3100 Model 10e and 20e 6              KA41-E : VAXserver 3100 Model 10e and 20e5              KA42-A : VAXstation 3100 Model 30 and 40o5              KA42-B : VAXstation 3100 Model 38 and 48_.              KA43-A : VAXstation 3100 Model 763              KA45   : MicroVAX 3100 Model 30 and 40 .              KA46   : VAXstation 4000 Model 60,              KA47   : MicroVAX 3100 Model 80)              KA48   : VAXstation 4000 VLCM2              KA49-A : VAXstation 4000 Model 90/90A.              KA49-B : VAXstation 4000 Model 95.              KA49-C : VAXstation 4000 Model 96,              KA50   : MicroVAX 3100 Model 90,              KA51   : MicroVAX 3100 Model 95(              KA52   : VAX 4000 Model 100(              KA53   : VAX 4000 Model 105(              KA54   : VAX 4000 Model 106,              KA55   : MicroVAX 3100 Model 85,              KA56   : MicroVAX 3100 Model 96(              KA57   : VAX 4000 Model 108,              KA58   : MicroVAX 3100 Model 88,              KA59   : MicroVAX 3100 Model 98              KA85   : VAX 8500              KA86   : VAX 8600              KA88   : VAX 88000              KA600  : VAX 4000-50 (aka VAXbrick)9              KA610  : MicroVAX I, VAXstation I (aka KD32) $              KA620  : rtVAX (VAXeln)"              KA62A  : VAX 6000-200"              KA62B  : VAX 6000-3000              KA630  : MicroVAX II, VAXstation II2              KA640  : MicroVAX 3300, MicroVAX 3400Q              KA650  : VAXstation 3200, MicroVAX 3500, MicroVAX 3600, MicroVAX III0"              KA64A  : VAX 6000-400A              KA655  : MicroVAX 3800, MicroVAX 3900, MicroVAX III+8"              KA65A  : VAX 6000-500  J                                                                      14-43               '                    Hardware Information         1              KA660  : VAX 4000-200, VAX 4 upgrade "              KA66A  : VAX 6000-600"              KA670  : VAX 4000-300"              KA675  : VAX 4000-400"              KA680  : VAX 4000-500#              KA681  : VAX 4000-500A "              KA690  : VAX 4000-600#              KA691  : VAX 4000-605AA#              KA692  : VAX 4000-700AK#              KA693  : VAX 4000-605A #              KA694  : VAX 4000-705A                KA730  : VAX-11/730               KA750  : VAX-11/750,              KA780  : VAX-11/780, VAX-11/782               KA785  : VAX-11/785"              KA7AA  : VAX 7000-600"              KA7AB  : VAX 7000-700"              KA7AC  : VAX 7000-800              KA800  : VAXrta(              KA820  : VAX 8200, VAX 8300(              KA825  : VAX 8250, VAX 8350              KA865  : VAX 8650  D           __________________________________________________________>           14.15  Where can I get software and hardware support                  information?   J                    Please contact the HP Customer Support Center. ServicesC                    and information, manuals, guides, downloads, and I                    various other information is available via the supportA                    link at:A  9                    o  http://www.hp.com/products/openvms/   I                    Various hardware and system documentation is available_                    at:  4                    o  http://www.hp.com/go/services/  I                    TSM (Terminal Server Manager), DEChub, DECserver, etc.h                    information:v  E                    o  http://www.compaq.com/support/digital_networks_                        archive/                      14-44               '                    Hardware Information         D                    The owner and maintainer of current DECserver andE                    related hardware is DIGITAL Network Products Group:                    (DNPG):  *                    o  http://www.dnpg.com/  D           __________________________________________________________B           14.16  Where can I get hardware self-maintenance support                  assistance?  D                    The HP Parts Directory and the HP Parts ReferenceE                    Guide (arguably the most direct descendents of the G                    HP Assisted Services program, of the Compaq AssistedrE                    Services program, and of the now-ancient DECmailer(C                    program) are available to customers that wish to_C                    maintain their own system(s) (self-maintenance),1F                    but that wish some level of assistance in acquiringD                    specific parts, hardware diagnostics and hardwareC                    manuals for the system(s), and that wish to haveeJ                    access to spares and module-level repairs for customer-3                    performed hardware module swaps:d  1                    o  http://www.hp.com/go/parts/o  2                    o  http://www.hp.com/buy/parts/  H                    The HP Parts Reference Guide replaces the CAS-CatalogH                    and DAS-Catalog parts catalogs and related resources.  I                    Details of the available self-maintenance programs andnG                    services can vary by geography and by the particular I                    services channel(s), and current program specifics arem0                    available via the above URLs.  D           __________________________________________________________G           14.17  Why does my system halt when I power-cycle the consolet                  terminal?  I                    Various VAX and Alpha consoles are designed to process C                    the BREAK signal, treating it as a HALT request.   J                    A BREAK is a deliberately-generated serial line framing                    error.   ?                    When a serial line device such as a terminalaE                    powers up (or sometimes when powering down) it can_D                    generate framing errors. These framing errors are8                    indistingushable from a BREAK signal.  J                                                                      14-45               '                    Hardware Information         D                    When a BREAK is received on a serial line consoleE                    for various VAX systems-including most VAXstation,e@                    MicroVAX, and VAX 4000 series-it is typicallyG                    interpreted as a HALT. Alpha systems will also oftensD                    process a BREAK in a similar fashion, halting the                    system.  D                    There is no uniform or generally-available way toJ                    disable this behaviour on every VAX or Alpha system. OnJ                    some systems, BREAK processing can be disabled in favorG                    of [CTRL/P], or [CTRL/P] is the only way to halt thec                    processor.s  I                    The most common way to avoid these halts is to disable G                    the serial line console or to simply not power-cycletC                    the console terminal. There is certain importantoE                    system state information that is displayed only oniH                    the console, OpenVMS expects to always have access to&                    the system console.  (                    Also see Section 5.6.  D           __________________________________________________________H           14.18  Can I reuse old keyboards, mice and monitors with a PC?  F                    Older HP keyboards (those with the DIGITAL logo andG                    the RJ modular jacks), older HP mice (those with the F                    DIGITAL logo and with the RJ modular jacks, or withE                    a DIN connector with pins in a configuration other G                    than the PC-standard DIN connector pin orientation),.D                    and older video monitors (with RGB synch-on-greenD                    video signaling) all use signaling formats and/orC                    communications protocols that differ from the PCAE                    standards, and are not (easily) interchangable noroH                    (easily) compatible with typical PC peripheral deviceH                    controllers. The LK201 and LK401 keyboards, the VSXXXG                    series mice, the VR260 and VR290 monitors, etc., aretF                    incompatible with most PC systems and with most KVM                    switches.  G                    Newer HP (and Compaq) keyboards (those with with PC-aH                    style DIN plugs, and the HP, Compaq or DIGITAL logo),D                    newer HP mice (with PC-pin DIN plugs, and the HP,D                    Compaq or DIGITAL logo), and newer video monitorsG                    (multi-synch, usually with a VGA or SVGA connection, E                    or later) are often interchangeable with "industrym                      14-46 d  t          '                    Hardware Information         C                    standard" PC systems, and can often be used with G                    most PC peripheral device controllers. LK461, LK463, G                    LK46W, LK471, PC7XS-CA, VRC16, VRC21, TFT-series LCD F                    flat-panel displays, etc., are typically reasonablyD                    compatible with most PC systems, and will usuallyI                    perform as expected within the limits of the hardware. E                    (For details of CRT and LCD display compatibility, -                    please see Section 14.19.)a  D                    Rule of thumb: if the peripheral device componentF                    was sold for use with the DEC 2000 (DECpc 150 AXP),F                    an AlphaServer series, an AlphaStation series, or aI                    more recent Alpha system, it will probably work with asG                    PC peripheral controller or with a PC-compatible KVMhF                    switch. If the peripheral device component was soldJ                    for use with an VT420 or older terminal, most VAX, mostG                    VAXstation, and most Alpha systems with names in the I                    format DEC [four-digit-number], it probably won't work >                    on a PC system or with a PC-compatible KVM.  I                    Note that the above is a general guideline, and should I                    not be read to indicate that any particular peripheral A                    device will or will not work in any particulardH                    configuration, save for those specific configurations9                    the device is explicitly supported in.i  B                    Software Integrators sells a video adapter cardF                    called Gemini P1 which will drive many of the olderE                    HP (DIGITAL-logo) fixed-frequency monitors on a PCu                    system:  *                    o  http://www.si87.com/  D                    The DIGITAL (classic 2-5-2-style) part number 29-J                    32549-01 converts the output from the RGB cable (3 BNC,J                    synch-on-green) that comes with the VAXstation 3100 andG                    VAXstation 4000 series to a female SVGA D connector. D                    You may be able to find third-party converters orF                    adapters (3 BNCs with synch-on-green signaling to 5=                    BNCs with VGA/SVGA, or to 15-pin VGA/SVGA.s  E                    This adapter will allow PC multisync monitors withbF                    the needed frequency specifications to be used withI                    the VAXstation series synch-on-green video connection.oF                    It may well also work with a VAXstation 2000 series  J                                                                      14-47 r             '                    Hardware Informatione        A                    systems, but specifics and performance of thatVI                    combination are not immediately known at this writing.t  G                    The protocol definition for the old DIGITAL keyboard I                    and mouse interfaces is buried at the back of the QDSS I                    section in the old VAXstation II manual, specifically, E                    in the back of the VCB02 Video Subsystem Technical7I                    Manual (EK-104AA-TM). The keyboard wiring and protocol E                    is in appendix B, and occupies circa 44 pages. The :                    mouse is in appendix C, circa 12 pages.  *                    Also see Section 14.19.  D           __________________________________________________________J           14.19  Which video monitor works with which graphics controller?  J                    To determine the answer to the "will this video monitorI                    or this LCD panel work with this graphics controller?"TJ                    question, please first locate the resolution(s) and theG                    frequencies that are possible/supported at both endscI                    of the video cable (on the display and on the graphics_E                    controller, in other words), and then determine if1J                    there are any matching settings available. If there areI                    multiple matches, you will need to determine which one 6                    is most appropriate for your needs.  G                    You will also need to determine if the video monitoraF                    or graphics controller requires the 3 BNC signalingF                    with the synchronization signals on the green wire,F                    or the 5 BNC signaling common on many PCs, or otherF                    connections such as the DB15 video connector or USBD                    connector used on various systems. (BNC signalingF                    is comparatively old, but prevalent with many olderG                    hobbyist AlphaStation or VAXstation configurations.)   J                    If there are no matches, you will likely need to changeG                    the hardware at one or both ends of the video cable.,  E                    The refresh frequencies for many devices have been H                    posted to comp.os.vms and/or other newsgroups. Search6                    the archives for details. Also see:  /                    o  http://www.repairfaq.org/,  4                    o  http://www.mirage-mmc.com/faq/  Z                    o  http://www.geocities.com/SiliconValley/Foothills/4467/fixedsync.html                      14-48 e             '                    Hardware Informationf        D                    o  http://saturn.tlug.org/sunstuff/ffmonitor.html  A                    o  http://hawks.ha.md.us/hardware/monitor.html   E                    LCD-based and plasma-based flat-panel displays are:E                    generally compatible with all recent OpenVMS Alpha B                    systems and supported graphics controllers. ForF                    best results, you should generally set the graphicsG                    controller to match the native LCD or plasma displaytA                    resolution and (for LCD displays) also set the/G                    controller refresh rate to 60Hz. Check your graphicsnD                    controller and your display documentation for anyD                    device-specific requirements and/or configuration#                    recommendations.s  G                    Some of the older graphics controllers around do notuG                    necessarily generate stable signals at 60 Hz, if the J                    controller can even generate that refresh rate; you mayG                    end up upgrading to a less-old controller. (At least I                    some of the PowerStorm 3D30 and PowerStorm 4D20 seriesdE                    controllers, for instance, are not necessarily theeF                    best choice for 60 Hz operations with an LCD, basedD                    on empirical testing with an AlphaStation XP1000,F                    PowerStorm 3D30, and a TFT2025 series LCD. DegradedC                    or mismatched signals produce degraded displays,yH                    obviously. The newest graphics controllers compatibleC                    with your particular system are generally better H                    choices here for use with LCD; the Radeon 7500 seriesC                    is a good choice for most EV6-class AlphaStationa)                    systems, for instance.a  *                    Also see Section 14.18.  D           __________________________________________________________A           14.20  Where can I get information on storage hardware?   F                    Information on various HP (Compaq, DIGITAL) OpenVMSG                    and other disk storage hardware and controllers, and I                    related technical information on SCSI, device jumpers, )                    etc., is available at:s  2                    o  http://theref.aquascape.com/  1                                              Note   B                       the aquascape website appears to have becomeD                       unavailable, and the FAQ maintainer is unaware  J                                                                      14-49               '                    Hardware Informations        D                       of a new or replacement server. You may or mayF                       not have some success looking for this or of anyF                       other now-unavailable sites using the world-wide&                       web archives at:  0                       o  http://www.archive.org/  D           __________________________________________________________D           14.21  Why does my LK401 keyboard unexpectedly autorepeat?  6                    There are several modes of failure:  C                    o  Pressing 2 and 3 keys at the same time causesrD                       one key to autorepeat when released. Check theF                       hardware revision level printed on the bottom ofE                       the keyboard. If the revision level is C01, the H                       keyboard firmware is broken. Call field service toH                       replace the keyboard with any revision level other                       than C01.   E                    o  Pressing certain keys is always broken. TypicalsF                       symptoms are: delete always causes a autorepeat,D                       return needs to be pressed twice, etc. This isF                       frequently caused by having keys depressed whileE                       the keyboard is being initialized. Pressing ^F2aD                       several times or unplugging and replugging theG                       keyboard frequently fix this problem. (Ensure youhE                       have current ECO kits applied; there is a patchn5                       available to fix this problem.)a  H                    o  A key that was working spontaneously stops workingG                       correctly. This may be either of the two previouseF                       cases, or it may be bad console firmware. EnsureF                       that you have the most recent firmware installedI                       on your Alpha system. In particular, an old versionmI                       of the DEC 3000 SRM firmware is known to have a bugi@                       that can cause this keyboard misbehaviour.                                  14-50 r  g          '                    Hardware Information       D           __________________________________________________________I           14.22  Problem - My LK411 sends the wrong keycodes or some keysy                  are deadm  H                    Check the firmware revision on the keyboard. HardwareF                    revision B01 introduced an incompatability with theD                    device driver which causes the keyboard to not beF                    recognized correctly. There is a patch available toF                    fix this problem: [AXPDRIV06_061] - the fix is alsoJ                    included in OpenVMS V6.2. The rev A01 keyboard, and the6                    LK450 should work without problems.  C                    If you are working from another operating system E                    platform, please see the DECxterm tool and relatedn8                    information on OpenVMS Freeware V5.0.  D           __________________________________________________________F           14.23  Which DE500 variant works with which OpenVMS version?  E                    Ensure you have a version of the Alpha SRM consoleSF                    with support for the DE500 series device. Apply ALLI                    mandatory ECO kits for the OpenVMS version in use, andoG                    also apply the CLUSIO, ALPBOOT, and ALPLAN kits, andoG                    apply any available ALPCPU ECO kit for the platform.                       o  DE500-XA:                       auto-detection, no auto-negotiation,E                       OpenVMS V6.2-1H1 and ALPBOOT ECO, also V7.0 andE$                       later and ECO.?                       Device hardware id 02000011 and 02000012.s7                       Component part number 54-24187-01                       o  DE500-AA7                       auto-detection, auto-negotiation,dG                       OpenVMS V6.2 and ALPBOOT and ALPLAN ECOs, or V7.1 (                       and later and ECO.?                       Device hardware id 02000020 and 20000022.t7                       Component part number 54-24502-01E                      o  DE500-BA7                       auto-detection, auto-negotiation,wF                       OpenVMS V6.2-1H3 and CLUSIO, ALPBOOT, ALPLAN and@                       ALPCPU ECOs, or V7.1-1H1 or later and ECO.F                       Device hardware id 02000030 (check connector, vsH                       DE500-FA) (other values on old Alpha SRM firmware)7                       Component part number 54-24602-010  J                                                                      14-51               '                    Hardware Informationu        A                    o  DE500-FA (100 megabit fibre optic Ethernet)d0                       OpenVMS V7.1-1H1 and laterF                       Device hardware id 02000030 (check connector, vsG                       DE500-BA) (other values possible on old Alpha SRM-                       firmware)M7                       Component part number 54-24899-014  J                    To check the DE500 device hardware id from OpenVMS, use)                    the following command:   #                    $ ANALYZE/SYSTEM ,                    SDA> SHOW LAN/DEVICE=EWc:  <                    The "hardware version" will be displayed.  E                    To set the DE500 speed and duplex settings via thesI                    associated Alpha SRM console environment variable, see                     Table 14-4.  J           ________________________________________________________________5           Table 14-4  DE500 Speed and Duplex Settingsu  J           ________________________________________________________________J           EWx0_MODE_setting_________________Meaning_______________________  F           Twisted-Pair                      10 Mbit/sec, nofull_duplex  D           Full Duplex, Twisted-Pair         10 Mbit/sec, full_duplex  F           AUI                               10 Mbit/sec, nofull_duplex  F           BNC                               10 Mbit/sec, nofull_duplex  G           Fast                              100 Mbit/sec, nofull_duplex   E           FastFD (Full Duplex)              100 Mbit/sec, full_duplex   J           Auto-Negotiate____________________Negotiation_with_remote_device  A                    To override the console setting and use LANCP:               $ RUN SYS$SYSTEM:LANCP)           LANCP> SET DEVICE EWA0/SPEED=10 ,           LANCP> DEFINE DEVICE EWA0/SPEED=106           LANCP> SET DEVICE EWA0/SPEED=100/full_duplex9           LANCP> DEFINE DEVICE EWA0/SPEED=100/full_duplex                       14-52 c  o          '                    Hardware Information         C                    Fast Ethernet (100Base, 100 megabit) controllers_F                    such as the DE500 series have a pair of connectionsC                    available-while traditional Ethernet (10Base, 10 F                    megabit) is inherently a half-duplex protocol, FastG                    Ethernet can be configured to use one or both of the F                    available connections, depending on the controller.A                    Fast Ethernet can thus be half- or full-duplexmF                    depending on the configuration and the capabilitiesE                    of the network controller and the Ethernet networkfI                    plant. Some Fast Ethernet controllers can also operatesH                    at traditional Ethernet speeds, these controllers areH                    thus often refered to as 10/100 Ethernet controllers.  D           __________________________________________________________B           14.24  How do I set the speed and duplex on OpenVMS I64?  F                    OpenVMS I64 on Integrity servers does not provide aE                    console-level environment variable akin to the SRMrI                    console variables used to manage the network speed andtF                    duplex settings on OpenVMS Alpha and Alpha systems.H                    On OpenVMS I64 on Integrity servers, LANCP is used toI                    manage the speed and the duplex setting of the network_                    controllers.h              $ RUN SYS$SYSTEM:LANCP)           LANCP> SET DEVICE EWA0/SPEED=10t,           LANCP> DEFINE DEVICE EWA0/SPEED=106           LANCP> SET DEVICE EWA0/SPEED=100/full_duplex9           LANCP> DEFINE DEVICE EWA0/SPEED=100/full_duplexw  C                    The EFI-level network bootstrap operations for a H                    network-based upgrade or a network-based installationJ                    of OpenVMS I64 require the use of autonegotiation and a3                    switch capable of supporting it.   >                    See Section 14.23 for a related discussion.  D           __________________________________________________________+           14.25  Third-party or Unsupported 4                  disk/tape/controllers/SCSI/widgets?  I                    A wide variety of third-party and formally-unsupported D                    widgets-SCSI and ATA/ATAPI (IDE) disks and tapes,A                    graphics controllers, etc-are obviously widelya@                    available, and are used on various platforms.  J                                                                      14-53 _  _          '                    Hardware Information         H                    If you purchase third-party or unsupported or genericF                    SCSI, ATA/ATAPI (IDE) storage devices, you and yourH                    device vendor will be responsible for the testing andI                    the support of the devices. In general, you can expectdI                    that HP will address non-standards-compliance problems E                    within OpenVMS (changes that will also not prevent3G                    operations with other supported devices, of course), E                    but you and/or the device vendor and/or the device F                    manufacturer are responsible for finding and fixingG                    problems in the particular third-party device and or '                    controller involved.e  I                    In particular, realize that neither SCSI nor ATA/ATAPItD                    (IDE) is a particularly standard interface, theseD                    interfaces tend to be a collection of optionally-G                    implemented and standardized interface features. You I                    should not and can not simply assume that all SCSI nornG                    ATA/ATAPI (IDE) storage devices are interchangeable.aG                    If you want to try to use a generic SCSI device, use J                    V6.2 or later, or (better) V7.1-2 or later. If you wishG                    to try to use ATA/ATAPI (IDE), use OpenVMS V7.1-2 or                     later.e  J                    On older OpenVMS releases, see the disk capacity limits!                    (Section 9.5).   D                    With SCSI disks on releases prior to V6.2, ensureF                    that you have the ARRE and ARWE settings configuredE                    correctly (disabled). (If not, you will see DRVERR =                    fatal drive errors and error log entries.)a  F                    Some SCSI disks set the medium type byte as part ofJ                    the SCSI size field-this is a SET CAPACITY extension toH                    SCSI specs. This problem also applies to VAX V7.1 and                    later.   F                    Disks with SCSI disk sizes past 8.58 GB and/or withJ                    the SET CAPACITY extension require ALPSCSI07 ECO or theJ                    OpenVMS Alpha V7.1-2 or later release. (See Section 9.5(                    for further details.)  >                    Based on the displays of the (undocumented)J                    SYS$ETC:SCSI_INFO tool; this tool is present in OpenVMS"                    V6.2 and later:                      14-54 7  a          '                    Hardware Information         K           Issuing 6-byte MODE SENSE QIOW to get current values for page 01hC0                  Page Code ................. 01hF                  Page Name ................. Read-Write Error Recovery0                  Saveable .................. Yes/                  Size ...................... 10nD                  Hex Data .................. E6 08 50 00 00 00 08 002                                              00 00  I                    The E6 shown indicates that the AWRE and ARRE bits aretF                    set, and this is incompatible with OpenVMS versionsE                    prior to V6.2. Further along in the same SCSI_INFO ,                    display, if you also see:  N           Issuing 6-byte MODE SENSE QIOW to get changeable values for page 81h0                  Page Code ................. 01hF                  Page Name ................. Read-Write Error Recovery0                  Saveable .................. Yes/                  Size ...................... 10 D                  Hex Data .................. C0 08 50 00 00 00 08 002                                              00 00  G                    The C0 value means that the AWRE and ARRE values canuF                    be changed on this particular SCSI device. (This isI                    not always the case.) If the bits are set, you can use I                    RZDISK from the OpenVMS Freeware, and can reset the E6 I                    flag byte to hexadecimal 26 (or whatever the remaining.=                    mask when you remove bits C0) on page one.   J                    Each SCSI and ATA/ATAPI (IDE) host contains non-trivialI                    SCSI and IDE driver software, and each device contains H                    equally non-trivial firmware- taken together with theF                    mechanical and electronic components, this softwareJ                    and firmware will determine whether or not a particular4                    device will function as expected.  F                    Also note that various devices-such as various SCSIF                    CD-R devices -can implement and can require vendor-E                    specific protocol extensions, and these extensionscG                    can require modifications to OpenVMS or the additionnC                    of various utilities. In various of these cases,oD                    these devices perform functions that will requireD                    them to use SCSI or ATA/ATAPI (IDE) commands thatB                    are (hopefully) architecturally-compatible SCSIC                    or ATA/ATAPI (IDE) command extensions. (Also seec0                    Section 7.1 and Section 9.7.)  J                                                                      14-55 t  s          '                    Hardware Information         I                    Some SCSI tapes lack odd-byte transfer support, makingrJ                    operations with OpenVMS problematic at best, as OpenVMSE                    expects odd-byte support. Examples of such includetH                    LTO-1 devices such as the HP Ultrium 230 series tape,I                    and the DLT VS80 series tapes. Due to the lack of odd- I                    byte transfer support, LTO-1 devices are not supported H                    by OpenVMS. LTO devices in the LTO-2 and later seriesE                    do reportedly presently all have odd-byte transfer H                    support, and operations are reportedly rather easier.:                    Do check for formal support, of course.  J                    In order for OpenVMS to officially support a particularJ                    device, integration and testing work is mandated. ThereF                    can be no certainty that any particular device willF                    operate as expected in any particular configurationD                    without first performing this (non-trivial) work.  I                    It is quite possible to find two devices-both entirelyeC                    compliant with applicable standards or interface 8                    documents-that will not interoperate.  ?                    The same general statement holds for OpenVMSgI                    bootstrapping on an unsupported VAX or Alpha platform.aH                    It might or might not work. In particular, please seeE                    the OpenVMS Software Product Description (SPD) foroF                    the list of platforms supported by OpenVMS. OpenVMSB                    is not supported on the Personal Workstation -aE                    series, on the Digital Server series platforms, ontH                    the AlphaServer 2100 series 5/375 CPU, on the Multia,F                    on the AlphaServer DS20L, and on a variety of otherI                    platforms. (You might or might not see success bootinga6                    OpenVMS on any of these platforms.)  '           _____________________________t;           14.25.1  Lists of third-party widgets on OpenVMS?   J                    Various folks have successfully used common third-partyH                    disk disk devices with OpenVMS, such as the ATA (IDE)H                    and SCSI variants of the Iomega Zip250 removable disk                    device.  E                    Common SCSI CD-R/CD-RW devices such as the PlextoroF                    PlexWriter 12/10/32S SCSI series and the HP DVD200iF                    series (recording CD-R) have also been successfullyD                    utilized with various AlphaStation and VAXstation                      14-56 o  n          '                    Hardware Informationw        G                    systems, and with tools such as CDRECORD. (A PlextoroF                    PlexWriter burn of 614400000 bytes (300000 sectors)B                    requires just over six minutes at 12x, using anD                    AlphaStation XP1000 666 MHz EV67 system UltraSCSIF                    host.) (See Section 9.7 for detailed discussions ofH                    recording optical media on OpenVMS, and the available                    tools.)  G                    If you choose to attempt to use third-party devices,sH                    ensure that you have the most current OpenVMS versionB                    and the most current ECO kit(s) applied. In theF                    specific case of the ATA (IDE) Iomega Zip250 drive,D                    ensure that you have the most current revision of*                    SYS$DQDRIVER installed.  '           _____________________________lG           14.25.2  Are the 2X-KZPCA-AA and SN-KZPCA-AA LVD Ultra2 SCSI?   H                    Yes. Both of these controllers are Ultra2 low-voltage7           _________differential_(LVD)_SCSI controllers.v  7           14.25.3  Resolving DRVERR fatal device error?a  I                    If this is on an OpenVMS version prior to V6.2, please5H                    see the AWRE and ARRE information included in section!                    Section 14.25.E  D           __________________________________________________________7           14.26  Looking for connector wiring pin-outs?   E                    The DECconnect DEC-423 Modified Modular Jack (MMJ)aH                    appears similar to a telphone or network modular jac,I                    though with the key offset to one side. The DECconnectsI                    MMJ connector pin-out is listed in Table 14-5, with aneJ                    end-on view of the connector pins and the connector key                    shown below._  J           ________________________________________________________________%           Table 14-5  DEC MMJ Pin-out   J                    _______________________________________________________J                    Pin_____Description____________________________________  4                    1       Data Terminal Ready (DTR)  )                    2       Transmit (TXD)i  1                    3       Transmit Ground (TXD-)o  J                                                                      14-57 w             '                    Hardware Information_      J           ________________________________________________________________-           Table 14-5 (Cont.)  DEC MMJ Pin-out_  J                    _______________________________________________________J                    Pin_____Description____________________________________  0                    4       Receive Ground (RXD-)  (                    5       Receive (RXD)  J           _________6_______Data_Set_Ready_(DSR)___________________________  !              +------------------+w!              | 1  2  3  4  5  6 |_!              +------------+    ++_                            +____+  D                    The BC16E-nn (where the "-nn" indicates the cableG                    length) cabling and keying "flips over" or "crosses-_I                    over" the signal wires, and this allows all DECconnect G                    MMJ connections to be wired identically; the ends of G                    the BC16E are symmetrical and fully interchangeable, E                    and allows either end of the cable to be connected_G                    either to the terminal or to the host. Specifically, B                    the BC16E-nn cross-over wiring looks like this:  7                   Terminal                         Host"6                   MMJ                              MMJ  9                DTR 1 --->---------->----------->--- 6 DSRn9                TXD 2 --->---------->----------->--- 5 RXD 5                    3 ------------------------------ 4b5                    4 ------------------------------ 3a9                RXD 5 ---<----------<-----------<--- 2 TXDi9                DSR 6 ---<----------<-----------<--- 1 DTRB  F                    DECconnect parts and connections are available fromF                    HP, and MMJ crimping dies for use in typical telco-J                    style crimping tools, and MMJ connectors, are availableH                    from Blackbox and from other communications equipment                    vendors.-  I                    The PC-compatible DB9 connector pin-out found on Alpha H                    and Integrity COM serial ports-and on most PC systems+                    is listed in Table 14-6.                       14-58    n          '                    Hardware Informationa        J           ________________________________________________________________$           Table 14-6  PC DB9 Pin-out  J                    _______________________________________________________J                    Pin_____Description____________________________________  4                    1       Data Carrier Detect (DCD)  (                    2       Received Data  (                    3       Transmit Data  4                    4       Data Terminal Ready (DTR)  !                    5       Ground   /                    6       Data Set Ready (DSR)_  0                    7       Request To Send (RTS)  (                    8       Clear To Send  J           _________9_______floating_______________________________________  F                    The MicroVAX DB9 console connector pin-out predatesB                    the PC-style DB9 pin-out (adapters discussed inE                    Section 14.27), and uses a then-common (and older) I                    standard pin-out, and uses the EIA-232 series standard /                    signals shown in Table 14-7.   J           ________________________________________________________________*           Table 14-7  MicroVAX DB9 Pin-out  J                    _______________________________________________________J                    Pin_____Description____________________________________  ,                    1       Protective Ground  *                    2       Transmited Data  (                    3       Received Data  0                    4       Request To Send (RTS)  4                    5       Data Terminal Ready (DTR)  /                    6       Data Set Ready (DSR)_  (                    7       Signal Ground  F                    8       Shorted to pin 9 on MicroVAX and VAXstation"                            2000...  J           _________9_______...series_systems,_otherwise_left_floating.____  F                    When pin 8 is shorted to pin 9, this is a BCC08 (orH                    variant) cable, most commonly used as a console cable  J                                                                      14-59               '                    Hardware Information         J                    on the MicroVAX 2000 and VAXstation 2000 series. (OtherJ                    systems may or may not tolerate connecting pin 8 to pin                    9.)  -                    The BN24H looks like this:   &                         MMJ       RJ45  $                          1---------8$                          2---------2$                          3---------1$                          4---------3$                          5---------6$                          6---------7  -                    The BN24J looks like this:X  &                         MMJ       RJ45  $                          1---------7$                          2---------6$                          3---------3$                          4---------1$                          5---------2$                          6---------8                      Also see:  :                    o  http://www.hp.com/go/openvms/wizard/  :                    o  http://www.airborn.com.au/rs232.html  5                    o  http://www.stanq.com/cable.htmlT  E                    o  For adapters and connectors, see Section 14.27.   D           __________________________________________________________C           14.27  What connectors and wiring adapters are available?-  H                    The H8571-B and H8575-B convert the (non-2000-series)B                    MicroVAX DB9 to the DECconnect DEC-423 ModifiedD                    Modular Jack (MMJ) pin-out; to the MMJ DECconnectG                    wiring system. The MicroVAX 2000 and VAXstation 2000bG                    requires a BCC08 cable (which has the 8-9 short, seenI                    Section 14.26) and the H8571-C or the H8571-D DB25-to-_I                    MMJ adapter for use with DECconnect. (For a discussion H                    of the console bulkhead on the MicroVAX II series andF                    on other closely-related series systems, please see%                    Section 14.3.3.4.)-                      14-60               '                    Hardware Informations        H                    Somewhat less ancient HP (HP, Compaq or DIGITAL logo)D                    systems will use either the DECconnect MMJ wiringD                    directly or-on most (all?) recent system designs-H                    the PC-compatible DB9 9-pin pin-out; the PC-style COM8                    serial port interface and connection.  G                    There are two DB9 9-pin pin-outs, that of the H8571- E                    B and similar for the MicroVAX and other and oldernH                    systems, and that of the H8571-J for the PC-style COMJ                    port, AlphaStation, Integrity, and other newer systems.G                    The older MicroVAX DB9 and the PC-style DB9 pin-outs &                    are not compatible.  J           ________________________________________________________________<           Table 14-8  DECconnect MMJ Connectors and Adapters  J                    _______________________________________________________J                    Part________Converts_BC16E_MMJ_male_to_fit_into________  B                    H8571-A     EIA232 DB25 25-pin female (common).J                                Functionally similar to the H8575-A, thoughD                                the H8575-A has better ESD shielding.  F                    H8571-B     Older MicroVAX (other than the MicroVAXI                                2000) DB9 EIA232 serial port. Functionally I                                similar to the H8575-B, though the H8575-B H                                has better ESD shielding. Note: Cannot beJ                                used on a PC, Alpha nor Integrity DB9 9-pin)                                connector.   D                    H8571-C     25 pin DSUB Female to MMJ, Unfiltered  ?                    H8571-D     EIA232 25 pin male (modem-wired)A  B                    H8571-E     25 pin DSUB Female to MMJ, Filtered  I                    H8571-J     PC, Alpha, Integrity 9 pin (DB9) male (PC-hJ                                style COM serial port) Note: Cannot be usedH                                on the older MicroVAX DB9 9-pin connector  E                    H8572-0     BC16E MMJ double-female (MMJ extender)   B                    H8575-A     EIA232 DB25 25-pin female (common).J                                Functionally similar to the H8571-A, thoughD                                the H8575-A has better ESD shielding.  J                                                                      14-61               '                    Hardware Informationn      J           ________________________________________________________________D           Table 14-8 (Cont.)  DECconnect MMJ Connectors and Adapters  J                    _______________________________________________________J                    Part________Converts_BC16E_MMJ_male_to_fit_into________  F                    H8575-B     Older MicroVAX (other than the MicroVAXI                                2000) DB9 EIA232 serial port. Functionally I                                similar to the H8571-B, though the H8575-B_H                                has better ESD shielding. Note: Cannot beJ                                used on a PC, Alpha nor Integrity DB9 9-pin(                                connector  G                    H8575-D     25 Pin to MMJ with better ESD Protectiont  @                    H8575-D     25 Pin to MMJ with better and ESD)                                Protection   A                    H8575-E     25 Pin Integrity rx2600 Management C                                Processor (MP) port to MMJ, with ESD )                                Protectione  ;                    H8577-AA    6 pin Female MMJ to 8 pin MJa  F                    BC16E-**    MMJ cable with connectors, available inJ           _____________________various_lengths____________________________  H                    Numerous additional adapters and cables are availableG                    from the (now out of print) OPEN DECconnect Building2I                    Wiring Components and Applications Catalog, as well asr:                    descriptions of the above-listed parts.  J                    The DECconnect wiring system has insufficient signalingG                    for modems, and particularly lacks support for modem #                    control signals.s  G                    The H8571-A and H8575-A are MMJ to DB25 (female) andnG                    other connector wiring diagrams and adapter-, cable-tD                    and pin-out-related discussions are available at:  :                    o  http://www.hp.com/go/openvms/wizard/  H                    Jameco has offered a USB-A to PS/2 Mini DIN 6 AdapterH                    (as part 168751), for those folks wishing to (try to)<                    use PS/2 Keyboards via USB-A connections.  I                    The LK463 USB keyboard is also a potential option, forBF                    those wishing to connect an OpenVMS keyboard to USBI                    systems or (via the provided adapter) to PS/2 systems.aF                    The LK463 provides the classic OpenVMS keyboard and                      14-62               '                    Hardware Information         F                    keyboard layout on USB-based system configurations,B                    including operations with the USB connection onI                    specific Alpha systems (and specifically on those with G                    supported USB connections) and on Integrity servers.s  I                    For information on the Alpha console COM port(s) or oneA                    the VAX console port, please see Section 14.3.   D           __________________________________________________________;           14.28  What is flow control and how does it work?c  8                    XON/XOFF is one kind of flow control.  G                    In ASCII, XON is the <CTRL/Q> character, and XOFF isi                     the <CTRL/S>.  E                    XON/XOFF flow control is typically associated with J                    asynchronous serial line communications. XON/XOFF is anI                    in-band flow control, meaning that the flow control is_*                    mixed in with the data.  B                    CTS/RTS is another type of flow control, and isF                    sometimes called hardware flow control. Out-of-bandE                    means that seperate lines/pins from the data lines @                    (pins) are used to carry the CTS/RTS signals.  B                    Both kinds of flow control are triggered when aH                    threshold is reached in the incoming buffer. The flowI                    control is suppose to reach the transmitter in time toiJ                    have it stop transmitting before the receiver buffer isJ                    full and data is lost. Later, after a sufficient amountH                    of the receiver's buffer is freed up, the resume flowF                    control signal is sent to get the transmitter going                    again.   E                    DECnet Phase IV on OpenVMS VAX supports the use ofcB                    asynchronous serial communications as a networkD                    line; of asynch DECnet. The communication devicesC                    (eg. modems, and drivers) must not be configured D                    for XON/XOFF flow control. The incidence of theseD                    (unexpected) in-band characters will corrupt dataC                    packets. Further, the serial line device drivers D                    might normally remove the XON and XOFF charactersH                    from the stream for terminal applications, but DECnetG                    configures the driver to pass all characters throughiF                    and requires that all characters be permitted. (TheG                    communication devices must pass through not only the   J                                                                      14-63               '                    Hardware Informationc        I                    XON and XOFF characters, they must pass all characters I                    including the 8-bit characters. If data compression is J                    happening, it must reproduce the source stream exactly.J                    No addition or elimination of null characters, and full%                    data transparency.s  B                    An Ethernet network is rather different than anC                    asynchronous serial line. Ethernet specifies theHI                    control of data flow on a shared segment using CSMA/CDhI                    (Carrier Sense Multiple Access, with Collision Detect)tH                    An Ethernet station that is ready to transmit listensH                    for a clear channel (Carrier Sense). When the channelH                    is clear, the station begins to transmit by assertingG                    a carrier and encoding the packet appropriately. The E                    station concurrently listens to its own signal, to H                    permit the station to detect if another station beganH                    to transmit at the same time-this is called collisionE                    detection. (The collision corrupts the signal in a I                    way that can reliably be detected.) Upon detecting the G                    collision, both stations will stop transmitting, and G                    will back off and try again a little later. (You can G                    see a log of this activity in the DECnet NCP network                     counters.)o  I                    DECnet provides its own flow control, above and beyondaG                    the flow control of the physical layer (if any). TheiD                    end nodes handshake at the beginning to establishE                    a transmit window size-and a transmitter will onlyhF                    send that much data before stopping and waiting forG                    an acknowledgement. The acknowledgement is only sent J                    when the receiver has confirmed the packet is valid. (AI                    well-configured DECnet generally avoids triggering any D                    underlying (out-of-band) flow control mechanism.)  D           __________________________________________________________0           14.29  CD and DVD device requirements?  J                    Read access to DVD-ROM, DVD+R/RW, DVD-R/RW, CD-ROM, andJ                    CD-R/RW devices on ATAPI (IDE) connections is generallyJ                    handled transparently by SYS$DQDRIVER, and SYS$DQDRIVERD                    will transparently de-block the media-native 2048E                    byte disk blocks with the 512-byte blocks expectedc=                    by OpenVMS and by native OpenVMS software._                      14-64               '                    Hardware Information         J                    Read access to DVD-ROM, DVD+R/RW, DVD-R/RW, CD-ROM, andI                    CD-R/RW devices on SCSI is handled by DKDRIVER, though J                    SYS$DKDRIVER will not transparently de-block the nativeJ                    2048-byte disk blocks into the 512-byte blocks expectedI                    by OpenVMS. The drive or external software is expectednF                    to provide this de-blocking, thus either a 512-byteJ                    block capable drive (such as all RRD-series SCSI CD-ROMH                    drives) is required, or host software is required forH                    a 2048-byte block drive. Third-party SCSI drives withI                    UNIX references in their support documentation or with H                    explicit 512-byte selectors or swiches will generallyD                    (but not always, of course) operate with OpenVMS.  F                    At least some of the Plextor PlexWriter SCSI drivesI                    can be successfully accessed (for read and write) from F                    OpenVMS, as can at least one Pioneer SCSI DVD driveF                    (for CD media). The Pioneer SCSI DVD drive switchesF                    to 2048 byte blocks for DVD media, and a block-sizeG                    conversion tool (written by Glenn Everhart) or otherl/                    similar tool can be applied.)  I                    OpenVMS also has supported HP DVD drives for the ATAPIx                    (IDE) bus.   A                    For some related information (and details on a <                    commercial DVDwrite package), please see:  C                    o  http://home.tiscali.de/dvd4openvms/supported_h#                       hardware.htmll  F                    No device driver currently presently permits directH                    block-oriented recording on DVD-RAM nor DVD+RW media,<                    nor other recordable or rewritable media.  B                    Recording (writing) of CD and DVD optical mediaF                    requires a recording or media mastering applicationJ                    or tool, and both commercial and non-commercial optionsH                    are available. See Section 9.7 for related details onI                    CDRECORD (both non-DVD and DVD versions are available,tE                    and at least one commercial version is available),DH                    and also see DVDwrite (commercial) or DVDRECORD (open                    source).g    J                                                                      14-65 m  a          '                    Hardware Information         A                    For information on the GKDRIVER (SYS$GKDRIVER)lI                    generic SCSI device driver and of the the IO$_DIAGNOSEbH                    $qio[w] interfaces (of SYS$DKDRIVER, SYS$DNDRIVER andE                    SYS$DQDRIVER) that are utilized by most CD and DVD I                    recording tools to send commands to SCSI, USB or ATAPI G                    devices (most USB and ATA devices-or more correctly,1I                    most ATAPI devices-can use SCSI-like command packets), H                    please see the SYS$EXAMPLES:GKTEST.C example, and seeG                    DECW$EXAMPLES:DECW$CDPLAYER.C example and please see E                    the various associated sections of the OpenVMS I/O +                    User's Reference Manual.d  H                    For information on creating bootable optical media on5                    OpenVMS, please see Section 9.7.3.U  D           __________________________________________________________C           14.30  Office-Friendly (Quieter) Integrity rx2620 series?   G                    The part number for the so-called Office-Friendly orMH                    Office Environment Integrity rx2620 series is AD244A.  H                    The AD244A option is incompatible with and eliminatesF                    the redundant cooling and power supply capabilitiesE                    of, but greatly reduces the sound output from, theUE                    Integrity rx2620 rack-mount computer-room variant._H                    (Server rack-mount configurations are rated for soundF                    output in the range of 70dB, per the HP QuickSpecs.I                    Suitable for the intended installation into a computer G                    room of course, but likely rather loud for an offices-                    environment installation.)p  G                    If you wish to retrofit this option into an existinguC                    Integrity rx2620 series, you must also order thecB                    HA113A1 (#53E) installation service; the optionG                    reportedly can not be installed by an end-user. Also0J                    reportedly, the option can be factory-ordered on customF                    configurations. If configuring for or converting anC                    existing rack-mount configuration for the officetE                    environment, also consider acquiring the availablen;                    pedestal-mounting option for the series.u                            14-66    1          '                    Hardware Information       D           __________________________________________________________D           14.31  KVM switches for AlphaServer and Integrity Servers?  G                    Various folks have reported success with the Raritan H                    series KVM (and specifically APKME the), and with the+                    HP-branded KVM switches.   F                    If you choose a KVM for use with Alpha or Integrity=                    servers, do ensure it provides either Unix G                    compatibility, X Windows compatibility, or specifies_I                    the Alpha or Integrity system. (This all usually meansSF                    that the switch supports keyboards that use the so-J                    called scanset three key-down and key-up sequences-key-H                    down and key-up are key to the way X Windows and thus%                    DECwindows works.)a  G                    Also see the discussion in Section 14.18 for related F                    information, and particularly for older pinouts-forJ                    those keyboard and mouse devices that pre-date the PS/2I                    DIN connections, the PC VGA/SVGA video connection, andbG                    such. Almost all VAX systems pre-date these pinouts,aG                    and peripherals intended for the older Alpha systemsh/                    also pre-date these pinouts.i                                            J                                                                      14-67                         J                    _______________________________________________________  7           15       Information on Networks and ClustersV      H                    The following sections contain information on OpenVMSG                    Networking with IP and DECnet, and on clustering and E                    volume shadowing, on Fibre Channel, and on relateds/                    products and configurations.   D           __________________________________________________________2           15.1  How to connect OpenVMS to a Modem?  J                    Please see the Ask The Wizard area topics starting with5                    (81), (1839), (2177), (3605), etc.   H                    o  http://www.hp.com/go/openvms/wizard/ (retired; use"                       ITRC forums)  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the available F                    ATW Wizard.zip archive, please see Section 3.8. ATWF                    has been superceded (for new questions) by the ITRCD                    discussion forums; the area remains available for                    reference.5  D           __________________________________________________________*           15.2  OpenVMS and IP Networking?  H                    The following sections contain information on OpenVMSD                    and IP networking, as well as IP printing topics.  '           _____________________________h9           15.2.1  How to connect OpenVMS to the Internet?e  D                    Some tutorial information and tips for connectingD                    OpenVMS systems to the Internet are available at:  5                    o  http://www.tmesis.com/internet/_        J                                                                       15-1 e  l          7                    Information on Networks and Clustersa      '           _____________________________..           15.2.2  Connecting to an IP Printer?  D                    To connect a printer via the IP telnet or lpr/lpdJ                    protocols, you will need to install and configure an IPH                    stack on OpenVMS, and configure the appropriate print                    queue.e  F                    With current OpenVMS IP implementations, the choiceE                    of telnet or lpr/lpd really amounts to determiningeJ                    which of these works better with the particular printer                    involved.  H                    To support network printing, the printer must includeG                    an internal or external NIC or JetDirect; an adapteru:                    connecting the network and the printer.  H                    While it is normally possible to use a host-connectedJ                    printer-when the host supports an LPD or telnet daemon,H                    and OpenVMS and most other operating systems have theF                    ability to serve locally-attached printers to otherF                    hosts on the network-it is generally far easier andG                    far more effective to use a printer that is directly H                    attached to the network. If your present printer doesI                    not have a NIC or a JetDirect, acquire an internal (if J                    available) or external NIC or JetDirect. Or replace theI                    printer. And obviously, most any operating system that E                    can serve its local printers usually also provides D                    a client that can access remote network-connected                    printers.  C                    Please see the Ask The Wizard (ATW) area topics-tH                    starting with topic (1020)-for additional information0                    on IP-based network printing.  H                    o  http://www.hp.com/go/openvms/wizard/ (retired; use"                       ITRC forums)  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the availablecF                    ATW Wizard.zip archive, please see Section 3.8. ATWF                    has been superceded (for new questions) by the ITRCD                    discussion forums; the area remains available for                    reference.p  J                    Please see Section 15.2.3 for information on Postscript                    printing.                      15-2     F          7                    Information on Networks and Clusters       '           _____________________________iC           15.2.3  How do I connect a PostScript printer via TCP/IP?   I                    Using TCP/IP Services (UCX) as the TCP/IP stack, it isTG                    possible to configure queues using the UCX$TELNETSYM E                    (TCP/IP Services prior to V5.0) or TCPIP$TELNETSYM H                    (with V5.0 and later) in order to print to PostscriptI                    printers. This assumes however that the printer itselfeF                    can convert whatever is passed to it into somethingH                    intelligible. As an example, if the printer has an IPJ                    address of 123.456.789.101 and jobs should be passed to#                    port 9100 then :q  A                    $ INITIALIZE/QUEUE/ON="123.456.789.101:9100" -r2                        /PROCESSOR=UCX$TELNETSYM  -"                        my_ip_queue  A                    $ INITIALIZE/QUEUE/ON="123.456.789.101:9100" - 4                        /PROCESSOR=TCPIP$TELNETSYM  -"                        my_ip_queue  E                    The port number of 9100 is typical of HP JetDirectsE                    cards but may be different for other manufacturerse                    cards.   F                    As a better alternative, DCPS Version 1.4 and laterD                    support IP queues using either HP TCP/IP ServicesD                    for OpenVMS software or Process Software MultinetF                    for OpenVMS. The usage of this type of interface isI                    documented in the DCPS documentation or release notes,TG                    and the DCPS$STARTUP.TEMPLATE startup template file.r  J                    For general and additional (non-Postscript) IP printingH                    information, please see topic (1020) and other topicsH                    referenced in that topic elsewhere within the Ask The                    Wizard area.r  H                    o  http://www.hp.com/go/openvms/wizard/ (retired; use"                       ITRC forums)  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the available F                    ATW Wizard.zip archive, please see Section 3.8. ATWF                    has been superceded (for new questions) by the ITRCD                    discussion forums; the area remains available for'                    reference. Also see:   ,                    o  http://www.wotsit.org/  J                                                                       15-3    F          7                    Information on Networks and Clusters         ?                    Please see Section 15.2.2 for pointers to an /                    introduction to IP printing.A  '           _____________________________(H           15.2.4  How do I set a default IP route or gateway on OpenVMS?  H                    If you have TCP/IP Services, then use the command for2                    TCP/IP Services V5.0 and later:                      $ TCPIP;                    SET ROUTE/GATE=x.x.x.x/DEFAULT/PERMANENT   D                    And for earlier TCP/IP Services versions, use the                    command:2                      $ UCX;                    SET ROUTE/GATE=x.x.x.x/DEFAULT/PERMANENT_  '           _____________________________4E           15.2.5  How can I set up reverse telnet (like reverse LAT)?   G                    Though it may seem obvious, Telnet and LAT are quite J                    different-with differing capabilities and design goals.  J                    Please see the documentation around the TCP/IP ServicesJ                    for OpenVMS TELNET command CREATE_SESSION. This commandC                    is the equivilent of the operations performed in.F                    LTLOAD.COM or LAT$SYSTARTUP.COM. There is no TELNETE                    equivilent to the sys$qio[w] control interface for F                    LTDRIVER (as documented in the I/O User's ReferenceF                    Manual) available, though standard sys$qio[w] callsI                    referencing the created TN device would likely operatec                    as expected.S  '           _____________________________dJ           15.2.6  Why can't I use PPP and RAS to connect to OpenVMS Alpha?  B                    OpenVMS Alpha IP PPP does not presently supportF                    authentication, and the Microsoft Windows NT optionD                    to disable authentication during a RAS connectionI                    apparently doesn't currently work-RAS connections will H                    require authentication-and this will thus prevent RAS                    connections.   E                    Future versions of OpenVMS and TCP/IP Services maysI                    add this, and future versions of Microsoft Windows maypB                    permit operations with authentication disabled.                      15-4o N  p          7                    Information on Networks and Clustersn      D           __________________________________________________________.           15.3  OpenVMS and DECnet Networking?  H                    The following sections contain information on OpenVMS)                    and DECnet networking.   '           _____________________________d2           15.3.1  Can DECnet-Plus operate over IP?  C                    Yes. To configure DECnet-Plus to operate over IP G                    transport and over IP backbone networks, install andnG                    configure DECnet-Plus, and install and configure the_J                    PWIP mechanism available within the currently-installedI                    IP stack. Within TCP/IP Services, this is a PWIPDRIVERSG                    configuration option within the UCX$CONFIG (versions_G                    prior to V5.0) or TCPIP$CONFIG (with V5.0 and later) &                    configuration tool.  '           _____________________________ G           15.3.2  What does "failure on back translate address request"                    mean?n  %                    The error message:   M                    BCKTRNSFAIL, failure on the back translate address request   I                    indicates that the destination node is running DECnet-cI                    Plus, and that its naming service (DECnet-Plus DECdns,iD                    LOCAL node database, etc) cannot locate a name toE                    associate with the source node's address. In other H                    words, the destination node cannot determine the nodeG                    name for the node that is the source of the incoming                     connection.  H                    Use the DECNET_REGISTER mechanism (on the destinationB                    node) to register or modify the name(s) and theF                    address(es) of the source node. Check the namespace/                    on the source node, as well.   B                    Typically, the nodes involved are using a LOCALH                    namespace, and the node name and address settings areI                    not coherent across all nodes. Also check to make sure I                    that the node is entered into its own LOCAL namespace.cI                    This can be a problem elsewhere, however. Very rarely,tI                    a cache corruption has been known to cause this error.k7                    To flush the cache, use the command:   J                                                                       15-5               7                    Information on Networks and Clusters         '                    $ RUN SYS$SYSTEM:NCLl?                    flush session control naming cache entry "*"e  J                    Also check to see that you are using the latest ECO forG                    DECnet-Plus for the version you are running. DECnet- 9                    Plus can use the following namespaces:s  D                    o  DECdns: DECnet-Plus distributed name services.  B                    o  LocalFile: a local file containing names and                        addresses.  D                    o  DNS/BIND: the TCP/IP distributed name services                        mechanism.  @                    o  The TCP/IP Services (UCX) local host file.  >                    Of these, searching DNS/BIND and LocalFile,>                    respectively, is often the most appropriate!                    configuration.   '           _____________________________i9           15.3.3  Performing SET HOST/MOP in DECnet-Plus?:  B                    First, issue the NCL command SHOW MOP CIRCUIT *  '                    $ RUN SYS$SYSTEM:NCLP%                    SHOW MOP CIRCUIT *   A                    Assume that you have a circuit known as FDDI-0XD                    displayed. Here is an example of the SET HOST/MOP<                    command syntax utilized for this circuit:  J                    $ SET HOST/MOP/ADDRESS=08-00-2B-2C-5A-23/CIRCUIT=FDDI-0  +                    Also see Section 15.6.3.g  '           _____________________________ =           15.3.4  How to flush the DECnet-Plus session cache?   '                    $ RUN SYS$SYSTEM:NCL ?                    FLUSH SESSION CONTROL NAMING CACHE ENTRY "*"t                        15-6F -             7                    Information on Networks and ClustersP      D           __________________________________________________________>           15.4  How to determine the network hardware address?  I                    Most Alpha and most VAX systems have a console command_C                    that displays the network hardware address. ManynC                    systems will also have a sticker identifying the E                    address, either on the enclosure or on the network %                    controller itself.   J                    The system console power-up messages on a number of VAXG                    and Alpha systems will display the hardware address,eC                    particularly on those systems with an integratedo4                    Ethernet network adapter present.  C                    If you cannot locate a sticker on the system, if D                    the system powerup message is unavailable or doesG                    not display the address, and if the system is at the B                    console prompt, start with the console command:                      HELPV  G                    A console command similar to one of the following iseB                    typically used to display the hardware address:                      SHOW DEVICE                     SHOW ETHERNET                    SHOW CONFIG  I                    On the oldest VAX Q-bus systems, the following consolesG                    command can be used to read the address directly offtG                    the (DELQA, DESQA, or the not-supported-in-V5.5-and-o4                    later DEQNA) Ethernet controller:  %                    E/P/W/N:5 20001920n  E                    Look at the low byte of the six words displayed byhH                    the above command. (The oldest VAX Q-bus systems-suchH                    as the KA630 processor module used on the MicroVAX IIH                    and VAXstation II series-lack a console HELP command,G                    and these systems typically have the primary networkEF                    controller installed such that the hardware addressB                    value is located at the system physical address                    20001920.)t  H                    If the system is a VAX system, and another VAX systemE                    on the network is configured to answer MaintenanceAC                    and Operations Protocol (MOP) bootstrap requestsV  J                                                                       15-7 s  s          7                    Information on Networks and Clusters         D                    (via DECnet Phase IV, DECnet-Plus, or LANCP), theB                    MOM$SYSTEM:READ_ADDR.EXE tool can be requested:                       B/R5:100 ddcu&                    Bootfile: READ_ADDR  G                    Where ddcu is the name of the Ethernet controller in F                    the above command. The primarly local DELQA, DESQA,F                    and DEQNA Q-bus controllers are usually named XQA0.H                    An attempt to MOP download the READ_ADDR program willG                    ensue, and (if the download is successful) READ_ADDRe5                    will display the hardware address.b  B                    If the system is running, you can use DECnet orE                    TCP/IP to display the hardware address with one ofE*                    the following commands.  %                    $! DECnet Phase IVA'                    $ RUN SYS$SYSTEM:NCPb2                    SHOW KNOWN LINE CHARACTERISTICS  !                    $! DECnet-Plus '                    $ RUN SYS$SYSTEM:NCL 4                    SHOW CSMA-CD STATION * ALL STATUS  3                    $! TCP/IP versions prior to V5.0b                    $ UCX&                    SHOW INTERFACE/FULL  4                    $! TCP/IP versions V5.0 and later                    $ TCPIP&                    SHOW INTERFACE/FULL  C                    A program can be created to display the hardwareSB                    address, reading the necessary information fromC                    the network device drivers. A complete example CCI                    program for reading the Ethernet or IEEE 802.3 network H                    controller hardware address (via sys$qio calls to theH                    OpenVMS network device driver(s)) is available at the!                    following URL:P  :                    o  http://www.hp.com/go/openvms/wizard/                        15-8o s  y          7                    Information on Networks and Clustersn        H                    To use the DECnet Phase IV configurator tool to watchD                    for MOP SYSID activity on the local area network:  '                    $ RUN SYS$SYSTEM:NCPdM                    SET MODULE CONFIGURATOR KNOWN CIRCUIT SURVEILLANCE ENABLEDc  H                    Let the DECnet Phase IV configurator run for at leastD                    20 minutes, and preferably longer. Then issue the&                    following commands:  '                    $ RUN SYS$SYSTEM:NCPuP                    SHOW MODULE CONFIGURATOR KNOWN CIRCUIT STATUS TO filename.txtN                    SET MODULE CONFIGURATOR KNOWN CIRCUIT SURVEILLANCE DISABLED  E                    The resulting file (named filename.txt) can now beOH                    searched for the information of interest. Most DECnetG                    systems will generate MOP SYSID messages identifyingiH                    items such as the controller hardware address and theH                    controller type, and these messages are generated and7                    multicast roughly every ten minutes.e  I                    Information on the DECnet MOP SYSID messages and otherIH                    parts of the maintenance protocols is included in theH                    DECnet network architecture specifications referenced#                    in section DOC9.l  '           _____________________________ J           15.4.1  How do I reset the LAN (DECnet-Plus NCL) error counters?  .                    On recent OpenVMS releases:  )                    $ RUN SYS$SYSTEM:LANCPiE                    SET DEVICE/DEVICE_SPECIFIC=FUNCTION="CCOU" devnameh  '           _____________________________ >           15.4.2  How do I install DECnet Phase IV on VMS 7.1?  F                    On OpenVMS V7.1, all DECnet binaries were relocatedF                    into separate installation kits-you can selectivelyI                    install the appropriate network: DECnet-Plus (formerlyeG                    known as DECnet OSI), DECnet Phase IV, and HP TCP/IP 1                    Services (often known as UCX).   I                    On OpenVMS versions prior to V7.1, DECnet Phase IV was_J                    integrated, and there was no installation question. YouI                    had to install the DECnet-Plus (DECnet/OSI) package onr  J                                                                       15-9               7                    Information on Networks and Clustersl        H                    the system, after the OpenVMS upgrade or installation                    completed.k  F                    During an OpenVMS V7.1 installation or upgrade, theD                    installation procedure will query you to learn ifH                    DECnet-Plus should be installed. If you are upgradingI                    to V7.1 from an earlier release or are installing V7.1 E                    from a distribution kit, simply answer "NO" to therJ                    question asking you if you want DECnet-Plus. Then-afterF                    the OpenVMS upgrade or installation completes - useI                    the PCSI PRODUCT INSTALL command to install the DECnet I                    Phase IV binaries from the kit provided on the OpenVMS -                    software distribution kit.y  E                    If you already have DECnet-Plus installed and wishrF                    to revert, you must reconfigure OpenVMS. You cannotG                    reconfigure the "live" system, hence you must rebootCF                    the system using the V7.1 distribution CD-ROM. ThenE                    select the DCL ($$$ prompt) option. Then issue then                    commands:  9                    $$$ DEFINE/SYSTEM PCSI$SYSDEVICE DKA0: ?                    $$$ DEFINE/SYSTEM PCSI$SPECIFIC DKA0:[SYS0.] O                    $$$ PRODUCT RECONFIGURE VMS /REMOTE/SOURCE=DKA0:[VMS$COMMON]   J                    The above commands assume that the target system deviceH                    and system root are "DKA0:[SYS0.]". Replace this withE                    the actual target device and root, as appropriate.lF                    The RECONFIGURE command will then issue a series ofH                    prompts. You will want to reconfigure DECnet-Plus offG                    the system, obviously. You will then want to use the E                    PCSI command PRODUCT INSTALL to install the DECnet D                    Phase IV kit from the OpenVMS distribution media.  J                    Information on DECnet support, and on the kit names, isH                    included in the OpenVMS V7.1 installation and upgrade!                    documentation.c  I                    Subsequent OpenVMS upgrade and installation procedures H                    can and do offer both DECnet Phase IV and DECnet-Plus!                    installations.                           15-10  