Admin Hierarchy Diagram

Admin Hierarchy Structure

TCPWave IPAM provides a structured interface to view and manage the administrative hierarchy. Accessible via the login drop-down, this interface displays key elements of the admin structure:

  1. Administrator: Individual users who manage and operate the system.

  2. Administrator Group: A collection of administrators grouped based on certain criteria or functions.

  3. Administrator Role: Specific roles assigned to administrators, encompassing a set of predefined functions.

  4. Functions: The specific tasks or operations that administrators can perform.

Administrator Roles

Purpose: Assign a set of predefined functions to one or more administrator groups. Functionality: Enables efficient and role-specific task management within the administrative structure.

Administrator Groups

Role: Group administrators together for organized management. Benefit: Simplifies the process of assigning permissions and roles to multiple administrators.

Administrator Permissions

TCPWave IPAM allows flexible assignment of permissions at two levels:

  1. Administrators: Individual users managing specific system aspects.

  2. Administrator Groups: Groups containing multiple administrators.

Types of Privileges

Administrators and groups can be granted the following privileges:

  1. Read: - Permission to view and search for records. - Ideal for oversight and monitoring without allowing modifications.

  2. Write: - Allows full access including adding, modifying, deleting, viewing, and searching records. - Suitable for administrators responsible for system changes and updates.

  3. Deny: - Restricts administrators/groups from adding, modifying, deleting, or even viewing records. - Used to safeguard critical system parts or restrict access based on role requirements.

Summary

The admin hierarchy in TCPWave IPAM is designed for clear and efficient management of users and roles. By delineating administrators into specific roles and groups, and assigning appropriate permissions, the system ensures a secure, organized, and effective administrative structure tailored to the unique operational needs of the organization.

Asset Management

Purpose

TCPWave Asset Management is designed to enhance an organization’s understanding and oversight of its assets throughout their lifecycle. This includes assessing asset needs, monitoring performance, and managing the stages of asset life. It’s particularly useful for tracking hardware assets, aiding in efficient license management, and providing insights through various reports related to usage, warranties, maintenance, and expiry.

Key Functionalities

Within the Asset Management interface, the following operations can be performed:

  1. Add Assets: Introduce new assets into the system. This could include entering details about new hardware pieces or software licenses acquired by the organization.

  2. Edit Assets: Update information on existing assets. This is useful for reflecting changes in asset status, location, user assignment, etc.

  3. Delete Assets: Remove assets from the system that are no longer in use or part of the organization’s inventory. This helps keep the asset database current and accurate.

  4. Bookmark Assets: Mark specific assets for easy and quick access in the future. This feature is beneficial for frequently referenced or high-priority assets.

  5. Import Assets: Bulk upload asset data, typically from a spreadsheet or a similar format. This is an efficient way to add multiple assets to the system at once, saving time and reducing manual entry errors.

Usage Scenarios

  • License Management: Avoid purchasing unnecessary licenses by having a clear view of existing software assets.

  • Hardware Utilization Reports: Gain insights into how hardware assets are being used within the organization.

  • Warranty Tracking: Keep track of warranty periods to manage repairs and replacements effectively.

  • Maintenance Scheduling: Schedule and track maintenance activities to prolong asset life and ensure optimal performance.

  • Expiry Alerts: Receive notifications about asset expiry, ensuring timely renewal or decommissioning.

Conclusion

TCPWave Asset Management offers a comprehensive solution for tracking and managing an organization’s assets. By leveraging these tools, businesses can make informed decisions about asset procurement, usage, and maintenance, ultimately leading to cost savings and enhanced efficiency.

Adding an Asset in TCPWave Asset Management Overview

TCPWave’s Asset Management system allows organizations to track and manage their hardware assets efficiently. This includes monitoring asset performance, managing inventory, and generating reports on usage, warranty, maintenance, and expiration. Here’s how to add a new asset:

Steps to Add an Asset

  1. Navigation:

    • Go to Administration >> Asset Management.

    • The system will display the Assets >> Create Asset page.

  2. Entering Asset Attributes:

    • Service Tag: Input the asset’s service tag.

    • Serial Number: Enter the asset’s unique serial number (Mandatory).

    • Vendor: Specify the vendor’s name.

    • Name: Provide the name of the asset.

    • Model: State the model of the asset.

    • Acquisition Type: Indicate how the asset was acquired.

    • CPU: Enter the number of CPU cores.

    • Capacity: Specify the asset’s capacity.

    • OS Version: Indicate the supported operating system version.

    • Maintenance Cost: Enter the cost of maintaining the asset.

    • Purchase Cost: Specify the purchase cost.

    • Purchase Date: Record the date of purchase.

    • Warranty-End-Date: State the warranty’s expiration date.

    • Disposal-Date: If applicable, enter the date of disposal.

    • Disposal-Reason: Provide the reason for disposal.

    • City: Enter the city where the asset is located.

    • Green-Zone: Check if the asset is in a green zone.

    • Description: Add a brief description of the asset.

  3. Confirmation:

    • Click OK. A prompt will appear for confirmation: “Are you sure you want to add the asset? Click Yes to proceed.”

    • Click YES. A message will confirm the successful creation of the asset: “Asset has been created successfully”.

Result

The new asset will now appear in the Asset Management grid. This grid features search functionality and sortable column headers for easy navigation and management.

Importance

Adding assets in TCPWave Asset Management ensures a comprehensive overview of hardware resources, facilitating informed decision-making regarding asset utilization, maintenance, and lifecycle management.

Contact Management

Purpose

The TCPWave Contact Management system is designed to store and organize contact information crucial for managing network services. This includes details of application owners, system administrators, database administrators, network personnel, shift supervisors, and support teams. The system plays a vital role in ensuring quick and effective communication during system outages or critical escalations affecting network operations.

Key Functionalities

  1. Add Contacts: Introduce new contact entries into the system.

  2. Edit Contacts: Update existing contact information as required.

  3. Delete Contacts: Remove outdated or unnecessary contact details.

  4. Bookmark Contacts: Mark frequently referenced contacts for quick access.

  5. Import Contacts: Bulk upload contact information from external sources.

Use Cases

  • System Outages: Quickly reach relevant personnel or support teams during network disruptions.

  • Escalation Processes: Facilitate swift escalation by having easy access to contact information of key stakeholders.

  • Network Management: Enhance communication channels for routine and emergency network service management.

How It Works

  • Navigate to the Contact Management interface within the TCPWave system.

  • Perform the desired operation (Add, Edit, Delete, Bookmark, or Import) using the user-friendly interface.

  • Maintain an organized database of contacts relevant to various network services and responsibilities.

Importance

In dynamic IT environments, having a centralized, accessible, and up-to-date contact database is invaluable. It ensures that communication lines are always open and efficient, especially in situations where timely response is crucial.

