NetXMS Forum

Hello
i configured Cisco DSL router on the netxms, i can see the status of all interface except the dialer it show UNKNOWN, i tried to follow the MIB OID, i found the NetXMS use ifXtable even when i disbale it, and the dialer and serial interface doesn't exist in ifXtable, are there any workarround to for the console to don't use ifXtable.
thx

Hello
I installed Netxms android client to show alarms on my tablet, i configured
server : 192.168.200.200
port: 4701
login: admin
pwd: netxms

but i got connexion refused ?!!
what's the problem ? where can i allow client to connect on server ?
best regards

Thx Victor
please how we can get doc about package ? we want to develop some specific features.
best regrads

Hi
i am using java console, when i close the console or logout then i login i don't find the history of Event Monitor, are there way to display them ?
best regards

Hi Victor
yes that what i want exactly but when i create the DCI on Switch Interface i can't find it in node's data collection configuration ! this only happen with the new version 1.2.4 i didn't have this problem with version 1.2.3 !
thx

Hi i will try to get screen ASAP
but juste to inform, that when i right click on the switch and go to DCI i can't find this DCI, i only see it on the last value tab !

when i right click on the interface i can see the DCI but no checkbox for show in performance tab

you can't see this DCI under node DCI !!! this is the problem

thx, but when i create the DCI directly on the switch port i can't find checkbox for show in performance tab !! this is in the version 1.2.4

in the new release 1.2.4 in the switch on the port when i create DCI i can't see this DCI in the performance tab how can i add it ?
best regards

Ok thanks,
when i try to do layer2 topology for each switch i get the schema for almost of them, but i have problem with the cascade ports, in fact the schema show on pcs in the second switch as node connected to this port, are there way to configure port as casacde ?

(trendent) TGE-240WS and SMC8612XL3 (SMC) and DES-6500 (DLINK).
please also how to configure switch port as cascade (not trunk) so the console display all the MAC addresses for this port.
thx

I am using DLINK and TRENDENT switch, i didn't find any configuration for LLDP !

Hi
i am using version 1.2.4, i discovered many snmp switches but when i tried to create auto map and selected the seed node nothing was done, it only display the seed node, what's the problem ?
other point, in some switches i got the switches doesn't support layer2 discovery, who Netxms know if the switch have this feature or not ?
in the case of cascade port in the switch the console only display one MAC address, are there any way to tell the console that this is cascade port and can have many MAC that it have to display them ?
best regards

Dear Victor
please do you have any idea about the release date of the version 1.2.4 that include automatic map ?
best regards

Hi Victor
for the map i could find any documentation about the configuration for that i asked about nagvis.
for the time response under 1s i always get zero so in the graph no deffirence between 800ms and 8 ms which is huge difference

Hi Victor
i have to questions please :

• for the ICMP response time is declared as unsigned integer, i think this isn't not precise and don't give clear information because the time is measured in 1000s.
• for the map it's possible to integrate NagVis ?
  best regards

Hi Victor
please is the winperf and wmi subagent will be released for the version 1.2.3 or not ?
when the automatic network map will be available ?

Hi Victor
i re-installed all from scratch, with Jetty from eclipse site and java from oracle site and not from Ubuntu repository and all things are working fine now on ubuntu 12.04 server.
many thanks.

Hi Victor
the same problem of :
Cannot create network map object "dzdze": No context available outside of the request service lifecycle.
No context available outside of the request service lifecycle.

Cannot create DCI for interface: No context available outside of the request service lifecycle.
No context available outside of the request service lifecycle.