| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2107.1 | Nothing exists at the moment... | CHRISB::BRIENEN | DECmcc Bridge|Station|SNMP Management. | Thu Jan 16 1992 16:36 | 7 |
| The conversion utility that does ETHERNIM ->MCC conversion only does
STATION and BRIDGE at the moment.
Is this function viewed as important?
Most people seem more concerned about getting Node4 information from
the NMCC/DECnet Monitor Database or NCP...
|
| 2107.2 | Yes please | TOOK::R_SPENCE | Nets don't fail me now... | Thu Jan 16 1992 17:51 | 6 |
| I have found that many sites have entered reference info into Ethernim
for all items on the LAN. That includes the DECnet nodes.
Also, NCP doesn't store reference info.
s/rob
|
| 2107.3 | Definately YES | CAPITN::BROWN_GR | a downunder upover | Fri Jan 17 1992 17:07 | 8 |
| I agree that it is very desirable to extract Ethernim data. Where we
are converting from a uVAX running DSP 1.2* there is usually a lot of data
been entered in the Ethernim database. It is very convenient to copy it
across when upgrading.
Anyway who uses NMCC/DECnet Monitor?
Graeme
|
| 2107.4 | Not planned for V1.2 | CHRISB::BRIENEN | DECmcc Bridge|Station|SNMP Management. | Mon Jan 20 1992 17:53 | 17 |
| The ENIM -> MCC Conversion Utility iniotially avoided Node4 for a
couple of reasons:
1. The REGISTER NODE4 sytntax was not stable during the
time we were writing the utility
2. A .COM file to extract Node4 instances out of the NCP
database was considered the preferable way to populate
MCC with Node4 entities
No work is planned RE: extracting Node4 information from the ENIM
Database for DECmcc V1.2.
However, assuming that someone *did* do such a thing: is there a
reliable algorithm for generating the Node4 entity's FullName from
the DECnet NodeName?
Chris
|