Chapter 3. Associating Objects with the Default Organization and Location

For Web UI Users

1. Navigate to Infrastructure > Domains and click Create Domain.
2. In the DNS Domain field, enter the full DNS domain name.
3. In the Fullname field, enter the plain text name of the domain.
4. Click the Parameters tab.
5. Click Add Parameter and fill in the Name and Value fields.
6. Click the Locations tab, and add the location where the domain resides.
7. Click the Organizations tab, and add the organization that the domain belongs to.
8. Click Submit to save the changes.

Associating the Domain with the Default Organization Using the Web UI

1. On the Main Menu, click Infrastructure Domains.
2. Select the domain in the Description column.
3. On the Locations tab, click Default_Location to add it to the Selected items list.
4. On the Organizations tab, click Default_Organization to add it to the Selected items list.
5. Click Submit.

Associating the Domain with the Default Organization Using Hammer ClI

1. Associate the domain to your organization.

   $ hammer organization add-domain --name "Default_Organization" --domain "domain_name.com"

2. Associate the domain to your location.

   $ hammer location add-domain --name "Default_Location" --domain "domain-name.com"

Configuring the Subnet Using the Web UI

1. On the Main Menu, click Infrastructure Subnets.

2. Click New Subnet and enter the information specific to your environment.

   1. If you use DHCP, enter the following information:

      • Name: Provisioning_Net
      • Network address: 172.17.13.0
      • Network mask: 255.255.255.0
      • Gateway Address: 172.17.13.1
      • Primary DNS Server: 172.17.13.2
      • Secondary DNS Server: Leave blank
      • IPAM: None
      • Start of IP Range: 172.17.13.100
      • End of IP Range: 172.17.13.150
      • VLAN ID: Leave blank
      • Boot Mode: DHCP

   2. If you use static IP addresses, enter the following information:

      • Name: Provisioning_Net
      • Network address: 172.17.13.0
      • Network mask: 255.255.255.0
      • Gateway Address: 172.17.13.1
      • Primary DNS Server: 172.17.13.2
      • Secondary DNS Server: Leave blank
      • IPAM: None
      • Start of IP Range: 172.17.13.100
      • End of IP Range: 172.17.13.150
      • VLAN ID: Leave blank
      • Boot Mode: Static
3. Click Submit.
4. Click Provisioning_Net to edit the subnet.
5. On the Domains tab, select example.org.
6. On the Capsules tab, change the TFTP and Discovery Proxy capsule to reflect the host name of the Satellite Server.
7. On the Locations tab, select Default_Location under All items to associate the domain with the default location.
8. On the Organizations tab, select Default_Organization under All items to associate the domain with the default organization.

Configuring the Subnet Using Hammer CLI

1. Create a subnet.

   1. Create a subnet using DHCP.

      # hammer subnet create --name Provisioning_Net \
      --organization "Default_Organization" \
      --locations 'RDU' \
      --domain-ids 1 \
      --boot-mode DHCP \
      --network 172.17.13.0 \
      --mask 255.255.255.0 \
      --ipam None \
      --dns-primary 172.17.13.1 \
      --gateway 172.17.13.1 \
      --from 172.17.13.100 \
      --to 172.17.13.150 \
      --tftp-id 1

   2. Create a subnet using static IP addresses.

      # hammer subnet create --name Provisioning_Net \
      --organization "Default_Organization" \
      --locations 'RDU' \
      --domain-ids 1 \
      --boot-mode Static \
      --network 172.17.13.0 \
      --mask 255.255.255.0 \
      --ipam None \
      --dns-primary 172.17.13.1 \
      --gateway 172.17.13.1 \
      --from 172.17.13.100 \
      --to 172.17.13.150 \
      --tftp-id 1

      Note

      You cannot set the discovery proxy using Hammer CLI.