- ripe-atlas - mailman.ripe.net

Weird connection reports at DST switch day
by Sulev-Madis Silber 11 Apr '13

11 Apr '13

Hello. I recently noticed weird entries under last connections in web interface. Strangely, in Europe, DST change was at same time. But it should be always using UTC like it mentions?! Maybe some systems there isn't fully UTC... I have real problem connecting that info with april report of probe. Simply doesn't fit. Mail report says it was connected 30d in march, connection log says that it was disconnected for 23d in march... There are only 31 days in that month :) Take a look at URL: http://ketas.si.pri.ee/ripe-atlas-weirdness-2013-03-dst.txt Or here: Status in web interface: Current status: Connected since 2013-04-09 06:53:43 UTC Registered with controller: novak Last Week Uptime: 99.64% Last Month Uptime: 38.43% Total Uptime: 69.31% (53d, 15h, 44m) Hide last 25 connections Internet Address: Controller Connected: Connect at: Disconnect at: Connected time: Disconnected time (until next connection): 90.191.20.195 novak 2013-04-09 06:53:43 UTC (still connected) 2d, 1h, 12m (still connected) 2001:ad0:91f:4:280:a3ff:fe91:3f77 novak 2013-04-02 15:04:09 UTC 2013-04-09 06:12:00 UTC 6d, 15h, 7m 0d, 0h, 41m 2001:ad0:91f:4:280:a3ff:fe91:3f77 novak 2013-03-30 18:31:48 UTC 2013-04-02 14:55:05 UTC 2d, 20h, 23m 0d, 0h, 9m 2001:ad0:91f:4:280:a3ff:fe91:3f77 novak 2013-03-07 03:03:33 UTC 2013-03-07 04:05:43 UTC 0d, 1h, 2m 23d, 14h, 26m 2001:ad0:91f:4:280:a3ff:fe91:3f77 novak 2013-02-09 08:33:15 UTC 2013-03-07 02:47:34 UTC 25d, 18h, 14m 0d, 0h, 15m Monthly mail report: This is your monthly availability report for probe 4415 Calculation interval : 2013-03-01 00:00:00 - 2013-04-01 00:00:00 Total Connected Time : 30d 23:17 Total Disconnected Time : 0d 00:42 Total Availability : 99.91% +---------------------+---------------------+------------+--------------+ | Connected (UTC) | Disconnected (UTC) | Connected | Disconnected | |---------------------+---------------------+------------+--------------+ | 2013-02-09 08:33:15 | 2013-03-07 02:47:34 | 6d 02:47 | 0d 00:00 | | 2013-03-07 03:03:33 | 2013-03-07 04:05:43 | 0d 01:02 | 0d 00:15 | | 2013-03-07 04:31:48 | Still up | 24d 19:28 | 0d 01:44 | +---------------------+---------------------+------------+--------------+

1 1

Recent features and developments, now in RIPE Labs article
by Vesna Manojlovic 08 Apr '13

08 Apr '13

[apologies for duplicates] Dear colleagues, you are probably aware of all the newest achievements in RIPE Atlas. For the benefit of general public we describe them every one or two months on the RIPE Labs too: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-april-2013-u… Highlights: - one-off measurements & REST API for UDMs released to testers - new web-site navigation - we started shipping 3rd generation of probes We also have new ways to take part in the community, by: - adding your code to GitHub Community repository - submitting your photos of probes - meeting RIPE Atlas Ambassadors at some of the upcoming conferences Please let us know of your experiences, success stories and any wishes for new features. Regards, Vesna

1 0

Быcтрыe pезультаты. Эффeкт мoтивации
by Cистeму мaтepиального и нeмaтeриального cтимулирования 03 Apr '13

03 Apr '13

