SI
SI
discoversearch

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 : Son of SAN - Storage Networking Technologies

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Douglas Nordgren who wrote (1555)10/31/1999 10:06:00 AM
From: Wei Yu  Read Replies (1) of 4808
 
>>For extensibility beyond that, I believe Capellix' FC-SW (fabric) Blade will be required to interoperate with other fabric switches (the backplane will pass the loops to the fabric blade which in turn will link to a fabric switch). <<

Douglas, In fact, you do not need a Capellix' FC-SW Blade in order to pass the loop traffic to other fabric switches. You can directly connect a Capellix port with a FL-port of the fabric switch. It will work like a hub attach to the switch. I do not think the port-to-port latency is a issue here. The port-to-port latency in Capellix is just as good as, or maybe better than fabric switch. In addition, the port-to-port latency is measured in ns, and the completion time of a FCP command is measured in us(micro-second)or ms. Thus, the port-to-port latency will not play a major part of the overall system performance. On the wavelength, I think there are Cappellix Blades which support GBIC. You can put in long-wave GBIC.

If Cappellix came out 6-9 months earlier, it is a killer product. Now, it may be little late. Most of FC devices have added N-port support, and the cost of Fabric is dropping fast.
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext