Port 60767: Xsan Filesystem Access — Where Storage Clustering Happens

What This Port Does

Port 60767 carries Xsan Filesystem Access traffic. Xsan is Apple's storage area network (SAN) system—a way for multiple Mac computers to share storage resources over Fibre Channel networks as if they were local disks. When Xsan clients connect to shared storage, port 60767 (along with other ports in the dynamic range) handles that communication.¹

Why It's in the Ephemeral Range

Port 60767 shouldn't exist here. The port range 49152-65535 is reserved for ephemeral (temporary) ports—numbers the operating system assigns dynamically to outgoing client connections. They're meant to be temporary, to live for a moment, then disappear.²

Xsan breaks this rule deliberately. It's a client-side service that needs specific, stable port numbers to work reliably across network boundaries. Apple assigned port 60767 as a standard address, even though it technically belongs to the ephemeral range. The system works because the rule is practical, not absolute.³

How It Works

Xsan is a clustered file system built on Quantum's StorNext technology. Multiple Macs (and Windows/Linux systems via StorNext) can connect to the same shared storage simultaneously, reading and writing files without stepping on each other's work. Port 60767 is part of how Xsan clients negotiate access to that shared storage.¹

For Ethernet access to Xsan volumes, Apple uses standard protocols like AFP, SMB/CIFS, and NFS. But direct Fibre Channel communication—the fast, block-level access that makes Xsan useful for professional video and media work—uses the port range including 60767.⁴

Checking What's Using This Port

On macOS, see what's listening on port 60767:

# List processes using the port
lsof -i :60767

# Check if TCP is listening
netstat -an | grep 60767

On Linux or other systems:

# Using netstat
netstat -tulpn | grep 60767

# Using ss (modern systems)
ss -tulpn | grep 60767

If you see Xsan-related processes, your system is part of a storage cluster. If nothing appears, the port is simply unused.

Why Unassigned Ports Matter

Port 60767 teaches an important lesson: the ephemeral range exists for flexibility, but sometimes flexibility means breaking the rules responsibly. Most of the 16,000+ ports in the ephemeral range stay truly ephemeral, assigned and released by the operating system. But when a service genuinely needs stable port numbers and has nowhere else to go, the system accommodates it.

The larger truth is that port numbers are practical addresses, not philosophical boundaries. They work because enough people agree what each number means. Port 60767 works because Xsan clients and servers agreed on it, even though it lives in a range that shouldn't contain agreements at all.

Related Ports

• Port 63146 — Another Xsan port, frequently visible in Xsan system logs⁴
• Ports 49152-65535 — The full ephemeral range where Xsan clients communicate¹
• Fibre Channel traffic — Xsan primarily runs over dedicated Fibre Channel connections, bypassing traditional TCP/IP ports entirely