| 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 |
Hi All,
We (DEC Munich) have recently installed DECMCC V1.2.3
at a customer site (Siemens) and the installation has started
to become somewhat problematic.The setup we have is as
follows:
(a) HARDWARE: DECstation 5000/133
96MB Memory
450 MB swap space
2 x ethernet interfaces
(b)SOFTWARE: Ultrix V4.3
DECmcc V1.2.3
DECnet OSI
The network consists of 8 OSI nodes(Decstations with Ultrix)
4 DECnis routers
13 DECserver 700s (SNMP)
2 FTVaxen running VMS with the OSI extensions
The network itself is a dual lan with each workstation
(including the DECmcc management node) and each of the FTVAXEN
being attached to LAN 1 via ln0 and to LAN 2 via ln1.
I have configured the MCC station according to the instructions
in the release notes and the Ultrix install guide. The problem
we have now is, that when we start up alarms and notification, the
alarm rules only fire once and then they become disabled due to
the following error:
data not returned due to lack of
return data buffer space.
Perhaps I should also mention that the MCC station is the sink node
for the DECnet OSI events. I assume however that the error has
nothing to do with this last fact. This phenomenon has only started
to occur recently and nobody has changed the node's configuration
since the installation.
If anyone can point me in the general direction of some configuration
guidelines for DECmcc Ultrix or indeed solve the problem directly,
(which would be heavenly) then that would be great and Siemens
grateful.
Thanks in advance
Denis
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4569.1 | more info, please | TOOK::S_KO | Hoot mon! | Mon Feb 22 1993 17:52 | 5 |
do the rules apply to your DECnis routers? or does this occur for all
rules? can you use ncl to make the request that the alarm rule is
trying to make?
| |||||
| 4569.2 | Yes in both instances ! | MFRNW1::DENIS | Tue Feb 23 1993 04:41 | 13 | |
Hi,
Yes to both questions. The error occurs with the DECnis's
and with ncl I can examine any entity I wish.
For example I can do a "show node <some node 5> csmacd station"
in ncl and it works.
But.......
the same command via the Iconic map will result in the error
message in .0.
Denis
| |||||
| 4569.3 | what's the command? | TOOK::PURRETTA | Tue Feb 23 1993 11:57 | 6 | |
Would you post the exact command that fails (the "SHOW NODE" command)
and I'll look to see if we made a fix in that area during the V1.3 release
cycle. I'll also try the command over here to see if I can reproduce
the problem you're seeing.
If you could post the alarm rule as well that may prove helpful.
| |||||
| 4569.4 | DNU_OSI note 499 | TOOK::PURRETTA | Tue Feb 23 1993 12:06 | 3 | |
It was pointed out to me that there's a similar problem mentioned
in the DNU_OSI notes file, note #499. This problem may be related.
| |||||