The New QLogic (ANCR) Message Board

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : The New QLogic (ANCR)

QLGC 16.07

0.0%

Aug 24 5:00 PM EST

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: KJ. Moy who wrote (14737)	3/2/1998 11:46:00 AM
From: Craig Stevenson	Read Replies (1) of 29386

KJ, I found some additional information on Public/Private loops, straight from T11. Here is a link to a document called, "Fibre Channel Private Loop SCSI Direct Attach". It is in PDF format, so you will need Acrobat Reader to view it. ftp://ftp.dpt.com/t11/pub/fc/plda/plda_21.pdf I think the relevant portion to our discussion is this quote: "4 Private versus Public Port behavior When an NL_Port is operating in an Arbitrated Loop topology as defined by FC-AL and successfully completes a Fabric Login (FLOGI) is called a Public NL_Port. An NL_Port that does not attempt a Fabric Login is called a Private NL_Port. Public NL_Ports whose Fabric Login fails revert to Private NL_Port behavior." It appears as if a Private Loop is simply a loop that doesn't log in to the fabric, while a Public Loop is one that does. It doesn't seem terribly complex, at least on the surface. If Arcxel only supports private loops, perhaps that's why they need "Stealth Mode", to allow communication between loops. Craig

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next