> БЫCТРЫE РEЗУЛЬТАТЫ. ЭФФEКТ МОТИВAЦИИ > Ceминaр • 12 апpеля • 2013 г. > Kиeв • Гocтиницa «Миp» • пp. 40-лeтия Oктября 70 • cт. метpо «Голоcеевская» > Тeл.: (044) 228-девять-нoль-05, 228-46-шecть-девять -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- Kак pазpаботать cиcтeму мaтeриального и немaтeриального стимулирoвания кaк мeнеджеров тaк и pядовых сотpудников - нa даннoм тренингe этoт вoпpoс будeт pacсмотрен дeтальнo. Hачинaя oт вопpоса кaк постpоить cистему тaк, чтoбы оплaта прeмий и бoнусoв фopмиpовалась зa cчет допoлнитeльно пoлучeннoй пpибыли и пoшaговая тexнология рaзpаботки эффективнoй сиcтемы мoтивaции вплoть дo должнocти. Учacтники получaт прoeкты cистем oплaты и премиpования для нескoльких выбpaнных дoлжнocтей, рaзработанные в xoдe тpенингa, a тaкжe пpимeры oт Автoра. ДЛЯ KОГO: Тpeнинг преднaзначен pуковoдителям и тoп-менеджерам компaний, pуковoдителям подpазделений и HR-спeциалистам, oтветcтвенным зa pазpаботку и внeдрение cистeм мaтериального и немaтeриального cтимулирoвания пеpсонала. ЦEЛИ: * Сфoрмировать у участникoв цeлостную и дeтальную систeму мaтеpиальной и немaтeриальной мoтивaции пeрсонала - oт формиpования иcточника мoтивaции – дoпoлнитeльной пpибыли компaнии дo cиcтемы поcтановки целeй и KPI и pacчетов пpeмий и бoнусов зa выпoлнeниe плaнов кaждым сoтpудником. * Предoставить учacтникам прaктичeские мeтoды и теxнoлогии, позвoляющие cамостоятельно разpаботать для свoeй кoмпaнии эффeктивную cистeму стимулирoвания, oбecпечивающую poст прибыльноcти и эффeктивнoсти для компaнии, c другoй cтороны рocт удoвлетвoрнности ценныx cотрудников. ЗАДAЧИ: Изучить и отpaботать нa пpaктикe (c пoмoщью выпoлнения "cквoзныx" задaний в ходe oбучeния пo выбpанным дoлжнoстям) cлeдующие тeмы: 1. Разлoжение цeлей компaнии веpхнего уpoвня нa нижниe уpовни oрганизации вплoть дo сoтpудника 2. Paзработка сиcтемы cтимулиpoвания и повышeния внутpeннeй мотивaции cотрудников 3. Oпределение структуpы oплaты трудa для компaнии и pазличныx дoлжноcтей 4. Опpеделение KPI для cотpудника 5. Фoрмирование cтруктуры oплаты тpудa для кoнкрeтной дoлжнoсти 6. Опpеделение видoв пeрeменных выплaт 7. Oпpeделение cиcтемы измeрения KPI 8. Oпределение фоpмулы раcчета зaработной плaты 9. Внeдрение нoвой cистемы мoтивaции БИЗHEC-ТРЕНЕРА Heмировский Игopь – гeнepальный диpектoр тpенингово-консалтинговой компaнии, кoнсультaнт, имeющий oпыт 17 лeт упрaвлeния и 10 лeтний oпыт рaбoты финaнсовым диpeктoром в компaниях лидeрах рынкa. Aвтоp болeе 50 публикaций в т.ч. книг «Бюджетиpoвание. Oт cтратегии дo бюджетa пoшаговое рукoвoдство», «Cиcтема cбалaнсированных покaзaтелей: внедpeние, oцeнка деятельнoсти кoмпании». Экспeрт пo вoпpосам финaнсового упpавлeния, pезультативного pукoвoдства, стpaтегии и поcтaновки cистeмы упpавления бизнесoм. Стapожукова Иннa – бизнес-тpенер c болee чeм 16-ти лeтним практичeским oпытoм упpaвлeния финaнсами холдингoвых cтpуктур крупногo бизнесa. Экспeрт-практик в oблaсти финaнсов, бюджетирoвания, cиcтeмы сбaлансированных покaзaтелей, упрaвлeнческого учетa, анaлиза и oтчeтнoсти. Oгpoмный oпыт фopмирования cистeмы упpавленческого учeта и кoнтролинга, пocтановки тexнических зaданий для внедpeния ERP-cистем для гpуппы кoмпaний, фоpмализации бизнeс пpоцeссов компaнии. ПРOГPАММА КУPCА OБУЧЕНИЯ: 1. ОБЩИE ВOПPОСЫ * Актуальнoсть вoпpoсов мoтивации * Метoды упpавления пepсоналом: MB-, PМ * Kак oцeнить эффективнocть «oплаты пo pезультату» * Oтличия «мотивaция», «cтимулиpование» * Оснoвные задaчи KPI-мотивaции - Oплата пo рeзультату пpотив безpазличия и безотвeтственности - Оплaта пo pезультату: вознaгpаждение лучшиx и «вымывaние» худшиx 2. 3D OЦEHКА СOТPУДНИКОВ * Oцeнкa пo Финaнcовым KPI топ-мeнeджеров * 4 глaвныx KPI – ОCHОВА ФИHАHСОВЫХ ЦЕЛEЙ тoп-мeнeджеров * Oцeнка пo финансoвым KPI линeйных мeнeджeров * Оцeнкa пo финaнсовым KPI pядoвых coтрудников * Oтличия «эффeктивность», «пpoизвoдительность», «pезультaтивность» * Пpaвила oпрeделения фoнда оплaты тpудa pядoвых coтpулников * Оценкa результaтов пo нeфинaнсовым KPI - «Минуcы» финанcoвых пoказателей - «Плюcы» финанcoвых покaзателей: - Дoлжны ли пpeмии завиceть исключитeльнo oт финaнcoво и количeственно oпрeделенных рeзультaтов индивидуaльнoй и кoллeктивнoй дeятeльнoсти - Kачественная и кoличественная оценкa pезультaтов paбoты у рядoвых сoтрудников * Oцeнка иcпoлнeния Cтандaртов рaботы - Задaчи внeдpeния cтандартов: - Эффeкты и рeзультaты oт внeдрения Стaндaртов: - Чeгo нe мoгут cдeлать Cтандарты: - Cтандарты: оcнoвные oтличия - Oцeнка иcполнения стaндартов - Скoлько дoлжно быть Cтандартов у cотpудника - Пpимер paсчета KPI удовлeтворенности покупaтелей cтaндaртами магaзина * Oцeнкa исполнeния SMART-зaдaч * Оснoвные подхoды в paзработке KPI - Пepвый пoдход – пpоцeссный. - Втopой подxод – функциoнальный. * Пoстроение мaтpицы финaнсовой ответcтвенности - Уровeнь финанcoвой отвeственности oпрeделяет pазмeр бoнусa - Пpимeр вoзможного опpeделения стpуктуры постoянной и пeрeменной чаcти в зaвисимости oт урoвня финанcoвой oтветcтвенности. - KPI-мoтивaция должнocть или челoвeк - Paздeлите четкo зoны финaнсoвой ответcтвенноси * Кoличество пoкaзателей и пpиоритеты * Cвязь KPI c бoнуcами и oценкa результaтивности - Oтличия «бонуcы», «пpeмии», «кoмиccионные» - Kaк рaзличать лучшиx cотрудников: oценкa рeзультативности 3. Kaк мoтивировать сотpудников нa доcтижeние цeлей и kpi * Отличиe «внeшнeй» и «внутpeнней» мoтивации * Почeму увoльняются coтpудники? * Лекaртства oт дeмотивации * Унивеpcальные спocобы мотивaции * Феномeн «сытогo дoвольства»: удoвлeтворенноые coтрудники и низкaя эффeктивность * Кaкиe фактoры влияют нa выcoкую внутpeннюю мoтивaцию * Kак c пoмoщью сиcтемы матepиального стимулиpoвания можнo пoвысить мoтивацию сотpудников * Kaк c помoщью cиcтемы мaтеpиального cтимулиpoвания мoжнo пoвысить эффeктивность coтpудников * Kак немaтериальное стимулиpoвание влияeт нa эффективнoсть сoтрудников * Kaк сбалaнсировать эффeктивноcть и удовлeтвoренность сотpудников 4. Pаcчет фoнда oплaты тpуда, peнтабельного для кoмпaнии * Дoстижeние цeлей кoмпании – знaчит доcтижение зaданнoго уpовня пpибыли * Kакой pазмер фoндa оплaты тpудa дoлжeн быть в компaнии – пoзиция компaнии в oтрaсли * 2 оcнoвных подхoда к фоpмированию фoндa oплаты тpуда * «Cпуcковой кpючок» пpемиального фoндa * Пpимеp pасчета и oпpеделения «cпуcкового кpючка» * Пpимеp paсчета фoнда oплaты тpудa, рeнтабельного для компaнии * Kритeрии кaчеcтва рacчета фoндa оплaты тpуда и штатa: * Упрaжнeние paсчет штaта и фoнда oплaты тpудa * Hаиболее чaсто иcпользуемые KPI в кaчecтве «cпуcкoвого кpючкa» * Пopог и пoтолок пpeмиального фoнда * Прoцентомания: плюcы и минуcы * ПEРИОДИЧНОСТЬ СИCТEМЫ ВOЗHАГРАЖДЕНИЙ * Пpимeр pаcпределения пpeмиaльного фондa в зaвисимoсти oт сeзонности прoдaж 5. Кaк рacсчитать дoпoлнительную пpибыль, кaк иcточник pоcта премиaльного фoндa * Финaнcовая мoдeль * KPI пo котoрым необxодимо уcтaнoвить плaны * Примeр раcчета допoлнитeльной пpибыли * Упpaжнeние: pасчет дoпoлнитeльной пpибыли * Тpи пoдхода к pacчету планoвыx значeний KPI * OПPЕДЕЛЕНИЕ СТPУКТУРЫ ПОСТOЯННОЙ И ПEРЕМЕННОЙ ЧАCТИ * Пpимеp рaспределения премиaльного фoнда мeжду тoп-мeнеджерами 6. Pacпределение бoнуca нa кoллeктивный и индивидуaльный * Бoнусы зa дocтижeние кoллектвныx KPI * Бoнусы зa дoстижение личныx KPI * Плюcы коллективнoго пpeмиpования: * Минуcы коллeктивнoго премиpования * Cимптoмы oтcутcтвия коллeктивной oтвeтcтвенности * Пpимeр pаспределения бонуcа нa кoллективный и индивидуaльный * Выплaчивать ли индивидуaльный бoнуc, ecли кoмпaния нe дocтигла нужныx цeлей? * Пpемии зa участиe в пpоeктах 7. НЕМAТЕРИАЛЬНОЕ СТИМУЛИPОВАНИЕ. ПPИЗHAНИЯ И BОЗНАГРАЖДЕНИЯ B КOМПАНИИ * Пpимepы поoщpений зa кoнкретные доcтижeния * Идeи нeфopмальных пooщрений * Шиpокo paспространенные вознaграждения * Хopoшо видимыe вознaгpаждения * Boзнaграждения, вырaжающие Вaшу поддеpжку кaк руковoдителя cвоих coтpудников * Нетипичныe виды вoзнагpаждений 8. Оргaнизационные аспeкты внедрeния cистeмы оцeнки эффeктивноcти и пeрeхода нa нoвую систeму oплaты тpудa * Цeнтры oтветcтвенности в opганизации, зaинтеpесованные в paзработке и oптимизации сиcтeмы вoзнаграждения и пoкaзателей оцeнки эффeктивности (KPI). Pоль oтдeла пеpсонала * КАK PАСПРЕДЕЛИТЬ OТВEТСТВЕННОСТЬ И РOЛИ * Психoлогические ocoбенности внедpeния cистeмы мoтивaции в кoмпaнии * Пpилoжeние: Пpимepы KPI пo дoлжнocтям РEГЛАМЕНТ * 9.00-18.00 * Перeрыв 13.30-14.30 * Рeгистрация c 9.30 в xолле. CТOИМОСТЬ * 1600.00 гpн. зa однoгo учacтникa. * Для втopoго и тpетьeго учaстника cкидки — 5% и 7% сooтветственно. * B cтoимoсть вхoдит: инфoрмaционно-консультационное oбслуживaние нa сeминаре, сбоpник мaтepиалов, кoфe-бpейк, oбед в рecторане, oбcуждение дoклaдoв и oбмен мнeниями c лектoром. ОТКAЗАТЬСЯ OТ PACСЫЛКИ * Извинитe, еcли этo пиcьмo пpичинило Вaм неудoбcтва. * Baш адpес взят из открытыx иcтoчников: бaз данныx предпpиятий, форумoв, веб-caйтов и т. п. * Чтoбы откaзaться oт рaссылки, пoжaлуйста, сoобщите нaм Bаш элeктрoнный адpес пo тeлeфoну. PEГИСТРАЦИЯ * Тeл.: (044) 228-дeвять-нoль-05, 228-46-шeсть-дeвять * Фaкc: * Kaждый учаcтник семинaра получaeт бухгaлтерский комплeкт — оpигиналы документoв: дoговoр, aкт, оpигинал cчeта, кoпии cвидeтeльств.

1 0

Быcтрые pезультаты. Эффeкт мотивaции
by Cистему материального и нeмaтeриального стимулирoвания 01 Apr '13

01 Apr '13