By leveraging TCPWave’s Contact Management system, organizations can significantly improve their network service management and response times to critical issues, thereby maintaining high operational standards.

Adding a Contact in TCPWave Contact Management

Overview

TCPWave’s Contact Management system is designed to store and organize key contact details for various personnel, such as application owners, system administrators, network personnel, and support teams. This system is particularly useful for quickly reaching out to the relevant contacts during system outages or escalations that affect critical network services.

Steps to Add a Contact

  1. Navigation:

    • Go to Administration >> Contact Management.

    • This action will open the Contacts >> Create Contact page.

  2. Filling in Contact Details:

    • Organization: Select the appropriate organization from the dropdown menu.

    • First Name: Enter the first name (up to 20 characters).

    • Middle Name: (Optional) Enter the middle name (up to 20 characters).

    • Last Name: Enter the last name (up to 20 characters).

    • Note: Organization, First Name, Last Name, and Email are mandatory fields.

    • Email: Provide the contact’s email address.

    • Phone Number: Input the contact’s phone number.

  3. Confirming Contact Addition:

    • Click OK. A message will ask for confirmation: “Are you sure you want to add the contact? Click Yes to proceed.”

    • Click YES. A confirmation message will then appear: “Contact has been created successfully.”

Result

The newly added contact will be listed in the Contact Management grid. This grid allows for easy searching and sorting of contact information.

Importance

Adding contacts in the TCPWave system ensures that all relevant personnel information is readily accessible. This functionality is crucial for effective communication and rapid response in the event of network issues, ensuring minimal disruption to mission-critical services.

Configuration Management

Audit Logging Configuration

Overview

  • Default Setting: Audit logging is enabled by default for all components.

  • Automatic Disabling: The system automatically disables audit logging for all components if the IPAM’s disk utilization exceeds 90%.

  • Undo Operations: When undoing actions, audit data is batch-processed with a 1-minute delay.

  • Access Control: Only users with FADM or SADM roles can modify audit logging settings.

Disabling Audit Logging

To turn off audit logging for specific components:

  1. Deselect Components: From the displayed grid, uncheck the boxes next to the components for which you want to disable logging.

  2. Confirmation Request: After deselection, click “OK”. A message will appear asking for confirmation: “Confirm that you want to update the audit logging configuration settings.”

  3. Finalize Changes: Click “YES” to confirm. A final message will confirm the successful modification of settings: “Audit Logging Configuration has been modified successfully.”

Enabling Audit Logging

To enable audit logging for specific components:

  1. Select Components: Choose the desired components by ticking their boxes in the grid.

  2. Confirmation Request: After selection, click “OK”. A validation message will prompt you to confirm the changes: “Confirm that you want to update the audit logging configuration settings.”

  3. Finalize Changes: Click “YES” to confirm. A message will then confirm that the audit logging configuration has been successfully updated: “Audit Logging Configuration has been updated successfully.” (Note: The original text erroneously states “deleted”; this should be “updated.”)

Central Logging

Overview

Splunk, a software tool, is used for big data analysis generated by machines. It offers a web interface for data search, monitoring, and analysis, generating real-time reports, graphs, and more. TCPWave IPAM supports two methods to transfer logs to a Splunk server: Splunk Forwarding and Splunk HTTP Event Collector (HEC).

Splunk Forwarding

  • Integration: TCPWave IPAM and remote appliances are integrated with Splunk forwarders for log transfers.

  • Configuration: Requires the Splunk server’s IP address and receiving port.

  • Default Setting: This feature is off by default.

  • Activation:

    • Enable by ticking the “Enable Splunk Forwarding” checkbox.

    • Enter Splunk Log Host: IP address of the Splunk server.

    • Enter Splunk Log Port: The configured receiving port on the Splunk server.

Splunk HTTP Event Collector (HEC)

  • Functionality: Splunk HEC receives data via HTTP/HTTPS for indexing and real-time analysis in Splunk.

  • Configuration:

    • Splunk server’s address

    • HTTP Port

    • HEC Token

  • Default Setting: Disabled by default.

  • Activation:

    • Enable by checking the “Send Logs to Splunk HEC” box.

    • Enter Splunk Log Host: IP address of the Splunk server.

    • Enter Splunk HTTP Port: The HTTP port configured on the Splunk server.

    • Enter Splunk HEC Token: The HEC token value set on the Splunk server.

Log Options

  • Enabling: Either or both logging methods can be enabled simultaneously.

  • Selection: Choose required logs from the grid to send to the Splunk server.

  • Additional Configuration: Enable Central Logging on individual DNS/DHCP appliances to transfer logs. IPAM Logs require no extra settings.

IPAM Logs

Logs that can be sent from the IPAM Appliance include:

  • TIMS Log

  • Audit Log

  • Messages Log

  • System Log

  • Data Engine Log

  • CLI Engine Log

  • TCPWave Scheduler Log

  • Discovery Engine Log

  • High Availability Log

  • DDNS Log

DNS Logs

Logs that can be sent from the DNS Appliance include:

  • DNS Log

  • Query Log

  • DNS Task Log

  • DNS Messages Log

  • System Log

  • NSD Log

  • TWCDNS Log

  • RPZ Log

  • DDNS Log

DHCP Logs

Logs that can be sent from the DHCP Appliance include:

  • DHCP Task Log

  • DHCP Messages Log

  • System Log

Sending Logs to Splunk Server

  • Select Logs: Choose logs from IPAM/DNS/DHCP appliances.

  • Confirmation: Click OK, then confirm by clicking YES on the prompt: “Confirm that you want to update the centralized logging configuration settings.”

  • Success Message: A confirmation message displays: “Central Logging Configuration has been modified successfully.”

This detailed guide provides clarity on setting up central logging with Splunk in the TCPWave IPAM system, including the types of logs that can be sent and the steps for configuring Splunk Forwarding and Splunk HEC.

Extended Attribute Management

Overview

Extended attributes in TCPWave IPAM allow for the customization of various entities with user-defined properties. Supported entities for extension include Network, Subnet, Object, Admin, Zone, Reverse Zone, and Resource Record.

Access Control

  • Role-Based Access: The availability of this section depends on the permissions associated with your user role.

  • Role Information: To understand your assigned role and permissions, go to Administrator Roles.

Operations

You can perform three key operations:

  1. Add

  2. Edit

  3. Delete

For additional functionalities like Refresh, Column Visibility, Reset Preferences, and More options, see the Common Functionalities section.

Adding Extended Attributes

