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 |
Hello, It seems that there are no entries in this notes conference defining the proper configuration guidelines for MCC. Things like: Performance charateristics for VAX 4000 model 60, VAX 4000 models 200,300 etc. VAX 6000-200,300,400 etc. Memory Specifics : 32,64,72 Application Specifics: # of supported DOMAINS with max alarm rules on a VAX 4000 model 60 Areas to beware of when configuring MCC monitoring hosts. The customer I am dealing with is presently using a 4000 model 200 and would like us to prepare a growth path plan for MCC and identify all the resources so that they can forecast what their system requirements will be over the next few years. Sounds somewhat like a benchmark..... Thanks, Michael
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
2837.1 | Any Statistics or Estimates?? | 36766::PICARD | Fri Apr 24 1992 11:11 | 11 | |
Hello, I would like to gather some performance data for MCC from somewhere. Preferably, from a reliable source. DECnet overhead, I/O characteristics, CPU utilization, the max. number of devices that can be monitored.... Performance bottlenecks? Any ideas or thoughts? Michael | |||||
2837.2 | TOOK::MINTZ | Erik Mintz, DECmcc Development, dtn 226-5033 | Fri Apr 24 1992 13:49 | 5 | |
I think the deafening silence you are hearing indicates that we are still gathering these numbers, and don't have anything ready to publish yet. -- Erik | |||||
2837.3 | 36766::PICARD | Wed May 13 1992 15:33 | 10 | ||
Erik, Thanks for the response. As soon as there is any information can you let us know where the information can be had. Our customers really need to have a base to estimate what types of resources that they'll need to support their enterprise networks. thanks, Michael |