> БЫCТPЫE PEЗУЛЬТАТЫ. ЭФФEКТ МОТИBАЦИИ > Ceминaр • 12 апрeля • 2013 г. > Kиев • Гостиницa «Миp» • пp. 40-лeтия Oктября 70 • cт. мeтpo «Голocеевская» > Тeл.: (044) 228-дeвять-нoль-05, 228-46-шесть-дeвять -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- Kaк рaзработать cиcтeму мaтepиального и нeматериального cтимулирования кaк менeджеров тaк и рядoвыx cотрудников - нa даннoм тpeнингe этoт вопрoс будeт pассмотрен детальнo. Haчинaя oт вoпpоса кaк поcтроить cистему тaк, чтoбы oплaтa прeмий и бонуcов фоpмировалась зa счeт дополнитeльно пoлучeннoй пpибыли и пошагoвая технoлогия разpаботки эффeктивной cистемы мотивaции вплoть дo должноcти. Учacтники получaт пpоeкты cистeм oплаты и прeмиpования для нeскoльких выбpанныx должноcтей, рaзpаботанные в xодe тpeнинга, a тaкже пpимеры oт Aвтoра. ДЛЯ КOГO: Трeнинг пpeдназначен pукoвoдителям и тoп-менeджерам кoмпаний, pуководителям пoдразделений и HR-cпециалистам, oтветственным зa рaзpаботку и внедpение сиcтем мaтepиального и нeматeриального стимулиpования перcонала. ЦEЛИ: * Сфoрмировать у учaстников целocтную и детaльную cиcтему матеpиальной и нeмaтeриальной мoтивации пepсонала - oт фоpмирования источникa мoтивации – допoлнитeльной пpибыли компaнии дo cиcтeмы пoстaновки цeлей и KPI и paсчетов пpeмий и бонуcoв зa выпoлнение плaнoв кaждым сoтpудником. * Прeдoставить участникaм пpaктичeские метoды и технoлогии, пoзволяющиe caмостоятельно pазработать для своeй кoмпании эффeктивную cистему стимулирoвания, обeспечивающую pоcт пpибыльности и эффeктивнoсти для кoмпaнии, c дpугой cтopоны poст удовлeтворнности цeнныx сотpудников. ЗAДАЧИ: Изучить и oтpaботать нa пpактике (c помoщью выполнeния "cквoзных" задaний в хoдe oбучения пo выбрaнным дoлжностям) слeдующие тeмы: 1. Разлoжение цeлей кoмпании веpхнего уpoвня нa нижниe уpoвни оpганизации вплoть дo сoтpудника 2. Paзработка сиcтeмы стимулиpoвания и пoвышeния внутреннeй мотивaции сoтpудников 3. Опpeделение стpуктуры oплaты тpуда для компaнии и pазличныx дoлжнoстей 4. Oпрeделение KPI для coтpудника 5. Фoрмиpование cтруктуры оплaты трудa для конкрeтной дoлжности 6. Oпределение видoв пeременных выплaт 7. Oпрeделение cистeмы измepения KPI 8. Опpеделение фoрмулы рacчета зapаботной плaты 9. Bнедрение нoвoй сиcтемы мoтивaции БИЗHEC-ТРЕНЕРА Hемировский Игoрь – гeнеральный диpектор тpeнингово-консалтинговой компaнии, конcультaнт, имeющий oпыт 17 лeт управлeния и 10 лeтний oпыт paбoты финaнсoвым диpектором в кoмпaниях лидеpaх рынкa. Автoр болee 50 публикaций в т.ч. книг «Бюджетирoвание. Oт cтpaтегии дo бюджeта пошaговое pукoводство», «Cистeма сбaлaнсированных покaзaтелей: внeдрeние, оцeнкa деятeльнoсти компaнии». Экcпepт пo вoпрoсам финансoвого упpавления, рeзультативного pукoвoдства, cтpaтегии и пoстaновки cиcтeмы упpавлeния бизнeсoм. Стapожукова Иннa – бизнec-тренер c болeе чeм 16-ти лeтним пpaктическим oпытом управлeния финaнcами холдингoвых стpуктур крупнoгo бизнeса. Экспeрт-практик в облaсти финанcов, бюджeтирoвания, cистeмы cбалaнсированных пoказaтелей, упpaвленческого учетa, aнaлизa и отчeтности. Огрoмный oпыт фoрмиpования cиcтeмы упpaвленческого учeта и контpoлинга, пocтановки теxнических зaдaний для внедpeния ERP-cиcтeм для гpуппы кoмпаний, фоpмализации бизнec пpoцeссов компaнии. ПРОГPАММА КУРCА OБУЧEНИЯ: 1. OБЩИE ВOПРОСЫ * Актуaльность вoпpосов мoтивaции * Мeтoды управлeния пepcоналом: MB-, PМ * Kак oцeнить эффeктивнoсть «oплaты пo pезультaту» * Oтличия «мотивaция», «стимулиpование» * Oсновные задaчи KPI-мотивaции - Oплата пo pезультату прoтив бeзpaзличия и бeзoтвeтственности - Oплaта пo pезультату: вoзнaграждение лучшиx и «вымываниe» xудших 2. 3D ОЦЕHКА СOТРУДНИКОВ * Oценкa пo Финансoвым KPI тoп-мeнeджеров * 4 главныx KPI – OСНОВА ФИHAHСОВЫХ ЦEЛEЙ тoп-мeнeджеров * Oцeнка пo финaнсовым KPI линейныx менеджeров * Оцeнкa пo финансoвым KPI рядoвыx сoтpудников * Oтличия «эффeктивнoсть», «прoизвoдительность», «результaтивность» * Пpaвила oпрeделения фондa оплaты трудa pядовыx coтрулников * Оценкa рeзультатов пo нeфинансовым KPI - «Минуcы» финaнсoвых пoказателей - «Плюcы» финанcoвых показaтелей: - Дoлжны ли прeмии зaвисеть иcключительно oт финaнсoво и количeственно опpeделенных рeзультaтов индивидуальнoй и коллeктивнoй дeятельности - Кaчeственная и кoличeственная оценкa pезультaтов pабoты у pядовыx сотpудников * Oцeнка иcполнeния Cтaндaртов paботы - Зaдачи внeдрения cтандартов: - Эффeкты и peзультаты oт внедрeния Стaндартов: - Чeгo нe мoгут cделaть Стaндарты: - Cтaндарты: oснoвные oтличия - Оцeнкa исполнeния cтaндартов - Cкoлько должнo быть Cтaндaртов у cотрудника - Примep paсчета KPI удовлетвoренности пoкупатeлей cтaндaртами мaгазина * Oцeнкa исполнeния SMART-зaдач * Оcнoвные пoдхoды в pазpаботке KPI - Пepвый подxод – пpoцессный. - Bтoрой подхoд – функциoнaльный. * Постpоение матpицы финaнсoвой oтвeтственности - Уpoвень финанcовой oтвественности oпрeделяет размeр бoнуca - Примep вoзмoжнoго oпpeделения структуpы постoянной и пepеменной чacти в завиcимости oт уpoвня финанcoвой oтветcтвенности. - KPI-мoтивaция должноcть или чeловeк - Раздeлите чeтко зoны финaнcoвой ответcтвенноси * Koличество пoкaзателей и пpиoритеты * Cвязь KPI c бoнуcами и oценкa peзультативности - Oтличия «бoнусы», «прeмии», «кoмиcсионные» - Kaк paзличaть лучшиx cотpудников: оцeнка peзультативности 3. Kак мoтивирoвать сoтрудников нa доcтижeние целeй и kpi * Отличиe «внешнeй» и «внутрeнней» мoтивации * Почeму увoльняются cотpудники? * Лeкaртства oт демотивaции * Унивepсальные споcобы мoтивaции * Фенoмен «cытoго дoвольcтва»: удoвлетвoренноые сoтpудники и низкaя эффективнocть * Kaкиe фaкторы влияют нa выcoкую внутpeннюю мoтивацию * Kак c пoмoщью систeмы матeриального стимулиpования мoжнo повыcить мoтивацию cотpудников * Kaк c помoщью cистемы мaтeриального стимулирoвания можнo пoвыcить эффективнoсть сотpудников * Kaк немaтeриальное cтимулирование влияeт нa эффeктивнoсть сотpудников * Кaк cбалaнсировать эффективнocть и удoвлетворенность сoтрудников 4. Раcчет фoндa оплaты трудa, pентaбельного для компaнии * Дocтижeние цeлей кoмпании – знaчит дoстижeние задaннoго урoвня пpибыли * Kакой paзмeр фoнда оплaты тpудa должeн быть в кoмпaнии – пoзиция компaнии в отpaсли * 2 оcновных подxoда к фоpмиpованию фoнда oплaты тpудa * «Спускoвой крючoк» пpемиального фoндa * Пpимep pacчета и опрeделения «спускoвого крючкa» * Пpимеp раcчета фoндa oплаты тpуда, рентaбельного для кoмпании * Критeрии качeства рaсчета фондa oплаты трудa и штатa: * Упpaжнeние рacчет штатa и фoнда oплаты трудa * Haиболее чаcто испoльзуeмые KPI в кaчеcтве «cпускoвого крючкa» * Пoрог и пoтoлoк пpемиaльного фондa * Процeнтомания: плюcы и минуcы * ПEРИОДИЧНОСТЬ СИСТEМЫ BOЗНАГРАЖДЕНИЙ * Пpимeр рacпределения пpeмиального фoндa в завиcимости oт сeзонности продaж 5. Kaк раcсчитать допoлнитeльную пpибыль, кaк иcтoчник poста пpемиaльного фондa * Финанcoвая модeль * KPI пo кoтopым неoбxодимо уcтaновить плaны * Пpимep pacчета дoполнитeльной пpибыли * Упpaжнeние: раcчет допoлнительной пpибыли * Тpи пoдxода к рaсчету плaнoвыx знaчeний KPI * ОПPEДЕЛЕНИЕ CТPУKТУРЫ ПОCТOЯННОЙ И ПEPEМЕННОЙ ЧАCТИ * Пpимep раcпределения пpeмиaльного фoнда мeжду топ-мeнеджерами 6. Pacпределение бoнуса нa кoллeктивный и индивидуaльный * Бонуcы зa доcтижение кoллeктвных KPI * Бoнуcы зa дoстижение личныx KPI * Плюcы кoллeктивнoго пpeмиpования: * Минуcы кoллeктивного пpемиpования * Cимптoмы oтcутcтвия коллeктивнoй отвeтственности * Пpимep рacпределения бoнуcа нa коллeктивный и индивидуaльный * Bыплачивать ли индивидуaльный бoнус, еcли кoмпания нe дocтиглa нужныx целeй? * Прeмии зa учaстиe в пpoектах 7. НЕМAТЕРИАЛЬНОЕ СТИМУЛИPOВАНИЕ. ПРИЗHAНИЯ И ВOЗHАГРАЖДЕНИЯ B КОМПAНИИ * Примеpы поoщpений зa конкpeтные дoстижения * Идeи нефopмальных пooщрений * Шиpoкo рaспространенные вознaгpаждения * Хоpошо видимыe вознaграждения * Вoзнaграждения, вырaжaющие Вaшу пoддepжку кaк pуковoдителя cвоиx coтpудников * Нeтипичные виды вознагpаждений 8. Opганизационные аспeкты внeдрeния систeмы оцeнки эффeктивности и пеpeхода нa нoвую cистему oплaты трудa * Цeнтры oтвeтcтвенности в оpганизации, заинтepесованные в разpаботке и oптимизaции cистeмы вознагpаждения и покaзателей oценки эффективнoсти (KPI). Рoль отдeла перcонала * KАК PАCПРЕДЕЛИТЬ OТBEТСТВЕННОСТЬ И РOЛИ * Псиxoлогические ocoбенности внедрeния cиcтeмы мoтивации в компaнии * Прилoжение: Примeры KPI пo дoлжнocтям РEГЛAМЕНТ * 9.00-18.00 * Пеpерыв 13.30-14.30 * Peгиcтрация c 9.30 в xолле. СТOИМOСТЬ * 1600.00 гpн. зa oднoгo учacтника. * Для втоpoго и тpeтьего участникa cкидки — 5% и 7% сooтветственно. * B стoимость вхoдит: инфopмационно-консультационное обcлуживaние нa сeминаре, сбоpник мaтepиалов, кoфе-брейк, обeд в pесторане, oбcуждение дoклaдов и oбмен мнeниями c лектoром. OТКAЗАТЬСЯ OТ РАCСЫЛКИ * Извинитe, eсли этo пиcьмо пpичинило Baм неудобcтва. * Вaш aдpeс взят из oткрытых иcточникoв: бaз дaнныx пpeдприятий, фоpумов, вeб-caйтов и т. п. * Чтoбы oткaзaться oт pаcсылки, пoжалуйcта, соoбщите нaм Bаш элeктрoнный адрeс пo тeлeфону. РEГИСТРАЦИЯ * Тeл.: (044) 228-дeвять-ноль-05, 228-46-шecть-девять * Фaкc: * Kаждый учacтник ceминaра пoлучаeт бухгaлтeрский кoмплeкт — opигинaлы докумeнтов: дoговор, aкт, оpигинaл cчeта, кoпии свидетeльств.

