sanman

Member
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About sanman

  • Rank
    Member
  1. Thanks for checking into that and the link.
  2. Thanks Kevin. In all cases though, do you have to have a switch in the network for it to be considered a fabric? That seems to be the case from what I've read.
  3. I've just started reading/learning about SANs and one question I now have is this: In a SAN, devices are identified by their WWN. In TCP/IP, devices are identified by a MAC/IP address combination. How does a TCP/IP host communicate with a server in a SAN, when that server doesn't speak IP?
  4. I'm a bit confused on the concept of what constitutes a fabric. The info I've read states that a fabric is one or more switches (it didn't say they had to be connected together). I've also read that a SAN can consist of multiple interconnected fabrics, or that you connect switches to create large SAN fabrics. So, my questions are as follows: Can a single switch be called/considered a fabric? Let's say you have a server with two HBAs, each HBA is connected to a switch (but those switches are not connected together). Would you say you have two fabrics, or a single fabric? If you then connected those switches together, what would it be called? Just trying to get a better understanding of what a fabric is. As you can tell, I'm just learning about SANs (but have a strong background in networking... Cisco routers /switches. The TCP/IP world). Thanks, Tom