Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with Network when system board replaced

Nipun Patel
Occasional Advisor

Problem with Network when system board replaced

Hi,
Recently our system board for DS25 had to be replaced.

We were using EIA0 (Fast/Ethernet Card) for connection to the internet or TCP/IP. Now with the new board (we were unable to save the SRM console settings from the previous board) we cannot connect to the internet. Somehow it seems the eia0-mode settings do not seem to match or there is a problem with the port

We havee static IP and have the following options for the mode

Auto-Sensing
Twisted-Pair
Full Duplex, Twisted-Pair
AUI
BNC
Fast
FastFD (Full Duplex)
Auto-Negotiate


I have tried with
1) Auto Negotiate
2) Full Duplex, Twisted Pair

For 1) I get
***Error (eia 0.0.0.8.0) No link,Auto Negotiation did not complete The
selected mode is illegal or incompatible.

For 2) I do not get any other message but when I boot up sometimes the internet connection seems fine and other time it hangs. This suggests that the settings are in correct.

Would setting a different speed and testing for each mode one at a time be the best option ?

As far as the switch is concerned the network people informed me that they are set at 100/Full

23 REPLIES
Ian Miller.
Honored Contributor

Re: Problem with Network when system board replaced

If the switch is fixed at 100/Full then set the card to FastFD
____________________
Purely Personal Opinion
Robert Brooks_1
Honored Contributor

Re: Problem with Network when system board replaced

Unless there is a problem with the switch, any modern version of VMS should correctly autonegotiate the speed and duplex settings.

This comes directly from the VMS engineer who works on the ethernet drivers.

-- Rob
Peter Zeiszler
Trusted Contributor

Re: Problem with Network when system board replaced

Ian had it closest. Actually contact your network admin and have they force the port for your system to 100/full then force your card to 100/full.

If you have the equipment you can also have the network guys test your network speed and duplex at the cable where it plugs into your system.

Check your speed and duplex at the boot time and after it has booted. I like using "mc lancp show dev ewa0 /param".

We have ran into multiple instances where auto negotiate does not work and also where forcing the card to a specific speed without forcing the switch didn't get them working together.

Andy Bustamante
Honored Contributor

Re: Problem with Network when system board replaced

Peter is correct, the settings on the Alphaserver and the switch need to match. You can change the Alphaserver with the LANCP utility and avoid rebooting.

$ MCR LANCP
LANCP> SET DEVICE EIA0/SPEED=100/FULL_DUPLEX

To make the changes permanent, replace SET with DEFINE.

You can use SHOW DEVICE/COUNTERS in LANCP to check for errors, this can be a sign of a duplex mismatch.

Andy
If you don't have time to do it right, when will you have time to do it over? Reach me at first_name + "." + last_name at sysmanager net
Steven Schweda
Honored Contributor

Re: Problem with Network when system board replaced

My experience is limited to stupid switches,
but I've never had a problem with
Auto-Negotiate.

Are you sure that nothing bad happened to the
E-net card or the cable (or the switch) when
the work was done to the system?
Eric Dittman
Frequent Advisor

Re: Problem with Network when system board replaced

If you hard-code the settings on one end of the connection you need to hard-code the settings on the other end. Autonegotiation doesn't work right if you have one end hard-coded and the other set to autonegotiate.
nipun_2
Regular Advisor

Re: Problem with Network when system board replaced

Ian, Peter and Andy
you guys are geniuses....

Doing so worked perfectly. Also the idea mentioned by Peter to do it in the terminal is very helpful. I was always shutting down the node.

So now I have got 2/3 nodes to work...and got all the switches set to 100 /FullFD

One node is not working so I got the following mail from my network admin
00-02-a5-20-07-5b - shows connected but is not visible on the router and is not pingable... It occasionally shows as an incomplete arp... Check it has gateway xx.xx.xxx.x and subnet mask yyy.yyy.yyy.yyy...

So I guess I can do this from lancp or tcpip?
I will try to figure out how to check those settings and if required modify them..so that the last node works. I believe this would be now be openvms issue and not the hardware issue as all of them are on FastFD

Nipun
Volker Halle
Honored Contributor

Re: Problem with Network when system board replaced

Nipun,

the first check would be $ TCPIP SHOW INT
Make sure, there is a valid interface defined with the expected address and network mask. The packets received and send counters should be non-zero.

