Use the following steps to install a physical Monitoring Point in your network. Once the APM can communicate with the Monitoring Point, additional features can be configured.
This install method is not recommended. It should only be used if you are unable to use the recommended method using a USB stick.
- Connect to the network
- Configure the Monitoring Point
- Assign licenses
- Set the Monitoring Point location
- Cable for Usage monitoring
- Configure additional features
- Determine the best place in your network to deploy the Monitoring Point.
- Configure your firewall rules to enable the Monitoring Point access to APM.
- The Monitoring Point can still be installed and configured without this step, but monitoring is not possible until it is done.
Connect to the network
To physically connect the Monitoring Point to the network:
- Verify that the switch you’ll be connecting to has its default port speed and duplex set to auto-negotiate.
- Using a standard Ethernet cable, connect the Monitoring Point to the switch using the Monitoring Point’s Primary network connection (See Monitoring Points. Look in the “port descriptions” section for your Monitoring Point). A cabling diagram can be found in Monitoring Point Cabling.
Configure the Monitoring Point
The instructions for the ‘Direct Connect’ physical Monitoring Point setup method are found within AppNeta Performance Manager (APM).
- Log in to APM.
- Select an organization if you belong to more than one.
- If you’re setting up your first Monitoring Point, you’ll automatically be taken to the first step of the Add Monitoring Point wizard.
- If your organization already has Monitoring Points, navigate to > Manage Monitoring Points > Add Monitoring Points.
- Click AppNeta hardware.
- Click Direct Connect.
- Follow the instructions provided.
Every Monitoring Point is sold with a base license that allows it to monitor a certain number of applications. The base license must be assigned to the Monitoring Point in APM before it can be used. Optionally, add-on licenses can be assigned.
To license a Monitoring Point:
- Within APM, navigate to > Manage Monitoring Points.
- Wait for the new Monitoring Point to show up in the list (you may need to refresh your screen).
- The Monitoring Point status should show “Connection Established” ().
- If it doesn’t appear after a few minutes, you’ll need to troubleshoot the problem.
- Assign a base license to the Monitoring Point.
- Optionally, assign add-on licenses as required.
Set the Monitoring Point location
When adding a new Monitoring Point to APM, you need to specify its location. This setting provides essential geographical context for the data that the Monitoring Point collects.
To set the location of the Monitoring Point:
- Enter the Monitoring Point location if prompted during the setup procedure.
- If you are outside the setup procedure, you’ll need to edit the Monitoring Point location.
Cable for Usage monitoring
In order to use Usage monitoring, the Monitoring Point must be cabled for it:
- Cable the Monitoring Point for Usage monitoring using one of the following methods:
Configure additional features
Once the Monitoring Point is connected to your network, you can configure it further based on your needs.
|Feature||Applicable Monitoring Point|
|Add a physical interface||m22, m25, m30, m35, m50, m70, r40, r45, r90, r400, r1000, v35|
|Add a VLAN interface||m22, m25, m30, m35, m50, m70, r40, r45, r90, r400, r1000, v35|
|Add a wireless interface||m22, m25, m30, m35, m50, m70|
|Add a static IP address||m22, m25, m30, m35, m50, m70, r40, r45, r90, r400, r1000, v35|
|Change the default interface||m22, m25, m30, m35, m50, m70, r40, r45, r90, r400, r1000, v35|
|Add static routes||m22, m25, m30, m35, m50, m70, r40, r45, r90, r400, r1000, v35|
|Enable DNS||m22, m25, m30, m35, m50, m70, r40, r45, r90, r400, r1000, v35|
|Enable 802.1X||m22, m25, m30, m35, m50, m70, r40, r45, r90, r400, r1000, v35|
|Add an interface for Usage monitoring||m70, r40, r45, r90, r400, r1000|
|Enable LDAP||m25, m35, m50, m70, r45, r90, r1000, v35|
|Enable TACACS+||m22, m30, r40, r400|
|r90 - 10Gbps Delivery/Experience monitoring on port 4||r90|
|r90 - 10Gbps Usage monitoring on port 3||r90|
|r400 - 10Gbps Delivery/Experience monitoring on eth 7||r400|
|r400 - 10Gbps Usage monitoring on eth 6||r400|
|r1000 - 10/40/100Gbps Delivery/Experience monitoring on port 2||r1000|
|r1000 - 10Gbps Usage monitoring on port 3||r1000|