To create a new extended attribute:

  1. Navigation: Go to Administration >> Configuration Management >> Extended Attribute Management.

  2. Create Attribute: Click the ‘Create’ button. A pop-up for creating a new extension appears.

  3. Configuration:

    • Attribute Name: Enter the name under the ‘Attribute’ field.

    • Type: Choose from String, Numeric, Date, IP Address, List, or Regular Expression.

    • Mandatory: Select Yes or No to indicate if the attribute is mandatory.

    • Description: Provide a description for the attribute.

    • Show on Grid: Check this box if you want the attribute to be displayed in the management grid.

  4. Confirmation: Click OK. A message confirms successful creation: “Extension has been created successfully”.

Editing Extended Attributes

To modify an existing extended attribute:

  1. Select Record: Choose the attribute from the grid to enable the Edit and Delete options.

  2. Edit Attribute: Click the ‘Edit’ button. An ‘Update Extensions’ pop-up appears.

  3. Make Changes: Edit fields such as Attribute Name, Type, Mandatory status, and Description.

  4. Confirmation: Click OK. A message confirms successful updating: “Extension has been updated successfully”.

Deleting Extended Attributes

To remove an extended attribute:

  1. Select Record: Choose the attribute from the grid.

  2. Delete: Click the ‘Delete’ button. A validation message asks for confirmation.

    • Delete References: If applicable, select ‘Delete all extension references’.

  3. Confirm Deletion: Click YES. A confirmation message appears: “Extension has been deleted successfully.”

Context Menu

For additional options:

  1. Right-Click: Right-click on a record in the Extended Attribute Management grid.

  2. Options: The context menu offers Edit and Delete options, mirroring the functionality described in the sections above.

Global Policy Management

Overview

The Global Options in TCPWave IPAM are pivotal for configuring overarching settings that impact the functioning of IPAM, DNS, and DHCP services. These options, categorized for ease of navigation, play a significant role in network infrastructure management. Due to their substantial influence on system behavior, managing these options is typically reserved for users with Super Administrator (SADM) or Functional Administrator (FADM) roles.

Key Guidelines

  • Change Management: Implement changes in a test environment first to prevent disruptions in live network operations.

  • Expert Advice: For complex configurations, consult with TCPWave Technical Support or Professional Services.

  • Role-Based Access: Adjustments to Global Options are limited to users with SADM or FADM privileges.

Categories and Options

  1. Appliance Configuration - Maximum Open Files: Sets the system’s limit on open files, critical for resource allocation. - OS Buffer Sizes: Dictates data transfer buffer sizes, influencing network service performance. - Listen Queue Size: Defines backend socket capacity, affecting incoming connection handling. - OS Swappiness: Manages memory page swapping to disk, impacting performance under heavy load. - Maximum Shared Memory Segment Size: Limits memory allocation for processes, important for resource-intensive operations.

  2. Bookmarks - Maximum Allowed Bookmarks: Restricts user-created bookmarks, aiding in interface organization.

  3. Cloud Configuration - Options for managing cloud instances, including object deletion handling, API request retries, and auto-import features.

  4. Dashboard and Database - License Warnings: Alerts about license usage and expiry. - Database Connection Pooling: Manages database connectivity and performance settings.

  5. DHCP and DNS - Settings for DHCP lease times, dynamic updates, DNS security, and performance tuning.

  6. Discovery - Controls for network auto-discovery processes, including timeout settings and alert configurations.

  7. Security Configuration - Configurations for authentication methods (LDAP, RADIUS, Kerberos, SAML) and access control, including user session management.

  8. SMTP and SNMP - Email Notifications: Settings for email alert configurations. - SNMP Polling: Manages SNMP response and retry settings for network device monitoring.

Best Practices

  • Documentation: Record all changes for accountability and future reference.

  • Incremental Implementation: Apply and evaluate changes step by step; revert if necessary.

  • Collaboration: Involve relevant stakeholders in decision-making processes.

  • Regular Review: Continuously reassess Global Options to align with evolving organizational needs and policies.

In summary, the management of TCPWave Global Options is a critical aspect of network administration, requiring careful consideration, expert consultation, and thorough documentation to optimize performance and maintain security within the IPAM system.

IPV4 License Management

Overview

License management in TCPWave IPAM is crucial for maintaining the validity and functionality of the system. The type of license purchased determines the maximum number of IPs that can be managed and the duration of the license’s validity.

License Update

License updates are necessary when a license has expired or is nearing its expiration. An expired license will trigger a system alert stating, “Product License Expired. Please contact support.”

Steps to Update the License:

  1. Navigation: Go to Administration >> Configuration Management >> License Management.

  2. Accessing the Update Interface: Click on License to open the Update License pop-up.

  3. Entering the License Key: Input the new license key into the provided field.

  4. Finalizing the Update: Click OK to complete the process. A confirmation message, “License has been updated successfully with total number of days,” will appear.

Note:

  • If a remote appliance serves as both DNS and DHCP or ADC, updating its license also updates the license for the other service.

  • When timsdns or timsdhcp services fail due to an invalid license, they will wait for an update from IPAM, allowing for remote appliance license updates even without active heartbeats.

IPAM Grid Details

The License Management grid provides detailed information, with columns like:

  • Appliance Name: Identifier of the appliance.

  • Appliance IP: Associated IP address.

  • License Validity: Duration of the license’s validity.

  • Date of Expiry: Specific expiration date of the license.

  • Licensed IP: IP address for which the license is issued.

  • Licensed Service Tag: Unique identifier for the licensed service.

  • Major/Minor Version: Software or firmware version.

  • Customer Name/ID: Owning customer’s details.

  • Maximum IPs: Maximum manageable IP addresses.

  • HA License: Indicates High Availability license status.

  • ADC Themis License: Status of ADC Themis license.

  • Chatbot License: Indicates a license for chatbot functionality.

  • DNS Titan End User Security: Details about DNS Titan security.

  • DNS Titan Security Expiry/Type: Expiry date and type of DNS Titan security.

DNS/DHCP/ADC Grid Details

Similarly, this grid includes details like appliance name, IP, license validity, expiry date, and more, specific to DNS, DHCP, or ADC appliances.

Context Menu

  • To access additional options, right-click on a record in the grid.

  • The context menu, including the option to Update License, will be displayed.

This structured approach to License Management in TCPWave IPAM ensures that all appliances are kept up-to-date with valid licenses, maintaining the system’s operational integrity.

Organizations

Overview

In TCPWave IPAM, the ‘Organization’ feature is essential for managing Users and Networks. Each organization can be linked with multiple networks and has the option to enable or disable the root zone.

Key Operations

  1. Adding Organizations: Create new organizational records.

  2. Editing Organizations: Modify existing organizational details.

  3. Deleting Organizations: Remove organizations from the system.

  4. Bookmarking Organizations: Bookmark organizations for quick access.

Adding an Organization in TCPWave IPAM

Overview

In TCPWave IPAM, organizations are fundamental entities used to group and manage users and networks. Each organization can be linked to multiple networks. Additionally, you have the option to enable or disable the creation of a root zone within an organization.

