Documents
Resources
Learning Center
Upload
Plans & pricing Sign in
Sign Out

ISIS - Pinnacle

VIEWS: 14 PAGES: 10

									                                                         Avid Port Usage Guide                                         - SEP 24 2009

Location                         Port                    Purpose

  ISIS                       Last Updated on: SEP 03, 2007 @09:43 by David Shephard

                                IP Port       UDP/TCP    Description
                                       3000     UDP      ISIS uServer Communication (well known port)
                              3001 -> 3400      UDP      ISIS uServers (ISBs & ISS, IXS)
                                       5001     UDP      ISIS uServers - SD to uServer for failover control
                                       5004     UDP      ISIS uServers - admin agent and related to uServer (localhost normally)
                                       5015     TCP      ISS/IXS agents and uServer agents - Admin Login via https

  Up to Version 1.3              4000-4399      UDP      ISIS Windows Client to ISB Data Transfer, ISB msg and System Director msg traffic (range migration)
                                                         ISIS Windows Client to ISB Data Transfer, ISB msg and System Director msg traffic (range
  Version 1.4 Onward           4200-4599       UDP       migration)

                                      5000      UDP      ISIS System Director - SD to SD failover control
                                      5003      UDP      ISIS System Director - Client, uServer and SD to SD control (well known port).
                                      5004      UDP      ISIS System Director - admin server and related to SD (localhost normally)
                                      5005      UDP      ISIS System Director - ISS/IXS status reporting to SD
                                      5015      TCP      ISIS System Director Admin Login via https

                                5016-5415       UDP      ISIS MAC Client to ISB Data Transfer, ISB msg and System Director msg traffic (range migration). Used for initial
                                                         prototype initiative and expects to migrate to same ports as NT client

                                                         Note - The port numbers for data transfer between client and ISB as well as those for incoming message traffic from
                                                         the index server or ISB's are all chosen from the range 4000-4399 (4200-4599 from V1.4 onward) on a dynamic
                                                         basis. That is, not all 400 ports are in use at any time, but the ports in use will vary over time over this entire range.


                                                         Note - With v2.0 ISIS onwards, the System Director will require use of TCP / UDP port 88 for Kerberos and TCP port
                                                         389 for LDAP when configured to use LDAP external ISIS user authentication in a Windows Active Directory
                                                         environment. Please see the "Windows AD and 3rd Party" Tab for further information on connections to Active
                                                         Directory.
                                                         See KB article to cover this:
                                                         http://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=289671




ISIS                                                                   KnowledgeBase document ID:
ff408ed4-8a9f-47ad-9455-a11edcd48f53.xls          http://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=243397                                                 Page 1 of 12
                                                          Note -The reason for port number changes in ISIS 1.4 refers to a conflict between Interplay requirements and ISIS.
                                                          The Interplay AIF Lookup Service, the LUS (Jini/Apache River) uses port 4160 for its discovery mechanism

                                                          Prior to version 1.4 the ISIS client cycled through ports 4000 - 4400 by default even though it has only a handful of
                                                          these ports open at once, it pokes holes in the firewall for all of them at boot time. Since 4160 is required for Jini then
                                                          the ISIS team had to make a decision to move the ISIS ports to 4200 - 4599 to avoid any conflict.

                     Source: Avid Unity ISIS Version 1.4 ReadMe • 0130-07876-01 Rev.A • December 2007
                             Avid Unity ISIS Administration Guide • 0130-07874-01 • September 2007




