The UAN product provides a role, uan_interfaces
in the Configuration Framework Service (CFS). This role is suitable for Application type nodes, and in some circumstancs, configuring the CHN, on Compute type nodes.
Enable CAN or CHN by setting the following in the UAN CFS repo (the filename may be modified to whatever is appropriate):
ncn-m001:~/ $ cat group_vars/Application_UAN/can.yml
uan_can_setup: true
SLS will be configured with either CAN or CHN, uan_interfaces
will use this setting to determine if a default route should be established over the nmn (CAN) or the hsn (CHN). To see how the site is configured, query SLS:
ncn-m001:~/ $ cray sls search networks list --name CHN --format json | jq -r '.[] | .Name'
CHN
(Optional) If the compute nodes are going to use the UAN CFS role uan_interfaces
to set a default route on the CHN, make sure there is an appopriate ansible setting for the compute nodes in addition to the UANs:
ncn-m001:~/ $ cat group_vars/Compute/can.yml
uan_can_setup: true
Once uan_can_setup
has been enabled, update the CFS configuration used for the nodes to initate a reconfiguration (see the Configuration Management section of the CSM documentation for more information)
The CSM documenation provides additional resources to validate the configuration of CAN and CHN for UANs and Computes. Consult the section titled “Enabling Customer High Speed Network Routing” in the CSM documentation for more information.