IP Address Management (IPAM)

IPv4 IPAM Appliance

Overview

The TCPWave IPAM Appliance is a comprehensive tool designed for managing various IP Address Management (IPAM) services and configurations. This documentation provides a detailed explanation of its features, functionalities, and the step-by-step process to add an IPAM appliance in the TCPWave system.

Main Functions of the TCPWave IPAM Appliance

1. User Interface for IPAM Services Management:

   • Manages various services such as NTP/DNS Resolver, SNMP, PAM Settings, SysLogs, etc.

   • Provides operations like start, stop, restart, and rebuild indexes for several services (NTP, SSH, SNMP, CLI Engine, Database, etc.).

2. Service Status Indicators:

   • A live, functioning IPAM is indicated in green.

   • An IPAM without a heartbeat, suggesting it’s not operational, is shown in red.

3. Default Configuration:

   • Automatically set as ‘localhost’ in the absence of Disaster Recovery (DR) or High Availability (HA) setups.

   • In a DR setup, it includes both master and slave IPAM appliances.

   • With HA setup, it encompasses all HA cluster IPAMs.

Operations Available in the TCPWave IPAM Interface

1. Add: Introduce new configurations or services.

2. Clone: Duplicate existing settings or services for reuse.

3. Edit: Modify existing configurations or settings.

4. Delete: Remove configurations or services.

5. Bookmark: Mark frequently used settings or pages for easy access.

6. Sync: Synchronize settings or services across different systems or networks.

7. Manage Services: Oversee and control various IPAM services.

8. Deploy Firmware: Update or install new firmware versions.

Additional Functionalities**

• Common Functionalities: Includes options like Refresh, Column Visibility, Reset Preferences, and More options.

• Grid Search Functionality: Allows for efficient searching and filtering within the grid or data view.

• Role-Based Access: Certain sections and functionalities are enabled or disabled based on the user’s assigned role.

Important Note

The access to certain functionalities or sections in the TCPWave IPAM appliance is contingent upon the permissions associated with the user’s role. Therefore, users should be aware of their specific role and the permissions it entails to fully utilize the IPAM appliance.

Adding an IPAM Appliance in TCPWave System

1. Accessing the IPAM Appliances Page

• Navigate to: Network Management > IPAM Management > IPAM Appliances.

• Click on the option to create a new appliance, leading to the “Create Appliance” page.

2. Completing Different Configuration Tabs

The creation process involves filling out information in several tabs:

1. Application Configuration

• IP Address: Enter the appliance’s IP address. Other fields like Organization and Appliance Name are auto-populated.

• Firewall Template: Select from a dropdown. This configures firewall rules based on the chosen template.

• Appliance Group: Specify the appliance group.

• Description: Provide a description for the appliance.

• Time Zone Attributes: Choose the appropriate time zone.

  Banner Configuration within Application Configuration:

  • Set appliance type, banner color, and enter descriptions for IPAM login and SSH banners.

2. NTP and DNS Resolver

• Configure NTP settings, including the number of NTP Appliances for synchronization, IP addresses, authentication details, and DNS Resolver settings.

3. Monitoring

• Configure SNMP settings, including enabling SNMP traps, specifying target IP addresses for traps, and community strings.

• Choose processes to monitor via SNMP.

• If SNMPv3 is enabled, additional details can be added in the SNMPv3 tab.

4. SNMPv3

• Add SNMPv3 user details, including username, passwords, and authentication and encryption protocols.

5. PAM Settings

• Configure LDAP and TACACS+ authentication settings.

• Set up root and iDRAC password settings.

6. Elevated Privileges

• This section allows assigning specific command execution privileges to users.

7. Network Configuration

• Manage network interfaces, routing tables, and IP routing information.

• Includes adding, editing, and deleting network interfaces and virtual interfaces, configuring duplex settings, and policy-based routing.

8. Syslog-NG

• Configure Syslog-NG for efficient log message management, including setting options, defining sources, filters, and destinations.

Key Points to Remember

