Hello,
I'm starting to use low level discovery on my Zabbix 2.0.4 server.
I want to add network interfaces (with active link state) automaticaly.
The default discovery (net.if.discovery) is not good enough because it only shows the interface name and not the link status.
For this purpose I have created an PowerShell discovery script with gives me the output below. Zabbix server retrieves the discovery (with no errors on the client log) but stops with error message:
"Cannot create item [net.if.in[{#DRIVER_NAME},bytes]]: item already exists. Cannot create item [net.if.in[{#DRIVER_NAME},bytes]]:"
The item is not existing, when I take a look at the items section of the host...
I have searched for other people with the same problem, but I could only find one person with the same error message.
He had solved the problem by changing the dash(-) symbol to a underscore in the macro.
I am not using dashes, but still have the problem.
Powershell discovery script output:
I also created an extended discovery script for harddrives. That discovery is working, the output format is the same:
I attached some screenshots with my settings and errors.
Hopefully somebody could point me to the right direction...
I'm starting to use low level discovery on my Zabbix 2.0.4 server.
I want to add network interfaces (with active link state) automaticaly.
The default discovery (net.if.discovery) is not good enough because it only shows the interface name and not the link status.
For this purpose I have created an PowerShell discovery script with gives me the output below. Zabbix server retrieves the discovery (with no errors on the client log) but stops with error message:
"Cannot create item [net.if.in[{#DRIVER_NAME},bytes]]: item already exists. Cannot create item [net.if.in[{#DRIVER_NAME},bytes]]:"
The item is not existing, when I take a look at the items section of the host...
I have searched for other people with the same problem, but I could only find one person with the same error message.
He had solved the problem by changing the dash(-) symbol to a underscore in the macro.
I am not using dashes, but still have the problem.
Powershell discovery script output:
Code:
{
"data":[
{
"{#NAME}":"NIC 2"
"{#DRIVER_NAME}":"HP NC326i PCIe Dual Port Gigabit Server Adapter"
"{#ENABLED}":"False"
},
{
"{#NAME}":"NIC 1"
"{#DRIVER_NAME}":"HP NC326i PCIe Dual Port Gigabit Server Adapter #2"
"{#ENABLED}":"True"
}
]
}
Code:
{
"data":[
{
"{#DRIVE_LETTER}":"C:"
"{#VOLUME_NAME}":""
"{#FILE_SYSTEM}":"NTFS"
},
{
"{#DRIVE_LETTER}":"D:"
"{#VOLUME_NAME}":""
"{#FILE_SYSTEM}":"NTFS"
}
]
}
Hopefully somebody could point me to the right direction...
Attached Files
Comment