| 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,
5847 Anyone !@!! ........ here's another problem, :- trying to
register a DECnis Box as a Phase V node from the Iconic Map I get the
following informational message -
'Access definition for an attribute or argument is not in the dictionary'
Anyone any ideas on this one ?
Thanks
/Brian
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5859.1 | Phase V Node Registration Problem again | KIRKTN::BFJONES | Wed Feb 09 1994 11:26 | 4 | |
5859 Anyone.........
/Brian
| |||||
| 5859.2 | looks like a mismatch between dictionary and entity | TAEC::FLAUW | Marc Flauw, CEM Technical Office, VBO | Thu Feb 10 1994 03:01 | 31 |
Brian,
I am not a Phase V specialist and if there is one, I will glad if he
(or she) can bring additional info on this problem, but the message
itself seems quite explanatory :
> 'Access definition for an attribute or argument is not in the dictionary'
A quick scan of the message file shows its code as PM_DICT_NO_ACCESS.
I think it means that the Iconic Map PM did not find in the dictionary
the information related to one of the attributes (or argument) returned
from the DECnis. Which means that it is likely to be a mismatch between
the MCC Phase V model and the DECnis model.
The Iconic Map PM, I think, does quite a lot of commands during a
registration. I would suggest you to retry using the FCL PM
registration and show all attrib commands for the node entity and its
various sub-entities to see if you get some error which would point you
to the mismatch.
I don't think that the FCL PM will returns the same error code. As the
original error returned by the mcc_dict routine is NOENTITY, you might
get this error instead.
Hope this helps,
Best regards,
Marc.
| |||||
| 5859.3 | MARVIN::COBB | Graham R. Cobb (Routing), REO2-G/C2, 830-3917 | Mon Feb 21 1994 13:40 | 16 | |
If there is ever another version of MCC shipped then this problem should go away. It is probably complaining about one of the new NODE attributes defined for SNMP support. There isn't anything you can do about it except get the dictionary updated with the latest NODE MSL (don't ask me how to do that!). It is a design fault in MCC bug that it ever displays a message (at least it doesn't bomb out). It is a safe working assumption that the node that is being managed will very often be a newer release than the one which was current when th manager was compiled! Getting extra information back should cause no comment at all. It is poor design like that that caused ISO to invent the completely unworkable "allomorphism" mechanism -- which is the single featue most likely to mean that OSI CMIP will never be adopted widely. Graham | |||||