Next you could check the LAN device counters with LANCP> SHOW DEV/COUNT EIA0 - note that you can also look at the LAN driver console messages with LANCP> SHOW DEV/INT EIA0 (will display internal counters and the console messages at the bottom).

Volker.
nipun_2
Regular Advisor

Re: Problem with Network when system board replaced

Hi Volker,
I executed the commands you mentioned and it seems to indicate that I don't have EIA0 configured as I do not even get that name as can be seen in the log below (Also attached as Text File)

Note: I have two ethernet cards WE0 is already congfigured for cluster. I need to use the EIA0 for connecting to the internet.

So I believe I need to figure out the correct options with

$@tcpip$config


========Log of the current network settings ============ (Also attached as Text File)

$ tcpip show int
Packets
Interface IP_Addr Network mask Receive Send MTU

LO0 127.0.0.1 255.0.0.0 319 319 4096
WE0 10.35.221.122 255.255.255.128 2543 2563 1500



LANCP> show dev /count EIA0

Device Counters EIA0:
Value Counter
----- -------
254989 Seconds since last zeroed
20116718763 Bytes received
9590441257 Bytes sent
62529329 Packets received
36359847 Packets sent
31946897 Multicast bytes received
16878723 Multicast bytes sent
228300 Multicast packets received
141932 Multicast packets sent
0 Unrecognized unicast destination packets
6587 Unrecognized multicast destination packets
0 Unavailable station buffers
0 Unavailable user buffers
0 Alignment errors
0 Frame check errors
0 Frame size errors
0 Frame status errors
0 Frame length errors
0 Frame too long errors
0 Data overruns
0 Send data length errors
0 Receive data length errors
0 Transmit underrun errors
0 Transmit failures
0 Carrier check failures
0 Station failures
0 Initially deferred packets sent
0 Single collision packets sent
0 Multiple collision packets sent
0 Excessive collisions
0 Late collisions
0 Collision detect check failures
LANCP>
nipun_2
Regular Advisor

Re: Problem with Network when system board replaced

Hi Volker,
I executed the commands you mentioned and it seems to indicate that I don't have EIA0 configured as I do not even get that name as can be seen in the log below (Also attached as Text File)

Note: I have two ethernet cards WE0 is already congfigured for cluster. I need to use the EIA0 for connecting to the internet.

So I believe I need to figure out the correct options with

$@tcpip$config


========Log of the current network settings ============ (Also attached as Text File)

$ tcpip show int
Packets
Interface IP_Addr Network mask Receive Send MTU

LO0 127.0.0.1 255.0.0.0 319 319 4096
WE0 10.35.221.122 255.255.255.128 2543 2563 1500



LANCP> show dev /count EIA0

Device Counters EIA0:
Value Counter
----- -------
254989 Seconds since last zeroed
20116718763 Bytes received
9590441257 Bytes sent
62529329 Packets received
36359847 Packets sent
31946897 Multicast bytes received
16878723 Multicast bytes sent
228300 Multicast packets received
141932 Multicast packets sent
0 Unrecognized unicast destination packets
6587 Unrecognized multicast destination packets
0 Unavailable station buffers
0 Unavailable user buffers
0 Alignment errors
0 Frame check errors
0 Frame size errors
0 Frame status errors
0 Frame length errors
0 Frame too long errors
0 Data overruns
0 Send data length errors
0 Receive data length errors
0 Transmit underrun errors
0 Transmit failures
0 Carrier check failures
0 Station failures
0 Initially deferred packets sent
0 Single collision packets sent
0 Multiple collision packets sent
0 Excessive collisions
0 Late collisions
0 Collision detect check failures
LANCP>
Volker Halle
Honored Contributor

Re: Problem with Network when system board replaced

Nipun,

you do not have EIA0 configured in TCPIP. Otherwise it would show up as an 'ie0' device.

You need to figure out which IP address and network mask to use and run @TCPIP$CONFIG -> Core environment -> interfaces.

Why would swapping the system board make the TCPIP interface configuration for EIA0 disappear ???

Volker.
Steven Schweda
Honored Contributor

Re: Problem with Network when system board replaced

> WE0 is already congfigured for cluster.

What does this mean? A VMScluster does not
use TCP/IP.

