<?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[Unable to get Bandwidth details on Map]]></title><description><![CDATA[<p dir="auto">Hi</p>
<p dir="auto">having some trouble getting bandwidth values from some switches i.e. lan-sw1.<br />
 lan-sw2, lansw3, lan-sw6, lan-sw8 (SMC 6152L2), see attachment, am able to get the bandwidth details on lan-sw4 (Edge Core ECS2100-28T) as seen in the attachment, have no idea if any specific configs need to be done on SMC 6512L2, other SNMP details are working fine for the the switches.</p>
<p dir="auto">another issue is with regards to the attached triangular topology, we we shut the link from one node, the link color does not turn red, even though the alarms are generated, however for other node in some other map things work fine, i have tried deleting the map topology and recreating it, have configured the the link color based on object status and selected the right port,</p>
<p dir="auto">the above are the only glitches i am having to deploy the NMS,</p>
<p dir="auto">hope someone is able to help me on this soon, will chuck off Whatsup Gold once the above work issues are resolved. WUG is currently monitoring close to 1000 network nodes, and im not so keen on buying additional licences , love the way Netxms provide required info in point and click manner the search functions are great too.</p>
<p dir="auto">Regards</p>
<p dir="auto">Clifford</p>
<hr />
<p dir="auto"><img src="/assets/uploads/files/smf/0000000003732-map.jpg" alt="map.jpg" class="img-markdown  img-fluid" width="1680" height="1050" /></p>
<p dir="auto"><img src="/assets/uploads/files/smf/0000000003734-DCI_for_Edge_Core_Switches-_Working_fine.JPG" alt="DCI for Edge Core Switches- Working fine.JPG" class="img-markdown  img-fluid" width="970" height="281" /></p>
<p dir="auto"><img src="/assets/uploads/files/smf/0000000003736-DCI_for_SMC_6152L2_Switches-_No_valuse.JPG" alt="DCI for SMC 6152L2 Switches- No valuse.JPG" class="img-markdown  img-fluid" width="1006" height="279" /></p>
<p dir="auto"><img src="/assets/uploads/files/smf/0000000003738-Triangle_Topology.JPG" alt="Triangle Topology.JPG" class="img-markdown  img-fluid" width="564" height="435" /></p>
]]></description><link>https://forum.netxms.org/topic/5254/unable-to-get-bandwidth-details-on-map</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 21:03:57 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/5254.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 23 Sep 2017 10:51:34 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Unable to get Bandwidth details on Map on Wed, 17 Jan 2018 10:17:09 GMT]]></title><description><![CDATA[<p dir="auto">Hi, victor</p>
<p dir="auto">Will this be added in the future releases?</p>
<p dir="auto">Regards</p>
<p dir="auto">Clifford Dsouza</p>
]]></description><link>https://forum.netxms.org/post/23710</link><guid isPermaLink="true">https://forum.netxms.org/post/23710</guid><dc:creator><![CDATA[clifford]]></dc:creator><pubDate>Wed, 17 Jan 2018 10:17:09 GMT</pubDate></item><item><title><![CDATA[Reply to Unable to get Bandwidth details on Map on Tue, 10 Oct 2017 14:07:55 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">if topology correlation is working, device D should become red, and rest of devices and links blue. Blue in that case means "unknown" - because links and devices could be up actually, but because of failed link NMS cannot determine their status. We probably could add map option to color all unreachable devices and links in red - will discuss that internally.</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/23172</link><guid isPermaLink="true">https://forum.netxms.org/post/23172</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Tue, 10 Oct 2017 14:07:55 GMT</pubDate></item><item><title><![CDATA[Reply to Unable to get Bandwidth details on Map on Fri, 06 Oct 2017 11:47:44 GMT]]></title><description><![CDATA[<p dir="auto">Hi</p>
<p dir="auto">The data is wrong i did a graph capture of zabbix and netxms, netxms does not graph properly, screen shots attached. but then this issue is only with a SMC6152L2 Switch, the other switches are graphed ok.</p>
<p dir="auto">so maybe compatibility issues</p>
<p dir="auto">The Link status thing seems to have worked somehow.</p>
<p dir="auto">One last Question regarding link status and color.</p>
<p dir="auto">Please refer to the attachment Map link Color preference</p>
<p dir="auto">Regards<br />
Clifford<br />
 </p>
<hr />
<p dir="auto"><img src="/assets/uploads/files/smf/0000000003752-zabbix_graph.JPG" alt="zabbix graph.JPG" class="img-markdown  img-fluid" width="1673" height="787" /></p>
<p dir="auto"><img src="/assets/uploads/files/smf/0000000003754-NetXMS_Graph.png" alt="NetXMS Graph.png" class="img-markdown  img-fluid" width="1481" height="851" /></p>
<p dir="auto"><img src="/assets/uploads/files/smf/0000000003756-Map_Link_Color_preference.JPG" alt="Map Link Color preference.JPG" class="img-markdown  img-fluid" width="638" height="661" /></p>
]]></description><link>https://forum.netxms.org/post/23166</link><guid isPermaLink="true">https://forum.netxms.org/post/23166</guid><dc:creator><![CDATA[clifford]]></dc:creator><pubDate>Fri, 06 Oct 2017 11:47:44 GMT</pubDate></item><item><title><![CDATA[Reply to Unable to get Bandwidth details on Map on Wed, 04 Oct 2017 20:42:05 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">do you have wrong data collected or data is correct but not shown on the map?</p>
<p dir="auto">For link status - could you please share screenshot of link properties?</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/23149</link><guid isPermaLink="true">https://forum.netxms.org/post/23149</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Wed, 04 Oct 2017 20:42:05 GMT</pubDate></item></channel></rss>