| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4739.1 | Read section 2.4.2 in release notes | RDGENG::PRATT | | Tue Mar 23 1993 11:34 | 26 |
| Hi Brad,
To increase the performance when looking into NODE via the IMPM, V1.3 now stores
all of the child entities in the MIR, instead of having to make excessive calls
to the NODE entity to find out what child entities are supported. Because of
this you have to update the MIR for all node entities.
You can either
a) Reregister manually each node
or
b)
$ define MCC_REGISTRATION_FM_LOG 01000000
$ mana/ent
MCC> register node *
MCC> exit
$ deassign MCC_REGISTRATION_FM_LOG
The same also applies to SNMP
Cheers
Ian
|
| 4739.2 | docs...what docs? :) | CTHQ::WOODCOCK | | Tue Mar 23 1993 11:50 | 6 |
| Ian,
Thanks much. Hadn't got to the docs yet: sacrilege, my fault.
cheers,
brad...
|
| 4739.3 | | MARVIN::COBB | Graham R. Cobb (DECNIS development), REO2-G/G9, 830-3917 | Fri Mar 26 1993 14:35 | 8 |
| Ian,
Does that mean that when we provide you with a new version of the DECNIS
software that implements a new module (DDCMP, FRBS, PPP, whatever) that you
will have to deregister and register each node manually to get look-into to
work? I would have thought that was unacceptable.
Graham
|
| 4739.4 | Manual update is required | RDGENG::PRATT | | Sat Mar 27 1993 15:44 | 10 |
| Graham,
You can either deregister, re-register each node, or else use the
toolbox to add the new module to the list of child entities supported.
Either way it is a manual process, and will need to be done for each
node that is registered. I'm not sure if once a node is registered that
you can do a 'mcc> register node *' using the FCL and it will then go
out and reregister everything. Maybe John Purretta can answer this.
Ian
|
| 4739.5 | Register Node * works if.... | TOOK::CAREY | | Tue Mar 30 1993 12:27 | 19 |
|
There's another note in here that details how to use the
"register node *" approach. Setting the registration logical
appropriately causes registration to process this request by
re-registering all of the children of all of the currently registered
nodes in your database.
Leaving this logical would cause this to be the normal behavior of
DECmcc, so that issuing a command to "register node router-1" would
re-register all of the children of router-1 if it was already
registered, and of course would register it normally if it wasn't
already registered.
Erik, do you have the note number describing this close at hand? We
did this to provide simple update tools for the migration from V1.2 to
V1.3.
-Jim Carey
|