RE: Problem with discovery

Hello!

As I can see from agent's config, your NetXMS server is not directly
connected to subnet in question (10.9.6.0/24). If it is true, does it
knows at least one managed server or device which is connected to that
subnet? I recommend you to manually add to NetXMS a router which
connects subnet 10.9.6.0, then NetXMS server will be able to discover
the rest of a subnet.

Tomorrow I'll try to explain in details how network discovery works, I
hope this will help you. Also, in the next release I can implement
active discovery mechanism - i.e. you specify an address range or a
subnet and NetXMS server will periodically check by ping and SNMP every
address in it. Looks like it may be more useful in your situation then
passive discovery mechanism.

Best regards,
Victor

> -----Original Message-----
> From: TIM MOORE [mailto:MOORET10_at_odjfs.state.oh.us]
> Sent: Friday, 29 September, 2006 20:30
> To: NetXMS Users
> Subject: [netxms-users] Problem with discovery
>
>
>
> I am still trying to get discover working. I just want to get some
> feedback to see what I'm missing.
>
> 1) I configured the Server Configuration to enable RunNetworkDiscover
> (it is set to 1). Also, I put the community string that we use in the
> config.
> 2) I set the Discover Filter field to 'Subnet'
> 3) I have a filter that Victor wrote for me that is called
> Filter::Subnet and looks like this:
> sub main()
> {
> return AddrInSubnet($1->ipAddr,"10.9.6.0","255.255.255.0");
> }
>
> 4) I have a linux server running the netxms agent. I have it modeled
> on the main server and can even view the agent's config, which I will
> post below.
>
> 5) I tried restarting the Netxms server but it never seems to start
> polling the 10.9.6.0 subnet.
>
> What am I not doing?
>
> agent config below (it is very generic and just has IP of
> netxms server
> in it)
>
> #
> # Sample configuration file for NetXMS agent
> #
>
> #
> # Servers
> #
> # List of management servers which have read access to this agent.
> # Both IP addresses and DNS names can be used. Multiple servers can be
> # specified in one line, separated by commas. If this parameter used
> more
> # than once, servers listed in all occurences will have access to
> agent.
> #
> # Examples:
> Servers = 10.3.8.44
> # Servers = 127.0.0.1, srv1.domain.com, srv2.domain.com
>
> #
> # ControlServers
> #
> # List of management servers which can execute actions on agent and
> change
> # agent's config. Hosts listed in this parameter also have read access
> to
> # the agent. Both IP addresses and DNS names can be used. Multiple
> servers
> # can be specified in one line, separated by commas. If this parameter
> used
> # more than once, servers listed in all occurences will have access to
> agent.
> #
> # Examples:
> ControlServers = 10.3.8.44
> # ControlServers = 127.0.0.1, srv1.domain.com, srv2.domain.com
>
> #
> # MasterServers
> #
> # List of management servers which have full access to agent. Hostss
> listed
> # in this group can upload files to agent and initiate agent upgrade,
> as well
> # as perform any task allowed for hosts listed in Servers and
> ControlServers.
> # Both IP addresses and DNS names can be used. Multiple servers can be
> # specified in one line, separated by commas. If this parameter used
> more
> # than once, servers listed in all occurences will have access to
> agent.
> #
> # Examples:
> MasterServers = 10.3.8.44
> # MasterServers = 127.0.0.1, srv1.domain.com, srv2.domain.com
>
> #
> # LogFile
> #
> # Agent's log file. To write log to syslog (or Event Log on Windows),
> # use {syslog} as file name.
> #
> # Examples:
> LogFile = {syslog}
> LogFile = /var/log/nxagentd.log
>
> #
> # RequireAuthentication
> #
> # If set to "yes", host connected to agent have to provide correct
> shared
> # secret before issuing any command. Default value is "no".
> #
> # Example:
> # RequireAuthentication = no
>
> #
> # RequireEncryption
> #
> # If set to "yes", host connected to agent will be forced to use
> encryption,
> # and if encryption is not supported by remote host,
> connection will be
>
> # dropped. Default value is "no". This parameter has no effect if
> agent
> # was compiled without encryption support.
> #
> # Example:
> # RequireEncryption = no
>
> #
> # EnabledCiphers
> #
> # Control what ciphers agent can use for connection encryption. Value
> for
> # this parameter is a cipher code. To enable more than one cipher,
> they
> # codes should be added. By default, all possible ciphers are enabled.
> #
> # Possible cipher codes:
> # 1 = AES-256
> # 2 = BLOWFISH
> # 4 = IDEA
> # 8 = Triple DES
> #
> # Example (enable AES-256 and IDEA):
> # EnabledCiphers = 5
>
> #
> # SharedSecret
> #
> # Agent's shared secret. Used only if RequireAuthentication set to
> "yes".
> #
> # Example:
> # SharedSecret = secret
>
> #
> # MaxSessions
> #
> # Maximum number of simultaneous communication sessions.
> Possible value
> can
> # be in range from 2 to 1024. Default value is 32.
> #
> # Example:
> # MaxSessions = 32
>
> #
> # SessionIdleTimeout
> #
> # Communication session's idle timeout in seconds. If agent will not
> receive
> # any command from peer within specified timeout, session will be
> closed.
> # Default value is 60 seconds.
> #
> # Example:
> # SessionIdleTimeout = 60
>
> #
> # FileStore
> #
> # Directory to be used for storing files uploaded by installation
> server(s).
> #
> # Example:
> # FileStore = /var/nxagentd
>
> #
> # TimeOut
> #
> # GET request timeout in seconds. If GET request cannot be completed
> for
> # specified amount of time, agent will return an error to server.
> # Default value is 5 seconds.
> #
> # Example:
> # TimeOut = 5
>
> #
> # StartupDelay
> #
> # Number of seconds agent should wait on startup before start
> servicing
> # requests. This parameter can be useful to prevent false reports
> about
> # missing processes or failed services just after monitored system
> startup.
> # Default value is 0, i.e. no startup delay.
> #
> # Example:
> # StartupDelay = 0
>
> #
> # PlatformSuffix
> #
> # String to be added as suffix to value of System.PlatformName
> parameter.
> #
> # Example:
> # PlatformSuffix = dbg
>
> #
> # EnableSubagentAutoload
> #
> # Enable or disable autoloading of platform subagent(s).
> # Default value is "yes".
> #
> # Example:
> # EnableSubagentAutoload = yes
>
> #
> # SubAgent
> #
> # Subagent to load. To load multiple subagents, you should use
> multiple
> # SubAgent parameters. Subagents will be loaded in the same order as
> they
> # appears in configuration file.
> #
> # UNIX example:
> # SubAgent = [path_to_netxms_install_dir]/lib/libnsm_linux.so
> #
> # Windows example:
> # SubAgent = winperf.nsm
>
> #
> # ExternalParameter
> #
> # Add parameter handled by external command. To add multiple
> parameters, you
> # should use multiple ExternalParameter entries.
> #
> # Syntax:
> # ExternalParameter = <parameter_name>:<command_line>
> # If you specify parameter name as "name(*)", then you can
> use $1 .. $9
> in
> # command line to substitute actual arguments passed from server.
> #
> # Examples:
> # ExternalParameter = Test:echo test
> # ExternalParameter = LineCount(*):cat $1 | wc -l
> # ExternalParameter = Test2(*):myprog $1 $2
>
>
>
> --------------------------------------
> Tim Moore
> 614.387.8197
> Network Operations Center
> ODJFS
>
> This e-mail message, including any attachments, is for the
> sole use of the intended recipient(s) and may contain
> private, confidential, and/or privileged information. Any
> unauthorized review, use, disclosure, or distribution is
> prohibited. If you are not the intended recipient, employee,
> or agent responsible for delivering this message, please
> contact the sender by reply e-mail and destroy all copies of
> the original e-mail message.
>
>
Received on Sat Sep 30 2006 - 00:25:52 EEST