- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- recievng NCP error upon reboot
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-22-2010 10:44 AM
тАО03-22-2010 10:44 AM
I am not sure why I am getting these errors on reboot. Network is fine. Any suggestions?
NCP-W-OPEFAI, Operation failure
Message from user DECNET on N058V6
DECnet starting
%SYSTEM-F-ILLIOFUNC, illegal I/O function code
%NCP-W-OPEFAI, Operation failure
%SYSTEM-F-ILLIOFUNC, illegal I/O function code
%NCP-W-UNRCMP, Unrecognized component , Circuit
Circuit = EWA-0
%NCP-W-UNRCMP, Unrecognized component , Circuit
Circuit = EWA-1
%NCP-I-NOINFO, No information in database
%%%%%%%%%%% OPCOM 22-MAR-2010 13:55:52.01 %%%%%%%%%%%
Later in the reboot process DECNET is started
%TCPIP-I-LOADSERV, loading TCPIP server proxy information
%%%%%%%%%%% OPCOM 22-MAR-2010 12:13:43.68 %%%%%%%%%%%
Message from user DECNET on N058V6
DECnet event 4.10, circuit up
From node 2.101 (N058V6), 22-MAR-2010 12:13:40.60
Circuit LLA-0
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-22-2010 11:26 AM
тАО03-22-2010 11:26 AM
Re: recievng NCP error upon reboot
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-22-2010 12:00 PM
тАО03-22-2010 12:00 PM
Re: recievng NCP error upon reboot
More information about your DECnet configuration would be helpful.
In the interim, I am more or less in agreement with Edgar. I suspect that you may not have accessible EWA-0 and EWA-1 devices.
As a start perhaps a LIST KNOWN CIRCUITS and a LIST KNOWN LINES from within NCP and a SHOW DEVICES from DCL would be helpful.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-22-2010 12:23 PM
тАО03-22-2010 12:23 PM
Re: recievng NCP error upon reboot
Bob, Here is the info- I didn't include the disks, I thought you wanted to see the ewa, eia and lla* devices
[SYSMGR]$MC NCP LIST KNOWN CIRCUITS
Known Circuit Permanent Summary as of 22-MAR-2010 16:19:29
Circuit State
EIA-0 off
EIA-1 off
EWA-0 on
EWA-1 on
LLA-0 on
[SYSMGR]$MC NCP LIST KNOWN LINES
Known Line Permanent Summary as of 22-MAR-2010 16:19:34
Line State
EIA-0 off
EIA-1 off
EWA-0 on
EWA-1 on
LLA-0 on
[SYSMGR]$MC NCP SHOW KNOWN CIRCUITS
Known Circuit Volatile Summary as of 22-MAR-2010 16:19:43
Circuit State Loopback Adjacent
Name Routing Node
EIA-0 off
EIA-1 off
LLA-0 on 2.623
[SYSMGR]$MC NCP SHOW KNOWN LINES
Known Line Volatile Summary as of 22-MAR-2010 16:19:50
Line State
EIA-0 off
EIA-1 off
LLA-0 on
[SYSMGR]$SHOW DEV
Device Device Error
Name Status Count
OPA0: Online 0
ASN0: Online 0
FTA0: Offline 0
RTA0: Offline 0
RTB0: Offline 0
TNA0: Online 0
TNA3: Online 0
TTA0: Online 0
TTB0: Online 0
Device Device Error
Name Status Count
$1$GGA900: Online 0
$1$GGA901: Online 0
$1$GGA902: Online 0
$1$GGA9003: Online 0
CMA0: Online 0
EIA0: Online 0
EIA2: Online 0
EIA3: Online 0
EIB0: Online 0
EIB2: Online 0
EIB3: Online 0
EWA0: Online 0
EWA5: Online 0
EWB0: Online 0
EWB3: Online 0
FGA0: Online 0
FGB0: Online 0
GHA0: Offline 0
LLA0: Online 0
LLA3: Online 0
LLA4: Online 0
LLA5: Online 0
LLA6: Online 0
LLA7: Online 0
LLA8: Online 0
MPA0: Online 0
OHA0: Online 0
OHB0: Online 0
PKA0: Online 0
PKB0: Online 0
PPP0: Online 0
SEA0: Online 0
SRA0: Online 0
UCM0: Online 0
USB0: Online 0
WSA0: Offline 0
[SYSMGR]$
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-23-2010 03:02 AM
тАО03-23-2010 03:02 AM
Re: recievng NCP error upon reboot
Question! Is your failover set LLA0 made up of EIAn devices, or EWAn devices??
If LLA0 = EWA0 + EWA1, then as implied by Edgar, you need to go into ncp and execute
NCP> define circuit
NCP> define line
This will remove them from the permanent database.
If they are set to "on" in the permanent data base, the system will try to bring up the lines and circuits at boot time, however since these devices are now subordinate to the LLA device, you will get the errors.
If EWA0 and EWA1 are NOT in your Failover Set, then there is some other issue.
HTH
Dave.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-23-2010 04:09 AM
тАО03-23-2010 04:09 AM
Re: recievng NCP error upon reboot
With all due respect I must demur from your characterization:
>NCP> define circuit
>NCP> define line
>
>This will remove them from the permanent database.
DEFINE [CIRCUIT|LINE] STATE OFF will not "remove them from the permanent database". It will prevent them from starting. PURGE [CIRCUIT|LINE] would remove the entries from the database.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-23-2010 04:55 AM
тАО03-23-2010 04:55 AM
Re: recievng NCP error upon reboot
NCP>show know lines
Known Line Volatile Summary as of 23-MAR-2010 08:49:02
Line State
EIA-0 off
EIA-1 off
LLA-0 on
but in lancp lla0 represents ewa0 and ewb0. ewa0 link is down.
LANCP> show dev /para lla0
N058V6 Device Characteristics LLA0 (23-MAR-2010 08:55:35.10):
Value Characteristic
----- --------------
1500 Device buffer size
Normal Controller mode
External Internal loopback mode
AA-00-00-3E-91-A0 Default MAC address (Hardware LAN address)
Multicast address list
Ethernet Communication medium
FF-FF-FF-FF-FF-FF MAC address (Current LAN address)
8 Minimum receive buffers
256 Maximum receive buffers
Yes Full duplex enable
Yes Full duplex operational
AA-00-04-00-65-08 MAC address (Current LAN address)
TwistedPair Line media type
1000 Line speed (mbps)
Disabled Auto-negotiation
Disabled Flow control
Disabled Jumbo frames
"EWA0" Failover device
"EWB0" Failover device (active)
Enabled/Active Logical LAN state
0 Failover priority
Link Up Link state
the error message indicates that it does not "see" ewa0 and ewa1( there is no device ewa1 found in lancp)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-23-2010 05:09 AM
тАО03-23-2010 05:09 AM
Re: recievng NCP error upon reboot
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-23-2010 05:21 AM
тАО03-23-2010 05:21 AM
Re: recievng NCP error upon reboot
What I do not understand is why is ewa0 status link is down. I thought both card status should be link up but only one card is "active├в perhaps ewa0 has gone bad?
I will purge ewa-1 and eia-1 from database
FYI, As far as I can tell - these errors have been going on since 4/2009.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-23-2010 05:22 AM
тАО03-23-2010 05:22 AM
Re: recievng NCP error upon reboot
when building a LAN Failover device (LLA0 in your case), the underlying physical LAN interfaces (in your case EWA0 and EWB0) are not available to other components of OpenVMS, only to the LAN failover driver (SYS$LLDRIVER). This explains, that DECnet cannot start/find lines and circuits EWA-0 and EWA-1, which correspond to the VMS devices EWA0 and EWB0.
The message is harmless, but it should still be eliminated by correctly PURGING EWA-0 and EWA-1 from the DECnet lines & circuits database.
Volker.