AppDynamics switched from Semantic Versioning to Calendar Versioning starting in February 2020 for some agents and March 2020 for the entire product suite.


    Skip to end of metadata
    Go to start of metadata

    You install the Network Agent as part of an overall workflow for setting up Network Visibility. The three supported workflows are:

    See Set Up Network Visibility on Linux

    Install the RPM Agent

    1. Check System Requirements. See Network Visibility Requirements and Supported Environments
    2. If you are installing the Network Agent as part of the Multi-Tenant Install workflow, stop each application of interest if it is monitored by an installed App Agent. You will restart each application after you install and set up the Network Agent.
    3. Verify that you have sudo or root access permissions on the machine where you want to install the Network Agent. (You do not need sudo or root access to run the Agent.)
    4. Open a command prompt on the host, enter the mount command, and check the mounted file system for the directory where you plan to install the Agent. The file system should not have the noexec and nsuid flags set.
    5. Download the network-agent package to the machine. 
    6. Verify that you have sudo or root access permissions on the machine where you want to install the Agent.
    7. Download the Agent package to the machine.
    8. Open a terminal window and enter: sudo rpm -ivh <installer.rpm>
      The Network Agent software is installed under /opt/appdynamics/netviz.  
    9. To start the Agent, enter: sudo service appd-netviz start
    10. Verify that the Network Agent is running: sudo service appd-netviz status 
    11. If you experience any problems or issues, see FAQs and Troubleshooting for Network Visibility
    12. If you are installing the Network Agent as part of a Set Up Network Visibility on Linux workflow, proceed to the next step in the workflow:

    Administer the RPM Agent

    You should run the following commands as a  <network_agent_user>  with permissions to configure and run the Agent on the host machine.

    OperationCommandNotes
    Start Agent
    sudo service appd-netviz start


    If the Agent starts successfully, the following displays:

    Starting appd-netviz (via systemctl): [  OK  ]

    Stop Agent
    sudo service appd-netviz stop

    If the Agent stops successfully, the following displays:

    Stopping appd-netviz (via systemctl):  [  OK  ]

    Restart Agent
    sudo service appd-netviz restart

    If the Agent restarts successfully, the following displays:

    Stopping appd-netviz (via systemctl):  [  OK  ]

    Check Agent status
    sudo service appd-netviz status

    The following example illustrates status output:

    appd-netviz.service - Appdynamics Network Monitoring
      Loaded: loaded (/usr/lib/systemd/system/appd-netviz.service; disabled; vendor
      Active: active (running) since Thu 2016-09-29 14:52:42 PDT; 14s ago
      Process: 3981 ExecStart=/opt/appdynamics/netviz/bin/appd-netmon (code=exited, 
      Process: 3973 ExecStartPre=/bin/chown -R appd-netviz:appd-netviz /opt/appdynam
      Process: 3968 ExecStartPre=/bin/mkdir -p /opt/appdynamics/netviz/run/ (code=ex
     Main PID: 3983 (appd-netmon)
        Tasks: 12 (limit: 512)
       CGroup: /system.slice/appd-netviz.service
               ├─3983 /opt/appdynamics/netviz/bin/appd-netmon
               ├─3984 appd-netagent -l /opt/appdynamics/netviz/scripts/netagent/lua/
               └─3985 appd-netcor -l /opt/appdynamics/netviz/scripts/netcor/lua/

    Sep 29 14:52:42 localhost.localdomain systemd[1]: Starting Appdynamics Network M
    Sep 29 14:52:42 localhost.localdomain systemd[1]: Started Appdynamics Network Mo
    lines 1-15/15 (END)

    Uninstall the RPM Agent

    To uninstall the Network Agent, enter:

    sudo rpm -e appd-netviz

    This command generates no output. To confirm that the Agent is removed, enter the status command again: sudo service appd-netviz status


    • No labels