Conference mvblab::alphaserver_4100

    Which version of SRM console? In the future, please include console
    revision in any problem report.
    
    I assume you were trying to connect once up and running UNIX? or did
    you try to connect prior to or during booting?
    
    V3.0-10 SRM console added COM1_MODEM and COM1_FLOW EVs (environment
    variables). V4.0B UNIX added some modem- and baud-related features. I
    have forwarded your mail to the UNIX person who added said support in
    combination with the V3.0-10 console release [Digital UNIX uses console
    callbacks for baud rate settings, etc.] I'll post his reply.
    
    The particular problem you are reporting sounds like console is not
    involved.
    
    As an FYI, you will need to cable around the embedded RCM should you
    desire a baud rate other than 9600. You will also need V2.0 or greater
    serial ROMs (SROMs) on each of your CPUs. As long as you're at 9600,
    you can use RCM and older revision SROMs.
    
    BC

    Comments back from UNIX person. Perhaps a upcase/lowercase problem?
    
From:	WASTED::paradis "Dennis Paradis ATSE  29-Jan-1997 0714" 29-JAN-1997 07:23:21.46
To:	29.492::cummins (Bill Cummins,PKO3-2/Q21,223-4641)
CC:	
Subj:	Re: I've asked this person what version of console he is using. 

Hi Bill,

	Sorry for not responding sooner I was out on vacation. I doubt that
they're using a serial console so the console firmware should not be an issue.
Yes we do support modem handling on both the ports. This appears to be a problem
with the settings or the casing of characters is incorrect. This certainly does
not sound like a driver problem.

								--dennis

    This business with "cable-around" the RCM is unclear. I've read the
    firmware release notes that talk about this per reply .1 but no mention
    is made as to what the COM1_xxxxxx EV's are supposed to be set to.
    
    My customer has a 4100 running OpenVMS and we are unable to dial-in to
    COM1 as long as the port is set for MODEM via the SET TERMINAL command.
    We get the infamous "modem not wired correctly" error. The modem is
    Hayes compatible and we have done the necessary "AT" commands so that
    the modem signals correctly - I've done this many, many times on
    VAXes. We also hooked up a break-out panel to verify the signals.
    
    We are using a BC29P cable which is advertised for this purpose.
    
    So, do we need to modify any of the COM1_xxxx EV's? I'll be *happy* to
    RTFM if someone will tell me where.
    
    Regards,
       Dan

    The RCM only needs to be cabled around if you will be modifying the
    COM1 baud rate from the 9600 default. The RCM firmware cannot keep up
    at alternate baud rates. The RCM function only provides software flow
    control (i.e. no hardware flow control - no real UART).
    
    The AlphaServer 4000/4100 Service Guide (Appendix C) explains how to
    connect a modem. There are two ways to connect a modem to "COM1" on
    AlphaServer 4100/4000:
    
     1) Via the modem port on the embedded RCM function (9-pin DIN-style
        connector). When connected and active, this bypasses the COM1 
        (MMJ) connection.
     2) By connecting a modem to the COM1 port (MMJ). This is typically
        only done when one wants remote access at higher baud rates.
    
    One must bypass the RCM hardware/software to use option #2. The SRM
    console's COM1_XXXXX EVs come into play in this scenario. Baud rate
    must not be changed from 9600 unless the RCM function is taken out of
    the loop. One would typically set COM1_BAUD to the desired rate,
    COM1_FLOW to HARDWARE, and COM1_MODEM to ON under this scenario.
    
    The documentation of the COM1_XXXX EVs is poor to non-existent because
    these were added post-FRS (and not only to the 4100/4000 platform) per
    the request of Digital UNIX in order to satisfy the requirements of a
    very large customer that wanted remote access at higher baud rates.
    
    It's been mentioned here before, but is worth repeating that V2.0 SROMs
    or greater are required to support alternate baud rates.
    
    If using option #1 above, this is where the RCM_XXXXX console EVs come
    into play. They are: RCM_INIT, RCM_ANSWER, and RCM_DIALOUT. Hopefully,
    these are fairly self-explanatory. RCM_DIALOUT is described in detail
    in Appendix C. I didn't see any reference to the init or answer strings
    in my quick scan of the documentation.
    
    Hopefully, a 9600 baud rate is sufficient for your customer's needs and
    you can rely upon the Service Guide documentation to accomplish what
    you wish to accomplish.
    
    BC

    Thanks much for your reply. A minor nit however in that the COM1 port
    is a 9-pin D-sub port and not an MMJ. The same is true for COM2. The
    customer verified this as well as the diagrams in chapter 6 of the
    Alphaserver 4100 Configuration and Installation Guide. Based on what
    you said about COMM1 being an MMJ I would ask if there is a variant
    that uses MMJ's and not 9-pin ports?
    
    Regards,
       Dan