WWN and NAA Identifier Lookup
Lookup online WWN and NAA identifiers from SAN text, device paths, and hex tokens to decode shape, company ID, and triage next actions.{{ result.summaryTitle }}
| Field | Value | Copy |
|---|---|---|
| {{ row.label }} | {{ row.value }} |
| Current | Token | Route | Profile | Assessment | Use | Copy |
|---|---|---|---|---|---|---|
| {{ row.rankLabel }} |
{{ row.tokenDisplay }}
{{ row.rawDisplay }}
|
{{ row.routeSummary }} | {{ row.profile }} |
{{ row.statusText }}
{{ row.reason }}
|
Active |
| Segment | Range | Value | Meaning | Copy |
|---|---|---|---|---|
| {{ row.label }} | {{ row.range }} | {{ row.value }} | {{ row.meaning }} |
| Priority | Action | Why | Copy |
|---|---|---|---|
| {{ row.priority }} | {{ row.action }} | {{ row.why }} |
By copying or publishing this embed code, you are responsible for how the tool appears and is used on your website.
- The embedded tool is provided for general informational and utility purposes only. It is not professional, legal, financial, medical, safety, or compliance advice.
- Results depend on the inputs, browser behavior, available data sources, and the current version of the tool. Review important results before relying on them.
- You are responsible for the surrounding page context, labels, instructions, privacy notices, accessibility, and any laws or policies that apply to your website.
- Do not embed the tool in a misleading, unlawful, harmful, or security-sensitive context.
- Simplified Tools may update, limit, suspend, or remove tools and embed behavior without prior notice.
- Analytics, network requests, cookies, browser storage, third-party services, and query parameters may apply depending on the tool and the embedding page.
If these terms do not work for your use case, do not embed the tool.
World Wide Names and NAA identifiers are durable storage identifiers used in Fibre Channel, SCSI, SAS, NVMe, and array inventory workflows. They often appear with punctuation, prefixes, Linux by-id paths, Solaris device paths, zoning output, or log fragments.
The operational risk is transcription error. A nearby node name, port name, LUN identifier, or path token can look similar to the value you meant to zone or mask. Decoding the shape, company ID, extraction route, and candidate queue helps separate a ready identifier from a fragment or the wrong adjacent token.
Structural parsing does not prove that a device is live, owned by a specific team, or safe to change. Use the decoded value as a triage aid, then confirm it against switch, host, and array records before acting.
Technical Details:
The lookup removes punctuation and non-hex text, collects WWN-like candidates from storage-specific wrappers, and chooses the strongest candidate according to selected shape, standard length, even byte alignment, validation readiness, and route priority. Strict mode accepts complete 16-hex or 32-hex values. Triage mode can review even-length fragments with 12 or more hex digits.
| NAA code | Label | Company ID position | Common use context |
|---|---|---|---|
| 1 | NAA 1 IEEE 48-bit | Hex digits 5-10 | Legacy 64-bit WWN, WWPN, or WWNN style name |
| 2 | NAA 2 IEEE Extended | Hex digits 5-10 | 64-bit WWN with locally assigned extension bits |
| 5 | NAA 5 IEEE Registered | Hex digits 2-7 | Registered 64-bit format often used for WWPNs and WWNNs |
| 6 | NAA 6 IEEE Registered Extended | Hex digits 2-7 | Extended identifiers common for device or LUN UIDs |
The tool also recognizes embedded forms such as naa. tokens, wwn-0x paths, scsi-3 and scsi-2 identifiers, nvme-eui tokens, nn-0x and pn-0x fabric references, fc-0x tokens, Solaris cXtWWNd paths, byte-pair strings, dotted 4-hex groups, 0x prefixes, and compact hex.
| State | Trigger | Interpretation |
|---|---|---|
| Ready for copy | Matches selected 64-bit or 128-bit shape, or auto detects a standard length | Use a canonical form consistently after external confirmation |
| Review before use | Valid standard length but wrong expected shape, or triage fragment | Recover workflow context before using the value |
| Recover source first | No hex, odd-length hex, or strict-mode nonstandard length | Find the complete source identifier before zoning or masking |
Everyday Use & Decision Guide:
Paste the whole SAN fragment when you are unsure where the identifier starts. The Token Queue keeps multiple candidates visible, which is useful when a log line contains both a node name and a port name or both host and device identifiers.
Use Expected shape when your workflow is clear. Choose 64-bit for host WWPN or WWNN work, 128-bit for naa.-style device or LUN identifiers, and Auto for mixed triage. Use Triage fragments only when screenshots or logs are incomplete.
- Copy Normalized hex only after status says Ready for copy.
- Check WWN Field Map before assuming which bytes are company ID.
- Use WWN Next Checks when multiple candidates or NAA 6/device-style values appear.
- Treat vendor hints as routing clues, not ownership proof.
A parsed 32-hex value may be a storage object or LUN UID rather than a host port. Confirm the surrounding context before putting it into zoning or host registration notes.
Step-by-Step Guide:
- Paste WWN or NAA text. If no identifier is found, recover the original command output, path, or ticket text.
- Open Advanced and choose an Example preset only for learning, or set Validation and Expected shape for the current workflow.
- Read the summary badge for Ready for copy, Review before use, or Recover source first.
- Open WWN Decode Fields and WWN Field Map to review normalized hex, byte-pair form, word-group form, NAA family, and company ID.
- Review WWN Token Queue and WWN Next Checks before using the identifier operationally.
Interpreting Results:
Ready for copy means the value satisfies the selected structural length policy. It does not prove the path is active or that the vendor hint owns the live device. Review before use means the value might be useful, but its shape or completeness does not match the selected workflow.
The Token Queue is important when more than one candidate appears. The selected candidate is the tool's best fit, but an alternate row may be the actual port, node, or device identifier you need.
Worked Examples:
10:00:00:60:69:00:23:74 becomes normalized hex 1000006069002374, a 64-bit NAA 1 style value with company ID digits 5-10. The status can be Ready for copy under Auto or 64-bit expected shape.
naa.6006016000001234567890ABCDEF1234 is a 32-hex NAA 6 style identifier. The next check is to confirm whether it names a storage object or LUN rather than a host port.
A 12-hex fragment such as 600601600000 fails strict mode but can be reviewed in Triage fragments mode. It should not be used for zoning or masking until the full 16-hex or 32-hex value is recovered.
FAQ:
What is the difference between WWN, WWPN, and WWNN?
WWN is the general identifier family. WWPN usually names a port, while WWNN usually names a node. The lookup can decode structure, but surrounding switch or host context is needed to prove port-versus-node use.
Why does the vendor say unresolved?
The local storage hint table did not match the extracted company ID. Cross-check an authoritative registry or your switch OUI database before using vendor ownership in a decision.
Why did strict mode reject my value?
Strict mode accepts only complete 16-hex or 32-hex identifiers. Use Triage fragments only to inspect incomplete text, then recover the full value before operational use.
Can I paste a whole device path?
Yes. The lookup extracts candidates from Linux by-id paths, Solaris device paths, naa. tokens, wwn-0x tokens, and related storage text.
Glossary:
- NAA
- Name Address Authority, the leading code that identifies the storage identifier format.
- OUI
- Organizationally Unique Identifier, the company ID portion used as a vendor clue.
- WWPN
- World Wide Port Name, commonly used in Fibre Channel zoning.
- WWNN
- World Wide Node Name, commonly used to identify a node rather than one port.