Guided 14-Day Evaluation

Validate the main IPAManager workflows with your own network device.

This external evaluation companion guides you through credential setup, device onboarding, network discovery, topology, monitoring, and configuration backup.

6 guided steps Uses the existing trial Progress saved locally No product modification
This guide runs entirely on the website.

It does not connect to the IPAManager server, read device data, or change the product. Step status and the optional evaluation profile are stored only in this browser.

Before you start

Prepare one suitable evaluation device.

1

An installed IPAManager 14-day trial.

2

One supported router, switch, or firewall reachable from the IPAManager server.

3

Working credentials for the workflows you plan to validate.

4

SNMP for CPU and memory metrics; SSH for configuration backup.

5

CDP or LLDP exposure when validating topology relationships.

6

Permission to test the selected device in your environment.

Do not enter passwords, SNMP communities, configuration text, or other sensitive information on this page.

1 FoundationCreate a Credential Profile Not started
Credentials Vault Watch from 00:08

Objective

Create a reusable profile that IPAManager can assign to the evaluation device for discovery, monitoring, topology, and configuration backup.

What to do

  1. Open Credentials Vault.
  2. Enter a clear Profile Name.
  3. Enter the SSH username and password when testing discovery, topology, or configuration backup.
  4. Configure the required SNMP version and authentication details when testing SNMP monitoring.
  5. Select the relevant authentication and privacy protocols when using SNMPv3.
  6. Click Save.
Action: Enter the access details required for the selected workflows.
Expected result: The profile appears in the vault and a creation confirmation is displayed.

Expected result

The credential profile appears in the Credentials Vault and can be assigned to devices.

Value validated

Device access settings can be managed as reusable profiles instead of being re-entered separately for each workflow.

If it does not work

Confirm that required fields are complete and use a distinct profile name. The actual device connection is validated in the next steps.

Record the result:
2 InventoryAdd Your First Device Not started
Inventory → Inventory Info Watch from 00:41

Objective

Add one reachable network device and associate it with the credential profile created in Step 1.

What to do

  1. Open Inventory, then Inventory Info.
  2. Enter the device hostname and management IP address.
  3. Add site notes only when useful for the evaluation.
  4. Select the vendor or operating system and the discovery method.
  5. Select the credential profile created in Step 1.
  6. Click Save Device.
Action: Define the device identity and assign its access profile.
Expected result: The device appears in the Network Inventory.

Expected result

A new inventory row appears with the hostname, management IP, vendor context, assigned profile, and initial status.

Value validated

The device becomes a managed object that can be used by discovery, monitoring, topology, and configuration-management workflows.

If it does not work

Confirm the IP address format, select a vendor and discovery method, and verify that a credential profile is assigned.

Record the result:
3 Network discoveryDiscover Networks from the Device Not started
Inventory → Discovery Control Watch from 02:23

Objective

Read network information from the device and review the discovered networks in the Subnets workspace.

What to do

  1. Remain on Inventory Info and locate Discovery Control.
  2. For a one-device evaluation, select the device and choose Scan Selected Devices.
  3. Leave Debug Mode disabled unless troubleshooting requires additional output.
  4. Start the discovery scan and wait for the progress bar to finish.
  5. Review the execution output for successful connection and discovery messages.
  6. Open Subnets and verify that learned networks are visible.
Action: Run a focused discovery scan and monitor its output.
Expected result: Discovered networks appear in Subnets with source and scan context.

Expected result

The scan completes and discovered networks are added or updated in the Subnets workspace with source-device context.

Value validated

IPAManager can convert device-derived network information into centralized subnet visibility instead of relying only on manually maintained records.

If it does not work

Verify device reachability, the assigned credential profile, the selected discovery method, and any access restrictions between IPAManager and the device.

Record the result:
4 Neighbor visibilityDiscover Topology Neighbors Not started
Topology Watch from 02:48

Objective

Scan the selected device for CDP or LLDP neighbor information and review the resulting topology relationships.

What to do

  1. Open Topology.
  2. Select the evaluation device under Devices to Scan.
  3. Click Start Scan.
  4. Wait until the scan output indicates completion.
  5. Scroll to Topology View.
  6. Review discovered nodes, links, interfaces, and relationship labels.
Action: Select the device, start the scan, and review the command output.
Expected result: The scanned device and available neighbor relationships appear in Topology View.

Expected result

A topology map displays the selected device and any discovered neighbors and links. The number of nodes depends on available CDP or LLDP data.

Value validated

Operational inventory can be supplemented with visual device relationships and interface context discovered directly from the infrastructure.

If it does not work

Confirm the device is accessible, CDP or LLDP is enabled where appropriate, and the assigned credentials permit the required discovery commands.

Record the result:
5 Device healthEnable Monitoring Not started
Monitoring Watch from 03:10

Objective

Enable monitoring for the evaluation device and confirm that availability and supported metrics are collected.

What to do

  1. Open Monitoring.
  2. Enable monitoring for the evaluation device. When the trial contains only intended test devices, Enable All can be used.
  3. Wait for the first monitoring poll to complete.
  4. Confirm that the device is marked as monitored.
  5. Review availability, ping status, CPU, memory, and last-check information.
  6. Open the device graph when historical metric context is required.
Action: Enable monitoring for the device and wait for the first poll.
Expected result: The device is monitored and its available health data is displayed.

Expected result

The device is marked as monitored, availability is reported, and supported ping or SNMP metrics are populated after polling.

Value validated

Availability and device-health context can be reviewed alongside IP address, subnet, inventory, and topology information.

If it does not work

Confirm reachability and the monitoring setting. When ping works but CPU or memory does not, verify SNMP version, credentials, UDP 161 access, and device support.

Record the result:
6 Configuration ManagementComplete a Configuration Backup Not started
Inventory → Config MGMT Watch from 05:10

Objective

Create the first stored configuration version for the evaluation device and verify that the backup result is available for review.

What to do

  1. Open Inventory, then Config MGMT.
  2. Select the evaluation device in the Devices table.
  3. Click Backup Selected.
  4. Wait for the Backup Cycle progress and per-device output to complete.
  5. Confirm that the device shows a successful backup status and a stored version.
  6. Select the version to review its metadata and configuration content.
  7. After a later backup, use version comparison to review configuration changes.
Action: Select the device and start the backup.
Expected result: The device has a successful backup result and version count.
Review: Open a stored version and use comparison after another version exists.

Expected result

A successful backup is recorded and at least one configuration version is available for the selected device.

Value validated

Configuration state can be retained as device-specific versions and reviewed from the same platform used for inventory, discovery, topology, and monitoring.

If it does not work

Verify SSH access, credential assignment, vendor selection, device reachability, and the permissions required to retrieve configuration data.

Record the result:
Evaluation result

Your IPAManager evaluation summary

0Completed
0Partial
0Need help
6Not started
WorkflowResultWhat it validates
Complete the steps above to build a technical evaluation record based on your own environment.
Next step

Continue the trial with the workflows that matter most.

After the first successful device, expand the evaluation to additional supported vendors and compare the operational value against the tools and manual processes currently used in your environment.