1 0

Credits accounting
by Vesna Manojlovic 25 Mar '13

25 Mar '13

Dear RIPE Atlas community, As we previously announced, we have now enabled tighter accounting of the credits that you earn and spend. This is part of the process to get rid of limits that are imposed on the number of probes you can use or number of measurements you can do. We are planning to make those limits more relaxed next month, but in order to do so we had to make the accounting more strict. From now on, if you are approaching zero credits, you will get a warning email; if you go on spending credits at the same rate, we will stop some of your measurements. You can find out more about earning and spending credits here: https://atlas.ripe.net/doc/credits You can see your own credit amount and history under "My Atlas" then "My Measurements". Background about the credit system: The credit system and all limitations were put in place to protect the system from overload, and to ensure fairness. Normally, you earn credits by hosting a probe. RIPE NCC members (LIRs) can also ask for 1,000,000 extra credits. Additionally, you can earn more credits by hosting a RIPE Atlas anchor, or by sponsoring multiple probes. If you have unused credits, you can transfer them from your account to a friend or colleague or, similarly, receive extra credits from them. However, if you have a particular measurement idea that would require more credits than you have available, and your measurements will contribute to the Internet community when the results are analysed and published, then we are more than happy to give you enough credits. Please get in touch with us for more details. Regards, Vesna -- Vesna Manojlovic BECHA(a)ripe.net Senior Community Builder @Ms_Measurements for Measurements Tools RIPE NCC http://ripe.net

1 0

Easy LG-style ping/traceroute interface?
by Roman Mamedov 19 Mar '13

19 Mar '13

Hello, I would like to suggest for RIPE to implement a simple "Looking Glass" style interface to run one-time measurements (ping and traceroute) on probes. If anyone doesn't know what Looking Glass is, some examples are http://lg.he.net/ , http://www.oneasiahost.com/lg/ , http://cl.edis.at/ etc. Key features of such Atlas interface would be: - Interface similar to generic "Looking Glasses" as those mentioned above; - Allow access to general public, not requiring registration or login (maybe with some rate-limiting on requests); - Allow running ping and traceroute from any probe (or maybe only from a subset, hosts of which express a desire to participate in this public LG subproject), to any arbitrary IPv4/v6/hostname destination; - One-shot execution only (not scheduled checking over time, like the current measurements); - Real-time returning of the results(!); this might be tricky, it means a RIPE server will need to have means to instantly connect to the selected probe, ask it to perform a measurement and then retrieve results, all in "online" real-time mode. This might exclude probes which are behind a NAT and without IPv6 or with strict firewalling. -- With respect, Roman

2 1

Include country code in UDM "Last 100"
by Adam Piggott 06 Mar '13

06 Mar '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I've just run my first UDM for a real-world diagnostic test. Very helpful! If the "Last 100" list data contained a country code column it would be helpful - especially when trying to track down a possible routing problem that may be related to the originator country. It would also be quite helpful to be able to add participating probe criteria using a negative, for example: "not GB, not US". Regards, - -- Adam Piggott, Proprietor, Proactive Services (Computing). http://www.proactiveservices.co.uk/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (MingW32) iEYEARECAAYFAlE2NmYACgkQ7uRVdtPsXDnHQACggHcxMZVmwodiNdwuZ48KATgz itIAn2Bk8F0rbS02WbHhl9NUlkZH+R27 =DTMB -----END PGP SIGNATURE-----

2 1

RIPE66 and another Atlas BoF?
by Vesna Manojlovic 05 Mar '13

05 Mar '13

Hi everyone, RIPE meeting in Dublin is approaching fast, and we are preparing for it full speed... ... which brings me to you - the RIPE Atlas Community! Will you be there? Do you want to have another BoF session? Would you like to share some of your experiences - with measurements, results, visualizations, success stories, use cases... Do you have questions to ask developers - tricks & tips, new features, favorite option that is missing? Few of the RIPE Atlas "staff" (RIPE NCC staff) will be there, we are available to talk with you in the hallways and during drinks, we will be giving official updates & presentations... ... but if you want the meeting of like-minded users and contributors, please do let me know, and I will request a BoF slot again. Cheers, Vesna http://ripe66.ripe.net

1 0

New version of probe firmware released: 4500
by Vesna Manojlovic 28 Feb '13

28 Feb '13

Dear probe hosts and community, few days ago we released the new version of RIPE Atlas probe firmware: 4500. These are the technical details: * RIPE Atlas probe software now supports two more architectures: TP-Link (for the next generation probes) and CentOS (for RIPE Atlas anchors). * There is now support for one-off measurements for ping, traceroute, DNS, and HTTPget. * We fixed a bug in DNS measurements in which, when querying local resolvers, more queries went to the last resolver. * Fixed "error" : { "TUCONNECT" : "Success"}. Before this version DNS TCP and HTTPget reported an error message "Success". When enough probes have been automatically upgaded to this new firmware, this will enable us to start testing the "one-off" or "near-real-time" measurements. We will enable this first for beta-testers, and after we fix the bugs reported by them, we will mae it available to all probe hosts, sponsors, and RIPE NCC members. Regards, Vesna

1 0

Notification regarding corrections to credit balances.
by Daniel Quinn 19 Feb '13

19 Feb '13

Dear all, We'd like to inform you that we've recently discovered a bug in our accounting process that has caused some of you to be allocated fewer credits than you deserve. We've fixed the bug today. We are now calculating exactly how many credits have not been accounted for, and we will be crediting everyone's accounts accordingly. We apologise for the mix up, and if you have any questions, please feel free to ask.

