GS80:Memory Channel Adapter Error

[Learn_1]

We have Alpha server GS80 running in cluster environment via memory channel adapter and LAN.
Now when i enter show device command the memory channel adapter status shows "UNAVAILABLE" and error count is 1.
system is up and running in cluster environment.
how can i proceed to further investigate what is the actual problen which is causing the memory channel to unavailable.

[Willem Grooters]

Some hints to look at:

1. Does it show op in SRM (>>> SHOW DEVICE)
2. Does your operator console signal an error on this device? (There should be a method to log the whole startup-sequence in a logfile but I don't know how to achieve that)
3. It _might_ be you need to load the drivers (SYSMAN - I don't know the exact commands), normally done during system startup somewhere (SYSTARTUP_VMS - but that's probably a bit late). It _should_ be mentioned in the device manual/cover-letter
4. Does OPERATOR.LOG show a message on this device?
5. Check the errorlog, if it is a hardware error it will show up there.

(The numbers don't mean a strict order, just a sequence I would follow from start on)

[Mike Naime]

Willem summed it up fairly well for Troubleshooting purposes.

On the ES80 console MBM will take you from your VMS system to the MBM prompt. From there a SHOW ERROR may help show any problems with the status of your boards.

CONNECT will return you to your VMS session


If the MBM does not show you anything, you may need to shutdown the VMS system to the console prompt in order to do a SHOW CONFIG. This information does not seem to be available from the MBM prompt on my 1280.


If you have a support contract with Compaq/HP, Log a call and have them look at your ERRLOG.SYS file. We normally FTP this to the hardware group to look at.

[Mike Naime]

If this is an intermittent problem, Power cycling the box may start it to functioning again for a while, but will not fix your problem.

[Jan van den Ende]

(to realise the suggestion by Willem of a startup logfile):
create a file STARTUP.COM in (for cluster:EACH) SYS$SPECIFIC:[SYSEXE] with just one command:
$ @SYS$COMMON:[SYSEXE]STARTUP.COM -
/output=SYS$MANAGER:STARTUP.LOG -
"''p1'" "''p2'" "''p3'" "''p4'" "''p5'" "''p6'"

Remember:
- /OUTPUT must be the FIRST item to follow @
- you now have to explicitly specify SYS$COMMON because SYS$SYSTEM:STARTUP.COM specifies this file itself
- during an upgrade procedure you have to temporarily rename it away
- of course you can specify your own logfile choice, but be aware that it is activated BEFORE any STARTUP.COM activity is done, so you are restricted to the system disk, and on that, only VERY few logicals names are already there!

I am using it for some 20 years now, and there have been times when it helped me A LOT!

[Willem Grooters]

I would suggest one more thing: Split SYSTARTUP_VMS.COM into a part to be executed 'interactively' during startup (as current) and a part to be done in batch (SUBMIT with /LOG=/KEEP/NOPRINT - so you can login from the console before the whole startup procedure is completed. If you have a lot of things to be started, it might be useful. Also, you are able to prepare to control your startup procedure - eventually without having to change startup files.
My own system works that way (not for 20 years, it's not that old).

[Vinit Adya_1]

Memory Channel Adapter is unavailable is normal behaviour when the adapter is being used:

I have dual MC adapters on my GS140:
Device Device Error
Name Status Count
MCA0: Unavailable 2
MCB0: Unavailable 2

Just to be sure you are using MC check the following

$sh cluster/conti
command> add circuit
command> add counter

You will see your MC interfaces as "OPEN" and counters incrimenting.

Hope this helps

[Ian Miller.]

On the question of logging of output during startup then set system parameter STARTUP_P2 to "D" to send output to SYS$SYSTEM:STARTUP.LOG.
(remember to manage the number of versions of this file)

Other values of STARTUP_P2 which can be included are

V - enable verify in STARTUP.COM
C - output of information messages by STARTUP.COM
P - enable verify during execution of DCL procedures called by STARTUP.COM