| 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 |
Hello,
I would like to have a much clearer idea of how DNS is used by DECmcc,
in particular when it comes to storing information about child
entities.
Is there a document which tells us in more detail how it all works?
Along the same line of thought, I would appreciate more detail in the
SRM on the use of the DNS routines, when to use mcc_dns_get_identifiers
as opposed to mcc_dns_read_attributes etc...
Any help on this subject would be immensely appreciated as I have a
customer who asks *lots* of questions.
Thanks all, have a nice week-end !
Philippe.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2642.1 | A simple example of child entity info | TRM::KWAK | Wed Apr 01 1992 17:08 | 102 | |
RE:.0
As far as I know, there is no document about how MCC stores
configuration info on DNS. However, I am planning on writing one
for MCC developers (and maybe for Customer Support group) after
DECmcc V1.2. It may be availalble in May or June.
A DNS object stores all information about Global entity and its child
entities' identifiers and attributes.
These are stored as binary attributes of the DNS object, and these
binary attributes are readable using DNS 1.1 on VMS.
Using DECdns 2.0 dnscp on Ultrix, you can see the binary attibute names
and their values in hex representation. The attribute values are
stored in ILV-encoded form, and thus do not make sense at all.
For example, SNMP's child entity ATTable (address translation table
can be stored as follows:
MCC> regi snmp .wk.MCCTS1 att ( 1, 16.20.144.52)
MCC> dir snmp .wk.MCCTS1 att *
SNMP MY_NS:.wk.MCCTS1 ATTable (1,16.20.144.52)
AT 1-APR-1992 15:19:32
Directory successful.
atKey = ( 1,
16.20.144.52 )
IN DNS, the DNS object's attribute name and its contents are:
(The binary attribute name encodes the MCC entity class hierarchy:
class 18 (SNMP 12 in hex) - class 3 (ATTable)
----"MCC"
| -- indicates child entity
| | -- depth of entity spec hierarchy
| | | __ class code for SNMP (18)
| | | | -- class code for ATTable
| | | | | __ Unused class code in hierarchy
| | | | | |
======== = = ==== ==== =======================================
%X 4D43435F 1 2 0012 0003 0000 0000 0000 0000 0000 0000 0000 0000
==
|_ means "binary attribute"
)
Attribute %X4D43435F120012000300000000000000000000000000000000: SET
Value: a0 82 0 67 bf 81 7b 82 0 43 a0 82 0 e 81 1 2 82 1 0
83 1 0 84 1 0 85 0 a1 82 0 2d 81 1 1 82 1 3 83 1
63 84 1 f a5 82 0 1d a1 82 0 9 83 1 1 84 1 23 85 1
1 a2 82 0 c 83 1 2 84 1 49 85 4 10 14 90 34 bf 81 7c
82 0 18 bf 63 82 0 13 81 1 f 83 1 0 a4 82 0 9 81 1
1 82 4 10 14 90 34
==> Binary attribute value in ILV-decoded format:
[ 0 ] (
[ 251 ] (
[ 0 ] (
[ 1 ] 02
[ 2 ] 00
[ 3 ] 00
[ 4 ] 00
[ 5 ]
)
[ 1 ] (
[ 1 ] 01
[ 2 ] 03
[ 3 ] 63 -- c
[ 4 ] 0f
[ 5 ] (
[ 1 ] (
[ 3 ] 01
[ 4 ] 23 -- #
[ 5 ] 01
)
[ 2 ] (
[ 3 ] 02
[ 4 ] 49 -- I
[ 5 ] 10 14 90 34
)
)
)
)
[ 252 ] (
[ 99 ] (
[ 1 ] 0f
[ 3 ] 00
[ 4 ] (
[ 1 ] 01
[ 2 ] 10 14 90 34
)
)
)
)
I hope this helps.
William
| |||||