Hubbry Logo
World Wide NameWorld Wide NameMain
Open search
World Wide Name
Community hub
World Wide Name
logo
7 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
World Wide Name
World Wide Name
World Wide Name
View on Wikipedia
from Wikipedia

A World Wide Name (WWN) or World Wide Identifier (WWID) is a unique identifier used in storage technologies including Fibre Channel, Parallel ATA, Serial ATA, SCSI and Serial Attached SCSI (SAS).[1]

A WWN may be employed in a variety of roles, such as a serial number or for addressability; for example, in Fibre Channel networks, a WWN may be used as a WWNN (World Wide Node Name) to identify an endpoint, or a WWPN (World Wide Port Name) to identify an individual port on a switch. Two WWNs which do not refer to the same thing should always be different even if the two are used in different roles, i.e. a role such as WWPN or WWNN does not define a separate WWN space. The use of burned-in addresses and specification compliance by vendors is relied upon to enforce uniqueness.

Formats

[edit]

Each WWN is an 8- or 16-byte number, the length and format of which is determined by the most significant four bits, which are referred to as an NAA (Network Address Authority). The remainder of the value is derived from an IEEE OUI (or from Company Id (CID)) and vendor-supplied information. Each format defines a different way to arrange and/or interpret these components. OUIs are used with the U/L and multicast bits zeroed, or sometimes even omitted (and assumed zero), though CID has U/L set to 1.[2]