• Role-Based Access: Certain configurations may depend on the permissions associated with your role.

• Firewall Configuration: Associating a firewall template updates firewall rules based on SNMP ACLs and the selected template.

• Monitoring Options: Choose which processes to monitor and whether to use SNMPv3 for enhanced security.

• PAM Settings: These include LDAP and TACACS+ settings, along with root password configurations.

• Elevated Privileges: Grant specific command execution rights to certain users or groups.

• Network Configuration: This involves detailed settings for network interfaces and routing, crucial for the appliance’s connectivity and operation.

• Syslog-NG: Set up for log message collection and management, crucial for troubleshooting and system maintenance.

Common Functionalities

In addition to these specific configurations, remember to utilize common functionalities like refresh, column visibility, reset preferences, and more options as needed throughout the process.

IPv6 IPAM Appliance

Overview The IPv6 IPAM (IP Address Management) appliance serves as a centralized interface designed to manage and configure various IPAM services. It plays a crucial role in environments utilizing IPv6, addressing the complexity and scale of IPv6 networks. This documentation provides a detailed explanation of its functionalities and features, including the step-by-step process to add an IPAM appliance.

Core Functionality

1. Service Management: - Manages IPAM services like NTP/DNS Resolver, SNMP, PAM Settings, SysLogs, etc. - Operations include starting, stopping, restarting, and rebuilding index operations for various services.

2. Status Indicators: - Live IPAM is indicated in green. - Inactive IPAM, without a heartbeat, is shown in red, indicating issues or non-operation.

3. Default Configuration: - Localhost Setup: IPAM appliance is set as ‘localhost’ by default in the absence of DR or HA setups. - DR and HA Configurations: In DR setup, includes master and slave IPAM appliances. In HA setup, encompasses all HA cluster IPAMs.

Available Operations on the IPAM Interface

1. Add: Introduce new IPAM configurations or services.

2. Clone: Duplicate existing configurations for efficient setup replication.

3. Edit: Modify configurations as per requirements.

4. Delete: Remove unnecessary or outdated configurations.

5. Bookmark: Mark frequently used settings or services for quick access.

6. Sync: Synchronize settings across different systems or network components.

7. Manage Services: Control and oversee various IPAM-related services.

8. Deploy Firmware: Update or install new firmware for the appliance.

Additional Features and Functionalities

• Common Functionalities: Includes Refresh, Column Visibility, Reset Preferences, More Options, essential for efficient interface management.

• Grid Search Functionality: Enables efficient searching through data and configurations within the grid or data view.

• Role-Based Access Control: Certain functionalities or sections are enabled or disabled based on the user’s assigned role. Detailed role information can be accessed under Administrator Roles.

Important Considerations

• Access to specific functionalities within the IPv6 IPAM appliance interface depends on the permissions associated with your administrative role. Understanding your role’s permissions is essential to utilize the interface effectively.

• Given the expanded address space and complexity of IPv6 networks, efficient management and configuration through the IPAM appliance are crucial for network stability and performance.

Use in IPv6 Environments

In an IPv6 environment, the IPAM appliance’s role becomes even more critical due to the vast address space and complexity it introduces in network management. The appliance provides a streamlined interface for handling large-scale and complex IPv6 networks, ensuring efficient address allocation, tracking, and overall network health monitoring.

Adding an IPAM (IP Address Management) Appliance

1. Access the IPAM Appliances Page

• Navigation: Go to Network Management > IPAM Management > IPAM Appliances. This displays the “IPAM Appliances” page.

• Creation: Click to initiate the creation process, leading to the “Create Appliance” page with multiple tabs for configuration.

2. Configuration Tabs and Their Details

Each tab requires specific information:

1. Application Configuration

• IP Address: Input the appliance’s IP address.

• Firewall Template: Choose from a dropdown list; configuring this affects the iptables and firewall rules.

• Appliance Group: Specify the group for the appliance.

• Description: Provide a detailed description.