Steps to Add an Organization

  1. Navigation: Go to Administration >> Configuration Management. The Organizations page should be the default view.

  2. Initiating Creation: Click the appropriate button to begin the process of adding a new organization. This action opens the ‘Create Organization’ page.

  3. Filling in Organization Details:

    • Name: Enter the organization’s name. This is a mandatory field.

    • Root Zone: - Check the box if you want to enable the creation of a root zone in the organization. The DNS root zone is the highest-level DNS zone in the Internet’s Domain Name System (DNS) hierarchy.

    • Description: Provide a brief description of the organization.

  4. Confirmation Process:

    • After entering details, click OK.

    • A prompt will appear: “Are you sure you want to add the organization? Click Yes to proceed.”

    • Click YES to confirm.

  5. Completion:

    • Upon confirmation, a message will display: “Organization has been created successfully.”

Post-Addition Details

  • The new organization will now be visible in the Organizations grid, equipped with search and sortable column headers.

  • In the “Root Zone” column: - A green tick (equivalent to 1) indicates that root zone creation is enabled for the organization. - A red tick (equivalent to 0) signifies that root zone creation is disabled.

Key Notes

  • This process is subject to the permissions associated with your user role. Refer to “Administrator Roles” for more details on your permissions.

  • The interface may also provide options for refreshing, adjusting column visibility, resetting preferences, and accessing more options as part of its common functionalities.

By following these steps, you can successfully add an organization to the TCPWave IPAM, tailoring it to your network management needs by configuring root zone settings and providing relevant details.

Grid Features

  • Number Dropdown: Allows selecting the number of records to view.

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

Role-Based Access

  • Access to these functionalities depends on the permissions of your user role. To understand your role permissions, navigate to Administrator Roles.

Deleting Organizations

  • Selecting: Choose an organization record from the grid. Edit, Delete, and Bookmark icons will be enabled.

  • Initiating Deletion: Click the delete icon. A message will appear for confirmation: “Are you sure you want to delete the selected Organization(s)? Click Yes to proceed.”

  • Confirming Deletion: Click YES. A confirmation message will display: “Organization has been deleted successfully.”

  • Precondition: If the organization has associated domains, locations, contacts, networks, templates, etc., these must be deleted before the organization can be removed.

Bookmarking Organizations

  • Selecting: Choose an organization from the grid. Edit, Delete, and Bookmark options become available.

  • Adding Bookmark: Click the bookmark icon. A confirmation message appears: “Bookmark has been added successfully.”

Context Menu

  • Accessing: Right-click on an organization record to open the context menu.

  • Options: - Edit: Modify selected organization. - Delete: Remove the organization. - Enable/Disable Root Zone: Toggle the root zone status for the organization. - Add Bookmark: Bookmark the organization.

Summary

The Organizations interface in TCPWave IPAM is a comprehensive tool for managing organizational entities related to users and networks. It includes capabilities for adding, editing, deleting, and bookmarking organizations, along with the ability to enable or disable root zones. This section’s accessibility is based on user roles, ensuring secure and appropriate management within the IPAM environment.

Object Types

Overview

In TCPWave IPAM, object types are essential for classifying network entities. They help categorize IP addresses into distinct groups, like network objects (single IP or subnet) or service objects (TCP/UDP ports, protocols). Users can utilize predefined object types or create custom ones.

Managing Object Types

From the Object Type interface, you can:

  1. Add New Object Types: Create custom categories for network entities.

  2. Edit Existing Object Types: Modify details of existing categories.

  3. Delete Object Types: Remove unused or redundant categories.

  4. Bookmark Object Types: Save frequently used types for quick access.

Adding an Object Type in TCPWave IPAM

Overview

Creating an Object Type in TCPWave IPAM involves defining a new category for organizing network entities. This process allows you to customize how network objects are classified, enhancing the system’s adaptability to specific network management needs.

Steps to Add an Object Type

  1. Navigation: - Go to Administration >> Configuration Management >> Object Types. - The Object Types management page will be displayed.

  2. Initiate Object Type Creation: - Click on the designated button to access the Create Object Type page.

  3. Entering Basic Attributes: - Object Type: Input the name for the new object type. - Auto-generation Prompt: Upon entering the object type, a message asks if you want to auto-generate prefix and suffix strings based on the object type. Click Yes to enable this feature, and the system will automatically fill in the prefix and suffix fields. - Description: Provide a brief overview of the object type. - Prefix and Suffix: Enter or review auto-generated values for these fields. - Zeros as Prefix: Choose Yes or No to decide if zeros should be used as a prefix in the initial sequence number. - Initial Sequence Number: Set the starting number for objects of this type. - Object Type Logo: Upload or select a logo to represent this object type.

  4. Confirm Addition: - Click OK to proceed. A validation message prompts for confirmation: “Are you sure you want to add the object type? Click Yes to proceed.”

  5. Finalize Addition: - Click YES. A confirmation message will display: “Object Type has been added successfully.”

Key Points

  • Customization: The auto-generation of prefix and suffix based on the object type name simplifies the process and ensures consistency.

  • Flexibility: The ability to set a prefix for the initial sequence number offers flexibility in numbering objects.

  • Visual Identification: Associating a logo with an object type aids in quick identification within the system.

Using the Interface

  • Number Dropdown: Select the desired number to view corresponding records.

  • Common Functionalities: Access features like Refresh, Column Visibility, and Reset Preferences for user convenience.

Permissions

  • Role-Based Access: Access to this section depends on user role permissions. Check your permissions under “Administrator Roles”.

Adding Object Type

To add an Object Type:

  1. Navigation: Go to Administration >> Configuration Management. The system displays the Object Type page.

  2. Initiate Addition: Click the addition icon to open the “Create Object Type” page.

  3. Input Details: - Name: Mandatory field. Enter the object type name. - Description: Provide a brief description.

  4. Confirm Addition: Click OK and then confirm with YES when prompted.

  5. Completion: A message confirms successful creation: “Organization has been created successfully.”

Editing Object Type

To edit an Object Type:

  1. Select Object Type: Choose an object type from the grid.

  2. Initiate Editing: Click the edit icon. Modify the required fields.

  3. Save Changes: Click OK and confirm the changes.

Deleting Object Type

To delete an Object Type:

  1. Select for Deletion: Choose the object type from the grid.

  2. Initiate Deletion: Click the delete icon. Confirm the action when prompted.

  3. Completion: A confirmation message appears upon successful deletion.

Bookmarking Object Type** ** To bookmark an Object Type:

  1. Select to Bookmark: Choose the desired object type from the grid.

  2. Add Bookmark: Click the bookmark icon. A confirmation message will appear.

Context Menu

  • Access: Right-click on a record to open the context menu.

  • Options Available: Edit, Delete, Add Bookmark.

Important Note

  • Usage Check: The system prevents deletion of object types currently in use to maintain data integrity.

