| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 265.1 | re: .0 | BARREL::LEMMON | | Mon Aug 20 1990 11:58 | 42 |
| > We are running the DECmcc-BMS UT1.0.1 software on a VAXstation 3100
> Model 30 running VMS V5.3 and we have a question regarding the REGISTER
> command. Should DNS subdirectories always be used now whenever
> registering any entity? For example:
>
> MCC> register snmp ipdevice
> or
> MCC> register snmp .mcc_snmp.ipdevice
>
> MCC> register bridge 800to400
> or
> MCC> register bridge .mcc_bridge_backtranslation.800to400
>
It is not "required" to register all global entities using a DNS
directory. I would say that it is recommended. This is because
you reduce the clutter in the DNS root directory.
Also, I noticed that in your example you specify the directory
mcc_bridge_backtranslation. I don't think that it is a good idea
to use this directory because the BRIDGE AM uses it internally. Create
another directory (e.g., MCC_BRIDGES)
> The release notes seem to imply now that one should specify DNS
> subdirectories when registering ANY entity. However, the conversion
> utilities, MCC_NODE4_LOAD.COM and MCC_RBMS_CONVERT_MAIN.EXE, generate
> *.TMP files with DNS subdirectories specified for the NODE4 entities
> but NOT for the BRIDGE entities. I used the MCC_DNS_SETUP.COM
> procedure to generate my DNS directories.
>
> Can someone provide me with clarification on this issue? Also, if I
> can use DNS subdirectory specifications for all my entities, can I correct
> the situation merely by the ERASE and REGISTER commands?
>
You can use DNS subdirectrory specifications, providing the DNS directory
exists, when registering all global entities.
Use the DEREGISTER command instead of the ERASE.
/Jim
|
| 265.2 | Bridge AM internal? | WLYWLD::BRIENEN | Chris Brienen - DECmcc (non-DECnet) AMs | Mon Aug 20 1990 13:54 | 7 |
| Just a nit:
The .mcc_bridge_backtranslation directory is used by the
MCC_DNS Routines (maybe Configuration FM, too?).
The Bridge AM accesses (reads) it indirectly by calling
MCC_DNS routines to translate name <-> address(es).
|
| 265.3 | tcp/ip ain't decnet | MKNME::DANIELE | | Tue Aug 21 1990 09:37 | 19 |
| > You can use DNS subdirectrory specifications, providing the DNS directory
> exists, when registering all global entities.
Nope, not SNMP. The name you use in a REGISTER SNMP command must be
a known host name. That is, it is either in UCX's local host database,
or it is a resolvable internet domain name ( assuming you have enabled
the UCX V1.3 BIND resolver ).
Neither of these have any connection whatsoever with DECdns, so
a name like '.mcc_anything.router3' is almost certain to fail.
There is a dns subdirectory used by mcc to process SNMP entities, but
that's for private use by mcc.
Hopefully the TCP/IP SNMP AM Use book and release notes cover this
sufficiently...
Regards,
Mike
|
| 265.4 | re:.3 | BARREL::LEMMON | | Tue Aug 21 1990 14:59 | 6 |
| If this is the case, all SNMP global entities MUST be stored in the DNS root
directory. Couldn't the access module strip off the directory part of the
name prior to accessing the agent?
/Jim
|
| 265.5 | no | MKNME::DANIELE | | Tue Aug 21 1990 15:55 | 17 |
| SNMP entities are not identified by a DNS fullname, but rather by an
Internet Name. TCP/IP is not DECnet. TCP/IP has its own name service.
There is really no reason to register TCP/IP entities in DECdns,
other than the fact that it's a requirement for mcc to work.
Given that, there is no problem ( in my opinion ) in storing SNMP
instances in a specific directory in DECdns ( it's actually .mcc_ip ).
These instances are stored there to make DECmcc work, NOT to build
a DECdns namespace. The Internet name space already exists.
To add to the fun, Internet Domain Names look like fullnames:
foo.bar.yuch.punt
So the mcc dns routines have to take special care in handling them.
Hoping this is somewhat clearer,
Mike
|
| 265.6 | Probs registering SNMP entities | WARNUT::GALLACHERM | | Wed Aug 22 1990 07:01 | 19 |
|
Hi Mike,
I have installed the SNMP AM on our pet MCC system. I have had some
trouble in getting it to work:
DNS-E-NOENTRYEXISTS (or something)
From your last node I gathered that the .mcc_ip dierctory should exist
- once I created it via dns$control I was able to register SNMP
entities through MCC with no problems.
Should the SNMP access module installation create this do this
directory ???
Mark
-//-
PS Is theer anywhere I get get my hands on some SNMP icons ???
|
| 265.7 | BMS/Director function | MKNME::DANIELE | | Wed Aug 22 1990 09:21 | 10 |
| Hi Mark,
Yes, there was some confusion about this, sorry.
It's mentioned in the BMS/director release notes. I believe it will
be performed by the dns startup procedure that massages dns for mcc.
Regards,
Mike
|
| 265.8 | Th e COM file will be updated. | TOOK::JESURAJ | | Thu Aug 30 1990 01:29 | 4 |
| Yup !! The COM will be updated to create .MCC_IP directory be done
before DECmcc V1.0 ships.
/ Jesuraj
|
| 265.9 | SNMP Icons | MAVIC::D_MOORE | | Thu Aug 30 1990 12:58 | 11 |
|
Re: .6
PS Is theer anywhere I get get my hands on some SNMP icons ???
The Iconic Map PM and Domain FM do not support the SNMP entity at this
time. That is why we didn't supply SNMP icons for the Iconic Map toolbox.
This work is in progress and we are expected to support SNMP icons in the
next field test release. At this point, please do not try to find or
create SNMP icons.
- Dave Moore
Iconic Map and Domain pl
|