| 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 |
Can someone explain this to me:
If I do:
MCC>show node4 *
I get:
Node4 DSP_NS:.DNA_NODE.SOUL
AT 9-APR-1992 15:14:52 Identifiers
Node not currently accessible.
But if I do:
MCC> show node4 soul all status
I get:
Node4 1.3
AT 9-APR-1992 15:16:07 Status
Examination of Attributes shows:
State = On
Physical Address = AA-00-04-00-03-04
Active Links = 2
Delay = 1
What is the difference? The reason I ask is because I'm trying to pin
down why alarm rules to test reachability show exceptions.
Node Soul changed it's address from 2.3 to 1.3 and is (and was)a router and
the MCC system went from being a router to end node. The same rules
worked before.
I'm sure it must be a DECnet problem, but I'm having trouble relating
the two products to see exactly what I should be looking for.
Any help would be greatly appreciated.
Rick
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2733.1 | Check your local node database against what is registered | TOOK::GUERTIN | Menagerie Control Center | Fri Apr 10 1992 11:11 | 7 |
I had a similar problem. It turns out that the node name (or address?)
in my local node database differed from the node name(/address) that
was registered. I believe that a wildcard use the node name/address
that was registered, but specifying the node name exactly may (I'm not
sure) just go to the local node database.
-Matt.
| |||||
| 2733.2 | where do names come from | TOOK::CALLANDER | MCC = My Constant Companion | Thu May 14 1992 09:57 | 2 |
* goes to your dns or local MIR
<name> goes to your ncp database
| |||||