Download udp config

The ToD server on the Cisco CMTS. Step 5 exit Example: Router(config)# exitRouter# Exits global configuration mode. Disabling Time-of-Day Service To disable the ToD server, use the following procedure, beginning in EXEC mode. Procedure Command or Action Purpose Step 1 enable Example: Router> enableRouter# Enables privileged EXEC mode. Enter your password if prompted. Step 2 configure terminal Example: Router# configure terminal Router(config)# Enters global configuration mode. Step 3 no cable time-server Example: Router(config)# cable time-serverRouter(config)# Disables the ToD server on the Cisco CMTS. Step 4 no service udp-small-servers Example: Router(config)# no service udp-small-servers Router(config)# (Optional) Disables the use of all minor UDP servers. Note Do not disable the minor UDP servers if you are also enabling the other DHCP or TFTP servers. Step 5 exit Example: Router(config)# exit Router# Exits global configuration mode. Configuring TFTP Service To configure TFTP service on a Cisco CMTS where the CMTS can act as a TFTP server and download a DOCSIS configuration file to cable modems, perform the following steps: Create the DOCSIS configuration files using the DOCSIS configuration editor of your choice. Copy all desired files (DOCSIS configuration files, software upgrade files, and Cisco IOS configuration files) to the Flash memory device on the Cisco CMTS. Typically, this is done by placing the files first on an external TFTP server, and then using TFTP commands to transfer them to the router’s Flash memory. Enable the TFTP server on the Cisco CMTS with the tftp-server command. Each configuration task is required unless otherwise listed

4 (Optional) Sets the number of hours for which statistics are maintained for an IP SLAs operation. Step 12 (Optional) history lives-kept lives Example: switch(config-ip-sla-udp)# history lives-kept 5 (Optional) Sets the number of lives maintained in the history table for an IP SLAs operation. Step 13 (Optional) owner owner-id Example: switch(config-ip-sla-udp)# owner admin (Optional) Configures the Simple Network Management Protocol (SNMP) owner of an IP SLAs operation. Step 14 (Optional) request-data-size bytes Example: switch(config-ip-sla-udp)# request-data-size 64 (Optional) Sets the protocol data size in the payload of an IP SLAs operation's request packet. Step 15 (Optional) history statistics-distribution-interval milliseconds Example: switch(config-ip-sla-udp)# history statisticsdistribution- interval 10 (Optional) Sets the time interval for each statistics distribution kept for an IP SLAs operation. Step 16 (Optional) tag text Example: switch(config-ip-sla-udp)# tag TelnetPollServer1 (Optional) Creates a user-specified identifier for an IP SLAs operation. Step 17 (Optional) threshold milliseconds Example: switch(config-ip-sla-udp)# threshold 10000 (Optional) Sets the upper threshold value for calculating network monitoring statistics created by an IP SLAs operation. Step 18 (Optional) timeout milliseconds Example: switch(config-ip-sla-udp)# timeout 10000 (Optional) Sets the amount of time an IP SLAs operation waits for a response from its request packet. Step 19 (Optional) tos number Example: switch(config-ip-sla-jitter)# tos 160 (Optional) In an IPv4 network only, defines the ToS byte in the IPv4 header of an IP SLAs operation. Step 20 (Optional) verify-data Example: switch(config-ip-sla-udp)# verify-data (Optional) Causes an IP SLAs operation to check each reply packet for data corruption. Step 21 exit Example: switch(config-ip-sla-udp)# exit Exits UDP configuration submode and returns to global configuration mode. Scheduling IP SLAs Operations This section describes how to schedule IP SLAs operations. Before you begin Note All IP SLAs operations to be scheduled must be already configured. The frequency of all operations scheduled in a multioperation group must be the same. The list of one or more operation ID numbers to be added to a multioperation group is limited to a maximum of 125 characters, including commas (,). Tip If the IP SLAs operation is not running and generating statistics, add the verify-data command to the configuration of the operation (while configuring in

