I like this system, but the biggest problem is that with my 4506 switch, it shows all interfaces on on all IP ranges in use.
Hi,
could you please describe problem in more details, or maybe show a screenshot?
Best regards,
Victor
Here is a screenshot, it shows multiple subnets and the switches are listed multiple times under different subnets.
The interfaces listed under each subnet under the same switch are the same interfaces even though they are not all in the vlans as access ports. In fact the 10.7 network listed is not configured on any ports, yet when I expand the switches tree it shows all of it's ports under the 10.7 network.
This makes no sense and is confusing.
Also I used the Installer for the webgui, but it is not working, even though the jetty webserver is running.
Really?
Hi,
can you share screenshot of "Interfaces" tab for the switch shown under 10.7 subnet?
Best regards,
Victor
If you look at my post before my Really? post, you will see I attached requested screenshot before you asked.
When you select switch object, on the right side of the screen you'll get object details view. There is "Interfaces" tab - this is what I was asking for.
Best regards,
Victor
ok, here is what you asked for with the latest version 2.0.4
Here is the switch config for the first port.
interface FastEthernet2/1
switchport access vlan 2
speed 100
duplex full
spanning-tree portfast
!
and vlan config
interface Vlan1
ip address 10.2.1.1 255.255.0.0
!
interface Vlan2
ip address 10.3.1.1 255.255.0.0
!
interface Vlan5
ip address 10.5.1.1 255.255.0.0
!
This port should not show up in the graph below as it' has access only to vlan 2 and no voice vlan defined, nor is it a tagged port allowing all vlans.
I never did see a reply to this?
The screenshot Victor asked for was for the "Interfaces" tab underneath the Object details. Something like the one attached.
Just to confirm your question:
- your switch is in multiple VLANs and networks
- your switch shows under every one of those networks underneath "Entire Network"
- when you expand the switch under any of those networks, it shows all interfaces, every time
- You are expecting that the switch will only list the interfaces which are actually a part of those networks
I guess the answer is that NetXMS does not treat interfaces under Entire Network like that. It only confirms if the node itself is in the network.
When you expand the node, it will list all child objects, e.g. interfaces. There is no filtering applied.
If the above is correct, I suggest submitting a feature request to filter interfaces listed on nodes under Entire Network to only show if the interfaces themselves are a part of the selected network.
Cheers,
Tursiops
Quote from: Tursiops on March 20, 2017, 10:54:42 PM
The screenshot Victor asked for was for the "Interfaces" tab underneath the Object details. Something like the one attached.
Just to confirm your question:
- your switch is in multiple VLANs and networks
- your switch shows under every one of those networks underneath "Entire Network"
- when you expand the switch under any of those networks, it shows all interfaces, every time
- You are expecting that the switch will only list the interfaces which are actually a part of those networks
I guess the answer is that NetXMS does not treat interfaces under Entire Network like that. It only confirms if the node itself is in the network.
When you expand the node, it will list all child objects, e.g. interfaces. There is no filtering applied.
If the above is correct, I suggest submitting a feature request to filter interfaces listed on nodes under Entire Network to only show if the interfaces themselves are a part of the selected network.
Cheers,
Tursiops
Yep that is exactly it with some additions/changes. I have a router in which the WAN Interface is the first one, and it shows in the WAN Network, and the rest of the interfaces which are not in the WAN network. And the same for the LAN Network. Also this is a bug, it is mis-representing what is actually there. I will attach the other screenshot in a moment.
I could not get this via the web interface. I had to use the console, is there a way to get it via the web interface, if not, i will request it as a feature.
I suggest submitting the original issue in the Bug Tracker (https://www.radensolutions.com/chiliproject/projects/netxms).
Not being a developer, I didn't call it a bug as it looks to me like the functionality you are looking for was never implemented (i.e. it's not broken, it's missing).
The "Interfaces" tab exists in the web interface on our installation (see attached screenshot; from a server with a single NIC) and can be reached in the same was as in the console. Not sure why it would not be visible in yours.
Quote from: Tursiops on March 28, 2017, 03:27:38 AM
I suggest submitting the original issue in the Bug Tracker (https://www.radensolutions.com/chiliproject/projects/netxms).
Not being a developer, I didn't call it a bug as it looks to me like the functionality you are looking for was never implemented (i.e. it's not broken, it's missing).
The "Interfaces" tab exists in the web interface on our installation (see attached screenshot; from a server with a single NIC) and can be reached in the same was as in the console. Not sure why it would not be visible in yours.
I am wondering myself. I used the latest downloads from the downloads for 64 bit windows.
Submitted
https://track.radensolutions.com/issue/NX-1229
Quote from: starkiller on April 25, 2017, 06:44:44 AM
Submitted
https://track.radensolutions.com/issue/NX-1229
What good does it do to submit this?
It has not gotten any traction that I can see.
Hi,
as I understood it is misconception, not a bug. When you walk object tree end expand object, you see ALL child objects. Interfaces are child objects of a node, so when you expand a node, you see all interfaces. It is irrelevant if you come to that node via subnet, or container, or template, etc. You always will see all objects below.
Best regards,
Victor
Quote from: Victor Kirhenshtein on August 03, 2017, 10:07:43 AM
Hi,
as I understood it is misconception, not a bug. When you walk object tree end expand object, you see ALL child objects. Interfaces are child objects of a node, so when you expand a node, you see all interfaces. It is irrelevant if you come to that node via subnet, or container, or template, etc. You always will see all objects below.
Best regards,
Victor
So your saying that it is irrelevant that the interface is not configured to have access to that vlan.
expanding the tree via vlan will show the interface since it could be configured to see that vlan, even though its not currently configured for that vlan.
So instead of showing facts, netxms is showing facts and possibilities.
Is there anything in the docs that state that netxms will show the vlan the interface is configured for as well as possible vlans the interface could be configured for?
No other network monitoring system does this that I am aware of.
OpenNMS, PandoraFMS, Zabbix to name a few open source free ones do not do this and neither do ones like Solarwinds or PRTG.
Victor this is very misleading as one expects a network monitoring system to show facts and not possibly configurations.
In any case I am just one user expressing and issue with the on part of the design of netxms which causes confusion compared to other NMS systems and hoping it would recognized as and issue and be fixed by the author.
Quote from: starkiller on August 04, 2017, 05:06:45 AM
In any case I am just one user expressing and issue with the on part of the design of netxms which causes confusion compared to other NMS systems and hoping it would recognized as and issue and be fixed by the author.
I just read through this entire thread.
Actually, you are one user that is fighting the system, instead of trying to understand how it works.
NetXMS make NO assumption, it does NOT show what could be. It shows what is.
You seem to completely misunderstand the concept that one node is one object, and it's linked to (it's bound) to many places around the system.
It's consistency.
The way you are proposing would be way too confusing to existing and new users.
One object, with the same Object ID would show different children (be that interfaces, or VPN connectors, or wireless interfaces, etc.) across different parts of the system.
I REALLY suggest trying to see how the system works and why it works that way instead of arguing why the way that works for thousands of NetXMS users is wrong.
You make 0 attempts to ask questions, to see why the system behaves how it does, or to understand NetXMS philosophy.
So you will have to accept my post doing the same.
Quote from: tomaskir on August 04, 2017, 11:32:21 AM
I just read through this entire thread.
Actually, you are one user that is fighting the system, instead of trying to understand how it works.
Everyone sees it differently.
Quote from: tomaskir on August 04, 2017, 11:32:21 AM
NetXMS make NO assumption, it does NOT show what could be. It shows what is.
You seem to completely misunderstand the concept that one node is one object, and it's linked to (it's bound) to many places around the system.
It's consistency.
I can only restate what the screenshots and config snippet show which is that the screen shots show interfaces as a child of a vlan/subnet that those interfaces are not part of and do not pass traffic for. The 2 objects should not be associated together as they have no association which should warrant such a graphical representation.
Quote from: tomaskir on August 04, 2017, 11:32:21 AM
The way you are proposing would be way too confusing to existing and new users.
One object, with the same Object ID would show different children (be that interfaces, or VPN connectors, or wireless interfaces, etc.) across different parts of the system.
I REALLY suggest trying to see how the system works and why it works that way instead of arguing why the way that works for thousands of NetXMS users is wrong.
I would hope that showing what is there vs showing what isn't there as being there is not confusing for users.
Interfaces are NOT descendants of a subnet - they are descendants of a node. Node can be in multiple subnets.
Best regards,
Victor
Quote from: Victor Kirhenshtein on August 11, 2017, 05:05:49 PM
Interfaces are NOT descendants of a subnet - they are descendants of a node. Node can be in multiple subnets.
Best regards,
Victor
I understand a node can be in multiple subnets. When you expand the subnet and it shows the interfaces of that node who are not configured for that subnet in that subnet is what I am referring to.
I have attached another screenshot. The Interfaces with the red circle around them are configured to be in the subnet with the red circle around them. The Interfaces with the Yellow Highlight are configured to be in the subnet with the yellow highlight.
The node is the ge0router, unless I am mistaken about what a node is.
I wanted to make it as clear as possible what I am describing.
Its a bug to me, but a work as designed to you Victor and a few others that use netxms.
I am fine with that as I am not using it in production because of this issue as I do not have time to explain why its visually misrepresented to those who have compared this to other systems out there. Thanks for taking the time to look at it Victor.