• Time Zone: Select the appropriate time zone.

  For Banner Configuration:

  • Select appliance type, banner color, and provide descriptions for IPAM login and SSH banners.

2. NTP and DNS Resolver

• Configure synchronization with NTP Appliances, including addresses, upstream and downstream authentication, key settings, and DNS resolver configurations.

3. Monitoring

• Set up SNMP for monitoring with options for enabling traps, specifying target IP addresses, and setting community strings.

• Choose processes to be monitored via SNMP (e.g., NTP Process, TIMS, MariaDB).

• Enable SNMPv3 and provide relevant user details if required.

4. SNMPv3

• Add SNMPv3 user details, including usernames, passwords, and authentication and encryption protocols.

5. PAM Settings

• Configure LDAP and TACACS+ settings, including enabling them on the appliance and setting passwords and IP addresses.

6. Elevated Privileges

• Allows setting privileges for specific users or groups to execute commands. This involves uploading sudoers settings and managing configurations.

7. Network Configuration

• Handle network interfaces, including adding, editing, and deleting interfaces and virtual interfaces. Set up duplex settings and policy-based routing (PBR).

8. Syslog-NG

• Set up Syslog-NG for log management. Configure options, sources, filters, destinations, and targets to manage log messages efficiently.

Key Components and Actions

• Sync Network Interface: Synchronize network interface configurations between the IPAM and remote systems.

• Routing Tables: Manage appliance routing tables, including adding, editing, and deleting tables.

• Syslog-NG Options: Customize Syslog-NG behavior, like message size, timestamps, and connection handling.

• Source and Filter Management: Define sources for log messages and set up filters to classify these messages.

Conclusion

This intricate process ensures a comprehensive setup of an IPAM appliance, covering all essential aspects from basic network settings to advanced monitoring and log management. It’s important to proceed with each step carefully, as these settings are crucial for the efficient management of network resources, especially in large and complex network environments.

IPv4 IPAM Appliance Defaults

The IPAM Appliance Defaults page serves as a comprehensive interface for configuring default settings for new IPAM (IP Address Management) appliances. These settings are crucial for ensuring consistent configuration across multiple appliances. Below is a detailed breakdown of each section:

1. Banner Configuration:

   • Appliance Type: Users select the type of appliance from a provided dropdown list.

   • Banner Color: Users choose a banner color from the dropdown list.

   • Banner Title: Users enter a title for the banner, adding a personalized touch.

2. NTP (Network Time Protocol) and DNS Resolver Configuration:

   • NTP Configuration: - Number of NTP Servers: Users select the number of NTP servers to synchronize with from a dropdown list. - NTP Servers: Users specify the IPv4 address of each NTP server (e.g., 172.16.0.35).

   • Upstream Authentication: For authenticating with NTP servers, users need to enable this option and provide the server’s IPv4 address, a key, and a SHA1.

   • Downstream Authentication: This option enables the appliance to serve as an NTP server for other devices. Users can either auto-generate or define a unique NTP key and SHA1, which is then displayed in a grid.

   • DNS Resolver Configuration: - Name Servers: Users enter the IPv4 address of DNS servers (e.g., 172.16.0.35). - Search Suffixes: Users input valid domain names for DNS searches (e.g., abc.com).

3. SNMP (Simple Network Management Protocol) Configuration:

   • General SNMP Settings: Users configure if SNMP traps are sent to third parties, specifying trap sink IP addresses, community strings, system location, and contact details.

   • Process Monitoring: Users select either to monitor all processes or only specific ones identified by checkboxes.

   • SNMPv3 Configuration: Users can add SNMPv3 users, specifying usernames, passwords, authentication protocols, and encryption protocols.

4. PAM (Pluggable Authentication Module) Settings:

   • LDAP and TACACS+ Settings: - LDAP: Users can enable LDAP authentication for the appliance. - TACACS+: Users enable TACACS+ authentication, enter a pass key, and confirm it. They also provide IPv4 addresses for up to four TACACS+ servers.