This streamlined process for managing object types in TCPWave IPAM enables efficient and orderly categorization of network entities, enhancing overall network management and organization.

VRF

Overview

Virtual Routing and Forwarding (VRF) is a key technology in routers for creating multiple, distinct routing tables. It allows network paths to be separated within a single device, enhancing network organization and functionality.

VRF Interface Operations

In the VRF interface of TCPWave IPAM, you can:

  1. Add VRF: Create new VRF instances.

  2. Edit VRF: Modify existing VRF configurations.

  3. Delete VRF: Remove VRF instances that are no longer needed.

  4. Bookmark VRF: Save VRF records for quick access.

Adding a Virtual Routing and Forwarding (VRF) Instance in TCPWave IPAM

Overview

Adding a VRF in TCPWave IPAM involves creating a new instance of Virtual Routing and Forwarding, which allows for multiple, isolated routing tables within a single network infrastructure. This process is crucial for enhancing network path segmentation and organizational efficiency.

Step-by-Step Guide to Add a VRF

  1. Navigation:

    • Access the VRF management area by going to Administration >> Configuration Management >> VRF.

    • This action opens the VRF management page.

  2. Initiate VRF Creation:

    • Click on the appropriate icon to access the Create VRF page.

  3. Completing VRF Attributes:

    • Select Organization: Choose the organization under which the VRF will be created.

    • VRF Name:

      • Enter a unique name for the VRF, distinct from other VRFs.

      • The name should not exceed 255 characters and can include any valid ASCII characters.

    • Route Distinguisher:

      • Input the Autonomous System (AS) number or IP address.

      • This component ensures uniqueness among identical routes across different VRFs, as outlined in RFC 4364.

    • Interface:

      • Assign the VRF to an interface, such as a loopback or VLAN. For instance, f0/0.82.

    • Route Target Settings:

      • Import: Set up to import routing information from specified target extended communities.

      • Export: Configure to export routing information to these communities.

      • This setting, an integer, identifies routes for export/import as per RFC 4364.

    • Description: Provide a brief description of the VRF’s purpose or characteristics.

  4. Confirming VRF Addition:

    • Click OK to proceed. A validation message will appear for confirmation: “Are you sure you want to add the VRF type? Click Yes to proceed.”

  5. Finalize Creation:

    • Click YES. Upon successful creation, a confirmation message “VRF has been created successfully” will display.

Post-Creation

  • VRF Display: The newly added VRF will be listed in the VRF grid, complete with searchable and sortable columns for easy management.

Additionally, the interface includes a Number Dropdown for selecting and viewing a specific number of records.

Common Functionalities

Refer to this section for actions like Refresh, Adjusting Column Visibility, Resetting Preferences, and accessing More options.

Permissions and Access

Access to the VRF section depends on the permissions associated with your user role. For details, consult the “Administrator Roles” section.

Specific VRF Operations

Deleting VRF 1. Selection: Choose the VRF record from the grid. 2. Initiate Deletion: Click the delete icon. A prompt will appear asking for confirmation: “Are you sure you want to delete the selected VRF? Click Yes to proceed.” 3. Confirmation: Click YES. A message will confirm successful deletion: “VRF has been deleted successfully.”

  • Note: If the VRF is linked to any subnets, the system will notify you. To proceed with deletion, first remove these references from the subnet.

Bookmarking VRF 1. Select VRF: Choose a VRF record from the grid. 2. Add Bookmark: Click the bookmark icon. A confirmation message will appear: “Bookmark has been added successfully.”

Context Menu 1. Accessing: Right-click on a VRF record to open the context menu. 2. Options: Includes Edit, Delete, and Add Bookmark.

  • For more details, refer to respective sections on Editing VRF, Deleting VRF, and Bookmarking VRF.

Summary

This VRF management interface in TCPWave IPAM simplifies the process of handling multiple routing table instances, allowing for an efficient and organized network infrastructure. The straightforward options for adding, editing, deleting, and bookmarking VRFs cater to various network configuration needs, ensuring flexibility and control for network administrators.

Change Management

Overview

TIMS IPAM’s integration with ServiceNow, a popular IT management platform, utilizes REST API to interface with ServiceNow for validating Change Request Numbers. This integration ensures that all actions performed during a user session in TIMS IPAM are aligned with an approved ServiceNow Change Request, reinforcing accountability and traceability in change management processes.

Operations in Change Management Interface

The Change Management interface in TIMS IPAM allows users to:

  1. Add Change Management Credentials: Set up new credentials for integrating with ServiceNow. This involves providing necessary information to establish a connection between TIMS IPAM and ServiceNow, ensuring that changes made in TIMS are tracked against valid ServiceNow Change Requests.

  2. Edit Existing Credentials: Modify the details of an existing ServiceNow integration. This might be necessary if there are changes in ServiceNow’s configuration, like updated API keys, change in account details, or alteration in the scope of tracked changes.

  3. Delete Credentials: Remove existing integration settings. This could be useful when changing ServiceNow accounts or discontinuing the integration with a particular ServiceNow instance.

  4. Bookmark Credentials: Mark certain integration settings for quick access. This feature is helpful for users who frequently need to access specific credentials due to regular changes or updates in the integration setup.

Purpose and Benefits

  • Streamlined Change Management: Integrating TIMS IPAM with ServiceNow simplifies tracking and validating changes, making the process more efficient and transparent.

  • Compliance and Audit Trails: Ensures that all changes are authorized and recorded, aiding in compliance and audit activities.

  • Reduced Errors and Downtime: By validating changes against approved requests, the likelihood of unauthorized or erroneous changes is minimized, reducing potential system downtime and issues.

This integration feature is particularly useful for large enterprises and IT departments that rely on structured change management processes to maintain system integrity and compliance.

Adding Change Management Credentials for ServiceNow Integration in TIMS IPAM

Overview

Setting up change management credentials in TIMS IPAM is a crucial step for integrating with ServiceNow. This process involves defining authentication details that allow TIMS IPAM to communicate with a ServiceNow instance, thereby ensuring that changes are tracked and validated against ServiceNow’s Change Request Numbers.

Steps to Add Change Management Credentials

  1. Accessing Change Management Settings:

    • Navigate to Administration >> Change Management in TIMS IPAM.

    • This action opens the Change Management Credentials page.

  2. Initiating Credential Setup:

    • Click the relevant button to open the Define Change Management Credentials page.

  3. Filling in Authentication Details:

    • Change Management Provider: This field will automatically be set to ServiceNow.

    • Instance URL: Enter the URL of your ServiceNow personal developer instance.

    • Username: Input the username associated with the ServiceNow instance.

    • Password: Provide the password for the ServiceNow instance.

    • Description: Add a brief description for reference. This might include details like the purpose or scope of these credentials.

  4. Saving Credentials:

    • Click OK to save the details.

    • Upon clicking, a validation message will confirm the successful addition: “Change Management Credential has been added successfully.”

