<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Maintenance Mode]]></title><description><![CDATA[<p dir="auto">I've seen this topic come up a few times: Could you please make a way to 'put a node into maintenance mode'? Scheduled would be super-awesome, but I'll gladly take manual. I really don't want this thing to wake me up at 3 in the morning when somebody is doing maintenance <img src="https://forum.netxms.org/assets/plugins/nodebb-plugin-emoji/emoji/android/1f642.png?v=72b86a538fc" class="not-responsive emoji emoji-android emoji--slightly_smiling_face" style="height:1.4em;width:auto;vertical-align:middle" title=":)" alt="🙂" /></p>
<p dir="auto">From browsing through the 1.1.7 source, it looks like you have quite a bit of it in place with the 'disabled' status for a node. Just suspend all polling while the node is in maintenance mode. No data collected. No events generated. Etc. Just a single event that the node has changed status (into maintenance mode) and one when it's come out of maintenance mode.</p>
<p dir="auto">Please? Pretty please?</p>
<p dir="auto">Peter</p>
]]></description><link>https://forum.netxms.org/topic/1516/maintenance-mode</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 13:21:16 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/1516.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 21 Dec 2011 05:14:55 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Maintenance Mode on Wed, 21 Dec 2011 16:12:47 GMT]]></title><description><![CDATA[<p dir="auto">The fact that it's hierarchical is actually great, I think. If the box gets put into maintenance mode, all its children should also be in maintenance mode anyway (unless they were unmanaged to begin with - they should!)</p>
<p dir="auto">The issue with using managed/unmanaged as a maintenance mode is that it indeed changes the way you had things setup. On our switches, I only have a few things that need managed. 90% of the interfaces is set to unmanaged. I'd have to redo that setup every time.</p>
<p dir="auto">If you can, have a look at how "What's Up Gold" does maintenance mode. Is really basic, but it works surprisingly well.<br />
<a href="http://docs.ipswitch.com/WhatsUp_Gold_v12.3/WebHelp/13689.png" rel="nofollow ugc">http://docs.ipswitch.com/WhatsUp_Gold_v12.3/WebHelp/13689.png</a></p>
]]></description><link>https://forum.netxms.org/post/6573</link><guid isPermaLink="true">https://forum.netxms.org/post/6573</guid><dc:creator><![CDATA[pzandvoort]]></dc:creator><pubDate>Wed, 21 Dec 2011 16:12:47 GMT</pubDate></item><item><title><![CDATA[Reply to Maintenance Mode on Wed, 21 Dec 2011 08:30:28 GMT]]></title><description><![CDATA[<p dir="auto">Hi!</p>
<p dir="auto">You can use unmanage/manage as a workaround for manual maintenance mode. System do nothing with unmanaged node. The only drawback is that unmanage operation is hierarchical, i.e. all interfaces and services of a node will change status as well, and when you do "manage" node again, they all come into "managed" state, even if some of them was unmanaged before.</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/6558</link><guid isPermaLink="true">https://forum.netxms.org/post/6558</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Wed, 21 Dec 2011 08:30:28 GMT</pubDate></item></channel></rss>