5. Password and Monitoring Settings:

   • Root Password Settings: Users set and confirm a root password.

   • iDRAC Monitoring Settings: If iDRAC monitoring is necessary, users enable it, input the IPv4 address, SNMP community string, and set a password.

6. Elevated Privileges Configuration:

   • Sudoers File: For users with FADM access, this tab enables the simultaneous update of sudoers configurations across all IPv4 IPAM appliances. Users can upload a sudoers file, preview its content, edit it, and save changes. Additionally, they can view, export, or match the current configuration with the existing one.

7. Syslog-NG Configuration:

   • Options: Users set parameters like time to reopen connections, message buffering, log message size, and timestamp settings.

   • Sources: Define the sources of log messages, such as internal syslog-ng messages, system-specific messages, or from text files.

   • Filters: Configure filters based on conditions like facility, priority, host, IP, and more.

   • Destinations: Specify destinations for the logs, like files, named pipes, local users, or all logged-in users.

   • Targets: Create targets by combining sources, filters, and destinations to route specific logs efficiently.

Overall, these settings allow for detailed customization of IPAM appliances, catering to various needs like network time synchronization, DNS resolving, process monitoring, authentication, and comprehensive logging through Syslog-NG.

IPv6 IPAM Appliance Defaults

The IPv6 IPAM (IP Address Management) appliance defaults page is specifically designed for setting up default configurations for new IPv6 IPAM appliances. These configurations cover various aspects, including banner settings, NTP and DNS resolver configurations, SNMP settings, authentication options, and iDRAC monitoring. Here’s a detailed breakdown:

1. Banner Configuration:

   • Appliance Type: Users select the type of appliance from a dropdown menu.

   • Banner Color: Users choose a color for the appliance banner.

   • Banner Title: Users input a title for the banner.

2. NTP (Network Time Protocol) and DNS Resolver Configuration:

   • NTP Configuration: - Number of NTP Servers: Users select the number of NTP servers from a dropdown list. - NTP Servers: Users enter the IPv6 addresses of NTP servers (e.g., 5000::2).

   • Upstream Authentication: For authentication with the NTP server, users need to provide the server’s IPv6 address, key, and SHA1.

   • Downstream Authentication: To authenticate the current appliance as an NTP server for other appliances, users can generate an NTP Key and SHA1, either automatically or by entering a user-defined key.

   • DNS Resolver Configuration: - Name Servers: Users enter the IPv6 addresses of DNS servers (e.g., 5000::14). - Search Suffixes: Users input valid domain names (e.g., abc.com).

3. SNMP (Simple Network Management Protocol) Configuration:

   • General SNMP Settings: Configure SNMP traps, including specifying trap sink IPv6 addresses, community strings, system location, and contact information.

   • Process Monitoring: Users select whether to monitor all processes or specific ones through checkboxes.

   • SNMPv3 Configuration: - Adding SNMPv3 Users: Users enter the username and passwords for SNMPv3 authentication and select appropriate authentication and encryption protocols.

4. PAM (Pluggable Authentication Module) Settings:

   • LDAP and TACACS+ Settings: - LDAP: Enable LDAP authentication on the appliance. - TACACS+: Enable TACACS+ authentication, providing passkeys and the IPv6 addresses of TACACS+ servers.

5. Root and iDRAC Password Settings:

   • Root Password: Set and confirm the root password for the appliance.

   • iDRAC Monitoring Settings: If iDRAC monitoring is needed, enable it and provide the necessary IPv6 address and SNMP community strings along with a password.

These settings ensure that a new IPv6 IPAM appliance can be configured quickly with predefined defaults, streamlining the setup process and ensuring consistency across deployments. Users have the flexibility to define how the appliance interacts with NTP servers, manages DNS resolutions, handles SNMP communications and authentication, and monitors system processes. The integration of LDAP and TACACS+ enhances security, and iDRAC support provides remote management capabilities.

Cloud Management

AWS AMI Management

What is an AWS AMI?

An Amazon Machine Image (AMI) is a template containing the software configuration required to launch a virtual server (instance) in the AWS EC2 environment. It includes the operating system, application server, and applications.