1 0

Warnings about running out of credits and runaway measurements
by Robert Kisteleki 18 Feb '13

18 Feb '13

Dear Atlas users, Today we're going to enable two features that have been forecasted in the January 2013 Atlas update (https://labs.ripe.net/Members/becha/ripe-atlas-january-2013-achievements) Both of these features are intended to prevent runaway measurements which consume system resources, and to limit the resources used by users who don't contribute (any more) to the system; thus they both contribute to the stability and scalability of RIPE Atlas. They are both controlled by the credit system. The first feature is about sending warning emails if someone is about to run out of credits. That is, if the current credit consumption rate (with a two day lookback period) seems to use up all credits of a particular user within the next week or so, then we'll send an email about this. This allows the user to organise some extra credits, or stop some less important measurements in due time. The second feature stops measurements if someone actually runs out of credits. For now we'll use a *warning only* mode -- that is, the process will not actually stop measurements, it will only send emails. After a couple of weeks we'll change this to actually stop (some of the) measurements as well as notify the user. Our tests show that at the moment there are about a dozen people who would see effects of these processes. Both of these are necessary steps towards removing the existing limits imposed by the system (such as maximum amount of probes that can be used). Please let us know if you have questions or concerns, either on this mailing list, or (privately) by sending a mail to atlas(a)ripe.net Best regards, Robert Kisteleki RIPE Atlas team

1 0

Phase 1 of RIPE Atlas Anchors pilot - report on RIPE Labs
by Vesna Manojlovic 15 Feb '13

15 Feb '13

Dear community, [apologies for the duplicates] we just published an article on RIPE Labs with the status & features available for the hosts of RIPE Atlas Anchor boxes after the Phase 1: https://labs.ripe.net/Members/becha/ripe-atlas-anchors-pilot-update-on-phas… Share and enjoy :) Vesna

1 0

UDM destinations also visible in RIPEstat
by Vesna Manojlovic 13 Feb '13

13 Feb '13

Hi, I just wanted to share one more RIPE Atlas-related feature of RIPEstat: when querying for a IP prefix or AS number, you can now see all the UDMs that terminate in the IP addresses in that ASN or prefix, in the "Activity" tab, called "RIPE Atlas measurements targets". (picture attached) Below is a reminder of the feature to see all the probes, too. Happy measuring! Vesna -------- Original Message -------- Subject: [atlas] Atlas probes visible in RIPEstat Date: Fri, 21 Dec 2012 10:11:26 +0100 From: Vesna Manojlovic <BECHA(a)ripe.net> To: RIPE Atlas People <ripe-atlas(a)ripe.net> Dear RIPE Atlas users, this might be of interest to you too -- it is now possible to see coverage of Atlas probes in any ASN, prefix or *country* in RIPEstat! It works both as a widget and as CLI: https://stat.ripe.net/widget/atlas-probes#w.resource=212/12 or whois -h stat.ripe.net AS3333 If you decide to embed this widget somewhere on your page, please do let us know, we like to see our work being used :) More interesting RIPEstat features in the article on RIPELabs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripestat-2012-december-… Cheers, Vesna

1 0

RIPE Atlas Community repository on GitHub
by Vesna Manojlovic 08 Feb '13

08 Feb '13

Hi everyone, an appropriate pastime for Friday afternoon - playing with GitHub ;-) I initially created https://github.com/RIPE-Atlas-Community/ripe-atlas-community-contrib for the contributions by you (and atlas-dev team) of the small programs, scripts, etc -- for visualizing RIPE Atlas measurements, analysing measurements data, and so on. We already had them listed here: https://atlas.ripe.net/doc/code However, GitHub seems to be *the* place for the community to exchange the code, so I am hoping that this repository will help share and maintain, and produce more code, and make it more useful for the rest of the world. First code in there is the one I inserted, created by Philip Homburg: "probes2kml.py", that shows probes on Google Earth. Please "add" more, or "link" your own contributions to this repository... ... or let me know how I can help to collect more of the RIPE Atlas specific code to this repository: from Wolfgang, Inigo, and others. Share and enjoy :) Regards, Vesna

1 0

Partial downtime over the weekend
by Robert Kisteleki 04 Feb '13

04 Feb '13

Dear all, On Friday we added the first devices of the upcoming next generation Atlas probes to our production network. Unfortunately, this triggered a bug in our controlling infrastructure, which resulted in some of the probes not being assigned any new measurements. Eventually, the affected probes ran out of measurement tasks. This bug affected about 30% of the probes approximately between Friday 23h and Sunday 12h (UTC). We apologise for any inconveniences this may cause. Regards, Robert Kisteleki RIPE Atlas team

1 0

New release in January, features you asked for...
by Vesna Manojlovic 01 Feb '13

01 Feb '13

Hi, we had a release 2 days ago, maybe you already noticed new features... * REST API -- althou in Beta! https://atlas.ripe.net/doc/rest * New costs for certain measurements: https://atlas.ripe.net/doc/credits & * 20 instead of 19 probes visualized in ping UDMs :) ... and if not, they are listed on RIPE Labs article: https://labs.ripe.net/Members/becha/ripe-atlas-january-2013-achievements ... and on the "announcements" page too: https://atlas.ripe.net/announce We are still working on "group access", and few more features are going to be announced to beta-testers soon. Share and enjoy! Regards, Vesna

4 4

2 probes down
by Jan Hugo Prins 23 Jan '13

23 Jan '13

Hello, This morning I got a notification that the probe in my datacentre is down. I checked everything and he looks just fine and is happily doing traffic. Then I noticed that the one behind my home fiber connection is also down, and that the starttime is about the same. Both of them at 6:56 this morning. Also checked that one and he is also doing traffic just fine. Houston, do we hava a problem? -- Met vriendelijke groet / Best regards, Jan Hugo Prins Infra and Isilon storage consultant E: jprins(a)betterbe.com T: +31-53-4800694 M: +31-6-26358951 S: jhaprins W: www.betterbe.com <http:///www.betterbe.com>

2 1

Thank you for making the 2012 a great year for RIPE Atlas!
by Vesna Manojlovic 16 Jan '13

16 Jan '13

Dear RIPE Atlas community, many thanks for hosting, testing & using RIPE Atlas! We have reached many milestones last year, and are looking forward to new challenges this year. Please see the story of the RIPE Atlas achievements in this RIPE Labs article: https://labs.ripe.net/Members/becha/ripe-atlas-2012-a-year-in-review Regards, Vesna -- Vesna Manojlovic BECHA(a)ripe.net Senior Community Builder @Ms_Measurements for Measurements Tools RIPE NCC http://ripe.net

1 0

Parametrization of UDM requests?
by Stephane Bortzmeyer 15 Jan '13

15 Jan '13

It seems that the parameters used for an UDM are the same for all probes. For instance, I would like to do a DNS UDM with a different question for each probe, something like "%p.mydomain.example" where %p would be replaced by the Probe ID. Is it possible? Or do you think it would be a worthwile improvment?

2 3

UI graphs
by nrw＠kaffeeschluerfer.com 10 Jan '13

10 Jan '13

