[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 |
2669.0. "How should Remote Node Entity work?" by ODIXIE::PEACOCKR () Tue Mar 31 1992 18:20
I am a little confused about how the Remote Node Entity works.....
Here's the scenario:
The DECMCC system is NODE_A. It is not a router. NODE_B, which has been
set up as a Phase 4 Icon is a router.
If I click on NODE_B and go into it's Remote Node Entity and then
select a specific "child" to show status - will I get the "reachable" or
"unreachable", or will I just get "- NOT RETURNED -" for state?
Is is possible to get the status returned on some nodes and nothing on
others? Is there something that has to be set up on these Remote Node
Children to allow them to return the STATE value?
Does the DECMCC system itself (NODE_A) have to be a Router to get this state
returned properly? (I didn't think so)
The reason I'm asking it that I talked to a customer who wanted to
create an alarm on Node Reachability using example C-2 in the 1.1
Alarms documentation and got an error message. Then he tried clicking
on NODE_B's Remote Nodes and all he got back was "NOT RETURNED".
(I realize that alarming on DECNET Events sinked from the Router might
be a better way to do this - but this is what he wanted to try)
Anyway, my overall lack of DECNET and DECMCC knowledge has me rather
confused. So if anyone could just briefly explain how this works and
what I should be seeing I would appreciate it.
Thanks,
Rick
T.R | Title | User | Personal Name | Date | Lines
|
---|