[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
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 |
1408.0. "Cannot register nodes, all else well." by HANNAH::B_COBB () Tue Aug 27 1991 22:24
I have a problem with MCC (V1.1.0) that I cannot figure out.
2 days ago I registered about 50 stations. All registered
ok. I used the Iconic map to move them around and such and
have done operations on them such as show counters and such
and they all work. Today I started MCC and my default domain
comes up ok, I can do operations but I cannot add any new
stations either fron the Iconic map ot the command line interface.
the error is :
The Requested Operation Cannot be Completed:
MCC Unhandled Service Reply = Cannot Communicate with Target
I cannot add ANY stations. All network functions work from the MCC
host to the nodes I want to add. There are no network problems that
stand out here. Ethernim, which runs on the same host, can see and
talk to all the nodes that fail upon adding with MCC.
The only things that have changed is that I reinstalled RDB on the HOST
node. That is the only thing that happened between the time it was
working and the time it failed that I know of. All other products
work fine, ELMS, TSM, LTM, and Ethernim. The nameserver is up and
running, when I bring up the Iconic map, I see a links from the MCC
host to the nameserver. I tried shutting off all of the network
management stuff (LTM, ETHERNIM and such) and then trying it again
but no luck. I get failures adding from the Iconic map and the command
interface.
What is the troubleshooting path for this problem?
Any help is appreciated.
T.R | Title | User | Personal Name | Date | Lines |
---|
1408.1 | | HANNAH::B_COBB | | Wed Aug 28 1991 17:19 | 5 |
| The problem turned out to be user error. I did not include an
alternate address when I registered the stations. I have registered
them ok now.
|