How to check WWN and Multipathing on Windows Server

How to check WWN and Multipathing on Windows Server

Introduction

World Wide Name (WWN) and multipathing are crucial elements in storage management for Windows Servers. This guide will walk you through the process of checking WWN and multipathing across different Windows Server versions.

Windows Server 2012-2022

Checking World Wide Names (WWNs) and iSCSI IQNs

Use the following PowerShell command:

Get-InitiatorPort

Checking ISCSI Connections

Execute this PowerShell command:

Get-IscsiTarget

Checking MPIO Connections

For MPIO (Multipath I/O) connections to SAN, use:

mpclaim -s -d

Checking Multipath for Specific Disks

List all disks:

list disk

Check multipath for a specific disk (e.g., Disk 0):

mpclaim -s -d 0

Suggested Read: Top 50 PowerShell Commands for Daily Use

Windows Server 2008

Use the Storage Explorer tool to view:

• FC switches in your storage fabric
• Details about switch port connections
• Information about other servers connected to the storage fabric
• HBA and LUN information

Windows Server 2003/2000

Using FCINFO (Fibre Channel Information Tool)

Run the “fcinfo” command in Command Prompt. It will show up HBA connected to the server with WWN

1. Download FCINFO from Microsoft Download Center
2. Run the following command in the Command Prompt:

fcinfo

This will display HBA information, including WWN.

Model-Based Utilities

Some vendor-specific utilities include:

1. HBAnyware utility
2. SANsurfer utility
3. Hitachi Storage Commands:

dlnkmgr view -path    # Check multipath output
dlnkmgr view -drv     # Check current settings
dlnkmgr set -lb on -lbtype rr    # Set load balancing
dlnkmgr set -pchk on -intvl 10   # Set path Health Checking
dlknmgr set -afb on    # Set Automatic Failback

Conclusion

Understanding how to check WWN and multipathing is essential for efficient storage management in Windows Server environments. By following this guide, you can effectively manage these aspects across various Windows Server versions and utilize vendor-specific tools when necessary.

Also Check: Unable to join machines to the domain. Error Message “The Specified User already exists”

• About
• Latest Posts

Ravi Chopra

With 19 years of hands-on experience in the IT industry, I’m passionate about sharing the knowledge I’ve gained across a wide range of technologies. Specializing in Active Directory, Azure, VMware, Windows, and Linux, I am dedicated to empowering IT professionals and enthusiasts with practical insights and solutions.

Whether you’re looking for troubleshooting tips, deep dives into systems architecture, or the latest in cloud computing, I’m here to help you navigate the evolving tech landscape. Let’s connect, learn, and grow together!

📧 ravi.chopra1709@gmail.com

Latest posts by Ravi Chopra (see all)

• Top Azure Interview Questions with Expert Answers (Scenario Based) - 22 December 2024
• Entra ID (Azure Active Directory): Migration and Integration Guide - 20 December 2024
• Active Directory Federation Services (ADFS): Implementation Guide - 16 December 2024