On Tue Jan 8 08:15:44 CET 2013, Florian Bauhaus f.bauhaus at portrix-systems.de wrote: > On 01/07/13 22:57, Olaf Maunz wrote: > > The graphics for the pings seem to have vanished in the UI. At least for my account... > > > > If you open the ping UDM there is (at least for me) an tab that says 'RRDs' and there you have all the graphs. I think Olaf did not refer to the UI of the UDMs, but to the UI of the probes. At least for me as well, the graphs of the statistics started to show no data for a period starting sometime between Jan 5 and Jan 6, 2013. At some point, I got the message that there was some maintenance going on on the Atlas infrastructure side. However, nothing changed with respect to the graphs not showing current data once the maintenance was through. Interestingly, the graphs started showing something again for data collected starting as of about 8 AM UTC this morning. Apart from some interruptions due to my public IP address changing, my probe was considered "up" all the time, and I also saw it running its tests and getting responses to the various probe messages. However I still need to figure out (I am sure it is in the documentation, I just didn't get around to looking for the relevant parts yet) how to access the raw data for recent measurements to see whether that data not being displayed in the graphs was due to the collected data somehow not getting to the Atlas infrastructure for some reason (despite probe being considered up), or whether there was just an issue displaying the collected data. Has anyone else seen similar issues and/or some idea what might have happened? Thanks! Kind regards, Joachim

2 3

[UDM] Cannot select "recursion desired" for DNS
by Stephane Bortzmeyer 08 Jan '13

08 Jan '13

When creating a new UDM with DNS (or DNS6), the checkbox "Recursion desired" is greyed and un-selectable. I know that recursion can request more resources from the DNS servers. Is it why it is currently unavailable? It does not seem documented in <https://atlas.ripe.net/doc/udm> which just says: Recursion desired Enable recursion. This is the RD flag described in RFC1035.

4 4

UI graphs
by Olaf Maunz 08 Jan '13

08 Jan '13

The graphics for the pings seem to have vanished in the UI. At least for my account...

2 1

UDM traceroute from all probes to single destination
by Павел Веселовский 24 Dec '12

24 Dec '12

Hello, For our study seems necessary to obtain traceroutes (IPv4/v6) from all probes to single destination (probe or IP address). Is it possible to obtain such raw data? -- Thanks in advance & Best Regards -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- Pavel Veselovskiy, Samara State Aerospace University, IT engineer Email: vpv(a)ssau.ru Phone: +7 927 686 12 32

2 1

UDM "Do not visualize" button issue
by ripe＠brite.cz 22 Dec '12

22 Dec '12

Hi team, I'm not sure what I am doing wrong, but I'm not able to have visual graphs created. No matter if I check or uncheck the "Do not visualize" button, after UDM creation finished the button "Do not visualize" becomes always checked and grayed. Is it possible to get graphs drawed somehow? Thank you, Jiri, probe 2413

3 3

Atlas probes visible in RIPEstat
by Vesna Manojlovic 21 Dec '12

21 Dec '12

Dear RIPE Atlas users, this might be of interest to you too -- it is now possible to see coverage of Atlas probes in any ASN, prefix or *country* in RIPEstat! It works both as a widget and as CLI: https://stat.ripe.net/widget/atlas-probes#w.resource=212/12 or whois -h stat.ripe.net AS3333 If you decide to embed this widget somewhere on your page, please do let us know, we like to see our work being used :) More interesting RIPEstat features in the article on RIPELabs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripestat-2012-december-… Cheers, Vesna

1 0

Updates since the previous "roadmap" announcement: November's features on RIPELabs
by Vesna Manojlovic 18 Dec '12

18 Dec '12

Dear RIPE Atlas community, here's a link to the article about what we implemented & worked on in November (and December): https://labs.ripe.net/Members/becha/ripe-atlas-roadmap-november-2012-update Highlights: - higher increase in number of probes & users - Community Pages - blogs covering Atlas (and undressing probes ;-) We are also busy making plans for 2013, and will let you know of them in January. As always, we are looking forward to your comments. Regards, Vesna

1 0

single measurement
by Pelsser Cristel 06 Dec '12

06 Dec '12

Hi, When launching measurements, we can specify a start time, end time and interval. Is it possible to specify that we want a single measurement (for example, a single traceroute from the list of probes to the destination) instead of playing with the start time, end time and interval? Cristel

2 2

IPv4/DNS entry not updated
by Daniel Gomez 04 Dec '12

04 Dec '12

Good Morning everyone, After a DSL restart from my ISP at 2:00, atlas.ripe.net has not updated the IPv4 and with it the DNS. The proble is online but it is listed as down. "dig A p4065.probes.atlas.ripe.net" is showing my IP from yesterday. There is any way to push an "update", in order for the probe to register the right IP ? Greetings, Daniel Gomez

2 1

Two users managing one probe
by Matthäus Wander 03 Dec '12

03 Dec '12

Hi, is it possible to register the same probe by two different users? I would like to give my co-worker full access to a probe in our group LAN. Kind regards, Matt -- Universität Duisburg-Essen Verteilte Systeme Bismarckstr. 90 / BC 316 47057 Duisburg

5 5

New page: RIPE Atlas Community
by Vesna Manojlovic 13 Nov '12

13 Nov '12

Good morning :) Since yesterday, we have a new page that shows the activity of the RIPE Atlas users community: https://atlas.ripe.net/atlas/community We are publishing top-ten hosts of the "Always Up" probes, top-ten UDM users: "Big Spenders" -- people who spend most credits, by doing the most measurements, and the flowing list of new arrivals, with flags of their countries. (Now you can see that there was IETF last week -- Bert gave away 55 probes!) Enjoy your additional few minutes of fame, if you name appears on one of these lists :) We are looking forward to your compliments, and to the further wishes on what else would you like to see here... We will be featuring these top-users in our communication, so expect some more attention from us... Ciao, Vesna

2 1

RIPE Atlas nominated for an ISOC Award
by Vesna Manojlovic 08 Nov '12

08 Nov '12

Hi guys, a bit of good news and publicity: RIPE Atlas has been nominated for an award by the Netherlands chapter of the Internet Society (ISOC). Please find a short announcement on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-nominated-fo… Makes me feel proud for being part of it :) Since RIPE Atlas if build with your help - congratulations, well done! Cheers, Vesna

2 1

Re: [atlas] "down" probe resurrection
by Artur Russu 08 Nov '12

08 Nov '12

Hi Philip, Connected it to my home network, directly to my provider, it has now a public IP address assigned by ISP's dhcp. Powered it from an USB power outlet (it has now 5 V/500 mA). Still reboots... :( What do your logs say? I will leave it like this for 24 hours. I guess that if this setup will still fail we'll have to return the probe to RIPE. Where can I find the procedure of returning a probe? Best Regards, Artur Russu PS Engineer TD / MCN / Mobile Packet Core Orange Moldova S. A. Tel.: +373 22 975381 Tel.: +373 691 98381 E-mail: artur.russu(a)orange.md

1 0

Probe sending DHCP request, not accepting?
by Michael-John Turner 07 Nov '12

07 Nov '12

Hi My probe arrived late last week and I finally hooked it up late yesterday afternoon. All was working fine until around 3:30am today when I received an automated email to say that my probe was down. I restarted it at around 7:00am when I got up but that didn't help - ever since it's been requesting a new IP every 3-5 seconds but not accepting the offered lease. From my dhcpd logs: Nov 6 07:12:02 dreamland dhcpd: DHCPDISCOVER from aa:bb:cc:dd:ee:ff via br0 Nov 6 07:12:02 dreamland dhcpd: DHCPOFFER on 192.168.1.248 to aa:bb:cc:dd:ee:ff via br0 Nov 6 07:12:05 dreamland dhcpd: DHCPDISCOVER from aa:bb:cc:dd:ee:ff via br0 Nov 6 07:12:05 dreamland dhcpd: DHCPOFFER on 192.168.1.248 to aa:bb:cc:dd:ee:ff via br0 (where aa:bb:cc:dd:ee:ff is the correct MAC, I've just redacted it). I've allocated the device a static IP based upon its MAC. Help! :) My probe ID is 3508. -mj -- Michael-John Turner mj(a)mjturner.net <> http://mjturner.net/

2 4

Question on UDMs
by Roman A. aka BasicXP 07 Nov '12

07 Nov '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello! First of all, I'd like to thank RIPE for such an interesting project, allowing to study the availability of various resources online. I have a question. If I'd like to set up a UDM, that will only be designated for my probe only, will it require credits or using my own probe is "free"? Thank you in advance. _____ Best regards, Roman A. aka BasicXP x12ozmouse(a)ya.ru -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJQk7vQAAoJEBjQX5UpOG9YquQP/RptIW1NbaPdOPczWUTYvjxB ZMRNHWO/VX2RWeYMIRWcoUpqVJSV2f7Sy+55hG6kkkcnWvXb+Do9ro4/MsyXocsD y+AXzgt9zgEaQMtJsgr7gjOttRp4vl9Y9RiQ/NfAV/QMZj6YH0QuoqjhpSLDYs6H bA8rmCAx2RGOTlhEvQTBnwI/K6zO8Cp9psLyQ1hzkQeUqlZbOGtD4AGpBuLOcrGR cHyckfN3Lww83oaecBEU1wjgOgUuHzTQzoJKhU7CLr0h0EeBC60Qd9CD75CW7yUD pAZA3JUHhAsYh4Bw5NDihuRhRqDYfo+Ch63JZvdNxznWgRXPgNjm8dm9BqC3rOM2 /aYo4MnglRke7VqCw9vPkw1IW/aXCfx7OoOt4Vp17dKal5iOS/FT2u58qFkzeLRT Mn90I5EdcEbB+Nuv3GsjYBI94JrrSK2KtcoV235mSTAGYyAM665c3fVR+HkOc9Eu s/msjchT3MBlEini6HVqAqdTFDaCro+mOw53lKzCch8VQSJRTrbHz1S7RgRVK9dB 89E1ij3HhUv6Tz9y3fGvWmNwFCWxgkY0qnB8erlFDcTxBtg/ou+a5oU2Yd6Pa14n HaZfXgzSjpasDSTDzxfLzpG/w7qhAluQgo2Q+fViG8yweVWvCDT9DrvbTEuUrPFq TuxIjj0uFFzfPUZrSTrW =GYfh -----END PGP SIGNATURE-----

4 7

New RIPE Atlas features from October, and roadmap for November and beyond
by Vesna Manojlovic 01 Nov '12

01 Nov '12

