- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: DECserver-700-08
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-25-2006 06:25 AM
тАО02-25-2006 06:25 AM
When i go to
NCP>show node apsv2 char
Node Volatile Characteristics as of 25-FEB-2006 14:20:33
Remote node = 1.28 (APSV2)
Service circuit = EIA-0
Hardware address = 08-00-2B-BD-FC-1E
However when I want to connect to the node I get this message.
NCP>connect node apsv2
Console carrier protocol not available - already in use
Console carrier protocol not available - already in use
Target does not respond
I rebooted the decserver but still get the same message. Is there anything else I should do ?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-25-2006 06:52 AM
тАО02-25-2006 06:52 AM
SolutionI'm assuming that the MAC address you show is correct for the new server.
Allan in Atlanta
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-25-2006 07:17 PM
тАО02-25-2006 07:17 PM
Re: DECserver-700-08
how did you assign address 1.28 and name APSV2 to this DecServer, if you can't connect to it?
May be you need to connect via serial port 1.
Antonio
http://it.openvms.org
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-25-2006 07:21 PM
тАО02-25-2006 07:21 PM
Re: DECserver-700-08
a LTA port in status 'Connecting' is very unusual. Did this new DECserver ever work ?
Can you connect with a terminal to a serial port of the DECserver and issue SHOW SERVER STATUS (will report MAC address of current Console User) and SHOW SERVER COUNTER commands ?
For creating a session to a DECserver port from the OpenVMS system, two important things must be considered for the connection to work:
- the SERVER NAME on the DECserver must be the same as specified in LATCP> SET PORT/NODE=xxx. There may NOT be more than 1 server on the LAN with the SAME NAME !
- the port must be set to ACCESS REMOTE (or DYNAMIC) and the port name must match the name specified with LATCP SET PORT/PORT=xxx
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-27-2006 06:59 AM
тАО02-27-2006 06:59 AM
Re: DECserver-700-08
NCP> CONNECT NODE nodename
command, it uses the hardware (MAC) address.
When you replaced your broken DECserver, did you update the hardware address in NCP:
NCP> SET NODE nodename HARDWARE ADDRESS new-mac-address
If this takes care of your problem, then make the change permanent by executing the command again, replacing SET with DEFINE.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-27-2006 12:21 PM
тАО02-27-2006 12:21 PM
Re: DECserver-700-08
Allan in Atlanta
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-28-2006 02:23 AM
тАО02-28-2006 02:23 AM
Re: DECserver-700-08
All I show in the MOM$load dir is a file called WWENG2.SYS;1 Wher would I find the "other" file you mentioned?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-28-2006 03:24 AM
тАО02-28-2006 03:24 AM
Re: DECserver-700-08
DSVCONFIG.COM comes with the installation of the DECserver software kit (DSVxxx). Do a DIR SYS$HELP:*DSV*.REL* to see if it is installed at all.
For booting the DECserver, you just need the correct xxENGx.SYS file in MOM$LOAD. For connecting to the DECserver with NCP CONNECT, you need the correct HARDWARE ADDRESS configured in your DECnet node database.
Does the DECserver boot ? There will be OPCOM messages about the downline load ($ REPLY/ENABLE=NET). They will contain the MAC address of your DS700.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-28-2006 09:15 AM
тАО02-28-2006 09:15 AM
Re: DECserver-700-08
Allan in Atlanta
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-28-2006 05:23 PM
тАО02-28-2006 05:23 PM
Re: DECserver-700-08
>>> Console carrier protocol not available - already in use
This means someone on this system has been using the remote console carrier already.
At any one time, one one process is allowed to use the remote console carrier for that controller.
Thanks and regards.
Michael