| 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 customer running mcc in a pilot right now and they are trying to do DECnet Autoconfig for their 200+ node DECnet network. Some questions have come up about the autoconfig procedure which I've not been able to find answers to in the documentation, so I was hoping that someone monitoring this conference might help clarify. Q. When doing DECnet autoconfig several (98%) of the nodes being addressed time out while "waiting for data". What kind of data is autoconfig looking for? Are there certain objects that need to be up and running at the remote nodes for autoconfig to work properly? Several of the nodes being 'discovered' are PCs or Apple desktop devices running DECnet. I could possibly understand these devices timing out, but most of the routers and host also time out during the autoconfig process. Q. When doing DECnet autoconfig, what determines a LAN segment search for DECnet nodes? Even though option 3 "All DECnet Ph IV Nodes in a LAN" is selected, the search goes on for all nodes on the North American continent. I was wanting to limit the autodiscovery process to just one LAN segment, but 45 minutes later, it was still running with 9 out of 10 nodes timing out. A general description of how DECnet autoconfig works would be helpful since the "how" is not clearly defined in the documentation. Thanks . Merlin
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4628.1 | DELNI::JCH486::huang | JoAnn Huang | Thu Mar 04 1993 13:51 | 30 | |
Re. -1:
>>Q. When doing DECnet autoconfig several (98%) of the nodes being addressed
>> time out while "waiting for data". What kind of data is autoconfig looking
>> for? Are there certain objects that need to be up and running at the
>> remote nodes for autoconfig to work properly?
The "Time out ..." message is from the Autoconfig collector due to the failue in
executing the following NCP command:
NCP> TELL node SHOW EXEC CHAR
NCP> TELL node SHOW ACTIVE CIRCUITS STATUS
NCP> TELL node SHOW LINE line-id CHAR
>>Q. When doing DECnet autoconfig, what determines a LAN segment search for
>> DECnet nodes?
>> Even though option 3 "All DECnet Ph IV Nodes in a LAN" is selected, the
>> search goes on for all nodes on the North American continent. I was
>> wanting to limit the autodiscovery process to just one LAN segment, but
>> 45 minutes later, it was still running with 9 out of 10 nodes timing out.
Autoconfig is collecting the criteria according to whatever you put it in.
Option 3 should work as specified. I don't know why it doesn't work for you, but
I'll try to run some more test to verify it.
Regards,
JoAnn
| |||||