News:

We really need your input in this questionnaire

Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Dani@M3T

#166
Announcements / Re: NetXMS 2.0-RC1 released
August 18, 2015, 12:12:25 PM
Thanks for the new release.
We just updated this morning from V2.0-M5 to V2.0-RC1 on Linux x64 from sources.
After the update, all custom Images in Image Library are lost. They all have a 'broken image' icon (of course also in all maps). The image files are still existing in the 'image' folder on the server. There must be a problem with the references. How can this be fixed?
#167
Hi Victor

Have you implemented this in V2.0-RC1? I just updated but cannot see any change.

thanks
Dani

#168
thanks!!!!
#169
Hi Victor

Thanks for the explanations. I started a feature request at the manufacturer of these devices (access points), but that can take very long.
It would be good to add a fallback by system name. Normally NetXMS will find node by ID and only if not the name would be second chance. Can you implement this for V2.0-RC1?

thanks
Dani
#170
Hi Victor

switch1 SNMP walk on OID .1.0.8802.1.1.2.1.4.1.1:
.1.0.8802.1.1.2.1.4.1.1.4.0.50.1 [INTEGER] = 4
.1.0.8802.1.1.2.1.4.1.1.4.0.57.2 [INTEGER] = 4
.1.0.8802.1.1.2.1.4.1.1.4.0.58.3 [INTEGER] = 4
.1.0.8802.1.1.2.1.4.1.1.5.0.50.1 [Hex-STRING] = FC AA AA AA 7C 08
.1.0.8802.1.1.2.1.4.1.1.5.0.57.2 [STRING] = °²Üo/4
.1.0.8802.1.1.2.1.4.1.1.5.0.58.3 [Hex-STRING] = 10 AA AA AA CA 4E
.1.0.8802.1.1.2.1.4.1.1.6.0.50.1 [INTEGER] = 7
.1.0.8802.1.1.2.1.4.1.1.6.0.57.2 [INTEGER] = 7
.1.0.8802.1.1.2.1.4.1.1.6.0.58.3 [INTEGER] = 7
.1.0.8802.1.1.2.1.4.1.1.7.0.50.1 [STRING] = 8
.1.0.8802.1.1.2.1.4.1.1.7.0.57.2 [STRING] = 1
.1.0.8802.1.1.2.1.4.1.1.7.0.58.3 [STRING] = 3
.1.0.8802.1.1.2.1.4.1.1.8.0.50.1 [STRING] = Uplink
.1.0.8802.1.1.2.1.4.1.1.8.0.57.2 [STRING] = lan
.1.0.8802.1.1.2.1.4.1.1.8.0.58.3 [STRING] = lan1
.1.0.8802.1.1.2.1.4.1.1.9.0.50.1 [STRING] = switch2
.1.0.8802.1.1.2.1.4.1.1.9.0.57.2 [STRING] = ap1.domain.com
.1.0.8802.1.1.2.1.4.1.1.9.0.58.3 [STRING] = gw1.domain.com
.1.0.8802.1.1.2.1.4.1.1.10.0.50.1 [STRING] = Switch2-Type
.1.0.8802.1.1.2.1.4.1.1.10.0.57.2 [STRING] = Linux
.1.0.8802.1.1.2.1.4.1.1.10.0.58.3 [STRING] = Gateway-Type
.1.0.8802.1.1.2.1.4.1.1.11.0.50.1 [STRING] = 
.1.0.8802.1.1.2.1.4.1.1.11.0.57.2 [STRING] = 8
.1.0.8802.1.1.2.1.4.1.1.11.0.58.3 [STRING] = 8
.1.0.8802.1.1.2.1.4.1.1.12.0.50.1 [STRING] = 
.1.0.8802.1.1.2.1.4.1.1.12.0.57.2 [STRING] = 8
.1.0.8802.1.1.2.1.4.1.1.12.0.58.3 [Hex-STRING] = 08 00


ap1 SNMP walk on OID .1.0.8802.1.1.2.1.3:
nothing. This device maybe does not support this OIDs for LLDP.

kind regards
Dani
#171
We have the following situation on a Cisco Switch ('switch1', LLDP enabled):

