| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
Ths DECmcc Director V1.3 SPD said VAXft 310 is not supported. A
customer wants to use it for purpose of development and backup to a
operational NMS.
(1) Is there any technical reason why unsupported?
(2) Any chance have it work in unsupported mode?
Faraday
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4852.1 | TOOK::MINTZ | Erik Pavlik Mintz | Fri Apr 09 1993 14:50 | 13 | |
There are several possible reasons why a processor might be unsupported, and I don't personally know which noe fits the VAXft 310. 1) It is a bounded configuration with less than the minimum memory specified in the SPD 2) The CPU is too slow 3) We were unable to gain access to the processor for testing, and customer demand was not sufficient to hold up shipment. Perhaps someone else knows the exact reason for this model. | |||||
| 4852.2 | FT310 is too slow. | TOOK::R_SPENCE | Nets don't fail me now... | Tue Apr 13 1993 15:18 | 13 |
The reason is clearly that the CPU is too slow. The V1.2 SPD stated
that the minimum cpu capacity was 6 vups. The FT310 is 3.8 vups.
I believe the V1.3 requirements for cpu were the same although
memory requirements did increase to 48mb (I think).
The software will likely run on the 310 but Digital will not support
it's use nor respond to problems encountered.
Likely problems you will encounter are alarm rule exceptions from
scheduled time past. Also, things like graphs will encounter goose
eggs more frequently.
s/rob
| |||||