Edit the files below as root. For changes to take effect, restart the network with /bin/systemctl restart network.

You may need the following:

• The static IP address and host name for your system.
• The network gateway IP address.
• The subnet mask of your network.
• DNS server IP address(es).
• Port configuration of any network interfaces.
• If your /etc/exports file contains file paths that are no longer valid, the NFS service will be unable to start. Make sure the file only contains valid file paths.
• Multipath drivers are supported on CentOS 7.2, however the luns IDs must be reconfigured. To do this:
  1. From a shell, as root, cd to /opt/Autodesk/DKU/current/Utils/Storage/DH_Configurator_v1.12
  2. Run ./DH_config.sh -d. You are prompted for the drive's IP address. The default values are 10.0.0.2 for Controller A, and 10.0.0.3 for Controller B.
  3. Enter the IP address of the drive you want to configure (Controller A or B).
  4. Select Option 9 (Update luns ID) from the list of options.
  5. Reboot the workstation.

etc/resolv.conf

resolv.conf is used by the OS to configure the system's Domain Name System (DNS) resolver. For help, at the command line enter man resolver.

/etc/sysconfig/network-scripts/ifcfg-ethn

Edit /etc/sysconfig/network-scripts/ifcfg-ethn, where n specifies the ethernet port number, usually 0 for the first on-board port. If your workstation has an add-on ethernet card installed, the Linux operating system may assign ports eth0 through eth3 to the add-on card. In this case, the on-board Ethernet ports become eth4 and eth5. You may need to set the following:

• Optionally set the GATEWAY if not set in /etc/sysconfig/network.
• IPADDR
• NETMASK
• MTU

Sample snippet from ifcfg-eth*n*:

DEVICE="eth0"
BOOTPROTO="static"
IPADDR="192.168.1.100"
NETMASK="255.255.0.0"
ONBOOT="yes"
GATEWAY=192.168.0.1

/opt/Autodesk/cfg/network.cfg

This file is only available after the installation of the Autodesk product. See the comments in the file itself for examples. If the file is changed, all running applications and background services immediately use the new configuration without the need for manual restart.

network.cfg parameters

UUID

The workstation's Universally Unique Identifier (UUID) is automatically generated by the application installer. Once assigned, the UUID should never be edited as it uniquely identifies the workstation and the resource it controls. Having different workstations using the same UUID will result in conflicts.

DisplayName

The DisplayName is the human-readable equivalent of the UUID and is the name displayed in the UI to identify the workstation. Does not have to be unique, but it helps if all effects and finishing workstations on a network use a different DisplayName so the users can know which is which. On Linux, this will usually map by default to the current hostname.

Metadata

Comma separated list of the local network interfaces to be used for metadata operations. Metadata operations are usually small IO operations that may degrade performance when done on a high speed network adapter when a lower speed adapter can be used instead. The order of the interfaces in the list is the order in which they will be tried. If left empty, all active interfaces will be used.

Data

Comma separated list of the local network interfaces to be used for large data operations. The order of the interfaces in the list is the order in which they will be tried. If left empty, all active interfaces will be used.

Multicast

Comma separated list of the local network interfaces to be used to limit multicast/discovery operations. If left empty, all active interfaces that support multicast will be used. In a facility where all machines are connected to the same networks (a house network and a high speed network for example), multicasting could only be done on one network to reduce traffic. Stone+Wire, unlike Wiretap, will only use the first non-loopback interface if multiple interfaces are defined.

To be usable for multicasting, the network interface must have the MULTICAST flag enabled at the OS level. This can be validated and changed using the ifconfig or ip link commands. Enabling the 'MULTICAST' flag on the 'loopback' interface is recommended to help ensure discoverability of local services.

Port

The UDP port to use for self-discovery. This value must be the same for every workstation on your network. Default: Port=7555.

Scope

Scope of the multicast. Consult your network administrator. For a network with one subnet, Link Local (224.0.0.1) should be used, with TTL = 1. For a network with more than one subnet, use a scope appropriate to your network requirements and router configuration; you also need to edit the TTL value. The scope value must be the same for every workstation on your network.

TTL

Multicast TTL (Time-To-Live) further refines the scope of the multicast. This tells the router how to deal with Self-Discovery, and works together with the "Scope". The TTL value must be the same for every workstation on your network.

/opt/Autodesk/cfg/service.cfg

By the default, Wiretap rely on mutlicast to discover other services running on the local and remote hosts on the network. Some configuration might prevent the use of multicast. The configuration file /opt/Autodesk/cfg/services.cfg can be used to manually expose these services.

/etc/sysconfig/network

Sample snippet from /etc/sysconfig/network.

NETWORKING=yes
HOSTNAME=workstation1
GATEWAY="10.1.0.25" // The GATEWAY value is used if no GATEWAY is defined in a network port’s configuration file.

/etc/hosts

You may need to edit the loopback setting which may look like 127.0.0.1 vxfhost.localhost.localdomain localhost by default. Optionally add hostname / IP address pairs for other workstations on your network.

Sample snippet:

127.0.0.1 localhost.localdomain localhost
192.168.0.100 workstation1

Static Ports

Here is a list of static network ports used by different service and the way to configure them

Dynamic Ports

Some services/clients will also open dynamic network ports in the range configured on the system. This range typically goes from 49,152 (0xC000) to 65,535 (OxFFFF). On linux, this range can be limited by editing /proc/sys/net/ipv4/ip_local_port_range.

Dynamic Range can be restricted for Backburner Monitor in the ☰ menu of the application or using the -e option.