| The DECNIS 500/600 management is very similar to the DEC WANrouter products.
They are fully manageable using Phase V network management (using the Phase
V AM from MCC or from NCL). This includes their Bridging functions, for
which we have defined a new Phase V management entity.
In addition, the Internet and bridging components are manageable (read-only)
through SNMP. This can be the TCP/IP AM or another SNMP management station.
This includes MIB-II, Bridge MIB and DEC Bridge MIB.
The ELM AM uses RBMS which the DECNIS does not support. I believe there is
work planned for the ELM AM to use SNMP (but I may be wrong).
No code changes are required to DECmcc V1.1 to manage the DECNIS products.
As they extend the Phase V network management in some ways, the data
dictionary that shipped with V1.1 is not complete for the DECNIS -- there
are some extra entities and attributes. I hope to work with the MCC group
to make sure that the dictionary shipped with V1.2 includes all the DECNIS
additions. For that reason, the SPD will say that V1.1 is required and V1.2
recommended (assuming it is shipping by the time we ship, which is likely).
I believe that the TCP/IP AM currently shipping includes MIB-II, the Bridge
MIB and the DEC Bridge MIB -- can anyone confirm or deny that?
For more information on the DECNIS products use the notesfile on
NOTED::DECNIS.
Graham Cobb
DECNIS Software Project Leader
|