Trackman V3 IT Requirements

Trackman V3 Server IT/Firewall Needs

  • Place V3 Server on Internal Stadium Network
    • Tagging page should only be accessible to devices on the Stadium Network
  • Whitelist server MAC address
    • MAC address of server will be provided by TrackMan in case IT department needs
      to approve network access for the server to be on local network
  • Set inbound/outbound firewall rules for provided ports
    • In order to be operational, V3 server requires certain endpoints outside of local network to be reachable.

Please pass this information to your IT department to ensure that the V3 server can function properly at the time of installation.

Required Ports and Endpoints

Internal Network

Port Description
80/tcp, 443/tcp – HTTP(S) EventHub Namespaces
metadata-v3-stadium-bb-trackman.servicebus.windows.net
control-v3-stadium-bb-trackman.servicebus.windows.net
ball-v3-stadium-bb-trackman.servicebus.windows.net
login.trackmanbaseball.com
account.trackmanbaseball.com
sastokenprovider.trackmanbaseball.com
heartbeatprocessor.trackmanbaseball.com
taggingappdispatcher.trackmanbaseball.com
tscservices.trackmanbaseball.com
contextualdatacacheservice.trackmanbaseball.com
tmtrackingsystemconfiguration.servicebus.windows.net
22/tcp SSH tunnel
53/tcp, 53/udp DNS
5671/tcp, 5372/tcp AMQP / Azure ServiceBus
9243/tcp Allow TCP outbound traffic for data upload

Internet endpoints

Port Description
ICMP Ping / network testing
20999

Scoreboard feed: UDP packets are broadcasted with destination port 20999 (required for scoreboard to be operational)

20998

Broadcast feed: UDP packets are broadcasted with destination port 20998 (required for scoreboard to be operational)

5671 and 5672

EventHub Namespaces

  • metadata-v3-stadium-bb-trackman.servicebus.windows.net
  • control-v3-stadium-bb-trackman.servicebus.windows.net
  • ball-v3-stadium-bb-trackman.servicebus.windows.net
  • tmtrackingsystemconfiguration.servicebus.windows.net

UDP 3478
UDP 41641

TailScale Remote Management.

No Inbound traffic from the Internet is needed, but local Inbound traffic for these ports/protocols to the BB server IP must not be blocked in the firewall:

Port Description
80/tcp, 443/tcp – HTTP(S) Tagging App: Local taggers will connect to the server by opening a web page in a browser

salt-master-prod.trackmanbaseball.com:22 (52.170.26.239:22)
metadata-v3-stadium-bb-trackman.servicebus.windows.net:5671 (52.191.45.185:5671)
metadata-v3-stadium-bb-trackman.servicebus.windows.net:5672 (52.191.45.185:5672)
metadata-v3-stadium-bb-trackman.servicebus.windows.net:443 (52.191.45.185:443)
control-v3-stadium-bb-trackman.servicebus.windows.net:5671 (52.191.45.180:5671)
control-v3-stadium-bb-trackman.servicebus.windows.net:5672 (52.191.45.180:5672)
control-v3-stadium-bb-trackman.servicebus.windows.net:443 (52.191.45.180:443)
ball-v3-stadium-bb-trackman.servicebus.windows.net:5671 (52.191.45.167:5671)
ball-v3-stadium-bb-trackman.servicebus.windows.net:5672 (52.191.45.167:5672)
ball-v3-stadium-bb-trackman.servicebus.windows.net:443 (52.191.45.167:443)
mirror.westeurope.cloudapp.azure.com:443 (40.74.59.159:443)
tscservices.trackmanbaseball.com:443 (13.107.246.57:443)
heartbeatprocessor.trackmanbaseball.com:443 (13.107.213.57:443)
sastokens.trackmanbaseball.com:443 (13.107.213.57:443)
contextualdatacacheservice.trackmanbaseball.com:443 (13.107.213.57:443)
account.trackmanbaseball.com:443 (13.107.246.57:443)
taggingappdispatcher.trackmanbaseball.com:443 (13.107.246.57:443)
proservices.trackmanbaseball.com:80 (unknown:80)
tmtrackingsystemconfiguration.servicebus.windows.net:80 (52.168.133.227:80)
tmprobbdevelopment.azurecr.io:80 (20.62.128.24:80)
trackmanrangecontainerregistry-on.azurecr.io:80 (20.62.128.19:80)
tmsharedreg.azurecr.io:80 (unknown:80)
pool.ntp.org:123 (51.81.226.229:123)

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request