| 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 folks, I have few problems with Chipcom Online System Concentrators. Problem is in EMM (Management Module) and behaviour is unpredictable. Customer has 7 concentrators. Configuration is star-like (6 is connected to 1 using fibers, two cannels between each others). And every concentrator have several twisted pair modules. EMM versions are 2.0 and 2.1. My problems is that SMTP and ping doesn't work all the time. I'm using DECmcc and Chipcom MIB extension. If I reset EMM module everything is ok after that. Both ping and SNMP works perfectly. And if I define alarms which are polling EMM, everything works fine several hours. But problems appears if I don't do any SNMP request to boxes. After few hours without SNMP communication behaviour is weird. If I do ping with datasize 64 and ethernet address is unknown (use ARP) response is alive. If address is known address is unreachable. With datasize 1 both works. But SNMP don't work ... It might take several hours or even days but every EMM module has the same feature... If I use same EMM module in our office in standalone Chipcom (with bridge module and EMM) it works fine forever. For me it seems to be bug but Chipcom UK says they have never seen this. I know there is problems with SNMP if EMM module has chip 18-00080.C. But these have chip 18-00080.B or D (some of those were updated from C to D). Has someone seen this? Rgds, //pasi (FNO/BSS/Telecom)
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4236.1 | V3.1 for EMM and V2.1 for OEBM... | ZTOIS1::VISTA | Renato VISTA, SIS Strasbourg, France | Tue Dec 15 1992 09:37 | 19 |
Hi,
I've met a few months ago some problem of Chipcom/Arpanet broadcast
frames which were not forwarded by OEBM V2.0 (Bridge module),
especially when I wanted to communicate from one hub to a second hub...
I don't know if you problem will be solved by them, but the last
versions of EMM and OEBM are
- V3.1 BASIC or ADVANCED, for EMM (Management Module)
- V2.1 for OEBM (Bridge Module)
If you have, for your customer, a maintenance contract, you normally
can get those last versions of firmware (updatable via a PC software).
Renato
| |||||