r400 Monitoring Point

The AppNeta r400 Enterprise Monitoring Point is used for monitoring in data center environments. A full list of features can be found on the Monitoring Point Feature Comparison page.

Specifications

Wireframe diagrams

Front view:

r400 wireframe - front view.

Rear view:

r400 wireframe - rear view.

Port descriptions

The following table shows how each port on the r400 is used. Maximum port speed is 1Gbps except where specified.

Port # Preconfigured? Port type Used for
E0 Yes Primary Usage monitoring port
(Out-of-band)

or
Primary Usage monitoring port
(Inline)
- part of Bridge 0 (with Port E1)
Port E0/Port E1(1) (uplink/downlink)
Usage monitoring
E1 Yes Primary Usage monitoring port
(Inline)
- part of Bridge 0 (with Port E0)
Port E0/Port E1(1) (uplink/downlink)
Usage monitoring
E2 Secondary Usage interface
can be added
Secondary Usage monitoring port
(Out-of-band)

or
Secondary Usage monitoring port
(Inline)
- part of Bridge 1 (with Port E3)
Port E2/Port E3(1) (uplink/downlink)
Usage monitoring
E3 Secondary Usage interface
can be added
Secondary Usage monitoring port
(Inline)
- part of Bridge 1 (with Port E2)
Port E2/Port E3(1) (uplink/downlink)
Usage monitoring
E4 Physical interface
can be added
Secondary network connection port Connectivity to APM
Delivery monitoring
Experience monitoring
E5 Yes Primary network connection port Connectivity to APM
Delivery monitoring
Experience monitoring
E6 (10Gbps) Yes Primary Usage monitoring port
(Out-of-band)
Usage monitoring
E7 (10Gbps) r400 10Gbps interface
can be added
Secondary network connection port Connectivity to APM
Delivery monitoring
Experience monitoring
Console Yes Console
(Speed = 19200
Data bits = 8
Stop bits = 1
Parity = None
Flow control = XON/XOFF)
 

Footnotes:
1. Fail-to-wire ports. They will continue to pass traffic, even during a power failure.

r400 10Gbps transceivers: The r400 ships with two 10Gbps 850nm multi-mode transceivers: Finisar FTLX8571D3BCL. You can replace these with different types of 10Gbps SFP+ modules if required.

LEDs

The following diagram shows what the LEDs on the r400 indicate.

LED Pattern Meaning
Power Green solid Monitoring Point is powered on.
HDD Yellow flashing Data access activity.

Hardware specifications

