What's my MAC address?

[Craig E.]

I have an telnet session open to another node on the network and want to find out its FDDI MAC address. When i logged in i tried an
arp -a and that returrned all the MAC addresses for all the nodes except the one i was logged into. I tried a lanscan and that returned the MAC address for the Ethernet interface where as i need the MAC for the FDDI interface. Is there some other way to get the MAC or some other qualifiers i could use, or even a file that has the MAC address stored somewhere?

Thanks,
CE

[Robert-Jan Goossens]

Hi,

try lanscan
# lanscan

Regards,
Robert-Jan

[RAC_1]

fcmsutil /dev/tdx

Anil

[Jeff Schussele]

Hi CE,

Try
lanscan -v
and then look under MAC Type column for FDDI.

HTH,
Jeff

[Marvin Strong]

lanscan

[Mel Burslan]

lanscan suggesters, if you read the question, you will see that Craig is asking for a FDDI MAC address not a LAN interface. I think he, kinda sorta, put a misleading title on the question. As far as I know FDDI interfaces do not have mac addresses they have WWN (World Wide Name) identifiers, which can be obtained by using command:

fcmsutil /dev/tdX

where X is unique to every fibre channel inteface installed on the system.

hope this helps.

[Jeff Schussele]

Nice try Mel.

From the man 7 fddi page....

fddi(7)
Description
See Also


NAME
fddi - Fiber Distributed Data Interface Tools

DESCRIPTION

This manual entry provides general information on the HP-UX FDDI (Fiber Distributed Data Interface) link tools.

Tools for HSC and EISA FDDI

fddiif Display FDDI driver operating statistics in real-time.
fddilink Display FDDI interface and network characteristics.

Tools for PCI FDDI

fddipciadmin
Display FDDI interface, driver and network statistics and characteristics.

Tools for HP-PB FDDI and S700 Built-in FDDI

fddiinit Initialize FDDI network interface; connect to FDDI network.
fddinet Display logical FDDI ring map information.
fddistat Display status information for the FDDI interface.
fddistop Stop and reset the FDDI interface.

General Link Tools

ifconfig Configure or display IP interface information.
ioscan Scan system for devices, display hardware path, class and description.
lanadmin Display link information, RFC 1213 MIB II statistics, reset the interface card, perform card self-test.
lanscan Scan system for LAN devices, display hardware path, station address (canonical format), instance number, hardware state, interface name, IP interface state, Network Management ID.
linkloop Verify LAN connectivity with a link-level test frame. Requires the Physical Point of Attachment number (PPA) of the local interface and station address of the remote station in canonical format. The PPA is the numeric portion of the interface name. For example, the interface lan2 has the PPA 2. Use lanscan on the remote system to get the remote station address in canonical format.
netfmt Format network trace and log files created with the nettl utility (see below). FDDI entity names are FDDI (HP-PB and S700 built-in FDDI), EISA_FDDI, HSC_FDDI and PCI_FDDI.
netstat Show network statistics for IP interfaces and upper-layer protocols.
nettl Start/stop network tracing and logging. FDDI entity names are FDDI (HP-PB and S700 built-in FDDI), EISA_FDDI, HSC_FDDI and PCI_FDDI.
ping Verify IP/ICMP connectivity to remote system.
syslogd Read and log system messages (the FDDI drivers log system messages using syslog routines).
what Get version identification information. Use what /stand/vmunix to determine if the correct FDDI driver has been installed, according to the following list:

fddi (for HP-PB FDDI), fddi0 (for EISA FDDI), fddi2 (for S700 built-in FDDI), fddi3 (for HSC FDDI), fddi4 (for PCI FDDI).

FDDI station addresses are represented as a series of hexadecimal digits using canonical format, or wire ("native") format. The canonical format uses Least Significant Bit (LSB) order. Wire ("native") format uses Most Significant Bit (MSB) order. Most HP-UX FDDI and network utilities use canonical format (fddilink and fddiif are two exceptions). The fddinet and fddistat commands display the addresses in canonical format by default and have a -n option to display the addresses in "native" (wire) format.

Notice that they reference lanscan, lanadmin, linkloop, ifconfig, etc. Not a mention of fcmsutil nor tdutil in there at all.

Even though it's fibre it's *still* a LAN device. Using your logic a GigE fibre would also need fcmsutil, huh?

Rgds,
Jeff

[Mel Burslan]

nope, but I happen to have a gelan as well as a few tachyon interfaces. lanscan -v does not give me any information about my tachyon interfaces and their so called MAC addresses. I do not claim that I am an expert on Fibre Channel but this is my experience so far.

[Mike Spencer]

Wow, nice counter-productive email, Jeff. By the way, try doing a "lanscan -v" as you've suggested here and see how much information you get regarding your FC interfaces.

I had a similar issue and I found Mel's post to be very helpful. Thanks, Mel.

[Jeff Schussele]

Wow, pretty subtle innuendo there Mike.
Just what are you trying to say?

I can tell you what I was saying is that fibre channel cards like A5158A & such are NOT network I/F devices and as such do not have MACs - they have WWNs of course. So not being network devices they will not show up in a lanscan output.

BUT....a FDDI card IS a network device & DOES have a MAC & WILL show up in a lanscan output.
There is NO FDDI device to run a fcmsutil or tdutil command against. So those utilities are useless in this regard. Just because a card uses fibre for media does not mean it's a fibre channel card.

What about *any* of that is wrong or counter-productive?

Rgds,
Jeff

[Mike Spencer]

What was so "subtle" about it?

If you want specifics, here are the counter-productive elements to your post:

1) "Nice try Mel."
2) "Even though it's fibre it's *still* a LAN device. Using your logic a GigE fibre would also need fcmsutil, huh?"
3) More generally...Do you really think it was necessary to post the entire man page for FDDI?

I'll admit, I just skimmed the thread and didn't distinguish FDDI from FC when I read it. My search, though, for "MAC for FC" lead me here and Mel's post was helpful.

I think most people that post here, especially "olympians", tend to keep their posts professional and accusation-free and I think that's the way it should be.


Mike

[Ashwani Kashyap]

The FDDI driver is a LAn driver/interface and if you have the correct drivers/patches you should get the MAc address via lanscan . The card type will be FDDI .
But lanscan will do it .