Skip to content

Latest commit

 

History

History
66 lines (61 loc) · 3 KB

proc_adding-a-subnet.adoc

File metadata and controls

66 lines (61 loc) · 3 KB

Adding a Subnet to {ProjectServer}

You must add information for each of your subnets to {ProjectServer} because {Project} configures interfaces for new hosts. To configure interfaces, {ProjectServer} must have all the information about the network that connects these interfaces.

To use the CLI instead of the {ProjectWebUI}, see the CLI procedure.

Procedure

  1. In the {ProjectWebUI}, navigate to Infrastructure > Subnets, and in the Subnets window, click Create Subnet.

  2. In the Name field, enter a name for the subnet.

  3. In the Description field, enter a description for the subnet.

  4. In the Network address field, enter the network address for the subnet.

  5. In the Network prefix field, enter the network prefix for the subnet.

  6. In the Network mask field, enter the network mask for the subnet.

  7. In the Gateway address field, enter the external gateway for the subnet.

  8. In the Primary DNS server field, enter a primary DNS for the subnet.

  9. In the Secondary DNS server, enter a secondary DNS for the subnet.

  10. From the IPAM list, select the method that you want to use for IP address management (IPAM). For more information about IPAM, see [Configuring_Networking_{context}].

  11. Enter the information for the IPAM method that you select.

  12. If you use the remote execution plugin, click the Remote Execution tab and select the {SmartProxy} that controls the remote execution.

  13. Click the Domains tab and select the domains that apply to this subnet.

  14. Click the {SmartProxies} tab and select the {SmartProxy} that applies to each service in the subnet, including DHCP, TFTP, and reverse DNS services.

  15. Click the Parameters tab and configure any subnet level parameters to apply to hosts attached to this subnet. For example, user defined Boolean or string parameters to use in templates.

  16. Click the Locations tab and select the locations that use this {SmartProxy}.

  17. Click the Organizations tab and select the organizations that use this {SmartProxy}.

  18. Click Submit to save the subnet information.

CLI procedure

  • Create the subnet with the following command:

    # hammer subnet create \
--boot-mode "DHCP" \
--description "My_Description" \
--dhcp-id My_DHCP_ID \
--dns-id My_DNS_ID \
--dns-primary "192.168.140.2" \
--dns-secondary "8.8.8.8" \
--domains "my-domain.tld" \
--from "192.168.140.111" \
--gateway "192.168.140.1" \
--ipam "DHCP" \
--locations "_My_Location" \
--mask "255.255.255.0" \
--name "My_Network" \
--network "192.168.140.0" \
--organizations "My_Organization"
--tftp-id My_TFTP_ID \
--to "192.168.140.250" \
Note

In this example, the --dhcp-id, --dns-id, and --tftp-id options use 1, which is the ID of the integrated {SmartProxy} in {ProjectServer}.