ISIS                                                                    KnowledgeBase document ID:
ff408ed4-8a9f-47ad-9455-a11edcd48f53.xls           http://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=243397                                                 Page 2 of 12
                                                       Avid Interplay Port Usage Guide
                                                                                   Version 24 SEP 2009

                            PRIMARY SOURCE: SEE APPENDIX C of document Avid® Interplay™ Software Installation and Configuration Guide Interplay v1.6
                                                  at http://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=263077
  This document lists networks ports used by Interplay. It does not include ports used by shared storage (Isis, MediaNet or Lanshare - documented elsewhere)


  Component/Location                      Port         Protocol Purpose
  Access                                   8321            UDP       Server Browser
                                            80             TCP       server communication
                                                                     Access can also be a Media Indexer client (update media status, Resync, ), Media Services Client (status tool plugin and
                                                                     submit jobs to archive and Transcode) and Transfer Engine client (status tool plugin, initiate WG2WG transfers) - see
                                                                     appropriate sections below.E6

  Active Directory                          135            TCP       RPC for Active Directory / Windows Domain Authentication
                                                                     SEE 3rd Party sheet for extended explanation

  Archive Provider                         1433            TCP       #Microsoft-SQL-Server (ms-sql-s)
                                           1433            UDP       #Microsoft-SQL-Server (ms-sql-s)
                                           1434            TCP       #Microsoft-SQL-Monitor (ms-sql-m)
                                           1434            UDP       #Microsoft-SQL-Monitor (ms-sql-m)
                                           8192            TCP       #FlashNetBackupClient (sdss)

  Assist                                                             Assist uses Access ports for Interplay engine communication, It is also a Media Idexer client. Please see appropriate
                                                                     sections for port usage

  Cluster Service                           135            TCP       RPC ; also used by Distributed Link Tracking Server - Service Name TrkSvr and Distributed Transaction Coordinator -
                                                                     Service Name MSDTC)
                                         Random            TCP       Randomly allocated high TCP ports; also used by Distributed Link Tracking Server - Service Name TrkSvr and Distributed
                                                                     Transaction Coordinator - Service Name MSDTC)
                                           3343            UDP       Cluster Services (service name: ClusSvc)

  DNS                                       53          UDP/TCP      DNS Client

  iNews                                      1            TCP        iNEWS Inter-system Messaging
                                             21         TCP (FTP)    FTP into iNEWS database: Teleprompters, Newscutter newsroom system tool, Data Receiver
                                             22        TCP or UDP    ssh
                                             25        TCP or UDP    sendmail
                                             67           UDP        used by PCU's to obtain an IP address via bootp
                                             80           TCP        http Web Access, for read-only database access
                                            513        TCP or UDP    rlogin
                                            600           TCP        FTP into Linux partition OBSOLETE in iNEWS 2.5 and later - see port 49152.
                                            698        TCP or UDP    may be required for Web Access through cgi-bin
                                            699           TCP        used by dbvisit (maintenance program) for on-line dbvisits – connection between iNEWS Servers.


Interplay Tcp port alloc                                                          KnowledgeBase document ID:
ff408ed4-8a9f-47ad-9455-a11edcd48f53.xls                     http://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=243397                                                   Page 3 of 11
                                               1019            TCP        server listens for client connections: iNEWS Workstation, Web Client, iNEWS COM, Data Receiver, iNEWS Instinct

                                               1020            TCP         Network dbdump / dbrestore between iNEWS Servers
                                              1020 †           UDP         Server updates/notifications sent to client, specified by client. Note each client running on a machine must bind to a
                                                                           unique socket. So if a user intends to run N sessions of iNEWS on the same machine, then ports 1020 through 1020 + (N-
                                                                           1) must be opened in the firewall. (TCP and UDP)
                                               1020 †         TCP          Search results sent to client from server, specified by client. Note each client running on a machine must bind to a unique
                                                                           socket. So if a user intends to run N sessions of iNEWS on the same machine, then ports 1020 through 1020 + (N-1)
                                                                           must be opened
             † These are the only ports on the iNEWS client. All other ports are on the iNEWS Server.
                                                 1022         TCP          iNEWS bioserver communication. Each bioserver is connected to every other bioserver. On an ABC system the A
                                                                           bioserver has a connection to both the B and C bioservers, The B bioserver is connected to the A and C bioservers. The
                                                                           C bioserver is connected
                                                 1023          TCP         used by connect and reconnect commands during startup
                                                 5901       TCP/SCTP first remote access port for VNC to Linux UI, may have more than one VNC session configured (5902, 5903, etc) I don’t
                                                                           think this is an officially supported configuration. These are not required to run iNEWS.
                                                 6100         TCP          FTS indexing (configurable)
                                                 6101         TCP          FTS searching (configurable)
                                                 6825         TCP          monitor, for ControlAir
                                                 6826         TCP          monitor for MOS
                                                 6827         TCP          Monitor for iNEWS Command
                                                49152         TCP          telnet OBSOLETE in iNEWS 2.5 and later - see port 49153.
                                                49152       TCP (FTP) FTP into Linux Partition.
                                                49153          TCP         Telnet


  Instinct                                                                Instinct uses Access ports for Interplay engine communication. It is also a Media Idexer client. Instinct E3is also an iNews
                                                                          Client Please see appropriate sections for port usage.

  Interplay Engine                             8321            UDP        Server Browser
                                                80             TCP        client communication

  Interplay Framework / Media Indexer                                     ports are dynamic and services register themselves with firewall to use any port
                                                161            UDP        SNMP
                                                162            UDP        SNMP Traps
                                            dynamic (0 -                  Codebase http server
                                               1024)
                                              dynamic                     Jini™ ERI ServerConnectionManager.
                                            dynamic (0 -                  Jini™ ERI ConnectionManager.
                                               1024)
                                             dynamic -       TCP/ UDP     TCP/UDP communications/notifications/http servers/snmp
                                            above 1024
                                               4160           TCP        Jini Discovery
                                               4160        UDP Multicast Jini Discovery


  LDAP                                          389             TCP
                                                636                       if SSL is enabled


