Network port detail · TCP/UDP

3225

Fcip-port
Protocol(s)
TCP/UDP
Range
Registered (1024-49151)
Reference
RFC 3821

Summary

// if you see it open
RFC 3821 requires FCIP entities to implement cryptographically protected authentication, data integrity, and confidentiality features. Restrict connections to authorized FCIP peers.
// common applications
Connecting Fibre Channel storage area ne FCIP peer connections transporting Fibre Channel traffic over IP networks; port assignment alone does not confirm observed application traffic.
[ 01 ] — Context

About port 3225.

Updated  ·  Confidence: High  ·  2 sources  ·  How this page is checked

IANA assigns TCP port 3225 the service name fcip-port for FCIP. RFC 3821 defines FCIP as a mechanism for connecting Fibre Channel storage area network islands over IP networks. The evidence establishes the protocol and assignment, but does not establish whether a particular host uses the port or whether it should be publicly reachable.

RFC 3821 describes FCIP links as using at least one TCP connection, with multiple connections permitted. FCIP carries Fibre Channel frames between storage network segments; it is intended for configured peers that extend a Fibre Channel fabric across an IP network. A connection on this port is consistent with FCIP, but the port number alone does not confirm the application.

The RFC’s security model requires cryptographic peer authentication, data integrity, and confidentiality features. Because this protocol connects storage fabrics, allow access only between authorized FCIP peers and apply the RFC’s security mechanisms. The available evidence does not support claims about prevalence, typical devices, malware association, or a general public-internet access policy.

Service
IANA assigns fcip-port to TCP port 3225 for FCIP.
Purpose
FCIP carries Fibre Channel frames across IP networks to connect storage network islands.
Exposure
Unknown. The sources describe configured FCIP peers but do not establish a general intended public-internet audience.
Security
RFC 3821 requires cryptographic authentication, integrity, and confidentiality features; restrict connections to authorized FCIP peers.
IANA service
fcip-port [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv

Protocol

FCIP transports Fibre Channel frames across IP networks to connect Fibre Channel storage network islands

[Confirmed] — https://www.rfc-editor.org/rfc/rfc3821.txt
TCP connection structure
An FCIP link contains at least one TCP connection and may contain more [Confirmed] — https://www.rfc-editor.org/rfc/rfc3821.txt
Security requirements
FCIP entities must implement cryptographically protected authentication, data integrity, and confidentiality features [Confirmed] — https://www.rfc-editor.org/rfc/rfc3821.txt
// registry data

Service assignments.

2 entries
// IANA / nmap services registry
NameProtocolDescriptionOpen frequency
fcip-port TCP FCIP 0.00%
fcip-port UDP FCIP 0.00%
IANA name
fcip-port
Transport
TCP
Range
Registered (1024-49151)
Reference
RFC 3821

Service assignments from the IANA Service Name and Transport Protocol Port Number Registry, with open-frequency data from nmap-services.