Result

The newly added change management credentials will facilitate communication between TIMS IPAM and the specified ServiceNow instance. This setup ensures that any changes made in TIMS IPAM are corroborated with ServiceNow’s Change Management system, adhering to organizational procedures and audit requirements.

Importance

Incorporating these credentials into TIMS IPAM’s workflow is vital for maintaining controlled and transparent change management processes, particularly in environments where compliance, traceability, and documentation of IT changes are essential.

Firmware Management

Purpose

TCPWave’s Firmware Management system equips users with the capability to securely update essential operating system software. This feature is particularly valuable for managing and automating firmware or BIOS upgrades across various remotely managed devices in the network.

Core Functions

In the Firmware Management interface of TCPWave IPAM, you can carry out two primary operations:

  1. Add Firmware Updates:

    • This function allows you to upload new firmware or BIOS updates to the system. It is essential for keeping your network devices up-to-date with the latest security patches and features.

    • The process typically involves specifying the firmware file and setting parameters for the upgrade process, ensuring compatibility with the targeted devices.

  2. Delete Firmware Versions:

    • This option is used to remove previously uploaded firmware versions from the system. It might be necessary in cases where a firmware version is outdated, no longer supported, or has been superseded by more recent updates.

    • Deleting older firmware versions can help in decluttering the management interface and avoiding confusion over which firmware versions are current and applicable for upgrades.

Key Considerations

  • Automated Upgrades: TCPWave IPAM’s interface facilitates automated firmware upgrades, simplifying the process and reducing manual intervention.

  • Safety and Reliability: The system is designed to ensure that firmware updates are carried out securely, minimizing the risk of interruptions or failures during the update process.

  • Device Compatibility: Users must ensure that the firmware they are adding is compatible with the devices they intend to update. Incorrect firmware can lead to system malfunctions or downtime.

Summary

TCPWave’s Firmware Management feature is a critical tool for network administrators, offering a streamlined and secure approach to managing firmware upgrades across networked devices. By simplifying the process of adding and deleting firmware versions, it helps maintain network stability and security.

Uploading and Deploying a Firmware or BIOS Patch in TCPWave IPAM Overview

Uploading and deploying firmware or BIOS patches in TCPWave IPAM involves a series of steps to ensure the secure and successful update of network appliances. This process is critical for maintaining the integrity and performance of network systems.

Steps to Upload a Firmware or BIOS Patch

  1. Accessing Firmware Management:

    • Navigate to Administration >> Firmware Management in TCPWave IPAM.

  2. Initiating Upload:

    • Click the appropriate button to open the Upload Patch pop-up window.

  3. Uploading the Patch:

    • Drag the firmware or BIOS file into the designated area. The system automatically populates details like Patch Version, Patch Level, and Description in the respective fields.

Steps to Deploy the Firmware Patch

  1. Navigate to Network Management:

    • Go to Network Management >> DNS/DHCP/IPAM Management.

  2. Select Appliances:

    • From the appliance management page, select the appliances that require the firmware update.

  3. Initiate Deployment:

    • Click Deploy Firmware. A Deploy Firmware Patch pop-up window will appear, listing available firmware patches.

  4. Choosing the Patch:

    • Select the desired firmware patch for deployment on the chosen appliances.

  5. Deploy the Patch:

    • Click Deploy to begin the update process.

The Deployment Process

  • Once the deployment is initiated, TCPWave IPAM sends the selected firmware patch to the chosen remote appliances through a secure messaging tunnel.

  • The system executes the necessary firmware upgrade commands.

  • After the upgrade, the remote appliances report back to TCPWave IPAM regarding the success or failure of the update.

  • If the upgrade is successful, the remote appliances automatically reboot to apply and integrate the latest firmware patch.

Key Considerations

  • Security: The firmware upgrade process is conducted via a secure channel, ensuring the integrity of the appliances.

  • Automatic Field Population: The system’s ability to auto-populate patch details streamlines the upload process.

  • Feedback Mechanism: The reporting of success or failure post-upgrade is crucial for monitoring and verification purposes.

  • Auto-Reboot Feature: The automatic reboot ensures that the appliance starts running on the new firmware without manual intervention.

By following these steps, administrators can effectively manage firmware or BIOS patches in the TCPWave IPAM environment, maintaining up-to-date and secure network appliances.

Location Management

Overview

The Location Management feature in DDI (DNS, DHCP, and IP Address Management) systems allows administrators to manage various locations defined across different organizations within the network. This centralized management of locations aids in streamlining operations and maintaining an organized network infrastructure.

Key Operations in Location Management

  1. Add Locations:

    • This function enables you to define new locations within the system. Adding a location typically involves specifying details such as the location’s name, address, associated organization, and other relevant attributes.

    • Adding locations is crucial for segmenting and managing network resources based on geographical or organizational divisions.

  2. Edit Locations:

    • Editing allows for modifications to existing location details. This might be necessary to update information about a location, such as changes in its name, address, or associated organizational units.

    • Regularly updating location information ensures that the network infrastructure remains aligned with the actual physical or organizational layout.

  3. Delete Locations:

    • This option is used to remove locations that are no longer relevant or needed. Deletion might occur due to organizational restructuring, closure of sites, or other operational changes.

    • Care should be taken to ensure that deleting a location does not adversely impact network management or associated configurations.

  4. Bookmark Locations:

    • Bookmarking facilitates quick access to frequently referenced locations. It is particularly useful in large networks with numerous locations, helping administrators swiftly navigate to specific entries.

  5. Import Locations:

    • Importing allows for bulk addition or update of location information from external data sources. This feature is highly useful for initial setup or large-scale updates to the location database.

    • Importing must be done carefully to ensure data integrity and accuracy.

Location Management Interface

  • The Location Management interface typically features a grid or list view displaying all defined locations.

  • It includes options for search, filter, and sort to easily locate and manage specific entries.

  • The interface is usually accessible to administrators or users with specific roles, emphasizing its importance in network management.

Benefits

  • Enhanced Organization: Centralized management of locations aids in the systematic organization of network resources.

  • Operational Efficiency: Efficient location management streamlines tasks related to network planning, deployment, and troubleshooting.

  • Comprehensive Network View: It provides a holistic view of the network’s geographical or organizational spread.

In summary, Location Management in DDI systems is a fundamental aspect of network administration, playing a key role in organizing and maintaining an efficient, well-structured network infrastructure.

Adding a Location in TCPWave IPAM’s Location Management

Overview

Location Management in TCPWave IPAM allows you to catalog various geographical locations associated with different organizations in your network infrastructure. This can include offices, data centers, or other relevant sites.

