Topology Discovery

Traverse discovers network connectivity, disks, controllers, VLANs, file systems, fiber channel switches, printers, SAN, NAS devices, and more.

In addition, Traverse discovers the capabilities, size, capacity, and other key attributes of each element, and the applications running on various devices, such as databases, active directory, radius, DNS, mail, and application servers.

With this information, Traverse builds the hierarchical topology map between your network devices such as switches, routers, VLANs, ATM/frame‐relay, and older generation bridges and hubs. Traverse maintains mappings and relationships between services and underlying components even in dynamic virtual environments.

Traverse includes an unmatched component template and signature library for IT infrastructure. This library provides detailed information on hundreds of the most commonly used infrastructure devices. As important, the library also contains intelligence on the key metrics for these devices.

With this library, Traverse saves time for users during:

  • Initial creation of topology maps, since much of the required data is prepopulated
  • Problem resolution by reducing extraneous metrics which can create noise in the data collected
  • Users can also create visual relationship maps between services and infrastructure, enabling better problem isolation and root‐cause analysis.

IT Service Containers

Different departments and users can create different views of the network to align with their roles within an organization. For example, a network administrator might create a container for the backbone routers and another for edge routers, while the database administrator might group all the databases in a database container.

Users Can:

  • Create Service Containers that include tests and/or devices from multiple departments and locations
  • Develop as many Service Containers as needed, as well as include discrete devices in multiple containers simultaneously
  • Generate reports on Service Containers
  • Receive real‐time status for defined Services, including uptime
  • Be alerted if IT Services fail or exceed user-defined thresholds

Netflow Analysis

Traverse supports integration with network flow and packet level data collection tools to provide seamless drill‐down from system and device-level monitoring to troubleshooting and analysis using flow and packet data.

This capability allows IT managers to drill down from a high level service-centric view to the specific host that is consuming bandwidth or resources. This seamless integration enables quick identification of impacted IT Services (what is affected), trouble areas (where to look) and problem sources (what to analyze further).

When service performance problems are detected, operations personnel can quickly analyze the flow data to identify abnormal traffic volume and traffic type that might be causing the performance degradation.

Supported protocols that provide the required flow data are NetFlow, sFlow, cflowd, and J‐Flow.

Network Configuration Manager

Traverse has an integrated Network Configuration and Change Management (NCM) module which automatically backs up configurations of all routers, firewalls, switches and load balancers within the network.

Traverse helps identify, control and account for the various items in the infrastructure, and ensure their integrity as part of the service delivery lifecycle.

Traverse can manage configurations of thousands of network devices including routers, switches, firewalls, load balancers and security appliances.

You can compare the changes made to any configuration and restore the previous configuration at any time. Having a tightly integrated NCM module provides instant troubleshooting and faster mean time to recover (MTTR).

Event Manager

Traverse collects, filters, categorizes, and displays a variety of events such as SNMP traps, Win events, and syslogs. Leveraging user-defined rules, Traverse then determines the severity of potential issues and takes the appropriate action with this event information.

Traverse supports acknowledgement and annotation of events. Selected events can be suppressed until a given time, and de‐duplication and correlation of events of the same category is supported. From the device‐level view, application users can initiate on‐demand customized actions, such as creation of remediation work tickets.

Because of the capabilities of the Business Service Containers, Traverse can immediately identify which services an event belongs to and the impact of an event on an IT or application service. Traverse integrates with most enterprise ticketing systems out of the box.

Predictive Analytics

Traverse’s predictive analytics capability enables automatic baselining and behavioral learning of cloud and physical infrastructure based on historical data analytics, to enable optimal resource provisioning. This behavioral analysis can be applied to all underlying components of an IT or business service, creating a demand-based performance profile of an IT service.

With these automated thresholding capabilities and comprehensive trend reporting, Traverse provides the power to identify problem sources before they materially impact the performance of business services.

SLA Manager

Traverse’s SLA Manager monitors and measures SLAs from a business service perspective, which enables identifying trends and avoiding failures using proactive reporting. In addition, the SLA Manager enables IT to measure the business impact of infrastructure issues.

While traditional SLA reporting tools can give the status of an individual metric (such as internet connectivity), Traverse can measure SLA compliance of end‐to‐end IT services while keeping time of day and weekend schedules as part of its calculation.

Traverse provides a rich set of SLA features:

  • Specify the length of the SLA compliance time interval as a day, week or month
  • Specify the time interval before the downtime is counted towards an SLA violation (e.g. a small outage of less than 30 seconds does not count towards an SLA violation)
  • Create complex SLA metrics to reflect end‐to‐end IT or Business Services
  • Specify the hour of day and day of week during which the SLA should be calculated (e.g., avoid weekends and non‐business hours in the calculations)