Interplay Tcp port alloc                                                               KnowledgeBase document ID:
ff408ed4-8a9f-47ad-9455-a11edcd48f53.xls                          http://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=243397                                                     Page 4 of 11
  Media Services Engine                  8080          TCP      listen for editor clients (SOAP)
                                         1099          TCP      listen; RMI protocol for providers and Status/Admin tool
                                      42000-42060      TCP      if 1099 not available:

  Media Services Providers / Status        1099        TCP      outbound; RMI protocol for providers and Status/Admin tool
  Tool
                                      42000-42060      TCP      if 1099 not available:

  Newscutter                                21                  Required for NRCS tool
                                           8080        TCP      outbound; Media Services connection to Media Services Engine (SOAP)
                                                                Newscutter uses Access ports for Engine communication. It also runs the Interplay Framework and a local Media
                                                                E3Indexer - see appropriate sections for port usage

  ProEncode Client                         8080       TCP/IP    SOAP Connection to Media Services (TCP, outbound) - run on editor systems (Newscutter)

  Transfer Cache                         1099          TCP      listen; RMI protocol for providers and Status/Admin tool
                                      42000-42060      TCP      if 1099 not available:
                                         6539          TCP      outbound for Transfer Engine status

  Transfer Engine                          6532       TCP/IP    Media Connectivity tool (defined in system32\drivers\etc\services com.avid.mct) The TM Server listens on this port for
                                                                requestes from other TM Servers (eg: initiating a workgroup transfer.).
                                           6535       TCP/IP    Playback protocol (defined in system32\drivers\etc\services com.avid.pbp) This is the default port used by TM Sever for
                                                                connecting to Playback Servers (Airspace etc.). This is configurable for some playback servers.
                                           6539       TCP/IP    Transfer Engine (defined in system32\drivers\etc\services com.avid.pbp com.avid.xmgr) The TM Server listens on this port
                                                                for incoming requests from the TM Client.

  Interplay Delivery Service             33321                  The hostname and port for the Interplay Delivery Receiver service. You must enter the
                                                                name of the system where the Interplay Delivery Receiver service is installed before you
                                                                can receive transfers from the Delivery service. By default the port is 33321. For more
                                                                information, see the Avid Interplay Media Services Setup and User’s Guide.
                                                                >>>Source InterplayAdminGuide_V2_0 Page 147/290
  Interplay Streaming Server          TCP Port 554              Darwin Streaming Server
                                         (RTSP)                 http://lists.netfilter.org/pipermail/netfilter/2004-July/054648.html
                                        UDP Port                TCP/UDP Ports 554 & 7070 (RTSP) and UDP ports 6790:6999 (RTP) - the way I believe it to work is that the stream is
                                       6970 - 6999              asked for and controlled using the TCP port then the video is streamed over the UDP port.
                                      (can be up to
                                          9999)                 http://www.geeklan.co.uk/?p=14
                                                                Darwin Streaming Server Port Usage: As Darwin SS uses the RTSP protocol to stream (unless you are streaming via port
                                                                80) you must have the following ports open on your firewall 554, 7070, 8000, 8001 then anything starting from 6970 & up
                                                                depending on how many clients you want to support




Interplay Tcp port alloc                                                     KnowledgeBase document ID:
ff408ed4-8a9f-47ad-9455-a11edcd48f53.xls                http://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=243397                                                Page 5 of 11
                                                    Avid Port Usage Guide                                          - 6/13/2005

