8/2/2023 0 Comments Apple xsan ports![]() ![]() The IP address of our metadata controllers metadata IP is 10.0.0.5. Through this entire article we are going to assume that the IP address of our metadata controllers production IP is 192.168.50.5. Once we step through this using Server Admin we will explain the same thing using the configuration files which should help users of old versions of Mac OS X Server or of Mac OS X Workstation. This example assumes that you are using Tiger Server for your metadata controller. Here is an example of how to do this using ipfw. A fix to get around this issue for these systems is to block metadata traffic on the production network interface. ![]() This doesn’t always work, and selecting a network controller to use is not an available option with Xsan clients and older versions of the Xsan software. This can be done by:Ĭlick on the Xsan listed under SAN ComponentsĬhoose the network controller you would like to connect using One way to fix this for metadata controllers is to choose the network adapter that you would like to use on the metadata network in Server Admin. We see this in many configurations and it can cause dropped packets, unmountable volumes and other intermittent issues. Namely that Xsan will attempt to use the corporate network for connectivity with clients. For systems that are obtaining directory information or need to be wired into the corporate network of many organizations this can cause issues. Xsan requires a dedicated ethernet network in the supported architecture by Apple. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |