Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!ames!sdcsvax!ucbvax!ENGVAX.SCG.HAC.COM!KVC
From: KVC@ENGVAX.SCG.HAC.COM (Kevin Carosso)
Newsgroups: comp.protocols.tcp-ip
Subject: DEC Ethernet addresses
Message-ID: <8708130054.AA01595@ucbvax.Berkeley.EDU>
Date: Wed, 12-Aug-87 19:27:00 EDT
Article-I.D.: ucbvax.8708130054.AA01595
Posted: Wed Aug 12 19:27:00 1987
Date-Received: Sat, 15-Aug-87 04:43:24 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 42

For VMS DECnet (using NCP):

to show the ethernet controller's hardware address:

---------------------------------------------------------------------
NCP> SHOW LINE UNA-0 CHARACTERISTICS
Line Volatile Characteristics as of 12-AUG-1987 16:06:40

Line = UNA-0

Receive buffers          = 6
Controller               = normal
Protocol                 = Ethernet
Service timer            = 4000
Hardware address         = 08-00-2B-05-D3-E3
Device buffer size       = 1498
---------------------------------------------------------------------


to show the ethernet controller's current address as set by DECNet:

---------------------------------------------------------------------
NCP> SHOW EXECUTOR STATUS
Node Volatile Status as of 12-AUG-1987 16:06:10

Executor node = 45.9 (ENGVAX)

State                    = on
Physical address         = AA-00-04-00-09-B4
---------------------------------------------------------------------

This is the one generated by DECnet from the node number via the
scheme: (area * 1024) + node = last_two_bytes

There seems to have been some confusion on these issues.

Also, I've noted that my DELUA controller and the DESVA controller in a
VAXstation-2000 have hardware addresses assigned in the group 08-00-2B.
I guess DEC got more than the AA-00-00 through AA-00-04 range.

        /Kevin Carosso                     kvc@engvax.scg.hac.com
         Hughes Aircraft Co.               kvc%engvax@oberon.usc.edu