WWN and NAA Identifier Lookup
Extract WWN and NAA values from SAN text and normalize the hex before decoding identifier fields or flagging fragments for operational review.{{ summaryTitle }}
{{ summaryLine }}
{{ primaryCopyAnnouncement }}
| Field | Value | Meaning | Copy |
|---|---|---|---|
| {{ row.label }} | {{ row.value }} | {{ row.detail }} |
The chart renderer is unavailable. Exact digit ranges remain available in the Decode record.
| Rank | Identifier | Source | Assessment | Use | Copy |
|---|---|---|---|---|---|
| {{ row.rank }} | {{ row.normalized }} | {{ row.source }} | {{ row.assessment }} | Selected |
| Priority | Check | Reason | Copy |
|---|---|---|---|
| {{ row.priority }} | {{ row.action }} | {{ row.reason }} |
Storage paths stay useful only when every hexadecimal identifier is tied to the right object. A switch report can place a World Wide Port Name (WWPN), World Wide Node Name (WWNN), device identifier, and logical-unit identifier beside one another. They may share the same 16- or 32-digit appearance while serving different operational roles.
World Wide Name (WWN) is a broad storage-networking term. WWPN identifies a Fibre Channel port and commonly appears in zoning or masking work. WWNN identifies a node that may contain several ports. Network Address Authority (NAA) is a structured identifier format whose leading hexadecimal digit selects a family and whose remaining fields can include an IEEE company identifier plus vendor-assigned bits.
| Evidence source | Likely identifier role | Verification needed |
|---|---|---|
| HBA or switch port output | WWPN or WWNN | Confirm the label identifies a port or a node |
Linux by-id path | SCSI or NVMe device identifier | Map the persistent path to the current device |
| Array or multipath report | Device, target, or logical unit | Confirm array ownership and LUN context |
| Incident text with several hex values | Mixed candidates | Keep the source label with the selected value |
Removing colons, dots, dashes, and wrappers is useful for comparison, but it does not discover the identifier's live owner. The first nibble can reveal an NAA family and a company field can suggest an assignee; neither proves that the value currently belongs to a particular host, switch port, array, device, or LUN.
A fragment is valuable for searching logs but unsafe for zoning, masking, inventory, or change execution. Operational reuse should begin with a complete identifier and end with confirmation in the live storage system or an authoritative inventory record.
How to Use This Tool:
Paste the smallest useful SAN excerpt and keep enough surrounding labels to distinguish adjacent identifiers.
- Paste up to 8,192 characters into SAN text or identifier. A direct WWN, a persistent path, or a short log excerpt can all be inspected.
- Leave Identifier shape on Auto detect unless you know the source must contain a 64-bit WWN or 128-bit NAA value. A pinned shape changes candidate ranking.
- Use Strict complete identifiers for operational records. Choose Triage only when an even fragment of at least 12 hex digits is useful for investigation.
- Review the selected normalized value, family, company field, and candidate queue. If several candidates were found, choose the row whose source label matches the intended port, node, device, or LUN.
Interpreting Results:
Ready for copy means the selected token contains exactly 16 or 32 hexadecimal digits and does not conflict with the requested shape. It is a structural verdict, not proof of ownership, uniqueness, reachability, zoning, masking, or active paths. Review before use marks a permitted fragment or a complete value that differs from the pinned shape.
Carry the normalized hex into a change record only after matching it to live switch, host, array, or inventory evidence. Treat the vendor hint as a clue from a small local mapping. A missing hint does not make the identifier invalid, and a matching prefix does not prove the current manufacturer or device role.
Technical Details:
Hexadecimal normalization uppercases the candidate and removes every non-hex separator or wrapper character. Sixteen hex digits represent 64 bits; 32 hex digits represent 128 bits. The parser recognizes common WWN, NAA, SCSI, NVMe, Fibre Channel, Solaris path, byte-pair, dotted-word, 0x, and compact forms.
Rule Core:
| Condition | Strict mode | Triage mode |
|---|---|---|
| 16 hex digits | Ready for copy | Ready for copy |
| 32 hex digits | Ready for copy | Ready for copy |
| Even fragment, 12 or more hex digits | Rejected | Review before use |
| Odd number of hex digits | Rejected | Rejected |
| Complete value differs from pinned shape | Review before use | Review before use |
Candidate selection first honors a row chosen by the reader. A pinned 64- or 128-bit shape then favors that length; otherwise complete identifiers outrank fragments. Recognizable wrappers outrank generic hexadecimal matches, earlier source positions break remaining ties, and longer candidates win last.
Lookup Core:
| Leading nibble | Family | Company identifier | Typical context |
|---|---|---|---|
1 | NAA 1, IEEE 48-bit | Hex digits 5–10 | Legacy 64-bit WWN form |
2 | NAA 2, IEEE extended | Hex digits 5–10 | Legacy extended 64-bit form |
5 | NAA 5, IEEE registered | Hex digits 2–7 | Common WWPN or WWNN form |
6 | NAA 6, IEEE registered extended | Hex digits 2–7 | Storage device, object, or logical-unit form |
For other leading nibbles, the first six digits are shown only as a prefix heuristic. The vendor hint covers a small set of known company identifiers and is not a live IEEE registry lookup.
Transformation Core:
The selected text follows a short, auditable path: recognize candidate wrappers, strip separators, rank the normalized values, validate length and shape, read the NAA family nibble, extract the family-specific company field, then divide the remaining digits into vendor or extension regions. The displayed byte-pair and four-digit word forms are alternate groupings of the same normalized hex; no bits are added or removed.
For NAA 5 and NAA 6, digit 1 is the family nibble, digits 2–7 hold the 24-bit company identifier, and digit 8 onward is vendor-assigned. NAA 6 values longer than 16 digits show the base 64-bit body separately from the extended tail. That anatomy helps compare records but still cannot infer a port, node, device, or LUN role from length alone.
For example, pn-0x5006016843B2C1D0 becomes 5006016843B2C1D0. The 16 digits form a complete 64-bit value and the leading 5 selects NAA 5. The pn source label remains the stronger clue that this particular value was presented as a port name.
Privacy and Accuracy Notes:
Parsing, ranking, validation, and vendor hints run in the browser without querying a switch, storage array, registry, or remote lookup service. Source context is excluded from candidate exports unless Candidate export context is enabled.
- Local parsing cannot verify that a candidate is assigned, unique, reachable, or currently in use.
- Vendor mappings are deliberately limited and can become incomplete as assignments or product ownership change.
- SAN logs may contain sensitive topology and asset data even when processing stays local; review exports before sharing them.
References:
- Guidelines for Fibre Channel Use of the Company_id, IEEE Registration Authority.
- Guidelines for Use of EUI, OUI, and Company ID, IEEE Registration Authority, April 1, 2022.
- SNIA Dictionary, Storage Networking Industry Association.
- Persistent naming attributes, Red Hat Enterprise Linux 10.