Integration with TCPWave IPAM:

TCPWave IPAM efficiently manages AMIs, crucial for launching instances in AWS through the Instance Provisioning Template. This template populates the list of available AMIs from AWS Images managed within TCPWave IPAM.

Operations in the AWS AMI Management Interface:

Users can perform key actions:

1. Add: Create a new AWS AMI entry.

2. Edit: Modify details of an existing AWS AMI.

3. Delete: Remove an unnecessary AWS AMI entry.

4. Bookmark: Mark an AWS AMI for future reference.

Detailed Process Description:

Adding an AWS AMI:

1. Navigate to the AWS AMI management section.

2. Select the option to add a new AMI, opening the creation page.

3. Enter necessary details, including the unique ID from AWS EC2.

4. Confirm details and save the new AMI record.

Editing an AWS AMI:

1. In the AWS AMI management section, choose the AMI to edit.

2. Modify necessary fields in the AMI’s record.

3. Save changes to update the AMI details.

Deleting an AWS AMI:

1. Select the AMI to delete from the list.

2. Confirm deletion, removing the selected AMI.

Bookmarking an AWS AMI:

1. Choose the AMI to bookmark.

2. Use the bookmark option for quick future access.

How to Add an AWS Image:

1. Accessing the AWS AMI Management Page: - Navigate: Network Management > Cloud Management > AWS AMI Management. - See existing AWS Images.

2. Initiating Addition of a New AWS Image: - Click the button for creating a new image, opening the ‘Create AWS Images’ page.

3. Completing AWS Image Details: - Fill fields under ‘AWS Image Details’:

   • Cloud Provider: Select from the dropdown.

   • Image Id: Enter the AMI Id.

   • Name: Assign a specific name.

   • Description: Provide a brief description.

4. Submitting AWS Image for Creation: - Click ‘OK’, confirm validation, and proceed.

5. Confirming the Addition: - Click ‘YES’ to add the AWS Image. - Message confirms successful addition.

6. Viewing Newly Added AWS Image: - Newly added AWS Image listed in the AWS Images grid.

By following these steps, seamlessly add a new AWS Image, ensuring your cloud management aligns with current AWS infrastructure needs.

AWS Instance Provisioning Template

What is an AWS Instance Provisioning Template?

The AWS Instance Provisioning Template in the IPAM system simplifies the creation of AWS Instances. Users can set up templates with predefined configurations, streamlining the process of creating multiple instances of a specified AWS type.

Key Functionalities of the AWS Instance Provisioning Template Interface:

1. Adding a Template: - Users can create a new AWS Instance Provisioning Template, specifying parameters for configuring and deploying AWS Instances.

2. Editing a Template: - Existing templates can be modified to adapt to changes in deployment requirements or instance specifications.

3. Deleting a Template: - Obsolete or no longer needed templates can be removed, maintaining an up-to-date template library.

4. Bookmarking a Template: - Users can bookmark frequently used templates for quick access, enhancing efficiency in recurrent deployments.

How These Operations Are Performed:

• Add:

  • Create a new template by selecting ‘Add,’ filling in necessary details, and saving it for future use.

• Edit:

  • Modify an existing template by selecting it from the list and making required changes.

• Delete:

  • Remove a template by choosing it and confirming deletion, irreversible with confirmation prompts.

• Bookmark:

  • Bookmark a template by selecting it for easier retrieval.

Practical Applications:

In real-world scenarios, templates streamline the process of deploying AWS Instances, saving time and reducing errors. Organizations can use predefined templates for recurrent deployments with specific configurations.

In conclusion, the AWS Instance Provisioning Template feature in IPAM is a powerful tool for managing AWS resources, offering a standardized, efficient, and error-reducing method for instance creation and management.

How to Add an AWS Instance Provisioning Template:

1. Starting the Process: - Navigate to Network Management > Cloud Management > AWS Instance Provisioning Template.

