RE: Help on features of NetXMS

Server should read ARP table from router. If it don't, it's an error. I
will check this.

About services: It's almost done. The second object tree (All Services)
expected to be used that way - you can create containers (or services,
whatever you call them), organize into hierarchy, put physical nodes on
bottom. We only need to allow to put not only entire nodes, but also
components (HDD, network service, etc.) to that tree, and implement
various status calculation algorithms. I expect to do this job in the
nearest releases.

Best regards,
Victor

-----Original Message-----
From: Christoffer Blindheim [mailto:netxms_at_christoffer.totalnett.no]
Sent: Monday, July 25, 2005 8:49 PM
To: NetXMS Users
Subject: Re: [netxms-users] Help on features of NetXMS

Victor Kirhenshtein wrote:
> Hello!
>
> 1. Templates
>
thanks

>
> 2. Autodiscovery
>
> It's a known bug that isRouter is not set correctly (actually, it's
> never set). I will correct this in upcoming version 0.2.3. If don't
> look to this flag, was subnets behing your Cisco router discovered
> corectly?

NetXMS didnt discover any devices behind my cisco router. Should be easy

  to read the ARP table from Bridge-MIB.

> 3. Layer 2
>
> We have plans for layer 2 topology support and layer 2 autodiscovery,
> but it is not a high-priority goal. You can expect this functionality
> in a 3 to 6 months.
>
>
> 4. Dependency on services
> What do you exactly mean?
What I can tell so far NetXMS is a clone of HP OpenView Operations/NNM.
Just wondering if you will implement services
- A harddrive is a service
- DNS service
- HTTP is a service
- network access is a service
- SMTP is a service

the STMP is dependant of DNS,network, and disk
the HTTP is depandant of DNS,network and disk
the DNS is dependant of network and disk

What Im thinking of a service model tree that describes the dependencies

between them.

-- 
Christoffer Blindheim