[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

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

2855.0. "Node Reachability - query end node directly?" by PJVAX::LAMB (Peter Lamb - GSG Santa Clara) Sun Apr 26 1992 02:16

    Hello,
    
    Perhaps the answer to this is obvious but I'll ask any way!!!...
    
    In the rule examples in the 1.2 docs for node reachability (for
    DECnet IV nodes anyway) the only example for determining reachability
    is through the router.  
    
    My question is whether there is any way to directly query the 
    individual (like the IP_reachability)?
    
    My problem is that if I tell the router to tell me the status of
    all the nodes in my domain half of them are indeterminate since they
    are in another area.   BTW the wild card capability in 1.2.7 works
    and works great (except that I can't figure out a way to exclude
    only nodes in one area).
    
    Regards,
    
    Peter Lamb

T.R	Title	User	Personal Name	Date	Lines
2855.1	try Ping	TOOK::MATTHEWS		`Mon Apr 27 1992 09:20`	4
	For IP nodes, try a PING via the SNMP AM. The example in the doc is DNA4 related. Future versions should have both IP and DNA examples. wally
2855.2	What about DECnet	MUTTON::LAMB	Peter Lamb - GSG Santa Clara	`Mon Apr 27 1992 15:18`	15
	Hi, Maybe I should rephrase my question. What about DECnet is there any way to directly query the reachablity of DECnet nodes with out asking the router? Additionally, what about when you have multiple DECnet areas (normal + hidden nodes) in your domain. A NODE4 * remote node * rule generates a lot of error messges when it tries to ask an area 30 router about the status of an area 63 node. Peter
2855.3	pick your own	TOOK::CALLANDER	MCC = My Constant Companion	`Fri Jun 19 1992 14:46`	3
	My way is to have a seperate domain for each area and then use a single wildcard rule on state <> up; this will poll onlly those entities in that domain. Just a suggestion.