2. Initiating the Creation of a New Template: - Click on the option to create a new template, directing you to the ‘Create New’ page.

3. Filling in Basic Attributes: - Choose your cloud provider, enter a template name, select an AMI, choose the instance family, and select the instance type.

4. Specifying Additional Attributes: - Choose tenancy, set shutdown behavior, pick an IAM role, enter a key name, enable termination protection, and enable detailed monitoring.

5. Adding Notes: - Provide a description under the ‘Notes’ section.

6. Configuring Advanced Attributes: - Input any necessary user data for instance configuration or scripts during launch.

7. Setting Up Storage Options: - Under the ‘Storage’ tab, complete fields for device type, device, snapshot, volume type, size, delete on termination, and encryption.

8. Assigning Security Groups: - Under the ‘Security Groups’ tab, input VPC IDs for security groups.

9. Completing the Template Creation: - Click ‘OK’ to proceed. Confirm the addition with a validation message.

10. Viewing the Newly Added Template:

• The newly created template will be listed in the AWS Instance Provisioning Template grid.

11. Cancelling the Process:

• If needed, click ‘Cancel’ to stop the creation process.

By following these steps, efficiently create an AWS Instance Provisioning Template, simplifying and standardizing the process of launching AWS instances.

Azure Instance Provisioning Template

Overview of Azure Instance Provisioning Template:

The Azure Instance Provisioning Template within the IPAM system streamlines the creation of Azure Instances. Users can design configuration templates to efficiently create multiple Azure Instances with predefined settings, ensuring consistency and saving time.

Key Functionalities within the Azure Instance Provisioning Template Interface:

1. Add a Template: - Users can create a new template for Azure Instance creation, defining parameters like instance size, type, and network settings.

2. Edit an Existing Template: - Existing templates can be updated to adapt to changing deployment needs or updates in Azure services.

3. Delete a Template: - Remove templates that are no longer needed, maintaining an up-to-date and clutter-free template library.

4. Bookmark a Template: - Mark frequently used templates for quick access, enhancing efficiency in recurrent deployments.

Performing Operations on the Azure Instance Provisioning Template:

• Add:

  • Initiate the creation of a new template, input Azure-specific details, and configurations, saving the template for future deployments.

• Edit:

  • Modify a template by selecting it from the list and adjusting its settings based on new requirements or updates in Azure features.

• Delete:

  • Choose a template for deletion, confirm the action, and permanently remove the template from the system.

• Bookmark:

  • Easily bookmark a template for quick retrieval and repeated use, enhancing user convenience and efficiency.

Practical Application:

Templates significantly ease the process of deploying Azure Instances, saving time and reducing errors. Predefined templates ensure accuracy and consistency in deployments with specific configurations.

In summary, the Azure Instance Provisioning Template in the IPAM system is a critical tool for managing Azure resources, providing a standardized and efficient method for instance creation, enhancing operational efficiency, and ensuring consistency across deployments.

How to Add an Azure Instance Provisioning Template:

1. Accessing the Template Creation Page: - Navigate to Network Management > Cloud Management > Azure Instance Provisioning Template.

2. Initiating a New Template Creation: - Click the button for creating a new template, opening the ‘Create New Azure Instance Provisioning Template’ page.

3. Filling in Basic Attributes: - Select your cloud provider, enter a template name, choose an Azure region, disk type, VM size, and provide a description.

4. Specifying Virtual Machine Image Attributes: - Choose image publisher, offer, SKU, version, username, password/SSH public key, and public IP address assignment.

5. Confirming the Creation of the Template: - Click ‘OK,’ and confirm the creation with a validation message.

6. Completing or Cancelling the Process: - The newly created template will appear in the Azure Instance Provisioning Template grid. - To cancel the creation process, click ‘Cancel.’

By following these steps, efficiently create an Azure Instance Provisioning Template, streamlining the process of deploying Azure instances and ensuring consistency across multiple deployments.

Cloud Hosted Subnets

Definition: In TCPWave IPAM, a “Cloud Hosted Subnet” refers to a subnet associated with a cloud service provider like AWS, Google Cloud, or Azure.

