NetXMS Support Forum

We have racks that have shelves of non-rackable equipment and we also have some half-U switches. It would be useful if the Rack visualisation could support multiple nodes to one rack position in some way, at least with the Status Indicators and hovertips.

It would also be useful if we could define our own passive element images.

In NXMC, once you Apply your changes to a Rack objects Passive Elements in the UI, you can no longer perform any changes until you close and reopen the Properties window for the Rack object.

This would be useful, I wonder if this workflow can tie into the Location feature too?

It would be useful for Rack objects to support Map Appearance features like Containers and Nodes do.

What does the Root cause analysis script in the Alarm section of an Event Process Policy rule do? I assume it's for identifying root cause of an alarm, obviously, but I can't find documentation on the feature (what script should return) and the workflow of the feature.

I know SMTP authentication and it's transport (SSL/STARTTLS) has been spoken about for a while (1, 2) but what's the current status of this feature? Will it be implemented as another Notification Channel if at all?

It would be useful to be able to define a separate name for use in maps. We have an issue where we have to choose between descriptive node names, have large icons or use shorter names as the node name on a map is truncated based on the size of it's icon.

Thanks, any ideas on what they might be used for in the future or if Layer 2 Topology discovery might influence this feature?

I'm looking to evaluate the Agent Tunnels feature but I wanted to learn more about how it works.

• Will there be support in the future to configure TLS protocol and cipher suites etc. for hardening?
• I'm assuming it's utilising Mutual TLS for server and client authentication?
• How are the agent certificates generated? Are they self-signed then registered with NetXMS server? Is a CSR generated on agent, sent to NetXMS, signed by NetXMS (How?) and then signed certificate returned? If the latter, how is the NetXMS CA managed?
• How is NetXMS server certificate validated (on initial connection and subsequent ones) by agents? I'm assuming agent needs to trust the Issuing CA of the NetXMS server certificate? Does it use the platforms relevant certificate store or a Java certificate store or just a file?

I'm curious too.

That's what we have done but it's tedious and having a proper installer is superior in every way.

I'm experimenting with logwatch parser configurations for Windows Event Logs, specifically with our ADFS farm:
<parser>
    <file>*AD FS/Admin</file>
    <macros>
    </macros>
    <rules>
<rule>
<match>.+?Error message: [ \r\n]+(.+?)-(.+) .+</match>
            <id>342</id>
<event param="2">100123</event>
        </rule>
    </rules>
</parser>

But it appears I'm blowing up EvtRender call, message too big?
2020.05.25 15:55:17.555 *I* [                   ] NetXMS Agent started
2020.05.25 15:55:24.773 *D* [                   ] PostEvent(): event_code=100123, event_name=(null), timestamp=1590386123, num_args=10, arg[0]="[email protected]", arg[1]="The", arg[2]="AD FS", arg[3]="342", arg[4]="1", arg[5]="11902", arg[6]="1", arg[7]="http://schemas.microsoft.com/ws/2006/05/identitymodel/tokens/UserName", arg[8]="[email protected] user name or password is incorrect", arg[9]="System.IdentityModel.Tokens.SecurityTokenValidationException: [email protected] ---> System.ComponentModel.Win32Exception: The user name or password is incorrect

   at Microsoft.IdentityServer.Tokens.LsaLogonUserHelper.GetLsaLogonUserHandle(SafeHGlobalHandle pLogonInfo, Int32 logonInfoSize, SafeCloseHandle& tokenHandle, SafeLsaReturnBufferHandle& profileHandle)

   at Microsoft.IdentityServer.Tokens.LsaLogonUserHelper.GetLsaLogonUserInfo(SafeHGlobalHandle pLogonInfo, Int32 logonInfoSize, DateTime& nextPasswordChange, DateTime& lastPasswordChange, String authenticationType, String issuerName)

   at Microsoft.IdentityServer.Tokens.LsaLogonUserHelper.GetLsaLogonUser(String domain, String username, String password, DateTime& nextPasswordChange, DateTime& lastPasswordChange, String issuerName)

   at Microsoft.IdentityServer.Service.LocalAccountStores.ActiveDirectory.ActiveDirectoryCpTrustStore.ValidateUser(IAuthenticationContext context)

   --- End of inner exception stack trace ---

   at Microsoft.IdentityServer.Service.LocalAccountStores.ActiveDirectory.ActiveDirectoryCpTrustStore.ValidateUser(IAuthenticationContext context)

   at Microsoft.IdentityServer.Service.Tokens.MsisLocalCpUserNameSecurityTokenHandler.ValidateTokenInternal(UsernameAuthenticationContext usernameAuthenticationContext, SecurityToken token)

   at Microsoft.IdentityServer.Service.Tokens.MsisLocalCpUserNameSecurityTokenHandler.ValidateToken(SecurityToken token)



System.ComponentModel.Win32Exception (0x80004005): The user name or password is incorrect

   at Microsoft.IdentityServer.Tokens.LsaLogonUserHelper.GetLsaLogonUserHandle(SafeHGlobalHandle pLogonInfo, Int32 logonInfoSize, SafeCloseHandle& tokenHandle, SafeLsaReturnBufferHandle& profileHandle)

   at Microsoft.IdentityServer.Tokens.LsaLogonUserHelper.GetLsaLogonUserInfo(SafeHGlobalHandle pLogonInfo, Int32 logonInfoSize, DateTime& nextPasswordChange, DateTime& lastPasswordChange, String authenticationType, String issuerName)

   at Microsoft.IdentityServer.Tokens.LsaLogonUserHelper.GetLsaLogonUser(String domain, String username, String password, DateTime& nextPasswordChange, DateTime& lastPasswordChange, String issuerName)

   at Microsoft.IdentityServer.Service.LocalAccountStores.ActiveDirectory.ActiveDirectoryCpTrustStore.ValidateUser(IAuthenticationContext context)"
2020.05.25 15:55:24.773 *D* [logwatch           ] ExtractVariables: Call to EvtRender failed: The data area passed to a system call is too small.


Found the problem, if you have all the interfaces as 'ignore' then it will cause this situation, I expected the node to just rely on the Use ICMP on primary IP address to determine node status setting.

We have a number of offline nodes that show their status as normal, despite being completely offline. There is no DCI for Status, it's just a node with ICMP and SNMP enabled and has children interfaces generated by an old SNMP Configuration Poll.

What could be causing this?

Seeing as the NXMC option has been removed from the only Windows NetXMS install package available (the server one), can we please have a dedicated NXMC Windows install? Preferably MSI?
At the very least, can you please out put the file version metadata information on the nxmc.exe binary so those of us who use deployment tools to install and keep software up to date and write proper and correct rules. With just the ZIP file, it's a real pain to deploy NXMC.