unable to delete decnet node

[TMcB]

Hi Everyone

I need to delete a node from decnet.
I tried decnet_register / option 1 / show node 1.12
but I get :
Directory Service: Local name file
Error - Node name lookup failure
49::00-01:AA-00-04-00-0C-04:00
Number of nodes reported on: 0

Other options in decnet_register always give same reply :
Error - Node name lookup failure
This happens if I use node address 1.12 or node name

But I can still set host to node, and I can see it using ncl.
How do I deleted the node from ncl, when I cant see it in decnet_register?

The node name is stal02 - but in ncl it appears to include it as LOCAL:.BD3100

Thanks

> mc ncl show node 1.12
Node 1.12
at 2007-03-22-09:20:15.209+00:00Iinf

Identifiers
Name = LOCAL:.STAL02
Address =
{
(
[ DNA_CMIP-MICE ] ,
[ DNA_SessionControlV3 , number = 19 ] ,
[ DNA_OSItransportV1 , 'DEC0'H ] ,
[ DNA_OSInetwork , 49::00-01:AA-00-04-00-0C-04:21 (LOCAL:.BD3100) ]
) ,
(
[ DNA_CMIP-MICE ] ,
[ DNA_SessionControlV2 , number = 19 ] ,
[ DNA_OSItransportV1 , 'DEC0'H ] ,
[ DNA_IP , 0.0.0.0 ]
) ,
(
[ DNA_CMIP-MICE ] ,
[ DNA_SessionControlV3 , number = 19 ] ,
[ DNA_NSP ] ,
[ DNA_OSInetwork , 49::00-01:AA-00-04-00-0C-04:20 (LOCAL:.BD3100) ]
)
}

[Volker Halle]

TMcB,

the NCL SHOW NODE x.x command connects to the 'remote' node x.x and shows you information from that node.

If you want to obtain this kind of information for the local node, use:

$ MC NCL SHOW name, address

What do you really want to do ?

Volker.

[TMcB]

Hi Volker

from the local node, I dont want users to be able to set host to node stal02

[Volker Halle · Accepted solution]

TMcB,

there may still be the STAL02 node name entry in the session control naming cache. You can flush the cache with:

$ MC NCL FLUSH SESSION CONTROL NAMING CACHE ENTRY "*"

There may also be a logical name STAL02 on your local node, which translates to the remote node address.

Volker.

[TMcB]

Hi Volker

the "flush session" command resolved the issue.

I really appreaciate your help with this

Bye

[Colin Butcher]

Hello,

The naming caches are 'sticky', even over reboots. Always flush the naming caches after changing information in the DECnet namespaces.

You might find this http://www.downloads.xdelta.co.uk/vmstjv5%20feb2005/decnet%20article%20vms%20tj%20v5%20feb2005.pdf useful for some of the background to Phase V.

Cheers, Colin (www.xdelta.co.uk).