Unreachable trigger not working with zabbix server 2.0 and lecacy client?

[Tristan]

Gents,

i have just updated my zabbix environment to Zabbix server 2.0.3. I noticed that when a client is not responding(offline), the unreachable alert doens't trigger.

The clients are using a zabbix 1.6.8 agent.

Is this a config issue or are the more similair issues?

[Tristan]

after a little research i read this in the logs:
8435:20121017:105248.004 item [tc-acc-01:status] became not supported: Not supported by Zabbix Agent

i use a key "status" and that key has the unreachable trigger like this:
{Template_Windows:status.last(0)}=2

It looks like the status key is depricated. I didn't read this in the upgrade notes. DId i miss something?

[Tristan]

after a little research i read this in the logs:
8435:20121017:105248.004 item [tc-acc-01:status] became not supported: Not supported by Zabbix Agent

i use a key "status" and that key has the unreachable trigger like this:
{Template_Windows:status.last(0)}=2

It looks like the status key is depricated. I didn't read this in the upgrade notes. DId i miss something?

Sorry,
i must read better!
A status item has been removed. Instead of it a new internal item - zabbix[host,agent,available] has been added. The database upgrade process doesn't convert all existing 'status' keys and associated triggers to the new syntax, so they have to be converted manually.

[davidking]

but when I added this new internal item, it's still not supported, the log from zabbix server is:
item [xxx:zabbix[host,agent,available]] became not supported: Not supported by Zabbix Agent.
zabbix server version 2.0.2 and the agent are with 2.0.2 or 2.0.3. Did anyone use this new item successfully?

[rts]

davidking: You'll need to change the type from "Zabbix Agent" to "Zabbix Internal".