WWN and NAA Identifier Lookup

A storage change can turn on one small hexadecimal name. In Fibre Channel and SCSI-family environments, World Wide Names (WWNs) and Network Address Authority (NAA) identifiers give hosts, switches, arrays, and operating systems a durable way to refer to ports, nodes, devices, and logical units. Those names matter because ordinary device names such as /dev/sdb can change after a reboot, path failover, enclosure move, or controller replacement.

The difficult part is not only finding a hex string. The same SAN note can contain a World Wide Port Name (WWPN), a World Wide Node Name (WWNN), a device WWID, and a LUN-style NAA value in one line. A port identifier that belongs in a zoning worksheet is not the same operational object as a storage-object identifier copied from a Linux persistent path. Mixing those roles can send a change record, escalation, or masking step toward the wrong target.

NAA is the leading format code inside many storage identifiers. The first hexadecimal nibble tells the reader which family is being used, and the following digits may carry an IEEE organizational value plus vendor-controlled fields. A complete 64-bit WWN contains 16 hexadecimal characters. A complete 128-bit NAA-style identifier contains 32 hexadecimal characters. Colons, dots, dashes, prefixes, and path wrappers change how the value is printed, not the underlying bytes.

Structural clues are useful, but they are not inventory proof. A value can have the right length, a recognized NAA family, and a familiar company ID while still pointing at the wrong port, node, device, or stale path. The decode should clean up the identifier and narrow the next check, then host, switch, array, or asset records should confirm the live object.

How to Use This Tool:

Use the lookup as a cleanup and triage step before a WWN or NAA value enters zoning, masking, inventory, or escalation notes.

1. Paste the value or surrounding SAN text into WWN or NAA text. A full path or log line is often safer than a hand-copied fragment because the lookup can surface several candidate identifiers.
2. Keep Example preset on Custom for real work, or load a preset when you want to compare common WWPN, NAA, Linux by-id, Solaris, NVMe EUI, mixed-log, or fragment inputs.
3. Set Validation to Strict 16 or 32 hex for operational values. Use Triage fragments 12+ hex only when you are intentionally recovering evidence from an incomplete note, screenshot, or ticket.
4. Choose Expected shape before trusting the first row. Use 64-bit WWN for WWPN or WWNN work, 128-bit NAA for device or LUN identifiers, and Auto when the pasted text may contain both.
5. Run Lookup and read the summary status. Ready for copy means the selected value matches a complete length policy, Review before use means the value still needs confirmation, and Recover source first means the source text is not safe to reuse.
6. Check WWN Decode Fields for Normalized hex, display forms, Validation verdict, Identifier family, Company ID / OUI, Vendor hint, and Storage context.
7. Open WWN Token Queue when more than one token appears. Use an alternate row only when its surrounding label, path, or command output matches the job you are doing.
8. Use WWN Field Map to record the digit ranges and WWN Next Checks to choose the next host, switch, array, registry, or inventory confirmation.

Interpreting Results:

Start with Validation verdict and Normalized hex. Those fields tell you whether the selected token is byte-aligned, complete under the chosen policy, and ready to copy in a consistent form. Then read Identifier family, Company ID / OUI, Vendor hint, and Storage context to decide what the value is likely to represent.

• Ready for copy means the shape is complete. It does not prove that the port is logged in, that the device is mapped, or that the value belongs to the vendor shown by the local hint.
• Review before use means the token may help a search or incident note, but it does not match the selected shape or complete-length rule strongly enough for a change record.
• Recover source first means the copied text lacks usable hex, has an odd number of hex characters, or fails strict length rules. Return to the original command output or record before acting on it.

A ranked candidate is a starting choice, not an authority. Mixed discovery output can place a node name, port name, and device identifier next to each other. When WWN Token Queue contains several rows, pick the row whose label and surrounding text match the task, then verify it against switch, host, multipath, array, or inventory records.

Technical Details:

WWN-style values are hexadecimal byte strings. Two hex characters form one byte, so a complete 64-bit value has 16 hex characters and a complete 128-bit value has 32. Separators such as colons, dots, hyphens, and path prefixes are display conventions. The canonical value is the cleaned hexadecimal sequence.

The NAA nibble is the first four bits of many Fibre Channel-style identifiers. It declares which address format is being used and where the IEEE company identifier appears. NAA 5 and NAA 6 place the 24-bit company identifier immediately after the NAA digit, while NAA 1 and NAA 2 carry reserved or vendor-controlled bits before the company identifier. Vendor-controlled tails are not globally interpretable without platform records.

