(09-04-2012, 08:01 PM)pmcdaid link Wrote: I am not sure what you mean by " ... only work from 4.0.1 in advance."
As you suggest, I will use the massive module edit operation in the console, since adding str_warning (at least) doesn't work in the configuration file to automatically configure the agent on the server.
This would be a useful addition.
I am using 4.0.2, but the remote agent is custom for the network element I am using.
Err.. sorry, I meant that it only works since version 4.0.1...
Well.. it should work actually.. however that reminds me of an old bug where these module configuration tokens were not added to the software agent..
When I meant version 4.0.1 I was talking about the software agent's version, not the console/server version... I say this because you could perfectly have a 4.0 software agent reporting to a 4.0.2 server.
Are you sure you're using 4.0.2 for your software agent?
In any case, if you are using a custom software agent to monitor your network element, keep in mind that the XML generated by your module must include something like:
Code:
<module>
<name>ModuleName</name>
<type>generic_data_string</type>
<str_warning>matchingexpression</str_warning>
<str_critical>matcherror</str_critical>
<data>value</data>
</module>
Set your agent into debug mode or send the XML file to another path where the Data Server doesn't process it, and check the content of your module's XML structure.
If those tokens are present, then you must make sure that your Pandora Console/Server are 4.0.2 and that the DB has been properly upgraded.
Regards.