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 - StanHubble

#16
General Support / Update from 2.2.12 to 2.2.14
May 14, 2019, 08:20:17 AM
Took about 1/2 hour in total (running nxdbmgr check before and after manual schema update).
MSSQL database is about 68GB.
All i can say is ........
.........WOW
It flies now....and no timeouts!!!!!

netxmsd: sho stats
Objects............ 78972
Monitored nodes.... 12782
Collectible DCIs... 243070
Active alarms...... 99052


Now I can start to clear out some of the active alarms.

A huge thank you  to all the people at Radensolutions for a great and evolving product.


:) :) :) :)


#17
Feature Requests / Table/List Counts
May 10, 2019, 11:01:03 PM
NXMC:Various Perspectives,


It would be nice to have row counts on any/all of the table/list displays.

I know i can write scripts to count them and that works for some things, but summary tables add a different dimension to things and some/all/me of my users have trouble finding things on the right-click context menus.

thanks,
Stan
#18
Feature Requests / Container Counts
May 10, 2019, 10:04:54 PM
Nxmc: Object Details(of a container): General Dialog of Overview.

Would it be possible to display total non-recursive child object counts.

Because it is sometimes hard to tell the difference between 273 and 327 nodes or objects in a container.

thx
Stan
#19
What OS is your server on?
#20
You will need to expose your netxms server port 470x to those "RDP accessable nodes" or at least one to act as a proxy on each of the remote networks.  Then setup a certificate on the server and add a "serverconnection=<Externalipofyournetxmsserver>" line in the agent configuration file of the proxy node on the remote network.  Optionally (but recommended) you can enable zones on your server and assign each remote proxy as the proxy agent for each zone you define.  That's the condensed version of remote connections, there are a number of posts here on the forums that describe each of the steps.

Have fun and ask questions..
stan
#21
Thanks alot Victor!!
it worked without a hitch.

PS C:\ProgramData\NetXMS\bin> .\nxdbmgr.exe upgrade
NetXMS Database Manager Version 2.2.12 Build 9516 (2.2.12-2-gf93e98c349) (UNICODE)

Upgrading database...
Upgrading from version 22.40 to 22.41
Upgrading from version 22.41 to 22.42
Database upgrade succeeded
PS C:\ProgramData\NetXMS\bin> .\nxdbmgr.exe check
NetXMS Database Manager Version 2.2.12 Build 9516 (2.2.12-2-gf93e98c349) (UNICODE)

Checking database (excluding collected data):
* Zone object properties                                               [PASSED]
* Node object properties                                               [PASSED]
* Node to subnet bindings                                              [PASSED]
* Interface object properties                                          [PASSED]
* Interface bindings                                                   [PASSED]
* Network service object properties                                    [PASSED]
* Network service bindings                                             [PASSED]
* Cluster object properties                                            [PASSED]
* Cluster member nodes                                                 [PASSED]
* Template to node mapping                                             [PASSED]
* Object properties                                                    [PASSED]
* Container membership                                                 [PASSED]
* Event processing policy                                              [PASSED]
* Network map links                                                    [PASSED]
* Data tables                                                          [PASSED]
* Raw DCI values table                                                 [PASSED]
* DCI thresholds                                                       [PASSED]
* Table DCI thresholds                                                 [PASSED]
Database doesn't contain any errors
Database check completed
#22
NetXMS Database Manager Version 2.2.12 Build 9516 (2.2.12) (UNICODE)

Upgrading database...
Upgrading from version 22.41 to 22.42
SQL query failed ([Microsoft][SQL Server Native Client 10.0][SQL Server]Cannot define PRIMARY KEY constraint on nullable
column in table 'address_lists'.):
ALTER TABLE address_lists ADD CONSTRAINT pk_address_lists PRIMARY KEY (list_type,community_id,zone_uin,addr_type,addr1,addr2)
Rolling back last stage due to upgrade errors...
Database upgrade failed


I started from 2.2.10 and got this error on a direct upgrade to 2.2.12 so i reverted back to 2.2.10,
did a ".\nxdbmgr check" --> clean.
upgraded to 2.2.11
then another ".\nxdbmgr check" --> clean.
and tried another upgrade to 2.2.12 with the same error.

The first run through i let the windows installer update the schema but things ended up in the same conditions. subsequent tries I deselected the update schema option, but nxdbmgr upgrade fails with the same condition.

