Yes the NCP commands work on a standalone VMS (VAX and Alpha) system. Possinle reasons for the failure (that I can think of....): - wrong circuit name - DECnet not configured - phase 5 running, not phase 4 - insufficient privileges BTW you must use LAT, IP or a locally attached terminal to perform this trick. What happens if you do this, assuming that EWA-0 is correct:: $ mc ncp def circ ewa-0 service enabled $ mc ncp set circ ewa-0 state off $ mc ncp set circ ewa-0 state on Hans -----Original Message----- From: Mark Wickens <mark at wickensonline.co.uk> Sender: owner-hecnet at Update.UU.SE Date: Thu, 15 Sep 2011 10:14:28 To: <hecnet at Update.UU.SE> Reply-To: hecnet at Update.UU.SESubject: [HECnet] Satellite configuration/NCP crash Guys, I'm following the procedure in the Cluster manual, pp10-9, to configure a VAX satellite from an alpha boot node, and I'm getting a system crash. My question is whether I need to run this procedure with the Alpha in standalone mode, or whether this is a situation requiring a patch, or whether I can get away with something different. This is the first part of the procedure to enable the MOP server. The second part is to configure the MOP service for the VAX satellite. The Alpha is running OpenVMS 8.3 Thanks for the help, Mark. The log is: $$ mcr ncp NCP>define circuit ewa-0 service enabled state on NCP>set circuit ewa-0 state off NCP> %%%%%%%%%%% OPCOM 15-SEP-2011 10:03:37.64 %%%%%%%%%%% Message from user DECNET on SLAVE DECnet event 4.7, circuit down, circuit fault