HP Virtual Connect Fibre Channel Networking Scenarios Cookbook
155
If a port status is unlinked and no connectivity exists, one of the following causes may appear:
Not Linked/E-Key—Port is not linked due to an electronic keying error. For example, a mismatch in the type of
technology exists between the server and module ports.
Not Logged In—Port is not logged in to the remote device.
Incompatible—Port is populated with an SFP module that does not match the usage assigned to the port, such as
a Fibre Channel SFP connected to a port designated for Ethernet network traffic.
Note: A port that is not assigned to a specific function is assumed to be designated for Ethernet network traffic. An
FCoE-capable port that has an SFP-FC module connected that is not yet assigned to a fabric or network is designated
for a network, and the status is "Incompatible". When a fabric is created on that port, the status changes to "Linked".
Unsupported—Port is populated with an SFP module that is not supported. For example:
- An unsupported module is connected.
- A 1Gb or 10Gb Ethernet module is connected to a port that does not support that particular speed.
- An LRM module is connected to a port that is not LRM-capable.
- An FC module is connected to a port that is not FC-capable.
Administratively Disabled—Port has been disabled by an administrative action, such as setting the uplink port
speed to ‘disabled.’
Unpopulated—Port does not have an SFP module connected.
Unrecognized—SFP module connected to the port cannot be identified.
Failed Validation—SFP module connected to the port failed HPID validation.
Smart Link—Smart Link feature is enabled.
Not Linked/Loop Protected—VCM is intercepting BPDU packets on the server downlink ports and has disabled
the server downlink port to prevent a loop condition.
Linked/Uncertified—Port is linked to another port, but the connected SFP module is not certified by HP to be
fully compatible. In this case, the SFP module might not work properly. Use certified modules to ensure server
traffic.