- play_arrow Introduction
- play_arrow Overview
- About the Paragon Automation (Pathfinder, Planner, Insights) User Guide
- Paragon Automation Overview
- Paragon Pathfinder Overview
- Paragon Insights Overview
- Paragon Planner Overview
- Understand Differences between Paragon Pathfinder and Planner
- Paragon Automation GUI Overview
- Paragon Automation GUI Menu Overview
- play_arrow Access the Paragon Automation GUI
- play_arrow Access the Paragon Planner
- play_arrow Configure SMTP, LDAP, and Portal Settings
- play_arrow Manage Users
- play_arrow Manage Roles
- play_arrow Manage User Groups
- play_arrow Identity Providers
-
- play_arrow Workflows
- play_arrow Base Platform
- play_arrow Paragon Pathfinder
- play_arrow Paragon Planner
- play_arrow Paragon Insights
-
- play_arrow Manage Devices and Network
- play_arrow Devices
- play_arrow Device Groups
- play_arrow Device Images
- play_arrow Network
- play_arrow Network Groups
- play_arrow Topology Filter
-
- play_arrow Manage Device Templates and Configuration Templates
- play_arrow Configuration Templates
- Configuration Templates Overview
- Configuration Templates Workflow
- About the Configuration Templates Page
- Add Configuration Templates
- Preview and Render a Configuration Template
- Assign Configuration Templates to a Device Template
- Deploy a Configuration Template to a Device
- Edit, Clone, and Delete a Configuration Template
- play_arrow Device Templates
-
- play_arrow Manage Playbook, Rules, Resources, and Graphs
- play_arrow Playbooks
- play_arrow Rules
- Understand Paragon Insights Topics
- Rules Overview
- About the Rules Page
- Add a Predefined Rule
- Edit, Clone, Delete, and Download Rules
- Configure a Custom Rule in Paragon Automation GUI
- Configure Paragon Insights Notification for LSP Gray Failures
- Configure Multiple Sensors per Device
- Understand Sensor Precedence
- Configure Sensor Precedence
- play_arrow Resources
- Understand Root Cause Analysis
- About the Resources Page
- Add Resources for Root Cause Analysis
- Configure Dependency Between Resources
- Example Configuration: OSPF Resource Dependency
- Edit Resources and Dependencies
- Upload Resources
- Download Resources
- Clone Resources
- Delete User-Generated Resources and Dependencies
- Filter Resources
- play_arrow Graphs
- play_arrow Grafana
-
- play_arrow Manage Sensor Settings, Insights Settings, and Data Summarization Profiles
- play_arrow Sensor Settings
- Sensors Overview
- About the Ingest Settings Page
- Configure NetFlow Settings
- Configure a Rule Using Flow Sensor
- About the Frequency Profiles
- Manage Frequency Profiles
- Apply a Frequency Profile
- Configure Offset Time
- Configure a Rule Using Server Monitoring Sensor
- Configure Native GPB Ingest
- Configure sFlow Settings
- Configure SNMP Ingest
- Configure a Rule Using SNMP Scalar
- Configure SNMP Trap and Inform Notifications
- Configure Outbound SSH Port for iAgent
- Configure System Log Ingest
- System Log Optional Configurations
- Configure a Rule Using Syslog
- Understand Inband Flow Analyzer 2.0
- Configure Device Details for Inband Flow Analyzer Devices
- Delete an Inband Flow Analyzer Device
- Understand Bring Your Own Ingest
- Load BYOI Default Plug-ins
- Configure Bring Your Own Ingest Default Plug-in Instances
- Build and Load BYOI Custom Plug-in Images
- Configure Bring Your Own Ingest Custom Plug-in Instances
- Use Sample Rule and Playbook Configurations for BYOI Custom Plug-in Instances
- Configure Ingest Mapping for Default BYOI Plug-in Instances
- Delete a BYOI Plug-in
- About the Diagnostics Page
- Use the Self Test Tool
- Use the Reachability Test
- Use the Ingest Test Tool
- Use the No-Data Tool
- Paragon Insights Tagging Overview
- Types of Tagging
- Add a Tagging Profile
- Apply a Tagging Profile
- Delete a Tagging Profile
- Understand User-Defined Actions and Functions
- Modify User-Defined Action, Function, and Workflow Engines
- Enable UDA Scheduler in Trigger Action
- Understand kube-state-metrics Service
- play_arrow Insights Settings
- About the Insights Settings Page
- Add Alert Blackouts
- About Alert Notifications
- Use Exim4 for E-mails
- Configure the Exim4 Agent to Send E-mail
- Configure a Notification Profile
- Enable Alert Notifications for Device Groups and Network Groups
- Configure Report Settings
- Configure Scheduler Settings
- Configure a Retention Policy
- Configure Destination Settings
- Time Series Database (TSDB) Overview
- Manage Time Series Database Settings
- Backup and Restore the TSDB
- Time Series Database Replication Scenarios
- play_arrow Data Summarization Profiles
-
- play_arrow Configure Your Network
- play_arrow Topology
- play_arrow Network Information Table
- Network Information Table Overview
- About the Node Tab
- Add a Node
- Edit Node Parameters
- Delete a Node
- About the Link Tab
- Add a Link
- Edit Link Parameters
- Delete a Link
- About the Tunnel Tab
- Understand How Pathfinder Handles LSPs
- Reroute LSPs Overview
- Segment Routing Overview
- Add a Single Tunnel
- Add Diverse Tunnels
- Add Multiple Tunnels
- Edit and Delete Tunnels
- About the Demand Tab
- About the Interface Tab
- Container LSP Overview
- About the Container LSP Tab
- Add a Container LSP
- Edit Container LSP Parameters
- Maintenance Event Overview
- About the Maintenance Tab
- Add a Maintenance Event
- Edit a Maintenance Event
- Simulate a Maintenance Event
- Delete a Maintenance Event
- About the P2MP Groups Tab
- Add a P2MP Group
- Edit P2MP Group Parameters
- About the SRLG/Facility Tab
- Add an SRLG/Facility
- Edit SRLG/Facility Parameters
- About the Topology Group Tab
- Add Anycast Group Tunnels
- play_arrow Tunnels
- play_arrow Change Control Management
-
- play_arrow Monitoring
- play_arrow Monitor Network Health
- play_arrow Manage Alarms and Alerts
- play_arrow Monitor Jobs
- play_arrow Analytics
- play_arrow Monitor Workflows
-
- play_arrow Administration
- play_arrow Manage E-mail Templates
- play_arrow Manage Audit Logs
- play_arrow Configure External EMS
- play_arrow Manage Task Scheduler
- play_arrow Manage Security Settings
- play_arrow License Management
-
View Inventory Reports
Paragon Automation enables you to generate and view Inventory reports that provide details of the hardware inventory in the network. For information on the types of Inventory reports and how to generate them, see Inventory Reports Overview.
To access the page for to a specific Inventory report, select Reports > Inventory > Report-Name.
You can perform the following actions on this page:
View the following Inventory reports:
Download a report—Hover over the Download button on the top-right corner of the report and select either CSV or JSON to download the report as a comma-separated values file (CSV) or JavaScript Object Notation (JSON) file, respectively.
Show or hide columns in a report—Click the vertical ellipsis icon at the top-right corner of the report and select the columns that you want displayed in the report.
Only the columns that you selected are displayed.
Table 1 explains the fields displayed in the Devices report.
Field | Description |
---|---|
Device Name | Name of the device present in the network. |
Vendor | Name of the device vendor. Example: Juniper |
IP Address | IPv4 address of the device. |
Source | Filename of the configuration file from where the device details are collected. |
System Name | System name for the device. |
Description | Description for the device. |
Contact | Contact name for the device. |
Location | Physical location of the device. |
Last update by CLI | Date (in MM:DD:YYYY format) and time (in HH:MM:SS 12-hour or AM/PM format) at which the configuration file was last updated as a result of device collection. |
Chassis Type | Type of chassis. Example: WS-C6509-E |
Hardware Version | Hardware revision model of the chassis. |
Hardware ID | Serial number of the chassis. |
ROM Version | ROM monitor version. |
ROM System Version | ROM system software version. |
Configuration Register | SNMP configuration register value. |
Memory | RAM (in bytes) available to the CPU. |
Configuration Memory | Non-volatile configuration memory available, in bytes. |
Configuration Memory In Use | Non-volatile configuration memory used, in bytes. |
Boot Image | Information related to the boot image. Example: a string starting with flash:, bootflash:, disk0: |
Processor | Processor used in the device. Example: PowerPC405 |
OS Version | Version of OS that is currently installed on the device. |
Management IP Address | Management IP Address that is used by Paragon Planner to discover the device. |
Model | Additional details not known from the vendor, for example, by distinguishing JUNIPER and JUNIPER_EX. |
OS Family | OS family to which the device belongs. Example: JUNOS |
Last Update by SNMP | Date (in MM:DD:YYYY format) and time (in HH:MM:SS 12-hour or AM/PM format) at which the configuration file was last updated as a result of SNMP collection. |
Hostname | Hostname of the device. |
IPv6 | IPv6 address of the device, if any. |
AS | Autonomous system (AS) number assigned to the device. |
Table 2 explains the fields displayed in the Device Parts report.
Field | Description |
---|---|
Name | Name of the device part. |
Device Name | Name of the device to which this part belongs. |
Vendor | Name of the device vendor. Example: Juniper |
IP Address | IP address of the device to which the part belongs. |
Part | Part number associated with the device part. |
Serial Number | Serial number of the device part. |
Description | Description for the device part. |
Estimated Cost | Estimated cost of the device part. |
Hostname | Hostname of the device. |
AS | AS number assigned to the device. |
Model | Additional details not known from the vendor, for example, by distinguishing JUNIPER and JUNIPER_EX. |
Card ID | Location of the card on the device. Example: S-0/1 |
Table 3 explains the fields displayed in the Line Cards report.
Field | Description |
---|---|
Card Name | Name of the line card. For example: WS-X6704-10GE |
Device Name | Name of the device to which this part belongs. |
Vendor | Name of the device vendor. Example: Juniper |
IP Address | The IP address of the device to which the part belongs. |
Card ID | Location of the card on the device. Example: S-0/1 |
Connected Ports | Sum of the number of ports that meet one or more of the following conditions:
|
Reserved Ports | Number of reserved ports in the line card. A port is considered reserved if the interface description in the configuration file contains one or more of the following keywords:
|
Shutdown Ports | Number of ports that have operational status or administrative status as Down. |
Port Count | Number of ports on the line card. |
Part | Part number of the line card. |
Serial number | Serial number of the line card. |
FRU Line Cards | Name of the field-replaceable unit (FRU) line card (applicable only to Cisco devices). |
FRU Route Memory | Route memory allocated to the FRU (applicable only to Cisco devices). |
FRU Packet Memory | Packet memory allocated to the FRU (applicable only to Cisco devices). |
L3 Engine Type | Type of L3 Engine (applicable only to Cisco devices). |
L3 Engine | Details related to the L3 engine (applicable only to Cisco devices). |
TAN | Top Assembly Number (TAN) or ordering number (applicable only to Cisco devices). |
Description | Description for the line card. |
Controller Memory | Controller memory (applicable only to Cisco devices). |
Estimated Cost | Estimated cost of the line card. |
Management IP Address | Management IP Address that is used by Paragon Planner to discover the device. |
Version | Line card version information. Example: rev A0 ver 4 |
Hostname | Hostname of the device. |
Operational State | Operational state of the device. |
Admin State | Administrative state of the device. |
AS | AS number assigned to the device. |
Table 4 explains the fields displayed in the Line Cards Usage report.
Field | Description |
---|---|
Card Name | Name of the line card. For example: WS-X6704-10GE |
Device Name | Name of the device to which this part belongs. |
Card ID | Location of the card on the device. Example: S-0/1 |
Connected Ports | Sum of the number of ports that meet one or more of the following conditions:
|
Reserved Ports | Number of reserved ports, based on the customizable keywords found in the description in the configuration file. |
Shutdown Ports | Number of ports that have operational status or administrative status as Down. |
Number of Ports | Number of ports on the line card. |
Hostname | Hostname of the device. |
Table 5 explains the fields displayed in the Miscellaneous Parts report.
Field | Description |
---|---|
Name | Name of the device part. Example: Power supply, fan, display |
Device Name | Name of the device to which this part belongs. |
Vendor | Name of the device vendor. Example: Juniper |
IP Address | IP address of the device to which the part belongs. |
Part | Part number associated with the device part. |
Serial Number | Serial number of the device part. |
Description | Description for the device part. |
Estimated Cost | Estimated cost of the device part. |
Hostname | Hostname of the device. |
AS | AS number assigned to the device. |
Model | Additional details not known from the vendor, for example, by distinguishing JUNIPER and JUNIPER_EX. |
Card ID | Location of the card on the device. Example: S-0/1 |
Table 6 explains the fields displayed in the Physical Interfaces report.
Field | Description |
---|---|
Interface | Name of the physical interface. Example: GigabitEthernet0/0/0/0 |
Device Name | Name of the device that contains the physical interface. |
Vendor | Name of the device vendor. Example: Juniper |
IP Address | IP address of the physical interface. |
Admin Status | Administrative status (active, down, or unknown) of the physical interface. |
IP Addr | Loopback IP address of the device, typically the first IP address in the IP address range is listed. |
Media Type | Media type for the physical interface. Example: Ethernet, FE, GE |
MTU | Maximum Transmission Unit (MTU) of the physical interface. |
Bandwidth | Bandwidth of the physical interface. Example: 1000.0M |
Physical Address | Physical address (MAC address) for the physical interface. |
Operational Status | Operational status (Active, Down, or Unknown) of the physical interface. |
Description | Description for the physical interface. |
IPv6 | IPv6 address of the physical interface, if any. |
Management IP Address | Management IP Address that is used by Paragon Planner to discover the device. |
Card ID | Location of the card on the device. Example: S-0/1 |
Aggregated Link | Aggregated link (if any) associated with the physical interface. Example: PortChannel, Bundle-Ether |
VLAN | List of VLANs on the physical interface. Example: 22 100-102 105-108 |
Switchport Mode | Switchport mode for layer 2 interfaces. Example: Access or Trunk |
Hostname | Hostname of the device. |
AS | AS number assigned to the device. |
Table 7 explains the fields displayed in the Transceivers report.
Field | Description |
---|---|
Name | Name of the transceiver. Example: SFP-10GBase-ER |
Device Name | Name of the device. |
Vendor | Name of the device vendor. Example: Juniper |
IP Address | Loopback IP address of the device, typically the first IP address in the IP address range is listed. |
Index | Location of the card on the device. Example: S-0/1 |
Part | The part number associated with the transceiver. |
Serial Number | Serial number of the transceiver. |
Estimated Cost | Estimated cost of the transceiver. |
Hostname | Hostname of the device. |
AS | AS number assigned to the device. |
ContainedIn | Name of the line card that contains the transceiver. |