The WWN formats include:[3]

  • "Original" IEEE formats are essentially a two-byte header followed by an embedded EUI-48 address (which contains the OUI). The first 2 bytes are either hex 10:00 or 2x:xx (where the x's are vendor-specified) followed by the 3-byte OUI and 3 bytes for a vendor-specified serial number. Thus, the difference between NAA 1 format and NAA 2 format is merely the presence of either a zero pad or an extra 3 nibbles of vendor information.
  • "Registered" IEEE formats dispense with padding and place the OUI immediately after the NAA. The OUI is no longer considered to be part of a EUI-48 address. For NAA 5 format, this leaves 9 contiguous nibbles for a vendor-defined value. This is the same format used by the companion NAA 6 format, the only difference being a 16-byte number space is assumed, rather than an 8-byte number space. This leaves a total of 25 contiguous nibbles for vendor-defined values.
  • "Mapped EUI-64" formats manage to fit an EUI-64 address into an 8-byte WWN. Since the NAA is mandatory, and takes up a nibble, this represents a four-bit deficit. These four bits are recouped through the following tricks: First, two bits are stolen from the NAA by allocating NAAs 12, 13, 14, and 15 to all refer to the same format. Second, the remaining two bits are recouped by omitting the U/L and multicast bits from the EUI-64's OUI. When reconstructing the embedded EUI-64 value, the U/L and multicast bits are assumed to have carried zero values.

Presentation

[edit]

WWN addresses are predominantly represented as colon separated hexadecimal octets, MSB-first, with leading zeros — similar to Ethernet's MAC address. However, there is much variance between vendors.[4]

Example usage

[edit]

Linux uses WWN to identify disks by providing symbolic links to the real device entry: 

ls -l /dev/disk/by-id/
[…]
lrwxrwxrwx 1 root root  9 Jul  4 22:00 wwn-0x5002e10000000000 -> ../../sr0
lrwxrwxrwx 1 root root  9 Jul  4 22:00 wwn-0x500277a4100c4e21 -> ../../sda
lrwxrwxrwx 1 root root 10 Jul  4 22:00 wwn-0x500277a4100c4e21-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Jul  4 22:00 wwn-0x500277a4100c4e21-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Jul  4 22:00 wwn-0x500277a4100c4e21-part3 -> ../../sda3

(There are more entries in this directory which are omitted here)

The target names (sr0, sda) might change when new devices are added to the computer (e.g. sda might become sdb) but the WWN will be the same. That is an advantage when the WWNs are used in configuration files and scripts, e.g., /etc/fstab.

How to Find WWN Information in Linux

[edit]

There are various ways how to find WWN information.[5]

Regardless of HBA type, below commands can be used to find WWN number information.

Method 1

[edit]
# cat /sys/class/fc_host/host*/port_name

0x10000090fa2537d6

0x10000090fa253a29

Method 2 : using syminq command

[edit]

If EMC Storage is being used so there is a chance you must have SYMCLI software installed. syminq comes with SYSCLI. syminq is also helpful in getting WWN in easy way. 

[root@server]# syminq hba
Host Name : server
HBA Type            : FibreChannel
HBA Name            : Emulex-LPe11000-E-2
Vendor              : Emulex Corporation
Model               : LPe11000-E
Serial Number       : BT01473025
Firmware Version    : 2.72A2 (Z3D2.72A2), sli-3
Driver Version      : 8.2.0.63.3p; HBAAPI(I) v2.1.g, 12-07-07
Node WWN            : 20000000c9b0513a
Number of Ports     : 1
Port WWN            : 10000000c9b0513a
Port name           : /sys/class/scsi_host/host3
Port type           : NPort
Port FCID           : 2764032
Port speed          : 4gbit
Supported speed     : 4gbit
Port state          : Online
Supported COS       : 00000008
Supported FC4 types : 0000010000000001000000000000000000000000000000000000000000000000
Active FC4 types    : 0000010000000001000000000000000000000000000000000000000000000000
Max frame size      : 2048

Method 3 : using hbacmd command

[edit]

It will work if hbanyware package is installed. 

[root@server]# /usr/sbin/hbanyware/hbacmd listHBAs
Manageable HBA List
Port WWN   : 10:00:00:00:c9:b0:55:2e
Node WWN   : 20:00:00:00:c9:b0:55:2e
Fabric Name: 10:00:50:eb:1a:5f:c7:0c
Flags      : 8000fe00
Host Name  : server
Mfg        : Emulex Corporation
Serial No. : BT01474056
Port Number: n/a
Mode       : Initiator
Port WWN   : 10:00:00:00:c9:b0:51:32
Node WWN   : 20:00:00:00:c9:b0:51:32
Fabric Name: 10:00:50:eb:1a:5f:bd:0c
Flags      : 8000fe00
Host Name  : server
Mfg        : Emulex Corporation
Serial No. : BT01472998
Port Number: n/a
Mode       : Initiator
[root@server]#

Method 4 : using systool command

[edit]

systool utility comes with Linux distros. If it is not available it can be installed on servers where HBA is already installed. 

 # systool -c fc_host -v
(output trimmed for clarity)
  Class Device path = "/sys/class/fc_host/host8"    port_name           = "10:00:00:00:c9:b0:51:32"    node_name           = "20:00:00:00:c9:b0:51:32"

List of OUIs commonly seen as WWN Company Identifiers

[edit]

OUIs can be queried searching the IEEE organization's Public Manufacturers OUI list. OUIs can also be queried by searching IEEE Standards Registration authority [1].

See also

[edit]
[edit]

References

[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

World Wide Name

View on Grokipedia
from Grokipedia
A World Wide Name (WWN) is a globally , typically 64 bits or 128 bits in length, assigned by manufacturers to nodes and ports in storage networking technologies such as (FC), (SAS), and Advanced Technology Attachment (ATA), functioning analogously to a in Ethernet networks for ensuring device identification in storage area networks (SANs). WWNs are structured according to the Network Address Authority (NAA) format defined by the INCITS T11 committee, where the NAA identifier specifies the type and ensures uniqueness through a combination of company-assigned codes and vendor-specific extensions, often represented in hexadecimal ASCII for interoperability across FC, SAS, and iSCSI environments. There are two primary types: the Node World Wide Name (WWNN), which identifies an entire device or node, and the Port World Wide Name (WWPN), which identifies a specific port on that node, allowing for precise addressing in FC fabrics. In FC SANs, WWNs are hard-coded into hardware like host bus adapters (HBAs), switches, and storage arrays at the factory, enabling , LUN masking, and fabric login processes without requiring dynamic assignment, which supports scalable and secure connectivity in enterprise storage infrastructures. Beyond FC, WWNs facilitate consistent naming in SAS domains for and in for extending FC semantics over IP networks, promoting as outlined in standards like FC-FS (Framing and Signaling). The assignment process is overseen by registration authorities to prevent duplicates, with the IEEE managing portions of the for vendor use.

Overview

Definition

A World Wide Name (WWN) is a globally assigned to network interfaces, nodes, and ports in storage technologies, particularly those utilizing serial bus topologies like . It functions as a permanent, hardware-based address, akin to a in Ethernet networks, but is specifically designed for high-speed storage area networks (SANs) where reliable device identification is essential. WWNs are hard-coded into devices by manufacturers to ensure persistence across reboots, fabric changes, or network reconfigurations. WWNs are available in 64-bit or 128-bit formats, with the 64-bit variant being the most common in traditional implementations, while 128-bit extensions support advanced addressing needs in modern storage protocols. This structure allows for an immense , preventing collisions in large-scale deployments. Manufacturers derive WWNs from IEEE-assigned Organizationally Unique Identifiers (OUIs) to guarantee worldwide uniqueness without central coordination beyond the initial assignment. In distinction from other network identifiers, MAC addresses are confined to Ethernet layer-2 framing and local connectivity, whereas WWNs enable end-to-end identification in lossless, ordered-delivery environments like SANs. Similarly, IP addresses serve as dynamic, routable layer-3 identifiers that can be reassigned, but WWNs remain immutable to support consistent device tracking in storage ecosystems. The historical roots of WWNs trace to IEEE standards for Extended Unique Identifiers (EUIs), developed in the and 1990s to provide scalable, unique addressing for emerging serial bus architectures, including those standardized by the INCITS T11 committee for .

Purpose and Importance

World Wide Names (WWNs) serve as permanent, globally unique identifiers for devices and ports in storage area networks (SANs), enabling consistent recognition regardless of physical port changes or dynamic network reconfigurations. This permanence is crucial in environments like Fibre Channel SANs, where devices frequently connect and disconnect, preventing identification conflicts that could disrupt connectivity. WWNs play a key role in mechanisms such as and LUN masking, where they define authorized device interactions to ensure secure and reliable data access. In , WWNs allow flexible grouping of initiators and into isolated communication domains, enhancing by limiting visibility and broadcast traffic. For LUN masking, storage arrays use WWNs to selectively expose logical unit numbers (LUNs) to specific hosts, preventing unauthorized access. Additionally, in multipathing configurations, WWNs maintain device identity across redundant paths, supporting and load balancing to minimize during path failures. In enterprise storage, WWNs facilitate fault isolation by enabling precise device tracking during diagnostics, allowing administrators to pinpoint issues without affecting the broader network. They also support inventory management through SAN tools that catalog devices by WWN, simplifying asset tracking and compliance in large-scale deployments. Duplicate WWNs within a fabric are strictly prohibited and can lead to severe issues, including rejected logins, disabled ports, path outages, and potential network disruptions or from conflicting access. Fabric switches typically detect and isolate duplicates to preserve stability, underscoring the critical need for unique assignments.

Structure

Components

A World Wide Name (WWN) in its standard 64-bit configuration consists of a 4-bit Network Address Authority (NAA) field, followed by a 24-bit (OUI) assigned by the IEEE to the manufacturer (in certain formats), and vendor-specific extension fields that allow the vendor to uniquely assign the remaining portion based on serial numbers or other internal schemes. The NAA field specifies the overall format and authority of the WWN, such as IEEE registered (NAA 5) or extended formats, ensuring global uniqueness while adhering to standardized allocation rules. This structure derives from the IEEE Extended Unique Identifier (EUI-64) standard, adapted for storage networking protocols like , where the OUI portion uniquely ties the identifier to the producing organization. For advanced scenarios involving , 128-bit WWNs extend the structure to accommodate N_Port ID Virtualization (NPIV), incorporating a 4-bit NAA, 24-bit OUI, and up to 100 bits of vendor-specific data (including virtualization-specific indicators like port indices or logical unit extensions) to support multiple virtual ports sharing a physical interface without identifier collisions. These extended WWNs, often using NAA format 6 (IEEE Registered Extended), enable finer-grained identification in virtualized environments by embedding hierarchical elements like domain or partition details, allowing a single physical node to present numerous distinct logical identities to the fabric. The adoption of 128-bit formats addresses scalability limitations in dense virtualization setups, where traditional 64-bit addressing might exhaust available unique combinations. WWNs are differentiated by scope into Node WWNs (WWNNs) and Port WWNs (WWPNs), with the WWNN serving as a device-wide identifier that remains consistent across all ports on a given node, such as a host bus adapter or storage controller, to represent the entire entity in . In contrast, the WWPN is port-specific, uniquely identifying an individual port to facilitate precise and within the fabric, even as multiple ports on the same node share the underlying WWNN. This distinction ensures that network policies can target either the broader node for administrative purposes or specific ports for connectivity management, enhancing flexibility in storage area networks. The IEEE defines specific types for WWNs through the Network Address Authority (NAA) field, supporting affiliations for unique entity identification, group affiliations via the individual/group (I/G) bit in the first octet (0 for , 1 for group addressing in scenarios), and domain affiliations in extended formats that incorporate fabric domain elements for hierarchical networking. These types, such as NAA 1 (IEEE 48-bit ), NAA 2 (extended group-capable), and NAA 5/6 (registered with domain support), allow WWNs to adapt to diverse affiliation needs while maintaining global uniqueness.

Formats and Encoding

World Wide Names (WWNs) are encoded as 64-bit values, represented in notation as a 16-character string, often separated by colons or hyphens for readability, such as 21:00:00:20:37:49:91:5c. This format ensures uniqueness across networks and related technologies, with the hexadecimal digits directly corresponding to the binary bits of the WWN. The encoding rules are specified in standards from the INCITS T11 committee, including FC-FS for framing, which defines the NAA-based structures. The binary structure of a WWN begins with a 4-bit Network Address Authority (NAA) identifier in the most significant , followed by fields allocated for company identification and vendor-specific data. For NAA type 1 (IEEE format, binary 0001), the structure allocates the NAA in bits 63-60, followed by 12 zero bits (bits 59-48), a 24-bit IEEE-assigned (OUI) in bits 47-24, and a 24-bit vendor-specific identifier in bits 23-0, effectively embedding a 48-bit padded to 64 bits. In contrast, NAA type 2 (IEEE extended, binary 0010) uses bits 63-60 for the NAA, bits 59-48 for 12 bits of vendor-specific data, bits 47-24 for the 24-bit OUI, and bits 23-0 for 24 bits of additional vendor-specific extension, enabling full 64-bit uniqueness without padding. These bit allocations ensure compatibility with IEEE-assigned identifiers while allowing extension for serial numbers or other unique elements. IEEE Registered WWNs, also known as burned-in addresses, utilize globally unique OUIs assigned by the IEEE Registration Authority with the Universal/Local (U/L) bit set to 0 (indicating global administration), ensuring permanence and manufacturer-assigned uniqueness as per IEEE guidelines for EUI formats. Locally Administered WWNs, however, set the U/L bit to 1 (in the OUI field, typically bit 46 for NAA=2), allowing network administrators or vendors to assign identifiers locally without relying on IEEE registration, though this requires careful management to avoid conflicts. The encoding rules for these distinctions are harmonized in FC-BB standards for Fibre Channel over Ethernet, which adopt the same NAA structures to maintain interoperability with IEEE 802.1-based Ethernet addressing.

Display and Notation

Presentation Conventions

World Wide Names (WWNs) are typically presented in notation to facilitate readability in documentation, command-line interfaces, and management tools within environments. The most common format separates the 16 digits into eight pairs using colons, such as 10:00:00:00:c9:xx:xx:xx, where each pair represents one byte of the 64-bit identifier. This colon-separated convention aligns with practices in major SAN vendors' tools, enhancing visual parsing by grouping bytes clearly. Alternatively, WWNs may appear without separators as a continuous 16-digit string, particularly in configuration files or when embedding in scripts, to simplify data entry or transmission. According to standards and industry specifications, hexadecimal digits in WWN presentations should use uppercase letters (A-F) for consistency and to match the formal encoding conventions derived from IEEE guidelines. This uppercase requirement ensures uniformity across documentation and avoids ambiguity in parsing tools that may interpret case differently. However, some implementations deviate slightly; for instance, () Fabric OS command outputs often render digits in lowercase, as seen in switch WWN displays like 10:00:00:05:1e:7a:7a:00. In contrast, and MDS series tools typically employ uppercase or mixed case in examples, such as 21:00:00:20:37:6f:db:bb, prioritizing readability over strict case enforcement in CLI results. In logs, user interfaces, and diagnostic outputs, WWNs are frequently truncated to the last four digits (representing the final two bytes) for brevity, especially when multiple identifiers appear in dense listings or error reports. This practice, common in HPE Storage management interfaces, allows quick identification without overwhelming display space while retaining unique suffixes sufficient for local context. Full WWNs are used in formal configurations or detailed audits to ensure global uniqueness, but truncation aids operational efficiency in high-volume SAN monitoring. Vendor tools may vary this further; for example, interfaces often display complete WWNs in views but abbreviate in summary logs, whereas tools consistently show full formats in port diagnostics with optional filtering. In SAS and environments, WWNs follow similar colon-separated formats for 64-bit identifiers, though SAS may use 128-bit extended formats displayed as 32 hex pairs (e.g., 50:06:0b:00:00:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx). Qualified Names (IQNs) incorporate WWNs but are presented as dotted-decimal strings for IP compatibility.

Examples

A representative example of a World Wide Node Name (WWNN) for a host bus adapter is 10:00:00:00:c9:2f:65:d6, following the NAA-1 (IEEE Company ID) format where the prefix 10:00 indicates use of the vendor's OUI (c9:xx for /Emulex) combined with a derived from the adapter's or . In contrast, a typical World Wide Port Name (WWPN) for a storage array might be 50:00:00:00:00:00:00:01, where the 50:00 prefix signifies a NAA-5 (IEEE Registered) format assigned by the vendor for global uniqueness. This value identifies a specific on the array, such as a front-end interface, and is derived from the vendor's (OUI) combined with sequential numbering for ports. Duplicate WWNs in a Storage Area Network (SAN) can lead to severe operational disruptions, as Fibre Channel fabrics enforce uniqueness to prevent conflicts. For instance, if two devices attempt to login with the same WWPN within the same fabric domain, the switch will reject the second login, potentially isolating one device and causing path failures or data access outages. In multi-domain scenarios, the fabric may remove affected devices and generate reliability, availability, and serviceability (RAS) logs, resulting in unpredictable responses to service requests like port WWN queries and requiring manual intervention to resolve zoning or configuration errors. A real-world example of WWN assignment appears in zoning configuration files, where WWNs are explicitly defined to link hosts and storage. In a MDS switch configuration snippet, WWNs are assigned as follows:

zone name example_zone vsan 1 member pwwn 10:00:00:00:c9:2f:65:d6 member pwwn 50:00:00:00:00:00:00:01 zoneset name example_zs vsan 1 member zone example_zone

zone name example_zone vsan 1 member pwwn 10:00:00:00:c9:2f:65:d6 member pwwn 50:00:00:00:00:00:00:01 zoneset name example_zs vsan 1 member zone example_zone

This setup assigns the HBA's WWPN to connect with the storage port's WWPN, ensuring secure and directed traffic flow within the fabric.

Applications

In Fibre Channel

In Fibre Channel (FC) networks, World Wide Names (WWNs) serve as unique 64-bit identifiers for nodes and ports, enabling precise addressing and connectivity in storage area networks (SANs). Specifically, the World Wide Port Name (WWPN) identifies individual N_Ports on end devices such as hosts or storage arrays, while the World Wide Node Name (WWNN) identifies the overall node. During Fabric Login (FLOGI), an N_Port initiates a session with an F_Port on the fabric switch by sending a FLOGI frame containing its WWNN and WWPN to the well-known address 0xFFFFFE, allowing the switch to assign a dynamic 24-bit Fibre Channel Identifier (FCID) in the domain-area-port format for routing purposes. This process ensures lossless, in-order delivery of frames across the fabric, with the F_Port acting as the interface to upstream fabric services. WWNs integrate deeply with FC fabric services, facilitating discovery, registration, and management. After FLOGI, the N_Port registers with the (a fabric service at well-known address 0xFFFFFC) using its WWPN and WWNN, enabling other devices to query and locate it via the Switch Name Server (SNS) for establishing Port Login (PLOGI) sessions. Fabric services like the Management Service and Login Service also leverage WWNs to authenticate and authorize access, ensuring in multi-domain environments. For instance, during PLOGI between two N_Ports, devices exchange WWPNs and WWNNs along with service parameters to negotiate classes of service and buffer credits. Zoning in FC fabrics relies on WWNs to enforce and isolation by binding specific devices into logical groups. WWPN-based allows administrators to create zones that permit communication only between designated initiator and target WWPNs, preventing unauthorized access across the SAN regardless of physical changes. This soft approach enhances flexibility, as devices can be relocated without reconfiguring zones, while providing isolation to mitigate risks like unauthorized data access or fabric-wide disruptions. In practice, zone sets activated on switches enforce these WWPN bindings at the hardware level, supporting up to thousands of zones per fabric for large-scale deployments. The use of WWNs is mandated by key FC standards developed by the INCITS T11 committee. The Framing and Signaling (FC-FS) standard, which encompasses physical interface specifications like FC-PI, requires WWNs for and node identification in frame headers and payloads to ensure and unique addressing. Similarly, the Fibre Channel Switch Fabric (FC-SW) standard specifies WWNs for fabric topology management, including principal switch selection based on WWN priority and inter-switch linking. These standards, such as FC-SW-6 and FC-FS-5, define WWN formats and their mandatory inclusion in protocols to support scalable, secure fabrics. The role of WWNs has evolved significantly from early FC topologies to modern switched fabrics. In Fibre Channel Arbitrated Loop (FC-AL) environments, WWNs provided hard addressing during loop initialization for up to 126 devices sharing a single loop, but scalability was limited by contention and single-point failures. The transition to switched fabrics under FC-SW standards shifted reliance on WWNs for fabric-wide uniqueness, enabling thousands of devices across multiple switches with dynamic FCID assignment and for isolation, thus improving performance and reliability in enterprise SANs.

In Other Protocols

In iSCSI, World Wide Names (WWNs) are not natively used for node identification, as the protocol relies on iSCSI Qualified Names (IQNs) in the format iqn.yyyy-mm.reversed-domain:specifier to uniquely identify initiators and targets independently of network addressing. However, for with (FC) storage area networks (SANs), iSCSI-to-FC gateways map IQNs to WWNs, assigning virtual WWNs (such as node WWNs and port WWNs) to iSCSI hosts from a pool to enable seamless and LUN masking in mixed environments. This mapping ensures that iSCSI initiators appear as FC nodes, preserving FC management practices like WWN-based while leveraging IP networks for connectivity. In (SAS), WWNs are used as SAS addresses, which are 64-bit unique identifiers for PHYs, ports, and devices, enabling device discovery and addressing in SAS domains for . SAS addresses follow the NAA format similar to FC WWNs, ensuring global uniqueness across expanders and initiators. (FCoE), defined in the T11 FC-BB-5 standard, encapsulates FC frames within Ethernet, allowing WWNs to function identically to native FC implementations. In FCoE endpoints known as ENodes, virtual N_Ports (VN_Ports) utilize port WWNs (pWWNs) and node WWNs (nWWNs) for login, discovery, and frame addressing during the Fibre Channel Initialization Protocol (FIP) process, where VN_Ports establish virtual links with fabric ports (VF_Ports) on FCoE switches. This direct carryover of WWNs in Ethernet frames via VN_Ports enables FCoE to support lossless Ethernet (Data Center Bridging) while maintaining FC's addressing and security models without requiring additional mappings. In NVMe over Fabrics (NVMe-oF), identification extends FC heritage through Namespace Globally Unique Identifiers (NGUIDs), which are optional 128-bit globally unique identifiers assigned by the NVMe controller to namespaces, functioning analogously to WWNs for identification in fabric environments like RDMA, TCP, or FC transports. This approach allows NVMe controllers and namespaces to interoperate with FC-based systems by aligning identifiers with WWN structures in the , facilitating consistent discovery and management in converged storage fabrics. WWNs, designed for FC's addressing architecture, face limitations in pure IP-based protocols, where they lack native support and require protocol-specific extensions or mappings to integrate with IP addressing and routing. In , this necessitates IQN-to-WWN translations via gateways for FC interoperability, potentially introducing overhead in heterogeneous SANs. FCoE mitigates this by embedding WWNs directly in Ethernet but demands specialized lossless networking to avoid frame loss inherent to standard Ethernet. Similarly, NVMe-oF addresses the gap through NGUIDs but still relies on transport-layer adaptations, such as capsule-based encapsulation, to carry these identifiers over IP fabrics without inherent FC zoning semantics.

Discovery and Management

Methods in Linux

In Linux systems, World Wide Names (WWNs) for Fibre Channel Host Bus Adapters (HBAs) and associated SCSI devices can be retrieved using standard command-line utilities that interface with the kernel's sysfs filesystem and SCSI subsystem. These methods provide access to both local HBA WWNs (node and port names) and remote target WWNs without requiring vendor-specific tools. To detect HBAs initially, the [lspci](/page/Lspci) command lists PCI devices, filtering for adapters with options like lspci | [grep](/page/Grep) -i fibre or lspci -nn | [grep](/page/Grep) -i hba, which identifies the device IDs and vendors. Once the HBA is located, WWNs are accessed via paths under /sys/class/fc_host/, where each host directory (e.g., host0) contains files such as node_name for the World Wide Node Name (WWNN) and port_name for the World Wide Port Name (WWPN); for example, cat /sys/class/fc_host/host0/port_name outputs the WWPN value. These attributes are exposed by the transport layer in the . For -level WWN queries on remote targets visible through the HBA, the lsscsi utility enumerates attached devices and, with the --transport option (e.g., lsscsi --transport), displays port names and identifiers for targets, aiding in mapping logical units to their WWNs. Complementing this, sg_inq from the sg3_utils package sends commands to a specific device (e.g., sg_inq /dev/sg0 --page=0x83), retrieving Vital Product Data (VPD) page 0x83 for Device Identification, which includes Network Address Authority (NAA)-formatted WWNs for the target. The systool command, part of the sysfsutils package, provides a formatted view of fc_host attributes with systool -c fc_host -v, listing details like port_name and node_name for all HBAs in a structured output, such as device paths and serial numbers. When handling multiple HBAs, iteration over directories is used, for instance, via a loop like for host in /sys/class/fc_host/host*; do echo $host; cat $host/port_name; done, which enumerates each host's WWNs; alternatively, /sys/class/fc_transport exposes remote port attributes for broader fabric discovery.

Vendor-Specific Tools

Vendor-specific tools provide proprietary command-line interfaces (CLIs) and utilities for discovering and managing World Wide Names (WWNs) in environments, often offering more detailed adapter-specific information than standard operating system commands. These tools are typically bundled with vendor management software and require the installation of corresponding host bus adapter (HBA) drivers. For Emulex (now part of ) HBAs, the OneCommand Manager application includes the hbacmd CLI, which enables querying of WWPNs and WWNNs. The ListHBAs command lists all detectable Emulex adapters, displaying their WWPN and WWNN for each port. Similarly, the HbaAttributes command, invoked as hbacmd HbaAttributes <WWPN | MAC>, retrieves detailed adapter attributes including the Node WWN (WWNN) and Port WWN (WWPN). The PortAttributes command, used as hbacmd PortAttributes <WWPN>, shows port-specific details such as the associated WWPN and WWNN for or FCoE functions. These commands operate on supported platforms like , Solaris, and Windows, providing output in a structured format for SAN administration tasks. QLogic (now part of Marvell) HBAs utilize the QConvergeConsole CLI (QCCLI) for WWN management and discovery. This tool allows administrators to query SAN components, including HBAs, to retrieve WWPN and WWNN values through commands like qaucli -pr fc -i <hba instance>, which displays port information such as Node WWN and WWN for connected adapters. Additionally, the older SANsurfer CLI (scli) under /opt/QLogic_Corporation/SANsurferCLI/ offers an interactive menu for HBA information, where selecting option 2 reveals WWPN details, and further submenu navigation displays the corresponding WWNN. The qaucli utility, part of QLogic's management suite, can also view port WWNs with commands like qaucli -pr <adapter>, aiding in zoning and fabric verification. These utilities support QLogic series like 2500, 2600, and 2700, focusing on CLI-based queries for adapter and fabric WWNs. Brocade (now part of ) switches employ the Fabric OS CLI for fabric-level WWN discovery, with the portshow command being central to viewing port-associated WWNs. Executed as portshow <port_number>, it outputs the port's own WWN (under "portWwn") and the WWNs of connected devices (under "portWwn of device(s) connected"), including support for NPIV virtual ports. For inter-switch links like EX_Ports, it displays additional WWNs such as the principal switch WWN and phantom domain WWNs. This command is essential for fabric connectivity, as it reveals login states and attached WWNs without requiring host access. Integration with operating systems, such as , requires loading vendor-specific drivers to enable these tools' access to HBA hardware. For Emulex adapters, the lpfc driver must be installed, as it provides the kernel interface for hbacmd to query WWNs; without it, tools report no adapters or limited information. This driver supports features like NVMe over Fabrics and is distributed via Broadcom's Linux driver kits, ensuring compatibility for WWN management in enterprise SANs.

Vendor Identifiers

Organizationally Unique Identifiers (OUIs)

The (OUI) is a 24-bit value assigned by the IEEE Registration Authority () to uniquely identify vendors, manufacturers, or organizations in the construction of globally unique identifiers, including World Wide Names (WWNs). This prefix ensures that devices from different vendors can be distinguished without collision in networked environments, such as storage area networks. The IEEE RA maintains a public registry of assigned OUIs to support standardization across various protocols. Vendors seeking to produce WWNs must apply to the IEEE for an OUI allocation, a process that involves submitting organizational details and agreeing to usage guidelines outlined in IEEE standards. Once assigned, the OUI enables the creation of unique identifiers by appending vendor-specific extensions, promoting in global deployments. This registration is essential for WWNs used in and related technologies, where the OUI guarantees worldwide uniqueness without reliance on local administration. In the standard 64-bit WWN format defined under the Network Address Authority (NAA) scheme, the OUI is positioned in bits 5 through 28, immediately following the NAA identifier in bits 1 through 4. This placement aligns with IEEE specifications for extended , allowing the OUI to serve as the core organizational component while leaving the remaining bits for vendor-defined serial numbers or port details. WWNs extend the principles of the EUI-48 format, which uses a 24-bit OUI followed by a 24-bit vendor extension for MAC addresses in local networks, adapting this structure for broader bus and port addressing in distributed systems like and . By incorporating the OUI in this manner, WWNs inherit the global uniqueness of EUI-48 while expanding to 64 bits to accommodate more complex addressing requirements in high-availability storage environments.

Common OUIs and Vendors

In Fibre Channel networks, certain Organizationally Unique Identifiers (OUIs) appear frequently in World Wide Names (WWNs), particularly those associated with host bus adapters (HBAs) and switches from leading vendors. These OUIs enable quick identification of device manufacturers during SAN troubleshooting, zoning, and inventory management. For instance, the OUI 00:00:00 is reserved by the IEEE for special purposes, such as addresses or testing, and should not appear in production WWNs. Another common example is 00:05:1e, assigned to (now part of ), often seen in switch port WWNs. Similarly, 00:00:c9 identifies Emulex HBAs (also under ), while 00:e0:8b denotes QLogic HBAs (acquired by Marvell). The following table lists representative OUIs commonly encountered in WWNs for Fibre Channel HBAs and switches, along with the associated vendor and typical products. This selection focuses on high-impact vendors in storage networking, drawn from the IEEE registry and vendor documentation. Note that due to acquisitions, some OUIs are maintained under parent companies.
OUIVendorTypical Products
00:00:00IEEE ReservedReserved (e.g., multicast, testing)
00:00:c9Emulex Corporation ()FC HBAs (e.g., LPe12000 series)
00:0a:33Emulex Corporation ()Legacy FC HBAs
00:10:9bEmulex Corporation ()FC adapters
00:e0:8bQLogic Corporation (Marvell)FC HBAs (e.g., QLE2560 series)
00:1b:32QLogic Corporation (Marvell)FC HBAs (e.g., QLE series)
00:24:ffQLogic Corporation (Marvell)FC HBAs
00:05:1eBrocade Communications ()FC switches (e.g., G620)
00:27:f8Brocade Communications ()FC switches (e.g., 6505)
00:10:86ATTO TechnologyFC HBAs (e.g., H6F0 series)
00:c0:ddQLogic Corporation (Marvell)FC switches
Over the past decade, there has been a notable shift in the storage networking industry from legacy vendors to consolidated modern providers such as , which acquired Emulex in 2015, QLogic in 2016, and in 2017. As of 2025, this consolidation has streamlined OUI usage, reducing fragmentation while maintaining for existing deployments. To verify an OUI's assignment and vendor, cross-reference it directly with the IEEE OUI registry, which provides the authoritative public list of allocations. This ensures accuracy, as OUIs are globally unique and updated periodically by the IEEE .

References

  1. https://www.techtarget.com/searchstorage/definition/World-Wide-Name-WWN
  2. https://datatracker.ietf.org/doc/html/rfc3980
  3. https://www.redbooks.ibm.com/abstracts/tips0202.html
  4. https://www.snia.org/education/online-dictionary/term/network-address-authority
  5. https://docs.broadcom.com/docs/12379617
  6. https://www.rfc-editor.org/rfc/rfc4044.txt
  7. https://standards.ieee.org/wp-content/uploads/import/documents/tutorials/eui.pdf
  8. https://www.computerweekly.com/answer/Fibre-Channel-SAN-zoning-Pros-and-cons-of-WWN-zoning-and-port-zoning
  9. https://www.ibm.com/support/pages/san-zoning-best-practices
  10. https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/6-5/vsphere-security-6-5/security-best-practices-and-scenarios/storage-security-best-practices/masking-and-zoning-san-resources.html
  11. https://www.oracle.com/technetwork/systems/articles/san-fundamentals-149861.pdf
  12. https://documentation.suse.com/sles/12-SP5/html/SLES-all/cha-multipath.html
  13. https://serverfault.com/questions/586462/san-zoning-advantages-and-disadvantages
  14. https://www.redbooks.ibm.com/redpapers/pdfs/redp5513.pdf
  15. https://www.cisco.com/c/en/us/td/docs/dcn/dcnm/1151/configuration/san/cisco-dcnm-san-configuration-guide-1151/inventory.html
  16. https://techdocs.broadcom.com/us/en/fibre-channel-networking/fabric-os/fabric-os-administration/9-1-x/Understanding-Fibre-Channel-Services-AG/v26919255/v26919214.html
  17. https://www.ibm.com/support/pages/storage-path-outage-due-duplicate-wwn-pureflex-system-and-lenovo-x86-servers
  18. https://techdocs.broadcom.com/us/en/fibre-channel-networking/fabric-os/fabric-os-administration/9-2-x/Perform-Advance-Configuration-Tasks-Admin1/v26748272/v26747499.html
  19. https://www.t10.org/ftp/t10/document.06/06-002r2.pdf
  20. https://www.sanog.org/resources/sanog8/sanog8-san-functional-overview-asimkhan.pdf
  21. https://powercampus.de/en/numbers-fc-world-wide-names-wwns/
  22. https://www.techtarget.com/searchstorage/definition/N_Port-ID-virtualization-NPIV
  23. https://techdocs.broadcom.com/us/en/fibre-channel-networking/fabric-os/fabric-os-administration/10-0-x/v26749369.html
  24. https://www.cisco.com/c/en/us/support/docs/storage-networking/mds-9000-series-multilayer-switches/200127-N-Port-Identifier-Virtualization-NPIV.html
  25. https://www.redbooks.ibm.com/redpapers/pdfs/redp4125.pdf
  26. https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/san_switching/421_n1_1/b_Cisco_n5k_nxos_sanswitching_config_guide_rel421_n1_1/Cisco_n5k_nxos_sanswitching_config_guide_rel421_n1_1_chapter14.html
  27. https://standards-support.ieee.org/hc/en-us/articles/4888705676564-Guidelines-for-Use-of-Extended-Unique-Identifier-EUI-Organizationally-Unique-Identifier-OUI-and-Company-ID-CID
  28. https://techdocs.broadcom.com/us/en/fibre-channel-networking/fabric-os/fabric-os-commands/9-2-x/Fabric-OS-Commands/wwn.html
  29. https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/command/reference/rel_4_2_1_N2_1/NX5000CommandReference/fibre-cmd-ref.html
  30. https://storage-admin.com/add-remove-colons-wwpn-lun-uuid/
  31. https://support.huawei.com/enterprise/en/doc/EDOC1100135772/46298a34/create-initiator-fc
  32. https://www.snia.org/sites/default/files/technical-work/smi-s/release/v140/SMI-Sv1.4r6_Host.book_.pdf
  33. https://support.hpe.com/hpesc/public/docDisplay?docId=sf000051178en_us&docLocale=en_US
  34. https://techdocs.broadcom.com/us/en/fibre-channel-networking/fabric-os/fabric-os-commands/9-2-x/Fabric-OS-Commands/portShow_922.html
  35. https://datatracker.ietf.org/doc/html/rfc3720
  36. https://www.t10.org/cgi-bin/ac.pl?t=d&f=doc_sas3r07.pdf
  37. https://www.broadcom.com/products/fibre-channel-networking/adapters-host-bus
  38. https://www.ibm.com/support/pages/system/files/inline-files/IBM_Storage_Systems_WWPN_Determination_Version_6.5.pdf
  39. https://docs.broadcom.com/docs/53-1004781
  40. https://www.redbooks.ibm.com/abstracts/tips0035.html
  41. https://techdocs.broadcom.com/us/en/fibre-channel-networking/fabric-os/fabric-os-administration/9-2-x/Understanding-Fibre-Channel-Services-AG.html
  42. https://www.juniper.net/documentation/us/en/software/junos/storage/topics/concept/fibre-channel-terminology.html
  43. https://www.enterprisestorageforum.com/networking/storage-basics-understanding-fibre-channel-zones/
  44. https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-manager/GUI-User-Guides/Storage-Mgmt/4-0/b_UCSM_GUI_Storage_Management_Guide_4_0/b_UCSM_GUI_Storage_Management_Guide_4_0_chapter_011.html
  45. https://datatracker.ietf.org/doc/html/rfc3821
  46. https://www.enterprisestorageforum.com/networking/1-2-4-8-10-the-evolution-of-fibre-channel/
  47. https://fibrechannel.org/fibre-channel-zoning-fundamentals-and-fundamental-questions/
  48. https://datatracker.ietf.org/doc/html/rfc3721
  49. https://www.snia.org/education/online-dictionary/term/sas_address
  50. https://www.cisco.com/c/dam/en/us/products/collateral/storage-networking/mds-9700-series-multilayer-directors/guide-c07-733622.pdf
  51. https://nvmexpress.org/wp-content/uploads/NVM-Express-Base-Specification-Revision-2.3-2025.08.01-Ratified.pdf
  52. https://docs.kernel.org/scsi/scsi_fc_transport.html
  53. https://access.redhat.com/solutions/55334
  54. https://www.mankier.com/8/lsscsi
  55. https://linux.die.net/man/8/sg_inq
  56. https://docs.broadcom.com/docs/12381582
  57. https://www.marvell.com/content/dam/marvell/en/drivers/release-2023-04-21/documentation/marvell-fibre-channel-adapters-qlogic-series-qconvergeconsole-cli-user-guide.pdf
  58. https://www.ibm.com/docs/en/tcs-service?topic=ufeqa-obtaining-wwnn-wwpn-values-qlogic-adapter
  59. https://www.veritas.com/support/en_US/article.100015890
  60. https://techdocs.broadcom.com/us/en/fibre-channel-networking/fabric-os/fabric-os-commands/9-1-x/Fabric-OS-Commands/portShow_911.html
  61. https://docs.broadcom.com/docs/12399036
  62. https://www.rfc-editor.org/rfc/rfc3980.html
  63. https://standards.ieee.org/regauth/oui/tutorials/EUI48.html
  64. https://standards.ieee.org/regauth/oui/tutorials/EUI64.html
  65. https://standards-oui.ieee.org/oui/oui.txt
  66. https://www.dell.com/support/kbdoc/en-us/000067530/what-is-an-organization-unique-identifier-o-u-i
  67. https://extreme-networks--uatq1.sandbox.my.site.com/ExtrArticleDetail?an=000086031
Add your contribution
Related Hubs
User Avatar
No comments yet.