According to your LANCP output, _someone_ is
using EIA0. DECnet? What?

> $@tcpip$config

Start with "Core environment" - "Interfaces",
but it might pay to go through the whole
thing, and see what's what.
Volker Halle
Honored Contributor

Re: Problem with Network when system board replaced

WE0 may be used for cluster communication.

$ ANAL/SYS
SDA> SHOW LAN
SDA> EXIT

is the best tool to find out, which protocols are active on which network device.

Volker.
Robert Brooks_1
Honored Contributor

Re: Problem with Network when system board replaced

$ ANAL/SYS
SDA> SHOW LAN
SDA> EXIT

is the best tool to find out, which protocols are active on which network device.

----

On V8.3, SHOW DEVICE /FULL for LAN devices displays the protocol in use on each device.

For example . . .

Device EWA2:, device type DE500, is online, network device, error logging is
enabled.

Error count 0 Operations completed 58472
Owner process "NETACP" Owner UIC [SYSTEM]
Owner process ID 0000041B Dev Prot S:RWPL,O:RWPL,G,W
Reference count 2 Default buffer size 1498

Operating characteristics: Full duplex, Autonegotiation.

Speed (Mbits/sec) 100
Def. MAC addr 08-00-2B-86-AD-95 Current MAC addr AA-00-04-00-88-39
Protocol name DECNET Protocol type 60-03
nipun_2
Regular Advisor

Re: Problem with Network when system board replaced

Hi,
I choose the following when I executed the command

$tcpip$config

INTERFACE Configuration


The Ethernet device(s) on your system are: EWA0:
EIA0: * Not Configured *

Start of configuration questions for Internet interface WE0 instead of EIA0 which we want.


Note: Vol, you are right this has nothing to do with the hardware error and it's replacement. This (EIA0) just hasn't been configured.


Nipun
Steven Schweda
Honored Contributor

Re: Problem with Network when system board replaced

> Start of configuration questions for
> Internet interface WE0 instead of EIA0
> which we want.

Just agree with the current configuration of
the interface(s) which you like, and you
should eventually get to the one(s) which
you wish to change.
Volker Halle
Honored Contributor

Re: Problem with Network when system board replaced

Nipun,

EWA0 (we0) currently is the only LAN device configured for TCPIP on your system. If you want to configure EIA0 (ie0) as well, just don't change the EWA0 config and continue on to the next device, which will be EIA0. You need to know the correct IP address, name and network mask to configure that interface.

You need to restart TCPIP to activate the new configuration. You could also do this manually, a reboot - if possible - is the cleanest solution.

Volker.
nipun_2
Regular Advisor

Re: Problem with Network when system board replaced

Hi all,
Thanks for the response. Configuring EIA0 without touching EWA0 is exactly what I wish to do

However,
When I execute $@tcpip$config



I am providing the options I choose after choose
1) Core Environment -> Interface


=======log output==============

INTERFACE Configuration


The Ethernet device(s) on your system are: EWA0:
EIA0: * Not
Configured *

Start of configuration questions for Internet interface WE0.


WE0 is the Ethernet device EWA0:


Interface: WE0
IP_Addr: 10.35.221.122 NETWRK: 255.255.255.128 BRDCST:
10.35.221.127
C_Addr: C_NETWRK: C_BRDCST:

Flags:
Receive buffer: 0

HP TCP/IP Services for OpenVMS Interface WE0 Reconfiguration
Menu

Reconfiguration options:

1 - Configure interface manually (Current
default)
2 - Let DHCP configure interface

[E] - Exit menu (Do not reconfigure interface WE0)

Enter configuration option: 1


So here I have only option 1 and 2 in which case it always goes to WE0 so how do go to EIA0?

Volker Halle
Honored Contributor

Re: Problem with Network when system board replaced

Nipun,

you should enter 'E' for Exit menu (Do not reconfigure interface WE0).

Then you will be taken to the configuration questions for the next device.

Volker.
nipun_2
Regular Advisor

Re: Problem with Network when system board replaced

Oooops....

Hi Volker I followed the instructions. Unfotunately I executed them at a different node since I was working remotely. So now I have two problems

