Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Operations Connector10.11

Integrate > Zabbix > Install > Upgrading from a Previous Version

Upgrading from a Previous Version

If OpsCx for Zabbix is already installed on your system, you can directly upgrade from OpsCx for Zabbix 2.00 to 2.01.

Limitations

Upgrade is supported only from OpsCx for Zabbix 2.00. Upgrading from OpsCx for Zabbix 1.x is not supported.
The configuration files will not be upgraded automatically during the upgrade process. The configuration files of Ops Connector for Zabbix 2.00 and 2.01 are the same except zabbix_metrics.conf file.
After the upgrade is finished, start the event, metric and topology services manually.

Follow the installation procedure as described in Installing Ops Connector for Zabbix topic. The installation program will detect the older version and automatically upgrade your existing OpsCx for Zabbix.
After the upgrade is finished, existing configuration files remains same. If the upgrade performs correctly, the old policies remain active.

To use the new polices, deactivate the old policies and activate the new policies.

If you have the policies of OpsCx for Zabbix 2.00, no need to re-import the policies. The existing policies will work as usual. If you are using OpsCx for Zabbix 2.00, under very high metric load condition if infrastructure is found to be not scalable, you can control the load by specifying the required metrics in zabbix-metric-keys instead of * in zabbix_metrics.conf file. For information on zabbix-metric-keys, see Metric Collection Options.