<?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[switch port search for down node]]></title><description><![CDATA[<p dir="auto">Hello</p>
<p dir="auto">Maybe a dumb question, but havent found easy solution yet. Lets imagine 200 ip cameras or other kind of devices connected to 10 x 24 port swithes. When a node or multiple nodes go down, what would be the easiest way to find out to what port they belong to? at the beginning switch will remember the device, but after some times it will forget it and netxms will show blank interface.</p>
<p dir="auto">Some ideas:<br />
* dig throught logs to see what port went down (not very usefull when 20 devices go down roughtly at same time.)<br />
* add interface descriptions to switch ports (but what if the ports are moved around and forgot to change description)</p>
<p dir="auto">Any button like: "find switch port" last seen port or somthing ? <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>
]]></description><link>https://forum.netxms.org/topic/6074/switch-port-search-for-down-node</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 12:15:23 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/6074.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 01 Aug 2019 18:26:41 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to switch port search for down node on Fri, 09 Aug 2019 07:03:29 GMT]]></title><description><![CDATA[<p dir="auto">Yes, it is there for some time already: <a href="https://track.radensolutions.com/issue/NX-593" rel="nofollow ugc">https://track.radensolutions.com/issue/NX-593</a>.</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/26248</link><guid isPermaLink="true">https://forum.netxms.org/post/26248</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Fri, 09 Aug 2019 07:03:29 GMT</pubDate></item><item><title><![CDATA[Reply to switch port search for down node on Sun, 04 Aug 2019 04:06:02 GMT]]></title><description><![CDATA[<p dir="auto">Not to hijack, but I like the idea of a connection history feature a lot, is there an issue number I can vote on at all?</p>
]]></description><link>https://forum.netxms.org/post/26229</link><guid isPermaLink="true">https://forum.netxms.org/post/26229</guid><dc:creator><![CDATA[normalcy]]></dc:creator><pubDate>Sun, 04 Aug 2019 04:06:02 GMT</pubDate></item><item><title><![CDATA[Reply to switch port search for down node on Fri, 02 Aug 2019 09:46:02 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">one possible workaround is to use hook script on topology poll to collect information about devices connected to the switch and update custom attribute or comment on those devices. We also have request for adding "connection history" functionality to NetXMS so probably after some time system will keep track of ports used for device connection automatically.</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/26221</link><guid isPermaLink="true">https://forum.netxms.org/post/26221</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Fri, 02 Aug 2019 09:46:02 GMT</pubDate></item></channel></rss>