This knowledge base has moved to the documentation site. Please visit the knowledge base here for the most up to date content. This site is no longer maintained.

Installing New Relic Servers on a Cumulus Linux Switch

Follow

New Relic Servers is a server monitoring tool. This article describes how you can use this tool to monitor x86-based switches running Cumulus Linux.

{{table_of_contents}}

Preparing for the Installation

Warning: This only works on x86-based switches!

You need the following

For more information on creating accounts, read the New Relic documentation.

Installation

To install New Relic Servers:

  1. Since Cumulus Linux is Debian based, install the Debian server agent. As with installing any package, you must use root permissions to install the agent:
    cumulus@switch$ sudo -i
    root@switch:~# 
  2. Add the New Relic repo to your apt sources list:
    root@switch:~# echo deb http://apt.newrelic.com/debian/ newrelic non-free >> /etc/apt/sources.list.d/newrelic.list
  3. Add the repository's signing key:
    root@switch:~# wget -O- https://download.newrelic.com/548C16BF.gpg | apt-key add -
  4. Update the switch's repository to add the new packages:
    root@switch:~# apt-get update
  5. Install the New Relic Servers system monitoring client:
    root@switch:~# apt-get install newrelic-sysmond
  6. Find the New Relic license key and install it:
    root@switch:~# nrsysmond-config --set license_key=[YOURLICENSEKEY]

In New Relic Servers, a default dashboard is set up for each Cumulus Linux switch. You can set up custom dashboards or alerts.

Installing the New Relic Service in a Management VRF

If you intend to run New Relic in a management VRF, follow these steps to add it into the mgmt VRF.

  1. Using NCLU, create a management VRF:
    cumulus@switch:~$ net add vrf mgmt
    cumulus@switch:~$ net pending
    cumulus@switch:~$ net commit
  2. Copy the file /etc/systemd/system/newrelic-infra.service to /lib/systemd/system/:
    cumulus@switch:~$ cp /etc/systemd/system/newrelic-infra.service /lib/systemd/system/newrelic-infra.service
    
    cumulus@switch:~$ cat /lib/systemd/system/newrelic-infra.service
    [Unit]
    Description=New Relic Infrastructure Agent
    After=syslog.target
    
    [Service]
    Type=simple
    ExecStart=/usr/bin/newrelic-infra
    MemoryLimit=1G
    Restart=always
    RestartSec=20
    StartLimitInterval=0
    StartLimitBurst=5
    
    [Install]
    WantedBy=multi-user.target
  3. Reload the system daemons:
    cumulus@switch:~$ sudo systemctl daemon-reload
  4. Reference the newrelic-infra service in the /etc/vrf/systemd.conf file:
    cumulus@switch:~$ cat /etc/vrf/systemd.conf
    # Systemd-based services that are expected to be run in a VRF context.
    #
    # If changes are made to this file run systemctl daemon-reload
    # to re-generate systemd files.
    
    chef-client
    collectd
    dhcpd
    dhcrelay
    hsflowd
    netq-agent
    netq-notifier
    netqd
    newrelic-infra
    ntp
    puppet
    snmpd
    snmptrapd
    ssh
    zabbix-agent
  5. Check the contents of the vrf.conf file:
    cumulus@switch:~$ cat vrf.conf
    # created by vrf generator
    
    [Unit]
    SourcePath=/lib/systemd/system/newrelic-infra.service
    After=network-online.target networking.service
    
    [Service]
    ExecStart=
    ExecStart=/usr/bin/vrf task exec %I /usr/bin/newrelic-infra
  6. Start the New Relic service:
    cumulus@switch:~$ sudo systemctl start newrelic-infra@mgmt
  7. Check its status:
    cumulus@switch:~$ sudo systemctl status -l newrelic-infra@mgmt
    
    ● newrelic-infra@mgmt.service - New Relic Infrastructure Agent
       Loaded: loaded (/lib/systemd/system/newrelic-infra.service; disabled)
       Drop-In: /run/systemd/generator/newrelic-infra@.service.d
                └─vrf.conf
        Active: active (running) since Mon 2017-06-12 20:45:59 UTC; 1min 35s ago
      Main PID: 7026 (newrelic-infra)
        CGroup: /system.slice/system-newrelic\x2dinfra.slice/newrelic-infra@mgmt.service
                └─7026 /usr/bin/newrelic-infra

Example Dashboard

List of switches

 

Default dashboard

Comments

This support portal has moved

Cumulus Networks is now part of the NVIDIA Networking Business Unit! The NVIDIA Cumulus Global Support Services (GSS) team has merged its operations with the NVIDIA Mellanox support services team.

You can access NVIDIA Cumulus support content from the Mellanox support portal.

You open and update new cases on the Mellanox support portal. Any previous cases that have been closed have been migrated to the Mellanox support portal.

Cases that are still open on the Cumulus portal will continue to be managed on the Cumulus portal. Once these cases close, they will be moved to the Mellanox support portal.

Powered by Zendesk