The node (SC4238) on which I executed this has lost network connectivity and I am not able to modify the connectivity of the required node (Salsa- which still doesn't have connection).

To be more clear I have the session when I was by mistake on SC4238 node and executed the
$@tcpip$config
Core Environmnet ->Interface -> Exit to go to device EIA0

Pasted below as well as attached as text.

*********************************

Start of configuration questions for Internet interface IE0.


IE0 is the Ethernet device EIA0:


Interface: IE0
IP_Addr: 192.168.1.211 NETWRK: 255.255.255.0 BRDCST: 192.168.1.255
C_Addr: C_NETWRK: C_BRDCST:

Flags: DHCP
Receive buffer: 0

HP TCP/IP Services for OpenVMS Interface IE0 Reconfiguration Menu

Reconfiguration options:

1 - Configure interface manually
2 - Let DHCP configure interface (Current default)

[E] - Exit menu (Do not reconfigure interface IE0)

Enter configuration option: 1
Enter fully qualified host name: salsa.bidmc.harvard.edu

Host salsa.bidmc.harvard.edu exists in the database.
salsa.bidmc.harvard.edu is an alias for salsa.

Enter Internet address [10.35.221.122]:
Enter Internet network mask for salsa.bidmc.harvard.edu [255.0.0.0]: 255.255.255
.128
Enter broadcast mask for salsa.bidmc.harvard.edu [10.35.221.127]:

The following parameters will be used to define the
Internet interface IE0:

Host name: salsa.bidmc.harvard.edu
Internet address: 10.35.221.122
Network mask: 255.255.255.128
Broadcast mask: 10.35.221.127

* Is the above correct [YES]:

failSAFE IP

failSAFE IP uses multiple Network Interface Controllers
(NICs) to provide high availability of IP addresses.
In the event of a NIC failure, (e.g. any event
preventing the NIC from receiving data), all IP
addresses associated with the failed NIC are reassigned
to a preconfigured failover target.

In a cluster configuration, the IP address may be
preconfigured on NICs across other cluster members.
This provides cluster-wide failover for the IP address.

See the management guide for more configuration options.
You will be asked what other NICs on this node will
act as failover targets.

* Configure failover target for failSAFE IP [NO]:

End of configuration questions for Internet interface IE0



This CPU is a member of a VMScluster.

You may specify that the Internet interface(s) on this
CPU will participate in an Internet VMScluster.

An Internet VMScluster can be configured so that all
cluster members appear to remote network hosts as a
single virtual host.

The Internet VMScluster is identified by its cluster
host name and address, and must be activated on each
of the hosts that are members of the Internet
VMScluster.

* Define Internet VMScluster [NO]:



HP TCP/IP Services for OpenVMS Core Environment Configuration Menu

Configuration options:

1 - Domain
2 - Interfaces
3 - Routing
4 - BIND Resolver
5 - Time Zone

A - Configure options 1 - 5
[E] - Exit menu

Enter configuration option: e







HP TCP/IP Services for OpenVMS Configuration Menu

Configuration options:

1 - Core environment
2 - Client components
3 - Server components
4 - Optional components

5 - Shutdown HP TCP/IP Services for OpenVMS
6 - Startup HP TCP/IP Services for OpenVMS
7 - Run tests

A - Configure options 1 - 4
[E] - Exit configuration procedure

Enter configuration option: 5
Begin Shutdown...


%TCPIP-I-INFO, TCP/IP Services shutdown beginning at 15-AUG-2006 17:31:00.18
%TCPIP-S-SHUTDONE, TCPIP$DHCP_CLIENT shutdown completed
%TCPIP-S-SHUTDONE, TCPIP$FTP_CLIENT shutdown completed
%TCPIP-S-SHUTDONE, TCPIP$FTP shutdown completed
%TCPIP-S-SHUTDONE, TCPIP$POP shutdown completed
%TCPIP-S-SHUTDONE, TCPIP$PROXY shutdown completed
%TCPIP-S-SHUTDONE, TCPIP$RLOGIN shutdown completed
%TCPIP-S-SHUTDONE, TCPIP$SMTP shutdown completed
%TCPIP-S-SHUTDONE, TCPIP$SNMP shutdown completed
%TCPIP-S-SHUTDONE, TCPIP$SSH_CLIENT shutdown completed
%TCPIP-S-SHUTDONE, TCPIP$SSH shutdown completed
%TCPIP-S-SHUTDONE, TCPIP$TELNET shutdown completed

The following Internet devices are still active on
your system:

BG304:
BG1122:

Before restarting TCP/IP Services you should stop
the processes associated with the above BG
devices. To locate these processes, issue the DCL
SHOW DEVICE BGn /FULL.




WARNING - The following TN devices are still active:

TNA3:
TNA4:

%TCPIP-S-SHUTDONE, TCP/IP Kernel shutdown completed
%TCPIP-S-SHUTDONE, TCP/IP Services shutdown completed at 15-AUG-2006 17:31:02.99

Shutdown request completed.
Press Return to continue ...


HP TCP/IP Services for OpenVMS Configuration Menu

Configuration options:

1 - Core environment
2 - Client components
3 - Server components
4 - Optional components

5 - Shutdown HP TCP/IP Services for OpenVMS
6 - Startup HP TCP/IP Services for OpenVMS
7 - Run tests

A - Configure options 1 - 4
[E] - Exit configuration procedure

Enter configuration option: 6
Begin Startup...


%TCPIP-I-INFO, TCP/IP Services startup beginning at 15-AUG-2006 17:31:08.37
%TCPIP-I-NORMAL, timezone information verified

There are one or more processes which did not
terminate when TCP/IP Services was last shutdown.

WARNING - The TCPIP$INET_STARTUP procedure will
now start the TCP/IP Kernel. Subsequent I/O
operations on the following Internet devices,
which are currently assigned and active in your
system, may fail:

BG304:
BG1122:

You may choose to stop the processes that are
using the above Internet devices. Issue the DCL
command SHOW DEVICE BGn /FULL for each of the
listed devices to identify the processes.

%RUN-F-CREPRC, process creation failed
-SYSTEM-F-DUPLNAM, duplicate name
%TCPIP-E-STARTFAIL, failed to start TCP/IP Kernel
-TCPIP-E-CREACPERR, error creating ACP process
*************************************************


Now I realized the problem so I went to SALSA (the oringal node with the problem).

However...it now seemed to complain about overwriting IP address...

Here is the log

=======================================================================================
WHEN ACTUALLY LOGGED TO SALSA
======================================================
$

IE0 is the Ethernet device EIA0:

IE0 has not been configured

HP TCP/IP Services for OpenVMS Interface IE0 Configuration Menu

Configuration options:

1 - Configure interface manually
2 - Let DHCP configure interface

[E] - Exit menu (Do not configure interface IE0)

Enter configuration option: 1
Enter fully qualified host name: salsa1.bidmc.harvd.edu
Enter Internet address for salsa1: 10.35.221.122

This Internet address is used by host: salsa

Enter Internet address for salsa1:
Interrupt




Steven Schweda
Honored Contributor

Re: Problem with Network when system board replaced

You can't have two interfaces with the same
IP address on the same subnetwork.

If you wish to use 10.35.221.122 on SALSA,
you'll first need to stop using it on SC4238.

"TCPIP SET NOINTERFACE IE0"?

Or set it to some other address.

Or use a different address for SALSA.
Nipun Patel
Occasional Advisor

Re: Problem with Network when system board replaced

Hi Steve,
Thanks for the command usage to remove the interface.
I already have the older settings and would like to set it to a different IP address.

I tried to use
$@tcpipconfig
Core Environment->Interfaces->

and then chose EIA0 for SC4238 but it doesn't allow me to choose a different IP address with the message as shown in the previous log I presented.

So the mixup is

SC4238 has beeen assigned Salsa's IP address as well as the name salsa.bxx.xxx

and now I can't seem to modify the EIA0 for SC4238 and SALSA. (The log is as what I had pasted earlier). I believe I need to go in a sequence like

1) disable both(SC4238 and Salsa) EIA0's (using set no interface command TCPIP SET NOINTERFACE IE0"?and remove old information and start fresh.

Is that a good approach in this case of mixup.





Volker Halle
Honored Contributor

Re: Problem with Network when system board replaced

Nipun,

you would not only have to remove the interface from the TCPIP config, but also the incorrect hostname to IP address mapping in the local host database and - maybe - even in the local communcation configuration:

Check with:

$ UCX SHOW HOST
$ UCX SHOW CONF COMM

Remove wrong name/address with:

$ UCX SET NOHOST name or /ADDRESS=...

$ UCX HELP will give more details for the commands to be used.

Volker.