Spec Sub-spec Value
Network connections
Wired 6 x 1 GigE
2 x 10 GigE (SFP+)
Wireless No
Wireless security N/A
Console port Yes
Storage 2 hours stored locally in case Monitoring Point is disconnected from APM
Power
Power supply IEC internal power supply
Power supply input 100 - 240VAC
50 - 60 Hz
Max current 4A-1.5A
Max power 400W
Dimensions
Width 438 mm (17.24")
Depth 292 mm (11.50")
Height 44 mm (1.73")(1 RU)
Weight 5 kg (11 lb)
Operating temperature 4°C - 27°C (40°F - 80°F)

Setup

Monitoring Point setup

Use the following steps to install the r400 in your network. The procedure creates a .zip file with the information necessary for the r400 to connect back to APM. The .zip file is then loaded onto the r400 using a USB stick. Once APM can communicate with the r400, additional features can be configured.

Use this procedure for initial setup only.
To reconfigure the r400, see Configure additional features.

Prerequisites

  • Determine the best place in your network to deploy the r400.
  • Configure your firewall rules to enable the r400 access to APM.
    • The r400 can still be installed and configured without this step, but monitoring is not possible until it is done.
  • A surge-protected power source.
  • A USB stick (blank, FAT32-formatted) is required for initial setup.

Connect to power

Connect the r400 to surge protected power using the power cable provided. The power LED should be on. If not, press the power switch.

Create an install file

To create the install (.zip) file:

  1. Log in to APM.
  2. Select an organization if you belong to more than one.
  3. If you’re setting up your first Monitoring Point, you’ll automatically be taken to the first step of the Add Monitoring Point wizard.
  4. If your organization already has Monitoring Points, navigate to > Manage Monitoring Points > Add Monitoring Points.
  5. Click AppNeta hardware.
  6. Click USB Configuration.
  7. Follow the instructions provided.
    • A .zip file is created.

Load the install file

To load the install (.zip) file on your r400:

  1. Copy the .zip file to your blank FAT32-formatted USB stick.
  2. Confirm that the r400 is powered on and in a ready state.
  3. Insert the USB stick into the r400. The r400 indicates that the USB stick has been inserted.
  4. Wait until the r400 is finished.
  5. Remove the USB stick.
    • The install file is loaded on your r400.

Connect to the network

To physically connect the r400 to the network:

  1. Verify that the switch you’ll be connecting to has its default port speed and duplex set to auto-negotiate.
  2. Using a standard Ethernet cable, connect the r400 to the switch using the r400’s network connection port (typically the Primary network connection port - E5) as follows:

Diagram showing an AppNeta Monitoring Point connected to a switch via the network connection port. The switch is connected to a router, the router to the internet, and the internet to APM.

Optional - Configure for web proxy

For networks that require internet traffic to be forwarded by a web proxy, the r400 must be configured to connect to your proxy server so that it can communicate with APM.

The proxy settings on the r400 only affect how it connects and reports data back to APM. These settings are not used for performance monitoring. If you are using Experience monitoring, you will also need to configure access to the proxy either when you create a web app group or after the web app group is created.

To configure for web proxy:

  1. Log in to Web Admin on the r400.
  2. Navigate to Monitoring Point Settings > Proxy.
  3. Enter proxy information:
    • Proxy Address - the IP address of the proxy server.
    • Proxy Port - the port the proxy server is listening on.
    • Username - a valid user name on the proxy server (if authentication/authorization is required). Only basic and digest authentication protocols are supported. NTLM and Kerberos are not supported.
    • Password - the password for the username specified (if authentication/authorization is required).
  4. Click Submit.
  5. Wait for the sequencer process to restart.
  6. Click Home.
  7. Verify that the device connected to APM.
    • The Monitoring Point Connected field should show “Yes”.

Assign a base license

Every r400 is sold with a base license that must be assigned to it in APM before it can be used.

  1. Within APM, navigate to > Manage Monitoring Points.
  2. Wait for the new r400 to show up in the list (you may need to refresh your screen).
    • The r400’s status should show “Connection Established” (Green circle with white check mark).
    • If it doesn’t appear after a few minutes, you’ll need to troubleshoot the problem.
  3. To assign it a base license, navigate to > Manage Licenses.
  4. In the Parent Organization drop-down (if visible), select the parent organization containing the r400.
  5. In the Organization drop-down, select the child organization containing the r400.
  6. Click the APM Monitoring Points tab in the bottom table.
  7. For the r400 you want to add the license to, select > Assign Licenses.
  8. In the Base License section, select a base license.
  9. Click Submit. The r400 is ready to use.

Optional - Assign add-on licenses

In addition to a base license, you can add N/A to the r400. Before they can be assigned, you need to purchase them. Once purchased, they will be added to your organization and available for assignment.

To assign an add-on license to the r400:

  1. Navigate to > Manage Licenses.
  2. In the Parent Organization drop-down, select the parent organization containing the r400.
  3. In the Organization drop-down, select the child organization containing the r400.
  4. Click the APM Monitoring Points tab in the bottom table.
  5. For the r400 you want to add the license to, select > Assign Licenses.
  6. In the Add-on Licenses section, specify the types and quantities of licenses you want to add.
  7. Click Submit.
    • The new capabilities are ready to use.

Set the location

When adding a new r400 to APM, you need to specify its location. This setting provides essential geographical context for the data that the r400 collects. Typically, you specify its location during the setup procedure.

If you are outside the setup procedure, you’ll need to edit its location:

  1. Navigate to > Manage Monitoring Points
  2. For the r400 you want to edit, select > Edit Location.
  3. Specify the location of the r400.
  4. Click OK.
    • The location is set.

Optional - Cable for Usage monitoring

In order to use Usage monitoring, the r400 must be cabled for it.

Cable the r400 for Usage monitoring using one of the following methods: Out-of-band or Inline

Cabling for Usage monitoring - out-of-band

Out-of-band Usage monitoring requires that your switch is capable of port mirroring and that a mirror source and a mirror destination (also known as Switched Port Analyzer (SPAN) ports) have been configured. The switch’s mirror source port is the one being monitored (typically the aggregation point). The switch’s mirror destination port is connected to a Usage monitoring port (Out-of-band) on the Monitoring Point.

  • On the r400, the Usage monitoring port (Out-of-band) is Port E0.

Diagram showing an AppNeta Monitoring Point connected to the Mirror destination port of a switch via the Usage Monitoring port (Out-of-band).

Cabling for Usage monitoring - inline

Inline Usage monitoring involves using a pair of “bypass” ports (Usage monitoring ports (Inline)) to connect the Monitoring Point inline with the switch port being monitored (typically the aggregation point). The “uplink” port of the pair is connected upstream. The “downlink” port of the pair is connected to the uplink port on the switch. Traffic flows through the Monitoring Point from one of the bypass ports to the other. Traffic will continue to flow even if the Monitoring Point loses power.

  • On the r400, the Usage monitoring port (Inline) uplink is Port E0 and the Usage monitoring port (Inline) downlink is Port E1.

Diagram showing an AppNeta Monitoring Point connected between a switch and a router via the Usage Monitoring - inline ports.

Optional - Configure additional features

Once the r400 is connected to your network, you can configure it further based on your needs.

Change default password

For security reasons, you should change the r400 password from its default.

Set up monitoring

At this point the r400 setup is complete. Continue the APM setup procedure at Set up performance monitoring.

Image and configuration files

File type File link
(click to download)
System image file System image
Configuration file Configuration package

Setup Guide - PDF

A printable setup guide is also available: r400 Setup Guide

Troubleshooting connectivity to AppNeta

Your r400 is properly connected to AppNeta Performance Manager (APM) when the status icon in > Manage Monitoring Points shows Green circle with white check mark.

If this is not the case, use the troubleshooting procedure below to help determine why it is not connecting.

Symptoms Things to check
The power LED is off. Check that the power button has been turned on.
  Check that the power cable is plugged in to the device and to a surge protected power source.
  Check that the power source is providing power.
The Primary network connection port (E5) LED is not blinking. Check that the r400 is connected to the network via the Primary network connection port (E5)
  Check that the cable is also connected to an L2 switch on the network.
The r400 status shows as Connection Lost () Check the r400 configuration (via USB) and verify that the following are as expected:
- Time On System - time and time zone must be correct.
- Address Assignment - should be “Dynamic” (for DHCP) or “Static”
- IP address
- Subnet Mask
- Default gateway
- DNS servers
- Sequencer Status - should be “Operational”
- Internet Connection - should be “Available”
- Server Connection Status - should be “Connection OK”
  Check the firewall configuration.
  If a proxy is being used, check the proxy configuration on the r400 (via Web Admin).
  If a proxy is being used, verify that the proxy is reachable from the network the r400 is on.
  If a proxy is being used, verify that the APM servers have been allowed in any access controls which may exist on the proxy.

If you are still unable to resolve the issue, read the Monitoring Point configuration then contact AppNeta Support.

Access

View Monitoring Point status

To view a Monitoring Point’s status in APM:

  • Within APM, navigate to > Manage Monitoring Points.
    • The Monitoring Point status is indicated by the icon in the left column.
Icon Status Description
Green circle with white check mark OK The Monitoring Point is connected to APM.
Black circle with white minus sign Connection Lost The Monitoring Point is not connected to APM. Troubleshoot the issue.

Additional statuses can be found in the Additional Status columns. Hover over the icons for details and/or actions to take.

Icon Status Description
Shared The Monitoring Point is shared between organizations.
Unlicensed The Monitoring Point is unlicensed.
Monitoring Point Error There is a Monitoring Point error.
Upgrade Available There is a software upgrade available for the Monitoring Point.

Determine the Monitoring Point hostname or IP address

Once the r400 has connected to APM, you can view its hostname and IP address.

  1. Log in to APM.
  2. Make sure you are using the correct organization
  3. Navigate to > Manage Monitoring Points.
  4. Click the r400 you want to connect to. In the right pane:
    • the Host Name field contains the hostname.
    • the Public IP field contains the public IP address. Use this if you are connecting to the r400 across the internet.
    • the Host Networking Details section contains the active r400 interfaces and the local IP address of each. Use this if you are connecting to the r400 locally.

Access credentials

The r400 is shipped with a set of default credentials: a single username and password. The username cannot be changed but you can change the password. If you change the password and then forget it, there is a procedure to reset it.

Default credentials

You need r400 credentials to log into Web Admin or use the Admin API.

The default credentials for the r400 are:

  • Default username: root
  • Default password: appneta.admin (previously password or AppNeta)

Changing Monitoring Point password

To secure Web Admin and Admin API access your r400, it is recommended that you change the password from its default.

  1. Log in to Web Admin.
  2. Click Change Root Password.
  3. Enter new password and click Set Password.

Resetting Monitoring Point password

If you forget your r400 password you can reset it.

  1. Download the r400 Configuration package from the image and configuration files.
  2. Extract the contents to the root of an empty, FAT32-formatted USB stick.
    • There should be no folders. All files must be at the root level.
  3. Open autorun.sh on the USB stick.
  4. Uncomment the following line and substitute ‘root’ and your desired password in place of ‘username’ and ‘userpasswd’, respectively. Enclose the password in single quotes if the password includes special characters. If the password itself includes a single quote, use backslash to escape it.

    # ./scripts/configureAccounts.sh change username userpasswd
    
  5. Save your changes.
  6. Make sure the r400 is ready.
  7. Insert the USB stick into the r400.
    • The r400 reads the configuration from the USB stick and indicates that it is doing so.
  8. Wait until the r400 is finished.
  9. Remove the USB stick.
    • The r400 configuration is updated.
    • Any problems updating the configuration are logged in the usb.log file on the USB stick.
  10. Log in to Web Admin using your new username and password.

Access via Web Admin

There are a few different methods to log into the Web Admin interface depending on its state.

The Monitoring Point is currently connected to APM

Log in via APM.

  1. Log in to APM.
  2. Make sure you are using the correct organization
  3. Navigate to > Manage Monitoring Points.
  4. Click the Monitoring Point you want to connect to.
  5. Click Launch Monitoring Point Web Admin… in the right side panel.
  6. Log in.
    • Use credentials for the r400.
    • If you are unable to login, see Can’t log in.

The Monitoring Point has been connected to APM in the past but is not connected now

Log in directly (hostname or IP address from APM).

  1. Determine the r400 hostname or IP address from APM.

  2. Enter the IP address or hostname in the address bar of your web browser - http://<hostname-or-ip>.

  3. Log in.

    • Use credentials for the r400.
    • If you are unable to login, see Can’t log in.

The Monitoring Point has never been connected to APM

Log in directly (hostname or IP address from USB).

  1. Extract the r400 configuration using a USB stick.
  2. Double-click the .html file on the USB stick to open it in a browser.
    • The System Host Name field contains the hostname.
    • The IP Address field contains the IP address.
  3. Enter the IP address or hostname in the address bar of your web browser - http://<hostname-or-ip>.

  4. Log in.
    • Use credentials for the r400.
    • If you are unable to login, see Can’t log in.

Can’t log in?

  1. Try using the default r400 credential.
  2. Make sure the device status is OK Green circle with white check mark.
  3. Make sure the device is upgraded to the latest software.

  4. Make sure you’re using http://.

  5. If using a hostname, try again using its IP.
  6. If using a public IP, verify that port forwarding is enabled on the device performing NAT.
  7. Make sure you created a firewall rule for our capture server.
  8. Power the r400 off then on.
  9. If you are still unable to login, open a support ticket.

Access via USB

You can use a USB stick on an r400 to perform the initial setup and to read its configuration. A USB stick can also be used to update the Monitoring Point configuration. You can also determine when the USB stick can be inserted, when the USB stick is inserted, when the USB stick can be removed, and what to check if there is no response to USB stick insertion.

Read configuration

You can read the r400’s configuration using a blank FAT32-formatted USB stick.

  1. Power on the r400 and wait until it is ready.
  2. Insert the USB stick into the r400.
    • The r400 writes the configuration to the USB stick and indicates that it is doing so.
  3. Wait until the r400 is finished.
  4. Remove the USB stick and insert it in your computer.
    • The configuration is on the .html file.

Configure Monitoring Point

You can configure the r400 for additional features using an blank FAT32-formatted USB stick.

  1. In Image and configuration files, select the link for the feature you are configuring.
  2. Edit the downloaded config file for your needs.
    • Uncomment sections to be used (if required).
    • Replace content in arrow brackets (no arrow brackets should remain).
  3. Copy the file onto a USB stick.
  4. Make sure the r400 is ready.
  5. Insert the USB stick into the r400.
    • The r400 reads the configuration from the USB stick and indicates that it is doing so.
  6. Wait until the r400 is finished.
  7. Remove the USB stick.
    • The r400 configuration is updated.
    • Any problems updating the configuration are logged in the usb.log file on the USB stick.

USB stick can be inserted

A USB stick can be inserted into the r400 when it is ready.

The r400 indicates it is ready when the LCD cycles through appliance information beginning with the hostname.

USB stick inserted

If you insert a USB stick into the r400 when it’s ready the LCD displays ‘USB Drive Detected’.

If the pattern does not change, see No response to USB insertion.

USB stick can be removed

When the r400 is finished with the USB stick it lets you know that it can be removed.

You can remove the USB stick when the LCD displays ‘Complete/remove USB drive’.

No response to USB insertion

If the r400 LED pattern does not change when you insert the USB stick:

  1. Make sure the r400 is powered on and ready to receive the USB stick before you insert it.
  2. Power the r400 off then on and try again.
  3. Try reformatting or using a different FAT32-formatted USB stick.
    • Not all disk utilities format FAT32 properly. We recommend trying a full format with Windows 7 or 8 rather than OSX.
    • Not all USB stick chipsets are compatible with the r400. We recommend trying one from a different manufacturer.
  4. Contact AppNeta Support for help.

Configure

Methods

AppNeta Performance Manager offers several tools to manage and configure the r400:

Configuration method Description
APM Some management and configuration capabilities are accessed from within APM via > Manage Monitoring Points. For example, changing Monitoring Point location or renaming the Monitoring Point.
Web Admin
(recommended)
This is a web interface hosted on the r400. Use it to manage and configure the r400. For example, restart networking, add static IPs, and VLAN tags.
USB Some r400 management and configuration capabilities can be executed using files on a USB stick. For example, reflashing the r400.

Basic settings

There are a few settings that should be configured on the r400 including Time zone, Location, and Name.

Time zone

There are two time zones that must be configured - your local time zone and the Monitoring Point time zone.

The Monitoring Point time zone is specified when the r400 is initially configured and it can be seen in APM by navigating to > Manage Monitoring Points.

Having the correct time zone on the r400 is important for a number of reasons:

  • In conjunction with the r400’s system time, it is required in order for the r400 to connect to APM. If the time is not correct, then there could be an issue with certificate validity checks when connecting.
  • It is required for monitoring results to be timestamped correctly.
  • It is required in order to display the correct time in path performance charts when Source Monitoring Point Time Zone is set.
  • It is required for alert conditions to be applied at the right time according to alert time ranges you have set.
Set time zone using Web Admin
  1. Log in to Web Admin
  2. Navigate to System Configuration > System Time > Set Time Zone.
  3. In the Change time zone to field, select the time zone the r400 is located in.
  4. Click Save.
    • The r400’s time zone is set accordingly.

Location

The location specified for the r400 is necessary for a variety of reports and charts.

The r400’s location is specified during the setup procedure but it can be edited at any time.

  1. Navigate to > Manage Monitoring Points
  2. For the Monitoring Point you want to edit, select > Edit Location.
  3. Specify the location of your Monitoring Point.
  4. Click OK.
    • The Monitoring Point’s location is set.

APM name and hostname

All Enterprise Monitoring Points (EMP) have two names: a hostname and an APM name. The hostname is used to identify the Monitoring Point on the network. The APM name is used to identify the Monitoring Point within APM. By default, both of these names are the same and are generated by APM. They are of the form: <device type>-<unique string>.

If you manually change the APM name, the hostname is not affected. If you change the hostname, the APM name is changed automatically unless the APM name was changed manually. In this case, changing the hostname does not affect the APM name.

Rename a Monitoring Point

To change the r400’s APM name:

  1. Navigate to > Manage Monitoring Points.
  2. For the r400 you want to rename, navigate to > Rename.
  3. Either select the default or specify a new name.
  4. Click Confirm.
    • The r400’s APM name is changed.
Change the hostname

When you change the r400’s hostname, the APM name is changed automatically unless the APM name was changed manually. In this case, changing the hostname does not affect the APM name.

To change the r400’s hostname:

  1. Log in to Web Admin.
  2. Navigate to Network Configuration > Change Host Name.
  3. In the Host Name field, add the new hostname.
  4. Click Save.
  5. Click Restart Networking.
    • The hostname and the APM name are changed.

Restricting Access

Access to the Monitoring Point can be restricted using TACACS+.

TACACS+

By default, the r400 supports a single Web Admin user that is authenticated using a locally stored password but it can also use TACACS+ to perform authentication. Once TACACS+ is enabled, any user configured on the TACACS+ server (including one having the username root) can log in via Web Admin. The local r400 username is not authenticated locally as long as TACACS+ is enabled.

Enable TACACS+
  1. Log in to Web Admin.
  2. Navigate to Web Admin Interface Configuration > Configure TACACS+ Authentication.
  3. In the Enable TACACS+ field, select Yes.
  4. Update the configuration as appropriate.
  5. Click Save.
    • TACACS+ is enabled.

Important: Test that users can be logged in via TACACS+ prior to logging out.

Disable TACACS+
  1. Log in to Web Admin.
  2. Navigate to Web Admin Interface Configuration > Configure TACACS+ Authentication.
  3. In the Enable TACACS+ field, select No.
  4. Click Save.
    • TACACS+ is disabled.
    • Use the local r400 username and password to log into Web Admin.

Networking

The following networking-related features can be configured on the r400.

Hostname

See APM Name and Hostname

Default interface

The default interface is the one the r400 uses to connect to APM. By default, it is the Primary network connection port (E5).

You can view the default interface or change it to a Secondary network connection port if necessary once it has been added.

View default interface
  1. Log in to Web Admin.
  2. In the Pathview Appliance Status section, the Default Network Interface shows the default interface.
Change default interface
  1. Log in to Web Admin.
  2. Click Network Configuration.
  3. In the Default Interface section, click Change.
  4. In the Default Interface field, select the interface you want to set as the default interface.
  5. Click Save.
  6. Restart networking.
  7. Connect the interface to your LAN with an Ethernet cable.
    • It will take several minutes before the Monitoring Point status shows as “Connection Established” in APM.

Physical interfaces

You can configure additional physical interfaces if required. You must set one as the default interface, which will be used for r400 connectivity, and use the other as the source interface for a network path.

On the r400, secondary Usage monitoring ports can also be configured.

For the purposes of configuration, an interface can be thought of as an interface name/address family pair. For example, eth0/IPv4 and eth0/IPv6 are separate interfaces.

Be careful not to put two interfaces on the same subnet.

Add a physical interface
  1. Complete device setup.
  2. Log in to Web Admin.
  3. Click Network Configuration.
  4. Click Add New Interface.
  5. Update the configuration as appropriate.
  6. Restart networking. You will briefly lose connectivity. The interface is operational when networking restarts.
Edit a physical interface configuration
  1. Log in to Web Admin.
  2. Click Network Configuration.
  3. For the interface you want to edit, click the interface name.
  4. Update the configuration as appropriate.
  5. Click Save.
  6. Restart networking. You will briefly lose connectivity. The interface is reconfigured when networking restarts.
Delete a physical interface
  1. Log in to Web Admin.
  2. Click Network Configuration.
  3. For the interface you want to delete, click Delete Interface.
  4. Restart networking. You will briefly lose connectivity. The interface is deleted when networking restarts.

VLAN interfaces

802.1Q VLAN tagging can be enabled on the r400 by adding a VLAN interface type to an Ethernet port.

Add a VLAN interface

Video - A video is available for both APM Public and APM Private users that shows how to add a VLAN interface to a Monitoring Point.

  1. Complete device setup.
  2. Log in to Web Admin.
  3. Click Network Configuration.
  4. Click Add VLAN tagged interface.
  5. Make your changes.
  6. Restart networking. The interface is operational when networking restarts.
Edit a VLAN interface configuration
  1. Log in to Web Admin.
  2. Click Network Configuration.
  3. For the interface you want to edit, click the interface name.
  4. Update the configuration as appropriate.
  5. Click Save.
  6. Restart networking. You will briefly lose connectivity. The interface is reconfigured when networking restarts.
Delete a VLAN interface
  1. Log in to Web Admin.
  2. Click Network Configuration.
  3. For the interface you want to delete, click Delete Interface.
  4. Restart networking. You will briefly lose connectivity. The interface is deleted when networking restarts.

Interface - Addressing

After you create an interface the next step is to set up the interface addressing using either dynamic and/or static IP addresses.

The r400 supports configuring either DHCP or a single static IP address on an interface and only supports IPv4 addressing.

Potential loss of connectivity: Care must be taken when changing the IP address configuration on the primary network connection. If the new address is in a different subnet than the old one, you will lose network connectivity to the r400 after restarting networking.

View addressing
  1. Log in to Web Admin
  2. Click Network Configuration.
  3. Click on the interface you are interested in.
  4. The Address Source field shows the interface address.
Add addressing

At least one IP address (either static or dynamic) must be configured on an interface.

  1. Log in to Web Admin
  2. Click Network Configuration.
  3. Click on the interface you are interested in.
  4. For DHCP, in the Address Source field, select From DHCP.
  5. For a static IP address, in the Address Source field, select Static configuration.
    • In the IP Address field, add the static IP address (e.g., 192.168.1.1).
    • In the Netmask field, add the netmask (e.g., 255.255.255.0).
  6. Click Save.
  7. Click Restart Networking.
Edit addressing
  1. Log in to Web Admin
  2. Click Network Configuration.
  3. Click on the interface you are interested in.
  4. In the Address Source field, edit the IP Address and Netmask fields as appropriate.
  5. Click Save.
  6. Click Restart Networking.
Delete addressing
  1. Log in to Web Admin
  2. Click Network Configuration.
  3. Click on the interface you are interested in.
  4. In the Address Source field, select From DHCP. The interface address and netmask will be obtained from DHCP.
  5. Click Save.
  6. Click Restart Networking.

Interface - DNS

The Domain Name System (DNS) is essential internet functionality used for resolving domain names to IP addresses. When the target of a network or web path is identified by a domain name rather than by an IP address, the r400 uses DNS to resolve the target’s IP address.

How name servers are selected

Typically, the IP addresses of DNS name servers are configured within DHCP so, if the r400 uses DHCP, those name servers are available to it. Additional name server addresses can also be configured directly on a per address basis on r400 interfaces.

When a network or web path is initiated from the r400, a DNS request is made. It must determine which name servers to pass the DNS request to. If there are one or more name servers configured on the address the path is initiated from (either configured directly on the interface address or returned via DHCP), only those servers are used. If no name servers are configured on the interface address or returned by a DHCP server servicing the interface, then all name servers known to the r400 are used.

From the r400’s perspective, all name servers are considered equivalent. So, when a name resolution is required, the request is forwarded to the appropriate name servers. The first response received is used.

In cases where name servers are not equivalent (typically when providing sub-domain name resolution), this behavior may result in an incorrect name resolution. For example, a name server that cannot resolve a name may respond first with a negative result. This result is used by the r400 despite it receiving a positive result later on. In these instances, you want to associate a name server with a DNS Search Domain so that all requests for a given domain are forwarded to a specific name server (or set of servers).

View DNS configuration
  1. Log in to Web Admin.
  2. Click Network Configuration. The DNS configuration is displayed in the DNS section.
Add/Edit DNS configuration
  1. Log in to Web Admin.
  2. Click Network Configuration.
  3. Click on Configure DNS.
  4. Update the configuration as appropriate.
  5. Click Save.
  6. Restart networking.
Delete DNS configuration
  1. Log in to Web Admin.
  2. Click Network Configuration.
  3. Click on Configure DNS.
  4. Update the configuration as appropriate.
  5. Click Save.
  6. Restart networking.

Interface - Transmission Parameters

In general, transmission parameters (Maximum Transmission Unit (MTU), Auto negotiation, Speed, and Duplex) use default values but can be changed if necessary.

View transmission parameters
  1. Log in to Web Admin
  2. Click Network Configuration.
  3. Click on the interface you are interested in.
  4. Click Advanced Settings (at the bottom of the page). The advanced configuration parameters appear (Duplex and Speed and MTU).
Edit transmission parameters
  1. Log in to Web Admin
  2. Click Network Configuration.
  3. Click on the interface you are interested in.
  4. Click Advanced Settings (at the bottom of the page). The transmission parameters appear (Duplex and Speed and MTU).
  5. Update the transmission parameters as required.
  6. Click Save.
  7. Click Restart Networking.

Interface - Static Routes

Depending on where a Monitoring Point is deployed, you may need to add static routes. Static routes are configured per interface.

Add static routes
  1. Complete Monitoring Point setup.
  2. Log in to Web Admin
  3. Click Network Configuration.
  4. In the Routing section, click Add Static Route.
  5. Update the fields as appropriate.
  6. Click Save.
  7. Restart networking.
    • The static route can be used.
Edit static routes

To edit a static route you need to delete the route then add it again with a changed configuration.

Delete static routes
  1. Log in to Web Admin
  2. Click Network Configuration.
  3. In the Routing section, for the route you want to delete, click Delete Route.
  4. Restart networking.
    • The static route deletion is complete.

NTP

By default the r400 uses NTP to keep the clock accurate. A set of default NTP servers is pre-configured and additional servers can be added.

List currently configured NTP servers
  1. Log in to Web Admin.
  2. Navigate to System Configuration > System Time.
    • The Set NTP time server field contains a list of the currently configured NTP servers.
Add an NTP server
  1. Log in to Web Admin.
  2. Navigate to System Configuration > System Time.
  3. In the Set NTP time server field, enter each NTP server on a new line.
  4. Click Apply NTP.
  5. Click OK.
    • The NTP servers are added to the list.
Delete an NTP server
  1. Log in to Web Admin.
  2. Navigate to System Configuration > System Time.
  3. In the Set NTP time server field, delete any NTP servers you want deleted.
  4. Click Apply NTP.
  5. Click OK.
    • The NTP servers are removed from the list.

Web proxy

For networks that require internet traffic to be forwarded by a web proxy, the r400 must be configured to connect to your proxy server so that it can communicate with APM.

The proxy settings on the r400 only affect how it connects and reports data back to APM. These settings are not used for performance monitoring. If you are using Experience monitoring, you will also need to configure access to the proxy either when you create a web app group or after the web app group is created.

  1. Log in to Web Admin.
  2. Navigate to Appliance Configuration > Proxy Configuration.
  3. Enter proxy information:
    • Proxy Address - the IP address of the proxy server.
    • Proxy Port - the port the proxy server is listening on.
    • Proxy Username - a valid user name on the proxy server (if authentication/authorization is required). Only basic and digest authentication protocols are supported. NTLM and Kerberos are not supported.
    • Proxy Password - the password for the username specified (if authentication/authorization is required).
  4. Click Save.
  5. Wait for the sequencer process to restart.
  6. Click Home.
  7. Verify that the device connected to APM. In the Sequencer Status pane, Server connections should show “Connected to

Usage monitoring

The following Usage monitoring related features can be configured on the r400.

Usage monitoring ports

The r400 comes with ports E0, E1, and E6 (10 Gbps) preconfigured as the “Primary Usage monitoring ports”. Ports E2 and E3 are designated as “Secondary Usage monitoring ports”. These not preconfigured and must be added before they can be used. You can edit the configuration of secondary Usage monitoring port pairs to change between out-of-band monitoring and inline monitoring. To disable a secondary Usage monitoring port you can delete it.

Add a secondary Usage monitoring port

Video - A video is available for both APM Public and APM Private users that shows how to add a secondary Usage monitoring port via the Web Admin or the Admin API.

  1. Log in to Web Admin.
  2. Click Network Configuration.
  3. Click Add New Interface.
  4. For out-of-band Usage monitoring:
    1. In Interface Type, select Mirror Input.
    2. In Interface Name, select the interface (if more than one is available).
    3. Click Create.
  5. For inline Usage monitoring:
    1. In Interface Type, select Bridge.
    2. Click Create.
  6. Restart the Monitoring Point. The interface is operational when networking restarts.
Edit a secondary Usage monitoring port configuration

To edit a secondary Usage monitoring port configuration, you need to delete the port then add it again with a changed configuration.

Delete a secondary Usage monitoring port
  1. Log in to Web Admin.
  2. Click Network Configuration.
  3. For the interface you want to delete, click Delete Interface.
  4. Restart networking. The interface is deleted when networking restarts.

Name Capture Interfaces

The r400 can run Usage monitoring on two interfaces concurrently. Give each interface a meaningful name so that there’s no confusion when starting and stopping Usage monitoring.

To name a capture interface:

  1. Navigate to > Manage Monitoring Points.
  2. For the Monitoring Point you are interested in, select > Name Capture Interfaces.
  3. In the Name field, enter the new capture interface name.
  4. Click Submit.
    • The interface name is changed.

Packet Capture Passphrase

The passphrase is used to encrypt your .pcap files generated by Packet Capture. While the passphrase is required to download capture files, it is not required to view packet capture analysis of capture files through APM. Remember the passphrase. If you lose it you can reset it, but you cannot download any captures encrypted with the old passphrase.

Determine if a passphrase is configured
  1. Log in to Web Admin.
  2. Navigate to Appliance Configuration > Capture Passphrase Configuration.
    • If there is a passphrase configured, you will receive a warning message saying that a passphrase is already configured for the device.
Set the passphrase

Setting the passphrase is required in order to perform packet captures.

  1. Log in to Web Admin.
  2. Navigate to Appliance Configuration > Capture Passphrase Configuration.
  3. In the Passphrase field, enter your passphrase.
  4. In the Confirm Passphrase field, re-enter your passphrase.
  5. Click Set Passphrase.
    • The passphrase it set.
  6. Click OK.
Clear the passphrase

This function is included in device setup and decommission, so you will likely never need to use it explicitly.

  1. Log in to Web Admin.
  2. Click Appliance Configuration.
  3. Click Clear Passphrase.
  4. Click OK.
    • The passphrase is cleared.

Packet Capture Analysis

The r400 provides limited packet capture analysis by default. You can enable or disable this analysis if desired.

Enable packet capture analysis
  1. Log in to Web Admin.
  2. Navigate to Appliance Configuration > Capture Analysis Configuration.
  3. Select Perform analysis of captures generated by this PathView Appliance.
  4. Click Save.
    • Packet capture analysis is enabled.
Disable packet capture analysis
  1. Log in to Web Admin.
  2. Navigate to Appliance Configuration > Capture Analysis Configuration.
  3. Select Do not perform analysis of captures generated by this PathView Appliance.
  4. Click Save.
    • Packet capture analysis is disabled.

Other Services

The following can also be configured on the r400.

SNMP

The r400’s read-only SNMP community string is provided when the r400 is queried by an NMS. By default, the string is either ‘AppNeta’ (for software version 9.10.0 or higher) or ‘public’ (for all other software versions).

Note that SNMP v2 is supported. SNMP v3 is not supported.

You can change the community string as follows:

  1. Log in to Web Admin
  2. Navigate to Appliance Configuration > SNMP Configuration.
  3. In the Read Community String field, enter the new community string.
  4. Click Save. The snmpd service is restarted and the change is applied.

Manage

Restart

Restarting the r400 will disrupt its connection to APM but it does not affect its software or its configuration.

To restart the r400:

  1. Log in to Web Admin.
  2. Click Restart Appliance.
  3. Click OK.
    • Access is lost while the r400 restarts.

Restart networking

Restarting networking on the r400 will disrupt its connection to APM but it does not affect its software or its configuration.

To restart networking on the r400:

  1. Log in to Web Admin.
  2. Navigate to Network Configuration.
  3. Click Restart Networking.
    • Access is lost while the networking system restarts.

Shutdown

To shut down the r400, power it off.

Delete

Deleting the r400 from an organization is typically done when you are moving it to another organization or freeing up its base license so it can be used by another Monitoring Point.

Deleting the r400 has the following effects:

  • All paths where the r400 is the source (and the monitoring history related to those paths) are deleted (though they can be moved to another Monitoring Point during the delete process).
  • All Usage monitoring data related to the r400 is deleted.
  • Tests, assessments, and packet captures are not deleted.
  • The base license and any add-on licenses that were assigned to the r400 become available again.
  • If the Monitoring Point has a legacy Usage-based license assigned to it, the license is deleted.
  • Access to the r400 from APM is lost.
  • The r400 is decommissioned. This resets the APM connection configuration on the r400.
  • In order to use the r400 again you need to redo the setup procedure.

    To delete the r400 from your organization:

  1. Navigate to > Manage Monitoring Points.
  2. For the r400 you want to delete, select > Delete.
    • You will be prompted to confirm this action, and optionally to move all affected paths to another Monitoring Point.

Manage software

There are a number of procedures to help manage the software running on the r400:

The effects of these procedures are summarized in the following table:

Procedure Software change? Network config change? APM access config change?
Upgrade software Y (latest software) N N
Reflash (USB image) Y (USB image) N N
Decommission N N Y (factory)(no APM access)
Reset to factory defaults (local image) Y (local image) Y (factory) Y (factory)(no APM access)
Reset to factory defaults (USB image) Y (USB image) Y (factory) Y (factory)(no APM access)

Upgrade software

AppNeta recommends keeping your r400 software up to date to take advantage of the latest features and bug fixes. You will see the Upgrade Available symbol () appear on the Monitoring Points page when the r400 is no longer running the latest software version.

You can configure APM to upgrade the r400 automatically or you can upgrade it manually from APM at any time.

Note that the upgrade process can result in a gap of up to 15 minutes of monitoring history. Also note that the r400 must be connected to APM in order for an upgrade to complete successfully.

Upgrade type

You can see which upgrade options are available on the Monitoring Points page.

To see the Upgrade Type currently assigned to your r400:

  1. Within APM, navigate to > Manage Monitoring Points.
  2. The Upgrade Type column shows the upgrade type. These include:
    • Manual - Upgrades are to be performed manually (no automation).
    • Managed - Upgrades are to be performed automatically when new software is released. This enables you to have the latest software running at all times. The software upgrade schedule is listed on the AppNeta service status page: http://status.appneta.com/.
    • Scheduled - Upgrades are to be performed automatically on a regularly scheduled interval. This enables you to schedule upgrades during your regular network maintenance window. You also have the option of skipping the next upgrade.
Configure upgrade automation

To configure Monitoring Point upgrade automation:

  1. Within APM, navigate to > Manage Monitoring Points.
  2. To configure a single Monitoring Point, select > Upgrade Settings next to the Monitoring Point you want to configure.
  3. To configure multiple Monitoring Points:
    1. Use the check boxes on the left to select the Monitoring Points to configure.
    2. In the Action drop-down, select Upgrade Settings.
  4. From the Upgrade Type drop-down, select the type of upgrade automation you want to use.
    • If you select Scheduled you will need to specify the upgrade schedule (Note: The upgrade schedule is based on the Monitoring Point time zone).
    • Start Date - The first day of the upgrade schedule.
    • Start Time - The start of the upgrade window.
    • Duration - The length of the upgrade window. Upgrades can only occur during the upgrade window.
    • Repeat - The period between the start of each upgrade window.
    • Skip next upgrade - Skip the next upgrade.
  5. Click Confirm. The Monitoring Point upgrade automation is set.
Manual upgrade

The upgrade process can be performed manually at any time to the Monitoring Point model no matter which of the upgrade automation settings is selected.

To upgrade Monitoring Point software to the latest release:

  1. Within APM, navigate to > Manage Monitoring Points.
  2. For the Monitoring Point you want to upgrade, select > Upgrade Now.
  3. Click OK.
    • The Monitoring Point software is upgraded to the latest release.

The Upgrade Now option is also available in the Action drop-down. Use this feature to upgrade multiple Monitoring Points at the same time.

Failed upgrade?

If an upgrade attempt fails, try the following:

  1. Retry the upgrade.
  2. Restart the r400 then retry the upgrade.
  3. Physically power the r400 off for 10 seconds then back on and retry the upgrade.
  4. Reflash the r400 using the latest image.

If you are still unsuccessful, contact AppNeta Support.

Reflash - USB image

Reflashing the r400 (USB image) involves rewriting the r400 file system with a software image downloaded to a USB stick. All configuration information is saved during a reflash. Also, the locally stored image is replaced by the downloaded image. This procedure is typically only required when upgrading the local system image or troubleshooting a problem on the r400.

Reflash using a USB stick

To reflash a r400 with a downloaded image using a USB stick:

  1. Download the System image file for the r400.

  2. Extract the contents to the root of an empty, FAT32-formatted USB stick. There should be no folders. All files must be at the root level.
  3. Edit the autorun.sh file with a text editor.
  4. Remove the “#” from the beginning of the RESTORE_SETTINGS="yes" line. This preserves the network and APM access configuration.
  5. Save the file.
  6. Make sure the r400 is powered on and ready to accept a USB stick.
  7. Insert the USB stick into the device.
  8. The device indicates that the USB stick is inserted.
  9. Wait until the device indicates that it is ready and the USB stick can be removed. This should be less than 15 minutes.
    • The r400 reflashes with the downloaded image. Connectivity to the r400 is lost during the reflash procedure.

Decommission

Decommissioning the r400 resets its APM access configurations but does not affect its network configuration (for example, its hostname, IP address, and any static routes) or the software it is running.

After decommissioning, the r400 is not accessible on the network. Its status will show as disconnected. Any paths and monitoring data are not removed from your organization until you delete it.

To use the r400 again, you should follow the Migrating Monitoring Between EMPs procedure if you are replacing a failed r400 or the Getting Started procedure to set up the r400 as a new device within APM.

  1. Log in to Web Admin.
  2. Click Appliance Configuration.
  3. Click Decommission PathView Appliance.
  4. Click OK. The r400 restarts with a factory APM access configuration.

Reset to factory defaults - local image

Resetting to factory defaults using a local image resets both the network and APM access configurations and reflashes the Monitoring Point using a software image stored locally on the device.

After resetting to factory defaults, the Monitoring Point is not accessible on the network. Its status will show as disconnected.

To use the Monitoring Point again, you should follow the Migrating Monitoring Between EMPs procedure if you are replacing a failed Monitoring Point or the Getting Started procedure to set up the Monitoring Point as a new device within APM.

Reset using Web Admin

To reset the r400 to factory defaults and the local image using Web Admin:

  1. Log in to Web Admin.
  2. Click System Configuration.
  3. Click Reset to Factory Defaults.
  4. Click OK. The r400 restarts using the local system image and factory configurations. Access to the r400 is lost.

Reset using the reset button

To reset the r400 to factory defaults and the local image, using the end of a paper clip, press the F/D button (located in a small hole to the left of the Ethernet ports on the front panel) for 15 seconds. Follow the prompts on the LCD.

Reset to factory defaults - USB image

Resetting to factory defaults using a downloaded image resets both the network and APM access configurations and reflashes the r400 using a software image downloaded onto a USB stick. It also updates the local system image.

After resetting to factory defaults, the r400 is not accessible on the network. Its status will show as disconnected.

To use the r400 again, you should follow the Migrating Monitoring Between EMPs procedure if you are replacing a failed Monitoring Point or the Getting Started procedure to set up the r400 as a new device within APM.

To reset the r400 to factory defaults and a downloaded image using a USB stick:

  1. Download the System image file for the r400.

  2. Extract the contents to the root of an empty, FAT32-formatted USB stick.
  3. Make sure the r400 is powered on and ready to accept a USB stick.
  4. Insert the USB stick into the r400.
  5. The r400 indicates that the USB stick is inserted.
  6. Wait until the r400 indicates that it is ready and the USB stick can be removed. This should be less than 15 minutes.
    • The r400 restarts using the downloaded system image and factory configurations. Access to the r400 is lost.

Migrate monitoring

See Migrate Monitoring between Monitoring Points.

Share

See Sharing a Monitoring Point.

Move between orgs

You can move the r400 from one organization to another but any paths and monitoring history associated with it are not moved. These can, however, be moved to another Monitoring Point in the old organization. You need to be an Organization Admin or Advanced user in the old and new organizations in order to move the r400 between them.

To move the r400 between organizations:

Step 1: Download the nis.config file for the new organization

The nis.config file is used to associate a Monitoring Point with an organization. It is normally configured as part of a Monitoring Point setup but it can be obtained independent of the setup procedure in order to associate a Monitoring Point with a different organization.

To download the nis.config file for the new organization:

  1. Change organization to the new organization.
  2. Navigate to > Manage Monitoring Points > Add Monitoring Points > AppNeta hardware > Direct Connect.
  3. Click Download File.
    • The nis.config file is downloaded to your computer.
Step 2: Update with the new nis.config settings
  1. Change organization to the old organization.
  2. Log in to Web Admin on the r400.
  3. Decommission the r400.
    • When the r400 is decommissioned you can no longer access it via APM. You need to use it’s hostname or IP address to access it.
  4. Log in to Web Admin on the r400 using its hostname or IP address.
  5. Navigate to Appliance Configuration > PathView Cloud Configuration.
  6. Click Choose File.
  7. Select the downloaded “<org-name>_nis.config” file.
  8. Click Save.
  9. Click OK.
    • The r400 restarts. Once restarted, it will be associated with the new organization.
Step 3: Finalize the move to the new organization

When a new Monitoring Point initially connects to an organization in APM it needs to be licensed and have its location specified. At that point it is available in the new organization and new paths can be created or existing paths can be moved to it.

To finalize the r400’s move to a new organization:

  1. In APM, change organization to the new organization.
  2. If prompted, specify the r400 licensing. Otherwise, assign a base license and any add-on licenses required.
  3. If prompted, specify the r400 location. Otherwise, set the location directly.
Step 4: Clean up the old organization

Moving a Monitoring Point to a new organization does not remove it from the old organization. From the perspective of the old organization, the Monitoring Point is simply disconnected. All paths and monitoring history are still available in the old organization.

To clean up the r400 from the old organization:

  1. Change organization to the old organization.
  2. If you want to preserve the paths and the associated monitoring history:
    1. Migrate old paths to another Monitoring Point.
  3. Once there are no more paths associated with the r400 (or you don’t care if they are deleted), delete the Monitoring Point from the old organization.