Dear RIPE Atlas users, I am pleased to announce the whole lot of new things you can do with RIPE Atlas in/since October: - one new map (comparing TCP & UDM DNS measurements) - easier credits administration - and for some of you, we worked together further on Atlas Anchors There's more, with pictures, in the RIPE Labs article: https://labs.ripe.net/Members/becha/ripe-atlas-roadmap-october-2012-update We are also announcing many new features till the end of the year, and plans for few months in the future, for example: - more notifications - more APIs - promoting active users etc Please let us know if you want us to increase the priority of some of the ones listed in the article. Regards, and enjoy the measurements, Vesna

1 0

Fwd: Issues encountered with assigning .0 and .255 as usable addresses?
by Tore Anderson 24 Oct '12

24 Oct '12

Here's a suggestion for an Atlas experiment and subsequent RIPE Labs article. Do a ping measurement from all the probes to the .0 and .255 address of the same /24, plus to another control address in the same /24, and compare success rates. It's particularly interesting for me as my own personal home page is accessible at 87.238.60.0 at the moment.., Might also be worth checking it out for IPv6 at the same time (at least the case where the last 64 bits are all zeroes). Tore -------- Opprinnelig melding -------- Emne: Issues encountered with assigning .0 and .255 as usable addresses? Dato: Mon, 22 Oct 2012 22:07:50 +0000 Fra: Paul Zugnoni <paul.zugnoni(a)jivesoftware.com> Til: nanog(a)nanog.org <nanog(a)nanog.org> Curious whether it's commonplace to find systems that automatically regard .0 and .255 IP addresses (ipv4) as src/dst in packets as traffic that should be considered invalid. When you have a pool of assignable addresses, you should expect to see x.x.x.0 and x.x.x.255 in passing traffic (ie. VIP or NAT pool, or subnets larger than /24). Yet I've run into a commercial IP mgmt product and getting reports of M$ ISA proxy that is specifically blocking traffic for an IP ending in .0 or .255. Any experience or recommendations? Besides replace the ISA proxy…. Since it's not mine to replace. Also curious whether there's an RFC recommending against the use of .0 or .255 addresses for this reason.

2 1

New probe firmware released: version 4.480
by Vesna Manojlovic 24 Oct '12

24 Oct '12

Hi everyone, few days ago we have released a new version of the probe firmware: 4.480. It introduces few bug fixes, and improvements that enable us to work on new features, but that still require work on the User Interface to make it visible to users. Until now, about 1.500 probes have been upgraded to new firmware. Below are the technical details. Regards, Vesna * Fixed bug in traceroute when it has to deal with rfc4884 objects (mpls) that have a wrong size. * Delayed DNS name resolution in ping and traceroute. This feature will soon be enabled through the UI. * Fixed bug in HTTP GET where some characters where not properly escaped in generating the result JSON. * Fixed bugs in the libevent stub resolver to better handle DNS errors and timeouts (affects mostly httpget) * Limit the amount of measurement data that is sent as one unit. This prevents probes that have not connected to a controller for some time from overloading the controller. * The probe uptime is now in the DNS SOS messages that are sent by probes before they try to connect. This will allow making a distinction between various reasons for disconnects: e.g. probe reboot vs. network problems. (also published on https://atlas.ripe.net/announce )

1 0

Convert json traceroute output to normal traceroutes.
by Jan Hugo Prins 17 Oct '12

17 Oct '12

Hi, Because I'm a little more used to reading regular traceroute output instead of JSON files, I created a little python script to convert the ATLAS traceroute output to readable traceroutes. Comments are always welcome ofcourse. The whois information is gathered from Cymru using: https://github.com/JustinAzoff/python-cymruwhois -- Met vriendelijke groet / Best regards, Jan Hugo Prins Infra consultant E: jprins(a)betterbe.com T: +31-53-4800694 M: +31-6-26358951 S: jhaprins W: www.betterbe.com

4 5

Forcing https in Atlas
by Robert Kisteleki 16 Oct '12

16 Oct '12

Dear Atlas users, At the moment the Atlas UI servers allow regular, unsecured (http) connections from clients. For particular features, most notably anything that requires authenticated users, we're using secure (https) connections. Unfortunately, the potential mixing of the two schemes causes glitches and inconsistencies for some users. Therefore on 15 October we will start enforcing secure connections towards the Atlas UI servers (atlas.ripe.net and *.atlas.ripe.net). We'll do this by automatically redirecting all http queries to their https equivalents. This should not cause any changes to those of you who already use https by default, and should not cause any notable changes to anyone else. However, some clients (especially CLI based ones) may need some extra flags to deal with https connections. Regards, Robert Kisteleki

2 2

A Case Study of AAAA Filtering
by Vesna Manojlovic 15 Oct '12

15 Oct '12

Hi all, at RIPE 65, Lorenzo Colitti from Google raised the question whether Internet users would see significant filtering of AAAA DNS queries or replies, either by their ISP or by their Customer Premise Equipment (CPE). Emile & Philip used RIPE Atlas to provide an answer to this question. https://labs.ripe.net/Members/emileaben/ripe-atlas-a-case-study-of-aaaa-fil… Regards, Vesna

4 5

Atlas main database maintenance
by Andreas Strikos 15 Oct '12

15 Oct '12

Dear Atlas users, Tomorrow around 09:30 CEST we will bring down our main database for maintenance. Hopefully, the whole process will not take more than 2 hours. The majority of the web site functionalities and user interaction with the system will not be available but we don't expect any loss of data flowing in from the probes. We are sorry for any inconvenience this might cause. Regards, Andreas Strikos

1 0

traceroute via ICMP?
by Jens Weibler 10 Oct '12

10 Oct '12

Hi, how is the development of traceroute via ICMP going? My central firewall team doesn't like opening many udp-ports for traceroute :( -- Jens Weibler IT-Services Hochschule Darmstadt www.h-da.de University of Applied Sciences Fachbereich Informatik www.fbi.h-da.de Schöfferstr. 8b D-64295 Darmstadt Tel +49 6151 16-8425 Fax +49 6151 16-8935 jens.weibler(a)h-da.de

2 3

Ping does no longer visualize?
by Sebastian Wiesinger 05 Oct '12

05 Oct '12

Hi, I just noticed that the Ping probe has changed, I can now enter more options but I'm unable to visualize the results. Even if I uncheck "do not visualize" I get no graphs. Regards Sebastian -- noris network AG - Thomas-Mann-Straße 16-20 - D-90471 Nürnberg Tel +49-911-9352-0 - Fax +49-911-9352-100 http://www.noris.de - The IT-Outsourcing Company Vorstand: Ingo Kraupa (Vorsitzender), Joachim Astel, Hansjochen Klenk - Vorsitzender des Aufsichtsrats: Stefan Schnabel - AG Nürnberg HRB 17689

2 2

RIPE Atlas roadmap, September 2012 version
by Vesna Manojlovic 05 Oct '12

05 Oct '12

[apologies for duplicates] Dear colleagues, we just published a RIPE Labs article with the RIPE Atlas roadmap update for September: https://labs.ripe.net/Members/becha/ripe-atlas-roadmap-september-2012-update (the fact that is already October today is a bit confusing, but we presented this version during the RIPE 65 meeting last week...) This is the invitation to look at our plans, and let us know what you think, so that we can take that into account when making new plans, next month. Thanks, Vesna

1 0

Cannot change network configuration
by Tibor Djurica Potpara 04 Oct '12

04 Oct '12

Hello, I have recently changed the router that my Atlas probe is connected to. Since it is now in a separate subnet from my home LAN, with dedicated DHCP/RA configuration, there is no longer need for static address configuration, so I would like to revert its settings back to autoconfiguration for both IPv4 and IPv6. However, in the web interface,//"Change Probe's Network Configuration" menu is greyed out, so I cannot do anything even though the probe is up. What am I to do? Thank you, Tibor

4 3

Strange IPv6 problem with Atlas
by Max Grobecker 02 Oct '12

02 Oct '12

Hello, I got my new Atlas a few days ago and connected it to my network (in a separated VLAN). In this VLAN I'm announcing routing advertisements with autonomous IPv6 addressing enabled. Appearently the probe heard this advertisement and have chosen to communicate over IPv6 - but with a link-local IPv6 address only...?! This leads to "Beyond scope"-Messages from my router which I captured with tcpdump: fe80::280:a3ff:fe91:4070.58730 > 2a01:4f8:161:3281::43:148.443: Flags [S], seq 2585125851, win 5360, options [mss 1340,sackOK,TS val 4294950236 ecr 0,nop,wscale 1] fe80::225:90ff:fe92:2478 > fe80::280:a3ff:fe91:4070: ICMP6, destination unreachable, beyond scope 2a01:4f8:161:3281::43:148, source address fe80::280:a3ff:fe91:4070 My routing advertisements are currently looking like that: fe80::225:90ff:fe92:2478 > ff02::1: [icmp6 sum ok] ICMP6, router advertisement, length 64 hop limit 64, Flags [none], pref medium, router lifetime 1800s, reachable time 0s, retrans time 0s prefix info option (3), length 32 (4): 2a02:a00:e000:b:e6::/96, Flags [onlink, auto, router], valid time 86400s, pref. time 14400s mtu option (5), length 8 (1): 1400 source link-address option (1), length 8 (1): 00:25:90:92:24:78 Is there anything I can do to make the probe communicate over IPv6? Manual IP configuration is not possible since the menu item is greyed out (althrough my probe runs on FW 4470). I disabled RA at the moment so the Atlas cube can talk to the RIPEs Atlas servers. Thank you in advance! -- Greetings from Wuppertal, Germany Max Grobecker

3 3

10/8
by Randy Bush 01 Oct '12

01 Oct '12

an external border, where an atlas probe is on the soft gooey inside, logged packets sourced from 10/8? could this have been the atlas probe? randy Sep 29 08:36:44 r0.sea.rg.net 390: Sep 29 08:36:43.966: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(53649) -> 23.63.172.166(443), 1 packet Sep 29 08:36:49 r0.sea.rg.net 391: Sep 29 08:36:48.466: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(46959) -> 23.63.205.115(443), 1 packet Sep 29 08:42:32 r0.sea.rg.net 392: Sep 29 08:42:31.363: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(53649) -> 23.63.172.166(443), 1 packet Sep 29 11:24:45 r0.sea.rg.net 393: Sep 29 11:24:44.826: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(32986) -> 64.12.235.15(443), 1 packet Sep 29 11:31:35 r0.sea.rg.net 394: Sep 29 11:31:34.644: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(53512) -> 143.225.229.137(554), 1 packet Sep 29 11:37:32 r0.sea.rg.net 395: Sep 29 11:37:31.453: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(53512) -> 143.225.229.137(554), 8 packets Sep 29 11:43:21 r0.sea.rg.net 396: Sep 29 11:43:20.339: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(59262) -> 38.102.136.104(80), 1 packet Sep 29 11:43:33 r0.sea.rg.net 397: Sep 29 11:43:32.151: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60780) -> 69.171.228.74(443), 1 packet Sep 29 11:45:23 r0.sea.rg.net 398: Sep 29 11:45:22.013: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60761) -> 69.171.228.74(443), 1 packet Sep 29 11:45:26 r0.sea.rg.net 399: Sep 29 11:45:25.017: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60759) -> 69.171.228.74(443), 1 packet Sep 29 11:48:57 r0.sea.rg.net 400: Sep 29 11:48:56.480: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(46352) -> 174.37.29.147(80), 1 packet Sep 29 11:49:32 r0.sea.rg.net 401: Sep 29 11:49:31.465: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60780) -> 69.171.228.74(443), 1 packet Sep 29 11:49:32 r0.sea.rg.net 402: Sep 29 11:49:31.465: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60781) -> 69.171.228.74(443), 2 packets Sep 29 11:50:32 r0.sea.rg.net 403: Sep 29 11:50:31.466: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60761) -> 69.171.228.74(443), 1 packet Sep 29 11:50:32 r0.sea.rg.net 404: Sep 29 11:50:31.466: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60759) -> 69.171.228.74(443), 1 packet Sep 29 11:54:32 r0.sea.rg.net 405: Sep 29 11:54:31.469: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(46352) -> 174.37.29.147(80), 1 packet Sep 29 12:10:05 r0.sea.rg.net 406: Sep 29 12:10:04.260: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60333) -> 193.0.6.139(443), 1 packet Sep 29 12:10:11 r0.sea.rg.net 407: Sep 29 12:10:10.292: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60348) -> 193.0.6.139(443), 1 packet Sep 29 12:10:24 r0.sea.rg.net 408: Sep 29 12:10:22.640: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60363) -> 193.0.6.139(443), 1 packet Sep 29 12:13:30 r0.sea.rg.net 409: Sep 29 12:13:29.535: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(33721) -> 193.0.6.133(443), 1 packet Sep 29 12:14:10 r0.sea.rg.net 410: Sep 29 12:14:09.435: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(37936) -> 178.63.78.16(80), 1 packet Sep 29 12:14:29 r0.sea.rg.net 411: Sep 29 12:14:28.256: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(33754) -> 193.0.6.133(443), 1 packet Sep 29 12:15:32 r0.sea.rg.net 412: Sep 29 12:15:31.489: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60348) -> 193.0.6.139(443), 2 packets Sep 29 12:15:32 r0.sea.rg.net 413: Sep 29 12:15:31.489: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60363) -> 193.0.6.139(443), 1 packet Sep 29 12:15:32 r0.sea.rg.net 414: Sep 29 12:15:31.489: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60364) -> 193.0.6.139(443), 2 packets Sep 29 12:15:32 r0.sea.rg.net 415: Sep 29 12:15:31.489: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60366) -> 193.0.6.139(443), 2 packets Sep 29 12:19:32 r0.sea.rg.net 416: Sep 29 12:19:31.492: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(37936) -> 178.63.78.16(80), 2 packets Sep 29 12:19:32 r0.sea.rg.net 417: Sep 29 12:19:31.492: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(33754) -> 193.0.6.133(443), 2 packets Sep 29 12:21:00 r0.sea.rg.net 418: Sep 29 12:20:59.386: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(39687) -> 206.219.196.114(443), 1 packet Sep 29 12:21:42 r0.sea.rg.net 419: Sep 29 12:21:41.318: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(39683) -> 206.219.196.114(443), 1 packet Sep 29 12:23:57 r0.sea.rg.net 420: Sep 29 12:23:56.533: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(56161) -> 88.221.216.66(80), 1 packet Sep 29 12:24:20 r0.sea.rg.net 421: Sep 29 12:24:19.673: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(39741) -> 206.219.196.114(443), 1 packet Sep 29 12:26:32 r0.sea.rg.net 422: Sep 29 12:26:31.499: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(39687) -> 206.219.196.114(443), 2 packets Sep 29 12:27:32 r0.sea.rg.net 423: Sep 29 12:27:31.500: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(39683) -> 206.219.196.114(443), 10 packets Sep 29 12:28:53 r0.sea.rg.net 424: Sep 29 12:28:52.193: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(44361) -> 64.12.104.224(443), 1 packet Sep 29 12:29:32 r0.sea.rg.net 425: Sep 29 12:29:31.502: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(56162) -> 88.221.216.66(80), 7 packets Sep 29 12:29:32 r0.sea.rg.net 426: Sep 29 12:29:31.502: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(56161) -> 88.221.216.66(80), 6 packets

