i saw bounces of the most closely monitored, by my systems, of my probes between Apr 10 01:17:38 and 01:19:57. the others are on homey openwrt boxen which do not monitor closely. randy
On 4/11/13 12:35 , Randy Bush wrote:
i saw bounces of the most closely monitored, by my systems, of my probes between Apr 10 01:17:38 and 01:19:57. the others are on homey openwrt boxen which do not monitor closely.
Hi Randy, Can you give a bit more details? I found one probe that disconnected from its controller around that time. But is seems to disconnect more often. But nothing specifically for that interval.
philip,
i saw bounces of the most closely monitored, by my systems, of my probes between Apr 10 01:17:38 and 01:19:57. the others are on homey openwrt boxen which do not monitor closely. Can you give a bit more details? I found one probe that disconnected from its controller around that time. But is seems to disconnect more often. But nothing specifically for that interval.
the switch to which probe 2285 is connected logged the following: Apr 10 01:17:38 sw0.sea.rg.net 3081: Apr 10 01:17:37.570: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to down Apr 10 01:17:40 sw0.sea.rg.net 3082: Apr 10 01:17:39.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up Apr 10 01:19:55 sw0.sea.rg.net 3083: Apr 10 01:19:54.189: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to down Apr 10 01:19:57 sw0.sea.rg.net 3084: Apr 10 01:19:56.194: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up randy
around the same time(UTC) probe upgraded its firmware. 2013-04-08 01:01:30 4500 2013-04-10 01:27:23 4520 upgrade was finished and reconnected. -antony On Fri, Apr 12, 2013 at 11:28:16AM +0900, Randy Bush wrote:
philip,
i saw bounces of the most closely monitored, by my systems, of my probes between Apr 10 01:17:38 and 01:19:57. the others are on homey openwrt boxen which do not monitor closely. Can you give a bit more details? I found one probe that disconnected from its controller around that time. But is seems to disconnect more often. But nothing specifically for that interval.
the switch to which probe 2285 is connected logged the following:
Apr 10 01:17:38 sw0.sea.rg.net 3081: Apr 10 01:17:37.570: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to down Apr 10 01:17:40 sw0.sea.rg.net 3082: Apr 10 01:17:39.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up Apr 10 01:19:55 sw0.sea.rg.net 3083: Apr 10 01:19:54.189: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to down Apr 10 01:19:57 sw0.sea.rg.net 3084: Apr 10 01:19:56.194: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up
randy
2013-04-10 01:27:23 4520 upgrade was finished and reconnected.
the switch to which probe 2285 is connected logged the following: Apr 10 01:17:38 sw0.sea.rg.net 3081: Apr 10 01:17:37.570: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to down Apr 10 01:17:40 sw0.sea.rg.net 3082: Apr 10 01:17:39.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up Apr 10 01:19:55 sw0.sea.rg.net 3083: Apr 10 01:19:54.189: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to down Apr 10 01:19:57 sw0.sea.rg.net 3084: Apr 10 01:19:56.194: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up
is the 4520 a probe number? the probe of the log entries is 2285 but this is not a critical issue, to say the least randy
On Fri, Apr 12, 2013 at 05:39:21PM +0900, Randy Bush wrote:
2013-04-10 01:27:23 4520 upgrade was finished and reconnected.
the switch to which probe 2285 is connected logged the following: Apr 10 01:17:38 sw0.sea.rg.net 3081: Apr 10 01:17:37.570: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to down Apr 10 01:17:40 sw0.sea.rg.net 3082: Apr 10 01:17:39.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up Apr 10 01:19:55 sw0.sea.rg.net 3083: Apr 10 01:19:54.189: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to down Apr 10 01:19:57 sw0.sea.rg.net 3084: Apr 10 01:19:56.194: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up
is the 4520 a probe number? the probe of the log entries is 2285
It seems to be a firmware version (4520). Piotr -- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski@polsl.pl
On 4/12/13 10:39 , Randy Bush wrote:
2013-04-10 01:27:23 4520 upgrade was finished and reconnected.
the switch to which probe 2285 is connected logged the following: Apr 10 01:17:38 sw0.sea.rg.net 3081: Apr 10 01:17:37.570: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to down Apr 10 01:17:40 sw0.sea.rg.net 3082: Apr 10 01:17:39.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up Apr 10 01:19:55 sw0.sea.rg.net 3083: Apr 10 01:19:54.189: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to down Apr 10 01:19:57 sw0.sea.rg.net 3084: Apr 10 01:19:56.194: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up is the 4520 a probe number? the probe of the log entries is 2285
4520 is a firmware version. It is displayed on the web page for your probe. The controller logged that it finished sending the firmware to the probe at '2013-04-10 01:17:27' and the probe reboots shortly after that to install the firmware. It looks like the probe was up for 43 days before it rebooted.
the switch to which probe 2285 is connected logged the following: Apr 10 01:17:38 sw0.sea.rg.net 3081: Apr 10 01:17:37.570: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to down Apr 10 01:17:40 sw0.sea.rg.net 3082: Apr 10 01:17:39.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up Apr 10 01:19:55 sw0.sea.rg.net 3083: Apr 10 01:19:54.189: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to down Apr 10 01:19:57 sw0.sea.rg.net 3084: Apr 10 01:19:56.194: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up is the 4520 a probe number? the probe of the log entries is 2285 4520 is a firmware version. It is displayed on the web page for your
2013-04-10 01:27:23 4520 upgrade was finished and reconnected. probe. The controller logged that it finished sending the firmware to the probe at '2013-04-10 01:17:27' and the probe reboots shortly after that to install the firmware. It looks like the probe was up for 43 days before it rebooted.
Feb 25 14:08:25 sw0.sea.rg.net 3075: Feb 25 14:08:24.566: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to down Feb 25 14:08:25 sw0.sea.rg.net 3076: Feb 25 14:08:25.573: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/19, changed state to down Feb 25 14:08:30 sw0.sea.rg.net 3077: Feb 25 14:08:29.633: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/19, changed state to up Feb 25 14:08:30 sw0.sea.rg.net 3078: Feb 25 14:08:30.640: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up Feb 25 14:10:40 sw0.sea.rg.net 3079: Feb 25 14:10:39.130: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to down Feb 25 14:10:42 sw0.sea.rg.net 3080: Feb 25 14:10:41.135: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up i plead innocent. i was in singapore at apricot and the probe is in a locked cabinet randy
On 4/12/13 11:19 , Randy Bush wrote:
the switch to which probe 2285 is connected logged the following: Apr 10 01:17:38 sw0.sea.rg.net 3081: Apr 10 01:17:37.570: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to down Apr 10 01:17:40 sw0.sea.rg.net 3082: Apr 10 01:17:39.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up Apr 10 01:19:55 sw0.sea.rg.net 3083: Apr 10 01:19:54.189: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to down Apr 10 01:19:57 sw0.sea.rg.net 3084: Apr 10 01:19:56.194: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up is the 4520 a probe number? the probe of the log entries is 2285 4520 is a firmware version. It is displayed on the web page for your
2013-04-10 01:27:23 4520 upgrade was finished and reconnected. probe. The controller logged that it finished sending the firmware to the probe at '2013-04-10 01:17:27' and the probe reboots shortly after that to install the firmware. It looks like the probe was up for 43 days before it rebooted. Feb 25 14:08:25 sw0.sea.rg.net 3075: Feb 25 14:08:24.566: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to down Feb 25 14:08:25 sw0.sea.rg.net 3076: Feb 25 14:08:25.573: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/19, changed state to down Feb 25 14:08:30 sw0.sea.rg.net 3077: Feb 25 14:08:29.633: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/19, changed state to up Feb 25 14:08:30 sw0.sea.rg.net 3078: Feb 25 14:08:30.640: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up Feb 25 14:10:40 sw0.sea.rg.net 3079: Feb 25 14:10:39.130: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to down Feb 25 14:10:42 sw0.sea.rg.net 3080: Feb 25 14:10:41.135: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up
i plead innocent. i was in singapore at apricot and the probe is in a locked cabinet
The same story :-) '2013-02-25 14:08:13' was when it got firmware version 4500 :-)
Hello,
4520 is a firmware version. It is displayed on the web page for your probe. The controller logged that it finished sending the firmware to the probe at '2013-04-10 01:17:27' and the probe reboots shortly after that to install the firmware. It looks like the probe was up for 43 days before it rebooted.
Feb 25 14:08:25 sw0.sea.rg.net 3075: Feb 25 14:08:24.566: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to down Feb 25 14:08:25 sw0.sea.rg.net 3076: Feb 25 14:08:25.573: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/19, changed state to down Feb 25 14:08:30 sw0.sea.rg.net 3077: Feb 25 14:08:29.633: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/19, changed state to up Feb 25 14:08:30 sw0.sea.rg.net 3078: Feb 25 14:08:30.640: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up Feb 25 14:10:40 sw0.sea.rg.net 3079: Feb 25 14:10:39.130: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to down Feb 25 14:10:42 sw0.sea.rg.net 3080: Feb 25 14:10:41.135: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up
i plead innocent. i was in singapore at apricot and the probe is in a locked cabinet
Probes try to keep up a TCP connection to our infrastructure so that they can report, and we can involve them in new measurements quickly; as long as this is up they are shown as "connected", if not, they are shown as "disconnected". Such a connection can go down occasionally for a number of reasons: * the probe has to (decides to) reboot * the host's network (or home router) has a problem such as a power outage * the host wants to vaccum up but they don't have enough power sockets free * we ask the probe to upgrade its firmware * we do maintenance work on the controller and need to disconnect probes * the colo where we have infrastructure does network maintenance or has a hickup * there's a network split between the probe and the controller * many other reasons The "downtime" is expected to be a few (up to 20-30) minutes, and these are the times when the probe may upgrade its firmware. This happens all the time, it's a part of normal operation, so you don't need to worry if you see disconnect events. In the future we plan to switch to measuring the probe "uptime" (or "useful time") based on the regular measurements it does, rather than pure connection times. Regards, Robert
Probes try to keep up a TCP connection to our infrastructure so that they can report, and we can involve them in new measurements quickly; as long as this is up they are shown as "connected", if not, they are shown as "disconnected".
the logs i sent were of the probe disconnecting at layer two from the switch into which it is plugged. randy
On 2013-04-12 12:51, Robert Kisteleki wrote:
In the future we plan to switch to measuring the probe "uptime" (or "useful time") based on the regular measurements it does, rather than pure connection times.
I would also like to still see full path end-to-end uptime somewhere. Indeed, it's really questionable where the "end" is. Of course it might desirable to determine the uptime of "weaker end", in case when this is home installation, which can be physically and electrically unstable. I'm moving towards more stable home network here, with my >30min UPS / overvoltage protection. As for stats, this probe hosting location is private house in small town Saue, Estonia (I consider sending "probe action photo" to be included in that really good selection of existing ones), powered via insulated low voltage overhead mains cable and connected to internet via copper pair on where ADSL2+ runs to local ISP PoP. Ehm, now I'm going too far from original reason I wrote this message here... That should be up there somewhere. P.S: I had to say this, for name "Robert Kisteleki" in this mail my Thunderbird spell check suggests "Robert Telekinesis". I hope this wasn't bad personal joke...
On 2013.04.12. 23:22, Sulev-Madis Silber wrote:
On 2013-04-12 12:51, Robert Kisteleki wrote:
In the future we plan to switch to measuring the probe "uptime" (or "useful time") based on the regular measurements it does, rather than pure connection times.
I would also like to still see full path end-to-end uptime somewhere. Indeed, it's really questionable where the "end" is. Of course it might desirable to determine the uptime of "weaker end", in case when this is home installation, which can be physically and electrically unstable.
Most of our users seem to be interested more in the measurements results than in continuous end-to-end connections. But we can of course keep this information available. In fact we also planned to extend it with the reason for disconnects, when we know it (such as probe reboots).
P.S: I had to say this, for name "Robert Kisteleki" in this mail my Thunderbird spell check suggests "Robert Telekinesis". I hope this wasn't bad personal joke...
:-) Regards, Robert
not related but my probe working again at home, BT home hub died to stop routing so had to switch back to zyxel adsl for routing and find another spare port for network comms :) Colin
participants (7)
-
Antony Antony -
Colin Johnston -
Philip Homburg -
Piotr Strzyzewski -
Randy Bush -
Robert Kisteleki -
Sulev-Madis Silber