Location                             Port           Purpose
  File Manager                        1032          Used for licensing
                                      1403          Billing software
                                      5000          For failover configurations
                                      6014

  LANshare                              53          Allows Domain Name Services to connect on a LanServer
                                    137 - 139       Allows CIFs authentication on a LanServer
                                       445          Allows CIFs authentication on a LanServer
                                      6010          PortServer
                                      6012          PortServer with a load balancing switch (highly unlikely config, but included as a safeguard)
                                      6014          License server

  Media Manager                        80
                                      8080

  Media Manager Select                  80
                                       137          Required by some routers - netbios name service
                                       139          Required by some routers - netbios session service
                                       445          Required by some routers - Microsoft- ds
                                      1032          Used for licensing
                                      6010
                                      6012
                                      6014
                                      8080

  Transfer Manager                    6532          Media Connectivity tool
                                      6535          Playback protocol
                                      6539

  PortServer (Pro)                    6010
                                      6012
                                      6014

  ProEncode (DMS)                     8080

  Media Browse / Capture Manager   6000 - 6050      The firewall must be configured to to pass these UDP ports in BOTH directions between Profile and all MB components
                                    137 - 139       NetBIOS, used by Capture Service to communicate with ProfileXP.exe to trigger recordings
                                      1716          Passes UDP broadcast packets to allow the Profile Services to recover after a restart of the System Service
                                     11111          SV software uses this port to play out recordings from the low-res server
                                     11112          Used to send video in a preview window for Instant Record

  AirSpeed                             22           Secure Shell - Possibly required by remote clients
                                       23           For Telnetting into AirSpeed from another system
                                   80 & 8080        Outgoing connection to Media Manager


WG4                                                                   KnowledgeBase document ID:
ff408ed4-8a9f-47ad-9455-a11edcd48f53.xls         http://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=243397                                                      Page 6 of 11
                                     6010                      Outgoing connection to PortServer
                                     6530                      pluto_ftp
                                     6532                      Media Connectivity Tool
                                     6535                      Playback Protocol
                                     6538                      NVSysServer
                                     6539                      Transfer manager API - Possibly required by remote clients
                                     8990                      PAPI - Possibly required by remote clients
                                     8991                      PAPI - Possibly required by remote clients

  AirSpace                           6530
                                      20

  iNews                                 1           TCP        iNEWS Inter-system Messaging
                                       21         TCP (FTP)    FTP into iNEWS database: Teleprompters, Newscutter newsroom system tool, Data Receiver
                                       22        TCP or UDP    ssh
                                       25        TCP or UDP    sendmail
                                       67           UDP        used by PCU's to obtain an IP address via bootp
                                       80           TCP        http Web Access, for read-only database access
                                      513        TCP or UDP    rlogin
                                      600           TCP        FTP into Linux partition OBSOLETE in iNEWS 2.5 and later - see port 49152.
                                      698        TCP or UDP    may be required for Web Access through cgi-bin
                                      699           TCP        used by dbvisit (maintenance program) for on-line dbvisits – connection between iNEWS Servers.
                                     1019           TCP        server listens for client connections: iNEWS Workstation, Web Client, iNEWS COM, Data Receiver, iNEWS Instinct
                                     1020           TCP        Network dbdump / dbrestore between iNEWS Servers
                                                               Server updates/notifications sent to client, specified by client. Note each client running on a machine must bind to a unique
                                                               socket. So if a user intends to run N sessions of iNEWS on the same machine, then ports 1020 through 1020 + (N-1) must
                                    1020 †        UDP          be opened in the firewall. (TCP and UDP)
                                                               Search results sent to client from server, specified by client. Note each client running on a machine must bind to a unique
                                                               socket. So if a user intends to run N sessions of iNEWS on the same machine, then ports 1020 through 1020 + (N-1) must
                                    1020 †        TCP          be opened
          † These are the only ports on the iNEWS client. All other ports are on the iNEWS Server.
                                                               iNEWS bioserver communication. Each bioserver is connected to every other bioserver. On an ABC system the A
                                                               bioserver has a connection to both the B and C bioservers, The B bioserver is connected to the A and C bioservers. The C
                                     1022          TCP         bioserver is connected
                                     1023          TCP         used by connect and reconnect commands during startup
                                                               first remote access port for VNC to Linux UI, may have more than one VNC session configured (5902, 5903, etc) I don’t
                                     5901       TCP/SCTP think this is an officially supported configuration. These are not required to run iNEWS.
                                     6100          TCP         FTS indexing (configurable)
                                     6101          TCP         FTS searching (configurable)
                                     6825          TCP         monitor, for ControlAir
                                     6826          TCP         monitor for MOS
                                     6827          TCP         Monitor for iNEWS Command
                                    49152          TCP         telnet OBSOLETE in iNEWS 2.5 and later - see port 49153.
                                    49152       TCP (FTP) FTP into Linux Partition.
                                    49153          TCP         Telnet




