UDP (User Datagram Protocol) is a minimal message-oriented Transport Layer protocol (protocol is documented in IETF RFC 768).Īpplication examples that often use UDP: voice over IP (VoIP), streaming media and real-time multiplayer games. UDP on port 311 thinks that error checking and correction is not necessary or performed in the application, avoiding the overhead of such processing at the network interface level. UDP on port 311 provides an unreliable service and datagrams may arrive duplicated, out of order, or missing without notice. UDP port 311 would not have guaranteed communication as TCP. Guaranteed communication over TCP port 311 is the main difference between TCP and UDP. Only when a connection is set up user's data can be sent bi-directionally over the connection.Īttention! TCP guarantees delivery of data packets on port 311 in the same order in which they were sent. TCP is a connection-oriented protocol, it requires handshaking to set up end-to-end communications. TCP is one of the main protocols in TCP/IP networks. In macOS Monterey the Server.app interface for setting up and managing Xsan is gone.TCP port 311 uses the Transmission Control Protocol. Apple has produced an Xsan Management Guide (as of available on the Apple developer site). In this post I will walk through creating a new Xsan from scratch on macOS Monterey. Our test environment is made up of 2 Intel Mac Minis with ATTO Thunderlink fibre adapters connected to a fibre switch and one 12 drive RAID unit connected to the same switch. We have installed the ATTO driver and allowed it in System Preferences -> Security & Privacy -> General. The fibre switch is already zoned so that the Macs can see the storage. We also have a dedicated metadata network. Our Brocade Fibre Switch only supports 16 or 32 Gb/s SFPs, so we needed to upgrade our test RAID to also support 16Gb/s.Check the speeds that the fibre switch, client HBAs, and storage support.Each MDC (and client) needs a second ethernet port with static IP.We will install and configure dnsmasq on our MDC.We need to provide DNS for our metadata network.Our Xsan will have a metadata LUN, a dedicated journal LUN, and 2 user data LUNs.Both Minis have a secondary USB-C to ethernet adapter and a static IP on that port. To provide DNS services for the metadata network, you could use any number of solutions (a Raspberry Pi, a smart switch with that service, etc). For our solution we installed dnsmasq on our MDC. Running additional services on an MDC isn’t recommended, but works for our test system. On the Mac that will host your dns, copy/move these items, creating the folders as necessary.Copy src/dnsmasq, contrib/MacOSX-launchd/uk., and to your MDC.Open a Terminal window to the expanded folder (i.e.Expand the tar.gz file in your Downloads location.Download the current dnsmasq tar.gz from their site on a Mac that matches the architecture of your MDCs (Intel vs M1) and has Xcode or the Xcode Command-line tools installed.dnsmasq is available in Homebrew or MacPorts, but for our Xsan, I didn’t want to install all the extra that comes with a package manager. On both MDCs (and eventually any clients) add this server’s IP to the DNS servers list for the primary (non-metadata service) in System Preferences.Now start the dnsmasq process by bootstrapping the launchdaemon: sudo launchctl bootstrap system /Library/LaunchDaemons/uk.# localhost is used to configure the loopback interface The lines should be formatted as ip (tab) hostname, for example: #.At the bottom of the file add a line for each system.In a Terminal window run sudo nano /etc/hosts (or use your plain text editor of choice).Edit the /etc/hosts file to add both MDCs (and any fibre connected clients).We just need the most basic functionality. Assign the private hostnames to each of the systems with sudo scutil -set HostName ĭifferent storage vendors have different interfaces for creating LUNs on their storage.If you haven’t, assign the appropriate IPs to the metadata ethernet ports in System Preferences.Test your DNS entries with host and host.Make sure your other DNS server(s) are still listed and are below the MDC ip. Please see your vendors manual on the exact method for your storage. This section will discuss some strategies and then see how to label the LUNs for use in Xsan. Apple provides some discussion and guidance on drives, LUNs, and Storage Pools, in the Xsan Management Guide, which we won’t be discussing here. In this example we want to end up with a 2 drive, RAID 1 (mirror) LUN for metadata, a second 2 drive, RAID 1 LUN for the journal, and then two RAID 5 data LUNs.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |