[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference mvblab::alphaserver_4100

Title:AlphaServer 4100
Moderator:MOVMON::DAVISS
Created:Tue Apr 16 1996
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:648
Total number of notes:3158

497.0. "RCM setup problems" by PTOSS1::CYPHER () Sun Feb 16 1997 07:04

    I have a new customer that will have their two node (same cabinet)
    4100 VMS cluster managed remotely. I want to provide our remote group
    with maximum flexibility. With this desire in mind, I read this notes
    file and attacked the VGA0/COM1/RCM combination to test capabilities.
    I set console serial & init'd for starters. I used my laptop serially
    into COM1 via DB9 connectors. I checked the "combo" card on both cpu's
    & found I had one each rev A & C, refering to the diagram in 419.0.
    (Things-that-make-you-go-hummm?) Anyway, I removed the J5 jmpr on the
    C-rev module, verified J11 blk/yel went into the p/s, J7 on, J8 cable
    and J6 red/blk are connected to PCI backplane. On the rev-A module, J10
    yel/blk go into p/s, J6 is off, J5 goes to PCI backplane but is NOT
    connected (the jack thereon has a black jmpr on it) and J7 cable does
    connect to the PCI bkpln. The external cabinet-supplied 12v cables are
    connected to each rack-mounted cpu box, & measures 11.9x vdc.
    
    	I can get into RCM mode but cannot power cycle either system. Using
    the default ^]^]rcm, I do RCM> ENABLE and after perhaps 10-15 seconds
    receive   *** ERROR *** enable failed ... on both systems. All the 
    while I am attached to COM1. I attached a MultiTech modem to the RCM
    port in AT mode thinking the RCM needed to chat to enable. Though my
    modem cable is suspect, my experiment failed. Perhaps I will try a
    known good DB9->DB25 modem cable. My STATUS commands result in the
    following:
    
    	Firmware rev:	V1.0
    	Escape seq:	^]^]rcm
    	Remote access:	disabled   (cannot get this to "enabled")
    	Alerts:		disabled
    	Alerts pending:	no
    	Temp (C):	23.0
    	RCM power control: ON
    	External power:    OFF (I measured 12v here?)
    	Server power:	   ON 
    
    On the rev-A module, I can POWEROFF/POWERON and only the "ext pwr"
    status toggles from on/off, etc. I am really confused about the true
    capability of this RCM feature. I know I can put a modem on COM1 and
    the customer can use VGA0 and a remote person can dial in & do most
    anything, as is, excepting power cycle the box(es).  All I need is a 
    good 9600 modem & phone line on each cpu. For security, I am considering
    putting an old MDS01 on each COM1. Can you please provide some
    thoughts?
    
    Thank you,
    Dennis
T.RTitleUserPersonal
Name		DateLines
497.1POBOXB::BAKMon Feb 17 1997 13:205
I would recommend that you upgrade the A rev RCM to a C to insure you get full
functionality from the RCM. The diff is in how the RCM handles remote power
down/up.

	Dennis
497.2SERIES::CIAFFITue Feb 18 1997 09:5314
Dennis,
	have you set up the modem initialization string from the SRM console ?
When the console comes up take a look at the environment variables for the
RCM by typing >>>ls rcm*.  If I remember correctly the proper way to set it
up is >>>set rcm_init "at&f0e0v0x0s0=0".  That should be enough to enable the
modem.  Then from the serial line you can enter the rcm escape sequence, enter
rcm mode and type 'enable'.  If that doesn't work you may have to fiddle
with the init string.  Take a look at note 471.9 for more info.
	Also, make certain that you've entered a remote access password from
rcm mode. RCM>setpass otherwise you won't be allowed to connect once you call
in.


Marco
497.3MAY30::CUMMINSTue Feb 18 1997 10:088
    Re: -.1
    
    You would actually use:
    
       P00>>> SHOW RCM* 
    
    to display RCM init string and other RCM-related EV settings.
497.4RCM works great - here's some tipsPTOSS1::CYPHERFri Feb 28 1997 14:5947
    Well we finally got a phone in the room with the 4100's and began
    troubleshooting. After several problems, I worked great. This is a
    very impressive interface. Here are some tips. 
    
    1) We were using a MultiTech MT2834BA modem with an off-the-shelf
       9 pin-to-25 pin modem cable attached to the RCM port. This modem
       is capable of 28.8 but throttled to 9600 per our dialup speed.
    
    2) The RCM>ENABLE command worked fine with the modem properly attached
       and powered up. Entering RCM>STATUS showed proper operation.
    
    3) The console variables for RCM ended up being set to:
    
    		rcm_answer	ATXA
    		rcm_init	AT&F0E0V0X0S0=1	
    
    	Note the "S0=1" is necessary for the modem to auto-answer. If
    	left as "S0=0" no connection is possible. I believe the book is
    	incorrect.
    
    4)  With the password set, we were able to dial the modem from a 
    	HiNote running KEAterm at 9600-8-N. The modem answered and after
    	8-10 seconds the # password prompt appeared. Upon proper password
    	entry, several more seconds passed and we were attached to the
    	port. I is strongly suggested to be patient. Do not hit <cr> or
    	any other keys till the # appears. Likewise after entering the
    	password. Once you have control, you really have control!
    
    5)	Suggest setting SRM console variable "console" to serial. This
    	provides visibility for ALL console streams from init stuff to
    	operating system boot output. 
    
    6)	When booted and logged into the operating system (VMS in my case),
    	entering the escape sequence for RCM access yields the RCM>
    	prompt. In the case of a runaway machine, the "reset" and "halt"
    	RCM commands are the same as pushing the buttons! RCM>QUIT gets
    	you back to the op/sys prompt. Neat stuff!
    
    7)	RCM>poweroff (and poweron) work great as well, but I suggest using
    	them from a shutdown operating system. 
    
    I hope these notes help. The advice I received herein helped me deliver
    this service to a now-satisfied customer.
    
    Thanks to all,
    Dennis
497.5SERIES::CIAFFITue Mar 04 1997 14:4325
>>>    3) The console variables for RCM ended up being set to:
>>>        
>>>    		rcm_answer	ATXA
>>>    		rcm_init	AT&F0E0V0X0S0=1	
>>>    
>>>    	Note the "S0=1" is necessary for the modem to auto-answer. If
>>>    	left as "S0=0" no connection is possible. I believe the book is
>>>    	incorrect.


    
Dennis, the way the firmware is setup in the server management corner dictates 
that auto-answer in the modem be turned off.  The code doesn't allow a user
to connect unless there is a valid password and remote access has been enabled.
S0=1 turns on auto answer on the first ring.  Even if there is no valid password
a user will still be able to get the modem to answer.  It could be that the
code works fine in the case where the password has been set and remote access
enabled correctly.  What's confusing is the fact that you couldn't get it to
work with S0=0.  What does your modem manual say about S0 ?  Maybe you need
to set it to some other value to disable auto answer ?

Keep in mind that the modem you are using is not one of the ones we tested so
some of it's behavior may be unpredictable.

Marco