WG4                                                                              KnowledgeBase document ID:
ff408ed4-8a9f-47ad-9455-a11edcd48f53.xls                    http://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=243397                                                 Page 7 of 11
  Newscutter                      21                    Required for NRCS tool

  Avid|DS                        135                    Reserved for RPC Windows service. It is critical to: Service Location Protocol, DS Indexing and throttling services

  VNC                            5800                   For remote access to AirSpeed UI
                                 5900                   For remote access to AirSpeed UI

  Countdown/ENPS                  21
                                10540                   LowerPortIn, LowerPortOut
                                10541                   UpperPortIn, UpperPortOut



  ISIS                      Last Updated on: Nov 30, 2005 @13:14 by Pete Balkus

                                IP Port       UDP/TCP   Description
                                      3000      UDP     ISIS uServer Communication (well known port)
                             3001 -> 3400       UDP     ISIS uServers (ISBs & ISS, IXS)
                                      5001      UDP     ISIS uServers - SD to uServer for failover control
                                      5004      UDP     ISIS uServers - admin agent and related to uServer (localhost normally)
                                      5015      TCP     ISS/IXS agents and uServer agents - Admin Login via https

                                4000-4399      UDP      ISIS NT Client to ISB Data Transfer, ISB msg and System Director msg traffic (range migration)

                                       5000    UDP      ISIS System Director - SD to SD failover control
                                       5003    UDP      ISIS System Director - Client, uServer and SD to SD control (well known port).
                                       5004    UDP      ISIS System Director - admin server and related to SD (localhost normally)
                                       5005    UDP      ISIS System Director - ISS/IXS status reporting to SD
                                       5015    TCP      ISIS System Director Admin Login via https

                               5016-5415       UDP      ISIS MAC Client to ISB Data Transfer, ISB msg and System Director msg traffic (range migration). Used for initial
                                                        prototype initiative and expects to migrate to same ports as NT client

                                                        Note - The port numbers for data transfer between client and ISB as well as those for incoming message traffic from the
                                                        index server or ISB's are all chosen from the range 4000-4399 on a dynamic basis. That is, not all 400 ports are in use at
                                                        any time, but the ports in use will vary over time over this entire range.




WG4                                                                       KnowledgeBase document ID:
ff408ed4-8a9f-47ad-9455-a11edcd48f53.xls             http://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=243397                                                      Page 8 of 11
                                                     3rp Party Port Usage Guide
Location                        Port                 Purpose
                                                     Active Directory port usage which uses more than just tcp/135. AD may also use the following ports for both AD client to
  ACTIVE DIRECTORY                                   DC and DC to DC communications
                                  135      TCP/UDP   RPC endpoint mapper
                                  137      TCP/UDP   Network basic input/output system (NetBIOS) name service
                                  138        UDP     NetBIOS datagram service
                                  139        TCP     NetBIOS session service
                              1024-65535     TCP     RPC dynamic assignment
                                  445      TCP/UDP   Server message block (SMB) over IP (Microsoft-DS)
                                  389        TCP     Lightweight Directory Access Protocol (LDAP)
                                  389        UDP     LDAP ping
                                  636        TCP     LDAP over SSL
                                 3268        TCP     Global catalog LDAP
                                 3269        TCP     Global catalog LDAP over SSL
                                   88      TCP/UDP   Kerberos
                                   53      TCP/UDP   Domain Name Service (DNS)



  Front Porch Digital AMC        6101       TCP      Used for AMC
                                                     Archive Manager Communicator is the DIVA module in charge of the communication with Interplay Archive Engine or
                                                     Archive Provider. AMC is a kind of gateway that talks with AVID with the internal protocol defined by Avid SDK and talks
                                                     with DIVA actor in ftp mode.

                                                     TCP 6101 is used. This is for control and data paths.

                                                     AMC can be on a separate server so usually FPD put our AMC on a server close to Avid AE and AP and any firewall is
                                                     normally set between the DIVA AMC and the DIVA Actor as it is standard ftp in this case using 6121 tcp port.




Windows AD and 3rd Party                                               KnowledgeBase document ID:
ff408ed4-8a9f-47ad-9455-a11edcd48f53.xls          http://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=243397                                                Page 9 of 12
              Knowledge base document ID http://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=243397

DATE                    USER               REASON



                                           Add ISIS 2.0 AD/LDAP enhancements from N Kemsley
                                           Interplay Delivery Service, Stream Server port details
nnSEP 09                David Shephard     that "arrive" with Interplay 2.0
                                           Update interplay page with newer primary reference
            7-Jul-09 David Shephard        add 3rd party sheet
           20-Apr-09 David Shephard        Add history sheet
                                           Add interplay Framemwork port changes/clarification
            20-Apr-09   Bob Craig          approx row 60
             4-Feb-08   David Shephard
            13-Jul-07   David Shephard     Add ISIS 1.4 port changes
           16-May-07    David Shephard




Update History                                              KnowledgeBase document ID:
ff408ed4-8a9f-47ad-9455-a11edcd48f53.xls
                                       http://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=243397     Page 10 of 12

								
To top