NetXMS Support Forum

Hi Victor,

Should I take additional data, are you working this issue or should I escalate to MRV

Kind regards,
Henk

As an afterthought ... earlier this evening I also tried to retrieve the interface list from the commandline using nxsnmpwalk ... that worked!

Sure no problem ...Nope, same problem. After the poll the version is reset to 2c, I presume NetXMS detects the switch is using version 2c.

What OID is used by NetXMS to obtain the configuration/interface list?

I can then also go back to MRV and ask if they have a clue on whats going on. For your information, we are also utilizing the bigger 10G core switches of MRV (the ones giving me a headache are small CPE's) that do not complain and nicely return their interface list to NetXMS.

Perhaps I should take a trace of them as well so that we are able to compare?

Regards,
Henk

I executed the command again, this time I supplied the community string  Following the resulting reply:

.1.3.6.1.2.1.4.20.1.1.10.10.2.22 [40]: 10.10.2.22
.1.3.6.1.2.1.4.20.1.2.10.10.2.22 [02]: 4093
.1.3.6.1.2.1.4.20.1.3.10.10.2.22 [40]: 255.255.255.0
.1.3.6.1.2.1.4.20.1.4.10.10.2.22 [02]: 1
.1.3.6.1.2.1.4.20.1.5.10.10.2.22 [02]: 0

When run from the command prompt it times out. When I run it from within NetXMS it returns the management interface which, according to the mib browser seems to be the correct item to return. I have included the snmp walk from with NetXms and the MibBrowser as screenshot.

Since some time I am unable to poll the configuration of MRV switches, NetXMS reports "Unable to get interface list from node". since the network is fairly static the last few months I encountered this problem a fortnight ago. My gut feeling says this problem occurs resulting from applying security updates to the Windows OS but I am not entirely sure about that. What I do know is that Poll Configuration always functioned normally untill recently. Since I encountered this problem I have updated NetXMS to the latest version ( 1.00 rc2) but this did not resolve the problem.

I tried the suggestion mentioned under the same topic (1-2 years old topic) and used GetIF to see if the problem resides in the switch or if NetXMS is causing this problem. GetIF worked without a hitch and does return the interface list. I then took a Wireshark trace and interestingly enough I see the information flowing by but somehow NetXMS is still thinking it does noet receive the interface list. I have attached wireshark traces of both NetXMS and GetIF.

Any suggestions what might be causing this problem and is there a way to create the interfaces manually?

Kind regards,
Henk Hoven

I took the effort to investigate it a little further and took Wireshark traces of both NetXMS and GetiF. The OIDs that both NetXMS and GetiF utilizes are the same, the difference is that GetiF requests a whole bunch of parameters while NetXMS only requests the object name. Why an error is reported by NetXMS is puzzling me because snmp wise everything looks OK.

I have both traces attached.

Hi, I am experiencing exactly the same fenomenum, GetiF does return the interface list but NetXMS reports "unable to get interface list"

Sure can, attached screenshot from ONT1 created as a node with ip address 0.0.0.0

The OID field is grayed out and inaccessible, could this be caused by using 0.0.0.0 as the IP address?
Again many thanks for the timely response and eagerly awaiting the fix/next update.

Regards,
Henk

Hello,

I just upgraded NetXMS from version 2.26 to 2.27 and was hoping that I could now monitor our ONT's. I followed your suggestions but am still unable to monitor the ONTs. I can not enable data collection and whats more, I cannot specify a SNMP OID. The OID is necessary as the information regarding the ONTs is stored in the private part of the MIB.

Hopefully you have a workaround available, suggestions are more than welcome.

Kind regards,

Henk Hoven

Quote from: Victor Kirhenshtein on June 21, 2009, 04:56:03 PM
Hello!

It's almost possible - all required components are in place, I just need to fix few bugs. You can create nodes without IP addresses (by entering address 0.0.0.0  in node creation dialog). You can create "proxied" DCIs - i.e. you can define SNMP DCI on node without IP address and specify that real SNMP request will go to some different node. The only problem is that due to a bug in status poller nodes without IP address considered as "unreachable", which disables data collection for them. I'll fix that till next release.

Best regards,
Victor

Hello Victor,

You really know how to make a guy happy  I'll be looking forward to the next update, sorry for my late response but we had a major problem with our voip services that caused me to completely forget about the question I raised on this forum

Hi,

I am wondering if I can utilize NetXMS more efficiently in a GPON environment, In GPON CPE's are represented by what are called ONTs, the ONTs do not have a management IP address, instead they are managed from the central system (OLT). The central OLT system is recognized properly by NetXMS and readilly accessible using SNMP. What I am looking for is a way to manually create the ONTs and collect traffic and status information by accessing the central unit usng SNMP. To summarize, I am searching for a way to create an object (without an ip address) that collects its status and traffic information by referring to an SNMP oid stored in the central unit by reffering to the central units IP address and using SNMP to retrieve the stored information.

Is this at all possible?

Kind regards,

Henk Hoven