| 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 |
Any ideas on what could cause a healthy DECmcc 1.3 station to suddenly
report -
MCC> show bridge xx-xx-xx-xx-xx-xx all attrib
management protocol error
MCC>
This is not specific to the bridge entity and it seems to be related to
starting UCX but I can't see what's common to the two.
BMS was reinstalled and all seemed well for a day then we get that error
again. Any ideas?
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5697.1 | PLUNDR::LOWEG | WANTED!! A modern day Robin Hood. | Fri Oct 29 1993 08:16 | 6 | |
Are you using TSM ????
Gary .
| |||||
| 5697.2 | NPSS::WADE | Bill Wade, Network Systems Support | Fri Oct 29 1993 13:23 | 6 | |
re .1
Installed BMS and ELM AM/FM 1.3
| |||||
| 5697.3 | PLUNDR::LOWEG | WANTED!! A modern day Robin Hood. | Mon Nov 01 1993 06:32 | 7 | |
What type of bridges are you looking at when this error message is
returned ??
Gary.
| |||||
| 5697.4 | Is it registered? | TOOK::GUERTIN | I am never worng | Mon Nov 01 1993 13:29 | 4 |
Check to see if the bridge is registered or not. See if the message
changes after it is registered.
-Matt.
| |||||
| 5697.5 | Another situation with MANAGEMENT PROTOCOL ERROR | CSC32::J_MCCLELLAND | Off in the ETHERnet | Mon Mar 07 1994 10:42 | 50 |
I have been looking into a problem at Fermilab where the customer got a lot of this error type during network instability. I asked questions based on the prior replies in this note. Any ideas are welcome. John =============================================================================== | | I would like you to check this bridges' registration to see if it looks | normal. This response - management protocol error - happened on many devices, bridges and concentrators all of which seem to be registered correctly. | What type of bridge is this and at what rev level if you know it. This particular bridge is a Lanbridge 150 with firmware version 1.4. This error occurred to many different devices DECbridge 610 and DECconcentrator 500s. | | What else runs on this node, UCX, TSM, RBMS/DECelms, etc.? This machine runs TSM and RBMS/DECelms. | | Can you correlate this message with any other activity in your network? At the time this was happening we had a DECrouter trying to log to this machine. The Event logging account was not enabled so we were getting many logfails. Also we had what we think is a flaky Lanbridge 150. We saw a lot of collisions on the network but not a high utilization. We have since fixed the logging problem and removed the flaky 150 ( it was rebooting every few minutes) from the network and have not seen the error since. We depend on polycenter to tell us if the network is healthy so it would be useful to know what might cause these errors. Thanks Donna | |||||