switch1 Port1:
Connected to a second switch ('switch2') by a VLAN trunk port.
In Object Details of switch1 I can see on interface tab for Port1 peer node 'switch2.domain.com', peer discovery protocol is LLDP.
In Tools - Info - Topology Table (LLDP) on switch1 I can see as system name of the peer 'switch2'.
So everything is fine here

switch1 Port2:
Connected to an WLAN AP ('ap1') by a VLAN trunk port.
In Object Details of switch1 I can see no peer node on interface tab for Port2.
In Tools - Info - Topology Table (LLDP) on switch1 I can see as system name of the peer 'ap1.domain.com'.
Is it possible that NetXMS cannot recognition the peer if it sends FQDN instead of pure hostname?
What is the standard for LLDP system name?
#172
General Support / Re: Object Filter in Layer3-Maps
July 09, 2015, 02:55:12 PM
All my subnets has names like '10.1.17.0/24 (SiteA)' and all Containers are named like 'SiteA'. So I can filter like this:
// only Subnets with 'SiteA' oder 'SiteB' in name
if (($object->type == 1) && (($object->name ~= ".*(SiteA.*)") || ($object->name ~= ".*(SiteB.*)")))
   return true;


Now the filtered map looks ok! But...

...only one new problem. Cluster nodes:
I tried to make an extention of the filtering script to handle clusters. But I found with a test script that cluster nodes has no node parents.

parents = GetObjectParents($object);
foreach(p : parents)
   println("Type: " . p->type . " Name: " . p->name);

Is this by design? With 'GetObjectParents' function I get neither the cluster-object nor the container as parent object. So all clusters nodes are missing on filtered maps.
#173
Announcements / Re: NetXMS 2.0-M5 released
July 09, 2015, 12:02:04 PM
I see this errors in all Agent logs (V2.0-M5, Windows and Linux):
[08-Jul-2015 16:00:04.115] [ERROR] DB Library: Unable to load database driver module "sqlite.ddr": The specified module could not be found.
[08-Jul-2015 16:00:04.115] [ERROR] Unable to open local database


It's not the same as the missing-'sqlite.ddr' issue. The 'sqlite.ddr' is existing in 'bin'-directory. In debug-log are no more information on that and I can't see any faulting functions yet.
#174
General Support / Re: Object Filter in Layer3-Maps
July 08, 2015, 10:51:35 PM
Hi Victor

When I add the subnets to the containers, I got the connectors in Layer3 map. But that's not very elegant. The other solution seems to be better.
How can I change my filter to allow the necessary subnet objects?

My current filter script is this:
parents = GetObjectParents($object);
//if (parents == null) return false;
foreach(p : parents)
{
   if ((p->type == 5) && (p->name == "containerA" || p->name == "ContainerB")) return true;
}
return false;
#175
General Support / Re: Object Filter in Layer3-Maps
July 08, 2015, 05:34:34 PM
Default connection options are on default color. I also tried with manually set to black. VPN-connectors (dotted) and the 'normal' connectors always have the same color. The last printscreen was without automatic layout. Here is one with automatic layout. Here I can't see any arrangement. Everything is mixed up.
#176
General Support / Re: Object Filter in Layer3-Maps
July 08, 2015, 05:03:08 PM
ok, thanks for the explanation.

But do you have any idea why all connectors are missing on the filtered layer3 map?
#177
General Support / Re: Object Filter in Layer3-Maps
July 08, 2015, 04:55:27 PM
Hi Victor

I tried manually and automatic layout. At the moment it's automatic layout. On this map are routers, switches and end nodes.

Can you please also explain for short the trusted nodes in this situation (not in general).

thanks
Dani
#178
The list in the Parameter Selection should be updated too:

  • The configuration and the status poller parameters should be deleted
  • The 3 new thread pool parameters should be added
#179
General Support / Re: Object Filter in Layer3-Maps
July 08, 2015, 01:54:46 PM
Thanks Tomas for your help.

Now I hope Victor will see this thread soon.

Dani
#180
General Support / Re: Object Filter in Layer3-Maps
July 08, 2015, 01:13:25 PM
Yes maybe Victor can give an answer.

I only see one VPN connector but no other 'normal' connectors. See the attached printscreen. Strange. All nodes on the left side should be connected to one of the VPN endpoints and the two on the right side with the other. In the map without the filtering script all connectors are there