Rule Core

Candidate extraction favors storage-specific wrappers before plain hexadecimal text. The accepted forms include naa. tokens, wwn-0x paths, SCSI by-id values such as scsi-3 and scsi-2, nvme-eui. paths, Fibre Channel nn-0x, pn-0x, and fc-0x values, Solaris-style target paths, byte-pair strings, dotted 4-hex groups, 0x tokens, and compact 16- or 32-hex values.

Transformation Core

1. Collect WWN-like candidates from storage wrappers and plain hex text, merging duplicate normalized values when the same identifier appears in several forms.
2. Remove non-hex characters, uppercase the token, and keep the normalized value as the copy-safe form.
3. Rank candidates by explicit user selection, expected 64-bit or 128-bit shape, standard length, even byte alignment, validation readiness, storage-specific wrapper, position in the pasted text, and token length.
4. Decode the NAA family from the first hex digit and extract the company identifier from the family-specific digit range.
5. Build follow-up checks from the validation state, candidate count, 128-bit or NAA 6 shape, path-style extraction, and whether the company identifier has a local vendor hint.

Company ID and vendor hints should be read as routing clues. IEEE-administered organizational identifiers help explain part of the value, but the live ownership of a port, node, device, or LUN still depends on the storage environment that reported it.

Worked Examples:

Known vendor WWPN. 50:06:01:68:43:B2:C1:D0 becomes 5006016843B2C1D0 in Normalized hex. With Expected shape set to 64-bit WWN, the Validation verdict is ready for the selected shape, Identifier family reads as NAA 5, and Company ID / OUI resolves to 00:60:16. The vendor hint can speed triage, but the zone still needs confirmation that this is the intended port.

Linux by-id LUN value. /dev/disk/by-id/scsi-36006016000001234567890abcdef1234 yields 6006016000001234567890ABCDEF1234. Under 128-bit NAA, the length fits a complete extended identifier, and Storage context points toward a device or LUN workflow. Do not substitute it for an HBA WWPN without host or array confirmation.

Mixed discovery output. nn-0x20000090FAE0B5F5:pn-0x10000090FAE0B5F5 remote=/dev/disk/by-id/scsi-36006016000001234567890ABCDEF1234 contains node, port, and device-style candidates. WWN Token Queue lets you promote the row that matches the task before reading WWN Field Map.

Fragment from an incident note. 600601600000 fails strict operational use because it is neither 16 nor 32 hex characters. In Triage fragments 12+ hex, the Validation verdict changes to Review before use, which is useful for searching logs but not for zoning, masking, or asset updates.

Advanced Tips:

• Use Strict 16 or 32 hex for change tickets, zoning sheets, and asset records. Triage mode is for recovering partial evidence, not for approving an operational value.
• Set Expected shape before reading mixed SAN output. A 64-bit target favors WWPN and WWNN work, while a 128-bit target favors device or LUN identifiers.
• When WWN Token Queue lists several candidates, compare the source label and surrounding text before selecting a row. Node, port, and device identifiers can appear beside each other in one paste.
• Copy Normalized hex for records that need one stable representation, then keep a coloned display form only when the receiving system or worksheet expects byte-pair notation.
• Treat Vendor hint as a routing clue. Confirm live ownership with switch login, host adapter, array mapping, multipath, or inventory records before changing storage access.
• Use WWN Next Checks as a checklist after the decode, especially when the status is Review before use or the company ID comes from a heuristic prefix.

FAQ:

Glossary:

WWN

World Wide Name, a durable hexadecimal storage identifier used for ports, nodes, devices, or storage objects.

WWPN

World Wide Port Name, commonly used to identify one Fibre Channel port.

WWNN

World Wide Node Name, commonly used to identify a Fibre Channel node or adapter.

NAA

Network Address Authority, the leading format code that identifies the naming authority and layout of many WWN-style values.

OUI

Organizationally Unique Identifier, a 24-bit IEEE-administered organizational value used here as a company ID clue.

LUN

Logical unit number, a storage addressing concept often involved when an extended NAA value names a presented device.

References:

• Guidelines for Use of Extended Unique Identifier, Organizationally Unique Identifier, and Company ID, IEEE Registration Authority, April 1, 2022.
• Guidelines for Fibre Channel Use of the Company_id, IEEE Registration Authority.
• The SNIA Dictionary, SNIA, April 28, 2026.
• Persistent naming attributes, Red Hat Enterprise Linux 10.