Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
block:server_rack [2015/04/07 00:30]
rashy
block:server_rack [2018/07/04 00:37] (current)
lperkins2 [Server Rack] Update
Line 3: Line 3:
 {{:​blocks:​rack.png?​nolink&​128|}} {{:​blocks:​rack.png?​nolink&​128|}}
  
-The server rack houses up to four [[item:​server|Servers]]. Servers are basically computer cases in item format. Their main advantage is that they can allow for multiple ​CPUs, allowing more components to be controlled than via a normal computer. ​ +The server rack houses up to four [[item:​server|Servers]]. Servers are basically computer cases in item format. Their main advantage is that they can allow for multiple ​[[item:​component_bus|Component Buses]] ​allowing more components to be controlled than via a normal computer.
  
-The server rack also acts like a Power Distributor and Switch in one block, including the built-in servers. Each server slot can be configured to connect to one side directly, though, so the server in the slot can be used to control external block components, such as the Redstone I/O block.  ​+The server rack also acts like a Power Distributor and Switch in one block, including the built-in servers. Each server slot can be configured to connect to one side directly, though, so the server in the slot can be used to control external block components, such as the [[block:​redstone_io|Redstone I/O]] block.  ​
  
-The range in which Remote ​Terminals bound to servers in the rack can be used is configured in the server ​rack's GUI and applies ​to all servers in it.+Server Racks can also house a [[item:​terminal_server|Terminal Server]], ​which allows a [[item:​terminal|Remote ​Terminal]] to connect ​to the server ​rack wirelessly. ​ The Terminal Server must be attached to the same side of the case as the server ​it controls, ​and is roughly equivalent ​to a tier 2 screen and keyboard. ​ It allows up to 4 Remote Terminals to connect at a time.
  
-The Internal/​External switch button will make the internal switch either relay messages ​only to the servers in the rack (Internal) or work like a normal switch (External). For example, let's say there are four servers in the server rack, servers A, B, C and D. Servers ​A, B and C are connected to the left, right and back faces of the server, respectively,​ D is not connected to any face +The Server Rack GUI is composed of 3 sections. ​ On the left are 4 slots for components, ​the only valid components ​are Servers ​and Terminal ​Servers.
  
-In **External** mode, if a message arrives on the left faceserver A gets that message because it is in the same network anyway. The message is relayed ​to all other faces of the rack (if it didn't hop too often already), and therefore servers B and C will also receive ​the messageServer D will not receive ​the messageIf server ​A sends message, the same logic applies. If server ​D sends message, no-one will get it, because it isn't connected.  ​+In the middle are 5 vertical linescorresponding ​to each side of the rack except ​the front A key for which line is which is present on the right When a server ​is inserted into slot on the lefta '​primary'​ node is added to each vertical line.  Clicking on one of these nodes connects ​the Server to the side of the case controlled by that line If the server ​has [[item:​network_card|Network Card]] in it, a smaller node is created under the primary node for each network card in the server.  ​Like the primary node, clicking on one of the smaller nodes connects the network card to a side of the case.
  
-In **Internal** mode, if a message arrives ​on the left face, server A gets that message because it is in the same network anywayThe message is relayed to all servers ​in the rack, so servers B, C and D get the messageIt is *not* forwarded ​to the other faces of the rackhoweverIf server A sends a message, it is sent to all other servers ​in the server rackand also via the left face of the rack - it is *not* forwarded via the other faces of the rack. If server D sends a messageit is sent to all other servers in the rack.   +The single button ​on the Server Rack GUI does not appear to change anything beyond drawing a line between ​the boxes at the bottom of the vertical lines. 
-The main purpose of the internal mode is to allow more compact message filtering between networks, using two or more servers in a server rack to filter and forward ​the messages ​as desired + 
 +Servers inside the case can be accessed by right clicking on them in the front of the Server Rack This will open their component view, similar ​to right clicking a normal computer case.  To open the Rack GUI again, right click on the side of the Server Rackor above or below any installed Servers. 
 + 
 +Wired network messages can only be sent between Servers with Network Cards. ​ The Network Cards must be configured ​in the Server Rack GUI to share a side.  To send or receive messages on an external network, the Network Card must be connected to the side of the case with the external Computer or [[block:​switch|Relay]] If you want Server-Server internal networkingwithout cross-talk outside ​the case, set the Network Cards to the case's unused side (as there are 5 valid sides, and a maximum of 4 servers, there is always an unused side).
  
 The Server rack is crafted using the following recipe: ​ The Server rack is crafted using the following recipe: ​