Beginning with DSA 16.10.01, you can define network fabric. If a network fabric is defined, it applies a logical network mask when a job plan generates data paths between AMPs and BARNC processes acting as media servers. Prior to DSA 16.10, network masks were used for the routing of traffic between nodes and media servers. Starting with DSA 16.10 all nodes are autoconfigured and node IP addresses can no longer be edited or removed.
Customers who use their media servers for multiple Teradata systems may need to use network fabric. For example, if the media servers and TPA nodes are connected both through BYNET® and a LAN interface, defining fabric is required.
The network fabric belongs to a specific Teradata system and defines the path from the TPA node to the BARNC IP address. If fabric is defined, job submission skips the logical net mask and selects the existing fabric when defining job data paths.
The fabric component can include all the nodes and their paths to one or more media servers.
The target group must define one media server that belongs to the network fabric. For best performance, include all media servers that belong to the fabric.
For DSA release 16.20.12 and later, you can define the network fabric using either the BAR Setup portlet or the CLI config_fabrics command.
You can define multiple fabrics but each must be unique. For example, System A can have two fabrics for two target systems B and C, fabricAB and fabricAC. The information is saved into the repository and can be edited if new media servers or nodes are added.
For multiple fabrics, update dsc.properties for the number of fabrics allowed per Teradata system: maxlimit.fabric=number-fabrics. Default is 64.
The fabric is used only for backup, restore, and analyze_validate jobs.