Silicon Investor (SI) -- The First Internet Community

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) -- Ignore unavailable to you. Want to Upgrade?

To: Pigboy who wrote (14714)	2/26/1998 5:25:00 PM
From: KJ. Moy	Read Replies (2) \| Respond to of 29386

More on private/public loop. From a reliable source, Arcxel only has private loop support and Ancor has public loop support. Since I cannot find any support documents to explain these terminologies, following explanation is my educated guesses. All comments are welcome. When number of devices are lower than 127, it's easy. You have one private FC/AL loop. When you have enough devices to occupy 3 loops and also you have large SMP servers which needs to be on switch ports by themselves. The communication paths can then go between any SMP to any loop devices, one node pair at a time of course. This scenario in my opinion(guess) constitutes a public loop support. Most OEM vendors would require this. On the other hand, if communication pairs can only be between devices from two seperate FC/AL loop via a 'switch/hub', then my opionion(guess) at this point for this kind of scenario is private loop support. It means it does not support N_port fabric switching with another loop device. Roy Sardina, can you help to explain this? Thanks. KJ