Steps to Add a Location

  1. Accessing Location Management:

    • Go to Administration >> Configuration Management >> Location Management. This action brings you to the Location Management section.

  2. Initiating Location Addition:

    • Click on the icon or button to add a new location. The system will display the Location >> New page.

  3. Filling Out Location Details:

    • Organization: Select the relevant organization from a dropdown menu.

    • Street1: Enter the primary street address of the location.

    • Street2: Provide additional address information if necessary.

    • City: Specify the city where the location is situated.

    • State: Enter the state or region of the location.

    • Zip Code: Provide the area’s zip or postal code.

    • Country: State the country of the location.

  4. Confirmation of Addition:

    • After entering all the details, click OK. A validation message will appear: “Are you sure you want to add the location? Click Yes to proceed.” If you need to make no changes to the data, select No.

  5. Finalizing the Addition:

    • Click YES to confirm. A confirmation message will display: “Location has been created successfully.”

Result

  • The newly added location will appear in the Location Management grid. This grid includes search and sorting capabilities, making it easy to find and manage locations.

Importance

  • Adding locations is crucial for effective network management, particularly in organizations with multiple sites. It aids in organizing network infrastructure by geographical area, enhancing clarity in network planning and operations.

By following these steps, you can efficiently add and manage geographical locations within TCPWave IPAM’s Location Management interface, contributing to better organization and oversight of network resources and activities.

Patch Management

Overview

TCPWave Patch Management provides a comprehensive system for safely and efficiently applying software updates. It’s specifically designed to support the patching of systems within the IPAM ecosystem, including IPAM Appliance itself. Key features include the use of TCPWave approved patches, encrypted installation images to prevent tampering, and the ability to schedule deployments and rollbacks during non-peak hours to minimize service disruptions.

Patch Management Operations

You can perform several operations within this module:

  1. Upload Patches: Introduce new patches into the system.

  2. Delete Patches: Remove patches from the system.

Patch Content and Properties

Each patch in TCPWave includes:

  • Metadata File: Contains patch properties and information for validation, formatted in name-value pairs.

  • Installation Image: An encrypted rpm format image, decrypted prior to installation.

  • deployPreInstall File: A script executed before patch deployment.

  • deployPostInstall File: A script executed after patch deployment.

  • rollbackPreInstall File: A script executed before rolling back a patch.

  • rollbackPostInstall File: A script executed after a patch is rolled back.

Uploading a Patch

  1. Access Patch Management: Go to Administration >> Patch Management.

  2. Initiate Upload: Click to open the Upload Patch pop-up. Drag and drop or upload the patch file.

  3. Provide Patch Details: The system auto-populates fields such as package name, version, level, server type, size, creation time, description, and message.

  4. Validate: Click Validate for the system to check the patch, ensuring the install image matches metadata details.

  5. Upload: After validation, click Upload to add the patch to the repository.

Quick Deployment

  1. Select Patch: Choose a patch from the Patches grid.

  2. Choose Appliances: Select appliances for the upgrade from the Patch Deployment Information grid.

  3. Deploy: Click Deploy and choose immediate deployment or schedule for a later time.

  4. Automatic Restart: Appliances may automatically restart to complete the patch process.

Workflow Deploy

  1. Create Custom Procedure: Select appliances and click Workflow deploy.

  2. Configure Steps: Arrange the sequence of patching for multiple appliances.

  3. Initiate Deployment: Confirm to start the patching process.

Rollback

Roll back a patch on appliances either sequentially or in parallel, after which system services restart automatically.

Force Reset

In case of a stalled or problematic deployment, you can reset the patch status.

Enable Auto Refresh

This feature updates the deployment or rollback status in real time.

Deleting a Patch

Remove a patch from the repository if it’s not dependent on other patches and is not installed on any appliance.

Summary

TCPWave’s Patch Management module ensures secure, efficient, and scheduled updates across the IPAM ecosystem. With its robust set of features, it facilitates safe software updates while minimizing operational disruptions.

Resiliency Management

AWS S3 Recovery

TCPWave IPAM’s integration with AWS S3 provides a robust solution for database backup and recovery. This feature enhances data resilience by allowing the creation, storage, and retrieval of database snapshots in AWS S3, ensuring that your network management system’s data remains secure and recoverable.

Key Functionalities

  1. Backup Snapshot: This functionality enables you to create and store database snapshots on AWS S3.

  2. Restore: Allows for the retrieval and restoration of data from a stored snapshot.

  3. Delete: Permits the removal of no longer needed snapshots from AWS S3.

Prerequisites for Setup

  1. AWS CLI Credentials: Configure these credentials by logging into the IPAM appliance as a root user and executing aws configure.

  2. Permission Adjustment: After configuring, copy the .aws directory to /home/twcadmin/ and adjust permissions accordingly.

  3. Setting Global Options for S3 Bucket: Ensure a valid AWS S3 bucket name is set in the IPAM’s global options. This bucket can be created either via the AWS CLI or the AWS S3 console.

Automated Snapshot Storage

  • To automate database snapshot creation, set up a scheduled job in the IPAM’s Scheduler Management. This job will regularly create and upload database snapshots to your designated S3 bucket.

Creating Database Snapshots

  1. Access: Navigate to the AWS S3 Recovery page via the IPAM’s Resiliency Management section.

  2. Initiate Snapshot Creation: Start the process to generate a .tar.gz file of the database, which will be uploaded to AWS S3.

  3. Confirmation: Verify the snapshot’s creation in both the IPAM interface and on the AWS console.

Restoring Database Snapshots

  1. Selection: Choose the desired snapshot from the AWS S3 Recovery page.

  2. Initiate Restoration: Start the process to revert the database to the state captured in the selected snapshot.

Deleting Database Snapshots

  1. Select Snapshots: From the AWS S3 Recovery page, pick the snapshots you want to delete.

  2. Delete: Remove these snapshots, which will also delete them from the AWS S3 bucket.

Conclusion

The AWS S3 Recovery integration in TCPWave IPAM offers an effective way to manage data backups and restoration. It ensures not only the integrity and availability of the network management system’s data but also simplifies the process of data resilience management. With automated backup options, easy restoration processes, and the ability to delete outdated backups, administrators can maintain their network’s data efficiently and securely.

Disaster Recovery (DR) Configuration

TCPWave IPAM’s Disaster Recovery (DR) feature provides a robust method for ensuring continuous operation of your network management system in the event of a failure. Setting up a DR configuration involves designating a secondary (slave) IPAM appliance that can take over in case the primary (master) appliance encounters issues.

