HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
BladeSystem Virtual Connect
Showing results for 
Search instead for 
Did you mean: 

unknown initiator/target Virtual Connect (VC) Fibre Channel and SAN Switch

Trusted Contributor

unknown initiator/target Virtual Connect (VC) Fibre Channel and SAN Switch

Mohammed was looking to help a customer with a SAN question:




Dear Experts

            I have a query from my customer about the Virtual Connect (VC) Fibre Channel when connected to the SAN switch. As it appeared as unknown initiator/target as per the attachment screen shoot , both SAN Switch and VC FC latest update firmware Any advice for this query




Linar had looked at the info sent by Mohammed and replied:




VC runs NPIV, so it does the first FLOGI itself. That's what you see in Name Server with FCID of xxyy00 on a switch port. VC however doesn't run any FCP (read: SCSI) functions so it's neither an Initiator nor Target.


Later on when HBAs log in via VC they get their own addresses like xxyy01, xxyy02 and so on. These are FCP Initiators. But Virtual Connect is not, so what the customer observes is precisely what is expected in NPIV environment.




Any other comments for Mohammed?