[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | Alpha Developer Support |
| Notice: | [email protected], 800-332-4786 |
| Moderator: | HYDRA::SYSTEM |
|
| Created: | Mon Jun 06 1994 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3722 |
| Total number of notes: | 11359 |
3241.0. "Integrated Systems Incorporated" by HYDRA::AXPDEVELOPER (Alpha Developer support) Thu Feb 27 1997 03:22
Company Name : Integrated Systems Incorporated
Contact Name : Rob Curley
Phone : (408)542-1688
Fax : (408)542-1954
Email : [email protected]
Date/Time in : 27-FEB-1997 03:21:42
Entered by : Nick Hudson
SPE center : REO
Category : vms
OS Version :
System H/W :
Brief Description of Problem:
-----------------------------
From: SMTP%"[email protected]" 26-FEB-1997 17:57:50.29
To: [email protected]
CC: [email protected], [email protected]
Subj: Determination of card addresses for ethernet and FDDI devices
Return-Path: [email protected]
Received: by asimov.mro.dec.com (UCX V4.1-12, OpenVMS V6.2 VAX);
Wed, 26 Feb 1997 17:57:48 -0500
Received: from pobox1.pa.dec.com by fluid.mro.dec.com; (5.65v3.2/1.1.8.2/19Nov96-0448PM)
id AA07660; Wed, 26 Feb 1997 17:57:58 -0500
Received: by pobox1.pa.dec.com; id AA17891; Wed, 26 Feb 97 14:58:01 -0800
Received: from karma.isi.com by mail1.digital.com (5.65 EXP 4/12/95 for V3.2/1.0/WV)
id AA12012; Wed, 26 Feb 1997 14:54:59 -0800
Received: from barcode.isi.com (barcode.isi.com [192.216.226.49])
by karma.isi.com (8.8.4/8.8.4) with ESMTP
id OAA15243 for <[email protected]>; Wed, 26 Feb 1997 14:54:58 -0800 (PST)
Received: (from curley@localhost)
by barcode.isi.com (8.8.4/8.8.4)
id OAA05294; Wed, 26 Feb 1997 14:53:58 -0800 (PST)
Date: Wed, 26 Feb 1997 14:53:58 -0800 (PST)
From: Rob Curley <[email protected]>
Message-Id: <[email protected]>
To: [email protected]
Subject: Determination of card addresses for ethernet and FDDI devices
Cc: [email protected], [email protected]
Hi - Can you help us determine how obtain the address of the ethernet
and FDDI controllers on a VAX or Alpha system? Some of our
software programs use these devices to lock the software license to.
For ethernet, we go into ncp:
$mcr ncp
NCP> show act line char
Can you tell me how to do this for a customer who has both devices?
My PIN number is 102395
Thank you for your assistance.
-------------------------------------------------------------------------------
Rob Curley | ____| | | Integrated Systems Incorporated
Product Integration Engineer | ___|_| | 201 Moffett Park Drive
Phone: (408)542-1688 | __|_|_| Sunnyvale, CA 94089
Fax: (408)542-1954 | \_|_|______
email: [email protected] | \_|_____
http://www.isi.com | \____
-------------------------------------------------------------------------------
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3241.1 | sent sample | KZIN::HUDSON | That's what I think | Thu Feb 27 1997 09:48 | 49 |
| From: DEC:.REO.REOVTX::HUDSON "[email protected] - UK Software
Partner Engineering 830-4121" 27-FEB-1997 14:47:13.53
To: nm%vbormc::"[email protected]"
CC: HUDSON
Subj: RE: Determination of card addresses for ethernet and FDDI devices
Hello Rob Curley
> Hi - Can you help us determine how obtain the address of the ethernet
> and FDDI controllers on a VAX or Alpha system? Some of our
> software programs use these devices to lock the software license to.
I am assuming this is something you want to do from inside a program?
I include below a C program (which is on the ASAP web pages, you can find it by
going to "http://www.partner.digital.com/www-swdev/" and following the links
down through "Technical Support", and the OpenVMS FAQs).
The program is written to get ethernet addresses. It uses $device_scan to get
a list of the relevant devices and $QIO to retrieve the ethernet address of
each.
In fact it will work for FDDI devices as well. Obviously in the case of a
machine that has multiple synchronous adapters, you'll have to work out which
one you want to use (or use all of them I suppose).
Note, I added a line of code to the web page example to show which devices it's
trying to read the addresses of (bracketed by "Nick" comments), otherwise you
can't tell what it's looking at.
Let me know if this helps
Regards
Nick Hudson
Digital Software Partner Engineering
Program output on a node which has both DEMNA and DEMFA:
$ r getadr
attempting to perform sensemode for device _FXA0:
attempting to perform sensemode for device _EXA0:
Ethernet hardware address = (08-00-2B-37-E1-1E)
Ethernet hardware address = (08-00-2B-39-86-B8)
$
<program included...>
|