Steps to Set Up Disaster Recovery Configuration

  1. Accessing DR Configuration:

    • Navigate to Administration > Resiliency Management > Disaster Recovery Configuration.

    • By default, you’ll land on the ‘Configuration’ tab

  2. Initiating Configuration:

    • Click on ‘Configure DR’.

    • Enter the IP address of the slave IPAM appliance.

    • Click ‘OK’ to begin the DR setup. Note that this puts the management appliances into a restricted mode until setup completion.

  3. Completing Setup:

    • Confirm the setup by clicking ‘YES’.

    • To monitor the setup process, you can view the logs in the ‘Configuration Log’ tab.

Initiating Failover

  • To initiate failover, go to the ‘Events and Actions’ tab.

  • Select the ‘Failover’ option and click ‘Apply’.

  • The status will update to ‘completed’ once the action is finished.

Role Reversal After Failover

  • Post-failover, the master appliance becomes the slave and will only redirect to the DR page.

  • The former slave appliance assumes the role of the master, enabling full functionality.

Log Monitoring During DR Setup

During a DR setup or when a standby node reconnects after disconnection:

  • The master node synchronizes data with the standby node. This can take several minutes to an hour.

  • The logs in /var/lib/mysql/mysql.err indicate successful completion.

  • Sample log entries:

    • [Note] WSREP: Member 0.0 (tcpwave-ipam) synced with group.

    • [Note] WSREP: Shifting JOINED -> SYNCED (TO: 14381495).

    • [Note] WSREP: Synchronized with group, ready for connections.

  • If the first sync attempt fails, the system will automatically retry to ensure completion without user intervention.

Important Note Before Failover

  • Before initiating a failover, always perform a ‘Sync slave’ action to ensure data consistency between the master and slave appliances.

  • Post Disaster Recovery switch, check the ‘Switch Log’ tab for relevant logs.

Conclusion

TCPWave IPAM’s Disaster Recovery feature provides an essential safeguard for network management systems, ensuring minimal disruption and continuous operation. Through a well-orchestrated process of failover and synchronization, it maintains network stability and data integrity, crucial for robust IT infrastructure management.

Point in Time Recovery

Point in Time Recovery is a crucial feature in TCPWave IPAM for database restoration in case of a disaster. This functionality allows for the creation, backup, restoration, and management of database snapshots and incremental changes.

Key Operations in Point in Time Recovery

  1. Backup Snapshot: Create a complete snapshot of the current database state.

  2. Backup Incremental Changes: Capture changes made after the last configuration to update backups.

  3. Restore Database: Revert the database to a specific snapshot state.

  4. Delete Snapshot: Remove a stored database snapshot.

  5. Upload: Add a database snapshot file to the system.

  6. Download: Retrieve a stored database snapshot file.

Creating Database Snapshots

  • Navigation: Go to Administration > Resiliency Management > Point in Time Recovery. The system will display the recovery page.

  • Process:

    • Click ‘Create Snapshot’.

    • Confirm the action. The system will then notify you once the snapshot is created successfully.

Backing Up Incremental Changes

  • Initiation: Click ‘Backup Incremental Changes’.

  • Confirmation: The system collects recent changes and creates a new backup file. Confirm the backup when prompted.

Restoring Database

  • Selection: Choose a database snapshot from the grid.

  • Restoration: Initiate the restoration. Note that the system will be unavailable during recovery. Confirm your action when prompted.

  • Limitation: Restoration cannot be performed if the system is in HA configuration mode.

Deleting a Database Snapshot

  • Process: Select a snapshot and click ‘Delete’.

  • Confirmation: Confirm the deletion. The system notifies upon successful deletion.

Uploading a Database Snapshot

  • Uploading: Click ‘Upload’. Use the pop-up to drag and drop or select a file for uploading.

  • Validation: The system checks if the file is a TCPWave-approved format.

Downloading a Database Snapshot

  • Download Initiation: Select a snapshot from the grid and click ‘Download’.

  • Downloading: Follow the link provided in the pop-up to download the file.

Access and Permissions

  • Role-Based Access: This section’s accessibility is determined by the permissions associated with your administrative role.

  • Common Functionalities: This includes options like Refresh, Column Visibility, Reset Preferences, and More, which are available based on your assigned role.

Conclusion

Point in Time Recovery in TCPWave IPAM is an essential tool for database management, offering comprehensive options for creating, managing, and restoring database states. This feature enhances data resilience by ensuring that snapshots and incremental changes can be effectively backed up, restored, or managed as per operational requirements.

High Availability (HA) Configuration

High Availability (HA) in TCPWave IPAM is a resilience mechanism using T-Mesh technology to ensure continuous service without interruptions or failures. This is achieved through an IPAM cluster setup using open-source Galera Cluster technology for database synchronization.

Setting Up HA in TCPWave IPAM

  1. Starting HA Configuration:

    • Go to Administration > Resiliency Management > HA Cluster Configuration.

    • If an IPAM appliance is not defined at its IP address, a validation message appears.

    • To start, click ‘Configure HA’ and confirm by clicking ‘YES’.

  2. Role of Master and Members:

    • The first IPAM appliance joining the cluster becomes the Master.

    • Other IPAM appliances are Members.

    • If the Master goes offline, another appliance takes over based on priority values and managed remotes.

  3. Requirements and Restrictions:

    • At least three IPAM appliances are recommended for the cluster.

    • Disaster Recovery configuration must not be in place before setting up HA.

Managing the HA Cluster

  1. Adding an IPAM Appliance to the Cluster:

    • When adding a new appliance, all existing data and remotes on it are lost and replaced with the cluster’s data.

    • Navigate to the HA IPAM Appliances grid and complete the fields in the ‘Add IPAM Appliance to HA Cluster’ pop-up.

  2. Removing an IPAM Appliance:

    • The Master cannot be removed directly. A new Master must be promoted first.

    • Removal results in redistribution of remotes and update of database configurations to standalone.

  3. Setting a New Master:

    • Choose an appliance from the grid and use the ‘Set Master’ option.

  4. Changing Priority:

    • Modify an IPAM appliance’s priority for selection as a new Master if the current Master fails.

  5. Rejoining the Cluster:

    • This option is available for appliances that need to reconnect to the cluster.

  6. Resetting HA Configuration:

    • This is done when dismantling the entire HA setup. All member IPAMs must be removed first.

Redistributing Remote Appliances

  • Remotes are connected to IPAM appliances based on ping time or user-set preferences. Redistribution can be initiated as needed.

Managing IPAM Appliance Preferences

  • Preferences for remote appliance connections can be set, prioritizing certain IPAM appliances over others.

Best Practices and Critical Notes

  • Regularly update HA configurations.

  • Manage priority settings for unplanned failovers.

  • Keep in mind that HA is different from disaster recovery and both should be managed accordingly.

  • Only authorized personnel with the appropriate administrative roles should access and configure HA settings.

Conclusion

The HA configuration in TCPWave IPAM ensures that the network remains operational and resilient through active-active configurations and prioritized failover mechanisms. Properly setting up and managing the HA environment is critical for continuous service delivery and system reliability.