3 4

RIPE Atlas at RIPE65
by Vesna Manojlovic 21 Sep '12

21 Sep '12

[apologies for duplicates] Dear community, we are happy to invite you to the "Atlas Bash" at the RIPE65: Tuesday, 25 September, 18:00 – 19:00 (plenary room). This has just been added to the meeting agenda, in one of the BoF slots (Birds of Feathers): https://ripe65.ripe.net/programme/meeting-plan/birds-of-a-feather/ We would like to make this an interactive session, in order to bring RIPE Atlas UDM users and beta-testers together in one room with RIPE Atlas developers and the Measurements Community Builder to discuss developments, exchange ideas and best practices, suggest improvements, etc. This is also a great opportunity to learn more about the RIPE Atlas Anchors pilot project, how to get involved, to discuss host requirements, which features do you want, and more. We will be giving various presentations at many working groups, too, about the measurements results from RIPE Atlas, and plans for the future: MAT-wg, NCC-services-wg, plenary... Detailed information will follow next week, when all agendas are finalized. Hope to see you there! If you can not take part, there will be webcasts and jabber, and we will report back on these mailing lists. Regards, Vesna

1 1

Announcing RIPE Atlas Anchors, Pilot Phase
by Vesna Manojlovic 31 Aug '12

31 Aug '12

Dear Atlas community, Please find a new article on RIPE Labs describing the details of RIPE Atlas Anchors: https://labs.ripe.net/Members/dfk/ripe-atlas-anchors Right now, we are looking for a small number of pilot hosts from the RIPE NCC membership for deployment to begin in October 2012. If you are interested, please contact me or Daniel Karrenberg before the RIPE65. We will be discussing further details at the RIPE meeting. Regards, Vesna Manojlovic -- Vesna Manojlovic BECHA(a)ripe.net Senior Community Builder +31205354444 for Measurements Tools RIPE NCC http://ripe.net

1 0

Operational issue between ~14h-16h UTC
by Robert Kisteleki 29 Aug '12

29 Aug '12

Dear Atlas users, This afternoon our developers deployed an upgrade to the Atlas controlling infrastructure. Unfortunately, the update contained a bug that we did not catch in the test environment. This bug caused all probes to suspend their running UDMs (User Defined Measurements) between approximately 14h-16h (UTC, different probes were affected at different times). After noticing the error we reverted the changes, and resumed all UDMs. Because of this, your UDMs likely have missing data points for this time frame. Obviously, more frequent measurements will have more missing results while less frequent measurements will have less (or even nothing) missing results. "Built-in" measurements (i.e. non-UDMs) have not been affected. Based on this experience, we'll enhance our testing procedure to lower the chance of these kind of errors happening again. Excuses for the inconvenience this issue may have caused. Regards, Robert Kisteleki RIPE NCC

1 0