Introduction

The OpsRamp platform is a secure, SaaS, AIOps platform for multi-tiered, multi-tenant, IT environments. The platform implements the core components that enable the Solutions layer.

The platform organizes the enterprise into tenants and provides mechanisms and policy definitions for managing accounts, users, user groups, and role-based access.

Key components involved in solution enablement include:

  • dashboards
  • inventory
  • alerts
  • monitors
  • patches
  • RBA
  • service desk
  • knowledge base
  • reports
  • run commands
  • launch consoles
  • run jobs/scripts

The documentation is organized around the main platform components:

  • Platform Feature Guides: Provides in-depth descriptions for how to use the core features.
  • Agents: Provides information about the agent and agent shield, a low-footprint, secure application that runs on managed servers and provides instrumentation required to manage your server.
  • Gateways: Provides information about the gateway, a secure server instrumented for IT environment management that collects the data needed to manage IT resources.

How to Troubleshoot the Registration Failure of Agent/Gateways

A new script has been introduced in the Agent/Gateway to troubleshoot registration and tunnel failures. This script will help you identify the reasons for registration and tunnel issues by performing essential checks and identifying the root cause of the issue.

Follow the guidelines below to run the script:

  • Agent: Go to the specified path and run the command: connectivity-debugger
    • Windows:
      • c:\program files (x86)\OpsRamp\Agent\utils
    • Linux:
      • /opt/opsramp/agent/lib/libexec/
  • Classic Gateway: You can run the script from any location by using the command: connectivity-debugger
  • NextGen Gateway: You need to provide some arguments to the script in Nextgen Gateway deployed using ISO or OVA.
    Below are examples of how to run the script from the NextGen gateway.

    You can run the script from any location, and you can also run it from the vprobe container.
    When you run the connectivity-debugger command, it will list all supported parameters.
    • Eg1: connectivity-debugger –url pod1.opsramp.com –key 7e0871cc-170b-4dea-9644-1852cdca3168
    • Eg2: connectivity-debugger –url pod1.opsramp.com –key 7e0871cc-170b-4dea-9644-1852cdca3168 –namespace default
    • Eg3: connectivity-debugger –url pod1.opsramp.com –key 7e0871cc-170b-4dea-9644-1852cdca3168 –proxy-ip 172.26.1.20 –proxy-port 3128
    • Eg4: connectivity-debugger –url pod1.opsramp.com –key 7e0871cc-170b-4dea-9644-1852cdca3168 –proxy-ip 172.26.1.20 –proxy-port 3128 –proxy-username user01 –proxy-password pass@01

Why should SSL inspection be disabled?

Before registering the agent or gateway, you need to disable SSL inspection on your network to make the connection successful. OpsRamp collectors (agents or gateways) establish a direct or proxy connection using raw socket (TLS) to the OpsRamp cloud. Data transfer occurs in the TLV message format defined by the OpsRamp.

Enabling SSL inspection for the OpsRamp agent or OpsRamp gateway connection can lead to disconnection. This is because intermediate servers within your network won’t comprehend or be able to interpret OpsRamp’s specific packet format, and due to this, when these intermediate servers are unable to understand the packet format, they will reset the OpsRamp connection.

To ensure uninterrupted connectivity, please keep SSL inspection disabled for OpsRamp agent and gateway connections.