| Title: | "ASK THE WIZARDS" |
| Moderator: | QUARK::LIONEL |
| Created: | Mon Oct 30 1995 |
| Last Modified: | Mon May 12 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1857 |
| Total number of notes: | 3728 |
Return-Path: "VMS001::WWW"@vms001.das-x.dec.com
Received: by vmsmkt.zko.dec.com (UCX V4.1-12, OpenVMS V6.2 VAX);
Mon, 10 Feb 1997 12:11:35 -0500
Received: from vms001 by mail11.digital.com (8.7.5/UNX 1.5/1.0/WV)
id MAA21555; Mon, 10 Feb 1997 12:00:03 -0500 (EST)
Date: Mon, 10 Feb 1997 12:00:42 -0500
Message-Id: <[email protected]>
From: "VMS001::WWW"@vms001.das-x.dec.com (10-Feb-1997 1200)
To: [email protected], [email protected], [email protected]
Subject: Ask the Wizard: '[email protected]'
X-VMS-To: [email protected]
Remote Host: (null)
Browser Type: Mozilla/4.0b1 (Win95; I)
Remote Info: <null>
Name: Sean Maddox
Email Address: [email protected]
CPU Architecture: Alpha
Version: v 6.2
Questions:
I have an Alpha 8200 5/300 that was upgraded from v6.2 to
v6.2-1h2 (12/96) when 3 kzpsa's were added. Two weeks ago
we upgraded to 1h3 for the scsi cluster support. In the
pci shelf of this box I have 2 DEFPA's (slots 11 & 10),
3 KZPSA's (8,7 & 6), 1 KZPAA (slot 5) and 1 Ethernet card
in slot 4. I am now having a problem with DECnet
recognizing circuits some of the circuits. At the time of
the upgrade we did not have any problems when booting, now
when DECnet starts up it returns an 'Invalid media address'
error for FPA-0. I have also seen this error on EWA-2
(ethernet in slot 4) and FPA-1 (slot 11). We have done
several things in an attempt to resolve this problem. We
re-ordered the pci shelf, putting the DEFPA's before the
KZPSA's, removing the ethernet & one DEFPA, booting from
the 6.2-1h2 system disk etc... At the time we were running
off of 6.2-1h2 we had the KZPSA's in and the storageworks
configured but not in use, we had our apps & system disks on
two of the internal buses. We also upgraded the firmware
to what is on the v3.7 firmware cd. We are trying to
determine if the problem is hardware related or OS related.
We do have a cluster of 4100's on v6.2-1h3 running virtually
the same configuration. The 8200 is currently the only
member of the cluster. Another interesting thing is that
I am running UCX over the DEFPA which leads me to believe
the hardware is performing, I just can't get DECnet to run
over it. Can you specify what it is DECnet is not seeing
when it returns the invalid media address error ? Any
help (eg: best person to talk to etc...) is appreciated.
Thanks
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1531.1 | IVADDR: Usually Duplicate Host Address | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Tue Feb 11 1997 10:51 | 60 |
Invalid media address usually indicates DECnet has detected another
node (or possibly the local node via multiple controllers connected
to the same LAN segment, or connected via inter-bridged LAN segments)
using the same address.
DECnet Phase IV does not support this configuration -- there are ways
to render the LAN "disjoint" from the perspective of a host node with
multiple controllers. DECnet-Plus does directly support this config.
--
$ H/M IVADDR
IVADDR, invalid media address
Facility: SYSTEM, System Services
Explanation: This message can occur for several reasons:
...
o A duplicate address test failed on an attempt to start a
network protocol.
o A hardware error occurred.
User Action: Take action appropriate to the cause of the error:
o If the error occurred on network activity, contact
the network manager, who can do the following tests to
determine the cause of the error:
- Test: Use the NCP command SHOW KNOWN LINES to check
whether the user's machine has multiple LAN lines.
If so, DECnet for OpenVMS may be trying to use more than
one LAN adapter on the same extended LAN.
Action: Run DECnet for OpenVMS on only one LAN adapter
per machine.
- Test: Disconnect the erring system from the LAN. Go to
another node on the LAN and set host to the erring node.
If you get a response, another system on your extended
LAN is up and running with your DECnet address.
Action: Decide which DECnet address each system can use.
- Test: Check for a halted node that was last using the
disputed DECnet address. Such a node's LAN adapter is
still active using the LAN address.
Action: Initialize the bus or power off the machine on
the node using the disputed DECnet address.
o If none of the above solutions applies and you suspect a
hardware error, contact a Digital support representative.
| |||||