Importing from Cloud

Purpose: This feature imports virtual instances from a specific cloud-hosted subnet into TCPWave IPAM, managing them as objects.

Automatic Import Job: A scheduled job, “Auto Cloud Import,” automatically imports instances from the cloud. The process includes: 1. Selecting subnets listed in the ‘Cloud Hosted Subnets’ section. 2. Performing the import based on a predefined schedule.

Requirement for Operation: To enable automatic import, set the “Enable Auto Cloud Import” global option to True.

Interface Operations

Several tasks can be performed through the interface:

1. Viewing: Access and view details of cloud-hosted subnets.

2. Enabling: Activate cloud-hosted subnets for auto-import.

3. Disabling: Turn off the auto-import feature for specific subnets.

Detailed Steps for Various Operations

Viewing Cloud Hosted Subnets

To view cloud-hosted subnets:

1. Navigate to Network Management > Cloud Management > Cloud Hosted Subnets.

2. Select an organization from the dropdown menu to view associated cloud-hosted subnets.

Enabling Cloud Hosted Subnets

By default, both newly created and existing subnets with a Cloud Provider are set for Auto Cloud Import.

To enable a cloud-hosted subnet:

1. Select the desired subnet from the cloud-hosted subnets grid.

2. Click ‘Update.’ You’ll receive a confirmation message, “Cloud hosted subnets have been updated successfully.”

Disabling Cloud Hosted Subnets

If you wish to stop auto-import for a subnet:

1. Deselect the subnet from the cloud-hosted subnets grid.

2. Click ‘Update.’ A confirmation message, “Cloud hosted subnets have been updated successfully,” indicates the change.

These features in TCPWave IPAM enable efficient management of cloud-hosted subnets, automating processes for importing and managing virtual instances within these subnets.

Google Instance Provisioning Template

Overview: The Google Instance Provisioning Template is a feature in TCPWave IPAM designed for creating Google Compute Engine (GCE) Instances. It streamlines the deployment process and allows for reusability, making it convenient for users.

Interface Operations: Users can perform various actions within this interface:

1. Add: Create a new Google Instance Provisioning Template.

2. Edit: Modify an existing template.

3. Delete: Remove a template that is no longer needed.

4. Bookmark: Mark a template for easy access in the future.

How to Add a Google Instance Provisioning Template: 1. Access the Template Page:

• Navigate to Network Management > Cloud Management > Google Instance Provisioning Template.

2. Start the Creation Process: - Click on the option to create a new template.

3. Fill in Basic Attributes: - Cloud: Select the desired cloud from the dropdown menu. - Template Name: Enter a unique name. - Google Cloud Zone: Choose from available zones. - Google Machine Type: Select the machine type based on the zone. - Description: Provide a description for the template.

4. Configure Boot Disk Attributes: - Image Families: Choose an image family. - Image: Select a boot disk image within the family. - Non-Deprecated: Filter non-deprecated images. - Boot Disk Types: Choose from available types. - Disk Size: Specify the boot disk size. - Delete boot disk when instance deleted: Check to delete the disk with the instance. - SSH Public Keys: Enter SSH public keys. - Allow HTTP traffic: Toggle HTTP traffic access. - Allow HTTPS traffic: Toggle HTTPS traffic access.

5. Finalize the Template Creation: - Click ‘OK’ to proceed. Confirm the addition.

6. Complete or Cancel the Process: - The new template appears in the grid. Click ‘Cancel’ to abort if needed.

How to Edit a Google Instance Provisioning Template: 1. Access the Template for Editing:

• Navigate to Network Management > Cloud Management > Google Instance Provisioning Template.

2. Initiate the Edit Process: - Select the template to edit.

3. Update Basic Attributes: - Modify cloud, name, zone, machine type, and description.

4. Modify Boot Disk Attributes: - Update image family, image, types, size, and other settings.

5. Confirming the Changes: - Click ‘OK’ to apply changes. Confirm the update.

