If AppNeta doesn’t see your monitoring point, and so you can’t continue with monitoring point setup, first grab its current configuration. If you were able to get the config, we know three things: the monitoring point is on, the software is running, and the USB port is working. Now, open the one and only html file and check the following:
- Are the network settings accurate?
- Is the monitoring point connected to the Internet?
- What is the status of the sequencer?
- Is the monitoring point configured for to connect to APM?
No IP address
Each monitoring point model has one port that is pre-configured for DHCP (the port labeled Primary network connections in this table). Use that port to connect back to APM.
No connection to Internet
If your network requires Internet traffic to be forwarded by proxy, the monitoring point won’t be able to connect to APM immediately after you complete USB Configuration because the monitoring point doesn’t yet have the proxy details. You enter these details via the monitoring point’s web admin interface. See configuring a monitoring point to use a web proxy.
Start usage monitoring by navigating to Usage > Monitoring Points and click play on the monitoring point of interest. You’re going to receive one of the following messages:
Started capturing flows on …
If you got this message, you either forgot to start monitoring or someone turned it off. Don’t worry, it happens all the time. Go get a coffee, your first results will roll in in 5 to 10 minutes.
Monitoring has already been started ….
Usage monitoring is on. Good. Now check the ‘most recent traffic rate’ column. You’ve already established that no data is coming in, so this column should say either ‘0 kbps’, or ‘-‘.
- If it says ‘0 kbps’, the monitoring point has established a connection with our servers and can upload data. So that means that there’s either something wrong with your cabling or your port-mirroring connection.
- If it says ‘-‘, the monitoring point SSL connection to APM is probably down. If this is in fact the case you won’t be able to reach web admin via the ‘Launch Monitoring Point Web Admin…’ link on the Manage Monitoring Points page. Check this link and then open a support ticket anyway. We’ll take it from there.
Failed to connect to the monitoring point …
Something is wrong with your monitoring point setup generally because our servers can’t reach it.
First try to reach web admin via the ‘Launch Monitoring Point Web Admin…’ link on the Manage Monitoring Points page. When you access web admin using this link, a capture server provides a reverse proxy so that your connection remains secure. If you can’t connect to web admin this way, double-check that outbound connections to web admin are not blocked by your firewall.