Hostname} sourceport port-number] [control {enable | disable}] (Optional) history buckets-kept size (Optional) data-pattern hex-pattern (Optional) history distributions-of-statistics-kept size (Optional) history enhanced [interval seconds] [buckets number-of-buckets] (Optional) history filter {none | all | overThreshold | failures} (Optional) frequency seconds (Optional) history hours-of-statistics-kept hours (Optional) history lives-kept lives (Optional) owner owner-id (Optional) request-data-size bytes (Optional) history statistics-distribution-interval milliseconds (Optional) tag text (Optional) threshold milliseconds (Optional) timeout milliseconds (Optional) tos number (Optional) verify-data exit DETAILED STEPS Command or Action Purpose Step 1 enable Example: switch> enable Enables privileged EXEC mode. Enter your password if prompted. Step 2 configure terminal Example: switch# configure terminal Enters global configuration mode. Step 3 ip sla operation-number Example: switch(config)# ip sla 10 Begins configuration for an IP SLAs operation and enters IP SLA configuration mode. Step 4 udp-echo {destination-ip-address | destination-hostname} destination-port [source-ip {ip-address | hostname} sourceport port-number] [control {enable | disable}] Example: switch(config-ip-sla)# udp-echo 172.29.139.134 5000 Defines a UDP echo operation and enters IP SLA UDP configuration mode. Use the control disable keyword combination only if you disable the IP SLAs control protocol on both the source and target switches. Step 5 (Optional) history buckets-kept size Example: switch(config-ip-sla-udp)# history buckets-kept25 (Optional) Sets the number of history buckets that are kept during the lifetime of an IP SLAs operation. Step 6 (Optional) data-pattern hex-pattern Example: switch(config-ip-sla-udp)# data-pattern (Optional) Specifies the data pattern in an IP SLAs operation to test for data corruption. Step 7 (Optional) history distributions-of-statistics-kept size Example: switch(config-ip-sla-udp)# historydistributionsof- statistics-kept 5 (Optional) Sets the number of statistics distributions kept per hop during an IP SLAs operation. Step 8 (Optional) history enhanced [interval seconds] [buckets number-of-buckets] Example: switch(config-ip-sla-udp)# history enhancedinterval 900 buckets 100 (Optional) Enables enhanced history gathering for an IP SLAs operation. Step 9 (Optional) history filter {none | all | overThreshold | failures} Example: switch(config-ip-sla-udp)# history filter failures (Optional) Defines the type of information kept in the history table for an IP SLAs operation. Step 10 (Optional) frequency seconds Example: switch(config-ip-sla-udp)# frequency 30 (Optional) Sets the rate at which a specified IP SLAs operation repeats. Step 11 (Optional) history hours-of-statistics-kept hours Example: switch(config-ip-sla-udp)# historyhours-ofstatistics- kept

UDP echo operation on the source. Note To add proactive threshold conditions and reactive triggering for generating traps, or for starting another operation, to an IP SLAs operation, see the "Configuring Proactive Threshold Monitoring" section. Before you begin If you are using the IP SLAs Responder, ensure that you have completed the "Configuring the IP SLAs Responder on the Destination Device" section before you start this task. SUMMARY STEPS enable configure terminal ip sla operation-number udp-echo {destination-ip-address | destination-hostname} destination-port [source-ip {ip-address | hostname} sourceport port-number] [control {enable | disable}] (Optional) frequency seconds (Optional) end DETAILED STEPS Command or Action Purpose Step 1 enable Example: switch> enable Enables privileged EXEC mode. Enter your password if prompted. Step 2 configure terminal Example: switch# configure terminal Enters global configuration mode. Step 3 ip sla operation-number Example: switch(config)# ip sla 10 Begins configuration for an IP SLAs operation and enters IP SLA configuration mode. Step 4 udp-echo {destination-ip-address | destination-hostname} destination-port [source-ip {ip-address | hostname} sourceport port-number] [control {enable | disable}] Example: switch(config-ip-sla)# udp-echo 172.29.139.134 5000 Defines a UDP echo operation and enters IP SLA UDP configuration mode. Use the control disable keyword combination only if you disable the IP SLAs control protocol on both the source and target switches. Step 5 (Optional) frequency seconds Example: switch(config-ip-sla-udp)# frequency 30 (Optional) Sets the rate at which a specified IP SLAs operation repeats. Step 6 (Optional) end Example: switch(config-ip-sla-udp)# end (Optional) Returns to privileged EXEC mode. Configuring a UDP Echo Operation with Optional Parameters on the Source Device This section describes how to configure a UDP echo operation with optional parameters on the source device. Note To add proactive threshold conditions and reactive triggering for generating traps, or for starting another operation, to an IP SLAs operation, see the "Configuring Proactive Threshold Monitoring" section. Before you begin If you are using an IP SLAs Responder in this operation, the responder must be configured on the destination device. See the "Configuring the IP SLAs Responder on the Destination Device" section. SUMMARY STEPS enable configure terminal ip sla operation-number udp-echo {destination-ip-address | destination-hostname} destination-port [source-ip {ip-address |

