| 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 |
I have a shared netsupport customer that is having DNS woes.
We have 3 MCC systems on the Networkk, and other systems will be using
DNS. We seem to have conflicts due to multiple clearinghouses.
Using the DNS>show char dir . command we sometimes see our
clearinghouse, sometime theirs. As this is a shared site, someone
decided NOT to send the customer any DNS documentation. Are their any
guidelines and commands 'online' I can get for them? I don't think the
problem will be difficult to solve as Clearinghouses can update each
other and be mirror copies of each other (we just don't know how to do
that) or clearinghouses can be different, and not interfere with each
other. We don't know how to do this either.
I am a resident Customer Services engineer onsite here, and I would
like them to be happy with our equipment and software...
This brings me to ask the big question, is there anyone else out
there (you perhaps) that are supporting a 'shared netsupport'
environment? Not trying to knock our ANC, but what kind of
documentation do you provide for your customers? It would seem that if
we 'stick' software on their box, we should provide a book to let them
know how to manage it? If not, I don't feel DEC should charge against
their allotted phone-support time to get such questions answered.
Any help I can get on the DNS question would be greatly appreciated
since this is a large customer and they ARE looking at other vendors
stuff all the time. I'd hate to lose their business.
Thanks in advance,
John Carow
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2360.1 | NYFDIN::SAMBAMURTY | Raja | Tue Feb 18 1992 11:18 | 3 | |
I think if you use the REBUILD DIR . ....blah command, you should be
able to set one up as a master, and the rest as read-only servers. I
think this will/should provide more consistent display.
| |||||
| 2360.2 | Several problems - need info | TOOK::R_SPENCE | Nets don't fail me now... | Tue Feb 18 1992 11:49 | 32 |
Ok, you have multiple questions here. Let me start to adress them.
- DNS Problem
- Documentation problem
- Definition of Shared Support problem
In order to give you advice on the DNS problem I need to know lots more
about your configuration. For example;
How many NAMESERVERS are there (Clearinghouses reside on nameservers)?
How many NAMESPACES are there?
Are all of the Nameserver's clearinghouses in the same namespace?
Which clearinghouse has the master replica (Read/Write)?
Which directories are replicated? To where?
When were (in this whole process) the replicas created? By whome?
When was all this done relative to installing DECmcc and registering
things into DECmcc?
I really need to understand the situation in order to proceed. The
solution is going to depend on what happened, what was tried to fix
it, and in what order (unless you want to trash it and start over).
The documentation problem is related to the netsupport contract.
What was sold to the customer? In a shared netsupport environment there
must be a contract that defines things like who owns which hardware,
who owns which software, and who supplies which services.
If you don't have that, get to the account manager and demand it.
In general, if the customer purchased a software license, but not
the documentation set, they don't get the docs. Find out what was
sold to them.
s/rob
| |||||
| 2360.3 | More info needed | TOOK::R_SPENCE | Nets don't fail me now... | Tue Feb 18 1992 11:51 | 7 |
Oh, re .-1
What versions of everything are you running? DECmcc, VMS etc and
what are the harware platforms involved (cpu model, mem size, disk
config etc)??
s/rob
| |||||
| 2360.4 | re .2 information coming... | SCOBIE::JCAROW | OK...We'll try it... | Tue Feb 18 1992 21:29 | 6 |
re:.2 thanks for the replies, I'll have the additional information you
need tomorrow morning. Until then...
Thanks
John Carow
| |||||