08-15-2014 01:40 PM
How do I send SYSLOG messages in an OC Setup?
How do I know which collector to send SYSLOG messages to?
This will help you send SYSLOG messages to correct NetMRI Collector
We have a "well known" variable call "$netmri_ipaddress" that is the Collector that discovered the device.
Use this CCS Script:
$vendor eq “Cisco” and $sysdescr like /IOS/
Add SYSLOG to Routers and Switches
08-15-2014 02:24 PM
$netmri_ipaddress could be used in a lot of places. You could write a script to include logging or update ACLs and instead of having to hard code the IP address of NetMRI, just use $netmri_ipaddress. You can share the script with colleagues on different networks, and they don't even have to upate the script for their environment (ok maybe a few tweaks, but won't have to chance the IP of NetMRI).
Definitely a great "hidden" variable to keep in mind when writing scripts.
08-21-2014 10:02 AM
Just tested it and you can not create a group gents.
You can ask your Account Team to file and RFE
06-08-2015 04:15 AM
I wanted to verify this setting from within a policy. We've got multiple collectors so this setting isn't that easy to verify. After a lot of trying, this is what worked for me:
<PolicyRuleLogic editor="raw-xml" expression='1' xmlns='http://www.infoblox.com/NetworkAutomation/1.0/ScriptXml'> <ConfigFileCheck label='1' note='' op='contains-all'> <Expr op='concat'> <Expr value='logging '/> <Expr field='data_source.DataSourcePrivateIPDotted'/> </Expr> </ConfigFileCheck> </PolicyRuleLogic>
06-08-2015 11:22 PM
I think I've spotted a bug here.
Looks like <Expr field='data_source.DataSourcePrivateIPDotted'/> resolves to nothing once the policy is deployed making all my devices match the policy if they contain "logging " in the config. When I test the policy from the OC GUI, it works just fine.
09-08-2015 03:20 PM
You can now do it with version 7.x