at this point i have reverted back to 2.2.10 , any ideas?

server -> win2012r2
dbserver -> win2012r2 with
Microsoft SQL Server Management Studio      12.0.5207.0
Microsoft Analysis Services Client Tools      12.0.5207.0
Microsoft Data Access Components (MDAC)      6.3.9600.17415
Microsoft MSXML                  3.0 6.0
Microsoft Internet Explorer               9.11.9600.19236
Microsoft .NET Framework               4.0.30319.42000
Operating System                  6.3.9600
#23
General Support / Re: error installing agent on Centos 7
September 11, 2018, 08:08:15 PM
you probably want:
yum install libcurl-devel
#24
General Support / Re: Monitoring Remote Networks
August 22, 2018, 10:45:13 PM
Are you able to put an agent on a server at the remote sites? (or any device that will take an agent and not be turned off).
If you can, then set up agent tunnels to your netxms server (you will have to open a port forward on your local edge device to your netxms server).  You will need to configure a certificate on you netxms server to get these phonehome tunnels working.  Once those tunnels are available you can then set the node that the agent is bound to in a given zone. Set it as the proxy in that zones' communications settings.  This sets all communications for any device  in that zone to go through that node.

I have about 450 zones set up this way with over 10000 nodes (mostly auto discovered).  Now most of these nodes I don't care about, other than that they are there. (ie what is plugged into what port on a managed switch).  I initially tried it with forwarded ports at the remote locations but that proved to be generally unworkable with dynamic isp connections and edge routers that we did not have access to.

Good Luck with your setup.
stan
#25
General Support / Re: Discovery of MAC addresses
August 08, 2018, 09:52:02 PM
We have been seeing this as well, and i finally had time to dig into it.  It seems that in our case any nodes discovered without an agent (netxms or snmp) since mid may do not have a mac address associated with them on the "unknown" interface.  This coincides to when i installed 2.2.5 on the server.  The ip of the node is definitely in the arp cache of a router that is in the same "zone" and shows up in a 'show arp <nodeidofrouter>' in nxadm.  The proxy agent versions are a mixture of 2.2.6 and 2.2.7 windows and linux, and it happens in all cases.

thx
stan

#26
General Support / Re: Errors Starting 2.2.7
July 27, 2018, 04:32:16 PM
Thanks for the help.  It has been 24 hrs now since I installed 2.2.7.17 and everything is seems to be running fine.

Start up was longer than it used to be, but I can live with that.
I still have a number of errors on some Template and Container Autobind scripts during startup that behave normally when the system is up and running.  These are complaining about null values on variables that are populated either from a GETDCIVALUEBYDESCRIPTION function or a custom attribute of the node being tested. 

Now with 2.2.7 recognizing Node types of "Virtual" I can change some of these autobind scripts key on this instead, but there is a problem.  The config poll is correctly identifying actual virtual machines (if they have an agent) both on VMware and Hyper-V.  But it is also identifying Hyper-V Host machines as virtual (both 2.2.6 and 2.2.7 agents).
I don't have visibility on any VMware hosts machines to say if it is the case with them as well.



Thanks again
Stan
#27
General Support / Re: Errors Starting 2.2.7
July 25, 2018, 08:47:39 PM
yes please.
#28
General Support / Re: Errors Starting 2.2.7
July 25, 2018, 12:00:03 AM
Yeah ! was too optimistic.....it died after about 12 hours and wont restart.
I have checked the DCI's throwing errors and they were complaining about null values.  They were all dependent dci's that used a GETDCIVALUEBYDESCRIPTiON function in the transformation script.




#29
General Support / Re: Errors Starting 2.2.7
July 24, 2018, 06:07:57 AM
I hate #$%@#$  windows.......
removed and reapplied the latest set of windows updates  and 10 reboots later
, re-allow netxms thru windows firewall rules (even though it is disabled) and held my left foot while drinking a beer
and like magic netxmsd starts properly.

I think it was the beer that did it.
#30
General Support / Re: Errors Starting 2.2.7
July 23, 2018, 02:07:02 PM
The show watchdog displays the dashes and then hangs, (Ctrl-C) will drop you back to command line.
I can restart nxadm after and do a show queue or show thread, but sho stat, sho watchdog, or show tunnel will hang.

I created the process dump but it is almost 10GB.  Zipped it is 500MB.  Will this forum accept an upload that big?