Signiant Support

Media Shuttle Relay Server FAQ Print


Use this FAQ to learn about the new Media Shuttle feature: Cloud Managed Relays.

What is the primary benefit of this release?
How do I know if this release applies to me (i.e., how do I know if I'm using cloud-managed Media Shuttle)?
What are the primary benefits of using a relay?
What is the most common scenario for using a relay?
What is the most common deployment of a relay?
From an Internet connected client using the above deployment, what does the network traffic look like?
I'd like to try this relay feature. How does Signiant recommend that I try it out?
What do I need to do to enable relays?
I currently have an external address specified. Can I use relays? Do I need to use the external address value?
Can I force my outbound traffic to use relays for my portals that are using object-based cloud storage?
Does this mean that every portal assigned to that storage server must use those relays?
How many relays can I assign to a storage server?
Do all the relays need to be running the same operating system? Agent version, etc?
Can I traverse several relays in a row? For example client → relayA → relayB → relayC → StorageServerA.
How does load balancing work?
If I've assigned a Media Shuttle storage server as a relay and it is offline, is it removed from the load balancing relay group?
If I've assigned a Signiant Agent as a relay and it is offline is it removed from the load balanced relay group?
What is the most scalable and fault tolerant configuration that I can create using Media Shuttle?
Are there any downsides to using a relay?
Is this feature compatible with the Use Multiple Ports option?
Is this feature compatible with the External IP Address option for a storage server?
Media Shuttle is working fine for me right now. Do I need to implement this feature?  

Q: What is the primary benefit of this release?
A: If you are using cloud-managed Media Shuttle you’ll be able to dictate the network path taken to route your Media Shuttle file transfers.

Q: How do I know if this release applies to me (i.e., how do I know if I’m using cloud-managed Media Shuttle)?
A: If you are using manage.mediashuttle.com to manage portals, this release applies to you. If you are managing your portals by logging on to a Signiant Manager you can already use relays to dictate the network path taken to route your Media Shuttle file transfers.

Q: What are the primary benefits of using a relay?
A: There are two primary benefits to using a relay:
  1. Simpler firewall configuration. Turning on relays ensures that only a single port is used for file transfer traffic. (This is already done by default without this feature being enabled).
  2. Control over file transfer traffic routing. Turning on relays allows you to control the network path taken to route your Media Shuttle file transfers.
Relays are often used (and required) by customers who want to maintain MPAA certification for their facilities.

Q: What is the most common scenario for using a relay?
A: Control the network path taken by remote personnel (i.e., Internet connected).

Q: What is the most common deployment of a relay?
A: Typically, customers deploy one or more relays in their DMZ and allow Signiant traffic originating from these servers to reach their internal networks. One or more Media Shuttle storage servers are deployed on the internal network.
Client → DMZ → Relay(s) → Internal Network → Storage Server(s)

Q: From an Internet connected client using the above deployment, what does the network traffic look like?
A: The network traffic is:
Client (UDP 49221) → DMZ → Relay(s) → UDP 49221 → Internet Network → Storage Server
Client (TCP 49221) → DMZ → Relay(s) → TCP 49221 → Internet Network → Storage Server
Client (TCP 80) → DMZ → Relay(s) → {Encapsulate HTTP into TCP 49221} → Internet Network → Storage Server

Q. I’d like to try this relay feature. How does Signiant recommend that I try it out?
A: We recommend that you install a new storage server in your DMZ and then do the following:
  1. Enable the relay on your storage server (or existing Signiant Agent).
  2. Configure Media Shuttle to route traffic through that storage server (or existing Signiant Agent).

Q: What do I need to do to enable relays?
A: Do the following to enable relays:
  1. Manually enable your relays services. For storages servers read How to make your storage server run as a relay. For Signiant agents read Relays in Chapter 3 in the Manager User’s Guide.
  2. Log into manage.mediashuttle.com and on the Storage page highlight the storage, click the options button and select Advanced. Enable Relays and enter up to four relays in a comma-separated list using the hostname or IP address.

     

Q: I currently have an external address specified. Can I use relays? Do I need to use the external address value?
A: The external address value was used to tell the Media Shuttle cloud which IP address to connect to for cloud connector calls (inbound 443) AND this value was also used as the relay (i.e., network path for file transfers). With version 2.0 of the Media Shuttle storage server, the inbound 443 call is no longer needed. You can simply move the value that was in the External Address field to the Relays field.

Q: Can I force my outbound traffic to use relays for my portals that are using object-based cloud storage?
A: Yes. Log into manage.mediashuttle.com and on the Storage page highlight the storage, click the options button and select Advanced. Enable Relays and enter up to four relays in a comma-separated list using the hostname or IP address.

Q: Does this mean that every portal assigned to that storage server must use those relays?
A: Yes.

Q: How many relays can I assign to a storage server?
A: You can assign up to four relays.

Q: Do all the relays need to be running the same operating system? Agent version etc?
A: No.

Q: Can I traverse several relays in a row? For example: client → relayA → relayB → relayC → StorageServerA.
A: Yes. However, you cannot specify more than the first relay hop in the relays field. The next hop needs to have a relay to the next target. In the above example:
  • relayA needs a rule that indicates the relay for StorageServerA is relayB.
  • relayB needs a rule that indicates the relay for StorageServerA is relayC.
  • relayC needs a rule that indicates the relay for StorageServerA is IP address of StorageServerA.
Q: How does load balancing work?
A: The client (i.e., web browser plug-in or Signiant App) attempts to connect to the target Media Shuttle storage servers simultaneously. The client connects to the first successful responding relay. The storage server list is randomized by the cloud services.

Q: If I’ve assigned a Media Shuttle storage server as a relay and it is offline, is it removed from the load balanced relay group?
A: No

Q: If I’ve assigned a Signiant Agent as a relay and it is offline is it removed from the load balanced relay group?
A: No

Q: What is the most scalable and fault tolerant configuration that I can create using Media Shuttle?
A: You can create a configuration with load-balanced relays and load-balanced storage servers in front of your portal’s storage.

Q: Are there any downsides to using a relay?
A: Yes, a relay effectively limits your maximum throughput to approximately 400-500Mbits/sec (regardless of your link’s capacity).

Q: Is this feature compatible with the Use Multiple ports option?
A: No. If you configure your storage server to use relay(s) the Use Multiple ports option is ignored.

Q: Is this feature compatible with the External IP address option for a storage server?
A: No. If you configure your storage server to use relay(s), the External IP address option is ignored.

Q: Media Shuttle is working fine for me right now. Do I need to implement this feature?
A: No. This feature is completely optional and only recommended for customers with advanced networking requirements.