| Title: | Alpha Support Conference |
| Notice: | This is a new Alphanotes, please read note 2.2 |
| Moderator: | VAXAXP::BERNARDO |
| Created: | Thu Jan 02 1997 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 128 |
| Total number of notes: | 617 |
Customer had a number of sattelite VAX nodes (originally running 5.5-2) which were "triggered" via NCP to do a network load from another VAX (I believe was a 3200). Recently the Customer has upgraded the "remote" Vaxes (all 4000/60) to VMS 6.2 and has added local system disks. The node that forces the trigger is now a alpha 2100 (also running 6.2) however the procedure they run to do this function now fails. I suspect the problem has to do with the way MOP has been implemented on the Alphas but need some form of confirmation. Currently we have a situation where if the remote Vaxs are at the chevron prompt the trigger works. Of course this is of no use if during shutdown of these "remote" Vax's we get to the line "SYSTEM SHUTDOWM COMPLETE...etc etc" and cant get to the chevron (without going to site). Yes - I have read of the unsupported workaround to the chevron problem however the "issue" in the Customers mind is why did trigger work on the Vax but now does not work on the Alpha. I would have thought that we should be able to trigger a remote node whatever state the node was in.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 83.1 | STAR::STOCKDALE | Tue Apr 15 1997 11:47 | 4 | ||
The trigger command in LANCP has a bug in V6.2, send me mail if you want a fixed LANCP.EXE or escalate via IPMT to get the fix. - Dick | |||||