- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: UCX Communication Error
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
тАО03-16-2009 12:56 AM
тАО03-16-2009 12:56 AM
Re: UCX Communication Error
When DECnet Phase IV software starts on a LAN interface, it re-programs the MAC address of the LAN interface to use the DECnet MAC address. It is calculated as AA-00-04-00 (fixed prefix) and then the DECnet-address (in your case 10.20) by calculating area*1024 + node-in-area (e.g. 10*1024+20) and swapping the 2 hex bytes.
The interface will then ONLY recognize the newly programmed MAC address.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-16-2009 01:04 AM
тАО03-16-2009 01:04 AM
Re: UCX Communication Error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-16-2009 01:19 AM
тАО03-16-2009 01:19 AM
Re: UCX Communication Error
If you are programming the 'Highway Data link', is there no way to ping from the 'external device' ?
If UCX SHOW ARP does not show the MAC address of the 'external device' HDL01, the VAXstation has never received an ARP response from that device, so it cannot send an ICMP message to that device.
If you doubt that the LAN interface on the VAXstation does work correctly, it may be possible to test with a loopback connector and some console-level test.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-16-2009 01:30 AM
тАО03-16-2009 01:30 AM
Re: UCX Communication Error
Also can you please tell, what type of tests can be performed on the LAN interface on the Vaxstation.
Also can this be a problem with the connection of the BNC Cable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-16-2009 02:11 AM
тАО03-16-2009 02:11 AM
Re: UCX Communication Error
Here is a pointer to the 'VAXstation 4000 Model 60 Owner├в s and System Installation
Guide'
http://vt100.net/mirror/mds-199909/cd1/vax/pmarioma.pdf
Chapter 4 describes 'Testing your Ethernet Subsystem'. Note that you may need a AUI loopback connector and a T-Connector with 2 terminators for the ThinWire port.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-16-2009 03:41 AM
тАО03-16-2009 03:41 AM
Re: UCX Communication Error
Thanks for the document, it was helpful.
It is no pinging to the highway data link device, there was a problem in the position of the network switch and also a terminator had to be attached at the thin wire ethernet end.
Thanks again, i had been stuck with this problem for the past two weeks
- « Previous
-
- 1
- 2
- Next »