Set the "Path" to the location of FactoryServer.exe, Set the "Arguments" to "-unattended". You can modify other settings if you want, but that's the only required step. Click "install", then run this command.nssm.exe start SatisfactoryServerServiceOther useful nssm commands:nssm.exe status SatisfactoryServerService # Checks the status of the Servicenssm.exe stop SatisfactoryServerService # Stops the service, and prevents it from auto-restartingDocker[]Docker is a cross-platform utility designed to run services in virtual machines in a compartmentalized fashion. This is an example dockerfile you can use to run the Satisfactory dedicated server inside a docker containerFROM cm2network/steamcmd:root#BUILD: docker build -t satisfactory .#RUN: mkdir data; docker run -p 15000:15000/udp -p 7777:7777/udp -p 15777:15777/udp -d --name=satisfactory -v $(pwd)/data:/home/steam/Satisfactory-dedicated satisfactoryENV STEAMAPPID 1690800ENV STEAMAPP SatisfactoryENV STEAMAPPDIR "${HOMEDIR}/${STEAMAPP}-dedicated"RUN echo -e "export LD_LIBRARY_PATH=${STEAMAPPDIR}/linux64:$LD_LIBRARY_PATH\n\bash ${STEAMCMDDIR}/steamcmd.sh +login anonymous +force_install_dir ${STEAMAPPDIR} +app_update ${STEAMAPPID} validate +quit\n\test -d ~/.config/Epic/FactoryGame/Saved || mkdir -p ~/.config/Epic/FactoryGame/Saved\n\test -d ${STEAMAPPDIR}/saves || mkdir ${STEAMAPPDIR}/saves\n\test -L ~/.config/Epic/FactoryGame/Saved/SaveGames || ln -s ${STEAMAPPDIR}/saves ~/.config/Epic/FactoryGame/Saved/SaveGames\n\${STEAMAPPDIR}/FactoryServer.sh" >> ${HOMEDIR}/entry.shRUN chmod +x "${HOMEDIR}/entry.sh" && chown -R "${USER}:${USER}" "${HOMEDIR}"USER ${USER}VOLUME ${STEAMAPPDIR}WORKDIR ${HOMEDIR}CMD ["bash", "entry.sh"]EXPOSE 15777/udp 15000/udp 7777/udpThe $STEAMAPPDIR is declared as a volume so that the savegames and the config of the server can be accessed and modified from outside the container. If that is not mapped to a host directory as done with -v, it will go into /var/lib/docker/volumes. You can find exactly where using docker inspect on the running container. More information here.Docker-Compose[] Use the following example docker-compose file in parallel with the Dockerfile and run docker-compose up -d for a detached background server.version: "3"services: satisfactory: build: . restart: always ports: - 15777:15777/udp - 15000:15000/udp - 7777:7777/udp volumes: - ./data:/home/steam/Satisfactory-dedicatedv · d · eSatisfactory game mechanicsPlayer abilitiesCodex • Console • Controls • Build Gun • Flashlight • HUD • Inventory • Crate • Ping • Resource Scanner • Resource node • Resource Well • Health • Radiation • To-Do List • SettingsUnlockable abilitiesOverclocking/Underclocking • Customizer • Map • Power • Productivity Display • Head lift • Fuels • FICSIT Productive Packer DeluxeProgressionDrop-pod • Onboarding (In-game tutorial) • Milestones • MAM • Alternate recipes (Analysis) • Space Elevator • AWESOME Sink • AWESOME Shop • FICSMASMiscellaneousFuture content • Old