can you send me a screenshot on how those failing entries are configured AND the entries file? Send it directly to me, NOT to the list.
-------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:salive@woodstone.nu] On Behalf Of Stratsianis, Spiros Sent: Wednesday, October 21, 2015 4:46 AM To: Servers Alive Discussion List Subject: RE: [SA-list] ping -l 1472 -f 10.10.10.10 Hi Dirk, I installed 7.9.2707 over the top of 7.2.2638, didn’t make any changes to the configuration file but found a problem. Some items ping ok but then fail due to a PingStart error. Some items always fail but other ones work sometimes but then fail other times. One example from the log file: Wednesday, 21 October 2015 11:26:21 AM AU Homebush Orange router PSYD2202 Wednesday, 21 October 2015 11:26:22 AM PING DEBUG: event start for ID= 0 pingID= 102 Wednesday, 21 October 2015 11:26:22 AM AU Homebush Orange router PSYD2202 OK with a successrate of 100% and an average roundtriptime of 187ms Wednesday, 21 October 2015 11:26:22 AM PING DEBUG: REMOVE for ID= 0 pingID= 102 Wednesday, 21 October 2015 11:26:22 AM PING DEBUG: REMOVED for ID= 0 pingID= 102 Wednesday, 21 October 2015 11:26:22 AM PingStart ERROR: Subscript out of range ( 0) - 1115- 102 Other PingStart errors from other devices: Wednesday, 21 October 2015 11:26:23 AM PingStart ERROR: Subscript out of range ( 0) - 19- 8 Wednesday, 21 October 2015 11:26:26 AM PingStart ERROR: Subscript out of range ( 0) - 16- 40 Wednesday, 21 October 2015 11:50:00 AM PingStart ERROR: Subscript out of range ( 0) - 1337- 225 Wednesday, 21 October 2015 11:50:04 AM PingStart ERROR: Subscript out of range ( 0) - 44- 26 Everything is ok when I go back to the previous version. Regards, Spiros From: Servers Alive Discussion List [mailto:salive@woodstone.nu] On Behalf Of dirk Sent: Sunday, 18 October 2015 1:31 AM To: Servers Alive Discussion List Subject: RE: [SA-list] ping -l 1472 -f 10.10.10.10 The new beta with this ping feature is on the beta site. http://beta.woodstone.nu (http://beta.woodstone.nu) dirk. -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:salive@woodstone.nu (mailto:salive@woodstone.nu)] On Behalf Of dirk Sent: Thursday, October 15, 2015 7:05 PM To: Servers Alive Discussion List Subject: RE: [SA-list] ping -l 1472 -f 10.10.10.10 It will be in the next beta upload. The inhouse version already has the feature and it seems to work as you wanted it to work. Keep an eye on http://beta.woodstone.nu (http://beta.woodstone.nu) for updates. dirk. -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:salive@woodstone.nu (mailto:salive@woodstone.nu)] On Behalf Of Stratsianis, Spiros Sent: Monday, October 12, 2015 2:10 AM To: Servers Alive Discussion List Subject: RE: [SA-list] ping -l 1472 -f 10.10.10.10 Thanks Dirk. Regards, Spiros From: Servers Alive Discussion List [mailto:salive@woodstone.nu (mailto:salive@woodstone.nu)] On Behalf Of dirk Sent: Saturday, 10 October 2015 1:10 AM To: Servers Alive Discussion List Subject: RE: [SA-list] ping -l 1472 -f 10.10.10.10 Just talked to the developper of our PING checker and he confirmed that for the moment the limit is at 512 bytes and the "do not fragment"-bit is NOT set by his code. If all goes well he'll do some change to the PING-er next week and it will be added as new feature to v8 of Servers Alive (and as such also to the v7.9beta) dirk -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:salive@woodstone.nu (mailto:salive@woodstone.nu)] On Behalf Of Stratsianis, Spiros Sent: Friday, October 09, 2015 7:15 AM To: Servers Alive Discussion List Subject: RE: [SA-list] ping -l 1472 -f 10.10.10.10 Hi, I did see that option but the maximum packet size seems to be 128 bytes and I can’t find an option to set ‘don’t fragment’ on the ping. (Without don’t fragment set, any large packet I send will get broken up) Regards, Spiros From: Servers Alive Discussion List [mailto:salive@woodstone.nu (mailto:salive@woodstone.nu)] On Behalf Of dirk Sent: Friday, 9 October 2015 4:00 PM To: Servers Alive Discussion List Subject: RE: [SA-list] ping -l 1472 -f 10.10.10.10 On the CHECK tab you can when selecting the PING check option set the size of the packet too. dirk. -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:salive@woodstone.nu (mailto:salive@woodstone.nu)] On Behalf Of Stratsianis, Spiros Sent: Friday, October 09, 2015 3:00 AM To: Servers Alive Discussion List Subject: [SA-list] ping -l 1472 -f 10.10.10.10 Hi, We sometimes have problems on our WAN links when carriers change MTU setting within their network. To trouble shoot we manually start pinging with a 1472 payload and ‘don’t fragment’ set. Can SA be set up to do the equivalent of ‘ping -l 1472 -f 10.10.10.10’? With best regards, Spiros Stratsianis Siemens Ltd. Global Service Information Technology IT Infrastructure Service - Service Delivery Regions Asia, Pacific, Middle East and Africa Operational Services - Collaboration GS IT IN SD AAE OPS COL 885 Mountain Highway Bayswater VIC 3153, Australia Tel: +61 (3) 9721-2934 Fax: +61 (3) 9721-2788 E-mail: spiros.stratsia...@siemens.com (mailto:spiros.stratsia...@siemens.com) Important notice: This e-mail and any attachment thereof contain corporate proprietary information. If you have received it by mistake, please notify us immediately by reply e-mail and delete this e-mail and its attachments from your system. Thank you. CAUTION - This message may contain privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify Siemens Ltd. or Siemens Ltd. (NZ) by return email and delete the document. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu (mailto:salive@woodstone.nu) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu (mailto:salive@woodstone.nu) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. CAUTION - This message may contain privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify Siemens Ltd. or Siemens Ltd. (NZ) by return email and delete the document. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu (mailto:salive@woodstone.nu) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu (mailto:salive@woodstone.nu) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. CAUTION - This message may contain privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify Siemens Ltd. or Siemens Ltd. (NZ) by return email and delete the document. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu (mailto:salive@woodstone.nu) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu (mailto:salive@woodstone.nu) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu (mailto:salive@woodstone.nu) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list.CAUTION - This message may contain privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify Siemens Ltd. or Siemens Ltd. (NZ) by return email and delete the document. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list.