T.R | Title | User | Personal Name | Date | Lines |
---|
2516.1 | not ELMS, but ELM AM? | NAC::FORREST | | Thu Jul 13 1995 18:40 | 6 |
| Chris, I think the DECbridge 90 came out after ELMS reached
end-of-development-life. I think support was included in the DECmcc ELM
Access Module. Anyway, the DECbridge 90 does speak what I call the RBMS
protocol. That is what the DECagent 90 uses to SNMP proxy for it.
jack
|
2516.2 | Not Supported under ELMS or ELM-AM | MSDOA::REED | John Reed @CBO = Network Services | Fri Jul 14 1995 00:50 | 13 |
| Watch out for the 90FL using the ELAM.
You can partially use POLYCENTER Network Manager to see STATUS and
COUNTERS, but not Characteristics of the DB90FL. The DB90 seems
to behave nicely under ELAM. When you register the 90FL, it will
time out with an obscure error about being interrupted in the middle of
the process. But it will show up, and you can look at counters and
status usng the FCL, (but not the ICPM). If you are looking for
graphical representation of the device stick with HUBwatch....
If you want the alarms, and counter data, he ELAM will work.
JR
|
2516.3 | PDM elms | MOLAR::BRIENEN | Open Network Management Group | Tue Jul 18 1995 20:39 | 23 |
| Thanks for the feedback!
The application I'm currently working with is the elms command line
that ships with POLYCENTER DECnet Manager (PDM), which layers on top of
POLYCENTER Netview (PNV). This elms was ported from MSU, and is running
on Digital Unix and NT.
It seems to work fine with the DB90s (DEWGB) we have on the local
ZKO LAN, but the customer (and DEC support person who has a test
LAN with DB90s and 90FLs) can't get elms working to them. Connecting
to them via ccr works fine.
Since the Bridge Topology code in PDM uses either ELMS or SNMP (mib II
and bridge mib) to query for interface/spanning tree information, the
90's never correctly appear on their bridge map.
From Jack's response, the DB90/90FL should at least be supporting the
mini-ELMS protocol for the DECagent90, so the problem must lie some-
where else.
/Chris
|