6. Final Steps or Cancellation: - The updated template is listed. Click ‘Cancel’ to abort.

Viewing Records: - Number Drop-Down: Select and view a specific number of records in the grid.

Role-Based Access: - Permission Dependency: Access depends on assigned permissions. Check ‘Administrator Roles’ for details.

Deleting a Google Instance Provisioning Template: 1. Select a template from the grid. 2. Click on ‘Delete’ and confirm.

Bookmarking a Google Instance Provisioning Template: 1. Choose a template from the grid. 2. Click on ‘Bookmark’ to add it.

Using the Context Menu: 1. Right-click on a record in the grid. 2. Access options to Edit, Delete, or Bookmark the selected template.

The Google Instance Provisioning Template feature in TCPWave IPAM offers a streamlined approach for managing GCE Instances, enhancing user experience and efficiency.

Provider Credentials Management

Overview: Provider Credentials in TCPWave IPAM are crucial for facilitating interaction with various cloud services. They are specific to each supported cloud provider, including AWS, Akamai, Google, Azure, Cloudflare, DynDNS, Neustar, and NS1.

Interface Operations: Users can perform key actions within this interface:

1. Add: Create new provider credentials.

2. Edit: Modify existing provider credentials.

3. Delete: Remove provider credentials no longer needed.

4. Bookmark: Mark certain credentials for quick access later.

Additional Functionalities: - Refer to the ‘Common Functionalities’ section for options like Refresh, Column Visibility, Reset Preferences, and More. - Number Drop-Down: Select how many records to view at once.

Role-Based Access: - Availability depends on assigned permissions. Check ‘Administrator Roles’ for details.

Managing Provider Credentials:

Adding Provider Credentials: 1. Accessing the Creation Page:

• Click the relevant button to open the ‘Create Provider Credentials’ page with ‘Provider Details’ and ‘Resource Role Mapping’ tabs.

2. Provider Details Section: - Select the organization. - Choose ‘Provider Type’ (AWS, Akamai, Google, Azure, Cloudflare, DynDNS, Neustar, or NS1). - Fill in provider-specific details based on the chosen type. - Confirm by clicking ‘OK’ and ‘YES’ on the validation message.

3. Adding Resource-Role Mapping (For AWS): - Go to the ‘Resource Role Mapping’ tab. - Open the Resource Role Mapping window. - Choose ‘Resource Type’ (e.g., Zone or VPC for AWS). - Enter Resource Name, Account Number, and IAM Role. - Confirm with ‘OK’.

4. Completing or Canceling: - A confirmation message appears upon completion. - Click ‘Cancel’ to abort the creation process.

Editing and Deleting Resource-Role Mapping:

• Select a mapping record, use Edit or Delete as required.

• Confirm changes with ‘OK’ or remove the record.

Associating a Zone Template:

• After adding a cloud provider, associate a zone template in ‘DNS Management > DNS Zone Templates’.

• Link it to the cloud provider under ‘Cloud DNS Providers’ tab.

Importing Cloud DNS Resource Records (RR):

• When adding an existing zone, enable ‘import cloud DNS RRs’ to import records to IPAM.

Deleting Provider Credentials: 1. Select the credential to delete from the grid. 2. Click ‘Delete’. Confirm with ‘YES’.

Associating TSIG Key with Cloud Provider: 1. Right-click on a provider credential record. 2. Select ‘TSIG Key’. 3. Choose ‘Provider Name’ and ‘TSIG Key Name’. 4. Click ‘Update’ and confirm.

Bookmarking Provider Credentials: 1. Choose a credential from the grid. 2. Click ‘Bookmark’. Confirm bookmarking.

Accessing the Context Menu: 1. Right-click on a record to view options like Edit, Delete, TSIG Key, and Bookmark.

In summary, managing Provider Credentials in TCPWave IPAM involves adding, editing, deleting, and bookmarking credentials for various cloud providers. This management is essential for effective interaction with cloud services, ensuring secure and efficient cloud network operations.