NetXMS Support Forum

Please login or register.

Login with username, password and session length
Pages: [1] 2 3 ... 10
 1 
 on: Today at 02:37:22 pm 
Started by yulian - Last post by Junoonguy
Hi Yulian,

I am having a same issue, just wondering if you can able to resolve this issue.

Thanks,

 2 
 on: Today at 10:40:40 am 
Started by onrudoy - Last post by onrudoy
В том и проблема, что не правильного сабнета нету.
Сабнет по маске 22, ноды в нем, на нодах та же маска прописана, а он все равно говорит что должна быть маска 24

 3 
 on: Today at 10:32:31 am 
Started by onrudoy - Last post by Alex Kirhenshtein
Удалите неправильный сабнет, на следующем configuration poll подсеть будет пересоздана правильно.
Только убедитесь, что ноды из сабнета есть где-то в infrastructure services, чтоб сервер их не удалил автоматически.

 4 
 on: Today at 10:01:00 am 
Started by onrudoy - Last post by onrudoy
Приветствую.
Подскажите пожалуйста как отключить уведомления о некорректной маске, или как исправить?
Все маски на хостах правильные 100%
В политиках уже убрал событие, а оно все равно сыпется.

 5 
 on: Today at 07:47:32 am 
Started by rameshpavaluri - Last post by rameshpavaluri
Hi Victor,

When are you available for online session and do we use team viewer or any other  preference?

Regards
Ramesh

 6 
 on: Today at 07:41:22 am 
Started by knut4linux - Last post by knut4linux
Thx Tursiops and merry christmas  8)

 7 
 on: Today at 12:24:32 am 
Started by clifford - Last post by gdodd
I do not see a way to export that list from the console.

This entry may help to accomplish the export.

https://wiki.netxms.org/wiki/Using_nxshell_to_automate_bulk_operations#Export_list_of_interfaces_to_CSV_file


 8 
 on: Today at 12:01:48 am 
Started by CrUser - Last post by gdodd
My guess is that raid_Status is NULL or some other value that does not match any of the cases.

To catch this, add
Code: [Select]
    default:
      evt = "SYNOLOGY_RAID_STATUS_ERROR";
      details = "NO_STATUS";

Assuming that allows the script to run, check that "raidStatus" is the Parameter and not the Description for the DCI you are getting the value from.
Possibly the script is not being run on the node where the "raidStatus" DCI is located.

 9 
 on: December 12, 2018, 06:08:57 pm 
Started by meshnet - Last post by meshnet
Good day,

I would be grateful for a feature to toggle (via button or with a key-combo) how maps are navigated with the keyboard & mouse

example:

control + mousewheel up
  - map zooms in

control + mousewheel down
  - map zooms out

control + left click drag
  - pans map in any direction

alt + left click drag
  - selects rectangular area where map is centered and zoomed in


 10 
 on: December 12, 2018, 04:22:21 pm 
Started by CrUser - Last post by CrUser
Hi,

I have one problem with scripting for maintenance of synology NAS equipment. unfortunately, Synology NAS server hasn't implement SNMP agent with sending traps for some alert. Because that I have to create events and alarm internaly from DCI parameters.
For the example, for the RAID status I can read DCI paratameter from NAS device which can be number of 1- 10. Every number present special condition of current RAID status. I have written one script to anaylize DCI parameters and generate specific event for any condition (number)
This is my script for DCI parameter named "raidStatus".

raid_Status= GetDCIValueByName($node, "raidStatus");
details = "NORMAL";
switch (raid_Status)
{
   case 1:
      evt = "SYNOLOGY_RAID_STATUS_NOTIFICATION";
      details = "NORMAL";
      break;
   case 2:
      evt = "SYNOLOGY_RAID_STATUS_NOTIFICATION";
      details = "REPAIRING";
      break;
   case 3:
      evt = "SYNOLOGY_RAID_STATUS_NOTIFICATION";
      details = "MIGRATING";
      break;
   case 4:
      evt = "SYNOLOGY_RAID_STATUS_NOTIFICATION";
      details = "EXPANDING";
      break;
    case 5:
      evt = "SYNOLOGY_RAID_STATUS_NOTIFICATION";
      details = "DELETING";
      break;
    case 6:
      evt = "SYNOLOGY_RAID_STATUS_NOTIFICATION";
      details = "CREATING";
      break;
    case 7:
      evt = "SYNOLOGY_RAID_STATUS_NOTIFICATION";
      details = "SYNCING";
      break;
    case 8:
      evt = "SYNOLOGY_RAID_STATUS_NOTIFICATION";
      details = "CHECKING";
      break;
    case 9:
      evt = "SYNOLOGY_RAID_STATUS_NOTIFICATION";
      details = "ASSEMBLING";
      break;
    case 10:
      evt = "SYNOLOGY_RAID_STATUS_NOTIFICATION";
      details = "CANCELING";
      break;
    case 11:
      evt = "SYNOLOGY_RAID_STATUS_ERROR";
      details = "DEGRADE";
      break;
    case 12:
      evt = "SYNOLOGY_RAID_STATUS_ERROR";
      details = "CRASHED";
      break;

PostEvent($node,evt,null, details);

Also, I have one event and suitable event procesing policy role with activation one NXSL script for creation new events for any RAID status case, like a "SYNOLOGY_RAID_STATUS_NOTIFICATION" with massage which I would get from my script, for example  "CHECKING".
Suitable Event for this case is configured with name "SYNOLOGY_RAID_STATUS_NOTIFICATION" and message
"Synology RAID status: %1"

During testing process I got NetXMS system error message that one of parameters can not convert to string.
I didn't found much guides for NXSL programing and I can't understand where is the problem with script posting parameters.

if anybody have suggestion for resolve this problem, please help me to solve this.

Thanks,
best regards,
Tomislav

Pages: [1] 2 3 ... 10