decnet plus not working after new network card

[TMcB]

Hi everyone

I've replace the network card on our alphaserver ds20. Decnet Plus no longer working.


The card is still seen as we0 (ewa0).
But when I run mc ncl show node it sees the old mac address.
How can I change it to see the new mac address

> mc ncl show node ruby1
Node RUBY1
at 2007-05-01-12:01:04.811+01:00Iinf
Identifiers
Name = LOCAL:.RUBY1
Address =
{
(
[ DNA_CMIP-MICE ] ,
[ DNA_SessionControlV3, number = 19 ] ,
[ DNA_OSItransportV1 , 'DEC0'H ] ,
[ DNA_OSInetwork , 49::00-01:AA-00-04-00-3D-07:21 (LOCAL:.RUBY1) ]
) ,
(
[ DNA_CMIP-MICE ] ,
[ DNA_SessionControlV2 , number = 19 ] ,
[ DNA_OSItransportV1 , 'DEC0'H ] ,
[ DNA_IP , 0.0.0.0 ]
) ,
(
[ DNA_CMIP-MICE ] ,
[ DNA_SessionControlV3 , number = 19 ] ,
[ DNA_NSP ] ,
[ DNA_OSInetwork , 49::00-01:AA-00-04-00-3D-07:20 (LOCAL:.RUBY1) ]

This mac address is the one which belonged to the old card.
Can anyone point me in the right direction of how to get it to see the new mac address.

Much appreciated.

[Ian Miller.]

The MAC address AA-00-04-00-3D-07 is generated from your DECnet address and is independent of the hardware. This is why you are seeing the same MAC address.

What is not working?

[TMcB]

Hi Ian

The card which has mac address AA-00-04-00-3D-07 is no loinger physically in the server.
The new card had mac address 00-06-2b-01-F0-8B.

Why is decnet still seeing the old mac address when this is no longer there

Thanks

[Volker Halle]

Hi,

when DECnet Phase IV protocol is being started on a LAN interface, the MAC address of the interface card is changed to the DECnet MAC address (AA-00-04-00-xx-xx). xx-xx are calculated from the DECnet address of the local node.

You can view the Hardware MAC Address with:

$ MC LANCP SHOW DEV/CHAR EWA0

It's shown as Hardware LAN Adress.

What doesn't work with DECnet ? Are there any errors on the LAN interface, how about bytes received/send counters ?

$ MC LANCP SHOW DEV/COUNT EWA
or
$ MC NCL SHOW CSMA_CD STATION csmacd-0 ALL COUNT

$ MC LANCP SHO DEV/INTERNAL

will show the messages issued by the LAN driver during startup or re-configuration.

Volker.

[TMcB]

Hi

The counters / errors all look ok (0).

When I try to set host now I am getting -
RUBY1> set host alf0
%SYSTEM-F-UNREACHABLE, remote node is not currently reachable

[Volker Halle]

Do you run other protocols on that LAN interface (e.g. TCPIP) ? Do they work ?

Are the CSMA-CD station and ROUTING CIRCUIT in state ON ?

Can you do SET HOST RUBY1 from node ALF0 ?

Volker.

[TMcB]

Hi Volker

I cannot set host from alf0 :
ALF0> set host ruby1
%SYSTEM-F-UNREACHABLE, remote node is not currently reachable

But I've just realised that from ruby1 I can set host to other machines so decnet must be working, just not to alf0.

I tried deleting the node using decnet-register and ran the flush command, but still cannot get to it

Thanks

[Duncan Morris]

Hi,

it looks as though DECnet is operating fine on RUBY1, but not on node ALF.

The change of NIC on RUBY1 is probably unrelated to the issue with ALF0, so concentrate on looking at ALF0.

Regards,

Duncan

[TMcB]

Hi Duncan

I'll do that now - I am unable to set host to ruby1 from any server.

I also noticed that ib ruby1 if I do set host 0, I get :
RUBY1> set host 0
Failure on the back translate address request

Username:


Thanks

[Duncan Morris]

Hi,

which node did you delete using decnet_register?

Are you using DECdns for the directory service as well as LOCAL, or just LOCAL?

On a node which used to be able to reach RUBY1, you should still have the LOCAL address info, so try running DECNET_REGISTER on that node and get it to display the info for RUBY1. Compare the result with the same info on RUBY1 itself!

Duncan