- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: --REGARDING NCL---
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-27-2007 04:26 PM
тАО02-27-2007 04:26 PM
--REGARDING NCL---
On our servers OpenVMS 7.3-2 is running and decnet phase V is installed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-27-2007 04:43 PM
тАО02-27-2007 04:43 PM
Re: --REGARDING NCL---
ALP $ mcr ncl loop loopback application name LOCAL:.alp2
Node 0 Loopback Application
at 2007-02-27-23:39:32.272-06:00I3.316
Start Time = 2007-02-27-23:39:32.247-06:00I3.316
But you'd better not be in a hurry if the
fellow at the other end is dead:
ALP $ pipe show time ; mcr ncl loop loopback application name LOCAL:.alpx ; show time
27-FEB-2007 23:39:56
Node 0 Loopback Application
at 2007-02-27-23:42:40.193-06:00I3.335
command failed due to:
process failure
The Connection to the remote mirror failed
Start Time = 2007-02-27-23:39:56.662-06:00I3.318
Reason = 32869556
27-FEB-2007 23:42:40
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-28-2007 10:58 PM
тАО02-28-2007 10:58 PM
Re: --REGARDING NCL---
DECnet will let you look at the adjacencies on the circuits. Do you have any DECnet routing nodes? If so then they will have a list of the adjacencies that they can see too.
Are you using "DECnet over IP" - if so then use TCPIP PING to probe the TCP/IP transpot layers.
Useful NCL commands are:
NCL> SHOW ROUTING CIRCUIT *
NCL> SHOW ROUTING CIRCUIT
Also to do the same thing for a remote node (typically a router such as a DECnis) use the form:
NCL> SHOW NODE
Another easy way is to hook up a LAN analyser to the local ethernet network and capture packets for a while (longer than HELLO TIMER, which by default in Phase V is 5 minutes [I think] - I usually bring it down to say 30 seconds or less). Assuming that you're using Phase IV compatible addressing then you'll see packets with source addresses of the form AA-00-04-00-xx-yy where xx-yy will give you the DECnet Phase IV address (byte reverse, then convert to decimal, then modulo 1024 gives you the area and the remainder modulo 1024 gives you the number within the area). SCSNODE =
This might help with some of the background:
http://www.downloads.xdelta.co.uk/vmstjv5%20feb2005/decnet%20article%20vms%20tj%20v5%20feb2005.pdf
Cheers, Colin (www.xdelta.co.uk).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-01-2007 08:48 AM
тАО03-01-2007 08:48 AM
Re: --REGARDING NCL---
you can check it very easily if you know decnet address of remote server and you can check decnet address of any system, give command in system prompt
$>>show net
Product: DECNET Node: horse Address(es): 12.23
Product: TCP/IP Node: horse Address(es): 10.192.0.23
As per your question now you can check it from another remote server by command
$>>set host 12.23
and remote node will connect definately if alive.
Atul Sardana.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-01-2007 09:27 AM
тАО03-01-2007 09:27 AM
Re: --REGARDING NCL---
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-01-2007 09:38 AM
тАО03-01-2007 09:38 AM
Re: --REGARDING NCL---
can mean many things. Whether DECnet or IP,
being able to "ping" a node tells you that it
can do something, but that's not the same as
telling you that it can do what you want it
to do.
For example, if you need to know if the Web
server is operating properly, then try to
download a Web page. While some failures
can stop both from working, "ping" and an
HTTP download can generally succeed or fail
independently. On the DECnet side, SET HOST
tells you one thing, but not everything.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-02-2007 12:14 AM
тАО03-02-2007 12:14 AM
Re: --REGARDING NCL---
$ if f$sea("node::login.com") .nes. "" then ...
Of course your proxy must be well defined then.
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2007 08:43 PM
тАО03-04-2007 08:43 PM