Monitoring Point Specifications

If the Monitoring Point you’re looking for is not listed here, check out the Monitoring Points - Legacy page.

m35

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

m35 wireframe diagrams

Front view:

Rear view:

m35 port descriptions

The following table shows what each port on the Monitoring Point is used for. Maximum port speed is 1Gbps.

Port #	Preconfigured?	Port type	Used for
E0	Yes	Primary network connection port	Connectivity to APM Delivery monitoring Experience monitoring
E1	Physical interface can be added	Secondary network connection port	Connectivity to APM Delivery monitoring Experience monitoring
E2	—	—	Unused
E3	—	—	Unused
E4	Yes	Primary Usage monitoring port (Inline) - part of Bridge 0 (with Port E5) Port E5/Port E4(1) (uplink/downlink)	Usage monitoring
E5	Yes	Primary Usage monitoring port (Out-of-band) or Primary Usage monitoring port (Inline) - part of Bridge 0 (with Port E4) Port E5/Port E4(1) (uplink/downlink)	Usage monitoring
WiFi	Wireless interface can be added	Secondary network connection port	Connectivity to APM Delivery monitoring Experience monitoring
Console	Yes	Console (Speed = 115200 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.

m35 LEDs

The following diagram shows what the LEDs on the Monitoring Point indicate.

m35 hardware specifications

m35 image and configuration files

File type	File link
System image file	System image
Configuration files	Reset device Wireless interface DHCP interface Static IP interface Additional static IP addresses VLAN interface Reset password

m35 setup guide - PDF

A printable setup guide is also available: m35 Setup Guide

m50

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

m50 wireframe diagrams

Front view:

Rear view:

m50 port descriptions

The following table shows what each port on the Monitoring Point is used for. Maximum port speed is 1Gbps.

Port #	Preconfigured?	Port type	Used for
0	Yes	Primary network connection port	Connectivity to APM Delivery monitoring Experience monitoring
1	Physical interface can be added	Secondary network connection port	Connectivity to APM Delivery monitoring Experience monitoring
2	Yes	Primary Usage monitoring port (Out-of-band) or Primary Usage monitoring port (Inline) - part of Bridge 0 (with Port 3) Port 2/Port 3(1) (uplink/downlink)	Usage monitoring
3	Yes	Primary Usage monitoring port (Inline) - part of Bridge 0 (with Port 2) Port 2/Port 3(1) (uplink/downlink)	Usage monitoring
WiFi	Wireless interface can be added	Secondary network connection port	Connectivity to APM Delivery monitoring Experience monitoring
Console	Yes	Console (Speed = 115200 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.

m50 LEDs

The following diagram shows what the LEDs on the Monitoring Point indicate.

m50 hardware specifications

m50 image and configuration files

File type	File link
System image file	System image
Configuration files	Reset device Wireless interface DHCP interface Static IP interface Additional static IP addresses VLAN interface Reset password

Connecting the m50 - PDF

A printable setup guide is also available: Connecting the m50

Safety and Regulatory

Safety and Regulatory guides include:

• General Safety Guidelines
• Regulatory Information

m70

The AppNeta m70 Enterprise Monitoring Point is used for monitoring in small office environments. Two variants are available: with wireless and without wireless. A full list of features can be found on the Monitoring Point Feature Comparison page.

m70 wireframe diagrams

Front view:

Note: The m70 variant without wireless has no wifi antenna connections.

Rear view:

Note: The m70 variant without wireless has no wifi antenna connections.

m70 port descriptions

The following table shows what each port on the Monitoring Point is used for. Maximum port speed is 1Gbps.

Port #	Preconfigured?	Port type	Used for
0	Yes	Primary network connection port	Connectivity to APM Delivery monitoring Experience monitoring
1	Physical interface can be added	Secondary network connection port	Connectivity to APM Delivery monitoring Experience monitoring
2	Yes	Primary Usage monitoring port (Out-of-band) or Primary Usage monitoring port (Inline) - part of Bridge 0 (with Port 3) Port 2/Port 3(1) (uplink/downlink)	Usage monitoring
3	Yes	Primary Usage monitoring port (Inline) - part of Bridge 0 (with Port 2) Port 2/Port 3(1) (uplink/downlink)	Usage monitoring
4	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 5) Port 4/Port 5(1) (uplink/downlink)	Usage monitoring
5	Secondary Usage interface can be added	Secondary Usage monitoring port (Inline) - part of Bridge 1 (with Port 4) Port 4/Port 5(1) (uplink/downlink)	Usage monitoring
WiFi (x4) (only on wireless variant)	Wireless interface can be added	Secondary network connection port	Connectivity to APM Delivery monitoring Experience monitoring
Console	Yes	Console (Speed = 115200 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.

m70 LEDs

The following diagram shows what the LEDs on the Monitoring Point indicate.

m70 hardware specifications

m70 image and configuration files

File type	File link
System image file	System image
Configuration files	Reset device Wireless interface (only applicable to wireless variant) DHCP interface Static IP interface Additional static IP addresses VLAN interface Reset password

Connecting the m70 - PDF

Printable setup guides are also available:

• Wireless variant: Connecting the m70
• No wireless variant: Connecting the m70

Safety and Regulatory

Safety and Regulatory guides include:

• General Safety Guidelines
• Regulatory Information

r90

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

r90 wireframe diagrams

Front view:

Rear view:

r90 port descriptions

The following table shows what each port on the Monitoring Point is used for. Maximum port speed is 1Gbps except where specified.

Port #	Preconfigured?	Port type	Used for
0	Yes	Primary network connection port	Connectivity to APM Delivery monitoring Experience monitoring
1	Secondary Usage interface can be added	Secondary Usage monitoring port (Out-of-band) or Secondary Usage monitoring port (Inline) - part of Bridge 0 (with Port 2) Port 1/Port 2(3) (uplink/downlink)	Usage monitoring(2)
2	Secondary Usage interface can be added	Secondary Usage monitoring port (Inline) - part of Bridge 0 (with Port 1) Port 1/Port 2(3) (uplink/downlink)	Usage monitoring(2)
3 (10Gbps)(1)	Yes	Primary Usage monitoring port (Out-of-band)	Usage monitoring(2) (Can be converted to Delivery/Experience)
4 (10Gbps)(1)	r90 10Gbps interface can be added	Secondary network connection port	Connectivity to APM Delivery monitoring Experience monitoring
5	Yes	Primary Usage monitoring port (Out-of-band) or Primary Usage monitoring port (Inline) - part of Bridge 1 (with port 6) Port 5/Port 6(3) (uplink/downlink)	Usage monitoring(2)
6	Yes	Primary Usage monitoring port (Inline) - part of Bridge 1 (with port 5) Port 5/Port 6(3) (uplink/downlink)	Usage monitoring(2)
Console	Yes	Console (Speed = 115200 Data bits = 8 Stop bits = 1 Parity = None Flow control = XON/XOFF)

Footnotes:
1. These SFP+ ports support a wide range of 10GBASE PHYs, both electrical and optical.
2. Only two of the Usage ports or port pairs should be in use at the same time.
3. Fail-to-wire ports. They will continue to pass traffic, even during a power failure.

Supported SFP/SFP+ modules

There are a number of SFP/SFP+ modules supported on ports 3 and 4.

Supported module types: 1000BASE-SR, 1000BASE-LR, 10GBASE-T, 10GBASE-SR, and 10GBASE-LR
Unsupported module types: 1000BASE-T

AppNeta has validated the following 10G modules:

• Finisar FTLX1471D3BCL (10GBASE-LR)
• Finisar FTLX8574D3BCL (10GBASE-SR)
• FluxLight SFP-10G-T (10GBASE-T)

r90 LEDs

The following diagram shows what the LEDs on the Monitoring Point indicate.

r90 hardware specifications

r90 image and configuration files

File type	File link
System image file	System image
Configuration files	Reset device DHCP interface Static IP interface Additional static IP addresses VLAN interface Reset password

Connecting the r90 - PDF

A printable setup guide is also available: Connecting the r90

Safety and Regulatory

Safety and Regulatory guides include:

• General Safety Guidelines
• Regulatory Information

r1000

The AppNeta r1000 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.

r1000 wireframe diagrams

Front view:

Rear view:

r1000 port descriptions

The following table shows what each port on the Monitoring Point is used for.

Port #	Preconfigured?	Port type	Used for
0 (10Gbps)	Yes	Primary network connection port	Connectivity to APM Delivery monitoring Experience monitoring
1 (10Gbps)	Yes	Primary Usage monitoring port (Out-of-band)	Usage monitoring (Can be converted to Delivery/Experience)
2 (QSFP)(1)	Yes	Secondary network connection port	Connectivity to APM Delivery monitoring Experience monitoring
3 (QSFP)(1, 2)	Yes	Secondary Usage monitoring port (Out-of-band)	Usage monitoring (Can be converted to Delivery/Experience)
Console	Yes	Console (Speed = 115200 Data bits = 8 Stop bits = 1 Parity = None Flow control = XON/XOFF)

Footnotes:
1. These ports are QSFP slots and require a QSFP module.
2. Usage monitoring is only supported to 10Gbps.

40/100Gbps network support limitations

On 40Gbps and 100Gbps networks, there are a few points to be aware of:

1. In order to achieve accurate capacity measurements, the MTU size is important. For 100Gbps networks, use a 9000-byte MTU. For 40Gbps networks, use a minimum 4000-byte MTU.
2. On 100Gbps networks, the maximum “Total Capacity” we can detect is approximately 96Gbps (on a dual-ended path, approximately 85Gbps on a single-ended path) rather than 99.58Gbps (maximum capacity with 9000-byte MTU taking packet overhead into consideration), so the “Total Capacity” on Delivery monitoring performance charts will show a maximum of 96Gbps even if the network is capable of 99.58Gbps. For Diagnostics tests, the maximum “Total Capacity” measurement is approximately 50Gbps for both dual- and single-ended paths.
3. On idle 100Gbps networks you may see average network utilizations of approximately 2Gbps. This shows as “Utilized Capacity (avg)” on Delivery monitoring performance charts. For networks with traffic this is not an issue and measurements are accurate.
4. Using PathTest with TCP, the maximum load generated is 37Gbps.

Supported SFP/SFP+/SFP28/QSFP/QSFP28 modules

A wide range of SFP/SFP+/SFP28/QSFP/QSFP28 modules (both optical and electrical) are supported on ports 2 and 3.

AppNeta has validated the following 40G QSFP+ modules:

• FluxLight (CISCO-OEM) QSFP-40G-SR4
• Mellanox MMA1B00-B150D (40G SR4)

and the following 100G QSFP28 modules:

• Arista QSFP-100G-CWDM4
• Juniper JNP-QSFP-100G-SR4
• Mellanox MMA1B00-C100D (100G SR4)
• Mellanox MMA1L30-CM (100G CWDM4)

r1000 LEDs

The following diagram shows what the LEDs on the Monitoring Point indicate.

r1000 hardware specifications

r1000 image and configuration files

File type	File link
System image file	System image
Configuration files	Reset device DHCP interface Static IP interface Additional static IP addresses VLAN interface Reset password

r1000 power supply replacement

The r1000 comes equipped with dual redundant hot-swap power supplies, allowing the system to continue operating when one power supply has failed or has been removed.

An LED at the back of the power supply module indicates the power supply status:

LED Color	Power Supply status
Red	Failed
Yellow	System power is off
Green	Normal operation

To replace a failed power supply:

1. Unplug the power cord from the failed power supply module (a red LED indicates the failed module)
2. Push the release tab on the back of the power supply then pull out the power supply (see diagram below).
3. Push the replacement power supply module into the power bay until you hear a click.
4. Reconnect the power cord to the new module.
5. Verify that the new power supply is working properly. The green LED will be illuminated and the power supply fans will be rotating.

Replacing a power supply module in the r1000

Connecting the r1000 - PDF

A printable setup guide is also available: Connecting the r1000

Safety and Regulatory

Safety and Regulatory guides include:

• General Safety Guidelines
• Regulatory Information

Container-based Monitoring Point (CMP)

The AppNeta CMP Enterprise Monitoring Point is software that runs in a Docker container. It supports Delivery/Experience monitoring up to 1Gbps. It is typically deployed in one of the following scenarios:

• Monitoring from a remote region - The Container-based Monitoring Point (CMP) is deployed in the public cloud in a region where you have users but where you can’t deploy at their locations. User experience can then be measured from that region to your critical applications.
• Monitoring to a cloud-based app - The CMP is deployed in the same Virtual Private Cloud (VPC) as your critical applications. It is used as a target when monitoring network performance from remote regions or sites. It can also be used to measure baseline user experience to your applications.
• Monitoring from a remote office - The CMP is deployed on a server in a remote office to monitor network and application performance from the perspective of users at that office.
• Monitoring from a workstation - The CMP is deployed on a user workstation to monitor network and application performance from the perspective of the work-from-home user. Typically though, this use case is achieved using a Native Monitoring Point.

The CMP can be deployed in Azure cloud using AKS orchestration or on Azure, AWS, a server, or a workstation, using Docker Compose. Keep in mind:

• Only one CMP can be running on a given host.
• The CMP can be licensed as either a c10 (using the “Workstation (c10/n10)” license) or as a c50 (using a “Strategic (m50/c50) / Legacy Small Office” license).
• The CMP does not have a Web UI. Instead, management of the CMP container is performed using the applicable orchestration commands.
• Capacity measurements can be influenced by networking on the host, kernel version on the host, other containers sharing the host.
• When targeting a CMP, use dual-ended monitoring.
• AKS
  • When deployed on Azure using AKS, a redundant instance is automatically created and failover is automatic.
  • To target a CMP deployed using AKS, run the terraform output command within the Azure Cloud Shell to determine the Load balancer fqdn to target.

CMP host requirements

The host requirements for the CMP are as follows:

Host requirement	Azure	AWS	Docker Compose
OS	Linux	Linux	Linux
CPU	D1 v2 (1 vCPU)	t3.medium (2 vCPUs) c5.large (2 vCPUs)	1 vCPU at or above 2.3GHz E5-2673 v3 spec.
RAM	3.5 GB	4 GB	4 GB
Storage	min 20 GB	min 20 GB	min 20 GB

CMP limitations

CMP limitations include:

• Only one CMP can be running on a given deployment host.
• DNS monitoring is currently not supported.
• Migrate monitoring is not currently supported.
• AppNeta Synthetic scripting is not supported.

A full list of features can be found on the Monitoring Point Feature Comparison page.

v35 (KVM)

The AppNeta v35 (KVM) Enterprise Monitoring Point is software that can be downloaded and run as a virtual machine on a KVM hypervisor. It is used for monitoring in small office environments. A full list of features can be found on the Monitoring Point Feature Comparison page.

v35 (KVM) port descriptions

The following table shows what each port on the Monitoring Point is used for.

Port #	Preconfigured?	Port type	Used for
eth0	Yes	Primary network connection port	Connectivity to APM Delivery monitoring Experience monitoring
eth1	Yes	Primary Usage monitoring port (Out-of-band)	Usage monitoring
eth2	Physical interface can be added	Secondary network connection port	Connectivity to APM Delivery monitoring Experience monitoring
eth3	Physical interface can be added	Secondary network connection port	Connectivity to APM Delivery monitoring Experience monitoring

Note that 10Gbps NICs are supported on eth0, eth2, and eth3. Only 1Gbps NICs are supported on eth1 - the Usage monitoring port.

v35 (KVM) guest requirements

Any virtual machine that comes up without the following minimum requirements will show up in APM as a v25, which is an unsupported Monitoring Point type that cannot be licensed.

Guest requirements	v35 KVM
CPU	2 cores
RAM	4 GB
Storage	16 GB
File system	ext4
Network interfaces	1 virtio_net interface
Host kernel drivers	virtio_net virtio scsi virtio balloon kvm-clock

v35 (VMware)

The AppNeta v35 (VMware) Enterprise Monitoring Point is software that can be downloaded and run as a virtual machine on a VMware hypervisor. It is used for monitoring in small office environments. A full list of features can be found on the Monitoring Point Feature Comparison page.

v35 (VMware) port descriptions

The following table shows what each port on the Monitoring Point is used for.

Port #	Preconfigured?	Port type	Used for
eth0	Yes	Primary network connection port	Connectivity to APM Delivery monitoring Experience monitoring
eth1	Yes	Primary Usage monitoring port (Out-of-band)	Usage monitoring

1Gbps NICs are supported.

v35 (VMware) guest requirements

Any virtual machine that comes up without the following minimum requirements will show up in APM as a v25, which is an unsupported Monitoring Point type that cannot be licensed.

Guest requirements	v35 VMware
CPU	2 cores
RAM	4 GB
Storage	16 GB
Network interfaces	1 vmxnet3 interface
Host kernel drivers	vmxnet3

Monitoring is supported up to 1Gbps.

Native Monitoring Point (NMP)

The AppNeta NMP Enterprise Monitoring Point is software that runs on the native operating system of a host computer and is used for Delivery monitoring. As such, it is typically used to monitor network performance from the perspective of a work-from-home user. The NMP can be licensed as either an n10 (using the “Workstation (c10/n10)” license) or as an n35 (using a “Strategic (m50/c50) / Legacy Small Office” license).

NMP specifications

Spec	Sub-spec	Value
Storage		2 hours stored locally in case disconnected from APM
Supported OS	Windows	Windows 8.1 and newer (all variants) and Windows Server 2012 and newer
	Mac OS	macOS 10.14 (Mojave), macOS 10.15 (Catalina), macOS 11.0 (Big Sur)
Virtual environments
	Hypervisors	ESXi 5.5 or higher
	Guest OS	64-bit RHEL 7 Windows 10 (all variants) and Windows Server 2016
Hardware requirements	Memory	512 MB
	CPU	2.0 GHz
	Disk space	10 MB

NMP limitations and issues

• Delivery monitoring only (no Experience monitoring, Usage monitoring, or Packet Capture).
• Does not support PathTest.
• Does not support voice or video testing when installed on a virtual machine.
• Scheduled access network links (for example, Fibre PON, DOCSIS Cable), typically provided by ISPs to residential customers, can show lower uplink capacity than expected.
• Capacity measurements in either direction are problematic on Wifi networks.
• On Windows machines:
  • The NMP can be used at a maximum speed of 500 Mbps when the NMP is either a path source or a path target.
  • TCP Traceroute and TCP Ping are not supported.
• On macOS machines:
  • The macOS NMP does not support Apple M-series processors.
  • macOS automatic time updates cause periodic jitter spikes and packet discards in voice and video tests. To work around this issue, uncheck > ​System Preferences​ > Date & Time > Set date and time automatically.

A full list of features can be found on the Monitoring Point Feature Comparison page.

Global Monitoring Point (GMP)

Global Monitoring Points are Container-based Monitoring Points owned by you but managed by AppNeta. They are installed in global cloud provider locations selected by you so that you can monitor your network and web applications from places where you have users but nowhere to install an Enterprise Monitoring Point without the burden of deploying, monitoring, and maintaining the Monitoring Point yourself. Global Monitoring Points are used only for Delivery and Experience monitoring (not for Usage monitoring).
A full list of features can be found on the Monitoring Point Feature Comparison page.

Global Monitoring Points are typically deployed in one of the following scenarios:

• Customer substitute - Monitor performance to core public-facing apps or internet-facing services from global locations representative of your customer base.
• Partner substitute - Monitor performance from specific regions to apps used by your distributors, integrators, or retail locations.
• Regional reference - Understand the performance of specific regions as a reference to identify the scope of issues reported at office locations.
• Performance baseline - Compare performance of your apps across different regions before and after updates to identify issues before customers do.

GMP limitations

GMP limitations include:

• DNS monitoring is currently not supported.
• Migrate monitoring is not currently supported.
• AppNeta Synthetic scripting is not supported.
• Traceroutes outbound from a GMP will not show the identity of any hops between the source and target.