Cray System Management Documentation > Cray System Management (CSM) Administration Guide > system layout service > Add UAN CAN IP Addresses to SLS

Add UAN CAN IP Addresses to SLS

Add the Customer Access Network (CAN) IP addresses for User Access Nodes (UANs) to the IP address reservations in the System Layout Service (SLS). Adding these IP addresses will propagate the data needed for the Domain Name Service (DNS).

For more information on CAN IP addresses, refer to the Customer Accessible Networks.

Prerequisites

This procedure requires administrative privileges.

Procedure

Retrieve the SLS data for the CAN.

export TOKEN=$(curl -s -k -S -d grant_type=client_credentials \
-d client_id=admin-client -d client_secret=`kubectl get secrets admin-client-auth \
-o jsonpath='{.data.client-secret}' | base64 -d` \
https://api-gw-service-nmn.local/keycloak/realms/shasta/protocol/openid-connect/token \
| jq -r '.access_token')

curl -s -k -H "Authorization: Bearer ${TOKEN}" \
https://api-gw-service-nmn.local/apis/sls/v1/networks/CAN|jq > CAN.json

cp CAN.json CAN.json.bak

Edit the CAN.json file and add the desired UAN CAN IP addresses in the ExtraProperties.Subnets section.

This subsection is located under the CAN Bootstrap DHCP Subnet section. The IP address reservations array needs to be added in the following JSON format:
```
      {
        "Comment": "x3000c0s23b0n0",
        "IPAddress": "10.103.2.20",
        "Name": "uan01"
      },
```
If multiple alias are required, the JSON format would be:
```
      {
        "Aliases": [
          "uan01-can",
          "uan01-slurm"
        ],
        "Comment": "x3000c0s23b0n0",
        "IPAddress": "10.103.2.20",
        "Name": "uan01"
      },
```
IMPORTANT: There must be an alias or name defined in a format that matches the hostname of the UAN. This is required by the CFS play uan_interfaces that configures the CAN interface on UANs. If the CAN is not being configured for a particular UAN, then this requirement is not needed.

Upload the updated CAN.json file to SLS.

curl -s -k -H "Authorization: Bearer ${TOKEN}" --header \
"Content-Type: application/json" --request PUT --data @CAN.json \
https://api-gw-service-nmn.local/apis/sls/v1/networks/CAN

Verify that DNS records were created.

It will take about five minutes before any records will show up.

For example:
```
nslookup uan01.can
```
Example output:
```
Server:     10.92.100.225
Address:    10.92.100.225#53

Name:       uan01.can
Address:    10.103.2.24
```
```
nslookup uan01-can.can
```
Example output:
```
Server:     10.92.100.225
Address:    10.92.100.225#53

Name:       uan01-can.can
Address:    10.103.2.24
```
As stated above, the UAN play uan_interfaces will attempt to nslookup the hostname of the node with with “.can” appended. Make sure this alias resolves if the CAN is going to be configured on that particular UAN. In certain upgrade scenarios, the expected alias may not have been added by default.