STRATUS-CS-FT server: Core (B1, C1)
These cabling instructions apply to GV STRATUS Express server and GV STRATUS Core server, specified as follows:
- Grass Valley FT
server with one or more roles from the following list only:
- GV STRATUS Ingest Services (Required)
- GV STRATUS Control Panel Service (Required)
- GV STRATUS Common Services (Required)
- License Manager (Required)
- GV STRATUS Data Mover Engine (Required)
- GV STRATUS Proxy Express Server (Required on Express server)
- GV STRATUS Control Panel (Required)
- GV STRATUS Core Services (Required)
- GV STRATUS Database (Required)
- GV STRATUS Summit MDI (Required)
- GV STRATUS BlackPearl MDI (Optional)
- GV STRATUS Common RESTful Archive MDI (Optional)
- GV STRATUS Diva MDI (Optional)
- GV STRATUS FlashNet MDI (Optional)
- GV STRATUS Masstech MDI (Optional)
- GV STRATUS Generic FTP MDI (Optional)
- GV STRATUS Proxy Streaming Service (Optional)
- GV STRATUS Rules Engine (Required. Must be assigned to Express/Core server or to dedicated Workflow Server)
- GV STRATUS Scheduled Transfer Engine (Optional)
- GV STRATUS Scheduled Ingest Engine (Not used in this GV STRATUS release)
- GV STRATUS Scheduled Ingest Manager (Not used in this GV STRATUS release)
- GV STRATUS SocialMedia Engine (Optional)
- GV STRATUS ExternalMedia Engine (Optional)
- GV STRATUS Traffic Gateway (Optional)
- GV STRATUS Topic Service Bus (Not used in this GV STRATUS release)
- GV STRATUS Web Apps (Required. Must be assigned to Express/Core server to display Statistics panel via Dashboard)
- GV STRATUS Web Client (Optional)
- GV STRATUS Workflow Engine (Required. Must be assigned to Express/Core server or to dedicated Workflow Server)
- GV STRATUS Xcode Control Engine (Required. Must be assigned to Express/Core server or to dedicated Workflow Server)
- GV Log Manager (Required)
- GV Log Viewer (Required)
- GV STRATUS Rundown Server Components (Optional)
- GV STRATUS Application (Use for test purposes only)
- If optionally used as a Render Engine, these additional roles:
- GV STRATUS Render Engine
Note: Network ports on CPU/IO module 0 and on CPU/IO 1 both connect to the
same network. For example, both control ports connect to the same control
network. Do not attempt to connect to different networks.